JP7213705B2 - Program, information processing device, and information processing method - Google Patents

Description

The present disclosure relates to a program, an information processing device, and an information processing method.

In recent years, commodity transactions between individuals using the Internet and communication lines have been carried out. For example, a seller registers and puts up an article on a predetermined trading platform, and a purchaser also makes a purchase application for the article put up on the predetermined trading platform. After that, the seller and the purchaser generally communicate with each other to pay the money and send and receive the goods. For example, Japanese Laid-Open Patent Publication No. 2002-200001 discloses a system for making payment when a product is received by a designated recipient at a designated location.

Japanese Patent Application Laid-Open No. 2018-036766

In the past, the delivery of goods was generally entrusted to the delivery of goods by delivery companies that are in charge of transportation in wide areas, but in recent years, as a new delivery business, Requests for delivery are also being considered. In this way, by requesting delivery from individuals, it is possible to provide buyers and sellers with new options for delivery methods, and to provide individuals in charge of delivery with a new means of income. can do. In addition, such personal delivery can be one means of solving the labor shortage in the delivery industry.

On the other hand, in the case of delivery by a delivery company, it is unlikely that the delivery company will not come to pick up the goods even though the delivery fee has been paid, or that the goods collected by the delivery company will not be delivered to the delivery destination and run away. ,Unthinkable. However, when a delivery request is made to an individual, such reliability cannot necessarily be guaranteed. Therefore, when a delivery request is made to an individual, a method for improving delivery reliability is desired.

Therefore, the present disclosure has been made in view of such circumstances, and aims to provide a program, an information processing apparatus, and an information processing method for realizing a highly reliable delivery method.

A program according to another embodiment of the present disclosure includes a step of receiving information related to a delivery request from another information processing device in an information processing terminal, and sending a predetermined a step of receiving, from a blockchain network, first transaction information for remittance of virtual assets, wherein the first transaction information specifies one or more unlocking conditions; and a second information code possessed by the delivery destination user regarding the delivery request, and the first information contained in the first information code and the second information contained in the second information code are read. and creating second transaction information including the first information and the second information as a release condition corresponding to one of the unlocking conditions, and transmitting the second transaction information to the blockchain network. .

FIG. 1 shows the configuration of a trading system 1 according to one aspect of the embodiment. FIG. 2 shows an example of a hardware configuration of an information processing device according to the present disclosure. FIG. 3 shows an example of a block diagram showing the functional configuration of the server 110 according to the first embodiment. FIG. 4 shows an example of the data structure stored in the delivery request DB 332. As shown in FIG. FIG. 5 shows an example of a block diagram showing the functional configuration of the deliverer terminal 120A according to the first embodiment. FIG. 6 shows an example of a data structure stored in the accepted matter DB 522. As shown in FIG. FIG. 7 shows an example of a block diagram showing the functional configuration of the seller terminal 120B and purchaser terminal 120C according to the first embodiment. FIG. 8 shows an example of the data structure stored in the delivery request DB 732 of the seller terminal 120B. FIG. 9 shows an example of the data structure stored in the delivery request DB 732 of the purchaser terminal 120C. FIG. 10 shows an example of a sequence diagram showing processing performed by the trading system 1 in the first embodiment. FIG. 11 shows an example of a block diagram showing the functional configuration of the server 110 according to the second embodiment. FIG. 12 shows an example of the data structure stored in the delivery request DB 1122. As shown in FIG. FIG. 13 shows an example of a block diagram showing the functional configuration of the deliverer terminal 120A according to the second embodiment. FIG. 14 shows an example of the data structure stored in the delivery request DB 1322. As shown in FIG. FIG. 15 shows an example of a block diagram showing the functional configuration of the seller terminal 120B according to the second embodiment. FIG. 16 shows an example of the data structure stored in the delivery request DB 1522. As shown in FIG. FIG. 17 shows an example of a sequence diagram showing processing performed by the transaction system 1 in the second embodiment. FIG. 18 shows an example of a block diagram showing the functional configuration of the deliverer terminal 120A according to the second embodiment. FIG. 19 shows an example of a block diagram showing the functional configuration of the seller terminal 120B and purchaser terminal 120C according to the second embodiment. FIG. 20 shows a diagram schematically showing the structure of transaction information in the second embodiment. FIG. 21 shows an example of a sequence diagram showing processing performed by the trading system 1 in the second embodiment. FIG. 22 shows a diagram schematically showing the structure of transaction information in a modified example of the second embodiment. FIG. 23 shows an example of a sequence diagram showing processing performed by the trading system 1 in the modified example of the second embodiment.

<Compliance with laws and regulations>
The disclosure herein, when implemented, will be implemented in compliance with the laws of each country implementing the disclosure. In addition, the disclosure described herein is implemented with all alterations, substitutions, variations, alterations, and modifications that may be made by those skilled in the art as necessary to comply with the laws and regulations of each country.

Modes for implementing a program, an information processing apparatus, and an information processing method according to the present disclosure will be described with reference to the drawings.

<System configuration>
FIG. 1 shows the configuration of a trading system 1 for effectively implementing an information processing method according to an embodiment of the present disclosure. As disclosed in FIG. 1, in transaction system 1, server 110A, server 110B, terminal 120A, terminal 120B, and terminal 120C are connected via network . Server 110A, server 110B, terminal 120A, terminal 120B, and terminal 120C may constitute a distributed ledger (hereinafter also referred to as "block chain"). In this disclosure, the blockchain will be described as a public type configuration without a central administrator, but it is not limited to this and may be a private type or a consortium type.

In the present disclosure, server 110A and server 110B may be referred to as server 110, respectively, when there is no need to distinguish between server 110A and server 110B.

In the present disclosure, the terminal 120A, the terminal 120B, and the terminal 120C may each be referred to as the terminal 120 when there is no need to distinguish between the terminal 120A, the terminal 120B, and the terminal 120C.

In the present disclosure, when there is no need to distinguish between the server 110 and the terminal 120 , the server 110 and the terminal 120 may each be expressed as the information processing device 200 . Note that the number of information processing apparatuses 200 connected to network 130 is not limited.

The server 110 provides predetermined services to the terminal 120 used by the user via the network 130 . Examples of predetermined services include, but are not limited to, payment services, financial services, e-commerce services, SNS (Social Networking Services) represented by instant messengers, content providing services such as music, videos, and books. The server 110 can provide a predetermined service to one or more terminals 120 by the user using the predetermined service via the terminal 120 .

In the present disclosure, a payment service means a service that allows one or more users to give and receive money or money equivalents. As non-limiting examples, one-dimensional codes (barcodes, etc.), two-dimensional codes (QR code (registered trademark), etc.) (hereinafter, one-dimensional codes and two-dimensional codes are collectively referred to as "two-dimensional codes, etc." ), short-range wireless communication (NFC (Near Field Communication), BLE (Bluetooth (registered trademark) Low Energy), Wi-Fi (registered trademark), ultrasonic communication, infrared communication, etc.) including. In addition, payment by reading a two-dimensional code or the like by the terminal 120 of the user (payer) who pays the price is expressed as "user-readable code payment" or "MPM (Merchant Presented Mode)". The terminal 120 of the user who performs the payment displays a two-dimensional code, etc., and the terminal 120 of the user (seller, claimant) at the store who bills for the payment reads the displayed two-dimensional code, etc. This is referred to as “store reading type code payment” or “CPM (Consumer Presented Mode)”. Note that the MPM and CPM may be dynamic or static.

As necessary, the terminal used by the user X is expressed as a terminal 120X, and the user information for a predetermined service associated with the user X or the terminal 120X is expressed as user information X. The user information is user information associated with an account used by the user in a predetermined service. User information includes, by way of example and not limitation, user's name, user's icon image, user's age, user's gender, user's address, user's hobbies, entered by the user or provided by a given service Information associated with the user such as preference, user identifier, electronic value (electronic money) balance information associated with the user, credit card information (credit card number, etc.) associated with the user. Any one of or a combination thereof may be used.

The network 130 plays a role of connecting two or more information processing apparatuses 200 . The network 130 means a communication network that provides a connection path so that the terminal 120 can transmit and receive data after connecting to the server 110 .

One or more portions of network 130 may be wired or wireless networks. Network 130 may include, by way of example and not limitation, an Ad Hoc Network, an intranet, an extranet, a Virtual Private Network (VPN), a Local Area Network (LAN), a wireless Wireless LAN (WLAN), Wide Area Network (WAN), Wireless WAN (WWAN), Metropolitan Area Network (MAN), Part of the Internet, Public Switched Telephone Network (Public Part of Switched Telephone Network (PSTN), mobile phone networks, ISDNs (Integrated Service Digital Networks), wireless LANs, LTE (Long Term Evolution), CDMA (Code Division Multiple Access), Bluetooth (registered trademark), satellite communication, etc., or a combination of two or more thereof. Network 130 may include one or more networks 130 .

The information processing device 200 may be any information processing device capable of implementing the functions and/or methods described in this disclosure.

The information processing device 200 may be, as a non-limiting example, a smart phone, a mobile phone (feature phone), a computer (as a non-limiting example, desktop, laptop, tablet, etc.), a server device, a media computer platform (as a non-limiting example , cables, satellite set-top boxes, digital video recorders, etc.); watch devices), other types of computers, or communication platforms.

<Hardware (HW) configuration>
The HW configuration of the information processing device 200 included in the trading system 1 will be described with reference to FIG.

The information processing device 200 includes a processor 201 , a memory 202 , a storage 203 , an input/output interface (input/output I/F) 204 and a communication interface (communication I/F) 205 . Each component of the HW of the information processing device 200 is interconnected via a bus B as an example and not a limitation.

The information processing apparatus 200 realizes the functions and/or methods described in the present disclosure through cooperation of the processor 201, the memory 202, the storage 203, the input/output I/F 204, and the communication I/F 205. do.

Processor 201 executes functions and/or methods implemented by codes or instructions contained in programs stored in storage 203 . Processor 201 includes, by way of example and not limitation, a central processing unit (CPU), a Micro Processing Unit (MPU), a Graphics Processing Unit (GPU), a microprocessor, a processor core, a multiprocessor. , ASIC (Application-Specific Integrated Circuit), FPGA (Field Programmable Gate Array), etc., logic circuits (hardware) formed in integrated circuits (IC (Integrated Circuit) chip, LSI (Large Scale Integration)), etc. Each process disclosed in each embodiment may be implemented by a dedicated circuit. Moreover, these circuits may be realized by one or more integrated circuits, and a plurality of processes shown in each embodiment may be realized by one integrated circuit. LSIs are also called VLSIs, super LSIs, ultra LSIs, etc., depending on the degree of integration.

Memory 202 temporarily stores programs loaded from storage 203 and provides a work area for processor 201 . The memory 202 also temporarily stores various data generated while the processor 201 is executing the program. Memory 202 includes, by way of example, and not limitation, random access memory (RAM), read only memory (ROM), and the like.

The storage 203 stores programs. The storage 203 includes, as non-limiting examples, HDDs (Hard Disk Drives), SSDs (Solid State Drives), flash memories, and the like.

Communication I/F 205 transmits and receives various data via network 130 . The communication may be performed by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. Communication I/F 205 has a function of executing communication with another information processing apparatus via network 130 . Communication I/F 205 transmits various data to other information processing apparatuses according to instructions from processor 201 . The communication I/F 205 also receives various data transmitted from other information processing apparatuses and transmits the data to the processor 201 .

The input/output I/F 204 includes an input device for inputting various operations to the information processing device 200 and an output device for outputting processing results processed by the information processing device 200 . The input/output I/F 204 may be integrated with the input device and the output device, or may be separated into the input device and the output device.

The input device is realized by any one or a combination of all kinds of devices capable of receiving input from a user and transmitting information related to the input to the processor 201 . Input devices include, but are not limited to, touch panels, touch displays, hardware keys such as keyboards, pointing devices such as mice, cameras (operation input via images), and microphones (operation input via voice).

The output device is realized by any one of all kinds of devices capable of outputting the processing result processed by the processor 201, or a combination thereof. When outputting the processing result as a video and/or moving image, the output device is any or all kinds of devices capable of displaying the display data according to the display data written in the frame buffer. It is realized by combination. Output devices include, but are not limited to, touch panels, touch displays, monitors (as non-limiting examples, liquid crystal displays, OELD (Organic Electroluminescence Display), etc.), head mounted displays (HDM: Head Mounted Display), projection mapping, holograms , devices capable of displaying images, text information, etc. in the air (or in a vacuum), speakers (audio output), printers, and the like. Note that these output devices may be capable of displaying display data in 3D.

The program of each embodiment of the present disclosure may be provided in a state stored in a computer-readable storage medium. The storage medium can store the program in a "non-temporary tangible medium". Programs include, by way of example and not limitation, software programs and computer programs.

The storage medium may, where appropriate, be one or more semiconductor-based or other integrated circuits (ICs), including, but not limited to, field programmable gate arrays (FPGAs), application specific ICs (ASICs), etc. ), hard disk drive (HDD), hybrid hard drive (HHD), optical disk, optical disk drive (ODD), magneto-optical disk, magneto-optical drive, floppy diskette, floppy disk drive (FDD), magnetic It may include tapes, solid state drives (SSDs), RAM drives, secure digital cards or drives, any other suitable storage media, or suitable combinations of two or more thereof. Storage media may, where appropriate, be volatile, nonvolatile, or a combination of volatile and nonvolatile.

Also, the program of the present disclosure may be provided to the information processing apparatus 200 via any transmission medium (communication network, broadcast wave, etc.) capable of transmitting the program.

Embodiments of the present disclosure may also be implemented in the form of a data signal embedded in a carrier wave in which the program is embodied by electronic transmission.

In addition, the program of the present disclosure is implemented using scripting languages such as JavaScript (registered trademark) and Python, programming languages such as C language, Go language, Swift, Kotlin, and Java (registered trademark) as examples without limitation. be done.

At least part of the processing in the information processing device 200 may be realized by cloud computing configured by one or more computers.

At least part of the processing in the information processing device 200 may be configured to be performed by another information processing device. In this case, at least part of the processing of each functional unit realized by the processor 201 may be performed by another information processing apparatus.

<Others>
Unless explicitly mentioned, the configuration of determination in the embodiments of the present disclosure is not essential, and predetermined processing is performed when the determination condition is satisfied, or predetermined processing is performed when the determination condition is not satisfied. You may

In this disclosure, unless stated otherwise or indicated by context, "or" has an inclusive rather than exclusive meaning. Thus, in this disclosure, "A or B" means "A, B, or both," unless stated otherwise or indicated by context. Further, "at least one of A and B" means "A, B, or both." Further, unless stated otherwise or indicated by context, "a," "an," or "the" shall mean "one or more." Thus, as used herein, "an A" or "the A" means "one or more A," unless stated otherwise or indicated by context.

The present disclosure encompasses all changes, substitutions, variations, alterations, and modifications that a person skilled in the art can make to the embodiments and/or examples of the present disclosure. Similarly, where appropriate, the appended claims cover all alterations, substitutions, variations, alterations, and modifications to the disclosed embodiments and/or examples that a person skilled in the art could make. contain. Further, the present disclosure provides one or more features of the embodiments and/or examples of the present disclosure and other embodiments and/or examples of the present disclosure that may be made by a person of ordinary skill in the art. It encompasses any combination of one or more features.

In addition, any device or system or component of a device or system that is adapted, arranged, capable, configured, usable, operable, or capable of performing a specified function References in the appended claims to the device, system or component so adapted, arranged, capable, configured, enabled, operable to the extent that the device, system, component or any particular feature thereof is activated, turned on, or unlocked.

This disclosure may obtain consent from the user prior to or immediately prior to practicing any embodiment or example, unless explicitly stated otherwise. In addition, the consent to be obtained may be comprehensive or may be obtained on a case-by-case basis.

Hereinafter, an embodiment according to an example of the present disclosure will be described with reference to the drawings. However, the embodiments described below are merely examples, and are not intended to exclude various modifications and application of techniques not explicitly described below. That is, the example of the present disclosure can be modified in various ways without departing from the scope of the present disclosure. In addition, in the description of the drawings below, the same or similar parts are denoted by the same or similar reference numerals, and the drawings are schematic and do not necessarily correspond to actual dimensions, proportions, and the like. Furthermore, even between drawings, there are cases where portions having different dimensional relationships and ratios are included.

<First embodiment>
In the first embodiment, in a transaction system 1 between users, a seller key (first information) included in a seller code (first information code) given to a delivery source user (seller) and a delivery destination user ( An embodiment in which payment of shipping charges to a delivery person can be executed when a purchaser key (second information) included in a purchaser code (second information code) given to a purchaser) is acquired. is. Details of the seller code, seller key, purchaser code and purchaser key will be described later.

In the program, information processing terminal, and information processing method according to the first embodiment, a predetermined information processing device gives an information code to each of a delivery source user and a delivery destination user for each delivery request. The deliverer collects the seller key and purchaser key included in each information code. Further, the deliverer generates a delivery charge payment request including the purchaser key and the seller key, and transmits the request to a predetermined information processing device. Note that the payment request may include information other than the seller key and the purchaser key (for example, a delivery person's identifier, etc.).

In the transaction system 1, for example, a distributor terminal 120A owned by a shipper, a seller terminal 120B owned by a delivery source user, a purchaser terminal 120C owned by a delivery destination user, and a server 110 for managing information codes are connected to a network. 130.

Hereinafter, assuming an electronic commerce platform for explanation, the terminal used by the individual who received the delivery request is the deliverer terminal 120A, the terminal used by the delivery source user (seller) is the seller terminal 120B, and the delivery destination user The terminal used by the (purchaser) will be described as a purchaser terminal 120C. However, the first embodiment is not limited to this.

<Effects of the first embodiment>
According to the first embodiment, along with the request for payment of the shipping fee, the seller key acquired at the delivery source (typically the seller) and the purchase order acquired at the delivery destination (typically the purchaser) By transmitting the delivery key, it is confirmed whether the delivery request has been properly fulfilled, and the payment of the delivery charge is executed. That is, the deliverer receives the item from the delivery source user and delivers the item to the delivery destination user, so that the delivery fee cannot be received unless the seller key and the purchaser key are acquired. In this way, the payment of the shipping fee is executed after confirming that the delivery has been made, so it is possible to avoid situations where the delivery person receives the shipping fee and does not deliver, realizing a highly reliable delivery method. can do. In addition, it is possible to suppress the occurrence of a situation in which a deliverer runs away with a package to be delivered, and from this point of view as well, a highly reliable delivery method can be realized.

<Functional configuration of the first embodiment>
The functional configurations of the server 110, the deliverer terminal 120A, the seller terminal 120B, and the purchaser terminal 120C will be described with reference to FIGS. Each functional unit disclosed in FIGS. 3, 5, and 7 is realized by cooperation of the processor 201, the memory 202, the storage 203, the input/output I/F 204, and the communication I/F 205 provided in the information processing apparatus 200. be done.

(1) Functional Configuration of Server 110 FIG. 3 shows an example of a block diagram showing the functional configuration of the server 110 according to the first embodiment. The server 110 is an example of an information processing terminal that issues an information code in response to a delivery request in the transaction system 1 and performs payment processing in response to receiving information included in the information code. The server 110 has an input/output I/F 311 , a communication I/F 312 , a storage section 320 and a control section 330 .

The input/output I/F 311 can be implemented using the input/output I/F 204, for example. Also, the communication I/F 312 can be implemented using the communication I/F 205, for example. Storage unit 320 may be implemented using memory 202 and/or storage 203, for example. The control unit 330 can be implemented, for example, by the processor 201 reading and executing a program stored in the storage unit 320 .

The storage unit 320 also stores a program 321 executed by the server 110 according to this embodiment, and a delivery request DB 332 that manages information on received delivery requests.

This program 321 is, for example, a program for issuing an information code in response to a delivery request and performing settlement processing in response to receiving information included in the information code. The program 321 may be recorded in a computer-readable recording medium, and may be installed in the computer from this recording medium.

The delivery request DB 332 manages information related to delivery requests received from the seller terminal 120B and/or the purchaser terminal 120C. Information related to delivery requests includes, for example, an ID assigned to each delivery request, a seller code assigned to a user (seller) at the delivery source, a seller key included in the seller code, a user at the delivery destination (purchase a purchaser code given to a purchaser) and a purchaser key included in the purchaser code. Also, information on the delivery source and/or the delivery destination (for example, address, telephone number, name, etc.) may be managed in association with the ID of the delivery request.

Furthermore, when the seller code includes the first encrypted information obtained by encrypting the seller key and the purchaser code includes the second encrypted information obtained by encrypting the purchaser key, the encryption key used for the encryption and the A decryption key for decrypting the encrypted information may be managed in association with the ID of the delivery request.

FIG. 4 schematically shows part of the data structure of the information about the delivery request stored in the delivery request DB 332. As shown in FIG.

The "delivery request ID" stores identification information for the server 110 to uniquely identify the delivery information. When the receiving unit of the server 110 receives a delivery request from the seller terminal 120B and/or the purchaser terminal 120C, the delivery request management unit 331 of the server 110 assigns an ID to the delivery request and stores the delivery request in the delivery request DB 332. can be instructed to be stored in

The "seller code" and "purchaser code" store, for example, two-dimensional codes such as bar codes and QR codes that are obtained by converting the seller key and the purchaser key. Here, the two-dimensional code refers to a code that can be converted by an optical detection device into an electrical signal based on a predetermined method based on the reflection of irradiated light, and that can be converted into a corresponding computer code.

Moreover, the seller code and the purchaser code are not limited to two-dimensional codes such as bar codes and QR codes, and codes suitable for exchanging information between terminals can be used. For example, a form suitable for infrared communication or wireless communication such as Bluetooth (registered trademark) may be used.

The “seller key” is information that the deliverer obtains from the delivery source user by reading the seller code. The shipper can indicate that the package has been received from the shipper user by presenting the seller key. The "purchaser key" is information that the deliverer obtains from the delivery destination user by reading the purchaser code. The deliverer can indicate that the package has been delivered to the delivery destination user by presenting the purchaser key.

The seller key and purchaser key may be, for example, a string of random alphanumeric characters and symbols. Similarly, a string of random alphanumeric characters and symbols can be used for each piece of information included in the information code in the present disclosure.

If the conversion method from the seller key or the like to the seller code or the like is predetermined, the delivery request DB 332 does not store the seller code and the purchaser code, and stores only the seller key and the purchaser key. It is good also as a mode to store.

In such a mode, for example, the transmitting section of the server 110 transmits the seller key and the purchaser key as they are to the seller terminal 120B and the purchaser terminal 120C, and displays the information code of the seller terminal 120B and the purchaser terminal 120C. It can be converted into a seller code and a purchaser code on the part 732 side. Also, when the transmission unit of the server 110 transmits the seller key and the purchaser key to the seller terminal 120B and the purchaser terminal 120C, it converts them into the seller code and the purchaser code based on a predetermined method and then transmits them. You can also

An expiration date may be set for each of the seller code and the purchaser code. Here, the term of validity can be, for example, a term for accepting payment requests for delivery charges. More specifically, when the seller code and the purchaser code are read beyond the expiration date and the seller key and the purchaser key are transmitted to the server 110, the request for payment of the shipping fee is not executed. can be

This makes it possible to impose a time limit on the delivery person until the delivery is completed, thereby further improving the reliability of the delivery.

The "encryption key" and "decryption key" store information for encrypting and decrypting the seller key and purchaser key. The "encryption key" and "decryption key" are preferably set individually for each delivery request ID. As a result, it is possible to prevent the first encrypted information and the second encrypted information associated with a plurality of delivery request IDs from being illegally decrypted with one decryption key. Note that the seller key and the purchaser key may be encrypted and decrypted using different encryption and decryption keys, respectively.

Next, returning to FIG. 3, the control unit 330 will be described. The control unit 330 has a delivery request management unit 331 and a payment processing unit 332 .

The communication I/F 312 receives a delivery request from the seller terminal 120B and/or the purchaser terminal 120C, or receives a seller key and a purchaser key together with a delivery charge payment request from the deliverer terminal 120A. It has a function as

The communication I/F 312 also transmits information related to a delivery request and a decryption key to the deliverer terminal 120A, transmits a seller code to the seller terminal 120B, and transmits a purchaser code to the purchaser terminal 120C. It has a function as a transmission unit to transmit data.

These functional configurations are realized by the processor 201 reading and executing the program 321 stored in the storage unit 320 . In addition, the functional configuration realized by the server 110 may be appropriately omitted, replaced, or added according to the embodiment or example.

The delivery request management unit 331 has a function of managing information in the delivery request DB 322 . As an example, when the receiving unit of the server 110 receives a delivery request from the seller terminal 120B and/or the purchaser terminal 120C, the delivery request management unit 331 stores a delivery request ID for uniquely identifying the delivery request. is attached, and information on the delivery request is stored in the delivery request DB 322 . Also, the delivery request management unit 331 sets a seller key and a purchaser key for each delivery request ID, sets the encryption key and decryption key as necessary, and stores them in the delivery request DB 322 .

At this time, the delivery request management unit 331 can also store the delivery information regarding the delivery source and delivery destination and the information regarding the delivery person in association with the created delivery request ID.

Further, when the seller key and the purchaser key are set for each delivery request ID, the delivery request management unit 331 instructs the transmission unit to transmit the information to the seller terminal 120B and the purchaser terminal 120C. give instructions.

The settlement processing unit 332 performs various processes for executing the settlement of the shipping charges. As an example, the settlement processing unit 332 receives a deposit request for depositing the shipping fee from the delivery source user and/or the delivery destination user together with the delivery request, and executes deposit processing based on the received deposit request. Then, when receiving a delivery charge payment request from the deliverer together with the seller key and the purchaser key, the payment processing for paying the deposited delivery charge to the deliverer is executed.

(2) Functional Configuration of Deliverer Terminal 120A FIG. 5 shows an example of a block diagram showing the functional configuration of the deliverer terminal 120A according to the first embodiment. The deliverer terminal 120A is an example of an information processing terminal used by a deliverer in the trading system 1. FIG. The deliverer terminal 120</b>A has an input/output I/F 511 , a communication I/F 512 , a storage section 520 and a control section 530 .

The input/output I/F 511 can be implemented using the input/output I/F 204, for example. Moreover, communication I/F512 can be implement|achieved using communication I/F205, for example. Storage unit 520 may be implemented using memory 202 and/or storage 203, for example. The control unit 530 can be realized, for example, by the processor 201 reading and executing a program stored in the storage unit 520 .

The input/output I/F 521 displays a predetermined screen, receives user operations using buttons displayed on the screen of the deliverer terminal 120A, the touch panel of the deliverer terminal 120A, and the like, and controls information related to the operations. Output to unit 530 .

The communication I/F 512 of the deliverer terminal 120A has a function as a receiving unit that receives information on delivery requests and decryption keys from the server 110 . The communication I/F 512 of the deliverer terminal 120A has a function as a transmission unit that transmits the seller key and the purchaser key to the server 110 together with the delivery fee payment request.

The storage unit 520 stores a program 521 executed by the deliverer terminal 120A and an accepted case DB 522 for managing information related to delivery requests received from the server 110. FIG.

This program 521, for example, acquires a seller key and a purchaser key from a delivery source user and a delivery destination user, and transmits a delivery charge payment request to the server 110 based on the acquired seller key and purchaser key. program.

Information relating to the delivery request received from the server 110 is managed in the accepted matter DB 522 . Information on the delivery request includes information on the delivery source and information on the delivery destination. Also, when the optical detection unit 532 of the deliverer terminal 120A reads the seller code and purchaser code given to the delivery source user and the delivery destination user, the seller key and purchaser code included in the information codes are read. Keys are appended to the record from time to time.

Furthermore, when the decryption key is received from the server 110, the received decryption key may be managed in association with the information regarding the delivery request. If the seller code contains the first cipher information that encrypted the seller key and the purchaser code contains the second cipher information that encrypted the purchaser key, the optical detector 532 uses this decryption key. to decrypt the first encrypted information and the second encrypted information.

FIG. 6 schematically shows part of the data structure of the information on the delivery request stored in the accepted case DB 522. As shown in FIG.

The "delivery request ID" stores identification information for the deliverer terminal 120A to uniquely identify the delivery request. The delivery request ID stored in the accepted item DB 522 may be the same as the delivery request ID stored in the delivery request DB 332 of the server 110 .

The "delivery source" stores information necessary for collection of the package, such as the address of the user who is the delivery source. In addition, the "delivery destination" stores information necessary for delivery of the package, such as the address of the delivery destination user.

The “seller key” stores information obtained by the optical detection unit 532 reading the seller code and indicating that the deliverer has received the package from the delivery source user. In the "purchaser key", information acquired by the optical detection unit 532 reading the purchaser code, and information indicating that the delivery person has delivered the package to the delivery destination user is managed.

"Decryption key" stores information for decrypting the seller key and the purchaser key.

Next, returning to FIG. 5, the control unit 530 will be described. The control section 530 has a delivery request management section 531 and an optical detection section 532 .

The delivery request management unit 531 has a function of managing information in the accepted case DB 522 . As an example, when the receiving unit of the deliverer terminal 120A receives information on the delivery request from the server 110, the delivery request management unit 531 stores the information on the delivery request in the accepted case DB 522. Also, when the receiving unit of the deliverer terminal 120A receives the decryption key together with the delivery request, the delivery request management unit 531 stores the decryption key in the accepted case DB 522 in association with the delivery request.

Further, when the delivery request management unit 531 acquires the seller key and the purchaser key, the delivery request management unit 531 instructs the transmission unit to transmit the information to the server 110 as a payment request based on the acquired seller key and purchaser key. can give instructions to

The optical detection unit 532 has a function of reading the seller code and the purchaser code and acquiring the seller key and the purchaser key. As an example, the optical detection unit 532 that has read the seller code acquires the seller key included in the seller code, and stores it in the accepted case DB 522 . At this time, if the seller code contains the first encrypted information obtained by encrypting the seller key, the seller key is obtained by decrypting the first encrypted information using the decryption key stored in the accepted matter DB 522. can do.

(3) Functional Configuration of Seller Terminal 120B and Purchaser Terminal 120C FIG. 7 shows an example of a block diagram showing the functional configuration of the seller terminal 120B and the purchaser terminal 120C according to the first embodiment. The seller terminal 120B is an example of an information processing terminal used by a delivery source user in the transaction system 1, and the purchaser terminal 120C is an example of an information processing terminal used by a delivery destination user in the transaction system 1. The seller terminal 120</b>B and the purchaser terminal 120</b>C have an input/output I/F 711 , a communication I/F 712 , a storage section 720 and a control section 730 .

The input/output I/F 711 can be realized using the input/output I/F 204, for example. Also, the communication I/F 712 can be implemented using the communication I/F 205, for example. Storage unit 720 may be implemented using memory 202 and/or storage 203, for example. The control unit 730 can be implemented, for example, by the processor 201 reading and executing a program stored in the storage unit 720 .

The input/output I/F 721 displays a predetermined screen, and also allows the user to use the buttons displayed on the screens of the seller terminal 120B and the purchaser terminal 120C, the touch panels of the seller terminal 120B and the purchaser terminal 120C, and the like. It receives an operation and outputs information about the operation to control unit 730 .

The communication I/F 712 of the seller terminal 120B and the purchaser terminal 120C has a function as a transmission unit that transmits a delivery request to the server 110 and a delivery fee deposit request. The delivery request may be made by either the seller terminal 120B or the purchaser terminal 120C, or both. Also, the delivery charge may be deposited by only the delivery source user, only by the delivery destination user, or by both the delivery source user and the delivery destination user. The seller terminal 120B and the purchaser terminal 120C can request the server 110 to deposit the delivery charges according to these deposit modes.

Communication I/F 712 of seller terminal 120B and purchaser terminal 120C has a function as a receiving unit for receiving a seller code or a purchaser code from server 110, respectively. If the delivery request management unit 731 of the seller terminal 120B and the purchaser terminal 120C has a function of creating a seller code or a purchaser code from the seller key or the purchaser key, the seller terminal 120B and the purchaser terminal The receiving unit 120C may receive a seller key or a purchaser key instead of the seller code or purchaser code. Hereinafter, a manner in which the seller terminal 120B and the purchaser terminal 120C receive the seller code or the purchaser code from the server 110 will be described. It may be in a mode of receiving.

The storage unit 720 stores a program 721 executed by the seller terminal 120B and the purchaser terminal 120C, and a delivery request DB 732 that manages the seller code or purchaser code received from the server 110. FIG.

This program 721 is, for example, a program for making a delivery request and a delivery charge deposit request, and receiving a seller code or a purchaser code corresponding to the delivery request.

The delivery request DB 732 manages the seller code or purchaser code received from the server 110 . Also, the delivery request ID set by the server 110 may be associated with the seller code or the purchaser code and managed.

FIG. 8 schematically shows part of the data structure of the information on the delivery request stored in the delivery request DB 732 of the seller terminal 120B, and FIG. 9 shows the information on the delivery request stored in the delivery request DB 732 of the purchaser terminal 120C. Schematically shows part of the data structure of

The "delivery request ID" stores identification information for the seller terminal 120B and the purchaser terminal 120C to uniquely identify the delivery information. The delivery request ID stored in the delivery request DB 732 may be the same as the delivery request ID stored in the delivery request DB 332 of the server 110 .

The "seller code" and "purchaser code" store the seller code and the purchaser code received from the server 110, respectively. Also, in association with this, a seller key included in the seller code and a purchaser key included in the purchaser code may be stored.

Next, returning to FIG. 7, the control unit 730 will be described. The control section 730 has a delivery request management section 731 and an information code display section 732 .

The delivery request management section 731 of the seller terminal 120B and the purchaser terminal 120C has a function of managing information in the delivery request DB 722. FIG. As an example, when the receiving units of the seller terminal 120B and the purchaser terminal 120C receive the seller code or purchaser code from the server 110, the delivery request management unit 731 sends the seller code or purchaser code to each It is stored in the acceptance matter DB 522 of the terminal.

The information code display unit 732 of the seller terminal 120B and the purchaser terminal 120C has a function of displaying the seller code or the purchaser code on the screens of the seller terminal 120B and the purchaser terminal 120C.

Also, if the optical detection unit 1332 of the deliverer terminal 120A can take more, the information code need not be displayed on the screen of the terminal. For example, the seller terminal 120B and the purchaser terminal 120C may have a printing section for printing the seller code or the purchaser code on paper or the like instead of the information code display section 732 .

As a result, for example, by pasting a piece of paper on which a purchaser code is printed to a delivery box provided at the delivery destination, the deliverer can store the package in the delivery box even if the delivery user cannot face the delivery destination user directly. At the same time, the purchaser key can be acquired.

<Transaction system operation processing of the first embodiment>
Processing of the program according to the first embodiment will be described with reference to FIG. FIG. 10 shows an example of a sequence diagram showing processing performed by the trading system 1 in the first embodiment. Note that the processing procedure described below is merely an example, and each processing may be modified as much as possible within the scope of the technical concept of the present disclosure, and steps may be omitted, replaced, and added as appropriate. be.

(Processing to notify the information code)
In step S1001 shown in FIG. 10, delivery request management section 731 of seller terminal 120B instructs the transmission section of seller terminal 120B to send a delivery request to server 110 in response to a user operation. Note that the delivery request management unit 731 of the purchaser terminal 120C can also transmit a delivery request to the server 110 without being limited to this.

Further, in step S1001, the delivery request management unit 731 of the seller terminal 120B can perform processing of depositing the delivery charge to the server 110 or an external system with which the server 110 cooperates according to the user's operation. Here, the delivery fee can be deposited with electronic money (or electronic value) owned by the user, savings in a bank account, points that can be used in an electronic commerce system, or the like.

By depositing the delivery charge in advance in this manner, it is possible to avoid a situation in which the delivery charge is not paid to the deliverer even though the delivery has been made.

In step S<b>1002 , the delivery request management unit 331 of the server 110 adds an ID to the received delivery request and stores it in the delivery request DB 322 of the server 110 .

In step S<b>1003 , the delivery request management unit 331 of the server 110 sets a seller key and a purchaser key for the stored delivery request ID, and stores them in the delivery request DB 322 . At this time, an expiration date may be set for each of the seller code and the purchaser code.

At this time, in step S1004, the delivery request management unit 331 of the server 110 sets the encryption key and decryption key for encrypting and decrypting the seller key and the purchaser key as necessary, and sends the delivery request. You may memorize|store in DB322. In this case, the delivery request management section 331 of the server 110 may store the first encrypted information and the second encrypted information obtained by encrypting the seller key and the purchaser key with the encryption key in the delivery request DB 322 .

In steps S1005 and S1006, the delivery request management unit 331 of the server 110 sends a seller code including a seller key and a purchaser The transmitter of the server 110 is instructed to notify the purchaser code including the key.

Further, when the encryption key and the decryption key are set in step S1004, in steps S1005 and S1006, the delivery request management unit 331 of the server 110 sends the first encryption information to the seller terminal 120B and the purchaser terminal 120C. and the purchaser code including the second encryption information.

In step S1007, the delivery request management unit 331 of the server 110 instructs the transmission unit of the server 110 to notify the deliverer terminal 120A (deliverer) of the information regarding the delivery request. At this time, when the encryption key and the decryption key are set in step S1004, in step S1007, the delivery request management unit 331 of the server 110 instructs the transmission unit of the server 110 to notify the decryption key to the deliverer terminal 120A. You can also give instructions to

(Processing to acquire seller key and purchaser key)
In step S1008, when the deliverer visits the delivery source user to pick up the package, the optical detection unit 532 of the deliverer terminal 120A detects the sales information displayed on the screen of the seller terminal 120B by the delivery source user. Scan the Merchant Code to get the Merchant Key. Then, the optical detection unit 532 of the deliverer terminal 120A stores the acquired seller key in the accepted matter DB 522 of the deliverer terminal 120A.

At this time, if the information included in the seller code is the first encrypted information, the optical detection unit 532 obtains the seller key by performing decryption using the decryption key stored in the accepted matter DB 522. can be done. The seller code is not limited to being displayed on the screen of the seller terminal 120B, and may be attached as a sticker to the package. In this case, the seller can deposit the package in advance at a predetermined pickup location such as a convenience store. This prevents the seller's address from being known to the deliverer. In the case of this configuration, it is preferable that the address of the pickup location, not the address of the deliverer, is registered as the information of the delivery source.

In step S1009, when the deliverer visits the delivery destination user to receive the package, the optical detection unit 532 of the deliverer terminal 120A detects the purchase price displayed on the screen of the purchaser terminal 120C by the delivery destination user. Read the purchaser code and get the purchaser key. Then, the optical detection unit 532 of the deliverer terminal 120A stores the acquired purchaser key in the accepted matter DB 522 of the deliverer terminal 120A.

At this time, if the information included in the purchaser code is the second encrypted information, the optical detection unit 532 obtains the purchaser key by decrypting using the decryption key stored in the accepted matter DB 522. can be done. The purchaser code is not limited to being displayed on the screen of the purchaser terminal 120C, and may be attached as a sticker to a delivery box or the like. In this case, even if the purchaser is absent, the delivery person can receive the delivery charge by delivering the package to the home delivery box.

When the information code contains encrypted information in this way, only the deliverer who has the decryption key can acquire the seller key and the purchaser key. Therefore, delivery reliability can be further improved. More specifically, it is possible to prevent a person who does not have a decryption key from fraudulently obtaining a shipping charge by reading information codes at random.

(Processing regarding requests for payment of shipping charges)
In step S1010, the delivery request management unit 531 of the deliverer terminal 120A instructs the transmission unit of the deliverer terminal 120A to transmit the acquired seller key and purchaser key to the server 110 together with a delivery charge payment request. instruct.

In step S<b>1011 , the settlement processing unit 332 of the server 110 checks the received seller key and purchaser key with the information stored in the accepted matter DB 522 . Then, when it is confirmed that the received seller key and purchaser key are the seller key and purchaser key corresponding to the specific delivery request ID, the settlement processing unit 332 of the server 110 performs the predetermined distribution. Processing of paying the shipping fee to the deliverer who owns the deliverer terminal 120A is performed.

If the delivery charge has not been deposited in step S1001, the settlement processing unit 332 of the server 110 instructs the seller terminal 120B and/or the purchaser terminal 120C to pay the delivery charge to the deliverer. request that

As a result, when the deliverer acquires predetermined information from the delivery source user and the delivery destination user, the payment of the deposited delivery charge is executed. Therefore, from the perspective of a person who requests delivery (for example, a delivery source user or a delivery destination user), for example, the delivery person receives the delivery fee and does not deliver, or the delivery person runs away with the package to be delivered. It is possible to suppress the occurrence of such a situation and realize a highly reliable delivery method.

<Modified Example of First Embodiment>
According to a modification of the first embodiment, in the transaction system 1 intended to collect goods, when the encrypted information contained in the information code given to the collection destination user is acquired and the encrypted information is decrypted, This is an embodiment that makes it possible to pay a collection fee to a collection person.

In the program, information processing terminal, and information processing method according to the modification of the first embodiment, the predetermined information processing device gives the information code to the collection destination user and the decryption key to the collection person for each collection request. Then, the recoverer decrypts the encrypted information included in the information code given to the recovery destination user with the decryption key, and transmits the encrypted information to a predetermined information processing device.

In this transaction system 1, for example, a collector terminal 120A owned by a collector, a client terminal 120B owned by a collection destination user, and a server 110 for managing information codes are connected via a network 130. FIG.

For the purpose of explanation, assuming a transaction system for the purpose of collecting articles such as oversized garbage, the terminal used by the person who received the collection request is used by the collector terminal 120A and the collection destination user (requester). The terminal is explained as the client terminal 120B. However, the modified example of the first embodiment is not limited to this.

<Effect of Modification of First Embodiment>
According to this modified example of the first embodiment, by transmitting the decryption information together with the collection fee payment request, it is confirmed whether or not the collection request has been properly fulfilled, and the collection fee is paid. Therefore, for example, the collection person cannot receive the collection fee unless he/she obtains the encryption information by collecting the article from the collection destination user who has the encryption information corresponding to the decryption key and decrypts it. As a result, it is possible to prevent situations in which the collector receives the collection fee and does not collect the item, or in which the collector himself/herself collects the item unrelated to the collection request received and unfairly obtains the collection fee. Therefore, a highly reliable recovery method can be realized.

<Functional Configuration of Modified Example of First Embodiment>
The functional configurations of the server 110, collection party terminal 120A, and client terminal 120B will be described with reference to FIGS. 11 to 16. FIG. Each functional unit disclosed in FIGS. 11, 13, and 15 is realized by cooperation of a processor 201, a memory 202, a storage 203, an input/output I/F 204, and a communication I/F 205 provided in the information processing apparatus 200. be done.

(1) Functional Configuration of Server 110 FIG. 11 shows an example of a block diagram showing the functional configuration of the server 110 according to the modification of the first embodiment. The server 110 issues an information code in response to a collection request in the trading system 1, and performs settlement processing in response to receiving decrypted information obtained by decrypting the encrypted information included in the information code with an appropriate decryption key. It is an example of an information processing terminal. The server 110 has an input/output I/F 1111 , a communication I/F 1112 , a storage section 1120 and a control section 1130 .

The input/output I/F 1111 can be implemented using the input/output I/F 204, for example. Also, the communication I/F 1112 can be implemented using the communication I/F 205, for example. The storage unit 1120 can be implemented using the memory 202 and/or the storage 203, for example. The control unit 1130 can be implemented, for example, by the processor 201 reading and executing a program stored in the storage unit 1120 .

The storage unit 1120 also stores a program 1121 executed by the server 110 according to this embodiment, and a collection request DB 1132 that manages information on received collection requests.

This program 1121, for example, issues an information code in response to a collection request, and performs payment processing in response to receiving decryption information obtained by decrypting the encrypted information included in the information code with an appropriate decryption key. program. The program 1121 may be recorded in a computer-readable recording medium, and may be installed in the computer from this recording medium.

The collection request DB 1132 manages information related to collection requests received from the client terminal 120B. Information related to the collection request includes, for example, the ID assigned to each collection request, the information code assigned to the collection destination, the cipher information included in the information code, the composite information obtained by decrypting the cipher information, the encryption key, and the decryption key. is mentioned. Also, information about the collection destination may be managed in association with the ID of the collection request.

FIG. 12 schematically shows part of the data structure of the collection request information stored in the collection request DB 1132. As shown in FIG.

“Collection request ID” stores identification information for the server 110 to uniquely identify the collection request. When the reception unit of the server 110 receives a collection request from the client terminal 120B, the collection request management unit 1131 of the server 110 assigns an ID to the collection request and instructs it to be stored in the collection request DB 1132. can be done.

"Information code" stores, for example, a two-dimensional code such as a bar code or a QR code that is converted from encrypted information. Here, the two-dimensional code refers to a code that can be converted by an optical detection device into an electrical signal based on a predetermined method based on the reflection of irradiated light, and that can be converted into a corresponding computer code.

Also, the information code is not limited to a two-dimensional code such as a bar code or a QR code, and a form suitable for exchanging information between terminals can be used. For example, a code suitable for infrared communication or wireless communication such as Bluetooth may be used.

It should be noted that if the conversion method from the encrypted information to the information code is determined in advance, the recovery request DB 1132 may store only the encrypted information without storing the information code.

In such a mode, for example, the transmission unit of the server 110 can transmit the encrypted information to the client terminal 120B as it is, and the information code display unit 1532 of the client terminal 120B can convert it into an information code. Further, when the transmission unit of the server 110 transmits the encrypted information to the client terminal 120B, it can be transmitted after being converted into an information code based on a predetermined method.

The "encryption information" stores information contained in the information code and obtained by the recovery person from the recovery destination user by reading the information code. The encrypted information is information obtained by encrypting the decrypted information with an encryption key.

Since the encrypted information is information that can be created from the composite information and the encryption key, the recovery request DB 1132 may store only the composite information and the encryption key without storing the encrypted information.

In such a mode, for example, when the transmitting unit of the server 110 transmits encrypted information to the client terminal 120B, the decryption information is converted into encrypted information using the encryption key, and the encrypted information is further converted into an information code. You can also send it later.

The "decryption information" is information obtained by the collector by decrypting the encrypted information with the decryption key. Information indicating that the

The "encryption key" stores information for encrypting the decryption information, and the "decryption key" stores information for decrypting the encryption information. The "encryption key" and "decryption key" are preferably set individually for each collection request ID. As a result, it is possible to avoid illegal decryption of encrypted information associated with a plurality of collection request IDs with one decryption key.

Next, returning to FIG. 11, the control unit 1130 will be described. The control unit 1130 has a collection request management unit 1131 and a settlement processing unit 1132 .

The communication I/F 1112 has a function as a receiving unit that receives a collection request from the client terminal 120B, and receives a collection fee payment request and decryption information from the collector terminal 120A.

Further, the communication I/F 1112 has a function as a transmission unit for transmitting an information code to the requester terminal 120B and transmitting information on the collection request and a decryption key to the collection person terminal 120A.

These functional configurations are realized by the processor 201 reading and executing the program 1121 stored in the storage unit 1120 . In addition, the functional configuration realized by the server 110 may be appropriately omitted, replaced, or added according to the embodiment or example.

The collection request management unit 1131 has a function of managing information in the collection request DB 1122 . As an example, when the receiving unit of the server 110 receives a collection request from the client terminal 120B, the collection request management unit 1131 attaches a collection request ID for uniquely identifying the collection request, is stored in the collection request DB 1122. The collection request management unit 1131 also sets decryption information for each collection request ID, sets an encryption key and a decryption key, and stores them in the collection request DB 1122 .

At this time, the collection request management unit 1131 can also store collection information about the collection destination and information about the collection person in association with the generated collection request ID.

Further, when the recovery request management unit 1131 sets the decryption information corresponding to the recovery request ID, the collection request management unit 1131 instructs the transmission unit to transmit the encryption information obtained by encrypting the decryption information with the encryption key to the requester terminal 120B. can give instructions.

The settlement processing unit 1132 performs various processes for executing settlement of the collection fee. As an example, the settlement processing unit 332 receives a deposit request for depositing the collection fee from the collection destination user along with the collection request, and executes deposit processing based on the received deposit request. Then, when receiving a collection charge payment request together with the decryption information from the collection person, the settlement processing for paying the deposited collection charge to the collection person is executed.

(2) Functional configuration of recovery party terminal 120A FIG. 13 shows an example of a block diagram showing the functional configuration of the recovery party terminal 120A according to the modification of the first embodiment. The collection party terminal 120A is an example of an information processing terminal used by the collection party in the transaction system 1 . The recovery person terminal 120A has an input/output I/F 1311 , a communication I/F 1312 , a storage section 1320 and a control section 1330 .

The input/output I/F 1311 can be implemented using the input/output I/F 204, for example. Also, the communication I/F 1312 can be implemented using the communication I/F 205, for example. Storage unit 1320 can be implemented using memory 202 and/or storage 203, for example. The control unit 1330 can be implemented, for example, by the processor 201 reading and executing a program stored in the storage unit 1320 .

The input/output I/F 1321 displays a predetermined screen, receives user operations using buttons displayed on the screen of the recovery party terminal 120A, the touch panel of the recovery party terminal 120A, and controls information related to the operations. Output to unit 1330 .

The communication I/F 1312 of the recovery person terminal 120A has a function as a receiving unit that receives information on the recovery request and the decryption key from the server 110. FIG. Further, the communication I/F 1312 of the recovery party terminal 120A has a function as a transmission unit that transmits the recovery charge payment request and the decryption information to the server 110 .

Storage unit 1320 stores program 1321 executed by collector terminal 120A and collection request DB 1332 for managing information on collection requests received from server 110 .

This program 1321 is, for example, a program for acquiring encrypted information from a collection destination user, acquiring decryption information from the encrypted information using a decryption key, and transmitting the acquired decryption information together with a collection fee payment request to the server 110. is.

The collection request DB 1332 manages information on collection requests received from the server 110 and decryption keys. Information about the collection request includes a collection request ID and information about the collection destination. Further, when the optical detection unit 532 of the recoverer terminal 120A reads the information code given to the recovery destination user, the encrypted information included in the information code is stored, and the encrypted information is decrypted with the decryption key. Decryption information is also stored.

FIG. 14 schematically shows part of the data structure of the collection request information stored in the collection request DB 1332. As shown in FIG.

The "recovery request ID" stores identification information for the recoverer terminal 120A to uniquely identify the recovery information. The collection request ID stored in the collection request DB 1332 may be the same as the collection request ID stored in the collection request DB 332 of the server 110 .

The "collection destination" stores information necessary for collection of articles, such as the address of the collection destination user. According to the information, the collector goes to the collection destination and collects the target article.

“Encrypted information” stores encrypted information acquired by the optical detection unit 1332 reading the information code. Further, the “decryption information” stores decryption information obtained by decrypting the encrypted information by the optical detection unit 1332 using the decryption key stored in the collection request DB 1332 .

The “decryption key” stores the decryption key received from the server 110 .

Next, returning to FIG. 13, the control unit 1330 will be described. The control section 1330 has a collection request management section 1331 and an optical detection section 1332 .

The collection request management unit 1331 has a function of managing information in the collection request DB 1322 . As an example, when the receiving unit of the recovery person terminal 120A receives the information regarding the collection request and the decryption key from the server 110, the collection request management unit 1331 stores the information regarding the collection request and the decryption key in the collection request DB 522. .

The optical detection unit 1332 has a function of creating decryption information from the information code and instructing the transmission unit to transmit the created decryption information to the server 110 . As an example, the optical detection unit 532 acquires encrypted information contained in the information code by reading the information code displayed on the screen of the client terminal 120B. Then, the optical detection unit 1332 decrypts the obtained encrypted information with the decryption key stored in the collection request DB 1322 and obtains the decrypted information. The optical detector 1332 instructs the transmitter to transmit the obtained decryption information to the server 110 . The optical detection unit 1332 can also cause the collection request management unit 1331 to store the encryption information and the decryption information.

(3) Functional Configuration of Client Terminal 120B FIG. 15 shows an example of a block diagram showing the functional configuration of the client terminal 120B according to the first embodiment. The requester terminal 120B is an example of an information processing terminal used by a user (collection destination user) who makes a collection request in the transaction system 1 . Client terminal 120</b>B has input/output I/F 1511 , communication I/F 1512 , storage unit 1520 , and control unit 1530 .

The input/output I/F 1511 can be realized using the input/output I/F 204, for example. Also, the communication I/F 1512 can be implemented using the communication I/F 205, for example. Storage unit 1520 can be implemented using memory 202 and/or storage 203, for example. The control unit 1530 can be realized, for example, by the processor 201 reading and executing a program stored in the storage unit 1520 .

The input/output I/F 1521 displays a predetermined screen, receives user operations using buttons displayed on the screen of the client terminal 120B, the touch panel of the client terminal 120B, or the like, and controls information related to the operations. Output to unit 1530 .

The communication I/F 1512 of the client terminal 120B has a function as a transmission unit that transmits a collection request to the server 110 and a collection fee deposit request.

Also, the communication I/F 1512 of the client terminal 120B has a function as a receiving section for receiving the information code from the server 110. FIG. If the collection request management unit 1531 of the client terminal 120B has a function of creating an information code from encrypted information, the receiving unit of the client terminal 120B may receive encrypted information instead of the information code. A mode in which the client terminal 120B receives the information code from the server 110 will be described below, but a mode in which encrypted information is received instead of the information code is also possible.

Storage unit 1520 stores program 1521 executed by client terminal 120B and collection request DB 1532 for managing information codes received from server 110 .

This program 1521 is, for example, a program for making a collection request and collection fee deposit request, receiving an information code corresponding to the collection request, and presenting the information code to the collection person terminal 120A.

Information codes received from the server 110 are managed in the collection request DB 1532 . Also, the collection request ID set by the server 110 may be associated with the information code and managed. FIG. 16 schematically shows part of the data structure of the collection request information stored in the collection request DB 1532 of the client terminal 120B.

The "recovery request ID" stores identification information for the requester terminal 120B to uniquely identify the recovery information. The collection request ID stored in the collection request DB 1532 may be the same as the collection request ID stored in the collection request DB 1132 of the server 110 .

The information code received from the server 110 is stored in the "information code". Also, the encryption information included in the information code may be stored in association with this.

Next, returning to FIG. 15, the control unit 1530 will be described. The control unit 1530 has a collection request management unit 1531 and an information code display unit 1532 .

The collection request management unit 1531 of the client terminal 120B has a function of managing information in the collection request DB 1522. FIG. As an example, when the receiving unit of client terminal 120B receives an information code from server 110, collection request management unit 1531 stores the information code in collection request DB 1522. FIG.

The information code display unit 1532 of the client terminal 120B has a function of displaying the information code on the screen of the client terminal 120B.

In addition, if the optical detection unit 1332 of the recovery person terminal 120A can detect more, the information code need not be displayed on the screen of the terminal. For example, the client terminal 120B may have a printing section for printing the information code on paper or the like instead of the information code display section 1532 .

As a result, for example, by pasting a piece of paper on which an information code is printed to a home delivery box provided at the collection destination, the collection person can store the package in the home delivery box even if he/she cannot face the collection destination user directly. You can get the information key with

<Transaction system operation processing of the modification of the first embodiment>
Processing of the program according to the modification of the first embodiment will be described with reference to FIG. FIG. 17 shows an example of a sequence diagram showing processing performed by the transaction system 1 in the modified example of the first embodiment. Note that the processing procedure described below is merely an example, and each processing may be modified as much as possible within the scope of the technical concept of the present disclosure, and steps may be omitted, replaced, and added as appropriate. be.

(Processing to notify the information code)
In step S1701 shown in FIG. 17, the collection request management unit 1531 of the requester terminal 120B instructs the transmission unit of the requester terminal 120B to transmit a collection request and collection fee deposit request to the server 110 in accordance with a user operation. give instructions to

In step S<b>1702 , the collection request management unit 1131 of the server 110 adds an ID to the received collection request and stores it in the collection request DB 1122 of the server 110 . Decryption information is set for the stored collection request ID (S1703), and an encryption key and a decryption key are set (S1704).

In step S1705, the collection request management unit 1131 of the server 110 creates encrypted information by encrypting the decryption information using the encryption key, and sends an information code including encrypted information to the client terminal 120B (collection destination user). is instructed to the transmission unit of the server 110 to notify the

In step S1706, the collection request management unit 1131 of the server 110 instructs the transmission unit of the server 110 to notify the collection request information and the decryption key to the collection person terminal 120A (collector).

(Processing to acquire encryption information)
In step S1707, when the recovery person visits the recovery destination user to collect the articles, the optical detection unit 1332 of the recovery person terminal 120A detects the information displayed on the screen of the requester terminal 120B by the recovery destination user. Read the code and get the cryptographic information. Then, the optical detection unit 1332 of the recovery party terminal 120A stores the acquired encrypted information in the recovery request DB 522 of the recovery party terminal 120A.

In step S1708, the optical detection unit 532 decrypts the encrypted information using the decryption key stored in the collection request DB 522 and creates decrypted information.

(Processing related to collection fee payment requests)
In step S179, the collection request management section 531 of the collection party terminal 120A instructs the transmission section of the collection party terminal 120A to transmit the acquired decryption information to the server 110 together with the collection charge payment request.

In step S1710, in response to the collection fee payment request, the settlement processing unit 332 of the server 110 pays the collected collection fee to the user who owns the collection terminal 120A.

As a result, when the collection fee is deposited in advance and the encrypted information possessed by the collection destination user can be decrypted with the decryption key possessed by the collection party, the deposited collection fee can be paid. Therefore, from the point of view of the person requesting collection, for example, there may be a situation where the collector receives the collection fee and does not collect, or a situation where the collector collects items that are not related to the collection request and obtains the collection fee. Generation can be suppressed, and a highly reliable recovery method can be realized. In addition, since the collector receives the collected collection fee, it is possible to avoid a situation in which the collection fee is not paid even though the money has been collected.

<Second embodiment>
The second embodiment is an example in which the payment of the delivery charge to the delivery person is executed using the virtual asset transaction information (second transaction information). In this modification, the seller key and purchaser key of the first embodiment are used as the seller key and purchaser key for electronically signing the second transaction information.

In the program, information processing terminal, and information processing method according to the second embodiment, the deliverer collects the seller key and the purchaser key from the delivery source user and the delivery destination user, and uses them to calculate the delivery charge. Generate transaction information for

More specifically, first, the seller or the purchaser sends a virtual asset corresponding to the shipping charge (hereinafter, the virtual asset corresponding to the shipping charge is simply referred to as "delivery charge") to the shipper. create transaction information for The virtual asset remitted with this transaction information is controlled so that it can be used only when predetermined conditions are met. Specifically, the virtual assets transferred with this transaction information are controlled so as to be unlocked by signatures of the seller key, the purchaser key, and the delivery person's private key.

In this trading system 1, for example, a deliverer terminal 120A owned by a deliverer, a seller terminal 120B owned by a delivery source user, and a purchaser terminal 120C owned by a delivery destination user are connected via a network .

Hereinafter, assuming an electronic commerce platform for explanation, the terminal used by the individual who received the delivery request is the deliverer terminal 120A, the terminal used by the delivery source user (seller) is the seller terminal 120B, and the delivery destination user The terminal used by the (purchaser) will be described as a purchaser terminal 120C. However, the second embodiment is not limited to this.

<Effects of Second Embodiment>
According to the second embodiment, in addition to improving the reliability of delivery in the first embodiment, the delivery source user and/or the delivery destination user can pay the delivery fee with virtual assets, and the delivery person can It is possible to receive payment for delivery charges using virtual assets.

In the second embodiment, the processing performed by the server 110 in the first embodiment can be replaced by a blockchain network, and the server 110 can be made unnecessary.

<Functional configuration of the second embodiment>
In the following description, the same reference numerals are assigned to the functional configurations similar to those of the first embodiment, and the description thereof is omitted. Further, the description of the same actions and effects as those of the first embodiment is also omitted. The following description will focus on differences from the first embodiment.

FIG. 18 shows an example of a block diagram showing the functional configuration of the deliverer terminal 120A according to the second embodiment. Also, FIG. 19 shows an example of a block diagram showing the functional configuration of the seller terminal 120B and purchaser terminal 120C according to the second embodiment. In the second embodiment, the deliverer terminal 120A, the seller terminal 120B, and the purchaser terminal 120C have transaction information DBs 1823 and 1923 in the storage section in addition to the functional configuration described in the first embodiment, and the control section It has transaction information creation units 1833 and 1933 .

Transaction information DBs 1823 and 1923 manage, for example, information related to transaction information transmitted to the blockchain network.

FIG. 20 is a diagram schematically showing the structure of transaction information in the second embodiment. The transaction information describes the conditions under which the user who created the transaction information allows the virtual asset to be used by the destination user.

In the following example, it is assumed that the seller pays the delivery charge, but the delivery charge is not limited to this, and the purchaser may pay the delivery charge. In FIG. 20, transaction information T01 is transaction information for remittance of the delivery charge from the seller to the deliverer, and transaction information T02 is transaction for the deliverer to release (use) the remitted delivery charge. Information.

Transaction information includes inputs and outputs. The output specifies, for example, the remittance amount and unlocking conditions. The unlocking condition is a condition required when using the virtual asset to be remitted this time with other transaction information. Note that an output that has not yet been referred to by an input of another transaction information among the outputs created by certain transaction information is also called UTXO.

The transaction information input includes information indicating the UTXO to be used this time (for example, a pointer) and UTXO release conditions. A release condition is a condition for using a UTXO and corresponds to an unlocking condition specified in the output of transaction information to which the UTXO was sent.

Here, in the transaction information T01, information referring to the UTXO from which the purchaser received the virtual asset corresponding to the delivery fee to be remitted this time as input, and the release condition corresponding to the unlocking condition specified by the UTXO (in this example, Seller's signature and public key) are specified. In addition, the amount of the shipping fee and the following two conditions are specified as unlocking conditions in the output.

Unlocking condition 1: Hash value of seller key, hash value of purchaser key, and hash value of public key of delivery person Unlocking condition 2: Predetermined elapsed time and delivery fee person) public key hash value

If the hash value of a certain user's data (value) is specified as the unlocking condition, the unlocking condition specified in the input of the transaction information that references the UTXO is the data that is the basis of the hash value. (value). Furthermore, when the hash value of the public key is designated as the unlocking condition, the unlocking condition is the signature of the public key and the private key corresponding to the public key.

The transaction information T02 contains a pointer to the output (UTXO) of the transaction information T01 as an input, and unlocking conditions corresponding to the unlocking conditions specified by the UTXO (in this example, a seller key, a purchaser key, a delivery person and the public key of the sender) are specified. In addition, as an output, the amount of money to be remitted out of the received delivery charge and unlocking conditions (a hash value of the delivery person's public key) are specified. The unlocking conditions are not limited to those shown in FIG. 20, and may be arbitrary conditions specified by the deliverer. Also. The transaction information T02 may include multiple outputs, and may specify different unlocking conditions for each output.

In this way, the delivery person acquires the seller key and the purchaser key within the predetermined period specified by the unlocking condition 2 in the output of the transaction information T01, and creates the transaction information T02. The shipper can obtain the shipping charges. Furthermore, in the transaction information T01 for remittance of the delivery charge, by designating a predetermined elapsed time as an unlocking condition for the output and a condition that the user who has paid the delivery charge can release (his own signature and public key), , if the transaction information specifying the unlocking condition corresponding to the unlocking condition 1 is not transmitted on the blockchain network within the predetermined elapsed time determined by the unlocking condition 2, the user who paid the delivery fee The relevant shipping charges can be refunded.

Transaction information creating units 1833 and 1933 have a function of creating transaction information for moving virtual assets. The transaction information created by the transaction information creating units 1833 and 1933 includes, for example, the transaction information shown in FIG.

<Transaction system operation processing of the second embodiment>
Processing of the program according to the second embodiment will be described with reference to FIG. FIG. 21 shows an example of a sequence diagram showing processing performed by the trading system 1 in the second embodiment. Note that the processing procedure described below is merely an example, and each processing may be modified as much as possible within the scope of the technical concept of the present disclosure, and steps may be omitted, replaced, and added as appropriate. be.

(Processing to confirm delivery request and deposit)
In step S1801, delivery request management section 731 of seller terminal 120B instructs the transmission section of seller terminal 120B to send a delivery request to deliverer terminal 120A in response to a user operation. Note that the delivery request management unit 731 of the purchaser terminal 120C can also transmit a delivery request to the deliverer terminal 120A without being limited to this. Further, when using the server 110 that manages the delivery person for each delivery request, the configuration may be such that the delivery request is made to the server 110 .

In step S1802, the transaction information creation unit 1933 of the seller terminal 120B creates transaction information T01 for remittance of the delivery charge to the delivery person according to the user's operation.

The transaction information T01 specifies unlocking conditions for the output generated by the transaction information T01. For example, when specifying a seller key and a purchaser key as unlocking conditions, it is preferable that the receiver of seller terminal 120B acquires the purchaser key from purchaser terminal 120C in advance.

In step S1803, the transaction information creating unit 1933 of the seller terminal 120B instructs the communication I/F 712 to transmit the created transaction information T01 to the blockchain network. Then, in step S1804, the receiver of the deliverer terminal 120A receives the transaction information T01 from the blockchain network. Thereby, the delivery person confirms that the delivery charge has been remitted under conditions that can be released by the delivery person.

The transaction information T01 may be created by the transaction information creation unit 1933 of the purchaser terminal 120C and transmitted to the blockchain network.

(Processing to acquire seller key and purchaser key)
The process of acquiring the seller key and purchaser key can be performed in the same manner as in the first embodiment.

For example, in step S1805, when the deliverer visits the delivery source user to pick up the parcel, the optical detection unit 532 of the delivery source user terminal 120A causes the delivery source user to display on the screen of the seller terminal 120B. Read the Merchant Code and get the Merchant Key. Then, the optical detection unit 532 of the deliverer terminal 120A stores the acquired seller key in the accepted matter DB 522 of the deliverer terminal 120A.

Also, in step S1806, when the deliverer visits the delivery destination user to deliver the package, the optical detection unit 532 of the deliverer terminal 120A causes the delivery destination user to display on the screen of the purchaser terminal 120C. Read the purchased purchaser code and acquire the purchaser key. Then, the optical detection unit 532 of the deliverer terminal 120A stores the acquired purchaser key in the accepted matter DB 522 of the deliverer terminal 120A.

(Processing related to payment of shipping charges)
In step S1807, the transaction information creation unit 1833 of the deliverer terminal 120A creates transaction information T02 using the seller key and the purchaser key. Furthermore, in step S1807, the deliverer terminal 120A instructs the communication I/F to transmit the created transaction information T02 to the blockchain network. As a result, the output of the transaction information T01 is released, and the delivery person can freely use the delivery charge.

On the other hand, if the transaction information T02 is not sent to the blockchain network by the elapsed time specified as the unlocking condition in the output of the transaction information T01, the delivery person uses the delivery fee remitted in the transaction information T01. become unable. In this case, the seller (the user who paid the delivery charge) can freely use the virtual asset corresponding to the delivery charge.

<Modification of Second Embodiment>
A modified example of the second embodiment is an example in which payment of a collection fee to a collection person is executed based on virtual asset transaction information (second transaction information).

In the following description, the same reference numerals are assigned to the functional configurations similar to those of the second embodiment, and the description thereof is omitted. Further, the description of the same functions and effects as those of the second embodiment will be omitted. The following description focuses on differences from the second embodiment.

In this modification, the collection party terminal 120A and client terminal 120B have the functional configuration shown in FIGS. 18 and 19. FIG.

FIG. 22 is a diagram schematically showing the structure of transaction information in this modified example. In FIG. 22, transaction information T03 is transaction information for remittance of the collection fee from the garbage collection requester to the collection person, and transaction information T04 is for the collection person to release (use) the remitted collection fee. It is transaction information for The differences in the structure of the transaction information in the second embodiment will be mainly described with reference to FIG. 22 .

In the transaction information T03, information referring to the UTXO from which the requester received the virtual asset corresponding to the collection fee to be remitted this time as input, and the release condition corresponding to the unlocking condition specified by the UTXO (in this example, the requester's signature and public key) are specified. In addition, the amount of collection fee and the following two conditions are specified as unlocking conditions in the output.

Unlocking condition 1: Hash value of information key and hash value of public key of recovery person Unlocking condition 2: Predetermined elapsed time and hash value of public key of user (in this example, client) who paid recovery fee

In the transaction information T04, the input is a pointer to the output (UTXO) of the transaction information T03, and the release condition corresponding to the unlocking condition specified by the UTXO (in this example, the information key and the public key of the collector) is specified. Also, as an output, the amount of the received collection fee to be remitted and the unlocking condition (hash value of the collector's public key) are specified. The unlocking conditions of the transaction information T04 are not limited to those shown in FIG. 22, and may be arbitrary specified by the collector. Moreover, the transaction information T04 may include a plurality of outputs, and different unlocking conditions may be specified for each output.

In this way, the collector obtains the information key and creates the transaction information T04 within the predetermined period specified by the unlocking condition 2 in the output of the transaction information T04. can be obtained. Furthermore, in the transaction information T03 for remittance of the collection fee, by designating a predetermined elapsed time as an unlocking condition for the output and a condition (own signature and public key) that can be released by the user who has paid the collection fee, , If the transaction information specifying the unlocking condition corresponding to unlocking condition 1 is not sent on the blockchain network within the predetermined elapsed time specified in unlocking condition 2, the requester will be charged a collection fee. can be refunded.

<Trading System Operation Processing of Modified Example of Second Embodiment>
Processing of the program according to the modification of the second embodiment will be described with reference to FIG. FIG. 23 shows an example of a sequence diagram showing processing performed by the transaction system 1 in the second embodiment. Note that the processing procedure described below is merely an example, and each processing may be modified as much as possible within the scope of the technical concept of the present disclosure, and steps may be omitted, replaced, and added as appropriate. be.

(Processing to confirm collection request and transaction information)
In step S2301, the collection request management unit 1531 of the requester terminal 120B instructs the transmission unit of the requester terminal 120B to transmit the collection request to the collection requester terminal 120A in accordance with the user's operation. If the server 110 that manages the collection person for each collection request is used, the collection request may be sent to the server 110 .

In steps S2302 and S2303, the transaction information creation unit 1933 of the requester terminal 120B creates transaction information T03 for transferring a predetermined virtual asset (collection fee) according to the user's operation, and transmits it to the blockchain network. Then, in step S2304, the receiving unit of the recovery person terminal 120A receives the transaction information T03 from the blockchain network.

(Processing to acquire information key)
The process of acquiring the information key can be performed in the same manner as in the second embodiment. For example, in step S2305, when the recovery person visits the recovery source user to pick up the article, the optical detection unit 1332 of the recovery source user terminal 120A causes the recovery source user to display the item on the screen of the client terminal 120B. read the information code and obtain the information key. Then, the optical detection unit 1332 of the recovery party terminal 120A stores the acquired information key in the recovery request DB 1322 of the recovery party terminal 120A.

(Processing related to payment of collection fees)
In step S2306, the transaction information creation unit 1833 of the collection party terminal 120A creates transaction information T04 using the information key. Furthermore, in step S2307, the collection party terminal 120A instructs the communication I/F to transmit the created transaction information T04 to the blockchain network. As a result, the output of the transaction information T03 is released, and the collector can freely use the collection fee.

As described above, the present invention is not limited to the above-described embodiments and examples, and various modifications are possible without departing from the gist of the present invention. In other words, the above-described embodiment is merely an example in all respects, and should not be construed as being limited.

For example, if the collection request in the second embodiment is such that a predetermined person goes to the requester and reads the information code to receive payment for the requested item, It is not limited to collection requests. An example of this is a drop-off service in which a delivery company leaves the product at the front door. In the case of the storage service, the delivery company delivers the product to a predetermined location such as in front of the client's entrance, and reads an information code such as a QR code installed at the predetermined location. As a result, it is possible to obtain compensation for the completed delivery.

Also, for example, a common key may be used in place of the private key, and if the blockchain network is a network in which information about the blockchain is distributed and shared among nodes, the communication means does not necessarily follow the P2P communication protocol. Absent.

Reference Signs List 1 transaction system 110, 110A, 110B server 120 terminal 120A delivery person terminal 120B seller terminal 120C purchaser terminal 120X terminal 130 network 200 information processing device 201 Processor 202 Memory 203 Storage 204 Input/output interface (input/output I/F) 205 Communication interface (communication I/F) 320 Storage unit 321 Program 330 Control unit 331 Delivery request management unit 331 Delivery request management 332 Settlement processing unit 520 Storage unit 521 Program 522 Case acceptance DB 530 Control unit 531 Delivery request management unit 531 Collection request management Unit 532 Optical detection unit 532 Optical detection unit 720 Storage unit 721 Program 722 Delivery request DB 730 Control unit 731 Delivery request management unit 732 Information code display unit 1120 Memory unit 1121 Program 1130 Control unit 1131 Collection request management unit 1131 Collection request management 1132 Settlement processing unit 1320 Storage unit 1321 Program 1330 Control unit 1331 Collection request Management unit 1332 Optical detection unit 1520 Storage unit 1521 Program 1530 Control unit 1531 Collection request management unit 1532 Information code display unit 1833, 1933 Transaction information creation unit 1823, 1923 ... Transaction information DB.

Claims (8)

to the information processing terminal,
a step of receiving information about a delivery request from another information processing device;
First transaction information for remitting predetermined virtual assets from virtual assets owned by a delivery source user and/or a delivery destination user to a deliverer user, wherein one or more unlocking conditions are specified receiving transaction information from a blockchain network;
A first information code possessed by the delivery source user regarding the delivery request and a second information code possessed by the delivery destination user regarding the delivery request are read, and the first information and the second information contained in the first information code are read. a step of obtaining second information included in the information code;
creating second transaction information including the first information and the second information as a release condition corresponding to one of the unlocking conditions, and transmitting the second transaction information to a blockchain network;
program. The step of receiving information about the delivery order includes:
receiving a decryption key;
The step of obtaining the first information and the second information includes:
a step of decrypting first encrypted information contained in the first information code and second encrypted information contained in the second information code using the decryption key;
obtaining the decoded first information and second information;
A program according to claim 1. One of the unlocking conditions specified in the first transaction information includes the passage of a predetermined period of time and information possessed by the user from whom the virtual asset was transferred according to the first transaction information,
3. A program according to claim 1 or 2. First transaction information for receiving information related to a delivery request from another information processing device, and remittance of predetermined virtual assets from a delivery source user and/or a delivery destination user to a delivery user, wherein one or more solutions are provided. a receiving unit that receives the first transaction information specifying a lock condition from a blockchain network;
A first information code possessed by the delivery source user regarding the delivery request and a second information code possessed by the delivery destination user regarding the delivery request are read, and the first information and the second information contained in the first information code are read. an optical detection unit that acquires the second information included in the information code;
a transaction information creation unit that creates second transaction information including the first information and the second information as a release condition corresponding to one of the unlocking conditions;
a transmission unit that transmits the second transaction information to a blockchain network;
Information processing terminal. The information processing terminal
a step of receiving information about a delivery request from another information processing device;
Blocking first transaction information for remittance of a predetermined virtual asset from a delivery source user and/or a delivery destination user to a deliverer user, the first transaction information specifying one or more unlocking conditions receiving from a chain network;
A first information code possessed by the delivery source user regarding the delivery request and a second information code possessed by the delivery destination user regarding the delivery request are read, and the first information and the second information contained in the first information code are read. a step of obtaining second information included in the information code;
creating second transaction information including the first information and the second information as a release condition corresponding to one of the unlocking conditions, and transmitting the second transaction information to a blockchain network;
Information processing methods. to the information processing terminal,
a step of receiving information about a collection request from another information processing device;
a step of receiving, from a blockchain network, first transaction information for transferring predetermined virtual assets from a recovery destination user to a recovery person, the first transaction information specifying one or more unlocking conditions; ,
a step of reading an information code possessed by the collection destination user regarding the collection request and acquiring information included in the information code;
creating second transaction information including the information as a release condition corresponding to one of the unlocking conditions, and transmitting the second transaction information to the blockchain network;
program. The first transaction information for receiving information on a collection request from another information processing device and transferring predetermined virtual assets from a collection destination user to a collection person, wherein one or more unlocking conditions are specified. a receiving unit that receives the first transaction information from the blockchain network;
an optical detection unit that reads an information code given to a collection destination user in response to the collection request and acquires information included in the information code;
a transaction information creation unit that creates second transaction information including the information as a release condition corresponding to one of the unlocking conditions;
a transmission unit that transmits the second transaction information to a blockchain network;
Information processing terminal. The information processing device
a step of receiving information about a collection request from another information processing device;
a step of receiving, from a blockchain network, first transaction information for transferring predetermined virtual assets from a recovery destination user to a recovery person, the first transaction information specifying one or more unlocking conditions; ,
a step of reading an information code possessed by the collection destination user regarding the collection request and acquiring information included in the information code;
creating second transaction information including said information as a release condition corresponding to one of said unlocking conditions, and sending it to a blockchain network;
Information processing methods.

Images