AU2017216540A1 - Method and system for providing proof of delivery - Google Patents

Abstract

A method and system for providing proof of delivery, the method including the steps of: receiving from a portable computing device: a proof of delivery request, and location information representing the geophysical location ofthe portable computing device; obtaining a signature code upon receiving the proof of delivery request; transmitting the signature code to the portable computing device; and storing proof of delivery information in a proof of delivery database, the proof of delivery information including: the signature code; authorisation information associated with a recipient's authorisation for delivery to be effected using the signature code in the absence of the recipient; the location information; and time information representing the date and time of the delivery. H:\nilb\Interwoven\NRPortbl\DCC\NLB\11083629_1.docx - 16/8/17 Receive a proof of delivery request and location information 210 from a portable computing device 4, Obtain a signature code upon receiving 220 the proof of delivery request Transmit the signature code to the portable computing device 230 Store proof of delivery information in 240 a proof of delivery database Fig. 2

Description

METHOD AND SYSTEM FOR PROVIDING PROOF OF DELIVERY Technical Field [001] The present invention generally relates to a method and system for providing proof of delivery, e.g., for providing proof that an item, such as mail, a package or a parcel, has been delivered to an intended address.

Background [002] With the rapid rise of e-commerce (including Internet shopping), there has been a rapid increase in the number of deliveries, particularly parcel deliveries, being made. However, in many circumstances the intended recipient is not present at the delivery address at the time the delivery is attempted. Presently, if a courier or other delivery person leaves a delivery item at the intended delivery address in the absence of the recipient, it can be difficult to prove that the delivery person actually arrived at the intended address and made a successful delivery.

[003] “Signature on delivery” (SOD) services may be employed to provide evidence of delivery. Typically, when a courier or a delivery person delivers a SOD item to an intended address, the recipient of the item needs to be physically present to receive the delivery, and to acknowledge receipt of the delivery, for example by signing a paper receipt or on a handheld electronic device.

[004] However, in some circumstances the intended recipient may not be at the delivery address when the SOD delivery is attempted (possibly because the precise time of delivery is not known, or because it is otherwise onerous or inconvenient for the recipient to be present at the delivery address when the SOD deliveries arrive). If the recipient is not present to take and acknowledge receipt of the item, delivery cannot be effected. The delivery company will then need to re-attempt delivery, or deliver the item to an alternative address for subsequent pick-up by the recipient. This adds substantial cost and inconvenience to the item delivery process.

[005] It is desired to address or ameliorate one or more disadvantages or limitations associated with the prior art, or to at least provide a useful alternative.

Summary [006] In a first aspect, the present invention provides a computer-implemented method for providing proof of delivery, including the steps of: receiving from a portable computing device: a proof of delivery request, and location information representing the geophysical location of the portable computing device; obtaining a signature code upon receiving the proof of delivery request; transmitting the signature code to the portable computing device; and storing proof of delivery information in a proof of delivery database, the proof of delivery information including: the signature code; authorisation information associated with a recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient; the location information; and time information representing the date and time of the delivery.

[007] In a second aspect, the present invention provides a computer-implemented method executed on a portable computing device, the method including the steps of: transmitting to a server: a proof of delivery request, and location information representing the geophysical location of the portable computing device; receiving a proof of delivery confirmation from the server, indicating that proof of delivery information has been stored by the server, the proof of delivery information including: a signature code generated by the server; authorisation information associated with a recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient; the location information; and time information representing the date and time of the delivery; wherein the proof of delivery confirmation includes the signature code.

[008] In a third aspect, the present invention provides a system for providing proof of delivery, including a portable computing device and one or more electronic processing devices, the one or more electronic processing devices being configured to perform the method of the first aspect.

Brief Description of the Drawings [009] Some embodiments of the present invention are hereinafter described, by way of example only, with reference to the accompanying drawings, wherein: [010] Figure 1 is a schematic diagram of an exemplary system for providing proof of delivery; [Oi l] Figure 2 is a process flow of an exemplar}' method executed by a seiver for providing proof of delivery; [012] Figure 3 is a process flow of an exemplary method executed by a portable computing device for providing proof of delivery; [013] Figure 4 is a schematic diagram of an example of the server shown in Figure 1; [014] F igure 5 is a schematic diagram of an example of the portable computing device shown in

Figure 1; [015] Figure 6 is an exemplary user interface for a recipient to create a delivery profile; [016] Figure 7 is an example of a delivery profile reference sheet; [017] Figure 8 is an exemplary user interface that allows a recipient to select whether to receive a notification when the unique barcode associated with their delivery profile is scanned; [018] Figure 9 is an exemplary user interface showing a recipient’s delivery instructions and authorisation information; [019] Figure 10A is an exemplary user interface which allows delivery personnel to request a signature code; [020] Figure 10B is an exemplary user interface showing a received signature code and a sent notification of a safe delivery; [021] Figure 10C is an exemplary user interface showing a sent notification of a missed delivery; [022] Figure 11 is an exemplar}' user interface for displaying a delivery history of a recipient; and [023] Figure 12 is an exemplary structure of a proof of delivery (PoD) system according to some embodiments.

Detailed Description [024] In the following description, the term "delivery item" refers to an item to be delivered. Examples of such items include: an item of mail, a parcel, and a package delivered by private or public delivery organisation (such as a courier or postal service).

[025] The term "recipient" refers to a person or entity to which the delivery item is intended to be delivered, and may also be known as the receiver, the addressee, the consignee, the household, or the customer or consumer of the delivery service.

[026] The term "delivery address" refers to an address to which the delivery item is intended to be delivered, which may be any suitable type of address or location, including but not limited to: a home address, a business address, or a specified location within a building or property. A delivery address may be associated with one recipient, or a plurality of recipients.

[027] The term "delivery personnel" is intended to refer to one or more people or an entity that is responsible for delivering the delivery item. The delivery personnel may also be known as the delivery person, the delivery driver, the courier, the postman / postwoman, or the consignor.

[028] The term “delivery company” is intended to refer to an enterprise or organization providing delivery services, and which employs the delivery personnel. A delivery company may be a postal service, a courier company, or a shipping company. It may include an online shop or online shopping website, where that shop or website arranges its own deliver}'.

[029] An example of a system for providing proof of delivery will now be described with reference to Figure 1.

[030] In this example, the system 100 includes at least one electronic processing device for providing proof of delivery, for example a server 110. The server 110 is in communication, via one or more communication networks 140, with at least one portable computing device 120 earned by delivery personnel 130. The server 110 is also in communication with a local or remote proof of delivery database 150 which stores proof of delivery information.

[031 ] The communication between the server 110 and the portable computing device 120 may be direct communication, or indirect communication through one or more intermedia electronic processing devices such as a server owned or operated by the delivery company.

[032] The portable computing device 120 may include, for example, a scanner, a mobile telephone handset, a tablet computer, or any other appropriate portable electronic device.

[033] In some examples, the server 110 may further be in connection with one or more of the following: a local or remote signature code database 160; a local or remote delivery profile database 170; a local or remote address database 180; one or more terminal devices 190.

[034] Although the databases 150,160,170, and 180 are shown as separate databases in Figure 1, in some embodiments some or all of them may be configured as a single database which stores all the relevant data for providing proof of delivery, or be configured based on the same data storage hardware.

[035] An example of a method 200 executed by the server 110 for providing proof of delivery will now be described with reference to Figure 2.

[036] At step 210, the server 110 receives from the portable computing device 120: a proof of delivery request, and location information representing the geophysical location of the portable computing device.

[037] The proof of deliver}' request and the location information is received from the portable computing device via the one or more communication networks 140.

[038] The proof of delivery request may be generated and sent by the portable computing device in response to a user input on the portable computing device, for example by pressing a hardware button, by tapping or clicking a button displayed on a touchscreen, or by any other suitable form of user input.

[039] In some examples, the location information may include at least geophysical location information obtained by a positioning module of the portable computing device, such as a GPS sensor, a Wi-Fi positioning module, a cellular network positioning module, or the like.

[040] In some other examples, the location information may include at least scanned information obtained by a scanning module of the portable computing device 120. For example, the portable computing device 120 may be a handheld scanner that includes a central processor, a scanning module, a display, a user input device (which may be combined with the display), and a communication module, where the scanning module may be used to scan machine readable symbols or tags (such as a Bluetooth beacon or a Near Field Communication tag). Alternatively, the portable computing device may be a smart phone which includes a processor, a digital camera, a touch screen, and a communication module, where the digital camera may function as a scanning module by acquiring a digital image of a symbol (such as a barcode or QR code).

[041] In some further examples, the location information may include both the geophysical location information and the scanned information.

[042] Upon receiving the proof of delivery request, the server 110 obtains a signature code at step 220.

[043] The signature code is a code, sign or token that is uniquely generated and may be associated with a particular delivery. The code, sign or token may taken any suitable form, including one or more of the following: words, letters, numbers, figures, or any other suitable symbols. For example, the signature code may be a series of letters, a series of numbers, a combination of alphanumeric characters, or a machine readable symbol such as a two-dimensional barcode.

[044] The signature code may be randomly generated by the server 110, for example by using methods of generating random digital codes that are known to a person skilled in the art.

[045] Alternatively, as shown in Figure 1, the server 110 may further be in communication with a local or remote signature code database 160 which stores a plurality of signature codes. At step 220 the server 110 may select one signature code from the plurality of predetermined signature codes stored in the signature code database 160.

[046] In the selection or generation of the signature code, the server 110 may determine whether a selected or generated signature code has previously been used, i.e., whether it has been transmitted to a portable computing device. If it is determined that the selected or generated signature code has been used, the server 110 may select or generate a different signature code. This process may be repeated until a signature code that has never been used is selected or generated. In some examples, the server 110 may further record date and/or time information representing when the signature code is used, and may allow reuse of a signature code if a predetermined time period (e.g., 6 months, 1 year, 3 years, or the like) has passed since the last use of the same signature code.

[047] Further, when the signature code is selected from the plurality of predetermined signature codes that are stored in the signature code database 160, the server 110 may cause removal or deletion of the signature code from the plurality of predetermined signature codes, for example by removing or deleting the signature code from the signature code database 160. By removing or deleting the signature code from the signature code database, potential signature code re-use is reduced or avoided.

[048] Next, at step 230, the server 110 transmits the signature code to the portable computing device 120.

[049] Finally, at step 240, the server 110 stores proof of delivery information in the proof of deliver)' database 150. The proof of delivery information includes: the signature code; authorisation information; the location information; and time information representing the date and time of the delivery.

[050] The authorisation information is associated with the recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient.

[051 ] The authorisation information may be information that directly represents the recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient.

[052] Alternatively, the authorisation information may include authorisation identification information associated with a delivery profile stored in a delivery profile database, such as a local or remote delivery profile database 170 as shown in Figure 1, which the server 110 may communicate with.

[053] The delivery profile may include at least information representing the recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient, and other suitable information associated with the recipient.

[054] The authorisation information may simply indicate whether the recipient agrees to authorise the delivery driver to use the signature code (e.g., “Yes” or “No”). The authorisation information may further indicate to what extent or under which conditions the recipient agrees to authorise the use of the signature code (e.g., Yes for all delivery items; Yes only if the item fits in the parcel box; Yes only if the value of the item is under a certain amount; No for all delivery items; etc.).

[055] The delivery profile may further include the recipient’s detailed information, for example one or more of the following: • The recipient’s one or more delivery instructions, instructing the deliver)' personnel on actions to be taken with respect to the delivery item; • The recipient’s name; • The recipient’s address; and • The recipient’s contact details, such as phone number.

[056] The delivery profile may be created at least in part by the recipient, for example by registering with the system 100. Alternatively, the delivery profile may be created by any other appropriate party on behalf of the recipient, such as the operator of the system 100, based on information collected from the recipient.

[057] In addition to the signature code, the authorisation information, the location information, and the time information, the proof of delivery information may further include or contain a reference to other suitable information, for example, one or more of the following: • portable computing device information associated with the portable computing device; • delivery personnel information associated with delivery personnel effecting delivery; • delivery' item information associated with an item being delivered; • recipient information associated with the recipient; • sender information associated with a sender.

[058] Further, although step 230 is performed before step 240 in the example as shown in Figure 2, in some other examples, step 230 may be performed after step 240, or performed at the same time when the step 240 is performed.

[059] An example of a method 300 executed by the portable computing device 120 for providing proof of delivery will now be described with reference to Figure 3.

[060] At step 310, the portable computing device 120 transmits to the server 110: a proof of delivery request, and location information representing the geophysical location of the portable computing device.

[061] Next, at step 320, the portable computing device 120 receives a proof of delivery confirmation from the server 110, the proof of delivery confirmation indicating that proof of delivery information has been stored by the server. As previously described, the stored proof of delivery information includes at least: the signature code generated by the server; authorisation information associated with a recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient; the location information; and time information representing the date and time of the delivery.

[062] The proof of delivery confirmation includes the signature code. The signature code received by the portable computing device may then be displayed on a display of the portable computing device, to allow the delivery personnel to record it, e.g., by writing it down on a paper receipt, or by inputting it into a delivery management system owned or operated by the delivery company. Alternatively, it may be automatically entered into the delivery management system by the computing device.

[063] It will be appreciated that at least in one example, the above described embodiments provide a simple and convenient method for providing proof of delivery. The described method allows the delivery personnel to request or otherwise receive a location-stamped and time-stamped signature code easily and conveniently through a portable computing device, thereby completing the delivery of the item even when the recipient cannot be present. This may allow the delivery personnel and the delivery company to avoid or reduce failure of delivery, and save the time, cost and inconvenience of re-attempting or re-directing delivery.

[064] A number of further features will now be described.

[065] In some examples, when obtaining the signature code, the seiver 110 may further execute the following steps: verifying the proof of delivery request based at least in part on the location information; and generating or selecting the signature code in response to successful verification of the proof of delivery request.

[066] For example, as described above the location information may include the scanned information or the geophysical location information. The server 110 may attempt to retrieve a postal address from an address database based on the scanned information and the geophysical location information. If there is no valid address corresponding to the scanned information or the geophysical location information, the server 110 may determine that the location information cannot be verified, and subsequently refuse to obtain (and transmit to the portable computing device) a signature code.

[067] In another example, the location information may include both the scanned information and the geophysical location information. The server 110 may determine whether the address retrieved based on the scanned information matches the address retrieved based on the geophysical location information, and may only generate or select the signature code if the two addresses match (within a configurable tolerance). This arrangement allows the server 110 to obtain and transmit to the portable computing device a signature code only in response to a genuine proof of delivery request, i.e., a proof of delivery request transmitted when the delivery personnel is actually at the delivery address.

[068] Further, when obtaining the signature code, the server 110 may execute the following steps: verifying the proof of delivery request based at least in part on the authorisation information; and generating or selecting the signature code in response to successful verification of the proof of delivery request.

[069] The authorisation information may be determined by the server 110 based on the proof of delivery request and/or the location information.

[070] The authorisation information may, for example, indicate whether the recipient has provided authorisation for delivery to be effected using the signature code in the absence of the recipient. Accordingly, the server 110 may obtain the signature code only if the authorisation has been provided.

[071] In another example, the authorisation information may indicate that the recipient agrees to use the signature code only under specified conditions, for example, one or more of the following: • the delivery attempt occurs within a specified range of time (e.g., during business hours) or date (e.g., between 16 January to 10 February); • the value of the delivery item is below a certain amount; or • the delivery personnel is from a specified delivery company.

[072] If the authorisation is limited to one or more specified conditions, the server 110 may further receive additional information (e.g., the value of the delivery item; the delivery company’s name; etc.) from the portable computing device, and may determine whether the conditions are satisfied.

[073] For example, if the recipient has authorised the use of a signature code only during business hours, the server 110 may refuse to obtain a signature code if it determines that the time the proof of delivery request was sent outside business hours.

[074] Further, in some examples, the time information may further include: a first scanning time information, representing the time of a first scan made by the portable computing device; and a second scanning time information, representing the time of a second scan made by the portable computing device.

[075] As previously described, the portable computing device may include a scanning module. The first scanning time information and the second scanning time information may, for example, represent the first scanning and second scanning of a machine-readable label attached to the delivery address, such as a two-dimensional barcode or NFC tag, by the scanning module of the portable computing device.

[076] in practice, the first scan may be the scan made when the delivery personnel arrives at the delivery address, while the second scan may be the scan made when the delivery personnel has just effected delivery, e.g., when the delivery personnel requests the signature code. This arrangement allows the system 100 to provide proof that the delivery personnel has waited at the delivery address for a reasonable period of time before leaving the delivery item in the absence of the recipient, and allows the waiting time to be recorded and subsequently revealed to a relevant party, such as the recipient or the delivery company.

[077] Further, as previously described, the server 110 may further be in communication with a local or remote delivery profile database 170 which stores delivery profile information, and the method executed by the server 110 may further include: retrieving delivery profile information from a delivery profile database 170; and transmitting the delivery profile information to the portable computing device.

[078] The delivery profile information may include one or more delivery instructions and the authorisation information left by the recipient. The delivery instructions provide directions to the delivery personnel regarding the delivery item (e.g., leave the item on doormat; leave the item behind the flower pot next to the front door; leave the item inside a secure parcel box; leave the item with a neighbour; etc.). As previously described, a delivery profile, which indicates the recipient’s delivery instructions and authorisation, may be created by the recipient or on behalf of the recipient prior to the delivery.

[079] The delivery profile information may be retrieved upon receiving a delivery profile request from the portable computing device 120.

[080] For example, the delivery personnel may use the portable computing device to scan a unique machine-readable label attached to the delivery address, such as a two-dimensional barcode or NFC tag. The portable computing device may send the delivery profile request in response to the scanning. Alternatively, the delivery personnel may manually input a unique web address for requesting the delivery profile information into a web-browser application executing on their portable computing device. In a further example, the delivery personnel may input a unique identifier associated with the delivery address or the recipient (e.g., a reference number) into an application executing on their portable computing device. Accordingly, the delivery profile information may be retrieved based on the scanned information, the unique web address, or the unique identifier.

[081 ] in another example, the portable computing device may include a positioning module, as previously described. Accordingly, the delivery profile request may include the location information, and the delivery profile information may be retrieved based on the geographic location information obtained by the positioning module.

[082] In some examples, as shown in Figure 1, the server 110 may further be in communication with a local or remote address database 180 which stores address information representing postal addresses. The server 110 may retrieve the delivery profile information by: retrieving address information representing a postal address from the address database 180 based on the location information; and retrieving the delivery profile information from the delivery profile database 170 based on the address information.

[083] Preferably, the portable computing device 120 includes a display. Upon receiving the signature code, the portable computing device 120 may display the signature code on the display, to allow the delivery personnel to record the signature code, for example by writing it down on a paper receipt or a touchscreen of a handheld device, or inputting it into a delivery management system by any other suitable method.

[084] Further, as shown in Figure 1, the server 110 may further be in communication with one or more terminal devices 190. The terminal devices 190 may include one or more of the following: a mobile phone, a portable or desktop computer, a tablet computer, or the like.

[085] From at least one terminal device 190, the server 110 may receive a proof of delivery reviewing request. Upon receiving the proof of delivery reviewing request, the server 110 retrieves the proof of delivery information from the proof of delivery database 150; and transmits some or all of the proof of delivery information to the terminal device 190.

[086] An example of a suitable server 110 is shown in Figure 4. In this example, the server 110 includes at least one processor 410, a memory 420, an external input/output interface 430, and an input/output device 440 such as a keyboard and/or a display, interconnected via a bus 450 as shown. The external interface 430 may be utilised for connecting the server 110 to peripheral devices and/or networks, such as the communications networks 140 and the local or remote proof of delivery database 150. in some examples, the external interface 430 may further be utilised for connecting the server 110 to the signature code database 160, the delivery profile database 170, the address database 180, or the terminal devices 190. Although a single external interface 430 is shown, this is for the purpose of example only, and in practice multiple interfaces using various methods (e.g. Ethernet, serial, USB, wireless or the like) may be provided.

[087] In use, the processor 410 may execute instructions in the form of applications software stored in the memory 420 to allow the required processes to be performed, including: communicating with the portable computing device 120, the proof of delivery database 150, and other suitable databases or devices; receiving from the portable computing device 120 a proof of delivery request and location information; obtaining a signature code upon receiving the proof of delivery request; transmitting the signature code to the portable computing device 120; and storing proof of delivery information in the proof of delivery database 150. The applications software may include one or more software modules, and may be executed in a suitable execution environment, such as an operating system environment, or the like.

[088] Accordingly, it will be appreciated that the server 110 may be formed from any suitable processing system, such as a suitably programmed computer system, PC, web server, network server, or the like. In one example, the server 110 is a standard processing system such as an Intel Architecture based processing system, which executes software applications stored on nonvolatile (e.g., hard disk) storage, although this is not essential. However, it will also be understood that the processing system could be any electronic processing device such as a microprocessor, microchip processor, logic gate configuration, firmware optionally associated with implementing logic such as an FPGA (Field Programmable Gate Array), or any other electronic device, system or arrangement.

[089] As shown in Figure 5, in one example, the portable computing device 120 includes at least one microprocessor 510, a memory 520, an output device 530, an input device 540, and an external input/output interface 550, interconnected via a bus 560 as shown. The portable computing device 120 may further include a positioning module 570 and/or a scanning module 580. The external interface 550 may be utilised for connecting the portable computing device 120 to peripheral devices and/or networks, such as the server 110, the communications networks 140, any other suitable servers, data stores or the like. Although a single external interface 550 is sho wn, this is for the purpose of example only, and in practice multiple interfaces using various methods (e.g. Ethernet, serial, USB, wireless or the like) may be provided.

[090] In use, the microprocessor 510 executes instructions in the form of applications software stored in the memory 520 to allow communication with the server 110, for example to send the proof of delivery request and the location information via the input/output interface 550, and to allow receiving a proof of delivery confirmation from the server 110. The applications software may include one or more software modules, and may be executed in a suitable execution environment, such as an operating system environment, or the like.

[091] Accordingly, it will be appreciated that the portable computing device 120 may be formed from any suitable processing system, such as a scanner, a portable computer, a tablet computer, a smart phone, or the like.

[092] An example of a method for providing proof of delivery will now be described in further detail with reference to Figures 6-12.

[093] In this example, a proof of delivery (“PoD”) system is provided. The PoD system allows recipients who receive deliveries to indicate their delivery instructions as well as their authorisation to use the signature code, by registering themselves and creating their own delivery profiles. The PoD system further allows the delivery personnel to retrieve and view the delivery instructions and the authorisation left by a recipient, and to request a signature code as a proof of delivery. The PoD system records the signature code associated with the delivery, and allows the recipient, or a third party such as the delivery company, to review or access the proof of delivery.

Registration by the Recipient [094] Using the PoD system, a recipient who receives deliveries may create a delivery profile by registering with the PoD system. The delivery profile includes: • one or more delivery instructions, instructing the delivery personnel with respect to actions to be taken with the delivery item (e.g., leave the item on doormat; leave the item behind the flower pot next to the front door; leave the item inside a secure parcel box; leave the item with a neighbour; etc.); • authorisation information, representing the recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient.

[095] The authorisation information may simply indicate whether the recipient agrees to authorise the delivery personnel to use the signature code (e.g., “Yes” or “No”).

[096] The authorisation information may further indicate to what extent or under which conditions the recipient agrees to authorise the use of the signature code (e.g., Yes for all delivery items; Yes only if the item fits in the parcel box; Yes only if the value of the item is under a certain amount; No for all delivery items; etc.).

[097] The delivery profile may further include the recipient’s detailed information, for example: • The recipient’s name; • The recipient’s address; and • The recipient’s contact details, such as phone number [098] When a recipient registers and creates the delivery profile, the PoD system may validate the address details of the recipient, for example by comparing the collected address of the recipient with valid postal addresses stored in an address database.

[099] In addition, the delivery profile may further include one or more alternative delivery choices, instructing the delivery personnel to take specified actions if the delivery item cannot be left without the recipient’s presence (e.g., if the recipient has not authorised the use of the signature code for any delivery item; or if the recipient agrees to use the signature code for items that can fit in the parcel box, but the delivery item fails to fit in the parcel box; etc.).

[ 100] The alternative delivery choices may include, for example: leaving the item at the nearest post office; leaving the item in a parcel locker at a specified address; leaving the item with the nearest after hours delivery service; etc.

[101] The registration and creation of the delivery profile may be made by a recipient using an application executing on a terminal device (e.g., a mobile phone, a tablet computer, a laptop or desktop computer, or the like), for example using a mobile application installed on a smart phone; or via a webpage displayed on the terminal device.

[102] Figure 6 shows an exemplary user interface for a recipient to create a delivery profile.

[103] As shown in Figure 6, the recipient may input detailed information including their name, address, delivery instructions, their authorisation to leave the delivery item using the signature code, their phone number, and their alternate delivery choice if the delivery item cannot be left without their presence.

[104] Any of these items may be manually input by the recipient, or alternatively be selected from a list, such as a drop-down list, in the example shown in Figure 6, the alternate delivery choice may be selected from a drop-down list, while the other information may be manually filled in. The drop-down list of the alternate delivery choices may include one or more third party delivery service providers. Similarly, although not shown in the figures, the user interface may allow the recipient to choose the delivery instructions and the authorisation from a list of predetennined selections. This arrangement may make the registration and creation of the delivery profile faster and more convenient for the recipient.

[105] Further, as shown in Figure 6, for each item in the delivery profile, the recipient may be allowed to choose the privacy level of the information, for example, whether it is “public” or “private” information. “Public” information may be defined as information visible to any delivery personnel, while “private” information may be defined as information that is only visible to one or more delivery personnel or one or more delivery companies specified by the recipient. In practice, there may be more than two privacy levels for the recipient to select from, and the accessibility of each privacy level may be defined in any other suitable forms.

[106] After the delivery profile has been created, the collected information is stored in a delivery profile database, such as delivery profile database 170 illustrated in Figure 1.

[107] The recipient may further be allowed to specify or receive from the PoD system authentication information, such as a username and/or a password, using which they can log into the PoD system, for example to review, edit or delete their delivery profile, or to check their delivery history records. Alternatively, the recipient may be allowed to log into the PoD system by providing at least some of the detailed information which they have registered, to allow the PoD system to verify their identity.

[108] Further, the recipient may be allowed to include more than one delivery address in the delivery profile. If the delivery profile includes a plurality of delivery addresses, the recipient may specify the same delivery instructions and authority information for all of these addresses, or create different delivery instructions and/or different authority information for each of these addresses.

[ 109] Further, the PoD system may allow grouping a plurality of delivery profile into a delivery profile group. For example, if a plurality of recipients live in the same household, or have a shared address, their delivery profiles may be managed by the PoD system in the same delivery profile group, while allowing each recipient to set their own delivery instructions, authorisation information, and further detailed information such as their name and their phone number.

[110] After successful registration and creation of the delivery profile, the recipient may be allowed to review and edit their delivery profile through the PoD system, and to have their delivery profile deleted from the PoD system. The recipient may change their delivery instructions, authorisation information, and detailed information from time to time. For example, when the recipient moves house, they may change their address in their delivery profile, which may include changing their address into a new address that has not previously existed in the PoD system, or into an address that already exists in the PoD system. Accordingly, this may also allow their delivery profile to be removed from a delivery profile group associated with their previous address, and/or to be added to another delivery profile group associated with their new address.

[111] Further, after successful registration and creation of the delivery profile, the recipient may be provided with a unique identifier associated with their delivery profile. The unique identifier may take any suitable form, including for example one or more of the following: a unique reference number, a unique web address such as a Uniform Resource Identifier (URI); a machine-readable optical label such as a one-dimensional or two-dimensional barcode.

[112] The recipient may further be provided with an electronic version or a hard-copy of a delivery profile reference sheet that embodies the unique identifier. An example of a delivery profile reference sheet is shown in Figure 7.

[113] In the example shown in Figure 7, the delivery profile reference sheet includes: • 701: a unique reference number “12345”; • 702: a unique web address “http://www. deliverypiOof.com.au/scan/12345”; and • 703: a two-dimensional barcode.

[114] The unique web address 702 or the unique reference number 701 may be used by delivery personnel to retrieve and view the delivery profile created by the recipient, for example by inputting the unique w'eb address or the unique reference number into a portable computing device carried by the delivery personnel.

[115] The two-dimensional barcode 703 may also be used by delivery personnel to retrieve and view the delivery profile. The two-dimensional barcode 703 may be scanned by the delivery personnel using a scanning module (e.g., a scanner or a camera) of the portable computing device. Scanning of the two-dimensional barcode may allow the delivery personnel to access the same webpage represented by the unique web address 701, or any other suitable user-interface that allow retrieval of the recipient’s delivery profile.

[116] If a hard copy of the delivery profile reference sheet is provided, it can be attached to a suitable location at the recipient’s delivery address, for example where the delivery personnel can easily notice it without intruding the recipient’s property. The delivery profile reference sheet may be attached, for example, on the front door, next to the door bell, on the letter box, on a parcel box, or the like.

[117] Further, in some examples, the hard copy of the delivery profile reference sheet may be provided as an adhesive label, such as a sticker, which may allow the delivery profile reference sheet to be attached conveniently and firmly to the suitable location at the delivery address by the recipient.

[118] If an electronic delivery profile reference sheet is provided, it can be printed out by the recipient, and subsequently attached to the suitable location in a similar manner as the hard copy.

[119] Further, if the delivery profile includes a plurality of delivery addresses, the recipient may provided a single electronic delivery profile reference sheet or unique identifier for all of these addresses, or a plurality of electronic delivery profile reference sheets or unique identifiers, each corresponding to a respective address recorded in the delivery profile.

[120] Further, as previously described, the PoD system may allow delivery profiles of a plurality of recipients to be managed in a delivery profile group. When two or more recipients have a shared address, they may be provided with the same delivery profile reference sheet or unique identifier, which is associated with the delivery profile group that includes their delivery profiles. Alternatively, they may be provided with different delivery profile reference sheets or unique identifiers, each corresponding to a delivery profile of one of these recipients.

[121] Further, when creating the delivery profile, the recipient may be allowed to choose whether to receive a notification from the PoD system when the unique identifier is used for retrieval of their delivery profile. For example, Figure 8 shows an exemplary user interface which allows the recipient to select whether or not to receive an Email or SMS notification when the unique barcode associated with their delivery profile is scanned.

Registration by the Delivery Personnel [122] The PoD system may also allow delivery personnel to register themselves and create a profile.

[123] The profile of the delivery personnel may include, for example, one or more of the following: • The delivery personnel’s name; • The delivery personnel’s contact details, such as mobile number; and • Which delivery company the delivery personnel works for.

[124] The registration may be made before any delivery or delivery attempt occurs. Alternatively, the registration may be made when the delivery personnel uses the PoD system for the first time to request a recipient’s delivery profile or the signature code.

[125] In some other examples, the PoD system may allow the delivery personnel to use the PoD system without registration in advance, but by inputting their details every time they use the PoD system. The inputted detailed information of the delivery personnel may be used to create a profile for them, or be abandoned after use.

[126] Registering the delivery personnel’s profile may allow the delivery personnel to avoid entering their details repeatedly for subsequent transactions, thereby saving the delivery personnel’s time in delivering the item. Registering the delivery personnel’s profile may further allow the PoD system to verily the delivery personnel’s identity when receiving a delivery profile request. The PoD may only provide the delivery profile to registered delivery personnel, thereby protecting the delivery data from unauthorised use. This arrangement may improve the security and privacy of the delivery profile data.

[127] The registration and creation of the delivery personnel’s profile may be made using an application executing on a suitable terminal device (e.g., a mobile phone, a tablet computer, a laptop or desktop computer, or the like), for example by using a mobile application installed on a smart phone; or via a webpage displayed on the terminal device. The registration may be performed by the delivery personnel themselves, or by the delivery personnel’s company.

[128] The delivery personnel or their company may further be allowed to specify or receive from the PoD system authentication information, such as a username and/or a password, using which they can log into the PoD system, for example for reviewing or editing the delivery personnel’s profile, or for checking their delivery history records. Alternatively, the delivery personnel or their company may be allowed to log into the PoD system by providing at least some of the detailed information which they have registered, to allow the PoD system to verify their identity.

[129] The registration and creation of the delivery personnel’s profile may alternatively be made by communication between the PoD system and one or more electronic processing devices owned or operated by the delivery personnel’s company, such as a delivery company’s server. This arrangement may allow registration and creation of profiles for a plurality of delivery persons, for example by the delivery company’s server sending to the PoD system a packaged dataset including detailed information associated with a plurality of delivery persons, and receiving from the PoD system a corresponding number of usernames and passwords. This arrangement may improve the efficiency of registering the detailed information for a large number of delivery personnel.

Delivery Process

Obtaining the recipient’s delivery profile [130] When arriving at a location indicated by the delivery address, the delivery personnel can see the delivery profile reference sheet attached to, for example, the front door. As shown in Figure 7, the delivery profile reference sheet includes at least one unique identifier associated with the recipient’s delivery profile.

[131] The delivery personnel may then retrieve and view the delivery profile left by the recipient by using the unique identifier.

[132] For example, the delivery personnel may use a portable computing device to scan the unique machine-readable optical label such as the two-dimensional barcode 703. Alternatively, the delivery personnel may manually input the unique web address 702 into a web-browser application executing on their portable computing device, or input the unique reference number 701 into a proof of delivery (“PoD”) application executing on their portable computing device. Alternatively, if the delivery profile reference sheet includes a machine-scannable tag, such as an NFC tag, the tag may be scanned by the delivery personnel using an appropriately capable portable computing device.

[133] The portable computing device may be any suitable electronic device that allows input of the unique identifier and communication with the PoD system. For example, the portable computing device may be a handheld scanner which includes a processor, a scanning module, a display, a keyboard, and a communication module, where the scanning module may be used to scan machine readable symbols. Alternatively, the portable computing device may be a smart phone which includes a processor, a digital camera, a touch screen, and a communication module, where a scanning module such as the digital camera is able to acquire digital image of the unique identifier.

[134] Having scanned or inputted the unique identifier, the portable computing device may send a delivery profile request to the PoD server through a communication network, requesting information registered in the recipient’s delivery profile. The delivery profile request includes information representing the unique identifier scanned or inputted by the delivery personnel.

[135] Upon receiving the delivery profile request, the PoD server retrieves from a delivery profile database a delivery profile that is associated with the unique identifier; and transmits the information recorded in the delivery profile (this information may be referred to as the “delivery profile information”) to the portable computing device, including for example, the recipient’s name, address, delivery instructions, their authorisation to leave the delivery item using the signature code, their phone number, and their alternate delivery choice if the delivery item cannot be left without their presence.

[136] When the portable computing device receives the information recorded in the delivery profile, this information is presented to the delivery personnel, for example by displaying it on the display of the portable computing device.

[137] As previously described, the recipient may select a privacy level for each item in their delivery profile, for example “public” or “private”. Accordingly, the PoD server may only send the information set as “public” to the portable computing device. Alternatively, the PoD server may send all the information in the delivery profile together with their privacy levels to the portable computing device, in which case the mobile computing device may be programmed to only present the information set as “public” to the delivery personnel.

[138] The information may be presented to the delivery personnel through the PoD application executing on the portable communication device; or via a webpage displayed on the portable communication device, or by any other suitable means.

[139] Figure 9 shows an exemplary user interface displaying the delivery profile of a recipient on a portable computing device. As shown in Figure 9, the recipient’s name, address, delivery instructions and authorisation to leave the delivery item using the signature code have been set by the recipient as “public” information thus visible to the delivery personnel, while the recipient’s phone number is set as “private” information, thus invisible to the delivery personnel, although it may be visi ble to other parties (such as the recipient themselves, or operating staff of the PoD system).

[ 140] Although not shown in the figures, if the recipient has allowed their phone number to be visible, the user interface may further include a “click to call” button so that the delivery personnel may click the button to make a phone call to the recipient, if required.

[141] As previously described, the PoD system may allow delivery profiles of a plurality of recipients to be managed in a delivery profile group. In some examples, when two or more recipients live in the same household or have a shared address, they may be provided with the same unique identifier associated with the delivery profile group, and scanning the unique identifier may allow retrieval of all delivery profiles included in the delivery profile group. Accordingly, the delivery personnel may be presented with a list of the delivery profiles of all these recipients associated with the unique identifier. Alternatively, the delivery personnel may be presented with a list of potential recipient names, and may select the name of the intended recipient from the list to review the delivery profile of the intended recipient. In a further example, when the PoD system determines that the unique identifier is associated with a plurality of recipients, the delivery personnel may be requested to input the intended recipient’s name or other identifying information, to allow the PoD system to retrieve and transmit the intended recipient’s delivery profile.

[142] Further, as previously described, the delivery profile of the recipient may include a plurality of delivery addresses, and the recipient may be provided with a unique identifier for all of these addresses. Accordingly, in some examples, the delivery personnel may be presented with a list of delivery instructions and authorisation information associated with all of these addresses. Alternatively, the delivery personnel may be presented with a list of the addresses included in the delivery profile, and may select one address from the list to review the delivery instructions and the authorisation information associated with the selected address.

[143] In another example, the portable computing device includes a positioning module, such as a GPS sensor, a Wi-Fi positioning module or a cellular network positioning module, which can generate or obtain geographical location information representing the geophysical location of the portable computing device. Accordingly, the delivery profile request may include the geographical location information, instead of the information representing the unique identifier scanned or inputted by the delivery personnel. Correspondingly, upon receiving the delivery profile request, the PoD server may retrieve the delivery profile associated with the recipient based on the geographical location information. For example, the PoD server may first retrieve a postal address from an address database based on the geographical location information, and then retrieve the delivery profile from the delivery profile database based on the postal address identified.

[144] As previously described, the PoD system may allow delivery profiles of a plurality of recipients to be managed in a delivery profile group when two or more recipients have a shared address. When the delivery personnel sends a delivery profile request associated with a shared address, the delivery profiles of all of these recipients may be retrieved by the PoD system based on the geophysical location of the portable computing device. Accordingly, the delivery personnel may be presented with a list of the delivery profiles of all of these recipients. Alternatively, the delivery' personnel may be presented with a list of potential recipient names, and may select the name of the intended recipient from the list to review the delivery profile of the intended recipient. In a further example, when the PoD system determines that the geographical location is associated with a plurality of recipients, the delivery personnel may be requested to input the intended recipient’s name or other identifying information, to allow the PoD system to retrieve and transmit the intended recipient’s delivery profile.

[145] In a further example, the portable computing device may include both (a) a positioning module, and (b) a scanning module (such as a digital camera or wireless tag reader), and may send both the geographical location information and the scanned unique identifier to the PoD server. The PoD server may use either the geographical location information or the scanned unique identifier to retrieve the delivery profile. Further, the PoD server may retrieve a first postal address from an address database based on the geographical location information, and retrieve a second postal address from the same or another address database based on the scanned unique identifier, and determine whether the first postal address matches the second postal address. The PoD server may only retrieve and send the delivery profile to the portable computing device if the first postal address matches the second postal address. This arrangement may allow the PoD server to provide the recipient’s profile only in the case of a genuine delivery attempt.

[146] In practice, the user interface as shown in Figure 9 may be displayed on the portable computing device after the delivery personnel scans a barcode or sends its geographical location information. In another example, the user interface may be automatically displayed on the portable computing device, based on the delivery personnel’s geographical location. For example, one or more delivery addresses may be inputted into the portable computing device before the delivery attempt occurs, and when the delivery personnel approaches the delivery address, the portable computing device may automatically send the geographical location to the PoD server, receive from the PoD server the delivery profile, and display the delivery profile for the delivery personnel to review.

[147] Upon reviewing the displayed delivery profile information (which includes at least the delivery instructions and the authorisation information), the delivery personnel may follow the delivery instructions and proceed to obtain a signature code if the recipient has provided authorisation for delivery to be effected using the signature code in the absence of the recipient.

[148] For example, according to the delivery instructions and authorisation information as shown in Figure 9, the delivery personnel may proceed to obtain a signature code only if the delivery item fits in the secure parcel box installed at the delivery location. If the delivery item does not fit in the secure parcel box, the delivery personnel may arrange another delivery attempt or contact the recipient to arrange and implement an alternate delivery choice.

[149] If the delivery personnel follows the instruction to leave the delivery item, they may request a signature code to be used as a proof of delivery. This request may be made, for example, by operating a button displayed on the PoD application executing on the portable communication device or on a webpage displayed on the portable communication device.

[150] Figure 10A shows an exemplary user interface 1000 which allows the delivery personnel to request a signature code, for example, by pressing, tapping or clicking a button 1010 displayed on a touchscreen of the portable computing device.

Obtaining the signature code [151] Upon receiving the delivery personnel’s input of requesting a signature code, the portable computing device sends a proof of delivery request to the PoD server via the communication network.

[152] The portable computing device also sends to the PoD server location information representing the geophysical location of the portable computing device.

[153] The location information may, for example, include scanned information obtained by a scanning module of the portable computing device.

[154] As previously described, the portable computing device may be a handheld scanner which includes a processor, a scanning module, a display, a keyboard, and a communication module, where the scanning module may be used to scan machine readable symbols. Alternatively, the portable computing device may be a smartphone which includes a processor, a digital camera, a touch screen, and a communication module, where a scanning module such as the digital camera is able to acquire digital image of the unique identifier.

[155] Accordingly, the delivery personnel may use the portable computing device to scan the unique machine-readable optical label such as the two-dimensional barcode 703. As the delivery profile reference sheet is attached to a suitable location at the recipient’s address, scanning of the barcode 703 indicates that the delivery personnel has arrived the recipient’s address. By sending the scanned barcode 703 to the PoD server, the delivery personnel provides evidence showing a genuine delivery attempt has occurred, i.e., the delivery' personnel has actually arrived at the recipient’s address.

[156] The scanned barcode 703 may be sent to the PoD server directly, or may be used to generate identification information representing the unique identifier (e.g., a unique web address or a unique reference number, associated with the recipient’s delivery profile), which may be sent to the PoD server instead of the scanned barcode 703.

[157] In another example, the location information may include geophysical location information obtained by a positioning module of the portable computing device. As previously described, the portable computing device may include a positioning module, such as a GPS sensor, a Wi-Fi positioning module, or a cellular network positioning module, which can generate or obtain location information representing the geophysical location of the portable computing device. Accordingly, the location information may include the geophysical location obtained by the GPS sensor, the Wi-Fi positioning module, or the cellular network positioning module.

[158] In a further example, the location information may include both the scanned information and the geophysical location information.

[159] Upon receiving the proof of delivery request, the PoD server obtains a signature code.

[160] In one example, the PoD server obtains the signature code by randomly generating a signature code.

[161] The PoD server may keep a record of the signature codes that have already been transmitted to a portable computing device before. Once a signature code is randomly generated, the PoD server determines whether a selected or generated signature code has previously been used, i.e., whether it has been transmitted to a portable computing device. If it is determined that the selected or generated signature code has been used, the PoD server generates a different signature code. This process may be repeated until a signature code that has never been used is selected or generated. In some examples, the server may further record date and/or time information representing when the signature code is used, and may allow reuse of a signature code if a predetermined time period (e.g., 6 months, 1 year, 3 years, or the like) has passed since the last use of the same signature code.

[ 162] The signature code is then tr ansmitted to the portable computing device, and is recorded by the PoD server as a used signature code. This may be achieved, for example, by the PoD server storing the used signature code in a used signature code database. This may allow the PoD server to ensure every signature code transmitted to a portable computing device is a unique one, thereby improving the reliability of the proof of delivery. The PoD server may further record date and/or time information representing when the signature code is used, and may allow reuse of a signature code if a predetermined time period (e.g., 6 months, 1 year, 3 years, or the like) has passed since the last use of the same signature code.

[163] In another example, the PoD server obtains the signature code by randomly generating a signature code, or selecting one signature code from a plurality of predetermined signature codes stored in a local or remote signature code database, with which the PoD server communicates.

[164] When a signature code is selected from the plurality of predetermined signature codes stored in the signature code database, the PoD server may cause removal or deletion of the signature code from the plurality of predetermined signature codes, for example by removing or deleting the signature code from the signature code database. This may allow the PoD server to ensure every signature code transmitted to a portable computing device is a unique one, thereby improving the reliability of the proof of delivery.

[165] Further, when selecting or generating the signature code, the PoD server may verify the proof of delivery request based at least in part on the location information, and only generate or select the signature code in response to successful verification of the proof of delivery request.

[166] For example, the PoD server may attempt to retrieve a postal address from an address database based on the location information received. If there is no valid address corresponding to the location information received, the PoD server may determine that the location information cannot be verified, and subsequently refuse to obtain a signature code.

[ 167] In another example, the location information may include both the scanned information and the geophysical location information. The PoD server may identify a delivery profile using the scanned information and subsequently retrieve the postal address included in the delivery profile, and also retrieve a postal address from an address database based on the location information received. The PoD server may further determine whether the address retrieved based on the scanned information matches the address retrieved based on the geophysical location information, and only generate or select the signature code if the two addresses match. This arrangement allows the PoD server to obtain and send to the portable computing device a signature code only in response to a genuine proof of delivery request, i.e., that the delivery personnel is actually at the delivery address when the proof of d elivery request is sent.

[168] Further, the PoD server may verify the proof of delivery request based at least in part on the authorisation information.

[169] For example, the authorisation information may indicate whether the recipient has provided authorisation for delivery to be effected using the signature code in the absence of the recipient. Accordingly, the PoD server may obtain the signature code only if the authorisation has been provided .

[170] In another example, the authorisation information may indicate that the recipient agrees to use the signature code only under specified conditions, for example, one or more of the following: • the delivery attempt occurs within a specified range of time (e.g., during business hours) or date (e.g., between 16 January to 10 February); • the value of the delivery item is below a certain amount; and • the delivery personnel is from a specified delivery company.

[171] If the authorisation is limited to one or specified conditions, the PoD server may further receive additional information (e.g., the value ofthe delivery item; the delivery company’s name; etc.) from the portable computing device, and determine whether the conditions are satisfied.

[172] As an example, if the recipient has authorised the use of a signature code only during business hours, the PoD server may refuse to obtain a signature code if it determines that the proof of delivery request has been sent from the portable computing device outside of business hours.

[173] in practice, the PoD server may use one or more of the verification processes described above. For example, the PoD server may perform verification based on both the location information and the authorisation information, and only obtain the signature code if both the verification processes are successful.

[174] Further, the various verification processes described above may be performed by the PoD server before obtaining the signature code. Alternatively, the verification may be performed after obtaining the signature code, but before transmitting the obtained signature code to the portable computing device, in which case the PoD server may decide whether to transmit the obtained signature code based on the verification result(s).

[175] When a signature code has been selected or generated, or is subsequently determined by the PoD server to be a valid signature code, the PoD server transmits the signature code to the portable computing device via the communication network.

[176] The PoD server also stores the signature code together with additional information, as proof of delivery information (“PoD information”), in a local or remote proof of delivery database, with which the PoD server communicates.

[177] The additional information stored together with the signature code includes at least the following: authorisation information; the location information received from the portable computing device; and time information representing the date and time of the delivery.

[178] The authorisation information is associated with the recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient.

[179] For example, the authorisation information may be the authorisation information retrieved from the recipient’s delivery profile. The PoD server may retrieve this authorisation information based on the location information received from the portable computing device. The location information can be used to identify a delivery profile of the recipient, for example, by determining a unique identifier associated with the delivery profile based on the scanned information, or by retrieving address information representing a postal address from an address database based on the received geographical location information. Authorisation information may be subsequently retrieved from the delivery profile database based on the address information. Storing the retrieved authorisation information may allow the PoD system to record the exact authorisation information at the time of the delivery, given that the recipient may subsequently change their authorisation information in their delivery profile.

[180] Alternatively, the authorisation information may include authorisation identification information associated with the delivery profile of the recipient stored in the delivery profile database. For example, the authorisation information may include the unique identifier associated with the delivery profile, which can be used to retrieve the authorisation information included in the delivery profile when required. As another example, the authorisation information may include a pointer indicating the storage address of the delivery profile, and/or the storage address of the authorisation information in the delivery profile database. This allows a reduction in the amount of data stored in the PoD information, and allows efficient utilisation of limited storage space in the PoD database.

[181] As previously described, the location information may include one or both of the following: • scanned information obtained by a scanning module of the portable computing device; and • geophysical location information obtained by a positioning module of the portable computing device.

[182] The location information received from the portable computing device may be stored directly, or be processed and/or converted into a different data form prior to being stored. For example, the PoD server may retrieve address information representing a postal address from an address database based on the geographical location information received, and may store the retrieved postal address information instead of the raw location information.

[183] The time information representing the date and time of the delivery may be, for example, one or more of the following: • the time when the proof of delivery request is received by the PoD server; • the time when the location information is received by the PoD server; and • the time when the PoD information is stored in the proof of delivery database.

[ 184] The time information representing the date and time of the delivery' may take any other suitable form. For example, the time information may include: a first scanning time information, representing the time of a first scan made by the portable computing device; and a second scanning time information, representing the time of a second scan made by the portable computing device.

[185] The first scanning time information and the second scanning time information are received from the portable computing device. They may represent the first scan and the second scan of a machine-readable optical label attached to the delivery address, such as the two-dimensional barcode 703. In practice, the first scan may be the scan made when the delivery personnel arrives the delivery address, while the second scan may be the scan made when the delivery personnel is about to leave the delivery address, e.g., when the delivery personnel requests the signature code. This arrangement allows the PoD information to provide proof that the delivery personnel has waited at the delivery address for a reasonable period of time before leaving the delivery item in the absence of the recipient, and allows the waiting time to be recorded and subsequently revealed to a relevant party, such as the recipient or the delivery company.

[186] In addition to the signature code and the above-mentioned additional information, the PoD information may further include or contain a reference to other suitable information, for example, one or more of the following: • portable computing device information associated with the portable computing device; • delivery personnel information associated with delivery personnel effecting delivery; • delivery item information associated with an item being delivered; • recipient information associated with the recipient; and • sender information associated with a sender.

[187] All of these items may be received from the portable computing device, for example together with the proof of delivery request. The recipient information may alternatively be retrieved from the delivery profile of the recipient, where the delivery profile may be identified using any of the methods described above. The delivery personnel information may alternatively be retrieved from the delivery personnel’s profile that has been registered in advance.

[188] The PoD information may further include delivery instructions included in the delivery profile of the recipient, which can be retrieved from the delivery profile database.

[189] Upon receiving the signature code, the portable computing device may display the signature code on a display of the portable computing device, to allow the delivery personnel to record the signature code as a receipt of delivery, for example by writing it down, or inputting it into the delivery company’s delivery management system, for example by using a delivery management application executing on the portable computing device, or via a webpage displayed on the portable computing device.

[ 190] For example, as shown in Fig. 1 OB, after pressing, tapping or clicking the button 1010, a signature code “VX172” is displayed in the area 1011, and a message prompting the delivery personnel to write down the signature code is displayed in the area 1012.

[191] Although in this example the signature code is a series of alphanumeric characters, as previously described, the signature code may take any other suitable form, for example one or more of the following: words, letters, numbers, figures or any other symbols. In some other examples, the signature code may be a series of letters, a series of numbers, a combination of alphanumeric characters, or a machine readable symbol such as a one-dimensional barcode or a two-dimensional barcode.

[ 192] The location information and time information stored associated with the signature code in the proof of delivery information may subsequently be c ompared with the receipt of delivery history recorded by the delivery company, for any suitable purpose such as confirming the deliver)' history of the delivery personnel or dispute settlement. For example, the recorded proof of delivery information may be used to corroborate the delivery personnel’s or the delivery company’s claim that they have delivered a package to a certain address, at a certain time, and with authorisation to leave from the recipient.

[193] In this way, the time-stamped and location-stamped signature code may function as a secure and independent “digital witness” of the delivery.

[194] Further, the delivery company or other interested parties may wish to be notified that a delivery has been effected. The PoD system may allow the PoD server to automatically send the signature code or the PoD information to an external system owned or operated by the delivery company or an interested party, for example, using a shared database, or through a predetermined data interface or communication protocol.

Notifying the Recipient [195] After storing a proof of delivery, the PoD server may notify the recipient that a delivery has been completed.

[196] The notification may, for example, be sent through an email, a short message service (SMS) message, a push via a mobile application (app) executing on the recipient’s mobile terminal device, or the like.

[ 197] The PoD server may send a notification to the recipient automatically, using the contact information provided in the recipient’s delivery profile.

[198] Alternatively, the PoD server may allow the delivery personnel to choose whether a notification is to be sent.

[199] As shown in Figure 10B, by pressing, tapping or clicking the button 1020, the delivery personnel may choose to have a notification sent to the recipient, informing the recipient of the safe delivery. The notification may be a standard message, for example including: the date and time of the delivery, the delivery company or the delivery' personnel’s name, and the relevant delivery item information. Alternatively, the notification may be a customised message that can be inputted or edited by the delivery personnel. The message may further include, for example, the detailed location where the delivery item has been left, or a photo of the delivered item being left at the delivery address.

[200] As shown in Figure 1 OB, after the standard or customised notification is sent, the content of the notification is displayed in the area 1021.

[201] In some circumstances, the delivery personnel may be instructed not to leave the delivery item at the delivery address. For example, the recipient may have chosen not to use the signature code in the absence of the recipient, or the recipient may have chosen to only authorise the usage of the signature code under a specified cond ition, and the specified condition cannot be satisfied (e.g., the delivery time is not in the specified time period; the delivery item cannot fit in the security parcel box; etc.). In these circumstances, the PoD system may allow the deliver}/ personnel to leave a message notifying the recipient that they have a missed delivery. The message may include further information, such as where to collect the delivery item, or the delivery personnel’s contact details.

[202] As shown in Figure 1 OB, the delivery personnel may choose to leave a message notifying the recipient that they have a missed delivery, by pressing, tapping or clicking the button 1030. The notification may be a standard message, or a customised message that can be inputted or edited by the delivery personnel. As shown in Figure 10C, after the notification is sent, the content of the notification is displayed in the area 1031.

[203] Alternatively, the delivery personnel may leave a paper message such as a message card to the recipient at the delivery address.

[204] Compared to leaving a paper message, the electronic notification allows the delivery company to save time and paper, thus reducing the cost of delivery. It may also allow instantaneous notification to the recipient, which may facilitate the recipient in contacting the delivery personnel or to arrange an alternatively delivery.

[205] As previously described, when creating the delivery profile, the recipient may choose whether or not to receive an email notification or an SMS notification when the unique barcode associated with their delivery profile is scanned. In a similar manner, the PoD system may further allow the recipient to choose whether to receive a notification when a safe delivery or a missed delivery has occurred, in which case the notification may only be sent if the recipient has indicated in their delivery profile their agreement to receive the notification.

[206] Further, the PoD system may allow sending the notification to an alternative recipient chosen by the recipient. For example, the recipient may specify' in the delivery profile an alternative recipient, to whom the safe delivery or missed delivery notification may be sent, in addition to the recipient themselves. This may allow the alternative recipient to collect the deliver}' item on behalf of the recipient.

[207] In addition, the PoD system may allow other suitable form of communication between the delivery personnel and the recipient, for example real time chat, voice calls or video calls. These can be performed through an application (e.g., the same application for requesting the recipient’s delivery profile information and / or the signature code, or other suitable application) executing on the portable communication device carried by the delivery personnel, and an application executing on a terminal device of the recipient. These forms of communication may be used not only to notify the recipient of attempted or actual delivery, but any other issues that may arise during delivery or attempted delivery by the delivery personnel.

Reviewing the Proof of Delivery [208] A recipient may wish to review their deliveries. The PoD system allows the recipient to review their delivery history, for example by logging in to the PoD system using the authentication or log-in information established when the recipient registered their delivery profile. The recipient may use any suitable terminal device to review their deliver}7 history, such as a mobile phone, a portable computer, a tablet computer, or the like. The recipient may, for example, use a PoD application executing on the terminal device or a webpage provided by the PoD system to retrieve and view their delivery history.

[209] Alternatively, the recipient may be required to input their detailed infomiation, so that the PoD system may verify the identity of the recipient and provide their delivery history.

[210] Accordingly, a proof of delivery reviewing request will be sent to the PoD server from the terminal device.

[211] Upon receiving the proof of delivery reviewing request, the PoD server retrieves the relevant proof of delivery information from the proof of delivery database, and transmits delivery history7 information including some or all of the relevant the proof of delivery information to the terminal device.

[212] The proof of delivery information may be retrieved by any suitable means.

[213] In one example, based on the log-in infomiation used by the recipient, the PoD server retrieves the recipient’s delivery profile, which includes the recipient’s address. Using this address, the PoD server scans the proof of delivery database, and identifies the proof of delivery information that includes location information which matches the address.

[214] In another example, if the proof of delivery information further includes the recipient’s detailed information, or includes a link to the recipient’s delivery profile, the relevant proof of delivery information can be identified based on the recipient’s detailed information or the recipient’s delivery profile.

[215] The retrieved delivery history may be presented on a display of the terminal device used by the recipient, for example through the PoD application executing on the terminal device or via a webpage provided by the PoD system.

[216] Further, in operation, the PoD server may also collect and record other data related to the recipient, and allow the recipient to review this data. For example, the delivery history being sent to the recipient may further include events such as missed delivery events, and/or the events recording that that the recipient’s delivery profile was requested or reviewed.

[217] Figure 11 shows an exemplary user interface for displaying the delivery history of a recipient.

[218] As shown by the delivery history, a signature code “VX172” has been requested at 9:35AM on 14 June. The delivery personnel’s contact number and the delivery company which performed the delivery are also presented to the recipient. Further, the delivery history shows that there is a missed delivery at 9:56AM on 17 June, associated with a reference number “847662”. The delivery history also shows that three requests for the delivery instruction, made by the delivery personnel scanning the unique barcode, have been received by the PoD server.

[219] Further, the delivery company or other interested parties may wish to review the deliveries that they performed. The PoD system may allow a proof of delivery reviewing request to be sent by the delivery company or the other interested parties.

[220] The PoD server may retrieve the relevant proof of delivery information from the proof of delivery database, using the search criteria specified (e.g., a specified driver, a specified date / time, a specified delivery item) in the proof of delivery' reviewing request.

[221] The PoD server then transmits the delivery history including the retrieved proof of delivery information to the delivery company or the other interested parties.

[222] The delivery company or the other interested parties may use a terminal device to retrieve and view the delivery history, which may be performed in a similar manner as the making of proof of delivery reviewing request by the recipient. Alternatively, the proof of delivery reviewing request made by the delivery company or the other interested parties may be sent through a predetermined data interface or communication protocol. Suitable access controls and safeguards may be adopted to protect the privacy of the delivery history data.

[223] Figure 12 illustrates an exemplary structure of the PoD system 1200.

[224] As shown in Figure 12, the PoD system 1200 includes: at least one terminal device 1210; a PoD server 1220; and at least one portable computing device 1230. The PoD server 1220 includes: a PoD public facing Web Portal 1221; a PoD application 1222; a PoD database 1223;a delivery profile (DP) database 1224; a PoD Public API 1225; a SMS gateway 1226; and an email gateway 1227.

Terminal Device 1210 [225] As shown in Figure 12, the PoD system 1200 includes at least one terminal device 1210 to allow the recipient to register their delivery profile.

[226] For example, the terminal device 1210 may include a smart phone or a web enabled mobile device 1211. The recipient may register with the PoD system and create their delivery profile by using a mobile browser which connects to the PoD public facing Web Portal 1221 or by using a dedicated PoD mobile application which communicates with the PoD application 1222 via the PoD Public API 1225.

[227] As another example, the terminal device 1210 may include a personal computer 1212, which may be any suitable type of computer, such as laptop computer, a desktop computer, a tablet computer, or the like. Using the personal computer 1212, the recipient can register and set up the delivery profile via a desktop browser which connects to the PoD Web Portal 1221.

[228] As previously described, the registration involves collecting address and contact details of the recipient, as well as their delivery instructions and their authorisation to use a signature code. The registration may further include validation of the address details of the recipient.

PoD server 1220 [229] The PoD server 1220 includes a PoD public facing Web Portal 1221. The PoD Web Portal 1221 is the public facing web based user interface which allows: 1) recipients to register and edit their delivery profiles, as well as review their delivery histories; and 2) delivery companies to register and edit their information, request recipient’s delivery instructions and authorisation information, request signature codes, as well as review their delivery histories.

[230] The PoD server 1220 further includes a PoD Application 1222, which provides process logic, security and access control to data stored in the PoD database 1223 and the DP database 1224.

[231] The PoD server 1220 further includes a PoD database 1223, which stores the proof of delivery information. The PoD database 1223 may further store other application related data such as the history of transactions performed by users of the PoD system.

[232] The PoD server 1220 further includes a delivery profile (DP) database 1224, which stores the delivery profile of recipients. The DP database 1224 may further store the profiles of the delivery personnel.

[233] Although the PoD database 1223 and the delivery' profile (DP) database 1224 are shown as separate databases in Figure 12, in some embodiments they may be configured as a single database which stores all the application related data (e.g., the proof of delivery information, the delivery profiles of recipients, the profiles of the delivery personnel, and any other relevant data), or be configured based on the same data storage hardware.

[234] The PoD server 1220 further includes a Public API 1225, which is a secure channel for external devices such as the terminal device 1210, the portable computing device 1230 and other third party devices to interact with the PoD Application 1222. Features of the Public API 1225 may include: a) Recipient registration; b) Delivery personnel Registration; c) Updating recipient’s delivery profile; d) Updating delivery personnel profile; e) Retrieval of delivery instructions; f) Obtaining signatures codes; g) Providing delivery history; and h) Providing communication means to allow the communication between the delivery personnel and the recipient.

[235] The PoD server 1220 further includes a SMS gateway 1226. The SMS gateway 1226 is used to provide SMS notifications to a recipient when a delivery related event occurs. The SMS gateway 1226 may further be used to provide SMS notifications to a delivery company or other interested parties when a delivery related event occurs.

[236] The PoD server 1220 further includes an email gateway 1227. The email gateway 1227 is used to provide email notification to a recipient when a delivery related event occurs. The SMS gateway 1226 may further be used to provide SMS notifications to a delivery company or other interested parties when a delivery related event occurs.

[237] As previously described, the portable computing device 1230 may include any suitable electronic device that allows input of the unique identifier and communication with the PoD system, such as a handheld scanner 1231 or a smart phone 1232.

[238] For example, when the portable computing device 1230 is a smart phone 1232, a PoD application may be installed on the smart phone 1232, which allows delivery personnel to: • register an account with the PoD system; • request and receive a recipient’s delivery instructions, when the delivery personnel has arrived at the delivery address; and • request and receive a signature code in the absence of the recipient, if the use of the signature code has been authorised by the recipient.

[239] The PoD application may communicate with the PoD Application 1222 over a mobile telecommunications network via the PoD Public API 1225.

[240] In another example, the portable computing device 1230 may be a barcode scanner 1231 provided by a delivery company. The hardware and/or software of the barcode scanner 1231 may be configured to perform similar function as the PoD application described above. For example, the scanners or the scanner support backend systems may be integrated to the PoD Public API 1225 to allow communication between the PoD server 1220 and the barcode scanner 1231. Alternatively, the barcode scanner 1231 may not be in direct communication with the PoD server 1220, but in communication with a Barcode Scanner Application 1240, as shown in Figure 12. The Barcode Scanner Application 1240 may be the back end management system that a delivery company uses to manage their fleet of barcode scanner devices in the field.

[241] The barcode scanner 1231 may use the Barcode Scanner Application 1240 as a proxy, and the Barcode Scanner Application 1240 may be in communication with the PoD Public API 1225 and may pass results back to the barcode scanner 1231. This forwarding of information may be performed without substantial forwarding delays.

[242] The reference in this specification to any prior publication (or information derived from it), or to any matter which is known, is not, and should not be taken as an acknowledgment or admission or any form of suggestion that that prior publication (or information derived from it) or known matter forms part of the common general knowledge in the field of endeavour to which this specification relates.

[243] Many modifications will be apparent to those skilled in the art without departing from the scope of the present invention as hereinbefore described with reference to the accompanying drawings.

Claims (9)

THE CLAIMS DEFINING THE INVENTION ARE AS FOLLOWS:

1. A computer-implemented method for providing proof of delivery, including the steps of: receiving from a portable computing device: a proof of delivery request, and location information representing the geophysical location of the portable computing device; obtaining a signature code upon receiving the proof of delivery request; transmitting the signature code to the portable computing device; and storing proof of delivery information in a proof of delivery database, the proof of delivery information including: the signature code; authorisation information associated with a recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient; the location information; and time information representing the date and time of the delivery.

2. The computer-implemented method of claim 1, wherein obtaining the signature code includes: randomly generating a signature code.

3. The computer-implemented method of claim 1, wherein obtaining the signature code includes: selecting a signature code from a plurality of predetermined signature codes stored in a signature code database.

4. The computer-implemented method of claim 2 or 3, wherein obtaining the signature code further includes: determining whether the signature code has previously been transmitted to a portable computing device.

5. The comp liter-implemented method of claim 3, wherein obtaining the signature cod e further includes: causing removal or deletion of the signature code from the plurality of predetermined signature codes.

6. The computer-implemented method of claim 1, wherein the authorisation information represents the recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient.

7. The computer-implemented method of claim 1, wherein the authorisation information includes authorisation identification information associated with a delivery profile stored in a delivery profile database, the delivery profile including information representing the recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient.

8. The computer-implemented method of claim 1, wherein the proof of delivery information further includes or contains a reference to: portable computing device information associated with the portable computing device.

9. The computer-implemented method of claim 1, wherein the proof of delivery information further includes or contains a reference to: delivery personnel information associated with delivery personnel effecting delivery.

10. The computer-implemented method of claim 1, wherein the proof of delivery information further includes or contains a reference to: delivery item information associated with an item being delivered.

11. The computer-implemented method of claim 1, wherein the proof of deliveiy information further includes or contains a reference to: recipient information associated with the recipient.

12. The computer-implemented method of claim 1, wherein the proof of delivery information further includes or contains a reference to: sender information associated with a sender.

13. The computer-implemented method of claim 1, wherein obtaining a signature code includes: verifying the proof of delivery request based at least in part on the location information; and generating or selecting the signature code in response to successful verification of the proof of delivery request.

14. The computer-implemented method of claim 1, further including: determining the authorisation information based on the proof of delivery request and/or the location information.

15. The computer-implemented method of claim 14, wherein obtaining a signature code includes: verifying the proof of delivery request based at least in part on the authorisation information; and generating or selecting the signature code in response to successful verification of the proof of delivery request.

16. The computer-implemented method of claim 1, wherein the time information includes: a first scanning time information, representing the time of a first scan made by the portable computing device; and a second scanning time information, representing the time of a second scan made by the portable computing device.

17. The computer-implemented method of claim 1, wherein the location information includes one or both of the following: geophysical location information obtained by a positioning module of the mobile computing device, or scanned information obtained by a scanning module of the mobile computing device.

18. The computer-implemented method of claim 1, further including: retrieving delivery profile information from a delivery profile database; and transmitting the delivery profile information to the portable computing device.

19. The computer-implemented method of claim 18, wherein the delivery profile information is retrieved upon receiving a delivery profile request from the portable computing device.

20. The computer-implemented method of claim 18, further including: based on the location information, retrieving address information representing a postal address from an address database; retrieving the delivery profile information from the delivery profile database based on the address information.

21. The computer-implemented method of claim 18, wherein the delivery profile information includes: one or more delivery instructions; and the authorisation information, representing authorisation for delivery to be effected using the signature code in the absence of the recipient.

22. The computer-implemented method of claim 1, further including: receiving a proof of delivery reviewing request from a terminal device; retrieving the proof of delivery information from the proof of delivery database; and transmitting the proof of delivery information to the terminal device.

23. A computer-implemented method executed on a portable computing device, the method including the steps of: transmitting to a server: a proof of delivery request, and location information representing the geophysical location of the portable computing device; receiving a proof of delivery confirmation from the server, indicating that proof of deliver)' information has been stored by the server, the proof of delivery information including: a signature code generated by the server; authorisation information associated with a recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient; the location information; and time information representing the date and time of the delivery; wherein the proof of delivery confirmation includes the signature code.

24. The computer-implemented method of claim 23, wherein the signature code is randomly generated by the server.

25. The computer-implemented method of claim 23, wherein the signature code is selected by the server from a plurality of predetermined signature codes stored in a signature code database.

26. The computer-implemented method of claim 23, wherein the authorisation information represents the recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient.

27. The computer-implemented method of claim 23, wherein the authorisation information includes authorisation identification infoimation associated with a delivery' profile stored in a delivery profile database, the delivery profile including information representing the recipient’s authorisation for delivery to be effected using the signature code in the absence of the recipient.

28. The computer-implemented method of claim 23, wherein the proof of delivery infoimation further includes or contains a reference to: portable computing device infoimation associated with the portable computing device.

29. The computer-implemented method of claim 23, wherein the proof of delivery information further includes or contains a reference to: delivery personnel information associated with delivery personnel effecting delivery.

30. The computer-implemented method of claim 23, wherein the proof of delivery information further includes or contains a reference to: delivery item information associated with an item being delivered.

31. The computer-implemented method of claim 23, wherein the proof of delivery information further includes or contains a reference to: recipient information associated with the recipient.

32. The computer-implemented method of claim 23, wherein the proof of delivery information further includes or contains a reference to: sender information associated with a sender.

33. The computer-implemented method of claim 23, further including: displaying the signature code on a display of the portable computing device.

34. The computer-implemented method of claim 23, wherein the time information includes: a first scanning time information, representing the time of a first scan made by the portable computing device; and a second scanning time information, representing the time of a second scan made by the portable computing device.

35. The computer-implemented method of claim 23, wherein the location information includes one or both of the following: geophysical location information obtained by a positioning module of the mobile computing device, or scanned information obtained by a scanning module of the mobile computing device.

36. The computer-implemented method of claim 23, further including: receiving delivery profile information from the server.

37. The computer-implemented method of claim 36, further including: transmitting to the server a delivery profile request.

8. The computer-implemented method of claim 3 6, wherein the delivery profile information includes: one or more delivery instructions; and the authorisation information, representing authorisation for delivery to be effected using the signature code in the absence of the recipient. 3

9. A system for providing proof of delivery, including a portable computing device and one or more electronic processing devices, the one or more electronic processing devices being configured to perform the method as claimed in any one of claims 1 to 22.