KR20240033484A - Single delivery management method and system using block chain - Google Patents

Abstract

The present invention relates to a single-item delivery management method and system using blockchain that can systematically and automatically manage a delivery person to prevent additional deliveries from being received until the delivery is completed when a single-item delivery is received.
The single delivery management method using blockchain according to the present invention includes the steps of creating a first channel consisting of a plurality of delivery platforms on a blockchain network and installing a first chain code in the first channel; and creating and updating a delivery person object and a delivery object through execution of the first chain code.
And, the first chain code includes a 'createDeliveryman' function for creating a deliveryman object corresponding to the client to be managed; When a first delivery order occurs, a delivery object for the first delivery order is created, and delivery for the first delivery order (hereinafter referred to as 'first delivery') is assigned to a delivery person (hereinafter, 'first delivery person') 'pickUp' function to reset the delivery progress status of '; And when the first delivery is completed, it includes a 'dropOff' function that updates the delivery progress status of the first delivery person and whether the delivery object has been completed.

Description

Single delivery management method and system using blockchain {SINGLE DELIVERY MANAGEMENT METHOD AND SYSTEM USING BLOCK CHAIN}

The present invention relates to a delivery management method and system implemented based on blockchain. More specifically, when a delivery person receives a single delivery, the present invention relates to a blockchain that can automatically manage to prevent additional deliveries from being received until the delivery is completed. It relates to a single delivery management method and system using .

Recently, for various reasons such as the spread of COVID-19, the increase in single-person households, and the development of delivery applications, the number of consumers ordering food using delivery applications rather than visiting restaurants directly has increased. At the same time, ‘single delivery’, which started on one delivery platform, gained attention. Single delivery is a premium delivery service that performs only one delivery at a time, unlike the existing bundled delivery format that delivers orders received from multiple stores simultaneously.

However, even though it is a single delivery, when the delivery person receives orders through various delivery platforms, there are cases where he takes advantage of the blind spot of being treated as a single delivery and actually performs a bundled delivery.

In other words, although in principle it is a single-item delivery that requires only one delivery at a time, there have been cases where the delivery person deviates from the delivery route and visits another area. This is a problem that occurs when a delivery person receives orders from two delivery applications and then makes two deliveries at the same time. Although it is actually a bundled delivery, each platform treats it as a single delivery.

Because of this, there was a problem that delivery orderers were provided with the same service as before, even though it was a premium service that required paying an additional fee.

To prevent this, delivery platforms are imposing sanctions such as terminating contracts with delivery workers who deliver single deliveries in bundles. However, in order to detect this, there was a limitation that a large amount of manpower was required because each delivery person's delivery route had to be personally checked. Additionally, even if caught along the delivery route, the delivery person may take a wrong turn, so there are limits to imposing sanctions on this.

Korean Patent Publication No. 10-2015-0060658 (published on June 3, 2015) Korean Patent No. 10-2315856 (registered on October 15, 2021)

The present invention is to solve the above problems, and the purpose of the present invention is to provide a block that can automatically and systematically manage the delivery person to prevent additional deliveries from being received until the delivery order is completed when a single delivery is received. It provides a single delivery management method and system using a chain.

The single delivery management method using blockchain according to the present invention to achieve the above purpose includes the steps of creating a first channel consisting of a plurality of delivery platforms on a blockchain network and installing a first chain code in the first channel. ; and creating and updating a delivery person object and a delivery object through execution of the first chain code.

And, the class of the delivery person object includes an 'IMEI' item containing a unique value for identification between delivery people; and an 'inDelivery' item containing a variable value to indicate the delivery progress status of the delivery person.

The 'inDelivery' item is configured to be set to 'true' when the delivery person is in progress of delivery, and to 'false' when delivery is not in progress.

And, the first chain code includes a 'createDeliveryman' function for creating a deliveryman object corresponding to the client to be managed; When a first delivery order occurs, a delivery object for the first delivery order is created, and delivery for the first delivery order (hereinafter referred to as 'first delivery') is assigned to a delivery person (hereinafter, 'first delivery person') 'pickUp' function to reset the delivery progress status of '; And when the first delivery is completed, it includes a 'dropOff' function that updates the delivery progress status of the first delivery person and whether the delivery object has been completed.

When executing the ‘pickUp’ function,

A first step of loading one deliveryman object (hereinafter referred to as 'first deliveryman object') among the plurality of deliveryman objects created by the 'createDeliveryman' function; A second step of calling the 'inDelivery' function of the first delivery person object; When the return for the call of the second step is 'false', the unique value of the 'IMEI' recorded in the first delivery person object (hereinafter referred to as 'first unique value') is used to 1 A third step of creating a delivery object with a unique value set (hereinafter referred to as ‘first delivery object’); and a fourth step of resetting the variable value of 'inDelivery' of the first delivery person object to 'true'.

If the return to the call of the second step is 'true', a 'first' step of calling another delivery person object (hereinafter referred to as 'second delivery person object') that is distinct from the first delivery person object; A second' step of calling the 'inDelivery' function of the second delivery person object; If the return for the call in the 'second' step is 'false', the unique value of the 'IMEI' recorded in the second delivery person object (hereinafter referred to as 'second unique value') is used to A third' step of creating a delivery object with a second unique value set; and a fourth' step of resetting the variable value of 'inDelivery' of the second delivery person object to 'true'.

And, when delivery of the first delivery order is completed, the 'dropOff' function is configured to reset the variable value of 'inDelivery' of the first delivery person object to 'false'.

According to the single delivery management method and system using blockchain according to the present invention, when a delivery person receives a single delivery, the delivery person is automatically excluded from receiving deliveries of multiple delivery applications until the delivery is completed. It has been possible to fundamentally prevent cases of receiving single deliveries from multiple delivery applications and making bundled deliveries.

Accordingly, customers can use the single-item delivery service with confidence, and store owners and delivery platforms can now reliably provide single-item delivery services to customers.

In addition, it is no longer necessary to manually check the delivery route of a delivery person to detect a delivery person who bundles a single delivery as in the past.

1 is a flowchart of a single-item delivery management method using blockchain according to the present invention.
Figure 2 is a block diagram showing the network structure of a single-item delivery management system using blockchain according to the present invention.
Figure 3 is a diagram showing the DeliveryMan class used in the chaincode according to the present invention.
Figure 4 is a diagram showing the delivery class used in the chaincode according to the present invention.
Figure 5 is a diagram showing pseudo-code of the 'createDeliveryman' function of the chaincode according to the present invention.
Figure 6 is a diagram showing the result of a delivery man object created by executing the 'createDeliveryman' function of the chaincode according to the present invention.
Figure 7 is a diagram showing pseudo-code of the 'pickUp' function of the chaincode according to the present invention.
Figure 8 is a diagram showing the result of a delivery object created by executing the 'pickUp' function of the chaincode according to the present invention.
Figure 9 is a diagram showing the results of a delivery person object changed by executing the 'pickUp' function of the chain code according to the present invention.
Figure 10 is a diagram showing pseudo-code of the 'dropOff' function of the chaincode according to the present invention.
Figure 11 is a diagram showing the results of a delivery person object changed by executing the 'dropOff' function of the chain code according to the present invention.
Figure 12 is a diagram showing the result of a delivery object changed by executing the 'dropOff' function of the chaincode according to the present invention.

The terms used in this specification are merely used to describe specific embodiments and are not intended to limit the invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, terms such as “comprise” or “have” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but are not intended to indicate the presence of one or more other features. It should be understood that this does not exclude in advance the possibility of the existence or addition of elements, numbers, steps, operations, components, parts, or combinations thereof.

In addition, in this specification, when a component is referred to as "connected" or "connected" to another component, the component may be directly connected or directly connected to the other component, but specifically Unless there is a contrary description, it should be understood that it may be connected or connected through another component in the middle.

Additionally, in this specification, terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another.

Hereinafter, preferred embodiments, advantages and features of the present invention will be described in detail with reference to the attached drawings.

Figure 1 is a flowchart of a single-item delivery management method using a blockchain according to the present invention, and Figure 2 is a block diagram showing the network structure of a single-item delivery management system using a blockchain according to the present invention.

Referring to Figures 1 and 2, the single delivery management method using blockchain according to the present invention includes a first channel creation step (S10), a delivery person object creation step (S20), a delivery object creation step (S30), and a delivery person object resetting step. It includes a step (S40), a step of resetting the delivery person object and a delivery object (S50), a step of creating a new block (S60), and a step of providing delivery information (S70).

The first channel creation step (S10) is a step of creating a first channel on the blockchain network consisting of multiple companies performing delivery work, that is, multiple delivery platforms. At this time, a chain code (hereinafter referred to as ‘first chain code’) is installed in the first channel.

Accordingly, channels consisting of a plurality of delivery platforms that are distinct from the delivery platforms constituting the first channel, that is, the second channel, third channel, and N channel, can also be created in the same way, and each of these channels has a chain. Code can be installed.

According to one embodiment, the chaincode of the present invention can be programmed using TypeScript, the database can be CouchDB, and the system can be operated on a network called HnNetwork.

According to one embodiment, the single-item delivery management method and system using blockchain of the present invention can be implemented using Hyperledger Fabric, a type of private blockchain platform.

Hyperledger Fabric is a framework derived from the Hyperledger project underway at the Linux Foundation, and is being developed by IBM. Network participants can be authenticated using CA (Certificate Authority), and a smart contract called 'chaincode' is hosted through general programming languages such as Go, node.js, and Java, making it suitable for business implementation.

In other words, Hyperledger Fabric is not a public blockchain in which anyone can participate in the network, but a private blockchain in which only authorized users can participate in the network.

Hyperledger Fabric is a service for corporate business, and only users authorized through a CA (Certificate Authority) can participate in the network. These characteristics ensure the reliability of network users.

Chaincode is a system that enables transactions when multiple users meet certain conditions without a third party. Through this, Hyperledger Fabric becomes decentralized. Hyperledger Fabric is a network comprised of various elements.

Representative examples of these elements include channels, organizations, peers, and ledgers. In a fabric network, each ledger is divided by channel, and only users of each channel can access the ledger of that channel. Therefore, the channel provides confidentiality of data.

Organizations are registered on the network using certificates through a Membership Service Provider (MSP). Peers are nodes that access the ledger and execute smart contracts. The ledger records all changes in data to be shared. The ledger consists of the World State and blockchain. World State refers to a database that records the current state, and blockchain is a place that stores all log records of state changes.

Additionally, Hyperledger Fabric runs using a container system called Docker. Docker is an execution environment abstraction system that creates an execution environment or program into an image and then manages it by creating and executing it as a container, which is an abstraction unit. In other words, in Hyperledger Fabric, peers, databases, CA organizations, etc. are run as one service through Docker.

Representative consensus algorithms used in Hyperledger Fabric include Kafka and RAFT. Kafka was used in the 1.x version of Hyperledger Fabric, and RAFT was used starting from the 2.x version.

Kafka is specialized for distributed environments and operates by exchanging events or messages between producers and consumers, and is useful for processing large amounts of logs in real time. The RAFT consensus algorithm uses a method in which a new block is created once the representative obtains the consent of the participants and confirms it, and has the advantage of successfully carrying out the agreement even if some servers fail.

The structure of Hyperledger Fabric is largely composed of multiple channels within one network, and each channel is formed by organizations. Each organization has a peer, and chaincode is installed and executed on the peer.

The single delivery management system using the blockchain of the present invention consists of multiple delivery platforms as the CA organization of the Hyperledger Fabric described above, and sets delivery workers as clients subject to management.

In the single delivery management system according to the embodiment of Figure 2, there are a total of two organizations in the consortium, that is, a first delivery platform (Platform 1) and a second delivery platform (Platform 2), and these organizations share data with each other. It consists of one channel (i.e., the first channel), each organization has one peer, and is configured to verify and manage transactions within the network through an orderer.

The chaincode including the first chaincode of the present invention includes the 'createDeliveryman' function, the 'pickUp' function, and the 'dropOff' function.

The 'createDeliveryman' function is a function to create a deliveryman object (i.e. deliveryman object) corresponding to the client you want to manage.

The 'pickUp' function is a function for creating a delivery object for the delivery order when a delivery order is generated and updating the delivery progress status of the delivery person assigned to the delivery.

For example, when a first delivery order is generated and delivery for it (hereinafter referred to as 'first delivery') is prepared or started, the 'pickUp' function is called to create a delivery object for the first delivery order, and the The first delivery may be configured to change the delivery progress status of the designated delivery person.

The 'dropOff' function is a function to update the delivery progress status of the delivery person and completion of the delivery object when delivery is completed.

For example, when delivery for the first delivery order is completed, it may be configured to change the delivery progress status of the delivery person who performed the first delivery and reset the delivery completion status of the delivery object created for the first delivery order. there is.

The classes used in chaincodes, including the first chaincode of the present invention, include two types of classes. Specifically, the first class is a DeliveryMan class for managing deliverymen, and the second class is a Delivery class for managing ordered deliveries.

Figure 3 shows the DeliveryMan class used in the chaincode according to the present invention.

Referring to Figure 3, the DeliveryMan class of the present invention includes 'IMEI', 'phone', and 'inDelivery' items.

'IMEI' (International Mobile Equipment Identity) is an item containing a unique value to identify multiple delivery workers who are clients to be managed. According to one embodiment, 'IMEI' may be composed of a key value including the delivery person's cell phone number, for example, may be composed of a total of 15 digits including the cell phone number.

The delivery person's mobile phone number is stored in the 'phone' item. 'inDelivery' is an item used as a variable to indicate the status of whether the delivery person is delivering a single item. Accordingly, 'inDelivery' records content including variable values indicating the delivery progress status of the delivery person.

According to one embodiment, the 'inDelivery' item of the delivery person object class may be configured to be set to 'true' if the delivery person is currently making a delivery, and set to 'false' if the delivery person is not currently making a delivery.

Figure 4 shows the delivery class used in the chaincode according to the present invention.

Referring to Figure 4, the delivery class of the present invention includes 'key', 'IMEI', 'target_place', 'in_time', 'out_time', and 'inDone' items.

According to one embodiment, the class of the delivery object according to the present invention may be created when a delivery item (eg, food) is picked up by a delivery person, that is, when delivery for the corresponding delivery order begins.

'key' is a unique number to identify the delivery order, and can be written in the form "D-{IMEI}". At this time, 'IMEI' is configured to use the 'IMEI' of the delivery person who picked up the delivery.

In other words, the unique value of 'IMEI' of the delivery object class may be generated using the unique value of 'IMEI' of the delivery person object created for the delivery person assigned to the delivery order.

'target_place' indicates the destination (i.e. delivery location) of the delivery order.

'in_time' indicates the time when the delivery item for the corresponding delivery order was picked up.

'out_time' indicates the time when delivery of the corresponding delivery order was completed. At this time, 'out_time' is set to '-1' at the time the delivery of the delivery order is picked up, and a specific value (i.e. delivery completion time) is set when delivery is completed.

By calculating the time taken for delivery through the 'in_time' and 'out_time' variables, it can later be used as a basis for determining whether the delivery person visited another location despite making a single delivery.

'isDone' is used as a variable to indicate whether the delivery has been completed. In other words, if delivery for the delivery order has not yet been completed, that is, when the delivery item for the delivery order has been picked up, the variable is set to 'false', and if delivery is completed, the variable is set to 'true'. It is set.

The deliveryman object creation step (S20) of the present invention is a step of creating a deliveryman object corresponding to the client to be managed through execution of the above-described 'create Deliveryman' function of the chaincode.

Figure 5 shows the pseudo-code of the 'createDeliveryman' function of the chaincode according to the present invention.

Referring to Figure 5, the 'createDeliveryMan' function of the chaincode according to the present invention first creates a unique identification value of the delivery man for whom an object is to be created, that is, an 'IMEI' unique value to be registered in the 'IMEI' item of the DeliveryMan class. Receive input.

At this time, if the delivery man object with the corresponding 'IMEI' unique value already exists, the function ends with the message "deliveryMan already exists."

If there is no existing delivery person object with the corresponding 'IMEI' unique value, a new delivery person object is created, the world state is updated, and the function ends.

Figure 6 shows the result of a delivery man object created by executing the 'createDeliveryman' function of the chaincode according to the present invention.

Referring to Figure 6, as explained in the DeliveryMan class in Figure 3, the 'IMEI' item is set with a key value unique to the delivery man, and the 'phone' item is set with the mobile phone number of the delivery man. can confirm.

Meanwhile, since delivery is not being performed at the time the delivery person object is created, you can see that the 'inDelivery' item is set to 'false' by default.

In the delivery object creation step (S30) of the present invention, when a delivery order is generated, the above-described 'pickUp' function is called to create a delivery object for the delivery order, and the delivery progress status of the delivery person assigned to the delivery is updated or changed. This is the step.

Figure 7 shows pseudo-code of the 'pickUp' function of the chaincode according to the present invention.

Referring to FIG. 7, the delivery object creation step (S30) and the delivery person object resetting step (S40) can be performed by executing the 'pickUp' function as shown in FIG. 7 when a delivery order is generated, and specifically, the following step 'S30 ' includes the first to third steps, and step 'S40' includes the following fourth step.

The first step of the delivery object creation step (S30) is a step of loading one delivery man object (hereinafter referred to as the 'first delivery man object') among the plurality of delivery man objects created by the 'createDeliveryman' function described above.

Here, the first delivery man object called when executing the 'createDeliveryman' function may be a delivery man object created for the delivery man who first receives the call when the delivery man calls for the delivery order.

According to another embodiment, the first deliveryman object called when executing the 'createDeliveryman' function may be configured to be loaded sequentially or randomly from among multiple deliveryman objects, or according to criteria set by the user.

The second step of the delivery object creation step (S30) is a step of calling the 'inDelivery' function of the first delivery person object called in the first step.

The third step of the delivery object creation step (S30) is, when the return to the call of the second step is 'false', the unique value of 'IMEI' recorded in the first delivery object (hereinafter referred to as 'first unique This is a step of creating a delivery object (hereinafter referred to as 'first delivery object') with the first unique value set using the 'value'. Through this, you can indicate which delivery person is performing delivery for the delivery order.

The fourth step, that is, the delivery person object resetting step (S40), is a step of resetting the variable value of 'inDelivery' of the first delivery person object in step 'S30' to 'true'. When the fourth step is completed, the 'pickUp' function ends.

Meanwhile, in the third step of the delivery object creation step (S30), if the return for the call in the second step is 'true', that is, if the delivery person is currently performing delivery, 'bundle delivery is unavailable' It is configured to display a message and load another delivery person object (hereinafter referred to as 'second delivery person object') that is distinct from the first delivery person object.

Subsequently, the 'inDelivery' function of the second delivery person object is called, and if the return to the call is 'false', the unique value of 'IMEI' registered in the second delivery person object (hereinafter referred to as 'second unique value') ') is configured to create a delivery object in which the second unique value is set.

In addition, the 'pickUp' function is terminated after resetting the variable value of 'inDelivery' of the second delivery person object to 'true'.

Figure 8 shows the result of a delivery object created by executing the 'pickUp' function of the chaincode according to the present invention.

Referring to Figure 8, as described in the delivery class of Figure 4, the delivery destination 'target_place' and the 'IMEI' of the delivery person performing delivery for the delivery order are set, and the 'IMEI' is set. You can confirm that the 'key' has been created.

Additionally, 'in_time' is set to the millisecond value when delivery for the corresponding delivery order began, and 'out_time' is set to '-1' because delivery has not yet been completed.

Meanwhile, since delivery cannot be completed when delivery has started, you can see that 'isDone' is set to 'false' by default.

Figure 9 shows the result of a delivery person object changed by executing the 'pickUp' function of the chaincode according to the present invention.

Referring to Figure 9, when a delivery object is created through execution of the 'pickUp' function, it can be seen that the variable value of 'inDelivery' of the delivery person object corresponding to the delivery object is changed from 'false' to 'true'.

In other words, a delivery person for the delivery order is assigned by the 'pickUp' function, and since the delivery has started, 'inDelivery' is reset to 'true'.

The delivery person object and delivery object resetting step (S50) of the present invention is the delivery progress status of the delivery person who performed the delivery and the contents of the corresponding delivery object through execution of the above-described 'dropOff' function upon completion of delivery for the delivery order. This is the step of updating or changing.

Figure 10 shows pseudo-code of the 'dropOff' function of the chaincode according to the present invention.

Referring to FIG. 10, the delivery person object and delivery object resetting step (S50) can be performed by executing the 'dropOff' function as shown in FIG. 10 when delivery for the corresponding delivery order is completed.

The 'dropOff' function calls the 'keyGen' function to create a key value to retrieve the delivery object for the delivery order for which delivery has been completed. The key value is in the form of "D-{IMEI}", so 'IMEI' is used as the input value.

Afterwards, the key value and 'IMEI' are used to retrieve the delivery object and delivery person object for the delivery order that has been completed, respectively. The 'dropOff' function is called when delivery is completed, so the 'isDone' variable of the delivery object, which indicates whether delivery has ended, is reset to 'true', and the 'inDelivery' variable of the delivery object, which indicates whether the delivery person is in progress, is reset to 'true'. After resetting to 'false', update the World State and exit the function.

For example, assume that a first delivery order is generated, a first delivery object is created correspondingly, and a first delivery person performs delivery for the first delivery order.

In the above case, when delivery of the first delivery order is completed and the 'dropOff' function is executed, the 'dropOff' function is executed using the 'IMEI' recorded in the delivery object of the first delivery person and the 'dropOff' function recorded in the first delivery object. Using 'IMEI', the delivery person object and delivery object (i.e., the first delivery person object and the first delivery object) corresponding to the first delivery order are retrieved.

Subsequently, the 'dropOff' function resets the variable value of 'inDelivery' of the first delivery person object to 'false' and resets the variable value of 'isDone' of the first delivery object to 'true'.

Figure 11 shows the result of a delivery person object changed by executing the 'dropOff' function of the chaincode according to the present invention.

Referring to Figure 11, when delivery for the corresponding delivery order is completed, it can be seen that the 'inDelivery' variable, which was set to 'true' by the 'pickUp' function, is reset to 'false'.

Figure 12 shows the result of a delivery object changed by executing the 'dropOff' function of the chaincode according to the present invention.

Referring to Figure 12, when delivery for the corresponding delivery order is completed, it can be seen that the 'isDone' function indicating whether delivery has been completed is reset from 'false' to 'true'.

The new block creation step (S60) of the present invention is a step in which a new block in which delivery-related information generated for the corresponding delivery order is recorded is created by the orderer through steps 'S30' to 'S50'. According to one embodiment, a new block may be created once confirmation is completed with the consent of participants of the corresponding channel (e.g., the first channel described above).

The delivery information provision step (S70) of the present invention is a step of providing delivery-related information recorded in the new block of step 'S30' so that the relevant channel participants can view it.

In other words, the participants of the channel (e.g., the above-mentioned first channel), that is, the organization (e.g., delivery platform) that constitutes the channel, use the chaincode (e.g., the first chaincode) installed on the peer of the organization. Through the execution of , you can access the block (i.e., the block created in step 'S30') and receive delivery information related to the delivery order.

According to the single delivery management method and system using the blockchain of the present invention as described above, when a delivery person receives a single delivery, the delivery person is automatically excluded from receiving deliveries of multiple delivery applications until the delivery is completed. As a result, it has been possible to fundamentally prevent cases where delivery workers receive single deliveries from multiple delivery applications and make bundled deliveries.

Accordingly, customers can use the single-item delivery service with confidence, and store owners and delivery platforms can now reliably provide single-item delivery services to customers.

In addition, it is no longer necessary to manually check the delivery route of a delivery person to detect a delivery person who bundles a single delivery as in the past.

Although preferred embodiments of the present invention have been described and illustrated above using specific terms, such terms are only for clearly describing the present invention, and the embodiments of the present invention and the described terms are in accordance with the technical spirit and scope of the following claims. It is self-evident that various changes and changes can be made without deviating from it. These modified embodiments should not be understood individually from the spirit and scope of the present invention, but should be regarded as falling within the scope of the claims of the present invention.

Claims (9)

On a blockchain network, a first channel consisting of a plurality of delivery platforms is created and a first chain code is installed in the first channel; and
Comprising the step of creating and updating a delivery person object and a delivery object through execution of the first chain code,
The class of the delivery person object is,
An 'IMEI' field containing a unique value for identification between delivery people; and an 'inDelivery' item containing a variable value to indicate the delivery progress status of the delivery person,
The ‘inDelivery’ item above is,
If the delivery person is in progress of delivery, it is set to 'true', and if delivery is not in progress, it is set to 'false'.
The first chain code is,
'createDeliveryman' function to create a deliveryman object corresponding to the client you want to manage;
When a first delivery order is generated, a delivery object for the first delivery order is created, and delivery for the first delivery order (hereinafter referred to as 'first delivery') is assigned to a delivery person (hereinafter, 'first delivery person') 'pickUp' function to reset the delivery progress status of '; and
When the first delivery is completed, it includes a 'dropOff' function that updates the delivery progress status of the first delivery person and whether the delivery object is completed,
When executing the ‘pickUp’ function,
A first step of loading one deliveryman object (hereinafter referred to as 'first deliveryman object') among the plurality of deliveryman objects created by the 'createDeliveryman'function;
A second step of calling the 'inDelivery' function of the first delivery person object;
When the return for the call of the second step is 'false', the unique value of the 'IMEI' recorded in the first delivery person object (hereinafter referred to as 'first unique value') is used to 1 A third step of creating a delivery object with a unique value set (hereinafter referred to as ‘first delivery object’); and
A fourth step of resetting the variable value of 'inDelivery' of the first delivery person object to 'true'. A single delivery management method using a blockchain, comprising a.
According to claim 1,
When the return to the call of the second step is 'true', a 'first' step of calling another delivery person object (hereinafter referred to as 'second delivery person object') that is distinct from the first delivery person object;
A second' step of calling the 'inDelivery' function of the second delivery person object;
If the return for the call in the 'second' step is 'false', the unique value of the 'IMEI' recorded in the second delivery person object (hereinafter referred to as 'second unique value') is used to A third' step of creating a delivery object with a second unique value set; and
A single delivery management method using a blockchain, comprising: a 'fourth' step of resetting the variable value of 'inDelivery' of the second delivery person object to 'true'.
According to claim 1,
According to claim 1,
Upon completion of delivery for the first delivery order,
The ‘dropOff’ function is,
A single delivery management method using blockchain, characterized in that the variable value of 'inDelivery' of the first delivery person object is reset to 'false'.
According to claim 1,
The class of the delivery object is,
'IMEI', which contains a unique value for identification between delivery orders, 'target_place', which indicates the destination (delivery place) of the delivery order, 'in_time', which indicates the time when the delivery item of the delivery order was picked up, the delivery order Includes an 'out_time' item indicating the time when delivery of the delivery was completed, and an 'isDone' item containing a variable value to indicate whether delivery of the corresponding delivery order was completed,
The ‘isDone’ item above is,
A single delivery management method using blockchain, characterized in that it is set to 'false' if delivery for the delivery order has not been completed, and is set to 'true' if delivery is completed.
According to clause 4,
The unique value of the 'IMEI' of the delivery object class is,
It is created using the unique value of the 'IMEI' of the delivery person object created for the delivery person assigned to the delivery order,
When delivery of the first delivery order is completed and the 'dropOff' function is executed,
Using 'IMEI' recorded in the first delivery person object and 'IMEI' recorded in the first delivery object, calling the first delivery person object and the first delivery object for the first delivery order ; and
A single delivery management method using blockchain, comprising the step of resetting the variable value of 'inDelivery' of the first delivery person object to 'false'.
According to clause 4,
Upon completion of delivery for the first delivery order,
The ‘dropOff’ function is,
A single delivery management method using blockchain, characterized in that the variable value of 'isDone' of the first delivery object is reset to 'true'.
According to claim 1,
The 'IMEI' is a single delivery management method using blockchain, characterized in that it consists of a key value including the mobile phone number of the delivery person.
According to claim 1,
The ‘inDelivery’ item above is,
A single delivery management method using blockchain, characterized in that the delivery person object is set to 'false' at the time of creation.
According to claim 1,
A single delivery management method using blockchain, wherein the blockchain is a Hyperledger Fabric blockchain.