TWI748627B - Logistics information management system and related computer program product - Google Patents

Abstract

A logistics information management system is disclosed, including a block chain subsystem; a logistics service subsystem for generating a take-over request including an order event identification data and a current vendor identification data; and a recipient device for generating a delivery destination information request including the order event identification data and the current vendor identification data according to the take-over request. The block chain subsystem receives the delivery destination information request, searches for an order event recorded in a recipient smart contract stored in the block chain subsystem according to the order event identification data, and reads a valid vendor identification data from the order event. The recipient device transmits an available-to-receive notice to the logistics service subsystem under the condition that the current vendor identification data matches the valid vendor identification data.

Description

Logistics information management system and related computer program products

The invention relates to an information management system, in particular to a logistics information management system and related computer program products.

With the rise of the Internet, consumers' shopping behavior on e-commerce platforms has become more popular. Generally speaking, after consumers make a purchase on the e-commerce platform, the e-commerce platform will notify the logistics company to deliver the goods. The logistics industry will plan the delivery route to the logistics agent based on the collected orders, and then the logistics agent can deliver the goods according to the planned route. However, in the process of delivery by the logistics agent, it often happens that the consignee is not at home or unable to receive the goods, resulting in the logistics agent being unable to deliver the goods to the consignee after arriving at the destination and having to re-deliver. Therefore, in the traditional goods distribution process, the logistics person often has to call the consignee to confirm whether the goods can be received, so as to avoid the situation of unmanned pick-up on site.

In particular, when the delivered goods have special properties, such as fresh food, or products that need to be refrigerated or frozen, the logistics agent must confirm in advance whether the individual consignees are all when the logistics agent arrives at the delivery location. Can be present in person to receive the goods, or whether there is someone else who can receive the goods on their behalf.

Obviously, when using traditional goods delivery mechanisms, logistics professionals often have to contact different consignees one by one in advance to confirm that the goods can be delivered to the designated location at the appropriate time. For logistics professionals, this approach not only consumes additional communication costs, but is also time-consuming and inconvenient.

In view of this, how to improve the efficiency and convenience of logistics personnel in delivery is really unclear. To resolve the issue.

This specification provides an embodiment of a logistics information management system, which includes: a blockchain subsystem including a plurality of blockchain nodes; a logistics subsystem is set up to allow a logistics agent device to approach a target area, Generate a receiving request containing a first current operator identification data and an order event identification data; and a consignee device configured to receive the receiving request, and according to the receiving request, generate a receiving request containing the order event identification Data and a delivery destination information request of the first current operator identification data; wherein, the blockchain subsystem is configured to receive the delivery destination information request, and according to the order event identification data, find out the information in the blockchain An order event recorded in a consignee smart contract stored in the system, and a qualified vendor identification data in the order event is read; where the qualified vendor identification data matches the first current vendor identification data In this case, the blockchain subsystem will read a delivery destination information in the order event; wherein, the consignee device is also set to generate and transmit a receivable after receiving the delivery destination information Notify the logistics subsystem.

This specification also provides an embodiment of a computer program product that allows a consignee device used in a logistics information management system to perform a consignee privacy protection operation, wherein the logistics information management system includes a zone Block chain subsystem, a logistics subsystem and the consignee device. The consignee's privacy protection operation includes: receiving a receiving request generated by the logistics subsystem when a logistics device is close to a target area, wherein the receiving request includes a first current operator identification data and An order event identification data; according to the receipt request, a delivery destination information request including the order event identification data and the first current operator identification data is generated; a delivery destination information is received; and when the delivery destination is received After the information, it generates and sends a receivable notification to the logistics subsystem; among them, the blockchain subsystem can receive the delivery destination information request, and based on the order event identification data, find out in the blockchain subsystem An order event in a consignee’s smart contract, and the order event includes a qualified vendor identification data; wherein, the qualified vendor identification data and the first current vendor identification Only when the data matches, the blockchain subsystem will provide the delivery destination information.

One of the advantages of the above-mentioned embodiment is that the logistics agent does not need to contact different consignees one by one in advance, and can automatically inquire about the goods located in the target area through the coordination operation of the logistics subsystem, the blockchain subsystem, and the consignee device. Whether the consignee is willing to receive the goods, it can effectively save the work time of the logistics staff, and thus can improve the efficiency of goods delivery.

Another advantage of the above-mentioned embodiment is that only when the current location of the consignee device is within the delivery destination, the consignee device can send the receivable notification to the logistics subsystem, so it can effectively avoid Consignees who are not in the delivery destination deliberately falsely claim that they can receive the goods, thereby ruining the possibility of the logistics staff making a trip in vain.

Other advantages of the present invention will be explained in more detail with the following description and drawings.

100: logistics information management system (logistics information management system)

101, 102: purchaser device (purchaser device)

103, 104: recipient device

105, 106: logistician device

110: e-commerce vendor subsystem

112: web server

114: database

116: block chain computing circuit

120, 130: logistics service subsystem

122, 132: communication circuit

124, 134: control circuit

126, 136: database

128, 138: block chain computing circuit

140: Block chain node cluster (block chain node cluster)

141~147: block chain node

150: block chain subsystem (block chain subsystem)

162: processing circuit

164: storage circuit

166: recipient privacy protection program

210: account creating module

220: take-over request processing module

230: position request processing module

240: encryption module

302~344, 402~418, 502~520, 602~616, 702~724, 802~818, 902~916, 1002~1016, 1102~1126: operation

FIG. 1 is a simplified functional block diagram of a logistics information management system according to an embodiment of the present invention.

FIG. 2 is a simplified functional module diagram of an embodiment of a consignee privacy protection program stored in a consignee device in FIG. 1.

FIG. 3 is a simplified flowchart of an embodiment of a method for registering related accounts of the logistics information management system in FIG. 1.

4 to 5 are simplified flowcharts of a method for ordering goods according to an embodiment of the present invention.

6 to 8 are simplified flowcharts of a route planning method for a target area according to an embodiment of the present invention.

9 to 11 are simplified flowcharts of a method for confirming the location of a consignee according to an embodiment of the present invention.

The embodiments of the present invention will be described below in conjunction with related drawings. In the drawings, the same reference numerals indicate the same or similar elements or method flows.

FIG. 1 is a simplified functional block diagram of a logistics information management system 100 according to an embodiment of the present invention. The logistics information management system 100 is used to distribute the delivered products to related consumers. The logistics information management system 100 includes an e-commerce subsystem 110, multiple logistics subsystems (for example, in FIG. 1 The exemplary logistics subsystems 120~130), multiple purchaser devices (e.g., the exemplary purchaser devices 101-102 in FIG. 1), and multiple consignee devices (e.g., the exemplary receiver devices in FIG. 1) Human devices 103-104), multiple logistics personnel devices (for example, the exemplary logistics personnel devices 105-106 in FIG. 1), and a blockchain subsystem 150.

In this embodiment, the e-commerce subsystem 110 is a system operated by a specific e-commerce company. The e-commerce merchant can use the e-commerce subsystem 110 to generate a web page or application screen for the purchaser to order goods. After the e-commerce subsystem 110 receives the order placed by the purchaser, it will ask the cooperating logistics company whether it is willing to undertake the delivery of related goods. After confirming the logistics company willing to deliver the goods, the e-commerce subsystem 110 can record the relevant order information and the identification data of the corresponding logistics company in the blockchain subsystem 150, and provide the relevant order information to the corresponding logistics company. The logistics sub-system (for example, the aforementioned logistics sub-system 120 or 130) is used by the corresponding logistics company to perform the subsequent goods distribution process. In addition, the e-commerce operator can also use the e-commerce subsystem 110 to transmit the goods information, expected delivery time (expected delivery time), and delivery location (delivery location) information to the relevant consignee’s device (for example, The aforementioned consignee device 103 or 104).

In this embodiment, the user of the purchaser device 101 or 102 can control the purchaser device 101 or 102 to purchase goods from the e-commerce subsystem 110 on the webpage or application screen provided by the e-commerce subsystem 110.

In practice, different purchaser devices 101 to 102 can be used by different purchasers. For the convenience of description, the user of the purchaser device 101 is referred to as a first purchaser, and the user of the purchaser device 102 is referred to as a second purchaser.

In the embodiment of FIG. 1, the different logistics subsystems 120 to 130 are systems operated by different logistics operators, and the different logistics devices 105 to 106 are equipment used by different logistics operators. For the convenience of description, the operator of the logistics subsystem 120 is referred to as a first logistics company, the operator of the logistics subsystem 130 is referred to as a second logistics company, and the user of the logistics system 105 is referred to as It is a first-rate logistics man, and The user of the Liushi device 106 calls it a second logistics worker. In addition, the following assumes that the first logistics personnel belong to the personnel of the first logistics company, and it is assumed that the second logistics personnel belong to the personnel of the second logistics company.

After the e-commerce subsystem 110 provides the order information to the logistics subsystem 120 or 130, the logistics subsystem 120 or 130 can plan the relevant logistics delivery itinerary according to the received order information, and the relevant logistics company can assign a suitable logistics taxi Carry out goods distribution operations according to the planned distribution itinerary.

For example, if the e-commerce company assigns the aforementioned first logistics company to deliver specific goods and provides order information to the logistics subsystem 120 through the e-commerce subsystem 110, the first logistics company can assign the first logistics company to carry out the aforementioned specific goods Distribution operations. In this case, the first logistics agent can use the logistics agent device 105 to obtain the distribution itinerary planned by the logistics subsystem 120, and perform the distribution operation of related goods accordingly.

After the e-commerce subsystem 110 provides the information of the goods purchased by the purchaser, the expected delivery time, and the receiving location to the consignee device 103 or 104, the consignee device 103 or 104 can send the aforementioned information It is displayed to the user in an appropriate manner so that the user of the consignee device 103 or 104 can obtain the aforementioned information.

In the process of the logistics agent distributing the delivered goods to the user of the consignee device 103 or 104, the consignee device 103 or 104 may request the blockchain subsystem 150 to verify whether the logistics provider to which the logistics agent belongs is valid Logistics industry. In addition, after confirming that the logistics company to which the logistics agent belongs is a qualified logistics company, the user of the consignee device 103 or 104 can also check whether he can be at the specified time through the consignee device 103 or 104 at an appropriate time. Notify the logistics staff of the relevant information of the receipt so that the logistics staff can know the aforementioned information.

In practice, different consignee devices 103-104 can be used by different users. In practical applications, the user of the consignee device 103 or 104 may be the aforementioned first purchaser or second purchaser, or other users other than the first and second purchasers. For the convenience of description, the user of the consignee device 103 is referred to as a first consignee, and the user of the consignee device 104 is referred to as a second consignee.

As mentioned above, the blockchain subsystem 150 records the order information generated by the e-commerce subsystem 110 and the identification data of the corresponding logistics company. In addition, in the process of the logistics agent distributing the delivered goods to the user of the consignee device 103 or 104, the blockchain subsystem 150 can verify whether the logistics company to which the specific logistics agent belongs is qualified according to the request of the consignee device 103 or 104 In order to prevent the consignee device 103 or 104 from mis-transmitting sensitive data such as the user’s current location information to the logistics agent of an unqualified logistics company.

In practice, the purchaser's devices 101~102 can be implemented by devices that can be connected to the Internet and can execute browsers or related applications, such as tablet computers, notebook computers, desktop computers, and mobile communication devices (such as smart phones, Wearable devices), or other similar devices.

As shown in FIG. 1, the consignee device 103 includes a processing circuit 162 and a storage circuit 164. The storage circuit 164 is used to store a consignee privacy protection program 166. In operation, the processing circuit 162 can control the overall operation of the consignee device 103 and execute the consignee privacy protection program 166 to run a consignee privacy protection operation. In this embodiment, other consignee devices in the logistics information management system 100 (for example, the consignee device 104) all have a main structure similar to the consignee device 103. For the sake of brevity, it will not be repeated here. .

The consignee devices 103-104 can be implemented by devices with positioning functions and capable of networking, such as tablet computers, notebook computers, mobile communication devices (such as smart phones, wearable devices), or other similar devices. In operation, the consignee device 103~104 can be used to receive and utilize Global Positioning System (GPS), BeiDou Navigation Satellite System (BDS), and Assisted GPS (AGPS) ), or signals generated by other suitable positioning systems to generate positioning information.

Please note that when the purchaser and the consignee are the same user, the purchaser's device and the consignee's device of the user may be different devices or the same device. When the purchaser and the consignee are different users, the purchaser's device of the purchaser and the consignee's device of the consignee may be different devices or the same device.

The logistics taxi devices 105-106 can be implemented by devices with positioning functions and capable of connecting to the Internet, such as mobile phones, tablet computers, and notebook computers. In operation, the logistics taxi devices 105-106 can be used to receive and use signals generated by the Global Positioning System, Beidou Satellite Navigation System, Assisted Satellite Positioning System, or other suitable positioning systems to generate positioning information.

In the embodiment of FIG. 1, the e-commerce subsystem 110 includes a website server 112, a database 114, and a blockchain computing circuit 116. The logistics subsystem 120 includes a communication circuit 122, a control circuit 124, a database 126, and a blockchain operation circuit 128. The logistics subsystem 130 includes a communication circuit 132, a control circuit 134, a database 136, and a blockchain operation circuit 138. The blockchain node cluster 140 includes a plurality of blockchain nodes (for example, the exemplary blockchain nodes 141 to 147 shown in FIG. 1).

In the e-commerce subsystem 110, the website server 112 is configured to communicate with the purchaser's device 101~102 and the consignee's device 103~104 through the Internet or other networks to provide web pages or application screens The users of the purchaser devices 101-102 purchase goods and establish related orders, and provide the goods information, expected delivery time, receiving location, etc., to the consignee devices 103-104. The website server 112 is also set to communicate with the logistics subsystem 120~130 and the blockchain subsystem 150 through a suitable network (intranet or Internet), so as to transmit the related order to the logistics subsystem 120 ~130, and store relevant order information in the blockchain subsystem 150. The database 114 is coupled to the website server 112 and used to store the e-commerce account of individual consignees (hereinafter referred to as the consignee account) and order-related information for the website server 112 to query. The blockchain computing circuit 116 is coupled to the website server 112, and is used to act as one of the nodes of the blockchain subsystem 150, and can act as a communication bridge between the e-commerce subsystem 110 and the blockchain subsystem 150 .

In the logistics subsystem 120, the communication circuit 122 is configured to communicate with the e-commerce subsystem 110 and the blockchain subsystem 150 via the Internet or other networks. The control circuit 124 is coupled to the communication circuit 122, the database 126, and the blockchain operation circuit 128, and is provided To control the operation of the aforementioned devices. The blockchain arithmetic circuit 128 is coupled to the communication circuit 122 to act as one of the nodes of the blockchain subsystem 150 and can serve as a communication bridge between the logistics subsystem 120 and the blockchain subsystem 150.

In the logistics subsystem 130, the communication circuit 132 is configured to communicate with the e-commerce subsystem 110 and the blockchain subsystem 150 via the Internet or other networks. The control circuit 134 is coupled to the communication circuit 132, the database 136, and the blockchain operation circuit 138, and is configured to control the operation of the aforementioned devices. The blockchain computing circuit 138 is coupled to the communication circuit 132 to act as one of the nodes of the blockchain subsystem 150 and can serve as a communication bridge between the logistics subsystem 130 and the blockchain subsystem 150.

The blockchain subsystem 150 in this embodiment is composed of the blockchain computing circuit 116 in the e-commerce subsystem 110, the blockchain computing circuit 128 in the logistics subsystem 120, and the blockchain computing in the logistics subsystem 130. The circuit 138 is composed of multiple blockchain nodes 141 to 147 in the blockchain node cluster 140.

In practice, the website server 112 can be implemented with a single server, or can be implemented with a combination of multiple servers located in the same geographic area or located in different geographic areas. Blockchain computing circuits 116, 128, 138, and blockchain nodes 141~147 can all be implemented with one or more processor modules or computers suitable for blockchain consensus algorithm operations . The communication circuits 122 and 132 can be implemented by various appropriate circuits that comply with relevant network communication, wireless communication, or mobile communication specifications, such as network interface cards (NIC), wireless transmission (Wi-Fi) circuits, Or mobile communication circuits and so on. Both the control circuits 124 and 134 can be implemented by one or more processor modules with appropriate computing capabilities. The databases 114, 126, and 136 can all be implemented using various relational databases or non-relational databases.

In some embodiments, the blockchain computing circuit 116 can be integrated into the website server 112. Similarly, the blockchain computing circuit 128 can be integrated into the control circuit 124, or the blockchain computing circuit 138 can be integrated into the control circuit 134.

Please note that the aforementioned purchaser devices 101~102, consignee devices 103~104, logistics staff Devices 105~106, e-commerce subsystem 110, logistics subsystem 120~130, in actual implementation, can be set up for the user to control the required man-machine interface devices (for example, display, keyboard, mouse, touch screen, etc.) ), but in order to simplify the content of the drawing, these man-machine interface devices are not shown in Figure 1.

The consignee privacy protection program 166 in the aforementioned consignee device 103 can be implemented by a computer program product composed of one or more functional modules. For example, FIG. 2 is a simplified functional module diagram of the consignee privacy protection program 166 in FIG. 1. In the embodiment of FIG. 2, the consignee privacy protection program 166 includes an account creation module 210, a receipt request processing module 220, a positioning information request processing module 230, and an encryption module 240.

The following is used with FIG. 3 to further illustrate the registration method of the relevant account in the logistics information management system 100. FIG. 3 is a simplified flowchart of an embodiment of a method for registering related accounts of the logistics information management system 100.

In the flowchart of FIG. 3, the process in the column of a specific device represents the process performed by the specific device. For example, the part marked in the "Consignee Device" field is the process performed by any consignee device; the part marked in the "E-commerce Subsystem" field is the process performed by the e-commerce subsystem 110 The process performed; the part marked in the "blockchain subsystem" field is the process performed by the blockchain subsystem 150; the part marked in the "logistics subsystem" field is the process performed by any logistics The flow of the subsystem; the rest can be deduced by analogy. The aforementioned logic is also applicable to other subsequent flowcharts.

In order to be able to deploy a smart contract, query, or modify the content of the smart contract on the blockchain subsystem 150, the e-commerce operator can register with the blockchain subsystem 150 to obtain the login qualification. For example, an e-commerce operator can use the e-commerce subsystem 110 to register with the blockchain subsystem 150. At this time, the e-commerce subsystem 110 can perform the process 302 to send a corresponding registration request to the blockchain subsystem 150.

In practice, the e-commerce subsystem 110 can use the website server 112 or the blockchain computing circuit 116 to communicate with the blockchain subsystem 150 to send a registration request to the blockchain subsystem 150.

In the process 304, the blockchain subsystem 150 may receive the registration request generated by the e-commerce subsystem 110.

Then, the blockchain subsystem 150 can perform the process 306 to generate an e-commerce subsystem personal account (PA) corresponding to the e-commerce subsystem 110 according to the registration request of the e-commerce subsystem 110.

In the process 308, the blockchain subsystem 150 may transmit the account information of the personal account of the e-commerce subsystem (hereinafter referred to as the personal e-commerce account information) to the e-commerce subsystem 110. The aforementioned e-commerce personal account information can usually include a blockchain address representing a personal account of an e-commerce subsystem (hereinafter referred to as the e-commerce account blockchain address), which is similar to the e-commerce subsystem 110 or its e-commerce provider. A corresponding private key (hereinafter referred to as an e-commerce private key).

In the process 310, the e-commerce subsystem 110 can receive the e-commerce personal account information generated by the blockchain subsystem 150 through the website server 112 or the blockchain computing circuit 116, and can store the received e-commerce personal account information In the database 114. Afterwards, the e-commerce operator can use the e-commerce subsystem 110 to log in to the blockchain subsystem 150 with the obtained e-commerce account blockchain address and e-commerce private key, so as to establish, query, or modify related smart contracts.

Similarly, in order to be able to access the data in the blockchain subsystem 150, the logistics industry can register with the blockchain subsystem 150 to obtain the login qualification. For example, a logistics company can use the corresponding logistics subsystem to register with the blockchain subsystem 150. At this time, the logistics subsystem can perform the process 312 to transmit a corresponding registration request to the blockchain subsystem 150.

For example, when the first logistics company uses the logistics subsystem 120 to register with the blockchain subsystem 150, the control circuit 124 of the logistics subsystem 120 will perform the process 312 to use the communication circuit 122 or the blockchain computing circuit 128 to transmit a corresponding The registration request is sent to the blockchain subsystem 150.

For another example, when a second logistics company uses the logistics subsystem 130 to register with the blockchain subsystem 150, the control circuit 134 of the logistics subsystem 130 will perform the process 312 to use the communication circuit 132 or the blockchain computing circuit 138 to transmit a The corresponding registration request to the blockchain Subsystem 150.

In the process 314, the blockchain subsystem 150 will receive the registration request generated by the relevant logistics subsystem. For example, the blockchain subsystem 150 may receive the registration request generated by the aforementioned logistics subsystem 120 or the registration request generated by the aforementioned logistics subsystem 130.

In the process 316, the blockchain subsystem 150 may generate a logistics subsystem personal account corresponding to the logistics subsystem according to the registration request of the specific logistics subsystem.

For example, the blockchain subsystem 150 can generate the first logistics subsystem personal account corresponding to the logistics subsystem 120 according to the registration request of the logistics subsystem 120.

For another example, the blockchain subsystem 150 can generate a second logistics subsystem personal account corresponding to the logistics subsystem 130 according to the registration request of the logistics subsystem 130.

In the process 318, the blockchain subsystem 150 may transmit the account information of the personal account of the logistics subsystem to the corresponding logistics subsystem.

For example, the blockchain subsystem 150 can transmit the account information of the personal account of the first logistics subsystem (hereinafter referred to as the first account information) to the logistics subsystem 120. The aforementioned first account information usually includes the blockchain address representing the personal account of the first logistics subsystem (hereinafter referred to as the first blockchain address), and a private key corresponding to the logistics subsystem 120 or the first logistics company. (Hereinafter referred to as the first private key). In this case, the control circuit 124 of the logistics subsystem 120 can perform the process 320 to use the communication circuit 122 or the blockchain operation circuit 128 to receive the aforementioned first account information, and the control circuit 124 can transfer the first account information Store in the database 126.

For another example, the blockchain subsystem 150 can transmit the account information of the personal account of the second logistics subsystem (hereinafter referred to as the second account information) to the logistics subsystem 130. The aforementioned second account information usually includes the blockchain address representing the personal account of the second logistics subsystem (hereinafter referred to as the second blockchain address), and a private key corresponding to the logistics subsystem 130 or the second logistics company. (Hereinafter referred to as the second private key). In this case, the control circuit 134 of the logistics subsystem 130 can perform the process 320 to use the communication circuit 132 or the blockchain operation circuit 138 to receive the aforementioned second account information, and the control circuit 134 can transfer the second account information The account information is stored in the database 136.

After that, the first logistics company can use the logistics subsystem 120 to log in to the blockchain subsystem 150 with the aforementioned first blockchain address and first private key to access the blockchain subsystem 150.

Similarly, the second logistics company can use the logistics subsystem 130 to log in to the blockchain subsystem 150 with the aforementioned second blockchain address and second private key to access the blockchain subsystem 150.

On the other hand, in order to receive notifications from the e-commerce subsystem 110 (such as product information, expected delivery time, receiving location, etc.), the consignee can register with the website server 112 of the e-commerce subsystem 110 to receive The foregoing notice.

For example, the aforementioned first consignee can use the consignee device 103 to register with the website server 112 of the e-commerce subsystem 110. In practice, the first consignee can input relevant registration information on the consignee device 103, such as the consignee’s name, consignee alias, account name, phone number, identification number, and/or other Information for indicating the identity of the first consignee for registration, where the account name can be a combination of characters, numbers, and/or symbols set by the first consignee. In this case, the consignee device 103 will proceed to the process 322.

In the process 322, the processing circuit 162 will, under the control of the account creation module 210 of the consignee privacy protection program 166, send a corresponding consignee account request containing the aforementioned registration data to the website server 112 of the e-commerce subsystem 110.

Then, the website server 112 can perform the process 324 to receive the consignee account request generated by the consignee device 103.

In the process 326, the website server 112 of the e-commerce subsystem 110 may establish a corresponding consignee account (hereinafter referred to as the first consignee account) according to the received consignee account request, and assign the first consignee account number 1. The account information of the consignee account is stored in the database 114. In practice, the account information of the first consignee account may include the aforementioned registration information of the first consignee, for example, the consignee’s name, consignee alias, account name, telephone number, identification number, and/or Other information that can be used to indicate the identity of the first consignee.

In the process 328, the website server 112 of the e-commerce subsystem 110 may send the aforementioned first The account information of the consignee account is given to the consignee device 103.

At this time, the consignee device 103 will proceed to the process 330. In the process 330, the account creation module 210 of the consignee privacy protection program 166 can control the processing circuit 162 to receive the account information of the first consignee account generated by the e-commerce subsystem 110. In this way, the first consignee can use the consignee device 103 to log in to the website server 112 of the e-commerce subsystem 110 with the first consignee account.

In the logistics information management system 100, users of other consignee devices (for example, the aforementioned consignee device 104) can use their respective consignee devices to register with the e-commerce subsystem 110 in the same manner as described above. For example, the aforementioned second consignee can use the consignee device 104 to register with the e-commerce subsystem 110 to obtain a corresponding second consignee account.

As shown in FIG. 3, after the e-commerce subsystem 110 establishes the corresponding consignee account for individual consignees in the aforementioned process 326, the e-commerce subsystem 110 will also proceed to the process 332.

In the process 332, the website server 112 or the blockchain computing circuit 116 can send a consignee smart contract establishment request corresponding to a specific consignee to the blockchain subsystem 150.

Next, the blockchain subsystem 150 will perform the process 334 to receive the consignee smart contract establishment request generated by the e-commerce subsystem 110.

In the process 336, the blockchain subsystem 150 may establish a corresponding consignee smart contract according to the received consignee smart contract establishment request.

In the process 338, the blockchain subsystem 150 may send the generated smart contract identification data of the consignee to the e-commerce subsystem 110. In practice, the aforementioned smart contract identification data of the consignee can be implemented by the blockchain address of the smart contract of the consignee in the blockchain subsystem 150.

In the process 340, the website server 112 or the blockchain computing circuit 116 of the e-commerce subsystem 110 can receive the consignee's smart contract identification data generated by the blockchain subsystem 150, and the website server 112 can receive the goods The personal smart contract identification data is stored in the database 114, and the consignee smart contract identification data is associated with a consignee account corresponding to the specific consignee Number to establish associations.

In the process 342, the website server 112 of the e-commerce subsystem 110 can send the consignee smart contract identification data generated by the blockchain subsystem 150 to the corresponding consignee device, and the consignee device will The process 344 is performed to receive and store the aforementioned consignee smart contract identification data.

For example, after the e-commerce subsystem 110 establishes the first consignee account corresponding to the first consignee, it can proceed to the process 332 to transmit a consignee smart contract establishment request corresponding to the aforementioned first consignee to the district The blockchain subsystem 150 enables the blockchain subsystem 150 to perform the process 336 to establish a first consignee smart contract corresponding to the first consignee. Then, the blockchain subsystem 150 can send the smart contract identification data of the first consignee to the e-commerce subsystem 110, and the website server 112 can perform the process 340 to store the smart contract identification data of the first consignee in the data Library 114. In addition, the website server 112 also performs a process 342 to transmit the identification data of the first consignee smart contract to the corresponding consignee device 103. At this time, the processing circuit 162 of the consignee device 103 will perform the process 344 according to the control of the account creation module 210 of the consignee privacy protection program 166 to receive and store the first consignee smart contract identification data.

For another example, after the e-commerce subsystem 110 establishes the second consignee account corresponding to the second consignee, it can also perform the process 332 to transmit a consignee smart contract establishment request corresponding to the aforementioned second consignee The blockchain subsystem 150 is given to the blockchain subsystem 150 to perform the process 336 to establish a second consignee smart contract corresponding to the second consignee. Then, the blockchain subsystem 150 can send the smart contract identification data of the second consignee to the e-commerce subsystem 110, and the website server 112 can proceed to the process 340 to store the smart contract identification data of the second consignee in the data Library 114. In addition, the website server 112 will also perform a process 342 to send the second consignee smart contract identification data to the corresponding consignee device 104. At this time, the consignee device 104 will perform the process 344 according to the control of its consignee privacy protection program (not shown in the figure) to receive and store the second consignee smart contract identification data.

The following will further illustrate the operation mode of the logistics information management system 100 when different buyers order goods in conjunction with FIGS. 4 to 5. 4 to 5 are simplified flowcharts of a method for ordering goods according to an embodiment of the present invention.

When a purchaser wants to purchase a specific item, he can log in to the website server 112 of the e-commerce subsystem 110 through his device, and select the item to be purchased from the webpage or application screen provided by the website server 112, and Provide consignee information and receiving location. In practice, the purchaser can provide the consignee’s name, consignee’s alias, account name, phone number, identification number, and/or other information that can indicate the identity of the consignee related to a specific consignee Give it to the web server 112 as the aforementioned consignee information.

In practice, the aforementioned consignee information can be or include the consignee’s name, consignee’s alias, consignee’s account name, consignee’s phone number, consignee’s identification number, and / Or other information that can indicate the identity of the consignee. In addition, the aforementioned receiving location may be or may include a specific address, specific positioning coordinates, text describing a specific location, or text describing the correlation with a specific landmark.

In this case, the website server 112 of the e-commerce subsystem 110 can perform the process 402 to receive the goods information (for example, the name of the goods, the serial number of the goods, the code of the goods, the identification code of the goods), the consignee information, And receiving position.

In some embodiments, in addition to the aforementioned goods identification data, consignee information, and receiving location, the purchaser can also set the webpage or application screen provided by the website server 112 through the purchaser’s device The assigned delivery time of the goods, for example, a specific date, and/or a specific time period (for example, morning, afternoon, evening, and/or a specific time point).

In this case, the website server 112 of the e-commerce subsystem 110 may also receive the designated delivery time set by the purchaser in the process 402.

For example, when the first purchaser uses the purchaser's device 101 to log in to the website server 112 and purchase goods, the purchaser's device 101 can set the related product information (hereinafter referred to as the first target product data) and the consignee's data (hereinafter (Referred to as the first target consignee profile), The receiving location (hereinafter referred to as the first target receiving location), and the designated delivery time (hereinafter referred to as the first target delivery time). In this case, the website server 112 may perform the process 402 to receive the first target product data, the first target consignee data, the first target receiving location, and the first target product data set by the first purchaser through the purchaser device 101. A target delivery time.

For another example, when the second purchaser uses the purchaser's device 102 to log in to the website server 112 and purchase goods, the purchaser's device 102 can set the related goods data (hereinafter referred to as the second target product data) and the consignee data ( Hereinafter referred to as the second target consignee data), the receiving location (hereinafter referred to as the second target receiving location), and the designated delivery time (hereinafter referred to as the second target delivery time). In this case, the website server 112 may perform the process 402 to receive the second target product data, the second target consignee data, the second target receiving location, and the second target product data set by the second purchaser through the purchaser device 101 2. Target delivery time.

In the process 404, the website server 112 of the e-commerce subsystem 110 can create a corresponding initial order containing the goods information set by the purchaser, the consignee information, the receiving location, and the designated delivery time.

For example, in the process 404, the website server 112 can set the first target product data, the first target consignee data, the first target receiving location, and the first target delivery time (if the first If specified by the purchaser), create a corresponding first initial order containing the aforementioned information. In practice, the website server 112 can also record the product attributes corresponding to the first target product (for example, whether it is an item that needs to be refrigerated, an item that needs to be frozen, a fragile item, a bulky item, etc.), and also records it in the aforementioned In the first initial order.

For another example, in the process 404, the website server 112 may set the second target product data, the second target consignee data, the second target receiving location, and the second target delivery time (if the first 2. If specified by the purchaser), create a corresponding second initial order containing the aforementioned information. Similarly, the website server 112 may also determine the product attributes corresponding to the second target product (for example, whether it is an item requiring refrigeration, an item requiring freezing Items, fragile items, bulky items, etc.) are also recorded in the aforementioned second initial order.

In the process 406, the website server 112 of the e-commerce subsystem 110 may perform a location de-identification process on the receiving location set by the purchaser to generate a delivery corresponding to the receiving location. Destination information (delivery destination information). In practice, the website server 112 can generate the corresponding delivery destination information by removing part of the data in the receiving location that can be used to determine the specific location, or obscuring the specific location of the receiving location, so that The delivery destination information can be used to represent a specific delivery destination (delivery destination) that is spatially related to the delivery location, but the specific location of the delivery location cannot be restored from the delivery destination information.

For example, assuming that the first target receiving location set by the first purchaser is a specific address, the website server 112 may perform spatial de-identification processing on the specific address to generate a specific address corresponding to the specific address but not including the specific address. Complete content of a first delivery destination information (delivery destination information). For example, the website server 112 may remove the house number and floor information of the specific address, and use the removed result as the first delivery destination information. For another example, the website server 112 may remove the house number, floor information, and street section number of the specific address, and use the removed result as the first delivery destination information. For another example, the website server 112 may remove the house number, floor information, and street name of the specific address, and use the removed result as the first delivery destination information.

For another example, assuming that the first target receiving location set by the first purchaser is a geographic coordinate in the data format (x1, y1), the website server 112 may de-identify the geographic coordinate to generate the A geographic grid (geographical grid) with corresponding geographic coordinates but covering a larger area is used as a corresponding first delivery destination information. For example, the website server 112 may expand the geographic coordinates outward by a predetermined range (for example, 3 meters, 5 meters, 10 meters, 20 meters, 50 meters, 100 meters, etc.). A corresponding geospatial grid is formed, and the geospatial grid is used as the first delivery destination information corresponding to the first target receiving location.

Similarly, the website server 112 can also use the aforementioned various methods to perform the spatial de-identification process of the process 406 on the second target receiving location set by the aforementioned second purchaser to generate corresponding second delivery destination information.

The website server 112 may perform the process 408 after establishing an initial order each time, so as to generate a corresponding delivery request according to the initial order. As mentioned earlier, the content of each initial order may include the product information set by the purchaser, consignee information, receiving location, target delivery time, and product attributes. In practice, the website server 112 can integrate the product information recorded in the initial order, a delivery destination information generated based on the receiving location, and an expected delivery time in an appropriate data format to correspond to the initial order One of the delivery requests, so that the content of the delivery request includes product information, delivery destination information, and expected delivery time. The aforementioned expected delivery time may be the target delivery time set by the purchaser, or the delivery time set by the e-commerce subsystem 110 according to a predetermined condition. For example, the e-commerce subsystem 110 can use the result of adding a predetermined number of hours or days to the time point of the initial order creation as the expected delivery time. In some applications, the website server 112 may also record the consignee information and/or product attributes (for example, whether it is an item requiring refrigeration, an item requiring freezing, a fragile item, a bulky item, etc.), and also record it in The delivery request corresponding to the initial order.

In practice, after generating a delivery request, the website server 112 can transmit the delivery request to one or more logistics subsystems. Alternatively, the website server 112 may also send the multiple delivery requests to one or more logistics subsystems in batches after generating multiple delivery requests.

For example, the website server 112 may generate a delivery request corresponding to the aforementioned initial order in the process 408, and then transmit the delivery request to a specific logistics subsystem.

In one embodiment, the website server 112 may send the delivery request to a randomly selected logistics subsystem.

In another embodiment, the e-commerce company may assign corresponding priorities to the logistics subsystems of all cooperative logistics companies in advance, and the website server 112 may transmit the delivery request to the logistics subsystem with the highest priority in the process 408. Ordered logistics subsystem.

For the convenience of description, it is assumed here that the website server 112 transmits the distribution request to the logistics subsystem 120 corresponding to the first logistics company in the process 408. In this case, the communication circuit 122 of the logistics subsystem 120 will perform the process 410 to receive the delivery request generated by the website server 112.

Then, the control circuit 124 of the logistics subsystem 120 can determine whether to accept the delivery request generated by the website server 112 according to the operation of related personnel or a predetermined logistics processing energy algorithm. For example, the control circuit 124 or related personnel may assign the attributes of the goods, the distance to the delivery destination, the expected delivery time, the number of available means of transport, the types of available means of transport, the types of equipment on the available means of transport, and the number of available logistics taxis. , And/or various other related factors are taken into consideration together to determine whether the received delivery request can be accepted.

If the control circuit 124 decides to reject the delivery request, the process 412 can be performed to send a corresponding rejection notice to the website server 112 through the communication circuit 122. At this time, the website server 112 will perform the process 414 to receive the rejection notice generated by the logistics subsystem 120.

In this case, the website server 112 may transmit the delivery request to another randomly selected logistics subsystem (for example, the logistics subsystem 130). Alternatively, the website server 112 may transmit the delivery request to another logistics subsystem (for example, the logistics subsystem 130) with the next highest priority.

Conversely, if the control circuit 124 decides to accept the delivery request, the process 416 can be performed to send a corresponding acceptance notification to the website server 112 through the communication circuit 122.

For another example, the website server 112 may generate multiple delivery requests corresponding to multiple initial orders in the process 408, and then send the multiple delivery requests in batches to a specific logistics subsystem.

In one embodiment, the website server 112 may send multiple delivery requests in batches to random A selected logistics subsystem (for example, logistics subsystem 120).

In another embodiment, the e-commerce company can assign corresponding priorities to the logistics subsystems of all cooperative logistics companies in advance, and the website server 112 can send multiple delivery requests in batches to those with the highest priority in the process 408. Ordered logistics subsystem.

If the website server 112 receives a logistics subsystem to generate a rejection notice for the multiple delivery requests, the website server 112 may send the multiple delivery requests to another randomly selected logistics subsystem (for example, the logistics subsystem 130) . Alternatively, the website server 112 may transmit a plurality of the delivery requests to another logistics subsystem (for example, the logistics subsystem 130) with the next highest priority. The other operations of the logistics subsystem are similar to those mentioned above and will not be described again.

Since the website server 112 will spatially de-identify the receiving location in the aforementioned process 406 to convert it into the corresponding delivery destination information, the control circuit 124 of the logistics subsystem 120 determines whether to accept the delivery request in the aforementioned process. During the process, the specific address or precise geographic coordinates of the receiving location cannot be obtained, so the control circuit 124 does not and does not need to take the specific address or precise geographic coordinates of the receiving location into consideration. This approach can ensure that the logistics subsystem 120 cannot obtain the specific address or precise geographic coordinates of the receiving location at this stage, and can prevent the receiving location of the goods from being leaked due to various human factors or technical problems, and thus can be The privacy of the receiving location provides higher protection.

In the process 418, the website server 112 will receive the acceptance notification generated by the logistics subsystem 120 and establish a corresponding target order.

In practice, the website server 112 can create a correspondence that includes the partial content of the corresponding initial order, the delivery destination information in the corresponding delivery request and the expected delivery time, and the identification data of the logistics company that accepts the delivery request in the process 418. Target order. In this embodiment, the logistics company that accepts the delivery request refers to the first logistics company corresponding to the logistics subsystem 120.

For example, the website server 112 in the process 418 may create a product information and a delivery destination. Information, expected delivery time, and a corresponding target order with the identification data of the first logistics company.

For another example, in the process 418, the website server 112 may create a corresponding target order including the product information, the designated delivery time, the attributes of the product, the delivery destination information, the expected delivery time, and the identification data of the first logistics company.

The aforementioned identification data of the first logistics company can be implemented in different ways.

In one embodiment, the first blockchain address registered in the blockchain subsystem 150 by the aforementioned logistics subsystem 120 can be used as the identification data of the first logistics company. In this case, the logistics subsystem 120 can send the first blockchain address to the website server 112 through the acceptance notice in the aforementioned process 416, and the website server 112 can use the first blockchain address in the process 418 The blockchain address is used as the identification data of the first logistics company.

In another embodiment, the e-commerce company can assign different codes to different logistics companies as identification data of different logistics companies. For example, an e-commerce company can assign a first code to the first logistics company as the identification data of the first logistics company. In this case, the logistics subsystem 120 can send the first code to the website server 112 through the acceptance notice in the aforementioned process 416, and the website server 112 can use the first code as the first code in the process 418. Identification data of the first logistics company.

After establishing one or more target orders, the e-commerce subsystem 110 may proceed to the process 502 in FIG. 5.

In the process 502, the website server 112 of the e-commerce subsystem 110 can transmit target order information corresponding to a target order content to a corresponding logistics subsystem.

For convenience of description, the following assumes that the target order referred to in the process 502 is a corresponding target order generated by the website server 112 after the logistics subsystem 120 accepts a specific delivery request generated by the website server 112. As mentioned above, the content of the target order may include the partial content of the corresponding initial order, the corresponding delivery destination information and expected delivery time, and the identification data of the first logistics company.

In this case, the website server 112 may include the content of the target order in the process 502 A target order information of is sent to the logistics subsystem 120.

In the process 504, the communication circuit 122 of the logistics subsystem 120 receives the target order information generated by the e-commerce subsystem 110, and the control circuit 124 can store the target order information in the database 126.

In the process 506, the website server 112 or the blockchain computing circuit 116 of the e-commerce subsystem 110 can identify an identification data of the target order (hereinafter referred to as target order identification data), a consignee account number, and the target order. The identification data of the logistics company in the order (hereinafter referred to as the qualified company identification data) and the delivery destination information in the target order are sent to the blockchain subsystem 150.

As mentioned above, the content of an initial order corresponding to the target order will contain the consignee data set by the purchaser, and the consignee data can be or can include the consignee’s name and consignee The alias of the consignee, the account name of the consignee, the telephone number of the consignee, the identity identification number of the consignee, and/or other information that can indicate the identity of the consignee.

If the initial order contains the consignee’s account name, the website server 112 or the blockchain computing circuit 116 can use the consignee’s account name in the initial order as the aforementioned consignee in the process 506 Person account.

If the initial order does not contain the consignee’s account name, the website server 112 can use the consignee’s name, consignee’s alias, consignee’s phone number, and consignee’s phone number recorded in the initial order. And/or other information that can indicate the identity of the consignee, find a corresponding consignee’s account name in the database 114, so that the website server 112 or the blockchain computing circuit 116 is in the process 506 , The account name of the consignee can be used as the aforementioned account of the consignee.

In addition, the website server 112 or the blockchain computing circuit 116 can also instruct the blockchain subsystem 150 in the process 506 to write the aforementioned data into a consignee smart contract corresponding to a consignee smart contract identification data.

As mentioned above, after the website server 112 establishes the aforementioned consignee’s account, it will request the blockchain subsystem 150 to establish a corresponding consignee’s smart contract, and the blockchain subsystem 150 The consignee smart contract identification data corresponding to the consignee smart contract will be sent to the website server 112.

Therefore, in the process 506, the website server 112 or the blockchain computing circuit 116 transmits a consignee smart contract identification data corresponding to the aforementioned consignee account to the blockchain subsystem 150 to instruct the blockchain sub-system The system 150 writes the aforementioned target order identification data, consignee account number, qualified operator identification data, and delivery destination information into a consignee smart contract corresponding to the consignee smart contract identification data.

In the process 508, the blockchain subsystem 150 can receive the target order identification data, the consignee account number, the qualified business identification data, and the delivery destination information from the e-commerce subsystem 110.

In the process 510, the blockchain subsystem 150 can store the target order identification data, consignee account number, qualified operator identification data, and delivery destination information in accordance with the instructions of the website server 112 or the blockchain computing circuit 116. An order event is formed in a consignee smart contract corresponding to the consignee smart contract identification data.

In the process 512, the blockchain subsystem 150 may transmit an order event identification data corresponding to the aforementioned order event to the e-commerce subsystem 110.

In the process 514, the website server 112 or the blockchain computing circuit 116 of the e-commerce subsystem 110 can receive the order event identification data from the blockchain subsystem 150, and the website server 112 can send the aforementioned order event The identification data is stored in the database 114.

In the process 516, the website server 112 of the e-commerce subsystem 110 may transmit the aforementioned order event identification data and consignee smart contract identification data to the corresponding logistics subsystem 120.

In the process 518, the communication circuit 122 of the logistics subsystem 120 can receive the aforementioned order event identification data and the consignee's smart contract identification data, and the control circuit 124 can store the aforementioned information in the database 126.

In the process 520, the control circuit 124 of the logistics subsystem 120 can combine the received order event identification data and the consignee's smart contract identification data with the aforementioned target order information. Establish associations.

During operation, the e-commerce subsystem 110, the blockchain subsystem 150, and the corresponding logistics subsystem can repeat the operation in Figure 5 for other target orders generated by the e-commerce subsystem 110 to make other target orders The relevant information can be stored in the corresponding logistics subsystem and the blockchain subsystem 150.

Please note that in the above process in Figure 5, the data sent by the e-commerce subsystem 110 to the relevant logistics subsystem includes target order information, order event identification data, and consignee smart contract identification data, but does not need to include data that can be used for identification Information about the identity of the consignee. This approach can ensure that the logistics subsystem 120 cannot obtain relevant information that can be used to identify the identity of the consignee at this stage. Privacy provides high protection.

The following describes how the logistics information management system 100 distributes the goods to the consignee in conjunction with FIGS. 6-11. 6 to 8 are simplified flowcharts of a route planning method for a target area according to an embodiment of the present invention. 9 to 11 are simplified flowcharts of a method for confirming the location of a consignee according to an embodiment of the present invention.

As mentioned above, in the traditional goods distribution mechanism, the logistics industry will plan a delivery route to the logistics agent based on the collected delivery address information in multiple orders. In addition, in order to avoid the situation where no one picks up the goods after the logistics staff arrive at the destination, the traditional goods distribution mechanism often requires the logistics staff to contact different consignees one by one in advance to confirm that the goods can be delivered to the designated location at the appropriate time. Especially when the delivered goods have special properties (for example, fresh food, or products that need to be refrigerated or frozen, etc.). Therefore, the traditional delivery mechanism of goods not only consumes additional communication costs, but is also time-consuming and inconvenient for logistics personnel.

In order to avoid the problems caused by the traditional goods delivery mechanism, the logistics information management system 100 will use different mechanisms to plan the delivery route used to guide the logistics staff. For the convenience of description, the following will take the operation mode of the logistics subsystem 120 planning the delivery route for the logistics agent of the first logistics company as an example to illustrate the operation process of FIG. 6 to FIG. 8.

As shown in FIG. 6, after the control circuit 124 of the logistics subsystem 120 collects a predetermined number of multiple target orders, the control circuit 124 may proceed to the process 602.

In the process 602, the control circuit 124 can execute a predetermined path planning algorithm to plan multiple initial delivery routes according to the expected delivery time and the delivery destination information of the collected multiple target orders. , So that each initial delivery route corresponds to one or more target areas, where each target area covers the delivery destinations in the collected multiple target orders.

As mentioned above, in the aforementioned process 406, the website server 112 will spatially de-identify the delivery location set by the purchaser to generate corresponding delivery destination information to represent the existence of the delivery location. A delivery destination of spatial relevance. Obviously, the geographical range covered by the delivery destination will be larger than the corresponding receiving location.

Compared with the traditional delivery mechanism that is based on multiple specific delivery address information to plan the delivery route, the aforementioned logistics subsystem 120 plans the delivery route based on the delivery destination information in multiple target orders. Effectively reduce the amount of calculation and calculation complexity required when planning a delivery route.

In the process 604, the control circuit 124 may transmit different initial delivery routes to the logistics device used by different logistics agents through the communication circuit 122. For the convenience of description, the following assumes that the control circuit 124 will transmit one of the multiple initial delivery routes to the logistics vehicle device 105 used by the first logistics vehicle through the communication circuit 122 in the process 604.

In this case, the logistics taxi device 105 will perform the process 606 to receive the initial delivery route from the logistics subsystem 120.

After the logistics agent 105 receives the corresponding initial delivery route, the first logistics agent can use appropriate transportation tools (for example, trucks, cars, locomotives, flying vehicles, ships, etc.) along the predetermined schedule. Follow the initial delivery route to deliver the goods.

In the process of the first logistics agent distributing the delivered products, the logistics agent device 105 may perform the process 608 and the process 610.

In the process 608, the logistics taxi device 105 can provide the initial The delivery route is for the first logistics staff to refer to or follow.

In the process 610, the logistics taxi device 105 can track the change of the geographic location of the logistics taxi device 105 itself. In operation, the logistics taxi device 105 can use various positioning mechanisms to detect the current location of the logistics taxi device 105 and track changes in the geographic location of the logistics taxi device 105.

The logistics taxi device 105 can compare the detected current location of the logistics taxi device 105 with the location or boundary of the individual target area in the initial delivery route. When the logistics agent 105 is close to a specific target area, that is, when the distance between the position of the logistics agent 105 and the target area is less than a predetermined distance, the logistics agent 105 can perform the process 612.

In the process 612, the logistics taxi device 105 may generate and transmit a target area route planning request corresponding to the specific target area to the logistics subsystem 120.

For example, the logistics taxi device 105 may integrate the center coordinates, geographic area information, and/or identification data of the target area into a target area route planning request in an appropriate data format in the process 612, and combine the The route planning request for the target area is transmitted to the logistics subsystem 120.

In this case, the communication circuit 122 of the logistics subsystem 120 can perform the process 614 to receive the route planning request of the target area from the logistics taxi device 105. Then, the control circuit 124 may obtain or convert the data of the corresponding target area from the content of the received target area route planning request.

In the process 616, the control circuit 124 can find out the multiple order event identification data of the corresponding delivery destination in the target area.

As mentioned above, the control circuit 124 stores the target order information from the e-commerce subsystem 110 in the database 126, and also associates the order event identification data from the e-commerce subsystem 110 with the target order information. . Therefore, the control circuit 124 can compare the delivery destinations in the individual target order information stored in the database 126 with the target area in the process 616 to find out how many corresponding delivery destinations are in the target area. Target order information. Then, the control circuit 124 can, based on the multiple target order information, Find out a plurality of corresponding order event identification data from the database 126.

Next, the control circuit 124 of the logistics subsystem 120 will perform the process 702 in FIG. 7 to generate multiple receipt requests corresponding to the aforementioned multiple order event identification data, so that each receipt request includes a corresponding Order event identification data and identification data of the first logistics company.

For example, in the process 702, the control circuit 124 may integrate the identification data of the first logistics company and a first order event identification data among the aforementioned multiple order event identification data into a first receiving request in an appropriate data format. The control circuit 124 can integrate the identification data of the first logistics company and a second order event identification data among the aforementioned plurality of order event identification data into a second receiving request in an appropriate data format. The rest can be deduced by analogy.

As mentioned above, the control circuit 124 of the logistics subsystem 120 associates the order event identification data, the consignee's smart contract identification data, and the target order information from the e-commerce subsystem 110. Therefore, the control circuit 124 can find the corresponding multiple consignee smart contract identification data from the database 126 according to the aforementioned multiple order event identification data.

In practice, the control circuit 124 can access the blockchain subsystem 150 through the communication circuit 122 or the blockchain operation circuit 128, so as to read the identification data and data of the multiple consignee smart contracts in the blockchain subsystem 150. Contents of multiple order events corresponding to one order event identification data to obtain multiple consignee accounts recorded in the multiple order events.

Then, the control circuit 124 can perform the process 704 to transmit different receipt requests to different recipient devices through the communication circuit 122.

In one embodiment, the control circuit 124 may directly transmit the aforementioned multiple receipt requests to multiple consignee devices corresponding to the aforementioned multiple consignee accounts through the communication circuit 122.

In another embodiment, the control circuit 124 can send the aforementioned multiple receipt requests and multiple consignee accounts to the website server 112 of the e-commerce subsystem 110 through the communication circuit 122, and request the website server 112 to The multiple receipt requests are respectively transmitted to multiple consignee devices corresponding to the aforementioned multiple consignee accounts.

During operation, the control circuit 124 transmits the number of receipt requests to individual consignee devices through the communication circuit 122. There may be only one or multiple receipt requests.

For the convenience of description, the following assumes that the control circuit 124 will directly or indirectly transmit one of the multiple receipt requests to the consignee device 103 used by the first consignee through the communication circuit 122 in the process 704 .

In this case, the processing circuit 162 of the consignee device 103 can perform the process 706 to receive the receipt request from the logistics subsystem 120.

In the process 708, the receiving request processing module 220 of the consignee privacy protection program 166 can control the processing circuit 162 to obtain a corresponding order event identification data and a current operator identification data from the receiving request. Under normal circumstances (for example, when the receiving request has not been tampered with or forged by a malicious person), the current operator identification data obtained by the processing circuit 162 should be the identification data of the first logistics company. For the convenience of the following description, the current operator identification data obtained by the processing circuit 162 in the process 708 is referred to as the first current operator identification data in the following.

In the process 710, the processing circuit 162 may generate and transmit a delivery destination information request including the aforementioned order event identification data and the first current operator identification data to the blockchain subsystem 150.

For example, the receiving request processing module 220 can control the processing circuit 162 in the process 710 to log in to the website server 112 of the e-commerce subsystem 110 with the first consignee account, and send the aforementioned delivery destination information request to the website server器112. The website server 112 or the blockchain computing circuit 116 uses the e-commerce subsystem personal account corresponding to the e-commerce subsystem 110 to log in to the blockchain subsystem 150 to send the delivery destination information request to the blockchain subsystem 150 . In other words, the consignee device 103 can indirectly transmit the aforementioned delivery destination information request to the blockchain subsystem 150 through the e-commerce subsystem 110. That is, the e-commerce subsystem 110 can be used as a medium for the consignee device 103 to access the blockchain subsystem 150.

In the process 712, the blockchain subsystem 150 receives the delivery destination information request from the consignee device 103, and obtains an order event identification from the delivery destination information request. Individual data and a first current business identification data.

In the process 714, the blockchain subsystem 150 will find a corresponding order event according to the order event identification data, and read the content of the order event.

In the process 716, the blockchain subsystem 150 compares the first current vendor identification data with the qualified vendor identification data recorded in the order event to determine whether the first current vendor identification data matches the qualified vendor identification data. If the first current vendor identification data does not match the qualified vendor identification data, the blockchain subsystem 150 will proceed to the process 718. Conversely, if the first current vendor identification data matches the qualified vendor identification data, the blockchain subsystem 150 will proceed to the process 722.

In the process 718, the blockchain subsystem 150 will send a rejection notice to the consignee device 103. At this time, the consignee device 103 will perform the process 720 to receive the rejection notice from the blockchain subsystem 150.

In practice, the blockchain subsystem 150 can send the rejection notice to the website server 112 or the blockchain computing circuit 116 of the e-commerce subsystem 110 in the process 718, and then the e-commerce subsystem 110 sends the rejection notice to the The consignee device corresponding to the first consignee account number (the consignee device 103 in this embodiment).

In the process 722, the blockchain subsystem 150 sends a delivery destination information recorded in the order event to the consignee device 103. At this time, the consignee device 103 will perform the process 724 to receive the delivery destination information from the blockchain subsystem 150.

In practice, the blockchain subsystem 150 can send the delivery destination information to the website server 112 or the blockchain computing circuit 116 of the e-commerce subsystem 110 in the process 722, and then the website server 112 can send the delivery destination information It is transmitted to the consignee device 103 corresponding to the first consignee account number.

As shown in FIG. 8, after the consignee device 103 receives the aforementioned delivery destination information, the consignee request processing module 220 of the consignee privacy protection program 166 controls the processing circuit 162 to perform the process 802.

In the process 802, the processing circuit 162 will determine whether the current position of the consignee device 103 is Located in a delivery destination corresponding to the aforementioned delivery destination information. During operation, the processing circuit 162 can use various positioning mechanisms to detect the current location of the consignee device 103. For the convenience of the following description, the current position of the consignee device 103 when the processing circuit 162 performs the process 802 is referred to as the first current position in the following.

If the processing circuit 162 determines that the first current location is within the delivery destination, the receiving request processing module 220 of the consignee privacy protection program 166 will proceed to the process 804. Conversely, if the processing circuit 162 determines that the first current location is not within the delivery destination, the receiving request processing module 220 will proceed to the process 810.

In the process 804, the receiving request processing module 220 will control the processing circuit 162 to generate an inquiry message, and provide the inquiry message in the form of audio and/or video to inquire whether the first consignee is willing to receive the goods. .

In practice, the processing circuit 162 can inform the first consignee of information related to the goods to be received in the query message, for example, the name of the goods, the information of the purchaser, the information of the consignee, the name of the e-commerce company, and/or The name of the logistics company, etc. The aforementioned information related to the goods to be received may be obtained by the consignee device 103 inquiring from the e-commerce subsystem 110, the logistics subsystem 120, and/or the blockchain subsystem 150, or it may be obtained from the e-commerce subsystem 110, the logistics subsystem 120, and/or the blockchain subsystem 150 are provided to the consignee device 103 in the previous stage.

If the first consignee uses various suitable methods (for example, sliding a specific image, clicking a specific image, inputting text or instructions, issuing a specific spoken command, shaking the consignee device 103, etc.) to the consignee The device 103 issues an instruction that it is willing to accept the goods, and the goods-receiving request processing module 220 will proceed to the process 806. Conversely, if the first consignee issues an instruction to the consignee device 103 that it is unwilling to receive the goods, the receiving request processing module 220 will proceed to the process 810.

In the process 806, the receiving request processing module 220 controls the processing circuit 162 to generate and transmit an available-to-receive notice to the logistics subsystem 120. Please note that in order to avoid leaking the information of the current location of the first consignee, the aforementioned processing circuit The receivable notification generated by 162 does not include information about the current location of the consignee device 103 (that is, the aforementioned first current location).

In the process 808, the communication circuit 122 of the logistics subsystem 120 receives the receivable notification from the consignee device 103.

In the process 810, the receiving request processing module 220 controls the processing circuit 162 to generate and transmit an unavailable-to-receive notice to the logistics subsystem 120.

In the process 812, the communication circuit 122 of the logistics subsystem 120 receives the unacceptable notification from the consignee device 103.

As mentioned above, the logistics subsystem 120 will transmit multiple different receiving requests corresponding to the aforementioned target area to different consignee devices. After each consignee device receives the corresponding receiving request, it can use the method of the aforementioned process 706 to process 810 to use the blockchain subsystem 150 to verify whether the identification data of the relevant logistics company is correct, and to determine whether the consignee’s device is correct. Whether the current location is in the corresponding delivery destination, and determine whether the relevant consignee is willing to receive the goods, and then generate and transmit the relevant notice of receivable or unacceptable goods to the corresponding logistics subsystem.

For the convenience of description, it is assumed that the logistics subsystem 120 successively receives multiple receivable notifications from multiple different consignee devices located in the target area through the aforementioned method. In this case, the control circuit 124 of the logistics subsystem 120 can perform the process 814.

In the process 814, the control circuit 124 of the logistics subsystem 120 can plan a target region delivery route corresponding to the target region according to the multiple delivery destinations corresponding to the received multiple receivable notifications. path). In practice, the control circuit 124 can execute various appropriate route planning algorithms to plan a delivery route in a target area that will pass through or include the multiple delivery destinations.

In the process 816, the control circuit 124 may transmit the delivery route of the target area to the corresponding logistics taxi device 105 through the communication circuit 122.

In this case, the logistics taxi device 105 will perform the process 818 to receive the logistics subsystem 120 The delivery route in the target area, and the delivery route in the target area is provided in the form of voice and/or video for the first logistics person to refer to or follow.

Next, the first logistics agent can control the transportation means to carry out the goods distribution operation along the aforementioned delivery route in the target area.

It can be seen from the foregoing description that the logistics subsystem 120 does not need to obtain specific individual delivery addresses and detailed consignee information in advance. It only needs to plan the corresponding target area delivery routes based on the aforementioned multiple delivery destinations. . Such a delivery route planning method can effectively prevent the logistics personnel from leaking the information and delivery addresses of individual consignees, so it can provide better protection for the privacy of the consignees.

In addition, the logistics subsystem 120 plans the delivery route in the target area based on multiple delivery destinations, instead of planning the delivery route in the target area based on multiple specific addresses, so it can reduce the amount of calculation and calculation required when planning the delivery route. Operational complexity.

Furthermore, the first logistics staff does not need to contact different consignees one by one in advance, and can automatically inquire whether they are located in the target area through the coordination operation of the aforementioned logistics subsystem 120, the blockchain subsystem 150, and multiple consignee devices. Of multiple different consignees are willing to receive the goods. Moreover, if the current location of a consignee device is not actually located in the corresponding delivery destination, the consignee device can automatically send the unacceptable notification to the logistics subsystem 120, so as to avoid the situation not in the delivery destination at that time. The consignee deliberately lied about being able to receive the goods, thus causing the possibility of the first logistics staff to make a trip in vain. Such an approach can effectively save a lot of work time of the first logistics personnel, reduce the possibility of the first logistics personnel being deceived, and thereby greatly improve the efficiency of goods distribution.

On the other hand, in the aforementioned process 802, the consignee device 103 compares the current location of the consignee device 103 with a delivery destination with a larger geographic coverage, rather than a specific receiving location. . Therefore, before the logistician has arrived at the location of the first consignee, as long as the consignee device 103 determines that the current location of the consignee device 103 is within the delivery destination and the first consignee is willing to receive the goods, The cargo person device 103 can send a receivable notification to the logistics subsystem 120.

In other words, before the logistician has arrived at the location of the first consignee, the route planning method for the target area proposed in Figures 6 to 8 does not require the first consignee to stay at the actual receiving location. . Therefore, before the logistics staff arrives at the actual receiving location, the aforementioned target area route planning method allows the first consignee to walk or move around the receiving location, so that the first consignee enjoys a better period during this period. Large range of motion and flexibility of movement.

Moreover, the consignee device 103 does not need to report the current location of the first consignee or the real-time location data of the consignee device 103 to the logistics subsystem 120 in the aforementioned operation process, so it can effectively avoid The location of the first consignee may be leaked due to human negligence or technical problems.

During operation, the other logistics subsystems in the logistics information management system 100 (for example, the logistics subsystem 130) can be compared to the operation mode of the logistics subsystem 120 in the aforementioned Figures 6 to 8, and are the logistics of the relevant logistics industry. Planning the required delivery route.

The following will further illustrate the operation mode of the logistics information management system 100 in the process of delivering goods along the aforementioned target area delivery route by the logistics agent in conjunction with FIG. 9 to FIG. 11. 9 to 11 are simplified flowcharts of a method for confirming the location of a consignee according to an embodiment of the present invention.

For the convenience of description, the following will take the aforementioned operation method of the first logistics agent distributing goods along the delivery route in the target area as an example to illustrate the operation process of the logistics information management system 100 at this stage.

As shown in FIG. 9, when the first logistics agent controls the means of transportation to deliver goods along the aforementioned delivery route in the target area, the logistics agent device 105 will perform the process 902 in FIG. 9 to detect and track the logistics agent. The geographic location of the device 105 changes. In operation, the logistics taxi device 105 can use various positioning mechanisms to detect the current location of the logistics taxi device 105 and track changes in the geographic location of the logistics taxi device 105.

As mentioned earlier, there will be multiple delivery destinations on the delivery route in the target area, and individual delivery destinations will be spatially related to individual receiving locations set by different purchasers.

Under normal circumstances, the first logistics staff will follow a predetermined order to the destination area delivery route Different delivery destinations online, and deliver related goods to one or more consignees located in each delivery destination.

In the aforementioned process 902, the logistics taxi device 105 can compare the detected current location of the logistics taxi device 105 with the individual delivery destinations in the delivery route of the target area. When the logistics agent 105 is close to a specific delivery destination, that is, when the distance between the position of the logistics agent 105 and the delivery destination is less than a predetermined distance, the logistics agent 105 may perform the process 904.

In the process 904, the logistics taxi device 105 can generate and transmit a position information inquiry corresponding to the delivery destination to the corresponding logistics subsystem 120. For example, the logistics taxi device 105 can integrate the center coordinates, geographic area information, and/or identification data of the delivery destination into a corresponding location information query in an appropriate data format in the process 904, and The location information query is sent to the logistics subsystem 120.

At this time, the communication circuit 122 of the logistics subsystem 120 can perform the process 906 to receive the location information query from the logistics taxi device 105. The control circuit 124 can obtain a corresponding delivery destination data from the received location information query content, or convert the location information query content into corresponding delivery destination data. Then, the control circuit 124 can query the database 126 for a specific target order information corresponding to the delivery destination data. For the convenience of description, it is assumed below that the aforementioned specific target order information indicates that the first logistics company wants to deliver a target product to the aforementioned first consignee.

Then, the control circuit 124 can perform the process 908 to generate a position information request including a specific order event identification data corresponding to the aforementioned specific target order information and the identification data of the first logistics company, and send the The location information request is sent to a corresponding consignee device.

As mentioned above, the control circuit 124 of the logistics subsystem 120 associates the order event identification data, the consignee's smart contract identification data, and the target order information from the e-commerce subsystem 110. Therefore, the control circuit 124 can perform according to the specific target order in the process 908 Information, find a corresponding order event identification data from the database 126 as the specific order event identification data, and find a consignee smart contract identification data corresponding to the first consignee.

In practice, the control circuit 124 can access the blockchain subsystem 150 through the communication circuit 122 or the blockchain operation circuit 128 to read the identification data of the consignee’s smart contract and the order event identification in the blockchain subsystem 150. The content of an order event corresponding to the data is used to obtain the consignee account number recorded in the order event.

In the aforementioned process 908, the control circuit 124 can directly send the positioning information request through the communication circuit 122 to a consignee device corresponding to the aforementioned consignee account number (in this example, the first consignee’s office). Consignee device used 103).

Alternatively, the control circuit 124 may send the location information request and the consignee account number to the website server 112 of the e-commerce subsystem 110 through the communication circuit 122 in the aforementioned process 908, and request the website server 112 to locate the location information. The information request is sent to a consignee device corresponding to the consignee account number (in this example, the consignee device 103 used by the first consignee).

In other words, the control circuit 124 can directly or indirectly transmit the location information request to the consignee device 103 used by the first consignee through the communication circuit 122 in the process 908.

In this case, the processing circuit 162 of the consignee device 103 can perform the process 910 to receive the positioning information request from the logistics subsystem 120.

In the process 912, the location information request processing module 230 of the consignee privacy protection program 166 can control the processing circuit 162 to obtain a corresponding order event identification data and a current operator identification data from the location information request. Under normal circumstances (for example, when the location information request has not been tampered with or forged by a malicious person), the current operator identification data obtained by the processing circuit 162 should be the identification data of the first logistics company. For the convenience of the following description, the current operator identification data obtained by the processing circuit 162 in the process 912 is referred to as the second current operator identification data in the following.

In the process 914, the processing circuit 162 may generate and transmit the identification information containing the aforementioned order event A logistics vendor identity authentication request (logistics vendor identity authentication request) of the second current vendor identification data is sent to the blockchain subsystem 150.

For example, the location information request processing module 230 can control the processing circuit 162 in the process 914 to log in to the website server 112 of the e-commerce subsystem 110 with the first consignee account, and send the aforementioned logistics provider identity verification request to the website server器112. The website server 112 or the blockchain computing circuit 116 uses the e-commerce subsystem personal account corresponding to the e-commerce subsystem 110 to log in to the blockchain subsystem 150 to send the logistic company identity verification request to the blockchain subsystem 150 . In other words, the consignee device 103 can indirectly transmit the aforementioned logistic company identity verification request to the blockchain subsystem 150 through the e-commerce subsystem 110. That is, the e-commerce subsystem 110 can be used as a medium for the consignee device 103 to access the blockchain subsystem 150.

In the process 916, the blockchain subsystem 150 receives the logistics provider identity verification request from the consignee device 103, and obtains an order event identification data and a second current provider identification data from the logistics provider identity verification request.

Next, the blockchain subsystem 150 will perform the process 1002 in FIG. 10 to find a corresponding order event based on the order event identification data, and read the content of the order event.

In the process 1004, the blockchain subsystem 150 compares the second current vendor identification data with the qualified vendor identification data recorded in the order event to determine whether the second current vendor identification data matches the qualified vendor identification data. If the second current operator identification data does not match the qualified operator identification data, the blockchain subsystem 150 will proceed to the process 1006. Conversely, if the second current operator identification data matches the qualified operator identification data, the blockchain subsystem 150 will proceed to the process 1012.

In the process 1006, the blockchain subsystem 150 will generate and send an identity authentication failure notice to the consignee device 103. At this time, the positioning information request processing module 230 controls the processing circuit 162 to perform the process 1008 to receive the identity verification failure notification from the blockchain subsystem 150.

In practice, the blockchain subsystem 150 can send the identity verification failure communication in the process 1006. It is notified to the website server 112 or the blockchain computing circuit 116 of the e-commerce subsystem 110, and the e-commerce subsystem 110 transmits the identity verification failure notification to the consignee device corresponding to the first consignee account number (in this In the embodiment, it is the consignee device 103).

In the process 1010, the positioning information request processing module 230 controls the processing circuit 162 to generate and send a rejection notice to the logistics subsystem 120 to reject the location information request from the logistics subsystem 120.

In the process 1012, the blockchain subsystem 150 will generate and send an identity authentication successful notice to the consignee device 103.

In this case, the positioning information request processing module 230 can control the processing circuit 162 to perform the process 1014 to receive the identity verification success notification from the blockchain subsystem 150.

In practice, the blockchain subsystem 150 can send a notification of the successful identity verification to the website server 112 of the e-commerce subsystem 110 or the blockchain computing circuit 116 in the process 1012, and the e-commerce subsystem 110 will then verify the identity successfully. The notification is transmitted to the consignee device 103 corresponding to the first consignee account number.

In the process 1016, the encryption module 240 of the consignee privacy protection program 166 controls the processing circuit 162 to encrypt the current location of the consignee device 103 with a ciphertext key to generate a consignee location ciphertext.

During operation, the processing circuit 162 can use various positioning mechanisms to detect the current location of the consignee device 103. For the convenience of the following description, the current position of the consignee device 103 when the processing circuit 162 performs the process 1016 is referred to as the second current position below. The processing circuit 162 can use the ciphertext key to execute various suitable encryption algorithms on the aforementioned second current location in the process 1016 to generate the aforementioned consignee location ciphertext.

Next, the encryption module 240 controls the processing circuit 162 to perform the process 1102 in FIG. 11.

In the process 1102, the encryption module 240 controls the processing circuit 162 to send the ciphertext key to the logistics subsystem 120 in response to the location information request from the logistics subsystem 120 in the process 908.

In this case, the communication circuit 122 of the logistics subsystem 120 can perform the process 1104 to connect The ciphertext key sent from the consignee device 103. The control circuit 124 can establish a correlation between the ciphertext key, the specific order event identification data corresponding to the positioning information request, and the consignee smart contract identification data corresponding to the specific order event identification data.

In the process 1106, the control circuit 124 of the logistics subsystem 120 can generate a recipient position information request (recipient position information request) corresponding to the received ciphertext key, and pass the recipient position information request through The communication circuit 122 or the blockchain operation circuit 128 transmits to the blockchain subsystem 150. In practice, the control circuit 124 can generate a consignee location information request containing the aforementioned specific order event identification data and the corresponding consignee smart contract identification data, and send the consignee location information request to the blockchain System 150. For example, in this embodiment, the aforementioned consignee smart contract identification data is the consignee smart contract identification data corresponding to the first consignee, and the aforementioned specific order event identification data is related to the aforementioned specific target The identification data of an order event corresponding to the order information.

In the process 1108, the blockchain subsystem 150 may receive and record the location information request of the consignee from the logistics subsystem 120. In operation, the blockchain subsystem 150 can retrieve the specific order event identification data and the corresponding consignee smart contract identification data from the consignee location information request, and record the consignee location information request in the The consignee's smart contract identification data and the specific order event identification data correspond to an order event.

In the process 1110, the blockchain subsystem 150 can generate an encrypted position information request corresponding to the receiver's location information request, and send the encrypted position information request to the specific order event identification data office. A corresponding consignee device (in this example, the consignee device 103 used by the first consignee). At this time, the consignee device 103 will perform the process 1112 to receive the location ciphertext request from the blockchain subsystem 150.

In practice, the blockchain subsystem 150 can send the location ciphertext request to the website server 112 or the blockchain computing circuit 116 of the e-commerce subsystem 110 in the process 1110, and then the website The server 112 transmits the location ciphertext request to the consignee device 103.

In the process 1114, the encryption module 240 of the consignee privacy protection program 166 controls the processing circuit 162 to transmit the ciphertext of the consignee's location generated in the process 1016 to the blockchain subsystem 150.

For example, the encryption module 240 can control the processing circuit 162 in the process 1114 to log in to the website server 112 of the e-commerce subsystem 110 with the first consignee account, and send the ciphertext of the consignee location to the website server 112. Then, the website server 112 or the blockchain computing circuit 116 uses the e-commerce subsystem personal account corresponding to the e-commerce subsystem 110 to log in to the blockchain subsystem 150 to send the ciphertext of the consignee's location to the block Chain subsystem 150. In other words, the consignee device 103 can indirectly transmit the ciphertext of the consignee's location to the blockchain subsystem 150 through the e-commerce subsystem 110.

In the process 1116, the blockchain subsystem 150 will receive and record the ciphertext of the consignee location sent from the consignee device 103 in the corresponding order event in the consignee smart contract corresponding to the first consignee account number (That is, the order event corresponding to the aforementioned specific order event identification data).

In the process 1118, the blockchain subsystem 150 will generate and send a position information available notice to the logistics subsystem 120 in response to the aforementioned consignee from the logistics subsystem 120 in the process 1106 Location request.

At this time, the communication circuit 122 of the logistics subsystem 120 will perform the process 1120 to receive the location information readable notification from the blockchain subsystem 150.

Then, the control circuit 124 of the logistics subsystem 120 can perform the process 1122 to access the blockchain subsystem 150 through the communication circuit 122 or the blockchain operation circuit 128, and read the consignee in the blockchain subsystem 150 and the aforementioned consignee. The smart contract identification data and the content of an order event corresponding to the specific order event identification data are used to obtain the ciphertext of the location of the consignee recorded in the order event.

In the process 1124, the control circuit 124 can use the received ciphertext key to decrypt the ciphertext of the consignee’s location read from the blockchain subsystem 150 to obtain the first consignee’s current Front position.

If the ciphertext key sent by the consignee device 103 to the logistics subsystem 120, the specific order event identification data used by the logistics subsystem 120, the consignee smart contract identification data used by the logistics subsystem 120, and from the blockchain subsystem If any one or more of the information in the ciphertext of the consignee's location read in 150 is incorrect, the control circuit 124 cannot use the ciphertext key to decrypt the ciphertext of the consignee's location, and therefore cannot obtain the first ciphertext. The current location of the consignee.

Conversely, if the ciphertext key sent by the consignee device 103 to the logistics subsystem 120, the specific order event identification data used by the logistics subsystem 120, the consignee smart contract identification data used by the logistics subsystem 120, and the slave block The ciphertext of the consignee's location read by the chain subsystem 150 is correct, and the control circuit 124 can use the ciphertext key to successfully decrypt the ciphertext of the consignee's location in the process 1124 to obtain the first consignee. The current position of the person (that is, the aforementioned second current position).

In this case, the control circuit 124 of the logistics subsystem 120 can perform the process 1126 to transmit the current location information of the first consignee to the corresponding logistics agent 105 through the communication circuit 122 to instruct the corresponding first logistics agent to perform deliver goods.

By using the current location information of the first consignee sent by the logistics subsystem 120 to the logistics agent device 105, the first logistics agent can know the current location of the first consignee. In this way, the first logistics personnel can deliver the related goods to the first consignee.

In practical applications, the logistics subsystem 120 can interact with other consignee devices in the target area in accordance with the aforementioned operation modes in Figures 9 to 11 to obtain and provide other consignee’s current location information to the logistics agent. 105, so that the first logistics agent can know the current location of other consignees.

It can be seen from the foregoing description that the first logistics agent can automatically obtain the first consignee through the corresponding logistics subsystem 120 without contacting the first consignee during the process of delivering the goods to the first consignee. The current position of (that is, the aforementioned second current position). This approach can save the first logistics staff's work time and improve the efficiency of their goods distribution.

In addition, the consignee device 103 can use the blockchain subsystem 150 to verify whether the identity of the logistics company corresponding to the aforementioned location information request is correct, so it can effectively avoid misrepresenting the current location of the first consignee to the wrong logistics worker. .

Furthermore, the consignee device 103 transmits the ciphertext key to the logistics subsystem 120, but does not directly transmit the ciphertext of the consignee's location to the logistics subsystem 120, but transmits the ciphertext of the consignee's location to the logistics subsystem 120 The blockchain subsystem 150 performs storage. Only the ciphertext key sent by the consignee device 103 to the logistics subsystem 120, the specific order event identification data used by the logistics subsystem 120, the consignee smart contract identification data used by the logistics subsystem 120, and the data from the blockchain Only when the ciphertext of the consignee's location read in the system 150 is correct, the logistics subsystem 120 can use the received ciphertext key to smoothly decrypt the ciphertext of the consignee's location to obtain and transmit the first receipt. The current location of the cargo person is given to the logistics taxi device 105. This approach can effectively reduce the possibility of the current location of the first consignee being stolen by malicious persons and leaking, and the blockchain subsystem 150 will also save all actions to access the ciphertext of the consignee’s location, so it can ensure the receipt The privacy of the cargo's real-time location information is more closely protected.

It can be seen from the foregoing that if a specific consignee doubts that its receiving location is leaked in the future, the operator of the e-commerce subsystem 110 can use the e-commerce subsystem personal account to log in to the blockchain subsystem 150 to query the blockchain. The access records of all order events in the consignee smart contract corresponding to the consignee are stored in the system 150. During operation, the blockchain subsystem 150 will record all the ciphertexts of the consignee location corresponding to the consignee in individual order events, and also fully record all access to the ciphertext of these consignee locations action. Based on the technical characteristics of the blockchain subsystem 150, it is difficult for the aforementioned access records stored in the blockchain subsystem 150 to be tampered with by interested persons. Therefore, operators of the e-commerce subsystem 110 and/or other logistics companies can The records in the chain subsystem 150 are used to trace all the objects that have accessed the ciphertext of the consignee’s location corresponding to the consignee and the access time, so as to determine whether the consignee’s receiving location is really leaked , And/or investigate the identity of the possible leaker.

Please note that the execution sequence of the processes in the foregoing flowcharts is only an exemplary embodiment, and does not limit the actual implementation of the present invention. For example, the process 312 in FIG. 3 can be adjusted to be performed before the process 302, or performed at the same time. For another example, the process 322 in FIG. 3 may be adjusted to be performed before the process 312, or performed at the same time. For another example, the process 332 in FIG. 3 can be adjusted to be performed before the process 328, or performed at the same time. For another example, the process 406 in FIG. 4 may be adjusted to be performed before the process 404, or performed at the same time. For another example, the process 506 in FIG. 5 can be adjusted to be performed before the process 502, or performed at the same time. For another example, the process 804 in FIG. 8 can be adjusted to be performed before the process 802, or performed at the same time. For another example, the process 1016 in FIG. 10 may be adjusted to be performed after the process 1102 in FIG. 11, or adjusted to be performed between the processes 1112 and 1114 in FIG. 11.

In addition, as mentioned above, the consignee device 103 can indirectly transmit the aforementioned delivery destination information request and logistics provider identity verification request to the blockchain subsystem 150 through the e-commerce subsystem 110. In this case, the process 342 and the process 344 in FIG. 3 can be omitted.

In some embodiments, individual consignees can use their consignee devices to register with the blockchain subsystem 150 to obtain direct access to the blockchain subsystem 150. For example, the first consignee may use the consignee device 103 to register with the blockchain subsystem 150 in advance. In this way, in the aforementioned processes 710, 720, 724, 914, 1008, 1014, and/or 1114, the consignee device 103 can access the blockchain subsystem 150 without using the e-commerce subsystem 110 As a medium.

In some embodiments, the e-commerce subsystem 110 may temporarily provide its e-commerce subsystem personal account number to the consignee device during a specific period of time, so that the consignee device can use the e-commerce sub-system of the e-commerce subsystem 110 The system personal account directly accesses the blockchain subsystem 150. For example, the e-commerce subsystem 110 may provide its personal account of the e-commerce subsystem to the consignee device 103. In this way, in the aforementioned processes 710, 720, 724, 914, 1008, 1014, and/or 1114, the consignee device 103 can use the e-commerce subsystem personal account of the e-commerce subsystem 110 to log in to the block The chain subsystem 150 can directly access the blockchain subsystem 150.

In some embodiments, the e-commerce subsystem 110 can further configure the blockchain subsystem The status of the order event recorded by the consignee smart contract in 150 is active (active) and inactive (inactive), so that the blockchain subsystem 150 can determine whether to respond to the request for the order event according to the status of the order event .

For example, in the process of FIG. 7 described above, if the status of an order event is active, the blockchain subsystem 150 can respond to a rejection notification or delivery destination information for a request from the consignee device for the order event. Conversely, if the status of the order event is inactive, the blockchain subsystem 150 may not respond to any message after receiving a request from the consignee device for the order event.

For another example, in the aforementioned flow of FIG. 10, if the status of the order event is active, the blockchain subsystem 150 can respond to the request of the consignee device for the order event in response to the notification of successful identity verification or the notification of identity verification failure. Conversely, if the status of the order event is inactive, the blockchain subsystem 150 may not respond to any message after receiving a request from the consignee device for the order event.

For another example, in the aforementioned process of FIG. 11, if the status of the order event is active, the blockchain subsystem 150 can respond to the request for location information of the consignee from the logistics subsystem. Conversely, if the status of the order event is inactive, the blockchain subsystem 150 may not respond to any message after receiving the receiver's location information request from the logistics subsystem.

Therefore, the e-commerce subsystem 110 may be designed to set the status of the corresponding order event as active during the delivery of goods by the logistics company, and set the status of the corresponding order event as inactive after the delivery of the goods is completed. In this way, it can be avoided that the blockchain subsystem 150 transmits the ciphertext of the location of the consignee to any logistics subsystem during a time period other than the delivery of the goods, which may cause the privacy of the consignee's location to be leaked.

In some embodiments, the receiving request processing module 220 may be configured to directly determine the first current when the blockchain subsystem 150 does not respond to the delivery destination information request generated by the receiver device 103 within a predetermined time. The identification data of the industry cannot pass the identity verification of the blockchain subsystem 150. In this case, the processes 718 and 720 in FIG. 7 can be omitted.

In some embodiments, the receiving request processing module 220 can be configured in the flow of FIG. 8 described above. It is assumed that the consignee is willing to accept the goods. In this case, the process 804 can be omitted.

In some embodiments, the processes 722 and 724 in FIG. 7 and the process 802 in FIG. 8 may be omitted. In this case, the blockchain subsystem 150 can directly send a confirmation notification to the consignee device 103 when it determines that the first current vendor identification data matches the qualified vendor identification data in the aforementioned process 716 of FIG. 7. After receiving the confirmation notification, the consignee device 103 can directly proceed to the process 804 in FIG. 8.

In other embodiments, the processes 722 and 724 in FIG. 7 and the processes 802 and 804 in FIG. 8 may be omitted. In this case, the blockchain subsystem 150 can directly send a confirmation notification to the consignee device 103 when it determines that the first current vendor identification data matches the qualified vendor identification data in the aforementioned process 716 of FIG. 7. After receiving the confirmation notification, the consignee device 103 can directly proceed to the process 806 in FIG. 8.

In another embodiment, the logistics subsystem 120 can be set to directly determine the first item corresponding to the consignee device 103 when the consignee device 103 does not respond to the receipt request from the logistics subsystem 120 within a predetermined time. One consignee is unable to receive the goods. In this case, the procedures 810 and 812 can be omitted.

In some embodiments, the positioning information request processing module 230 can be configured to directly determine the second current when the blockchain subsystem 150 does not respond to the logistics provider identity verification request generated by the consignee device 103 within a predetermined time. The identification data of the industry cannot pass the verification of the blockchain subsystem 150. In this case, the processes 1006 and 1008 in FIG. 10 can be omitted. In addition, the process 1010 can be further omitted.

In the specification and the scope of the patent application, certain words are used to refer to specific elements, and those skilled in the art may use different terms to refer to the same elements. This specification and the scope of the patent application do not use the difference in names as a way of distinguishing elements, but the difference in function of the elements as the basis for distinguishing. The "include" mentioned in the specification and the scope of the patent application is an open term and should be interpreted as "include but not limited to". In addition, the term "coupling" here includes any direct and indirect connection means. Therefore, if the text describes that the first element is coupled to the second element, it means that the first element can communicate with each other. It is directly connected to the second element through electrical connection, wireless transmission, optical transmission, or other signal connection methods, or indirectly electrically or signally connected to the second element through other elements or connection means.

The description method of "and/or" used in the description includes one of the listed items or any combination of multiple items. In addition, unless otherwise specified in the specification, any term in the singular case includes the meaning of the plural case at the same time.

The above are only preferred embodiments of the present invention, and all equivalent changes and modifications made in accordance with the claims of the present invention should fall within the scope of the present invention.

100: Logistics Information Management System

101, 102: Purchaser's device

103, 104: Consignee device

105, 106: Logistician device

110: E-commerce subsystem

112: Web server

114: database

116: Blockchain operation circuit

120, 130: logistics subsystem

122, 132: communication circuit

124, 134: control circuit

126, 136: Database

128, 138: Blockchain operation circuit

140: Blockchain node cluster

141~147: Blockchain nodes

150: Blockchain Subsystem

162: Processing Circuit

164: storage circuit

166: Consignee privacy protection program

Claims (11)

A logistics information management system (100), comprising: a blockchain subsystem (150), including multiple blockchain nodes (141~147); a logistics subsystem (120), which can be set up to be a logistics device ( 105) When approaching a target area, generate a receiving request including a first current operator identification data and an order event identification data; and a consignee device (103) configured to receive the receiving request, And according to the receiving request, a delivery destination information request including the order event identification data and the first current operator identification data is generated; wherein, the blockchain subsystem (150) is configured to receive the delivery destination information request , And based on the order event identification data, find out an order event recorded in a consignee smart contract stored in the blockchain subsystem (150), and read a qualified vendor identification data in the order event ; Wherein, in the case that the qualified operator identification data matches the first current operator identification data, the blockchain subsystem (150) will read a delivery destination information in the order event; wherein, the consignee The device (103) is also set to generate an inquiry message after receiving the delivery destination information to inquire about a consignee’s willingness to receive goods, and only after receiving a willingness to receive instructions from the consignee In the case of, a receivable notification is generated and transmitted to the logistics subsystem (120). The logistics information management system (100) according to claim 1, wherein the consignee device (103) is further configured to determine a first current when the consignee device (103) receives the delivery destination information The location, whether it is located within a delivery destination indicated by the delivery destination information, and only if the first current location is within the delivery destination, will the receivable notification be sent to the logistics subsystem ( 120). The logistics information management system (100) according to claim 2, wherein the logistics sub-system The system (120) is also configured to generate a positioning information request to the consignee including a second current operator identification data and the order event identification data when the logistics taxi device (105) is close to the delivery destination. Device (103); wherein, the consignee device (103) is further configured to receive the location information request, and according to the location information request, generate a logistics company that includes the second current operator identification data and the order event identification data Identity verification request; wherein, the blockchain subsystem (150) is also configured to receive the logistics provider’s identity verification request, and find out in the blockchain subsystem ( 150) the order event in the consignee's smart contract, and read the qualified vendor identification data in the order event; wherein, when the qualified vendor identification data matches the second current vendor identification data , The blockchain subsystem (150) will generate an identity verification success notification; wherein, the consignee device (103) is also configured to use a ciphertext key A second current location of the consignee device (103) is encrypted to generate a consignee location ciphertext. The logistics information management system (100) according to claim 3, wherein the consignee device (103) is also configured to transmit the ciphertext key to the logistics subsystem (120), and transmit the consignee The location ciphertext is given to the blockchain subsystem (150); wherein, the blockchain subsystem (150) is also configured to store the consignee’s location ciphertext in the order event in the consignee’s smart contract; Wherein, the logistics subsystem (120) is also set to read the ciphertext of the consignee's location recorded in the order event in the consignee smart contract in the blockchain subsystem (150); wherein, The logistics subsystem (120) is also configured to use the ciphertext key to decrypt the ciphertext of the consignee location to obtain the second current location of the consignee device (103), and transmit the second current location Give the logistics taxi device (105). The logistics information management system (100) described in claim 2 additionally includes: An e-commerce subsystem (110) is configured to establish the consignee smart contract in the blockchain subsystem (150), and write the delivery destination information and the qualified operator identification data into the consignee smart contract In order to form the order event; wherein, the e-commerce subsystem (110) is set to generate the delivery destination information according to a receiving location; wherein, the consignee device (103) is set to transmit a receiving The cargo person’s account number is requested to the e-commerce subsystem (110), so that the e-commerce subsystem (110) establishes a consignee account; wherein, the e-commerce subsystem (110) is set to establish the consignee The corresponding relationship between the account number and the identification data of a consignee smart contract of the consignee smart contract is used as the medium for the consignee device (103) to access the blockchain subsystem (150); among them, The consignee device (103) is also configured to use the consignee account to log in to the e-commerce subsystem (110) to send the delivery destination information request to the blockchain subsystem (150), and the e-commerce The subsystem (110) will request the blockchain subsystem (150) to provide the delivery destination information corresponding to the delivery destination information request based on the consignee’s account number and the corresponding relationship; wherein, the blockchain subsystem ( 150) It is also set to provide the delivery destination information to the e-commerce subsystem (110) when the qualified operator identification data matches the first current operator identification data, and the e-commerce subsystem (110) It is set to transmit the delivery destination information to the consignee device (103) according to the corresponding relationship. The logistics information management system (100) of claim 5, wherein the e-commerce subsystem (110) is further configured to perform a spatial de-identification process on the receiving location to generate the delivery destination information. A computer program product (166) that allows a consignee device (103) used in a logistics information management system (100) to perform a consignee privacy protection operation, wherein the The logistics information management system (100) includes a blockchain subsystem (150), a logistics subsystem (120) and the consignee device (103). The consignee’s privacy protection operation includes: a logistic device ( 105) When approaching a target area, receive a receiving request generated by the logistics subsystem (120), wherein the receiving request includes a first current operator identification data and an order event identification data; according to the receiving Request, generate a delivery destination information request including the order event identification data and the first current operator identification data; receive a delivery destination information; and after receiving the delivery destination information, generate an inquiry message to inquire about a delivery destination A receiving willingness of the consignee, and only when a receiving willingness instruction issued by the consignee is received, a receiving notice is generated and transmitted to the logistics subsystem (120); wherein, the The blockchain subsystem (150) can receive the delivery destination information request, and according to the order event identification data, find an order event in a consignee smart contract in the blockchain subsystem (150), and The order event includes a qualified supplier identification data; wherein, only when the qualified supplier identification data matches the first current supplier identification data, the blockchain subsystem (150) will provide the delivery destination information. The computer program product (166) of claim 7, wherein the consignee privacy protection operation further includes: determining a first current location when the consignee device (103) receives the delivery destination information, Whether it is located in a delivery destination indicated by the delivery destination information, and only when the first current location is within the delivery destination, will the delivery notification be sent to the logistics subsystem (120) . The computer program product (166) according to claim 8, wherein the logistics subsystem (120) can also be used when the logistics taxi device (105) is close to the delivery destination. Generate a location information request that includes a second current operator identification data and the order event identification data; wherein, the consignee privacy protection operation further includes: receiving the location information request; according to the location information request, generating and sending the information containing A logistics provider identity verification request of the second current operator identification data and the order event identification data is sent to the blockchain subsystem (150); an identity verification success notification sent from the blockchain subsystem (150) is received; After the successful notification of the identity verification, obtain a second current location of the consignee device (103); and use a ciphertext key to encrypt the second current location of the consignee device (103) to Generate a consignee’s location ciphertext; where, the blockchain subsystem (150) can receive the logistics provider’s identity verification request, and according to the order event identification data in the logistics provider’s identity verification request, find out where the area is The order event in the consignee's smart contract in the blockchain subsystem (150), and read the qualified vendor identification data in the order event; wherein, the qualified vendor identification data and the second current vendor identification data In the case of a match, the blockchain subsystem (150) will provide a notification of successful identity verification. The computer program product (166) of claim 9, wherein the consignee's hidden protection operation further includes: transmitting the ciphertext key to the logistics subsystem (120); and transmitting the consignee's location secret Text to the blockchain subsystem (150); where the blockchain subsystem (150) can store the consignee’s location ciphertext in the order event in the consignee’s smart contract; where the logistics sub-system The system (120) can read the consignee’s location ciphertext recorded in the order event in the consignee’s smart contract in the blockchain subsystem (150); wherein, the logistics subsystem (120) can Use the ciphertext key to decrypt the consignee location Ciphertext to obtain the second current position of the consignee device (103), to obtain the second current position of the consignee device, and transmit the second current position to the logistics agent (105). The computer program product (166) according to claim 8, wherein the logistics information management system (100) further includes an e-commerce subsystem (110), which is configured to establish the receipt in the blockchain subsystem (150) The consignee’s smart contract, and the delivery destination information and the qualified operator’s identification data are written into the consignee’s smart contract to form the order event; among them, the consignee’s privacy protection operation also includes: send-receive The shipper’s account requests the e-commerce subsystem (110) so that the e-commerce subsystem (110) establishes a consignee account; using the consignee’s account, log in to the e-commerce subsystem (110) to Send the delivery destination information to the blockchain subsystem (150); wherein, the e-commerce subsystem (110) can establish the consignee account according to the consignee’s account request, and establish the consignee’s account and The corresponding relationship between the identification data of a consignee smart contract of the consignee smart contract is used as a medium for the consignee device (103) to access the blockchain subsystem (150); wherein, the electronic The merchant subsystem (110) can request the blockchain subsystem (150) to provide the delivery destination information corresponding to the delivery destination information request based on the consignee’s account number and the corresponding relationship; wherein, the blockchain subsystem (150) Provide the delivery destination information to the e-commerce subsystem (110) under the condition that the qualified operator identification data matches the first current operator identification data, and the e-commerce subsystem (110) can be based on The corresponding relationship transmits the delivery destination information to the consignee device (103).

Images