ES2703127T3 - Systems and methods to electronically sign a delivered package - Google Patents

Abstract

A method comprising: receiving, on a smartphone (102; 504), authorization to receive a delivery of at least one physical package requested by a particular order part, where authorization includes receiving a private key associated with the part of particular order; identify (302) that at least one physical package is in transit; request (304) that at least one physical package be delivered to a location associated with the smartphone (102; 504); allow (308) a second party delivering the package to register at the location through the use of a mobile device (104; 506) that is associated with at least one physical package, where the registration comprises a near field communication stroke between the smartphone (102; 504) and the mobile device (104; 506), wherein the smartphone (102; 504) acts as a near field communication tag; receiving (310), on the smartphone (102; 504), an encrypted electronic token associated with at least one physical package designated for delivery to a destination, the electronic token that has been encrypted by a public key associated with the part of particular order, where the encrypted electronic token is received from the mobile device (104) during registration; electronically sign (312) at least one physical package by using the smart phone (102; 504), which includes decrypting the encrypted electronic token with a private key associated with the particular order part, where decryption is performed by the telephone smart (102; 504), and where the particular order part is different from a receiving part associated with the smart phone (102; 504) when the smart phone electronically signs the package; and send the decrypted electronic witness to a server (106) to verify that a party in possession of and / or accompanying the smartphone (102; 504) is authorized to receive the package.

Description

DESCRIPTION

Systems and methods to electronically sign a delivered package

Technical field

The present description generally refers to the field of computerized systems. More particularly, the description refers to computerized systems and methods for signing a delivered package.

Background information

Conventional systems allow a party to order products online, by phone or by mail. For example, by using a computer or mobile device, a party can access a website of a retailer, such as Amazon, to select the desired products and place the order. With the request, a party may include a name and / or address to indicate to whom and where the package should be delivered. For example, a party can indicate its own name and address.

By using a delivery company, the retailer can then send the packages of the order to a party in their name and / or address. In some cases, packages must be signed by a party included in the order. This may be the case, for example, if the package includes valuable, sensitive, or private products. To ensure that an authorized party signs the package, the delivery company can request that the party sign the current identification of the order. The delivery company can then transfer the package to the authorized party after he / she signs it.

In some cases, however, the party receiving the package may want to remain anonymous to the delivery company to maintain their privacy. In addition, some countries may have privacy laws that prohibit the delivery company from tracking and / or registering their consumers' identification information. Therefore, it may be important to allow an authorized party to sign an anonymous package anonymously.

In some cases, a party receiving the package may be in a different location from the location included with the order. Therefore, it may be important to allow the receiving party to receive a package delivered to him / her based on a location in real time.

WO 2009/101549 relates to a mobile device for authenticating a user in a service provider. The authentication process can be based on a response / challenge protocol, where the response is generated from the user's private key.

US 2011/0087887 generally refers to a digital authentication message that provides an irrefutable record that an authentication device and an authenticating device were located at a specific location and time. The authentication message comprises a date and time stamp, a location mark and a digital signature. The digital signature is produced by signing a digital hash with a private key.

DE 202011 101 134 relates to a storage container that can be used to receive the products sent. The storage container has a security module. A private / public key pair is generated in the security module when the storage container is manufactured. At the time of delivery, the carrier enters a delivery code that contains an encrypted shipping code and a signature within the security module. The security module verifies the signature by using the public key of the bearer, and decrypts the encrypted sending code by using the private key of the security module.

Summary

According to the invention, there is provided: a method as mentioned in claim 1; a computer readable medium as mentioned in claim 6; and a system as mentioned in claim 7.

Also described herein is a method comprising: identifying, by use of a mobile device, an encrypted electronic token associated with at least one physical package designated for delivery to a destination, the electronic token that has been encrypted by a first key associated with a particular part; and electronically signing, through the use of the mobile device, at least one physical package, which includes initiating a decryption of the encrypted electronic token with a second key associated with a particular part.

Also described herein is a computer readable medium that stores instructions, which, when executed by at least one processor, cause at least one processor to execute the method comprising: identifying, by the use of a mobile device, an encrypted electronic token associated with at least one physical package designated for delivery to a destination, the electronic token that has been encrypted by a first key associated with a particular part; and electronically signing, through the use of the mobile device, at least one physical package, which includes initiating a decryption of the encrypted electronic token with a second key associated with a particular part.

Also described herein is a system comprising: a mobile receiving device configured to: identify an encrypted electronic token associated with at least one physical package designated for delivery to a destination, the electronic token that has been encrypted by a first key associated with a particular part; and electronically signing at least one physical package, which includes initiating a decryption of the encrypted electronic token with a second key associated with a particular part.

Also described herein is a method executed by the mobile device, the method comprising: identifying an encrypted electronic token associated with at least one designated physical package

for delivery to a destination, the electronic token that has been encrypted by a key associated with a part that is associated with at least one physical package.

It should be understood that the foregoing general description and the following detailed description are illustrative and explanatory only and do not limit the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this description, illustrate some modalities and together with the description, serve to explain the principles of the described modalities.

Figure 1 illustrates an illustrative system for electronically signing a delivered package.

Figure 2 illustrates devices of an illustrative system for electronically signing a delivered package.

Figure 3 illustrates the operations of an illustrative method executed by a mobile receiving device to electronically sign a delivered package.

Figure 4 illustrates the operations of an illustrative method executed by a mobile receiving device to allow an delivered package to be electronically signed.

Figure 5 illustrates an illustrative system for electronically signing a package delivered by a mobile receiving device that is not owned by a party identified with the order.

Figure 6 illustrates the operations of an illustrative method for electronically signing a package delivered by mobile receiving device that is not owned by a part identified in the order.

Detailed description

The present disclosure generally refers to the electronic signature of a package in a manner that is disconnected from the identity and / or location of a signatory party. This may allow a party receiving the packet to protect its identity. This can also offer a receiving party the flexibility to receive the package in a location that is different from a location included with the order.

In the described modes, a party that orders products with a retailer has a public key and a private key, as is generally understood in the art. Private and / or public keys can be maintained through a Public Key Infrastructure (PKI). For example, the public key can be freely distributed, while the private key can only be in the possession of a restricted number of people.

When the order is placed, the retailer can generate an electronic token. The electronic token may be a series of alphanumeric characters, a string of bits, a series of numbers, or any other electronic representation. The electronic token can be generated randomly or can be linked to something, such as a biometrics. For example, an algorithm, such as a hash function, may be executed on some known biometric data of the order part, such as the name of the fingerprint data, to generate the electronic token.

The retailer, or some other party, can encrypt the electronic token with a public key of the order part. The encrypted token may appear as a random string of characters, such as an apparently random string of 1 and 0. The encrypted token is associated with the packet. For example, the encrypted token can be printed as a barcode on the package or stored on an RFID tag in the package. Alternatively or additionally, the encrypted token may be stored in a mobile device of a party delivering the package or in a server associated with the delivery company or a third party.

Another party, such as a party that sends and / or delivers the packet, can encrypt the electronic token. The private public key can be maintained, generated, and / or associated with a party that sends and / or delivers the package.

The order part has a private key that can unlock the encrypted electronic token. The order part may share the private key with another party, such as a receiving party, permanently or for a limited amount of time. The receiving party can determine that the package is out for delivery. The receiving party may indicate that a party delivering the package must deliver it to a current location of a receiving party, or to some other location, instead of a location indicated with the order.

The delivery party may alter its delivery route to deliver the package to a location in a receiving party, for example. A delivering party "registers" at a delivery location with a receiving party.

The delivering party participates in a "hit" near field communication (NFC) with the mobile device of a receiving party to verify that the delivering party has reached the exact location of a receiving party. The NFC hit transfers the encrypted electronic token to the mobile receiving device. The mobile receiving device initiates the deciphering of the electronic token. When the electronic token is successfully decrypted, then the receiving party may be deemed to have executed an electronic signature and the delivering party may leave the package in possession of and / or accompanying the receiving party.

The term "NFC hit" is commonly understood in the art, and may refer to joining two NFC compatible devices, for example, where one acts as an NFC reader / writer and the other acts as an NFC tag for the purpose of exchange of NFC. information. The device that acts as an NFC tag is a smartphone that emulates an NFC tag. Both devices can have reader / writer functionality, and one can initiate sending information to the other or try to receive information from the other, as if the other device were a fixed NFC tag.

As used herein, the term "part" is intended to be broadly applied to a person, group or corporate entity that may place an order, deliver or otherwise participate in the order, fulfillment or delivery of a package.

One or more mobile devices, such as a mobile receiving device, may be associated with a packet; in other words, the one or more mobile devices can be placed with a packet, attached to a packet, or in any other way placed within a closeness of the packet. The package is a physical package designated for delivery to a destination.

The precise location of a mobile device in relation to the package (within, united, within close proximity, or in close proximity, for example) may not matter; what matters is that the one or more mobile devices can effectively collect the type of particular information associated with the package and / or its contents. For example, this information collected by the sensor may include geographic information associated with the package at any given time. For the purposes of this description, a container or package may be a box, envelope or any other medium used to send documentation or products from one point to another. "Products" can refer to the item (s) in the container or package.

Reference will now be made in detail to the illustrative embodiments, the examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout all the drawings to refer to the same or similar parts.

Figure 1 illustrates system 100 for electronically signing a delivered package. The system 100 may include a mobile receiving device 102, the mobile delivery device 104, and / or server 106, connected by the network 108. The mobile delivery device 102 may be in possession of and / or accompanying a party that receives a package sent, while the mobile delivery device 104 may be in possession of and / or accompanying a party delivering the package sent. The server 106 may be associated with the third party application running on the mobile receiving device 102 and / or the mobile delivery device 104. The server 106 may be associated with a delivery company and may store data related to the delivery of the package .

The network 108 may be a shared, public, or private network, may encompass a wide area or local area, and may be implemented through any suitable combination of wired and / or wireless communication networks. In addition, the network 108 may comprise a local area network (LAN), a wide area network (WAN), an intranet, or the Internet. Network 108 may be a network in the cloud, a mesh network, or another type of distributed network. Some combination of mobile receiving device 102, mobile delivery device 104, and / or server 106 can be connected directly, via a wired or wireless connection, instead of connecting through network 108.

The mobile delivery device 104 may accompany a party delivering a package to a designated destination. The mobile delivery device 104 may collect location information, and may publish that location information via the server 106. For example, the mobile delivery device 104 may periodically send its location to the server 106.

The mobile receiving device 102 can track the location of the packet by polling the server 106 about the location of the mobile delivery device 104. The mobile receiving device 102 can further determine from the server 106 whether the packet is in transit to its destination designated, outside for delivery, and / or when the package is expected to be shipped or delivered. In general, the mobile receiving device 102 can retrieve different types of information associated with the order or sending of the packet from the server 106. The mobile receiving device 102 can receive information directly from the mobile delivery device 104.

The mobile delivery device 104 may be on track to deliver the package to an address or location designated with the order. While the mobile delivery device 104 is in the route, the mobile receiving device 102 may indicate to the server 106 that it would like the mobile delivery device 104 to deliver the packet to the current location of the mobile device 104 or some other location. The mobile delivery device 104 may then take an alternate route to deliver the package to the new designated location.

In delivery, the mobile delivery device 104 registers at a delivery location with receiving mobile device 102, and causes an encrypted electronic token to be transferred to the receiving mobile device 102. The receiving mobile device 102 decrypts the electronic token , signing the package anonymously.

System 100 is illustrative, and the amount and distribution of the different entities shown may be different depending on the specific modalities. For example, the components in system 100 can be combined and / or distributed over multiple entities, which include other computers, laptops, mobile phones, tablets, or other computer platforms. Therefore, the configuration described in the system 100 is only an example and is not intended to be limiting.

Figure 2 illustrates devices of an illustrative system 200 for electronically signing a delivered package. The system 200 may include the mobile device 202 and the server 204. The mobile device 202 may be similar to a mobile receiving device 102 and / or mobile delivery device 104 of Figure 1, and the server 204 may be similar to the server 106. Both mobile devices 202 and server 204 may include general purpose computer components configured to execute specific purpose instructions or code to perform certain actions.

The mobile device 202 may include a detection portion 206, which may include one or more software and / or hardware components for collecting data, such as environmental data. For example, the detection portion 206 may collect location information about itself. The location information may include the use of a Global Positioning System (GPS). Alternatively, location information can be determined through cell triangulation, wireless network association, fixed location scan capture, NFC hit, or mobile location scan capture. Some illustrative aspects of the mobile device 202 are described in U.S. applications no. 13 / 351,861 and 13 / 351,852.

The mobile device 202 may further include the central processing unit (CPU) 208 and a memory 210 for processing the data, such as the environmental data collected, the data entered, or the data retrieved from a storage device. The CPU 208 may include one or more processors configured to execute the computer program instructions to execute different processes and methods. The CPU 208 can read the computer program instructions from the memory 210 or from any computer readable medium. The memory 210 may include random access memory (RAM) and / or read only memory (ROM) configured to access and store information and instructions of the computer program. The memory 210 may further include additional memory for storing data and information and / or one or more databases for storing tables, lists, or other data structures.

The mobile device 202 may include the I / O Unit 212 for sending data over a network or any other means. For example, I / O Unit 212 can send data over a network, point-to-point connection, and / or point-to-multipoint either wirelessly or over a cable.

The device 204 may include a CPU 214 and / or a memory 216, which may be similar to the CPU 208 and the memory 210 of the mobile device 202. The storage server / device 204 may further include the database 218. The database 218 may store large amounts of data, and may include a magnetic, semiconductor, tape, optical, or other storage device. In some embodiments, the database 218 may store historical data for audit purposes. The server / storage device 204 may include an I / O Unit 220 to communicate with the mobile device 202. The I / O Unit 220 may be similar to the I / O Unit 212 in the mobile device 202.

The system 200 is illustrative only, and the amount and distribution of the different entities shown may be different depending on the specific modalities. For example, the mobile device 202 may not include the detection portion 206, the CPU 208, and / or the memory 210. The server 204 may be distributed across multiple entities, which include other distribution systems, sensors, computers, laptops, mobile phones, tablets, or other computer platforms. The mobile device 202 can be implemented or distributed in a similar manner on any computer platform. Therefore, the configuration described in the system 200 is only an example and is not intended to be limiting.

Figure 3 illustrates the operations of an illustrative method 300 that can be executed by a mobile receiving device 102 to electronically sign a delivered packet. The method 300 can be executed by the CPU 208 in the mobile receiving device 102. The method 300 can further be executed together with other components shown or not shown in the system 100. As explained, in some implementations, some steps in the method 300 they are optional and can be rearranged. In addition, additional steps may be added to method 300.

To initiate, the mobile receiving device 102 identifies a packet as being in transit (step 302). For example, the mobile receiving device 102 may receive a notification from the server 106 that the packet is out for delivery to a designated destination. The device 106 may be monitoring the status of the mobile delivery device 104 to determine its location and whether or not it is associated with the packet. When the server 106 determines that the package is out for delivery, with the mobile delivery device 104, can send the notification to the receiving mobile device 102.

Then, the mobile receiving device 102 may send a message to the server 106, requesting that the packet be delivered to the location of the receiving mobile device 102 (step 304). For example, a party in possession of and / or accompanying the mobile receiving device 102 may be out for lunch, and may want the package delivered to its current location instead of a designated location with the original order. The mobile receiving device 102 can specify its current location for delivery if it determines that the package will be delivered within a certain time (eg, 30 minutes), for example. Alternatively, the mobile receiving device 102 may specify another location for delivery if the package will be delivered in a longer time (e.g., in 2 hours), for example. In this way, the mobile receiving device 102 can dynamically adjust the delivery location based on the circumstances in real time. The delivery company may charge extra for a change in the delivery location.

The mobile receiving device 102 can then determine whether or not the packet is ready to be received (step 306). For example, the mobile receiving device 102 may receive a notification from the server 106 that the mobile delivery device 104 is within a predetermined distance or time period of the receiving mobile device 102. This determination may be made in accordance with information of the GPS. For example, the server 106 can monitor the location of the mobile delivery device 104 and send a notification to the receiving mobile device 102 when the location information (such as GPS coordinates) shows the mobile delivery device 104 in the same or similar ones. GPS coordinates that the mobile receiving device 102. For example, the server 106 can notify the mobile receiving device 102 that the package is ready to be received when the mobile delivery device 104 is near the main door or the loading dock.

If the packet is not ready to be received, then the mobile receiving device 102 keeps checking until the packet is ready to be received. If the packet is ready to be received, then the mobile receiving device 102 can allow the mobile delivery device 104 to register at a delivery location, for example, on the mobile receiving device 102 (step 308). This can be done by using a form of location tracking that is more accurate than GPS. The mobile delivery device 104 exchanges short range messages with the mobile receiving device 102 by a NFC hit. The registry can ensure that a delivery party actually delivers the package directly to a delivery location and / or reception party. The mobile receiving device 102 can send a registration confirmation to the server 106. In this way, the server 106 can ensure that the delivering party delivered the packet at the location requested by the recipient.

Then, the mobile receiving device 102 accesses an encrypted electronic token associated with the packet (step 310). During registration, the mobile delivery device 104 transfers the encrypted electronic token to the mobile receiving device 102. Additionally, the mobile receiving device 102 can scan or read the encrypted electronic token from the package, such as a bar code or an RFID tag The server 106 may send the encrypted electronic token to the mobile receiving device 102 via the network 108 or in any other way, either at the time of registration or before, such as the time at which the product was ordered.

The encrypted electronic token is encrypted by a public key associated with a particular party, such as a party who made the original order, or some other party. Because the key is public, it can be accessible to the retailer, for example, who may have generated a witness and encrypted the witness generated when the order was placed or sent, or at any other time.

The mobile receiving device 102 then electronically signs the packet upon deciphering the encrypted token (step 312). The mobile receiving device has a corresponding private key of the particular part

The private key is able to undo the encryption the witness that was made by using the public key. Therefore, the mobile receiving device 102 is able to decrypt the encrypted electronic token to determine the original electronic token. The mobile receiving device 102 sends the decrypted electronic token to the server 106 to verify that a party in possession of and / or accompanying the mobile receiving device 102 is authorized to receive the packet.

The mobile receiving device 102 may require additional security measures from a party that owns it, so that the party can electronically sign the packet. For example, the mobile receiving device 102 may require a password or biometric scan to allow a party to use the functionality described herein, which includes the ability to electronically sign a packet. The private key can be transferred by itself in encrypted mode and never be directly accessible by the user. Instead, the private key can only be accessible to an application running on the mobile receiving device 102 and / or server 106. For example, the application can be executed in a protected area on a mobile device 102 and / or server 106

When the receiving mobile device 102 sends the decrypted electronic token back to the server 106, and if the decrypted electronic token matches the original unencrypted token, then the server 106 can verify that the party receiving the packet is authorized. The device 106 may have to communicate with some other party, such as a retailer, to verify that the decrypted token matches the original unencrypted witness. In this way, server 106 may never need to gather identity information from a receiving party, which could protect the privacy of the receiving party and can ensure compliance with local laws.

Then, the mobile receiving device 102 can release the payment associated with the packets (step 314). For example, the order may have been structured to use cash payment on demand (COD). Therefore, when the electronic signature is verified and the delivering party transfers ownership of the package to the receiving party, the payment can be transferred. The receiving party may have the opportunity to inspect the package before confirming that the payment is transferred. This can give the receiving party an opportunity to determine if the product is damaged. Then method 300 can finish.

Figure 4 illustrates the operations of an illustrative method 400 executed by a mobile delivery device 104 to allow an delivered package to be electronically signed. The method 400 can be executed by the CPU 208 in the mobile delivery device 104. The method 400 can be further executed together with other components not shown in the system 100. As explained, some steps in the method 400 are optional and can be rearranged. In addition, additional steps may be added to method 400.

The method 400 starts when the mobile delivery device 104 receives a request to deliver a packet to a location of the receiving mobile device 102 (step 402). The mobile delivery device 104 may receive this request from the server 106, which in turn may have received the request from the mobile reception device 102. The mobile delivery device 104 may receive the request from the mobile reception device 102 directly or through other part. When the mobile delivery device 104 receives this message, it may already be in transit. For example, the mobile delivery device 104 may be traveling with a delivery part that is out for delivery with a plurality of packets, which includes the packet to be delivered to a location of the receiving mobile device 102. In one example, a delivery part can be a driver in possession of and / or accompanying the mobile delivery device 104. The delivery party can have many packages in its truck for delivery in a shift, such as in a day. The packages in the truck can be linked to the mobile delivery device 104. In this way, a location of the packages and a delivery part can be monitored by using location information collected by the mobile delivery device 104.

The mobile delivery device 104 may then interrupt a previously scheduled delivery route and establish a destination as the location received from the receiving mobile device 102 (step 404). For example, the mobile delivery device 104 may intend to deliver the package to a location in the package order, but may review a pre-planned route so that the package can be delivered to the location specified by the receiving mobile device. The mobile delivery device 104 may deliver the packet immediately to a location of the receiving mobile device 102 or may do so some time later depending on one or more factors such as: the synchronization of the delivery information provided by the mobile device of the mobile device. reception 102, traffic conditions, weather conditions, etcetera.

The mobile delivery device 104 may then determine whether or not the package is ready to be delivered (step 406). For example, the mobile delivery device 104 may determine that the package is ready to be delivered when it arrives at the location of the receiving mobile device 102. If the mobile delivery device 104 determines that the package is not yet ready to be delivered, then it continues verifying

Alternatively, if the mobile delivery device 104 determines that the package is ready to be delivered, then the mobile delivery device 104 may be registered at a delivery location, for example, that of the mobile receiving device 102 (step 408). The mobile delivery device exchanges a short distance message with the mobile receiving device 102, by a NFC hit, to confirm that it delivered the packet to the receiving part and not only in a close vicinity.

The mobile delivery device 104 may be registered in a stationary NFC tag. The stationary label can be located, for example, on a loading dock, door, or other location. The mobile delivery device 104 can write to the NFC tag to create a record that was registered at the location of the NFC tag. Alternatively or additionally, the mobile delivery device 104 may read from the NFC tag.

Then, the mobile delivery device 104 sends an encrypted electronic token to the mobile receiving device 102 (step 410). This occurs as part of the NFC hit, as part of the registration process.

The mobile receiving device 102 initiates the decryption of the encrypted electronic token, and the server 106 can verify that the decryption was successfully executed. Therefore, the mobile delivery device 104 can receive confirmation that the mobile receiving device correctly deciphered the electronic token, for example, from the server 106 (step 412). This is an indication to the mobile delivery device 104 that the mobile receiving device 102 has successfully electronically signed the packet. Therefore, the mobile delivery device 104 can indicate to a delivering party that the shipment is complete and then he / she can transfer ownership of the package to a receiving party and leave.

In some embodiments, the mobile receiving device 102 can release the payment upon confirmation that the electronic signature was accepted by the server 106. Therefore, the mobile receiving device can receive an indication from the server 106 that the payment was released. The mobile delivery device 104 may not transfer possession of the package unless the payment is first released by a receiving party. Then method 400 can finish. As described, a delivered package can be electronically signed by a party that does not have to provide any personally identifiable information such as their name, fingerprints, or other biometrics. Instead, a receiving party may only have access to a private key for the purpose of deciphering an electronic token associated with the package. The electronic token may have been encrypted by a public key of a party that placed an order for products in the package. The private key, therefore, is the complement of the public key, because it is capable of deciphering the encryption made through the use of the public key. The possession of the private key can be strictly controlled. In this way, a receiving party can prove that he / she is linked to the order part and is authorized to receive the package by virtue of the fact that he / she has access to the private key. And the receiving party can prove that he / she has access to the private key by allowing decryption of the encrypted token, which, generally, only the private key can fulfill.

Therefore, a party that receives the package may be different from a party that ordered the package. For example, a party that orders the package can share its private key with the party receiving the package to ensure that the receiving party is authorized to receive it.

Figure 5 illustrates an illustrative system 500 for electronically signing a package delivered by a mobile receiving device that is not owned by a party identified with the order. System 500 may include ordering device 502, mobile receiving device 504, and / or mobile delivery device 506. Mobile receiving device 504 may be similar to mobile receiving device 102 of Figure 1. Similarly , the mobile delivery device 506 may be similar to the mobile delivery device 104.

The system 500 may further include a messaging server 508, third-party application server 510, and / or sales server 512. The ordering device 502, the mobile receiving device 504, the mobile delivery device 506, the server messaging 508, third-party application server 510, and / or sales server 512 can be connected directly or via network 514. Network 514 can be similar to network 108 of Figure 1.

An order part can place a product order from the sales server 512, through the use of an ordering device 502. The ordering device 502 can be any type of computing device, such as a desktop, laptop, tablet, or mobile phone, for example. The order part can be associated with a private key and a public key. The private key can only be accessible for the part of the order and other parts to which the order part grants permission. The public key, however, can be administered by a PKI and can be publicly available.

Therefore, after the order is placed, the sales server 512 can have access to the public key of the order part. The sales device can generate a token, such as a string of letters and / or numbers, and can encrypt the token by using the public key of the ordering device. The sales server 512 may pass the original witness and / or the encrypted token to the third-party application server 510 and / or the messaging server 508. The messaging server 508 may include the electronic token encrypted in the packet as a code bar and / or can send the encrypted electronic token to the mobile delivery device 506.

When the ordering device 502 places the order, it can indicate an address for delivery. The ordering device 502 may indicate that the package must be signed before it is transferred to a receiving part. The order part can receive the package by itself, or it can delegate to another party to receive the package. To delegate to the other party, the order part may need to ensure that the receiving party has access to the private key of the order part.

Therefore, the order part can provide authorization to the receiving party by electronically transferring the private key to the mobile receiving device 504. In some embodiments, the private key can be stored by itself in an encrypted format. The private key can be used only for a specific time or limited to a number of uses.

The private key can be maintained on a remote server, such as a third-party application server 510. In that case, the ordering device 502 can ensure that the mobile receiving device 504 is able to access the private key or initiate a decryption by using the private key stored in the third-party application server 510.

The third-party application server 510 can be involved in enabling the electronic signature of the package. The third-party application server can be involved or linked with the organization that created the application running on the mobile receiving device 504 and / or the mobile delivery device 506.

After receiving mobile device 504 is authorized to receive the package, it can electronically sign the package on delivery. For example, the mobile receiving device 504 can gain access to the encrypted electronic token, and can decipher the encrypted electronic token. The decryption occurs in the mobile receiving device 504.

Figure 6 illustrates the operations of an illustrative method 600 for electronically signing a package delivered by a mobile device of via 504 that is not owned and / or operated by a party identified in the order. The method of Figure 6 is not the subject of the claims. Method 600 may be executed by CPU 208 and / or 214 in some combination of ordering device 502, mobile receiving device 504, and third-party application server 510, for example. The method 600 can be further executed together with other components not shown in the system 500. As explained, some steps in the method 600 are optional and can be rearranged. In addition, additional steps can be added to method 600.

To start, ordering device 502 can access sales server 512 to order a package (step 602). The sales server 512, by using a public key associated with the order part, can generate and encrypt a token when the order is placed. The sales server 512 can send the encrypted and unencrypted tokens to the messaging server 508. The encrypted electronic token can be passed to the mobile receiving device 504, messaging server 508, and / or third-party application server 510. And the witness unencrypted electronic mail may be sent to the messaging server 508 for the purpose of verifying the decryption of the encrypted electronic token.

Then, the ordering device 502 can authorize the mobile receiving device 504 to receive the packet (step 604). For example, ordering device 502 can electronically transfer its private key to mobile receiving device 504. Ordering device 502 can authorize mobile computer 504 to access the private key on the third-party server 510, or instruct the third-party server 510 to perform decryption if the private key is stored on the third-party application server 510.

The mobile receiving device 504 may be owned, accompanied, and / or operated by a different part of the order part. The mobile receiving device 504 may be owned, accompanied, and / or operated also by a different part of any part associated with the order. Identification of the part that owns, accompanies, and / or operates the mobile receiving device 504 may be unknown to the retailer, the delivery company, and / or the order part.

Then, the mobile receiving device 504 can determine if the packet is in transit, for example, by consulting the messaging server 508 (step 606). For example, the mobile receiving device 504 can determine that the package is out on the truck for delivery that day. When the packet is determined to be in transit, the mobile receiving device 504 may send location information to the messaging server 508 (step 608). The location information may indicate a location in which the mobile receiving device 504 can receive the packet.

The mobile receiving device 504 then determines whether the packet is ready to be received (step 610). For example, the mobile receiving device 504 may receive an indication from the messaging server 508 that mobile delivery device 506 is approaching or is in the location indicated by the mobile receiving device 504 in step 608, for example.

If the packet is ready to be received, then the mobile receiving device 504 may allow the mobile delivery device 506 to register at a delivery location, for example, that of the mobile receiving device 504 by the use of a NFC hit. , Bluetooth message, or RFID scan (step 612), for example. Then, the mobile receiving device 504 can access an encrypted electronic token associated with the packet, and can send the encrypted electronic token to the third-party application server 510 (step 614). The third-party application server 616, after receiving the encrypted electronic token, can determine that the mobile receiving device 504 is authorized to instruct the decryption. Then, third-party application server 616 can decrypt the electronic token with a private key from the order part (step 616).

The third-party application server 616 can then send a message to the messaging server 508 with the decrypted token. If the decrypted witness matches the original witness before encryption, then the messaging server can determine that the packet has been signed electronically by an authorized party.

The decryption may occur on the mobile receiving device 504 instead of the third-party application server 510. In that case, the mobile receiving device 504 could send the decrypted token to the messaging server 508, for example, to verify that it matches the original unencrypted witness generated by the sales server 512, for example. Then method 600 can finish.

While certain characteristics and embodiments of the invention have been described, other embodiments of the invention will be apparent to those skilled in the art from consideration of the description and practice of the embodiments of the invention described herein. In addition, although aspects of the embodiments of the present invention have been described in part as software, computer executable instructions and / or other data stored in the memory and other storage means, one skilled in the art will appreciate that these aspects can also be stored in or read from other types of tangible, non-transient, computer-readable media, such as secondary storage devices, such as hard drives, floppy disks or a CD -ROM, or other forms of RAM or ROM. In addition, the steps of the methods described can be modified in various ways, including by rearranging the steps and / or inserting or deleting steps, without departing from the principles of the invention.

It is intended that the description and examples be considered as illustrative only, with a true scope of the invention which is indicated by the following claims.

Claims (14)

Claims 1. A method comprising: receiving, on a smartphone (102; 504), authorization to receive a delivery of at least one physical package ordered by a particular order part, wherein the authorization includes receiving a private key associated with the particular order part; identifying (302) that at least one physical package is in transit; requesting (304) that at least one physical package be delivered to a location associated with the smartphone (102; 504); allowing (308) a second party delivering the package to register at the location by using a mobile device (104; 506) associated with at least one physical packet, wherein the record comprises a near field communication hit between the smartphone (102; 504) and the mobile device (104; 506), wherein the smartphone (102; 504) acts as a near-field communication tag; receiving (310), on the smartphone (102; 504), an encrypted electronic token associated with at least one physical package designated for delivery to a destination, the electronic token that has been encrypted by a public key associated with the party's part; particular request, wherein the encrypted electronic token is received from the mobile device (104) during registration; electronically sign (312) at least one physical package by using the smartphone (102; 504), which includes deciphering the encrypted electronic token with a private key associated with the particular order part, where the decryption is made by the telephone intelligent (102; 504), and wherein the particular order part is different from a reception part associated with the smartphone (102; 504) when the smartphone electronically signs the package; Y sending the decrypted electronic token to a server (106) to verify that a party in possession of and / or accompanying the smartphone (102; 504) is authorized to receive the packet. The method of claim 1, wherein the private key is stored in the smartphone (102; 504) in a protected format. 3. The method of claim 1, wherein electronically signing (312) the package completes the delivery of the package. The method of claim 1, wherein requesting (304) that the packet be delivered to a location associated with the smartphone (102; 504) causes a second party delivering the packet to deviate from a scheduled delivery route . 5. The method of agreement of claim 1 further comprising: release (314) a payment associated with the package after electronically signing (312) the package. 6. A computer-readable medium that stores program instructions, which, when executed by at least one processor, causes at least one processor to execute the method of any of the preceding claims. 7. A system comprising: a smartphone (102; 504) configured for: receive authorization to receive delivery of at least one physical package ordered by a particular order part, wherein the authorization includes receiving a private key associated with the particular order part; identify that at least one physical package is in transit; request that at least one physical package be delivered to a location associated with the smartphone (102; 504); enabling a second party delivering the package to register at the location by using a mobile device (104; 506) that is associated with at least one physical package, wherein the smartphone is configured to act as a communication tag of near field, and wherein the record comprises a close field communication stroke between the smartphone (102; 504) and the mobile device (104; 506); receiving an encrypted electronic token associated with at least one physical package designated for delivery to a destination, the electronic token that has been encrypted by a public key associated with the particular order part, wherein the encrypted electronic token is received from the device mobile (104) during registration; electronically sign at least one physical package, which includes deciphering the encrypted electronic token with a private key associated with the particular order part, wherein the decryption is made by the smartphone (102; 504), and where the order part particular is different from a reception part associated with the smartphone (102; 504) when the smartphone electronically signs the package; and sending the decrypted electronic token to a server (106) to verify that a party in possession of and / or accompanying the smartphone (102; 504) is authorized to receive the packet. The system of claim 7, wherein the smart phone (102; 504) is further configured to store the private key in a protected format. 9. The system of claim 7 further comprises: an ordering device (502) configured to order the package according to the user input from the order part, wherein the order part is different from a receiving part associated with the smartphone (102; 504) when the smartphone electronically signs the package. 10. The system of claim 7, wherein electronically signing the package completes the delivery of the package. The system of claim 7 further comprises the mobile device (104; 506), and wherein the smart phone (102; 504) is further configured to: determining, from the location information associated with the mobile device (104; 506), that the packet is in transit; Y sending a request to request that the mobile device (104; 506) deliver the packet to a location associated with the smartphone (102; 504). The system of claim 11, wherein the mobile device (104; 506) is configured to: generate a new delivery route that deviates from a previously planned delivery route. The system of claim 7, wherein the smartphone (102; 504) is further configured to: release a payment associated with the package after electronically signing the package. The system of claim 7 further comprises the mobile device (104; 506), wherein the mobile device is configured to register at a delivery location.