Delivery destination information management system, and delivery destination information management method

Abstract

To provide a delivery destination information management system capable of accurately grasping an address of a delivery destination.SOLUTION: A delivery destination information management system comprises: an acquisition unit which acquires a notification indicating agreement from a terminal device of a delivery destination when notifying a delivery request source of destination information based on a real estate ID according to an address of the delivery destination to which a delivery object is delivered; and a destination information transmission unit which transmits the destination information to the terminal device of the delivery request source when the notification is acquired.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a delivery destination information management system and a delivery destination information management method.

Background Art

[0002] When a user who is a delivery requester sends a delivery item to a recipient user, the user specifies the recipient's address, name, telephone number, etc. to a delivery company and requests the delivery. For example, the user who is the delivery requester specifies the recipient's address by inputting it into the address input field of the delivery request site using a touch panel, keyboard, or the like. In addition, there is a system that identifies a product on a network and sends this product to a specific individual (for example, Patent Document 1). In this system, the address, name, etc. are registered in advance as member information, and the product is delivered based on the registered address.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, since the delivery address is input by the user, etc., depending on the user, the way of writing the address when inputting may be different. For example, when "1-chome 1-banchi 1-gou" of the address is input as "1-1-1", although a hyphen needs to be input, characters with a similar appearance such as a minus sign or a circumflex may be input. Then, although it indicates one address, because the character codes are different, it becomes difficult to distinguish whether the address grasped by the company or organization and the address input by the resident are the same address. Also, when inputting the address, if a part of the address notation is omitted, the delivery address cannot be accurately grasped. Therefore, it is preferable to accurately grasp the delivery address.

[0005] The present invention has been made in view of such circumstances, and its object is to provide a delivery destination information management system and a delivery destination information management method capable of accurately grasping the delivery address.

Means for Solving the Problems

[0006] In order to solve the above-described problems, one aspect of the present invention is an acquisition unit that acquires a notification indicating agreement to notify a delivery source of destination information based on a real estate ID corresponding to the address of a delivery destination for delivering a delivery item from the terminal device of the delivery destination, and a destination information transmission unit that transmits the destination information to the terminal device of the delivery source when the notification is acquired. It is a delivery destination information management system having

[0007] Also, one aspect of the present invention is an acquisition unit that acquires a notification indicating agreement to generate destination information based on a real estate ID corresponding to the address of a delivery destination for delivering a delivery item, which is destination information notified to the delivery source of the delivery item, from the terminal device of the delivery destination, and a destination information transmission unit that transmits the destination information generated based on the notification to the terminal device of the delivery destination when the destination information is generated. It is a delivery destination information management system having

[0008] Also, one aspect of the present invention is a delivery destination information management method in which an acquisition unit acquires a notification indicating agreement to notify a delivery request source of destination information based on a real estate ID corresponding to the address of a delivery destination to which a delivery is made, and a destination information transmission unit transmits the destination information to the terminal device of the delivery request source when the notification is acquired.

[0009] Also, one aspect of the present invention is a delivery destination information management method in which an acquisition unit acquires a notification indicating agreement to generate destination information based on a real estate ID corresponding to the address of a delivery destination to which a delivery is made, which is destination information to be notified to the delivery request source of the delivery, and a destination information transmission unit transmits the destination information generated based on the notification to the terminal device of the delivery destination when the destination information is generated.

Advantages of the Invention

[0010] As described above, according to this invention, when notifying a delivery carrier of the delivery destination address, since the notification is made based on the real estate ID corresponding to the delivery destination address, it becomes possible to accurately grasp the delivery destination address.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Embodiments for Carrying Out the Invention

[0012] Hereinafter, a delivery destination information management system according to an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a schematic block diagram showing the configuration of a delivery destination information management system S according to an embodiment of this invention. The delivery destination information management system S is communicably connected via a network NW to a plurality of terminal devices (10A, 10B,... 10n), an information management server 20, a real estate ID server 30, an EC site server 40, a delivery company server 50, and a delivery company server 51.

[0013] The plurality of terminal devices (10A, 10B,... 10n) are each used by different individuals (users). The terminal devices (10A, 10B,... 10n) can use, for example, any one of a smartphone, a tablet, and a PC (Personal Computer). The functions installed in the terminal devices 10A, 10B,... 10n are the same. Here, although three terminal devices are shown in FIG. 1, there may be two, four or more, or even one. In this embodiment, the case where the terminal device 10 is operated by an individual who owns the terminal device 10 will be described, but the terminal device 11 may be operated by an individual who owns the terminal device 11. Here, as an example, the case will be described where the terminal device used by the user who is the delivery requester for requesting the delivery of a delivery item is the terminal device 10A, and the terminal device used by the user who can receive the delivery item at the delivery address of the delivery destination for delivering the delivery item is the terminal device 10B. Here, when a user using the terminal device 10A delivers a delivery item to a user using the terminal device 10B, the user of the terminal device 10A can be the delivery request source user, and the user of the terminal device 10B can be the destination user.

[0014] The information management server 20 transmits destination information based on a real estate ID (Identifier) corresponding to the address of the destination to which the delivery item is to be delivered to other devices. The destination information may be based on the real estate ID, and may be the real estate ID itself or the address corresponding to the real estate ID.

[0015] The real estate ID server 30 has a storage unit that stores the correspondence between the address and the real estate ID. When a real estate ID is specified from an external device, the address corresponding to the specified real estate ID is transmitted to the requesting device. The real estate ID is a common code for uniquely identifying land or a building. The real estate ID is identification information that can uniquely identify a real estate even in an address where the address notation is likely to vary or in a case where there are multiple buildings at the same address and lot number. For such a real estate ID, an address described by a uniquely determined address notation is associated and stored. Here, the address may be either a dwelling or a residence indication as long as the real estate ID can be obtained.

[0016] The EC site server 40 is a server used by a service provider and provides an Internet shopping service via the EC site. Here, in Internet shopping, the product purchased may be delivered as a delivery item, or an item that is not a product purchased in Internet shopping may be delivered as a delivery item. In delivering such a delivery item, by using the information management server 20 in the present embodiment, the delivery request source can have the delivery item delivered by the delivery carrier even if it does not directly grasp the address of the destination. Also, in FIG. 1, the case where the EC site server 40 is used is described as an example. However, as long as it can provide a service for delivering an item from the delivery requester to the destination, instead of the EC site server 40, a server other than the EC site server 40 may be used.

[0017] The delivery provider server 50 and the delivery provider server 51 are used by different delivery providers respectively. The delivery provider delivers the item for which delivery has been requested from the user of the delivery requester to the user designated as the destination based on the destination address. Also, in FIG. 1, the case where there are two delivery providers and the delivery provider server 50 and the delivery provider server 51 are used is described. However, the number of delivery providers may be three or more. In this case, three or more delivery providers may each use a different delivery provider server. That is, the number of delivery provider servers may be three or more.

[0018] The network NW includes at least any one of the Internet, a mobile phone network, a LAN (Local Area Network), etc. The network NW may be at least either wired or wireless.

[0019] FIG. 2 is a schematic functional block diagram showing the functions of the information management server 20. The information management server 20 includes a communication unit 201, a storage unit 202, an acquisition unit 203, a delivery provider identification information acquisition unit 204, a destination information generation unit 205, a real estate ID acquisition unit 206, a destination information transmission unit 207, and a control unit 208.

[0020] The communication unit 201 communicates with the terminal devices (10A, 10B,... 10n), the real estate ID server 30, the EC site server 40, the delivery provider server 50, and the delivery provider server 51 via the network NW. When communicating with the terminal devices (10A, 10B,... 10n), the communication unit 201 may communicate using any one of e-mail, SNS (Social Networking Service), a message exchange application, etc.

[0021] The storage unit 202 stores various types of data. The storage unit 202 has a user database that stores information about each user. FIG. 3 is a diagram showing an example of the user database stored in the storage unit 202. The user database is data in which, for example, a user ID, the address of the user for whom the destination management service is provided, the name, and the contact information are associated. Such a user's address may be stored in association with the user ID in the user database by executing the identity verification process described later, or the user may be asked to perform an operation input from the terminal device 10 to receive data input for the address and name and store them in association with the user ID. Also, although the case of registering the user's address in the user database is described as an example, any information that can identify the address may be used, and the real estate ID may be stored instead of the address. The contact information represents terminal identification information that can communicate with the terminal device used by the user indicated by the user ID. The terminal identification information may be any of an email address, a telephone number, unique identification information assigned to the terminal device, and the like. This contact information may be registered at the time of user registration.

[0022] Returning to FIG. 2, the acquisition unit 203 acquires a notification indicating agreement to notify the delivery requester of the destination information based on the real estate ID corresponding to the address of the delivery destination of the item to be delivered, from the terminal device of the delivery destination (for example, Embodiments 1-1 and 1-2 described later). Also, the acquisition unit 203 may be a function of acquiring, from the terminal device of the delivery destination, a notification indicating agreement to generate the destination information based on the real estate ID corresponding to the address of the delivery destination of the item to be delivered, which is the destination information notified to the delivery requester of the item to be delivered (for example, Embodiments 2-1 and 2-2 described later).

[0023] The delivery service provider identification information acquisition unit 204 acquires delivery service provider identification information for identifying the delivery service provider. For example, the delivery service provider identification information acquisition unit 204 acquires the delivery service provider identification information transmitted from any one of the terminal device 10 used by the destination user, the terminal device 10 used by the delivery requester user, and the EC site server 40 in response to being received by the communication unit 201. The delivery request service provider identification information only needs to be able to identify each of a plurality of delivery service providers. By identifying the delivery service provider with the delivery request service provider identification information, it is possible to identify which of the plurality of delivery service provider servers it is.

[0024] The destination information generation unit 205 generates destination information based on the real estate ID corresponding to the address of the destination to which the item to be delivered is delivered. The destination information only needs to be information capable of specifying the real estate ID, and may include at least one of the real estate ID and the address of the destination. Further, the destination information may be information processed from either the real estate ID or the address of the destination. This processing may be, for example, any of a process of adding the delivery request source user ID to which the destination information is notified, a process of adding information capable of specifying the delivery service provider, a process of encrypting the destination information, a process of representing the destination information by a two-dimensional barcode, etc.

[0025] The real estate ID acquisition unit 206 acquires the real estate ID corresponding to the user's address from the real estate ID server 30. The user's address used here may be the address acquired from the personal card by performing the identity verification process.

[0026] When the destination information transmission unit 207 acquires a notification indicating agreement to notify the delivery request source of the destination information, it transmits the destination information to the terminal device of the delivery request source. Here, after obtaining agreement from the terminal device 10 that is the destination, the destination information can be notified to the delivery request source. Also, the destination information transmission unit 207 may transmit destination information to the terminal device of the recipient based on a notification indicating agreement to generate the destination information notified to the sender of the delivery item. Here, after obtaining agreement from the terminal device 10 which is the recipient, destination information for notifying the sender can be generated and the destination information can be notified to the terminal device 10 of the recipient. The destination information transmission unit 207 transmits the destination information generated by the destination information generation unit 205.

[0027] The control unit 208 controls each part of the information management server 20.

[0028] FIG. 4 is a schematic functional block diagram showing the functions of the terminal device 10. The terminal device 10 includes a communication unit 101, a storage unit 102, an input unit 103, a display unit 104, a destination information acquisition unit 105, a destination information providing unit 106, and a control unit 107. The communication unit 101 communicates with terminal devices 10 other than its own terminal device 10, a real estate ID server 30, an EC site server 40, a delivery company server 50, and a delivery company server 51 via a network NW.

[0029] The storage unit 102 stores various data. For example, the storage unit 102 stores data received from other devices. The input unit 103 inputs various data in response to a user's operation input. The input unit 110 may be any of, for example, a touch panel, a keyboard, a mouse, etc. The display unit 104 is a display panel and displays various data. The display unit 104 and the input unit 103 may be realized by separate devices or may be integrally configured as a touch panel.

[0030] The destination information acquisition unit 105 acquires destination information from either the information management server 20 or a terminal device 10 other than its own terminal device 10. The destination information providing unit 106 transmits the destination information acquired at the terminal device of the sender to the device of the delivery company that delivers the delivery item. Also, when the destination information is acquired by the delivery request source terminal device from the destination terminal device, the destination information providing unit 106 notifies the destination information to the delivery company that delivers the delivery item from the delivery request source terminal device. The destination information providing unit 106 may notify the destination information to the electronic device of the delivery company indicated by the delivery company identification information added to the destination information. The control unit 107 controls each part of the own terminal device 10.

[0031] The above-described storage unit 102 and storage unit 202 are configured by a storage medium, for example, an HDD (Hard Disk Drive), a flash memory, an EEPROM (Electrically Erasable Programmable Read Only Memory), a RAM (Random Access read / write Memory), a ROM (Read Only Memory), or an arbitrary combination of these storage media. For example, a non-volatile memory can be used for the storage unit 102 and the storage unit 202.

[0032] The communication unit 201, the acquisition unit 203, the delivery company identification information acquisition unit 204, the destination information generation unit 205, the real estate ID acquisition unit 206, the destination information transmission unit 207, and the control unit 208 may be configured by a processing device such as a CPU (Central Processing Unit) or a dedicated electronic circuit. Also, the communication unit 101, the input unit 103, the display unit 104, the destination information acquisition unit 105, the destination information providing unit 106, and the control unit 107 may be configured by a processing device such as a CPU or a dedicated electronic circuit.

[0033] Next, the operation of the above-described delivery destination information management system S will be described. Here, the user who uses the terminal device 10A is the user of the delivery request source who requests the delivery of the delivery item, the user who uses the terminal device 10B is the user of the delivery destination of the delivery item, and the case where the user of the delivery request source does not know the address of the user of the delivery destination and delivers the delivery item will be described as an example. Here, it is assumed that the user of the terminal device 10A and the user of the terminal device 10B have each completed the authentication process in advance using the information management server 20. The authentication process will be described later.

[0034] ≪Embodiment 1-1≫ FIG. 5 is a sequence diagram for explaining the operation of the delivery destination information management system S. The user of the terminal device 10A inputs, from the input unit 103, a request to obtain the destination (the address of the recipient to whom the delivery is to be made) of the user of the terminal device 10B and the user ID assigned to the user of the terminal device 10B. Here, the case where the user of the terminal device 10A inputs the user ID assigned to the user of the terminal device 10B will be described. However, as long as it is information that can identify the destination user, it may be the user name or the nickname registered in association with the user ID (the same applies to Embodiment 1-2, Embodiment 2-1, and Embodiment 2-2 described later). Based on this operation input, the control unit 107 of the terminal device 10A transmits a destination acquisition request to the information management server 20, where the user ID of the user of the terminal device 10B is set as the destination user ID, and the user ID of the user using the terminal device 10A is set as the delivery request source user ID (step S101).

[0035] When the control unit 208 of the information management server 20 receives the destination acquisition request from the terminal device 10A, it transmits a confirmation notice to the terminal device 10B to inquire whether it is possible to notify the user of the terminal device 10A of the address of the user of the terminal device 10B (step S102).

[0036] When the control unit 107 of the terminal device 10B receives the confirmation notice, it displays a confirmation screen that enables the input of an instruction on whether to notify the user of the terminal device 10A with the address of the user of the terminal device 10B as the destination. The user of the terminal device 10B checks the confirmation screen and, if it is permissible to notify the user of the terminal device 10A with the address as the destination, makes an operation input to the "Notification Permission" operation button. Based on this operation input, the control unit 107 of the terminal device 10B transmits a permission notice indicating that the user of the terminal device 10A has permitted the notification of the destination information of the user of the terminal device 10B to the user of the terminal device 10A to the information management server 20 (step S103). Here, it can also be said that the permission notice indicating that the user of the terminal device 10A has permitted the notification of the destination information of the user of the terminal device 10B is a request input from the user of the terminal device 10B after reaching an agreement on notifying the delivery request source of the destination information based on the real estate ID corresponding to the address of the delivery destination of the delivered item.

[0037] The acquisition unit 203 of the information management server 20 acquires the permission notice from the terminal device 10B via the communication unit 201. Here, when the permission notice is acquired, it can be grasped that the destination user has agreed to notify the delivery request source of the destination information. When the permission notice is obtained, the real estate ID acquisition unit 206 reads the address of the user of the terminal device 10B from the storage unit 202 based on the user ID, queries the real estate ID server 30 for the real estate ID corresponding to the read address, and acquires the real estate ID. Here, the real estate ID corresponding to the address obtained by reading the address corresponding to the user ID from the storage unit 202 may be obtained, or the user of the terminal device 10B may directly input the address in step S103, and the real estate ID corresponding to the input address may be obtained. Also, if the same service has been used in the past and the real estate ID has already been recorded in the storage unit 202, it may be used by reading the real estate ID. Also, in that case, the address information associated with the registered real estate ID may be transmitted to the terminal device 10B for display, and the user may be asked to confirm that the address has not changed due to a move or the like, and the confirmation result may be obtained from the terminal device 10B by asking the user to input the confirmation result. (The same applies to Embodiment 1-2, Embodiment 2-1, and Embodiment 2-2 described later). When the destination information generation unit 205 of the information management server 20 acquires the real estate ID, it generates destination information based on the real estate ID. When the destination information is generated, the destination information transmission unit 207 of the information management server 20 transmits the destination information generated by the destination information generation unit 205 to the terminal device 10A based on the delivery request source user ID (step S104). When the destination information transmission unit 207 transmits the destination information based on the user ID of the delivery request source, it may use the contact information registered for the user, or the contact information of the terminal device 10A may be set when the destination acquisition request is received from the terminal device 10A in step S101.

[0038] The destination information acquisition unit 105 of the terminal device 10A acquires destination information via the communication unit 201. When the destination information is acquired, the destination information providing unit 106 transmits the destination information to the delivery service provider server 50 (step S105). As a result, the delivery service provider can grasp the address of the delivery destination based on the destination information. When the real estate ID is included in the destination information, the delivery service provider server can acquire the address corresponding to the real estate ID by inquiring the real estate ID server 30 about the address corresponding to the real estate ID. When the address is included in the destination information, since this address is the address corresponding to the real estate ID, this address can be used as the delivery destination address.

[0039] <Effect of Embodiment 1-1> In Embodiment 1-1, even if the user of the terminal device 10A does not know the address of the user of the terminal device 10B, which is the person to whom the delivery is to be made, by sending a destination acquisition request to the information management server 20, information capable of specifying the address of the user of the terminal device 10B can be acquired and notified to the delivery service provider. In addition, since the delivery service provider can be notified of the real estate ID corresponding to the delivery destination address or the address corresponding to the real estate ID, it becomes possible to accurately grasp the delivery destination address.

[0040] <<Embodiment 1-2>> FIG. 6 is a sequence diagram for explaining the operation of the delivery destination information management system S. The user of the terminal device 10B inputs, from the input unit 103, a request for notifying the user of the terminal device 10A of the destination of the user of the terminal device 10B and the user ID assigned to the user of the terminal device 10A. Here, the request for notifying the user of the terminal device 10A of the destination of the user of the terminal device 10B is a request input by the user based on the fact that the user of the terminal device 10B has agreed to notify the delivery request source of the destination information. Based on this operation input, the control unit 107 of the terminal device 10B transmits a destination notification request, which is a request for notifying the destination of the user of the terminal device 10B, with the user ID of the user of the terminal device 10B as the destination user ID and the user ID of the user using the terminal device 10A as the delivery request source user ID, to the information management server 20 (step S121).

[0041] The acquisition unit 203 of the information management server 20 acquires the destination notification request from the terminal device 10B via the communication unit 201. Here, when the destination notification request is acquired, it is possible to grasp that the destination user has agreed to notify the delivery request source of the destination information. When the destination notification request is acquired, the real estate ID acquisition unit 206 reads out the address of the user of the terminal device 10B from the storage unit 202 based on the user ID, inquires of the real estate ID server 30 about the real estate ID corresponding to the read address, and acquires the real estate ID. When the real estate ID is acquired, the destination information generation unit 205 of the information management server 20 generates destination information based on the real estate ID. When the destination information is generated, the destination information transmission unit 207 of the information management server 20 transmits the destination information generated by the destination information generation unit 205 to the terminal device 10A based on the delivery request source user ID (step S122). When transmitting the destination information based on the delivery request source user ID, the destination information transmission unit 207 may use the contact registered for the user, or the contact of the terminal device 10A may be set when receiving the destination acquisition request from the terminal device 10A in step S101.

[0042] The destination information acquisition unit 105 of the terminal device 10A acquires destination information via the communication unit 201. When the destination information is acquired, the destination information providing unit 106 transmits the destination information to the carrier server 50 (step S123). Thereby, the carrier can grasp the delivery destination address based on the destination information.

[0043] <Effect of Embodiment 1-2> In Embodiment 1-2, based on the intention of the user at the delivery destination, the destination information can be passed to the user of the delivery requester and notified from the user of the delivery requester to the carrier. In addition, since the carrier can be notified of the real estate ID corresponding to the delivery destination address or the address corresponding to the real estate ID, it becomes possible to accurately grasp the delivery destination address.

[0044] <Effects of Embodiments 1-1 and 1-2> In the above-described Embodiments 1-1 and 1-2, since the destination information is transmitted from the information management server 20 to the terminal device 10A, the user of the delivery destination (terminal device 10B) and the user of the delivery requester (terminal device 10A) do not need to directly communicate regarding the destination information. Therefore, even if the user of the delivery destination and the user of the delivery requester do not directly communicate with each other, the delivery item can be delivered from the user of the delivery requester to the user of the delivery destination.

[0045] <<Case of Embodiment 2-1>> FIG. 7 is a sequence diagram for explaining the operation of the delivery destination information management system S. The user of the terminal device 10A inputs, from the input unit 103, a request to acquire the destination of the user of the terminal device 10B and the user ID assigned to the user of the terminal device 10B. Based on this operation input, the control unit 107 of the terminal device 10A transmits a destination acquisition request to acquire the destination of the user of the terminal device 10B, where the user ID of the user of the terminal device 10B is the destination user ID and the user ID of the user using the terminal device 10A is the delivery requester user ID, to the information management server 20 (step S201).

[0046] When the control unit 208 of the information management server 20 receives a destination acquisition request from the terminal device 10A, it transmits a confirmation notice to the terminal device 10B to inquire whether it may generate destination information for notifying the user of the terminal device 10A of the address of the user of the terminal device 10B (step S202).

[0047] When the control unit 107 of the terminal device 10B receives the confirmation notice, it displays a confirmation screen on which an instruction for inputting whether it may generate destination information for notifying the user of the terminal device 10A of the address of the user of the terminal device 10B as the destination can be input. The user of the terminal device 10B checks the confirmation screen and, if it is possible to generate the destination information, makes an operation input to the operation button of "generation permission". Based on this operation input, the control unit 107 of the terminal device 10B transmits a permission notice indicating consent (permission) to generate the destination information to be notified to the delivery requester of the delivered item to the information management server 20 (step S203).

[0048] The acquisition unit 203 of the information management server 20 acquires the permission notice from the terminal device 10B via the communication unit 201. When the permission notice is acquired here, it can be grasped that the user of the terminal device 10B has consented to generate the destination information. When the permission notice is acquired, the real estate ID acquisition unit 206 reads the address of the user of the terminal device 10B from the storage unit 202 based on the user ID, inquires of the real estate ID server 30 about the real estate ID corresponding to the read address, and acquires the real estate ID. When the destination information generation unit 205 of the information management server 20 acquires the real estate ID, it generates destination information based on the real estate ID. When the destination information is generated, the destination information transmission unit 207 of the information management server 20 transmits the destination information generated by the destination information generation unit 205 to the terminal device 10B based on the destination user ID (step S204).

[0049] The destination information acquisition unit 105 of the terminal device 10B acquires destination information via the communication unit 201. When the destination information is acquired, the control unit 107 of the terminal device 10B transmits the destination information to the terminal device 10A (step S205). Here, the terminal device 10B may transmit the destination information to the terminal device 10A using any one of email, SNS, a message exchange app, etc. Also, the terminal device 10B may display a two-dimensional barcode including information of a URL (Uniform Resource Locator) from which destination information can be acquired on the display screen, and cause the camera of the terminal device 10A to capture it, so as to transfer the destination information to the terminal device 10A.

[0050] The destination information acquisition unit 105 of the terminal device 10A acquires destination information from the terminal device 10B. When the destination information is acquired, the destination information providing unit 106 transmits the destination information to the delivery service provider server 50 (step S206). Thereby, the delivery service provider can grasp the delivery destination address based on the destination information.

[0051] <Effect of Embodiment 2-1> In Embodiment 2-1, when there is a request to generate destination information from the user of the delivery requester, after confirming with the recipient user that the destination information is to be generated, the destination information can be generated. Also, the destination information can be notified to the delivery requester user after being notified from the recipient user to the delivery requester user, and can be notified to the delivery service provider. In addition, since the delivery service provider can be notified of the real estate ID corresponding to the delivery destination address or the address corresponding to the real estate ID, it becomes possible to accurately grasp the delivery destination address.

[0052] <<Case of Embodiment 2-2>> FIG. 8 is a sequence diagram for explaining the operation of the delivery destination information management system S. The user of the terminal device 10B inputs a destination information generation request from the input unit 103 to request the generation of destination information used to notify the user of the terminal device 10A of the destination of the user of the terminal device 10B. Here, the request for generating the destination information used to notify the user of the terminal device 10A of the destination of the user of the terminal device 10B is a request input based on the fact that an agreement (permission) has been made regarding generating the destination information to be notified to the delivery requester of the delivered item. When inputting this destination information generation request, the user of the terminal device 10B also inputs the user ID assigned to the user of the terminal device 10A, which can identify that the recipient of the destination information is the user of the terminal device 10A. Based on this operation input, the control unit 107 of the terminal device 10B transmits the destination information representing the destination of the user of the terminal device 10B to the information management server 20 with the user ID of the user using the terminal device 10A set as the delivery requester user ID in the destination information generation request (step S221).

[0053] When the control unit 208 of the information management server 20 receives a destination information generation request from the terminal device 10B, it inquires of the real estate ID server 30 about the real estate ID corresponding to the address of the user of the terminal device 10B and acquires the real estate ID. Here, when the destination information generation request is acquired, it can be grasped that the recipient user has agreed to generate the destination information to be notified to the delivery requester. When the destination information generation unit 205 of the information management server 20 acquires the real estate ID, it generates destination information based on the real estate ID. When the destination information is generated, the destination information transmission unit 207 of the information management server 20 transmits the generated destination information to the terminal device 10B based on the recipient user ID (step S222).

[0054] The destination information acquisition unit 105 of the terminal device 10B acquires destination information via the communication unit 201. When the destination information is acquired, the control unit 107 of the terminal device 10B transmits the destination information to the terminal device 10A (step S223). Here, as in step S205 described above, it may be transmitted by any of various transmission methods, or a two-dimensional barcode including information on a URL from which the destination information can be acquired may be displayed on the display screen and the terminal device 10A may be made to capture it with its camera, so that the destination information may be passed to the terminal device 10A.

[0055] The destination information acquisition unit 105 of the terminal device 10A acquires destination information. When the destination information is acquired, the destination information providing unit 106 transmits the destination information to the delivery service provider server 50 (step S224). Thereby, the delivery service provider can grasp the delivery destination address based on the destination information.

[0056] <Effect of Embodiment 2-2> In Embodiment 2-2, destination information can be generated based on the intention of the destination user, and the destination information can be notified from the destination user to the user who placed the delivery request, and notified from the user who placed the delivery request to the delivery service provider. In addition, since the delivery service provider can be notified of the real estate ID corresponding to the delivery destination address or the address corresponding to the real estate ID, it becomes possible to accurately grasp the delivery destination address.

[0057] In the above-described Embodiments 1-1, 1-2, 2-1, and 2-2, the case where the user who placed the delivery request does not know the address of the destination user has been described, but it may be the case that the user knows it. In this case, the destination information can be passed to the delivery service provider according to the same flow as in each of the above-described embodiments. The user who placed the delivery request purchases a product using the EC site server 40, requests shipment by specifying the destination user, and can notify the delivery service provider server of the destination information according to the processing shown in any of the above-described embodiments, and can have the product delivered to the destination user. In addition, the user who is the delivery requester may bring the delivery prepared by himself / herself to the base of the delivery service provider and notify the destination information to the delivery service provider server to which the base belongs according to the process shown in any of the above embodiments. Thereby, even for the delivery prepared by oneself, it is possible to have it delivered using the above destination information.

[0058] In the above-described Embodiments 1-1, 1-2, 2-1, and 2-2, the destination information generation unit 205 may generate the real estate ID as the destination information, or may generate the delivery destination address as the destination information. Further, the destination information generation unit 205 may generate, as the destination information, information obtained by processing either one of the real estate ID and the delivery destination address. When the destination information generation unit 205 performs this processing, for example, the processing may be performed by selecting and executing any one of the following Processings a to f, or at least two of Processings a to f may be combined and executed.

[0059] <Processing a> The destination information generation unit 205 may add the delivery requester user ID, which is the destination to which the destination information is to be notified, to the real estate ID or the delivery destination address. In this case, the destination information includes not only information that can identify the real estate ID but also the delivery requester user ID. Therefore, when the user of the terminal device 10A transmits the destination information to a device other than the delivery service provider server (for example, another terminal device 10), even if the destination information becomes graspable by a device other than the delivery service provider, it is possible to identify from which terminal device 10 the destination information was transmitted by referring to the delivery requester user ID included in the destination information. Thereby, even when the destination information has circulated outside the delivery service provider, it is possible to identify which terminal device 10 was the source of the circulation.

[0060] <Processing b> The destination information generation unit 205 may add information that can identify the delivery service provider to the real estate ID or the delivery destination address. Accordingly, even when there are multiple delivery providers, it is possible to stipulate which delivery provider the destination information should be notified to. For example, using the Internet shopping provided by the EC site server 40, a user of the terminal device 10A purchases a product and has the product delivered to a user of the terminal device 10B. In this case, any one of the terminal device 10A, the terminal device 10B, and the EC site server 40 may be used to specify the delivery provider. When the delivery provider is specified, the delivery provider identification information acquisition unit 204 acquires the delivery provider identification information assigned to the specified delivery provider from the source of specification (any one of the terminal device 10A, the terminal device 10B, and the EC site server 40).

[0061] When the terminal device 10A specifies the delivery provider, for example, in the above steps S101 and S201, when transmitting data, the user of the terminal device 10A may be asked to input the specification of the delivery provider, and the delivery provider identification information corresponding to the specified delivery provider may be included in the destination information. Also, in any of the steps S105, S123, S206, and S224, when transmitting the destination information to the delivery provider server, if the user of the terminal device 10A is asked to specify the delivery provider and the destination information is transmitted to the delivery provider server corresponding to the specified delivery provider, even if the destination information does not include the delivery provider identification information, the user of the terminal device 10A can specify the delivery provider. In this case, the terminal device 10A may have a function of specifying the delivery provider to which the destination information is to be transmitted.

[0062] When the terminal device 10B specifies the delivery provider, for example, in any of the steps S103, S121, S203, and S221, the user of the terminal device 10B may be asked to input the specification of the delivery provider, and the delivery provider identification information corresponding to the specified delivery provider may be included in the destination information. Also, when notifying the destination information from the terminal device 10B to the terminal device 10A in either step S205 or step S223, the user of the terminal device 10B may be asked to specify a delivery carrier, and the destination information with the delivery carrier identification information corresponding to the specified delivery carrier may be transmitted to the terminal device 10A. In this case, the terminal device 10B may have a function of executing a process of adding the delivery carrier identification information to the destination information.

[0063] When the EC site server 40 designates a delivery carrier, for example, when a product is purchased in the Internet shopping service provided by the EC site server 40 based on an instruction from the user of the terminal device 10A and the product is delivered to the user of the terminal device 10B as a delivery item, the virtual store of the Internet shopping may be set to designate the delivery carrier. In this case, the operator who operates the virtual store may register in advance with the EC site server 40 from the terminal device used by himself / herself which delivery carrier to use. Also, at the timing when the product is purchased, the EC site server 40 may select a delivery carrier based on a predetermined determination logic according to the dimensions of the product, the price of the product, etc.

[0064] <Processing c> The destination information generation unit 205 may perform a process of encrypting the destination information. For example, the delivery destination information management system S may perform transmission and reception of information between the information management server 20 and each delivery carrier server (50, 51) based on the public key cryptosystem. In this case, each delivery carrier server (50, 51) generates a public key and a secret key respectively, and transmits the public key to the information management server 20. The information management server 20 stores the received public key in the storage unit 202 in association with the delivery carrier identification information. Then, the destination information generation unit 205 adds the delivery request source user ID to the real estate ID or the address of the destination, and encrypts the destination information using the public key of the delivery carrier to be used. Then, the information management server 20 transmits the encrypted destination information to the terminal device 10A by any one of the methods of the above-described Embodiments 1-1, 1-2, 2-1, and 2-2. Here, the destination information generation unit 205 may add the electronic signature assigned to the information management server 20 to the encrypted destination information and then transmit it to the terminal device 10A.

[0065] In this case, the user of the terminal device 10A can receive the encrypted destination information by the terminal device 10A. However, since the destination information is encrypted, the user cannot directly grasp the address of the destination or the real estate ID. Thereby, even if the destination information is passed to the delivery request source user, it is possible to prevent the delivery request source user from grasping the address of the destination or the real estate ID. Then, when the encrypted destination information is transmitted from the terminal device 10A to the delivery carrier server, the delivery carrier server receives the encrypted destination information. Then, the delivery carrier server restores the destination information using the private key possessed by the delivery carrier server itself. Thereby, the delivery carrier server can obtain the destination information in an unencrypted state. Further, when an electronic signature is added to the encrypted destination information, the delivery carrier server inquires the server of the certification business operator about the electronic signature and verifies whether the destination information is created by the information management server 20. And when it is determined as the destination information created by the information management server 20 as a result of verification, the destination information may be restored using the private key. Here, when the electronic signature of the information management server 20 is added to the destination information, it is possible to confirm that the destination information is provided from the information management server 20, and it is possible to grasp that the source of the destination information is correct.

[0066] According to this embodiment, even if the delivery destination address or real estate ID is passed to the terminal device of the delivery requester, it is possible to prevent the delivery destination address or real estate ID from being grasped by the user of the delivery requester, and among multiple delivery companies, only the delivery company requested for delivery can decrypt the destination information and grasp the delivery destination address or real estate ID. Here, even if the destination information is sent to a delivery company server that has not been requested for delivery, the delivery company that has not been requested for delivery cannot decrypt the destination information, so it is possible to prevent the delivery destination address or real estate ID from being grasped. Also, since the destination information includes the user ID of the delivery requester, even if the destination information circulates to parties other than the delivery company requested for delivery, it is possible to identify the terminal device 10 from which it originated. In this way, when encrypting the destination information, the user ID of the delivery requester is included in the destination information. However, the encryption process may be performed without including it, or another piece of information may be added for the encryption process.

[0067] 〈Processing d〉 The destination information generation unit 205 may set a URL that can identify the delivery company to which the destination information is to be notified in the destination information. For example, each delivery company server (50, 51) transmits the URL of its own website to the information management server 20. The information management server 20 stores the URL received from the delivery company server in the storage unit 202 in association with the delivery company identification information. Then, when generating the destination information, the destination information generation unit 205 generates the destination information by adding data indicating the real estate ID or the delivery destination address as a parameter to the URL of the delivery company to be used. The information management server 20 transmits the generated destination information to the terminal device 10A by any of the methods of the above-described Embodiments 1-1, 1-2, 2-1, and 2-2. When receiving the destination information, the terminal device 10A displays the URL received as the destination information together with a message such as "Touching the URL will notify the delivery company of the delivery destination address."

[0068] When the user of the terminal device 10A checks this display screen, they perform a touch input on the URL via the input unit 103. As a result, the terminal device 10A accesses the web page of the URL set as the destination information. This web page is a web page provided by the delivery service provider server and is provided with an input field where the real estate ID can be input. When the terminal device 10A accesses this URL, it sets the parameters included in the destination information in the input field. Regarding this parameter, the terminal device 10A may automatically set it in the input field, or display the real estate ID (or the delivery destination address) based on the parameter on the web page or on a screen that prompts a touch input for the URL, and the user may input it into the input field manually based on this displayed content. Then, when a button such as "OK" is touched and input by the user, the real estate ID is notified to the delivery service provider server.

[0069] 〈Processing e〉 As a processing of the destination information, the destination information generation unit 205 may generate a two-dimensional barcode representing the destination information. In this case, the destination information generation unit 205 may generate a two-dimensional barcode representing the destination information and transmit it to the terminal device 10A or the terminal device 10B. When the terminal device 10A receives data representing the two-dimensional barcode, when the terminal device 10A receives the two-dimensional barcode, it displays the received two-dimensional barcode on the display unit 104. The terminal device 10A may interpret the two-dimensional barcode by performing image analysis on the displayed two-dimensional barcode and extract the real estate ID (or address) included in the two-dimensional barcode. Then, the extracted real estate ID (or address) may be transmitted to the delivery service provider server. Also, when the terminal device 10B receives data representing a two-dimensional barcode, upon receiving the two-dimensional barcode, the terminal device 10B displays the received two-dimensional barcode on the display unit 104. And when the user of the terminal device 10A, which is the party to whom the destination information is to be conveyed, is nearby, the user of the terminal device 10A is asked to read the two-dimensional barcode. Thereby, the destination information can be transferred to the terminal device 10A, and the destination information can be notified from the terminal device 10A to the delivery service provider server. Note that the terminal device 10A may receive a URL that can identify the delivery service provider based on the above-described process d, and obtain the destination information as a two-dimensional barcode based on the above-described process e. In this case, the terminal device 10A may access the received URL and set the real estate ID obtained from the two-dimensional barcode in the input field for inputting the real estate ID.

[0070] 〈Process f〉 The destination information generation unit 205 may add an expiration date to the destination information. If the destination information reaches the delivery service provider server within the expiration date, the real estate ID based on the destination information can be used. Also, for the destination information that has passed the expiration date, it may be made unable to be transmitted from the terminal device 10A to the delivery service provider server, or it may be made unable to be transmitted from the terminal device 10B to the terminal device 10A, or when the destination information reaches the delivery service provider server and the expiration date has passed, an error may be transmitted to the terminal device 10A.

[0071] ≪Identity verification process≫ FIG. 9 is a sequence diagram for explaining the operation of the delivery destination information management system S when performing identity verification for the user of the terminal device 10. Here, the case of performing identity verification for the user of the terminal device 10B, which is the recipient of the delivered item, will be described. However, for the user of the terminal device 10A as well, the identity verification process can be similarly performed using the terminal device 10A.

[0072] The user of the terminal device 10B inputs an instruction indicating the intention to register the personal identification information from the input unit 103. Based on this operation input, the terminal device 10B transmits information indicating the intention to register the personal identification information and the user ID of the terminal device 10B to the information management server 20 (step S300). When the information management server 20 receives the information indicating the intention to register the personal identification information and the user ID, it transmits request information for requesting the reading of the personal card to the terminal device 10B (step S301). Here, the personal card may be any medium capable of performing personal identification. For example, it may be any one of a my number card, a driver's license, a health insurance card, an electronic device (such as a smartphone, a tablet, etc.) equipped with the function of a my number card, etc.

[0073] When the terminal device 10B receives the request information for requesting the reading of the personal card, it displays a message such as "Please let the terminal device read the personal card". When the user of the terminal device 10B confirms this display content, the user causes the personal card he / she holds to be read by the terminal device 10B (step S302). Here, the personal card is equipped with an IC (integrated circuit) chip in which information necessary for personal identification (for example, information capable of individually identifying a living person, etc.) is stored. The terminal device 10B can read the information regarding the living person from this IC chip. When the personal card is a my number card, the terminal device 10B can acquire the basic four information as card information (information regarding the living person) from the my number card. The basic four information includes the user's address, name, date of birth, and gender. Also, here, the case of using a personal card is described, but a unique two-dimensional barcode or the like that can identify information capable of identifying a living person and is difficult to forge may be a medium individually issued to the living person. In this case, the two-dimensional barcode may be photographed by the camera of the terminal device 10B, and information regarding the living person may be extracted from the photographed image.

[0074] When the terminal device 10B acquires information about the user, it transmits the acquired information about the user to the information management server 20 as card information (step S303). Based on the card information received from the terminal device 10B, the information management server 20 performs an identity verification process and determines whether the identity verification is successful. If the identity verification is successful, the information management server 20 transmits to the terminal device 10B a card reading result indicating that the identity verification is successful and request information for requesting the input of additional information (step S304). The additional information may be, for example, the telephone number assigned to the terminal device 10B.

[0075] When the terminal device 10B receives the card reading result and the request information, it displays the card reading result on the display unit 104 and displays a message prompting the input of additional information, such as "Please enter additional information". If the identity verification is successful, a message such as "Identity verification successful" is displayed as the card reading result, and if the identity verification fails, a message such as "Identity verification failed" is displayed as the card reading result. The user of the terminal device 10B checks the card reading result. If the identity verification is successful, the user inputs the additional information and presses the send button. Thereby, the terminal device 10B transmits the additional information to the information management server 20 (step S305). Here, if the additional information is a telephone number, the user may input the telephone number manually. Alternatively, an application having a function capable of acquiring the mobile phone number (for example, "+Message (Plus Message) (registered trademark)" etc. in which the terminal device and the information management server can transmit a message with the telephone number as the destination) may acquire the telephone number assigned to the terminal device 10B and transmit the acquired telephone number to the information management server 20.

[0076] When the information management server 20 receives the additional information and the card information from the terminal device 10B, it transmits to the terminal device 10B the confirmation content (the additional information and the card information) for the received content to be confirmed (step S306). The terminal device 10B displays the confirmation details (card information and additional information) received from the information management server 20 on the display unit 104. As a result, the user of the terminal device 10B can check the confirmation details, and if there are no errors, input the confirmation result into the terminal device 10B by pressing a button such as "Confirmation OK". Based on the fact that the "Confirmation OK" button has been pressed, the terminal device 10B transmits to the information management server 20 that the confirmation has been completed (step S307). When the information management server 20 receives from the terminal device 10B that the confirmation has been completed, it performs a registration process by associating the user ID with the card information and additional information and writing them into the user database in the storage unit 202. Here, the information management server 20 may store the address among the card information received from the terminal device 10B in the user database, or may also store the name among the card information. As a result, the delivery address and name can be obtained from the information where the identity verification has been completed and registered.

[0077] In this way, by performing identity verification using the personal card, obtaining the user's address and registering it in the user database, the address stored in the personal card can be registered as user data. When the personal card is a My Number card, four basic pieces of information can be obtained from the My Number card. The address in the four basic pieces of information matches or has a high degree of consistency with the address to which the real estate ID is assigned. Therefore, by executing the identity verification process, the address in the four basic pieces of information can be obtained as the address of the destination user. As a result, the information management server 20 can obtain the real estate ID using an address with a high degree of consistency as the address used to identify the real estate ID. Also, in step S303, the case where the card information transmitted from the terminal device 10B does not include the real estate ID was explained. However, if the real estate ID can be read from the personal card by performing identity verification, the card information including the real estate ID may be transmitted from the terminal device 10B to the information management server 20. As a result, the information management server 20 can obtain the real estate ID from the terminal device 10B without accessing the real estate ID server 30. In addition, when the real estate ID is not included in the card information, the case of obtaining the real estate ID corresponding to the address obtained as the card information in step S303 has been described. However, the user may be allowed to input the address manually, and the real estate ID corresponding to the manually input address may be obtained.

[0078] In addition, according to the above-described Embodiments 1-1, 1-2, 2-1, and 2-2, since the destination information based on the real estate ID can be provided to the delivery carrier, the reference destination of the address can be made a unified address, and an address without notation variation can be obtained. That is, when the user inputs the address manually or by other means from the terminal device 10, depending on the user, the notation of the address may be different. For example, even if the actual address is denoted as "1-chome 1-banchi 1-go", the user may input "1-1-1", or a character having a similar appearance such as a hyphen, a minus sign, or a macron may be input. Then, although it indicates one address, since the character codes are different, it becomes difficult to distinguish whether the actual address and the address input by the user are the same address. In this case, the delivery carrier may not be able to identify the notation of the user's address. According to the above-described embodiments, the real estate ID corresponding to the user's address is obtained, and the destination information based on this real estate ID is provided to the delivery carrier. Therefore, it is not necessary for the user to provide the delivery carrier with the address input by text input or the like. Therefore, for characters that look similar but have different character codes, such as "‐" (hyphen), "-" (minus sign), and "ー" (macron), if there is a variation in the input method by the user, it may be difficult to identify the address. However, it is possible to provide the delivery carrier with an address (an address without notation variation) that eliminates such variation in the input method. In addition, since the destination information based on the real estate ID can be provided to any delivery carrier, even when deliveries are made from different delivery carriers to the same user, the same address can be provided to each of the plurality of delivery carriers.

[0079] In the above-described embodiment, since the destination information is generated after the identity verification process is performed, the address and name of the user obtained by performing the identity verification can be stored in the user database of the storage unit 202. Then, the destination information can be generated using the stored address. In this case, the destination information generation unit 205 may generate the destination information so as to include the name of the user stored in the user database in this destination information. Thereby, it is possible to notify the delivery service provider server of the destination information including not only the address of the delivery destination but also the name.

[0080] Also, according to the above-described embodiment, since the address based on the real estate ID can be provided to the delivery service provider so as to be recognizable as the address of the delivery destination, it is possible to eliminate the variation in the address notation, and it is also possible to avoid the situation where an address with a part of the delivery destination address (for example, a branch number, etc.) omitted is designated as the delivery destination address.

[0081] In the above-described embodiment, the case where the identity verification process is performed for the user of the delivery destination has been described, but the identity verification process may be performed for the user of the delivery requester. When the identity verification process is performed for the user of the delivery requester, the address of the delivery requester can be specified. Generally, a delivery note describes the address and name of the delivery destination and the address and name of the delivery requester. Therefore, the address obtained by performing the identity verification process can be used as the address of the delivery requester. Further, the information management server 20 may acquire the real estate ID corresponding to the address obtained by performing the identity verification process, and generate delivery requester information, which is information capable of specifying the address of the delivery requester using this real estate ID, and transmit it to the delivery service provider server. Thereby, if it is necessary to return the delivered item to the delivery requester, it can be returned to the address based on the real estate ID. Also, even if the real estate ID is not used, it may be returned to the address obtained by performing the identity verification process.

[0082] Also, in the above-described embodiments, even if the identity verification process has not been performed for at least one of the user who is the delivery requester and the user who is the recipient, any of the processes of the above-described Embodiments 1-1, 1-2, 2-1, and 2-2 may be executed. For example, even if the identity verification process shown in FIG. 9 above has not been performed, it is sufficient that the user's name and address are registered as user information in the user database. Also, when user information has not been registered in the user database, the user may be asked to input the address and name from the terminal device 10 at any stage of providing the destination information. Here, even if the identity verification process has not been performed, a real estate ID corresponding to the user's address can be obtained, and by providing the real estate ID to the delivery company, the delivery company can be made to grasp the address in a state where there is no variation in the address notation.

[0083] In the above-described embodiments, the case where the information management server 20 and the real estate ID server 30 are separate servers has been described. However, the function of the real estate ID server 30 may be incorporated into the information management server 20 and configured as one server. Also, the information management server 20 and the real estate ID server 30 may be configured as cloud servers. Also, the information management server 20 and the real estate ID server 30 may be managed by different operators.

[0084] Also, in the above-described embodiments, the case where the information management server 20 stores the addresses of each user in advance has been described. However, the address does not necessarily have to be registered. In this case, for the address of the recipient user, the user of the terminal device 10B may be asked to input it via the input unit 103 at the stage of generating the destination information. In this case, by asking the user to input not only the address but also the name, it is not necessary to register the user in advance in the information management server 20.

[0085] The terminal device 10 or the information management server 20 in the above-described embodiment may be implemented by a computer. In that case, a program for realizing this function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to realize it. Here, the "computer system" shall include hardware such as an OS and peripheral devices. Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, etc., and a storage device such as a hard disk built in a computer system. Furthermore, the "computer-readable recording medium" also includes those that dynamically hold a program for a short time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and those that hold a program for a certain period of time, such as a volatile memory inside a computer system serving as a server or a client in that case. Also, the above program may be for realizing a part of the above-described functions, and may further be realized in combination with a program already recorded in the computer system, or may be realized using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0086] As described above, the embodiments of the present invention have been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and designs and the like within the scope not departing from the gist of the present invention are also included.

Explanation of Reference Numerals

[0087] 10 Terminal device 10A Terminal device 10B Terminal device 11 Terminal device 20 Information management server 30 Real estate ID server 40 EC site server 50 Delivery company server 51 Delivery Service Provider Server 101 Communication Unit 102 Memory Unit 103 Input Unit 104 Display Unit 105 Destination Information Acquisition Unit 106 Destination Information Provision Unit 107 Control Unit 110 Input Unit 201 Communication Unit 202 Memory Unit 203 Acquisition Unit 204 Delivery Service Provider Identification Information Acquisition Unit 205 Destination Information Generation Unit 206 Real Estate ID Acquisition Unit 207 Destination Information Transmission Unit 208 Control Unit NW Network S Destination Information Management System

Claims

1. An acquisition unit that acquires, from the terminal device of the destination, a notification indicating agreement to notify the delivery requester of destination information based on a real estate ID corresponding to the address of the destination to which the item to be delivered is to be delivered; A destination information transmission unit that transmits the destination information to the terminal device of the delivery requester when the notification is acquired; A delivery destination information management system having the above.

2. An acquisition unit that acquires, from the terminal device of the destination, a notification indicating agreement to generate destination information based on a real estate ID corresponding to the address of the destination to which the item to be delivered is to be delivered, the destination information being notified to the delivery requester of the item to be delivered; A destination information transmission unit that transmits the destination information generated based on the notification to the terminal device of the destination when the destination information is generated; A delivery destination information management system having the above.

3. Having a delivery company identification information acquisition unit that acquires delivery company identification information for identifying a delivery company; The destination information is destination information to which the delivery company identification information is added; The destination information transmission unit transmits the destination information to which the delivery company identification information is added. The delivery destination information management system according to Claim 1 or Claim 2.

4. The acquisition unit acquires, from the terminal device of the destination, a notification indicating agreement to notify the delivery requester of destination information based on a real estate ID corresponding to the address of the destination to which the item to be delivered is to be delivered; When the notification is acquired, the destination information transmission unit transmits the destination information to the terminal device of the delivery requester. A delivery destination information management method.

5. The acquisition unit acquires, from the terminal device of the destination, a notification indicating agreement to generate destination information based on a real estate ID corresponding to the address of the destination to which the item to be delivered is to be delivered, the destination information being notified to the delivery requester of the item to be delivered; When the destination information is generated, the destination information transmission unit transmits the destination information generated based on the notification to the terminal device of the destination. A delivery destination information management method.

Images