Login| Sign Up| Help| Contact|

Patent Searching and Data


Title:
MY DROP BOX DELIVERY (MDB DELIVERY)
Document Type and Number:
WIPO Patent Application WO/2020/212725
Kind Code:
A1
Abstract:
MDB Delivery is Depository Containment Structure product with built in technology and functional elements to record information relating to a delivery or a collection transaction. The product is governed by a method of application, and service to provide a convenient, fast, secure and assured delivery service for all interfaces within a delivery process. MDB Delivery provides an integrated end to end delivery process between the Vendor, Courier and Recipient within a transaction. The integrated service means all users have visibility regarding delivery statuses and transaction receipt information. A user may also remotely control the functionality of the product via their online account.

Inventors:
DYSON JASON (GB)
Application Number:
PCT/IB2019/052792
Publication Date:
October 22, 2020
Filing Date:
April 05, 2019
Export Citation:
Click for automatic bibliography generation   Help
Assignee:
DYSON JASON (GB)
International Classes:
A47G29/14
Foreign References:
US20170286905A12017-10-05
US20180070753A12018-03-15
US20050061877A12005-03-24
GB2530013A2016-03-16
Other References:
None
Download PDF:
Claims:
CLAIMS

I Claim:

1. A Depository Containment Structure, that can be installed at a residential or commercial property and is associated with the postal address to which it is installed and the party to whom it is registered. Said depository containment structure can be used to temporarily house contents during a collection and or delivery process, comprising: a. A Hollow Body;

b. An Opening in said hollow body to provide a point of access for depositing and retrieving physical content;

c. A Closure connected to said hollow body for opening and closing of said opening; d. A plurality of Anchor Fixings for securing means of said depository containment structure to the external point of contact;

e. A Lock System for locking and unlocking said closure to said hollow body;

f. A Lock System Interface, for validating and permitting secured operation of said lock system;

g. A means for electrical Power acquisition and distribution.

2. A Depository containment structure as in claim 1, wherein said hollow body comprises: a. A structure with an inner and outer leaf providing a hollow structure to house functional components of the product;

b. An insulating material positioned between said inner and outer leaves to reduce the influence of external temperatures inside said depository containment structure; c. A means for allowing said anchor fixings to pass through both inner, and outer leaves to connect with the external environment;

d. A means for allowing mains power inlet;

e. A means for allowing power and communications cabling to pass through into said closure, thus facilitating said closure with power and communications connectivity.

3. A Depository containment structure as in claim 1, wherein said closure comprises:

a. A structure with an inner and outer leaf providing a hollow structure for containing functional components;

b. An insulating material positioned between said inner and outer leaves to reduce the influence of external temperatures, within said depository containment structure; c. A hinge fixed to the inner leaf of said hollow body, and inner leaf of said closure, allowing said closure to pivot for opening and closing movement of said opening and avoid risk of external tampering;

d. A handle to allow persons to physically open and close said closure;

e. A means for allowing cabling to extend through from said hollow body;

4. A Depository containment structure as in claim 1, wherein said lock system comprises: a. A moveable apparatus positioned within said hollow body that has 2 possible

positions; an extended position for locking, and a retracted position for unlocking; b. A fixed component positioned on said closure that accommodates the extended position of said moveable apparatus when said closure is closed, thus securing together; said closure with said hollow body.

5. A Depository containment structure as in claim 1, wherein said lock system Interface

comprises:

a. An electronic contactless key interface enabled to read encrypted coding for

controlled operation of said lock system;

b. A contactless key interface that operates via Near Field Communication technology to; receive, read and verify encrypted coding for the purpose of operating said lock system, thus enabling secured access to said depository containment structure; c. A keypad interface with numbers and action buttons to allow manual override for locking and unlocking said lock system.

6. A Depository containment structure as in claim 1, wherein said anchor fixings comprise: a. A plurality of anchor fixings that are installed from the outer side of the inner leaf of said hollow body, and pass through said hollow body and are embedded into the local external environment. Said anchor fixings have a head to connect the fixing with the inner leaf of said hollow body and securely pin said hollow body to the external environment.

7. A Depository containment structure as in claim 1, wherein said electrical power acquisition and distribution comprises: a. An Uninterruptable Power Supply unit for storing electrical energy and deploying electrical power to functional components of the product;

b. A means of generating solar power via Photovoltaic Cells, wherein the solar power generated is directed to said uninterruptable power supply;

c. A means for connecting the product to mains electrical power, wherein mains electrical power is directed to said uninterruptable power supply unit.

8. A Depository containment structure as in claim 1, further comprising:

a. A plurality of Weather Proof Seals positioned at closure contact points, anchor fixing points, and power inlets, for the purpose of avoiding contamination from the external elements.

9. A Depository containment structure as in claim 1, further comprising:

a. A means for Internet Connectivity, for sending and receiving, information and instructions, remotely;

b. A Communication Protocol for translating information and instructions for the purposes of remotely controlling and monitoring functional components of the product as well as recording and reporting data associated with delivery and collection transactions. Users can monitor and remotely control functional components via their MDB Delivery online account.

10. A Depository containment structure as in claim 1, further comprising a heating element for increasing internal temperature. A user can control, and monitor said heating element upon request via their online account, as set out in claim 9.

11. A Depository containment structure as in claim 1, further comprising a cooling element for reducing internal temperature. A user can control, and monitor said cooling element upon request via their online account, as set out in claim 9.

12. A Depository containment structure as in claim 1, further comprising a weight sensor for recording and measuring the weight of contents within said depository containment structure. Wherein the tare weight of contents is recorded during an unlock request, and a gross weight of contents is recorded at the time of locking. The difference between the tare and gross weights recorded provide a net weight which is associated with the delivery or collection transaction. A user can monitor the live weight of contents upon request via their online account, as set out in claim 9.

13. A Depository containment structure as in claim 1, further comprising a video camera for viewing the internal content of said depository containment structure for the purpose of visually recording a delivery or collection transaction. Wherein said video camera begins recording during an unlock request made via said lock system Interface and stops recording at the time of subsequent locking facilitated by said lock system. A user can monitor the live video feed via their online account, as set out in claim 9.

14. A Depository containment structure as in claim 1, further comprising an Internal Light positioned inside providing luminance to promote visibility. A user can control and monitor said internal light upon request via their online account, as set out in claim 9.

15. A Depository containment structure as in claim 1, further comprising an address plaque to identify the associated address of the product.

16. An internal carry case positioned within said depository containment structure allowing for convenient extraction of contents within depository containment structure, comprising: a. A single leaved hollow body to contain deposited contents and provide protection to functional components from deposited contents;

b. A plurality of handles for lifting and carrying said internal carry case and its

associated contents.

17. A mechanical lock, integrated with said lock system as in claim 1, wherein a mechanical lock is operated manually with a key to lock and unlock said closure of said depository containment, providing mechanical override access of said lock system.

18. A means of external locking said depository containment with an independent locking device, wherein protruding edges with slotted holes are positioned on the external leaf of said hollow body, and on external leaf of said closure, for the purpose of fastening both together with the use of an external lock, such as a padlock.

19. A service providing encrypted coding that is transmitted via near field communication technology from a mobile device to said lock system interface, said encrypted coding provides secure authorised unlocking of said lock system, thus providing secure access and ability to open said closure for depositing and collecting item/s.

20. An encrypted coding format as set out in claim 19, wherein said coding contains a series of auditable information, unique to a particular collection or delivery request, comprising: a. A MDB Vendor ID, further comprising; the vendors own order number, along with a bespoke code generated by MDB Delivery which is associated with said vendor upon registration and approval as a certified MDB Delivery vendor interface; b. MDB Courier ID, further comprising, a bespoke code generated by MDB Delivery which is associated with said courier upon registration and approval as a certified MDB Delivery courier interface;

c. MDB Recipient ID, comprising a bespoke code generated by MDB Delivery which is associated with said recipient upon registration and approval as a certified MDB Delivery recipient interface.

21. A service and method providing assurance to the delivery process by recording and

communicating information that is unique to a delivery or collection transaction, known as a Transaction Receipt. The information within said transaction receipt is recorded by functional components of said depository containment. Transaction receipt data is generated via a said communication protocol and is sent via internet connectivity, with data comprising:

a. A time and date record of access requests made via said lock system interface, information provided by said lock system interface;

b. A record of the Identity of the requestor, information provided by said lock system interface;

c. A weight record for the transaction, information provided by said weight sensor records;

d. A visual recording for viewing the actions taken during a delivery or collection transaction, information provided by said video camera records.

22. A service and assured method that is facilitated by an online account, wherein private persons or commercial entities can access a number of services, comprising:

a. A party can register to become an approved MDB Delivery User, wherein a person or company submit the required information for them to become a registered and approved MDB Delivery User for one, some, or all of the possible MDB Delivery interfaces (Vendor, Courier, Recipient);

b. A user can purchase MDB Delivery products;

c. A user can request survey and installation for enabling their MDB product;

d. A user can request MDB Delivery services, wherein a User can request collection and, or delivery services via their MDB product;

e. A user can view status updates for requested MDB Delivery service/s, wherein users can view updates for their MDB Delivery services;

f. A user can receive push notifications providing status updates for their requested MDB Delivery services;

g. A user can check the status of their MDB product, wherein a user can view; live lock status, live weight of contents, live visual feed, power status of the product as well as live temperature;

h. A user can remotely control the functional components of the MDB product

including as lock system, heating, cooling;

i. A user can raise transaction discrepancies, wherein a user can raise a discrepancy with MDB regarding their order, a MDB Delivery team will then evaluate discrepancies by investigating transactions using the transaction information recorded at the time of collection or delivery;

j. A user can request product maintenance, wherein a MDB party maintains or repairs a user's product;

k. A user can access customer support team.

23. A service that provides an integrated delivery process via an online platform providing direct three-way visibility for delivery transaction statuses and information, as well as an integrated communication platform between; vendors, couriers and recipients within a delivery process.

AMENDED CLAIMS

received by the International Bureau on 09 September 2020 (09.09.2020)

I Claim;

1. A Depository Containment Structure, that can be installed at a residential or commercial property, can be associated with the postal address to which it is installed and the party to whom it is registered, and can be used to temporarily house contents during a collection and or delivery transaction (figure 1), and can be governed in its operation by a governing body to provide security and assurance, comprising: a. A Hollow Body providing a cavity to allow storage of physical content (Figure 1 [Q]); b. An Opening in said hollow body, providing a point of access for depositing and

retrieving physical content (Figure 1 [S]);

c. A Closure connected to said hollow body providing access and security to said

opening (Figure 1 [I]);

d. Anchor Fixings for securing to the external point of contact (Figure 1 [C]);

e. Weatherproof seals to preserve the internal conditions and reduce the impact of external elements (Figure 1 [D]);

f. A plurality of Functional Components including; Lock System (Figure 1 [E]), Lock System Interface (Figure 1 [R]) (Figure 5), Mechanical Lock Override, Visual Recording (Figure 1 [H]), Weight Sensor (Figure 1 [J] ), Heating Element (Figure 1 [P]), Cooling Element (Figure 1 [P]), and a Light (Figure 1 [F]), said functional components record and control collection and delivery transactions providing assurances to collection and delivery processes, said functional components are programmed to operate automatically during a transaction, said functional components can be operated by a user locally, and remotely via an online account;

g. A means of Electrical Power Acquisition and Distribution to allow said functional components to operate (Figure 6);

h. A means of Communication Protocol linked to a remote server by internet

connectivity, facilitating remote control and monitoring of said functional components (Figure 1 [N]);

i. An Address Plaque to visually identify the associated postal address (Figure 1 [M]); j. An Internal Carrier providing an internal structure to protect said functional

components (Figure 1 [K]);

AMENDED SHEET (ARTICLE 19) k. A means of External Independent Locking, providing the ability to keep said closure secured with the use of an independent lock, such as a padlock (Figure 1 [A]);

L. A Governing Body that governs the application and use to provide security and assurances to the delivery process;

m. An online platform hosting a range of services.

2. A Hollow Body as in claim 1, further comprising:

a. A structure with an inner and outer leaf providing a hollow structure to house said functional components;

b. An insulating material positioned between said inner and outer leaves to reduce the influence of external temperatures (Figure 1 [V]);

c. A means for allowing said anchor fixings to pass through both inner and outer leaves to provide a physical connection with the external environment;

d. A means for allowing mains power inlet;

e. A means for allowing power and communications cabling to pass through into said closure, thus facilitating said closure with power and communications connectivity.

3. A Closure as in claim 1, further comprising:

a. A structure with an inner and outer leaf providing a hollow structure to house said functional components;

b. An insulating material positioned between said inner and outer leaves to reduce the influence of external temperatures;

c. Hinges fixed to the inner leaf of said hollow body, and inner leaf of said closure, allowing said closure to pivot providing opening and closing movement of said closure, said hinges are fixed to the inner leaves to reduce the risk of external tampering and unauthorised access (Figure 1 [G]);

d. A handle (Figure 1 [L]) to allow persons to physically open (Figure 1 [1]), and close (Figure 1 [2]) said closure;

e. A means for allowing cabling to extend through from said hollow body;

4. A Lock System as in claim 1 that comprises an apparatus that physically undertakes

movements between two positions to open and secure said closure from said hollow body, to provide governed access and security to said opening, further comprising:

AMENDED SHEET (ARTICLE 19) a. A means of physically moving between an extended position for locking and a retracted position for unlocking;

b. Where said lock system moves from its extended position (locked) to its retracted position (unlocked) the retraction of the apparatus opens said closure; c. Where said lock system moves from its retracted position (unlocked) to its extended position (locked) the extension of the apparatus closes said closure;

5. A Lock System Interface as in claim 1, comprising a unit providing an interface that facilitates the operation of said functional components including monitoring and governing the operation of said lock system, further comprising:

a. A clock and calendar for recording time and date of activity;

b. A contactless key interface such as near field communication to; receive, read and verify said encrypted coding (Figure 5 [A]);

c. A mechanical lock override as in claim 1 providing manual override operation of said lock system by using said lock system interface, wherein pressing the override key (Figure 5 [F]) followed by the input of a correct passcode sequence into the keypad will successfully instruct an unlock of said lock system;

d. An illuminated interface unit (figure 5 [A]) with numbers (figure 5 [G]), and action buttons to initiate sequences for; unlocking (figure 5 [FI]) and locking (figure 5 [I]), and identifying transactions prior to access such as a delivery (Figure 5 [D]) or a collection (Figure 5 [E] );

e. An illuminated information display screen (Figure 5 [B]);

f. Access validation technology that governs the operation of said lock system,

whereby requests for unlocking and locking are authorised or not authorised;

g. A means of detecting and reporting anomalies of said lock system such as an

unauthorised lock breach, whereby positioning sensors are integrated with the access validation software and sends an alert to the user when no authorisation has been sought and said lock system is in an unlocked state.

6. A lock system interface as in claim 5, further comprising a means of communicating with and recording data from said functional components, whereby said functional components automatically undertake a sequence of tasks before, during and after activity of said lock

AMENDED SHEET (ARTICLE 19) system, for each transaction, to record data for each transaction that will feature in said transaction receipt, sequence of tasks comprising:

a. Before successfully unlocking said lock system and after correct access credentials have been supplied, said lock system interface will record; date, time and identity of the user requesting the unlock, said lock system interface will then communicate with said functional components to; turn on said internal light, begin said visual recording and record tare weight of contents via said weight sensor;

b. during an unlocking said visual recording will continue;

c. after successful locking of said lock system, said lock system interface will record the date, time and identity of the party requesting locking, said lock system interface will then communicate with said functional components to; end said visual recording, record gross weight of contents via said weight sensor and calculate the net weight of the transaction, the next successful unlocking can only be permitted after this information is collated.

7. A plurality of Anchor Fixings as in claim 1, wherein said anchor fixings provide a method of fixing said Hollow Body to the external environment, further comprising:

a. Anchors with heads that are installed from the outer side of the inner leaf of said hollow body and pass through said hollow body and are embedded into the external environment, thus pinning said hollow body and preventing movement.

8. Electrical Power Acquisition and Distribution as in claim 1, wherein electrical energy is

acquired and stored before being distributed to said functional components, further comprising:

a. Photovoltaic Cells providing a means of acquiring electrical power via solar energy (Figure 1 [B]);

b. A means for connecting to mains electrical power as a secondary power supply (Figure 1 [T]);

c. An Uninterruptable Power Supply unit or Battery (Figure 1 [O]) (Figure 6 [B]) that stores electrical energy generated by said photovoltaic cells (Figure 6 [C]), and said mains power (Figure 6 [A]), and distributes electrical power to said functional components (Figure 6 [D]).

AMENDED SHEET (ARTICLE 19)

9. Weatherproof Seals as in claim 1 positioned at contact points of said; closure, anchor fixings, and power inlets, for the purpose of preventing contamination of the internal areas from the external elements.

10. A Communication Protocol as in claim 1, wherein data, recordings, instructions and

notifications can be sent and received via a remote server, facilitating remote transfer of information between said functional components and user via a computer or mobile device, further comprising: a. A means for Internet Connectivity, for sending and receiving, information and

instructions, remotely;

b. Remote Control Operation; providing the ability for a user to remotely control said functional components;

c. Live Monitoring; providing the ability for a user to monitor the live data of said

functional components;

d. Live Fault Reporting; providing a user with notifications relating to faults of said functional components;

e. Unauthorised Lock Breach alerts, as in claim 5.

f. Historical Data; providing access to data relating to remote control activity and

collection/delivery transaction data.

g. Transaction Receipts; whereby a data output is generated from said functional components for each collection/delivery transaction, and is made available in the form of an electronic receipt, known as a Transaction Receipt.

11. A Heating Element as in claim 1, that provides the functionality to increase the internal temperature of the cavity within said hollow body.

12. A Cooling Element as in claim 1, that provides the functionality to decrease the internal temperature of the cavity within said hollow body.

13. A Weight Sensor as in claim 1, wherein said weight sensor measures and records the weight of contents placed within said hollow body, further comprising;

a. A means of measuring and recording the live weight of contents at any time;

b. A means of measuring and recording the tare weight of contents prior to a collection or delivery transaction, whereby the weight of contents is automatically recorded

AMENDED SHEET (ARTICLE 19) upon an successful unlock request and before contents within said hollow body can be accessed;

c. A means of measuring and recording the gross weight of contents, whereby the weight of contents is recorded after said lock system has been locked after a transaction;

d. A means of recording the net weight of contents per transaction, whereby, the difference between said tare weight recording and said gross weight recording is calculated to provide a net weight per a transaction, conclusively negative net weight values would represent collection transactions where content has been removed, and positive net weight values would represent delivery transactions where content has been deposited.

14. Visual Recording as in claim 1, wherein a video camera visually records activity for a

collection or delivery transaction, whereby said visual recording automatically begins recording upon an unlock request made via said lock system interface and stops recording at the time of subsequent locking after a transaction.

15. An Internal Light as in claim 1, wherein a light provides illumination to the cavity of said hollow body and local areas to promote visibility, whereby said internal light is automatically switched on; upon a successful unlocking access request via said lock system interface, and when said live monitoring is in progress by a user.

16. An Internal Carrier as in claim 1, providing an independent structure that can be positioned within said hollow body, further comprising:

a. A single leaved hollow body that provides a secondary structure within said

depository containment structure to contain deposited contents and provide protection to functional components from deposited content;

b. Handles for lifting and carrying it and its associated contents.

17. A means of external independent locking as in claim 1, further comprising;

a. a protruding edge with a hole that is accessible when said closure is in a closed position (Figure 1 [2]), and is fixed from the inside of said hollow body with fixings that can be easily adjusted by the user such as screws or hexagon bolts;

AMENDED SHEET (ARTICLE 19) b. A protruding edge with a hole that is accessible when said closure is in a closed position (Figure 1 [2]), and is fixed from the inside of said closure with fixings that can be easily adjusted by the user, such as screws or hexagon bolts;

c. The ability to fasten together said hollow body and said closure, through the use of an external independent lock such as a padlock to interlock said holes on said protruding edges affixed to both said closure and said hollow body.

18. A depository containment structure as in claim 1, wherein its operation is governed by a Governing Body, said governing body is a party that can; govern a method of use, coordinate operational processes between users such as transactions, provide secure and controlled access for other parties, provide automated assurance by sharing information for each transaction to all parties, and provide aftercare such as resolving transaction discrepancies.

19. A governing body as in claim 18 that serves as the common interface between parties in a delivery/collection process through integrating; Vendors, Couriers and Recipients of a delivery processes (figure 7), by providing a registration service allowing users to become a registered user, further comprising:

a. Vendor Registration, said governing body allows a party to register with them as a Vendor, known as a Registered Vendor who sells items that require collecting and onward transit to the intended delivery address;

b. Courier Registration, said governing body allows a party to register with them as a Courier, known as a Registered Courier who collects item/s ready for delivery from said vendor and transports items for delivery onto the delivery address; c. Recipient Registration, said governing body allows a party to register with them as a Recipient, known as a Registered Recipient who is registered to receive items within a delivery process.

20. A governing body as in claim 18 that can remotely co-ordinate collection and delivery

transactions via linking the online accounts of registered users, comprising;

a. A user can raise a service request with said governing body defining a service

requirement for a collection or a delivery;

b. Said governing body can generate a job ticket for said service request which defines information of the requirement such as; collection address, delivery address and where possible the weight of the associated contents;

AMENDED SHEET (ARTICLE 19) c. Said governing body can then host said job ticket on an integrated platform such as an interactive map where the requirements are made visible to all registered couriers;

d. Said job tickets can be accepted by a registered courier whereby they accept to undertake the transaction;

e. Said job ticket can be ignored or rejected by a registered courier whereby no

acceptance is in place for them to undertake the transaction.

21. A governing body as in claim 18 that can provide secure and controlled unlocking and access permissions of said depository containment structure to parties other than the party to which said depository containment structure is registered to, secure and controlled access is provided by said governing body by generating encrypted coding and issuing it to said registered couriers, facilitating registered couriers with encrypted key codes to unlock a designated depository containment structure by presenting a designated encrypted code to said lock system interface in a method that is secure, controlled and auditable.

22. Encrypted coding as in claim 21 is generated by said governing body (figure 14) , and

contains a series of bespoke data held by said governing body (figure 13) that is compiled and transformed into an encrypted code for each transaction that can be issued to said registered couriers, and validated by said lock system interface.

23. A governing body as in claim 18 that can provide assurance to the delivery process by

recording transaction information generated by said functional components for each transaction, transaction information can be sent to all related parted parties within a transaction in the form of an electronic receipt known as a transaction receipt, and contains specific data relating to a collection or delivery transaction, comprising:

a. Transaction type, identifying whether the transaction was a collection or a delivery; b. time and date of transaction;

c. identity of the party requesting access;

d. A weight record for the transaction, information provided by said weight sensor; e. A visual recording for viewing the actions taken during a delivery or collection

transaction, information provided by said visual recording.

f. Status of the transaction, identifying if the transaction was successful or

unsuccessful.

AMENDED SHEET (ARTICLE 19) g. A comments section, whereby a note can be added to the transaction.

h. Photo upload, whereby a photo can be added to the transaction.

24. A governing body as in claim 18 that can provide dispute resolution between parties within a collection or delivery process, wherein parties are provided the opportunity to raise a discrepancy or request further action for a transaction, said governing body can coordinate actions and provide conclusion, further comprising;

a. Said governing body can receive discrepancies raised by users regarding issue/s with a transaction, such as a user reporting; a non-delivered item, a damaged item, or a missing item;

b. Said governing body can investigate discrepancies raised by users by observing the information recorded within said transaction receipt;

c. Said governing body can provide recourse actions in relation to transaction

discrepancies.

25. A governing body as in claim 18, further comprising a range of services made available via an online account, comprising:

a. User registration, as in claim 19;

b. Purchase products;

c. Survey, Install and Enabling, wherein a user can request services to establish said depository containment structure at their desired site;

d. Raise service requests, as in claim 20;

e. Status Updates, wherein a user can view the status for said service requests;

f. Push Notifications, wherein a user can receive automatic notifications during the process of each service request;

g. Product Status, wherein a registered user can check the status of said functional components;

h. A registered user can remotely control said functional components, as in claim 10; i. A registered user can raise discrepancies relating to a delivery or collection

transaction, as in claim 24;

j. A user can request product maintenance, wherein a party is coordinated to

maintains or make repairs to a user's product;

k. A user can access a customer support team.

AMENDED SHEET (ARTICLE 19) I. Site Plans and Photographs; whereby, layouts, access routes and photos of an address can be uploaded and accessed by couriers to better determine the location of said depository containment structure.

26. A Depository containment structure as in claim 1 that is not required to be registered by all parties within a delivery process to allow a delivery transaction to take place, wherein 3 possible relationship combinations exist (figure 8 [relationships; A, B and C only]), further comprising; a. a user can send items out for delivery by using said depository containment

structure that is registered to them and can be sent to a recipient that does not have said depository containment structure registered to them (Figure 8 [C]) (Figure 9 [MDB Relationship C]), said encrypted coding used for this relationship is formatted in a bespoke way to differentiate the transaction from other possible relationships (figures 19 & 20);

a. a user can send items out for delivery without using said depository containment structure and can be sent to a recipient that does have said depository containment structure registered to them (Figure 8 [B]) (Figure 9 [MDB Relationship B]), said encrypted coding used for this relationship is formatted in a bespoke way to differentiate the transaction from other possible relationships (figures 17 & 18); b. a user can send items out for delivery by using said depository containment

structure that is registered to them and send it to a recipient that has said depository containment structure registered to them (Figure 8 [A]) (Figure 9 [MDB Relationship A]), said encrypted coding used for this relationship is formatted in a bespoke way to differentiate the transaction from other possible relationships (figures 15 & 16).

27. A depository containment structure as in claim 1 that is variable in shape and size to better suit the individual needs of each user, further comprising: c. Domestic; a singular depository containment structure designed for a single party and is available in a plurality of sizes to accommodate the needs of each user for sending and receiving day-to-day items on a domestic scale and frequency (Figure 2);

AMENDED SHEET (ARTICLE 19) d. Multi Domestic; a plurality of depository containment structures joined together in one location designed for locations where multiple parties are present in a single location such as a block of flats, available in a plurality of sizes to accommodate the needs of each user for sending and receiving day-to-day items on a domestic scale and frequency (Figure 3);

e. Commercial; a singular depository containment structure designed for a single user and is available in a plurality of sizes to accommodate the needs of each user for sending and receiving items on a commercial scale and frequency (Figure 4);

f. Multi Commercial; a plurality of depository containment structures joined together in one location designed for locations where multiple parties are present in a single location, available in a plurality of sizes to accommodate the needs of each user for sending and receiving items on a commercial scale and frequency.

AMENDED SHEET (ARTICLE 19)

Description:
Patent Specification

Mv Drop Box Delivery (MDB Delivery)

Table of Contents

Defined Terms . 4

Executive Summary . 5

1. MDB Delivery Purpose . 7

2. MDB Products ..

2.1. Product Design

2.2. Product Features and Functionality .

2.2.1. Depository Containment Structure

2.2.2. Anchor Fixing .

2.2.3. Closure .

2.2.4. Weather Proofed Seals .

2.2.5. Lock System . 11

2.2.6. Insulated Casing . 11

2.2.7. Internal Carry Case . 11

2.2.8. Internet Connectivity . 11

2.2.9. Communication Protocol . 12

2.2.10. Lock System Interface . 13

2.2.11. Padlock Capability . 14

2.2.12. Weight Sensor . 15

2.2.13. Internal Video Camera . 15

2.2.14. Internal Lighting . 15

2.2.15. Heating and Cooling Element . 16

2.2.16. Power Supply . 16

3. MDB Delivery Service . 16

3.1. Online Account . 16

3.1.1. Request MDB Services . 17

3.1.2. Delivery Status . 17

3.1.3. Product Remote Control & Monitoring . 18

3.1.4. MDB Delivery Process Integration . 19

4. MDB Delivery Assurance & Process . 20

4.1. MDB Delivery Assurance . 20

4.1.1. Secu re Access . 20

4.1.2. Weight of Contents . 20

4.1.3. Visual Record . 21

4.1.4. Access Requestor Identity . 21

4.2. MDB Delivery Assurance Output . 21

4.2.1. Unsuccessful Delivery . 22

4.2.2. Successful Delivery . 23

4.3. MDB Interfacing Parties . 25

4.3.1. Types of MDB Vendor (Both Domestic and Commercial) . 25

4.3.2. Types of MDB Recipient . 26

4.3.3. Types of MDB Courier (Both Domestic and Commercial) . 26

4.4. MDB Interfacing Relationships . 27

4.4.1. MDB Interface Relationship Matrix . 27

4.4.2. MDB Relationship Flow Chart . 28

4.5. MDB Delivery Timeline Overview . 28

5. MDB Delivery Benefits . 28

5.1. The Environment . 29

5.1.1. Reducing Emissions . 29 5.2. Infrastructure . 30

5.2.1. Congestion . 30

5.3. Vendors . 31

5.3.1. Convenience . 31

5.3.2. Faster Deliveries . 31

5.3.3. Secure Process . 31

5.4. Couriers . 31

5.4.1. Reduced Failed Deliveries . 31

5.4.2. Faster Delivery Process . 31

5.4.3. Longer Delivery Window . 32

5.4.4. Optimise Courier Routing . 32

5.5. Recipients . 32

5.5.1. Convenience . 32

5.5.2. Faster Deliveries . 32

5.5.3. Security . 32

Appendix A: MDB Delivery - Relationship & Process Mapping (MDB-RPM) ....33

6. Introduction . 33

6.1. MDB Relationship A Process . 33

6.2. MDB Relationship B Process . 34

6.3. MDB Relationship C Process . 35

6.4. MDB Relationship D Process . 36

Appendix B: MDB Delivery - Encrypted Coding Structure (MDB-ECS) . 36

7. Introduction . 36

7.1. MDB User ID’s . 36

7.2. MDB Encrypted Code Generation and Structure Templates . 37

7.2.1. Example MDB ID Database . 37

7.2.2. Example MDB Coding Structure . 37

7.3. MDB Relationship Coding Examples . 37

7.3.1. MDB Relationship A . 38

7.3.2. MDB Relationship B . 38

7.3.3. MDB Relationship C . 38

7.4. Transmitting of MDB Delivery Encrypted Code . 39

Defined Terms

Ref Term Definition

DT1 Hollow Body A continuous structure with a flat bottom, and vertical sides surrounding its footprint.

DT2 Closure A door apparatus that is internally hinged to the Hollow

Body for opening and closing of the depository containment; Opening for access to collecting or delivering, and closing to secure.

DT3 Depository A structure that comprises a combination of the Hollow

Containment Body and Closure. Together these provide secure

Structure containment for items deposited and can be temporarily stored securely.

DT4 MDB My Drop Box - the completed Depository Containment

Structure encompassing all MDB Delivery functional components.

DT5 MDB My Drop Box Delivery - name of the company providing the

Delivery MDB product, assured service and process.

DT6 MDB MDB Vendor Only is a User that is a registered Vendor with

Vendor Only MDB to supply goods only, and does not have a MDB

product registered and enabled at their property or premises for the purposes of dispatching or receiving item/s.

DT7 MDB MDB Vendor and Sender is a User that is registered as an

Vendor and MDB Vendor to supply goods and has a MDB product Sender enabled and registered at their property or premises.

DT8 MDB A person or company that collects and/or delivers item/s

Courier within a delivery process between a vendor and a recipient.

DT9 MDB MDB Recipient is a User that has a MDB product registered

Recipient and enabled at their property or premises.

DT10 Non MDB MDB Recipient is a User that does not have a MDB product Recipient registered and enabled at their property or premises.

DT11 Traditional A person to person delivery transaction that does not

Delivery include an interface with a MDB product.

Process

DT12 User An interfacing User within the delivery process. A User can be either a private person or a commercial entity. Executive Summary

The MDB Delivery product is a mail and package deposit box that is registered to the address and party to which it is installed. The product has a door for accessing and securing. The door is internally hinged to prevent external tampering and can be locked to the main body of the deposit box. The product is fixed to its external environment with headed anchors installed from inside the deposit box, protruding through the deposit box, and embedding into the external environment thus pinning it securely. The product is fitted with a number of functional components that generate information for each transaction to provide an assured delivery process.

The MDB Delivery product provides couriers with a guaranteed point for collecting and delivering items within the delivery process. Couriers within a MDB Delivery process are registered and pre-approved parties for conducting dispatch and delivery services to MDB products. At the time a dispatch or delivery request is made, a designated courier receives an encrypted code from MDB Delivery which is associated with the dispatch and/or delivery request. The encrypted code is made available to the courier via their online MDB account. Once in possession of the encrypted code, the courier is then able to transmit the code from their handheld device via near field communication technology, to the lock system interface of the MDB Delivery product. Upon a valid encrypted code being presented, the locking system of the product will unlock, providing access for the courier to make a collection or a delivery. Once the courier makes the transaction and closes the door, the lock system will then automatically lock after 10 seconds. Alternatively, the courier can lock the product prior to the 10 second automated locking window by pressing the lock button on the lock system interface keypad. Once locked, the MDB product will then issue a transaction receipt to all parties within that delivery process. The transaction receipt contains the following information related to that transaction; Date, Time, Weight, Video recording, and the Identity of the registered courier. The information within the transaction receipt is generated by functional components of the product.

The MDB Delivery product is primarily powered by solar power which is generated by photovoltaic cells positioned on the product. Secondary power supply is received from mains power connectivity. Both primary and secondary power supply sources feed an uninterruptable power supply unit where electrical energy is stored. The uninterruptable power supply unit deploys power to the functional components of the product as and when required. The MDB Delivery product is fitted with internet connectivity and communication protocol, allowing information and instructions to be sent and received remotely between a MDB user and their registered product. The product is able to send transaction receipt information, and the user is able to monitor the status of their product as well as control its functional elements.

MDB Delivery provides registered couriers with a guaranteed collection and delivery point to securely collect and deliver items within the delivery process, therefore negating the need for the sender or recipient to be present at the time the transaction takes place. Furthermore, MDB Delivery provides a platform for couriers to make collections and deliveries 24hrs per day. MBD therefore provides vendors a more reliable method for achieving a same-day/next-day delivery service, when compared with traditional delivery process methods. MDB provides a guaranteed dispatch and delivery point for senders and recipients of deliveries making the sending and receiving functions for a delivery process more convenient. MDB Delivery provides couriers with better route management, bringing about process efficiencies throughout the wider logistics sector, meaning a greater ability for couriers to achieve more deliveries, successfully and securely. MDB Delivery can assist in contributing to enhancements of the environment by minimising vehicle emissions and

congestion by reducing travel time associated with deliveries and providing a more flexible window for couriers to make deliveries throughout the 24hr day. Furthermore, MDB Delivery can provide governance over when couriers can make deliveries such as restricting deliveries to non-peak hour travel time only, thus alleviating road traffic congestion, as well as incentivising its registered couriers to adopt more sustainable means of transit.

1. MDB Delivery Purpose

The MDB product is a Depository Containment Structure product that can be securely installed at an associated address. The MDB product has built in technology that only permits secured unlocking access to approved parties.

The MDB product is a guaranteed delivery point for couriers (private and commercial parties) making a delivery, it allows deliveries to be made 24 hours per day. MDB means a recipient of a delivery is not required to be physically present upon dispatching or receiving item/s. Therefore, removing the need for a Traditional Delivery Process and associated“signed-for” process.

MDB is also used as an assured collection point for dispatching items due for delivery. Users with a MDB product can place items due for delivery dispatch within their MDB product and can request a dispatch service via their MDB online account. This service benefits the sender of item/s as it bypasses the need for them to take the item to a delivery depot (such as a post office) for onward transit.

The MDB product houses several functions that contribute to providing an assured delivery service. Four functions of MDB products provide 4 sets of information for each delivery transaction, these include; Encrypted & Secure Access, weight record, visual record, courier identity.

Lock and Unlock technology is installed in a MDB product. Contactless sensors control the unlock function of the MDB product, the contactless sensors

communicate via near field communication technology sent from mobile devices. One-time encrypted passcodes are supplied to couriers prior to their transaction, allowing them gain secure access to a designated MDB product. Only MDB encrypted access codes permit unlocking access to MDB products. Additionally, for added security, only registered and approved couriers are able to obtain encrypted codes required for unlocking MDB products. The owner of a MDB have their own contactless access code for them to access their MDB product, as well as having a manual entry code and physical key for over-ride access. MDB products are installed with heating and cooling elements to enhance the breadth of uses for the User, meaning food items and other preservables can also be collected and delivered via MDB Delivery products.

MDB products come enabled with internet connectivity and communication protocol to allow; sending of information regarding delivery transactions, delivery status updates, remote control and remote communication.

Weight sensors are installed in the MDB product, the weight sensors provide information on the weight of deliveries as part of the assurance process.

Video camera is installed within a MDB product to record the delivery transaction taking place.

MDB Delivery maintains a record of all transactions and associated information related to each transaction. This information is made available to the respective MDB interfaces via their online account in the form of a transaction receipt. Where necessary should discrepancies arise for the delivery or collection of item/s the transaction receipt can be used to identify a responsible party and moreover identify a faster resolution to the issue at hand.

2. MDB Products

A package & mail drop box that can be installed at a suitable and accessible location at a domestic residence or commercial premises. An MDB product provides the infrastructure to the overall MDB solution. MDB Delivery products are suitable for both residential and commercial senders and recipients. Due to the differing needs of domestic and commercial parties, three products are available by MDB Delivery. All three MDB products have the same functionality and can be identified within this section. Figure 1 shows an example of a MDB Delivery Domestic product.

MDB Domestic Product: is a product installed at domestic properties.

Figure 2 outlines the concept design for a Domestic MDB product. This is appropriate for use at properties with an accessible external footprint, such as detached and semi-detached dwellings. MDB Multi Domestic: is a product installed at residential buildings, where more than one User lives within the same building. Figure 3 outlines the concept design for a Multi-Domestic MDB Product. This product is appropriate for properties where residents have no designated or accessible external footprint, such as residential blocks and high-rise flats.

MDB Commercial: is a product installed at commercial premises. Figure 4 outlines the concept design for a MDB Commercial product. This product is appropriate for sending and receiving large items.

For all 3 MDB product types a variety of sizes to be made available, to better suit the needs of the MDB Users.

2.1. Product Design

The product comprises of a secure hollow structure with an access point and closure for extracting and depositing item/s for delivery. The product self contains all functionality with components being built within the hollow sections of the Depository Containment Structure, between inner and outer leaves. Unlocking of the MDB’s closure for access is only permitted with a valid encrypted code or correct manual entry access code.

2.2. Product Features and Functionality

MDB provides freedom to Users to send and receive items for delivery at their leisure and without any of the hassle coordinating delivery times and reduces the need for repeated deliveries. The MDB process requires a User (Vendor and/or Recipient) to have a MDB product registered and enabled bat their receiving address, as well as a MDB registered and approved courier.

The MDB product includes a number of components and features to provide assurance to the delivery process. See the list of features within this section for more information. For the purposes of demonstrating the MDB product functionality, this specification refers to drawings which demonstrate functionality for MDB domestic product, only. The functionality of MDB products demonstrated within this section is transferable to all MDB products.

2.2.1. Depository Containment Structure

The primary feature of the product. The Depository Containment Structure contains all features and functionality documented within this section. The depository containment structure comprises an external and internal leaf that provides secured, insulated and weather proofed containment. Refer to item 1 and item 2 within Figure 1 for further detail.

2.2.2. Anchor Fixing

Anchor Fixings connect the Depository Containment Structure to the external environment. Anchor fixings are installed from inside the Depository Containment Structure for added security resilience and reduce the risk of external tampering. Refer to item C in Figure 1 for further detail.

2.2.3. Closure

A door to provide access for depositing and receiving deliveries. Closure is internally hinged to eliminate the risk of external tampering, and has an external handle to allow persons to open and close the Depository Containment Structure, safely. Refer to item I and item G within Figure 1 for further detail. 2.2.4. Weather Proofed Seals

Seals are installed at the door contacts, ground fixings, power inlets functional components, to preserve internal conditions of the depository containment. The purpose of the weather proofed seals to prevent ingress of external elements. Refer to item D within Figure 1 for further detail. 2.2.5. Lock System

Locking system to secure door and deny unauthorised entry to the MDB. The lock securely binds the closure and the Depository Containment Structure together.

Locking and un-locking control functions are available locally through the contactless code, manual code entry via the Lock System Interface, as well as by mechanical key for override, MDB Users can also control and monitor their lock system remotely via online account. The lock system will automatically lock after 10 seconds after the door is securely closed, or when the MDB courier presses the lock button on the keypad (which ever is first). When locked is confirmed the MDB Courier will be notified via their online account and prompted to mark the transaction as complete or incomplete. Refer to item E within Figure 1 for further detail.

2.2.6. Insulated Casing

Insulating material installed between the leaves of the Depository Containment Structure and within the door. Purpose of the insulated casing is to preserve the internal conditions of the Depository Containment Structure by reducing the influence of external elements and conditions. Refer to item V within Figure 1 for more detail.

2.2.7. Internal Carry Case

The internal carry case is positioned within the inner leaf of the Hollow Body. Its purpose is for MDB senders and recipients to conveniently carry all items due for dispatch or delivery at once. This function is not available for MDB Commercial product. Refer to item K within Figure 1 for more detail.

2.2.8. Internet Connectivity

Internet components securely contained within the leaves of the Depository

Containment Structure. Internet connectivity provides the means of communicating assurance information and facilitates remote control and monitoring. Information is sent via internet on to the MDB Delivery network. Refer to item N within Figure 1 for more detail. 2.2.9. Communication Protocol

MDB products have built-in communication protocol that translates, transmits and controls information and instructions via internet. The communication protocol permits the control, monitoring and reporting of MDB product functionality listed within this section. Users are able to access the remote control and status reporting via their online account. All delivery transactions and instructions are recorded by MDB as part of the MDB assurance process. Delivery transactions for a User’s MDB product are shared with the associated MDB User via their online MDB account. Refer to item M within Figure 1 for more detail. Information communicated via communication protocol comprise:

2.2.9.1. Activity Receipts - MDB Delivery retain a log of all activity for MDB products.

2.2.9.2. Collection and Delivery Transaction Receipts - MDB provide receipts for each collection and delivery request and associating the following information with the request to provide an audit trail for each collection and delivery made to an MDB product:

• Date & time - for both: unlock and lock actions,

• ID of courier that was granted access,

• Weight of T ransaction - recorded by calculating a net weight between the tare weight recorded upon unlocking, and a gross weight recorded at the time of locking.

• Visual record of the transaction - visual recording starts when the MDB is unlocked, and finishes when the MDB is locked.

2.2.9.3. Delivery Statuses - MDB Delivery provides Users with updates for their deliveries as they go through the stages in the delivery process.

2.2.9.4. MDB Control and Monitoring - MDB Delivery provides remote control functionality of the MDB and can be accessed via the Users online account. Functionality including:

• Lock and Unlock of the MDB;

• Heating and cooling on and off;

• View live feed from video camera;

• View live weight of contents;

• Power status:

o Solar Power generation status;

o UPS percentage of remaining power capacity;

o Mains Power status.

2.2.10. Lock System Interface

The lock system interface provides a user interface to the product. Refer to item R within Figure 1 . The lock system interface is also detailed as item A within Figure 5.1 allowing persons to securely unlock and lock the device. The lock system interface has a contactless function identified as (B) within Figure 5.1 , as well as a manual key pad function for override capability, identified as (C) within Figure 5.1.

2.2.10.1. Contactless Key Interface

The contactless key interface provides the primary form of assurance for the product and integrated service. Contactless key restricts permitted access to a MDB product to MDB registered and approved couriers, only. Couriers gain access to a MDB product by using a secure encrypted code generated by MDB for each delivery. The code is sent to a designated courier and stored in their handheld device within their MDB account. When a Courier is present at a MDB product they will first need to press the unlock button, identified as item H within Figure 5.2. Pressing the unlock button will then wake up the MDB product, the courier then presents the bespoke contactless code to the locking system interface for requesting unlocking of the device. The contactless key codes are transmitted from a handheld device via near field communication technology to the Contactless Key Interface on the MDB product. Once the courier has made their transaction they will then close the door and press the lock button. The lock button is identified as item I within Figure 5.2. When the lock button is pressed, the lock button will first will flash green while lock confirmation is sought, before turning solid green once locking is confirmed. Once lock confirmation is sought, the device is locked and will then generate a transaction receipt and issue it to the main server for forwarding on to all associated interfaces via their MDB account. MDB Vendor and Senders, and MDB Recipient parties have their own contactless key to receive their orders conveniently. Refer to Appendix B: MDB Delivery Encrypted Coding Structure (MDB-ECS) for more information regarding MDB Delivery encrypted coding.

2.2.10.2. Manual Entry Key Interface

The manual entry key interface, identified as item C within Figure 5.1 provides a means for manual overriding contactless interface in the event of a normal system outage or failure. The manual override is a numerical code that can be entered into the manual keypad. The manual keypad is identified as item G within Figure 5.2. To use the Manual entry key interface for gaining access, the user will need to first press the Override button, identified as item F in Figure 5.2 to wake up the product and trigger the override code process. The user will then press the respective transaction button for the function they are accessing the product for;

• For a delivery transaction the user will press the Delivery transaction button, identified as item D within Figure 5.2.

• For a collection transaction the user will press the Collection transaction

button, identified as item E within Figure 5.2.

After the transaction button is pressed the user will then enter their numerical override code into the manual keypad followed by the unlock button identified as item H in Figure 5.2. For security purposes, each time the manual override key is used the User is be notified and are requested to verify the override activity. In the event of a manual key code entry failure the User can access their MDB product with a unique mechanical key that physically overrides the lock system.

2.2.11. Padlock Capability

MDB products have padlock capability built in for added security. Users are able to padlock their MDB products for additional reassurance, however Users are warned that if they are expecting a MDB collection or delivery, then padlocks are to be removed in order for couriers to achieve successful access. If padlocks are not removed the MDB user will be responsible for any unsuccessful transactions recorded. Refer to item A within Figure 1 , or Figure 14 for more detail.

2.2.12. Weight Sensor

The second form of assurance. Weight sensors are positioned at the bottom of the Hollow Body. The weight sensors generate weight stamps before and after deliveries are made. The weight recording is made available in the Transaction Receipt for the particular collection or delivery, on the Users online account. A MDB User is also be able to view the live weight status of their MDB product via their online account.

Refer to item J within Figure 1 , or Figure 15 for more detail.

2.2.13. Internal Video Camera

The third form of assurance is to document a visual record of collections and deliveries being made. A video is triggered upon all successful access being granted to a MDB product. A short clip is be recorded of the transaction process. The video will end once the door has been locked after collection or delivery. The video camera is positioned inside the Depository Containment Structure and films the internal aspects. The recording for a MDB collection or delivery is made available in the MDB Transaction Receipt, made available to Users via their online account. The MDB User is able to view the contents of the MDB at any time via their online account. Refer to item H within Figure 1 , or Figure 16 for more detail.

2.2.14. Internal Lighting

Positioned inside the Depository Containment Structure to assist the video camera visibility when recording, along with providing a safe and visible environment for making and receiving collections and deliveries. The light turns on when the MDB product is unlocked and turns off when the MDB product is locked. The light turns on when a User remotely views the contents of their MDB via their online account. Refer to item F within Figure 1 , or Figure 17 for more detail. 2.2.15. Heating and Cooling Element

Heating and Cooling elements are installed in the Depository Containment Structure and provides heating and cooling boost as required to preserve certain deliveries (e.g. food deliveries) at the Users discretion. The MDB User is able to control heating and cooling via their online account. Refer to item P within Figure 1 , or Figure 18 for more detail.

2.2.16. Power Supply

Power is required to support the functionality of the product. Power is deployed to the MDB via a UPS (Uninterruptible Power Supply) from primary and secondary power supply sources, as identified below:

2.2.16.1. Primary Power - supplied by solar power via

Photovoltaic Cell. This is identified as item C in Figure 6. Also see item B in Figure 1 for more information.

2.2.16.2. Secondary Power - supplied by Mains Power

connectivity in the event of Solar/UPS failure, or inadequacy. This is identified as item A in Figure 6. Also see item T and item U within Figure 1.

3. MDB Delivery Service

3.1. Online Account

MDB Users are required to have a MDB account from which their MDB product and personal/company information is registered to. The Users account is hosted on an online platform. From their online account, MDB Users can; Request MDB services, remotely control their MDB product, monitor the status of their MDB product, and check the statuses for their requested services. 3.1.1. Request MDB Services

3.1.1.1. Delivery - from their online account a MDB User can request delivery to their MDB. For example, when a User makes an order online and selects MDB as their delivery option the with the vendor, a MDB service request is generated, therein MDB Delivery generate the encrypted code for that order and distribute it to a designated, courier.

3.1.1.2. Dispatch - The User can request for dispatch of a delivery by sending a delivery from their MDB product. The User requests dispatch service via their online account. The User places item/s in their MDB clearly displaying the delivery address as per normal delivery processes. MDB then coordinate courier collection before onward transit to the intended recipient. Should the recipient be an MDB Recipient, this will become evident at the time of making the dispatch request. The User requesting dispatch services will be notified if the recipient is a MDB Recipient. The sender is then prompted to select whether they wish to send to the recipients MDB, or as per traditional person to person delivery method.

3.1.2. Delivery Status

Throughout the delivery process the MDB online platform provides all Users with visibility of the status for all of their MDB requested services. From their online account The MDB User is able to receive and view the following:

3.1.2.1. Notifications - Users can choose which notifications they wish to receive and which notification they do not wish to receive regarding their requested service/s. 3.1.2.2. Progress of MDB Requests - Users can check statuses for all of their MDB deliveries and dispatches along with an estimated date and time for collection or delivery.

3.1.2.3. Transaction Receipts - Users will receive a transaction

receipt for their requested. The information contained within the transaction receipts are generated from the functional elements of the MDB product and will contain the following information:

• Date and Time - the date and time of when the transaction took place, recording the unlock date and time as well as the date and time of the lock confirmation.

• Courier ID - identity of the user that made the transaction

• Weight - the weight of the transaction made.

• Video Recording - a visual record of the transaction.

3.1.3. Product Remote Control & Monitoring

MDB products are enabled with internet connectivity and have communication protocol technology with defined communication parameters. This allows MDB Users to remotely control their MDB products and monitor their status. From their online account Users are able to utilise the following functions of their MDB product, remotely:

3.1.3.1. Lock & Unlock - the User is able to remotely control and monitor status for lock and unlock their MDB.

3.1.3.2. Turn Heating On and Off - the User is able to remotely

control the heating system, as well as monitor its status.

3.1.3.3. Turn Cooling On and Off - the User is able to remotely

control the cooling system, as well as monitor its status.

3.1.3.4. Turn Lighting On and Off - the User is able to remotely

control the lighting on and off as well as monitor its status.

3.1.3.5. View Contents - the User is able to remotely view a live

stream of their MDB’s contents. 3.1.3.6. Monitor Weight - the User is able to remotely view the weight of contents within their MDB.

3.1.3.7. Monitor Power Status (UPS and Solar) - the User is able to remotely monitor and set status notifications regarding the power of their MDB via their online account. Such as;

• Photovoltaic cell working - Yes/No

• UPS working - Yes/No

• UPS back-up power remaining (time and percentage)

• Mains Power working - Yes/No

3.1.3.8. Location & Disturbance Alert - The User is alerted if their

MDB product changes location, or if the lock system has been breached without validity. In the event of a lock breach a Transaction Receipt is generated as per normal validated entry which includes a video recording of the event.

3.1.4. MDB Delivery Process Integration

The MDB product and service provides optimum integration between all parties involved in the delivery process. As Figure 7 demonstrates, MDB provides a platform whereby all parties have visibility of a delivery via their online account, with access to information such as; Product ID, Order ID, Delivery status updates, MDB Delivery Assurance information. This therefore enhances transparency of the delivery process, thus further promoting reliability, sustainability and speed of deliveries.

MDB provides a link between all parties entailed within the delivery process meaning optimum efficiency and effectiveness of the delivery process. The Traditional Delivery Process typically connects two of the three parties in a delivery process, however MDB provides a platform for connectivity and visibility between all three parties to promote a more; proactive, efficient and effective global delivery solution. 4. MDB Delivery Assurance & Process

4.1. MDB Delivery Assurance

MDB provides assurance to a delivery service. MDB delivery assurance is provided via the design, functionality and audit trail of information collated by a MDB product for MDB collection and delivery transactions. The following sections list and describe the 4 lines of assurance provided by MDB in the delivery process.

4.1.1. Secure Access

MDB provides a manual key to the owner of a MDB product which can only unlock that particular MDB product. Couriers accessing a MDB product are be provided with a contactless one-time encrypted passcode via their MDB online account. The passcode generated is unique for each delivery. Onetime passcodes provide certified and secured access to MDB products, see Appendix B: MDB Delivery Encrypted Coding Structure (MDB-ECS), for an example of the MDB contactless encrypted coding structure. When a valid MDB contactless code is presented to the MDB lock system interface, the code will request unlocking of the MDB lock system. Before unlocking is achieved, the MDB will record the following information from its functional elements providing an audit trail relatable to the transaction in question:

• Date of the request;

• Time of the request;

• Tare weight of the MDB contents;

• Video camera start;

• Identity of the MDB Courier requesting access

4.1.2. Weight of Contents

During an unlock request being sought from a MDB product, the MDB automatically records the tare weight of contents within the MDB product, before unlocking is granted and additional contents can be deposited. When contents have been added and the MDB is subsequently closed and locked, the gross weight of contents within the MDB are automatically recorded. The difference between the tare and the gross weight provide the net weight which is associated to the transaction.

4.1.3. Visual Record

During an unlock request being sought from an MDB product, the video camera inside the MDB product begins to record the delivery transaction. The recording stops once the MDB product has been successfully locked. This information is recorded and associated with the transaction made.

4.1.4. Access Requestor Identity

Anyone with unlocking rights to a MDB product will have to first be a registered and approved MDB Courier, this can be either a commercial courier, or private persons conducting a private delivery. Upon unlocking of a MDB product, a series of information is collated and recorded. Part of this information is the identity of the User whom unlocked the MDB product. See Appendix A: MDB Delivery Relationship and Process Mapping (MDB-RPM), for more information.

4.2. MDB Delivery Assurance Output

The secure access to MDB products provides secure containment for items to be collected from, or delivered to, a MDB product. The User is able to retrieve item/s at their own convenience. Additionally, the audit trail available from the MDB transaction receipt, allows MDB to investigate any discrepancies raised in the delivery process, and where necessary escalate directly with the relevant parties for mitigation and fast resolution.

At the end of an MDB delivery process the MDB Recipient is required to select a status for each delivery. The status selected determines the course of action in order to close out the request. Until the transaction has been verified by the MDB

Recipient as; successful, and complete, the MDB request remains open on their account. Below are possible statuses for both unsuccessful and successful deliveries, along a description and where practicable, the routes for mitigation in each case.

4.2.1. Unsuccessful Delivery

4.2.1.1. Not Delivered -“This delivery is not here”

This status is selected by the MDB Recipient if a MDB delivery is stated as complete by the MDB Courier but the item/s are not present when the recipient goes to collect it from their MDB. MDB Delivery are then able to investigate this by identifying the; date and time, ID of the MDB Courier, weight of the transaction, and a video record of the delivery transaction taking place for that specific delivery.

The transaction information generated by MDB, allows MDB Delivery to identify a responsible User for an item being marked as Not Delivered.

Examples as follows:

4.2.1.1.1. Recipient Responsible - if the“Not Delivered” status has been incorrectly entered by the MDB Recipient and the package has in fact been successfully delivered, this will become evident upon MDB viewing the data from the transaction receipt. In this case the MDB Recipient will receive a notification to state that there is evidence of the delivery being successfully made and will prompt the MDB Recipient to update their status accordingly.

4.2.1.1.2. Courier Responsible - if the“Not Delivered” status has been correctly entered by the MDB Recipient and the package has not been delivered, this will become evident upon the weight and visual records hosted by MDB for the associated delivery transaction. In this case the MDB Courier will receive a notification stating there is evidence of a non-delivered item for a particular delivery. Furthermore, if the courier appears to have; obscured, damaged or interfered with the MDB, the delivering User will be held responsible and receive a notification informing them of a non-delivered item, all the same. Successful Delivery

4.2.2.1. Incorrect Order

4.2.2.1.1. Entire Delivery Is Incorrect -“This Delivery has arrived, but is not what I wanted, I want to return the entire delivery”

This status will be selected by the MDB Recipient if a MDB delivery has been successfully delivered but the entire delivery is incorrect. The MDB Recipient will be prompted to provide details about the delivered contents stating what is wrong with the order. MDB will then escalate this with the vendor from which the MDB Recipient ordered from. MDB Delivery, or the MDB User can generate a MDB collection and delivery request from the recipients MDB product to return item/s to the vendor, see Figure 7 for more information.

4.2.2.1.2. Part of Delivery of Incorrect -“This delivery has arrived, but some items are incorrect, I want to return the incorrect items”.

This status will be selected by the MDB Recipient of a MDB delivery has been successfully delivered but part of the delivery is incorrect. The MDB Recipient will be prompted to provide details about the delivered contents stating what is wrong with the order. MDB will then escalate this with the Vendor from which the MDB Recipient ordered from. MDB Delivery, or the MDB User can generate a MDB collection and delivery request from the recipients MDB product to return the item/s to the vendor, see Figure 7 for more information.

Damaged Order

4.2.2.2.1. Entire Delivery is Damaged -“This delivery has arrived, but it is Damaged”

This status will be selected by the MDB Recipient if the transaction has been successful but the entire delivery is damaged. The MDB Recipient will be prompted to provide details about the delivered contents stating what is wrong with the order. MDB will then escalate this with the Vendor from which the MDB Recipient ordered from. MDB Delivery, or the MDB User can generate a MDB collection and delivery request from the recipients MDB product to return the item/s to the vendor, see Figure 7 for more information.

4.2.2.2.2. Part of Delivery is Damaged -“This delivery has arrived, but some items are damaged, I want to return the damaged items”

This status will be selected by the MDB Recipient of a transaction has been successful but the entire delivery is damaged. The MDB Recipient will be prompted to provide details about the delivered contents stating what is wrong with the order. MDB will then escalate this with the Vendor from which the MDB Recipient ordered from. MDB Delivery, or the MDB User can generate a MDB collection and delivery request from the recipients MDB product to return the item/s to the vendor, see Figure 7 for more information. 4.2.2.3. Completed Order

4.2.2.3.1. The Delivery has been received and is complete

-“The item/s have arrived and it is what I wanted, Thanks MDB”

This status will be selected by the MDB Recipient if a MDB delivery has been successfully delivered, and the MDB Recipient has collected it from their MDB with no damages or issues with the delivered items.

4.3. MDB Interfacing Parties

This section defines the possible interfacing parties (or Users) of the MDB process and the scenarios when the MDB service can be used.

The MDB process consists of 4 potential interfaces. The 4 potential interfaces are made up of 2 types of Vendor, and 2 types of Recipient. All interfaces are all connected by a Courier party.

All interfacing parties must be registered with MDB Delivery to enable them to undertake their respective roles within the MDB Delivery process.

All types of; Vendors, Couriers and Recipients stated apply to both Domestic and Commercial entities.

4.3.1.Types of MDB Vendor (Both Domestic and

Commercial)

4.3.1.1. MDB Vendor & Sender

MDB Vendor and Sender is a User that is registered as an MDB Vendor to supply goods and has a MDB product enabled and registered at their property or premises. This User uses their MDB product to dispatch their goods. The goods for dispatch are then collected by a registered MDB Courier and are transited to a Recipient by the courier. 4.3.1.2. MDB Vendor Only

MDB Vendor Only is a User that is registered as a Vendor with MDB Delivery to supply goods, but does not have a MDB product registered and enabled at their property or premises for the purposes of dispatching or receiving item/s. MDB Vendor Only parties, dispatch their item/s for delivery via the Traditional Delivery Process.

4.3.2. Types of MDB Recipient

4.3.2.1. MDB Recipient

MDB Recipient is a User that has a MDB product registered and enabled at their property or premises. This User receives delivered item/s via their MDB product. Items are delivered to their MDB product by registered MDB

Couriers.

4.3.2.2. Non MDB Recipient

Non-MDB Recipient is a User that does not have an MDB product registered and enabled at their property or premises. This User receives their item/s as per the Traditional Delivery Process.

4.3.3. Types of MDB Courier (Both Domestic and

Commercial)

MDB Couriers are registered and approved couriers with MDB Delivery, these can be both; commercial entity, or private persons. Within the MDB process Couriers can be further identified as; MDB Courier (Collection), and MDB Courier (Delivery), these roles are defined below.

4.3.3.1. MDB Courier (Collection)

A MDB Courier (Collection) party is one that collects item/s from an MDB Vendor and Sender’s MDB product. MDB generates and provides the MDB Courier with encrypted coding to their hand-held device, permitting the courier with access to a designated MDB product.

4.3.3.2. MDB Courier (Delivery)

A MDB Courier (Delivery) party is one that delivers item/s to a MDB

Recipient’s MDB product. MDB generates and provides the MDB Courier with encrypted coding to their hand-held device, permitting the courier with access to a designated MDB product.

Where MDB Delivery services are end-to-end, such as Relationship A (defined below), the MDB Courier (Collection) and MDB Courier (Delivery) can be the same User.

4.4. MDB Interfacing Relationships

MDB Delivery assurance is dependent on whether the recipient of a delivery has a MDB product enabled and registered at their property or premises. Of the potential MDB interfacing parties; 2 are Senders, 2 are Couriers, and 2 are Recipients. To best demonstrate the potential relationships associated with the MDB service, the matrix below in Figure 8 demonstrates only the Sender and Recipient parties as ultimately, they are bound by a couriering User regardless. The Matrix below demonstrates 4 potential relationships, identified as A-D. Only 3 of these potential relationships are applicable to the MDB service (A-C). The remaining relationship (D) is a surplus one that ultimately provides no MDB service. This surplus relationship identifies a traditional person to person delivery method and is included for completeness.

4.4.1. MDB Interface Relationship Matrix

See Figure 8 for the MDB Delivery Interface Matrix. 4.4.1.1. MDB Relationship Matrix Summary

Relationships A & B: are relationships that provide a MDB assured Delivery Service as the Recipient has a MDB product enabled at their property or premises. Relationship C: is a relationship that can be partly facilitated by the MDB service but cannot provide a MDB Assured Delivery Service, as the Recipient does not have a MDB product enabled and registered at their property or premises.

Relationship D: is not a MDB service and is a surplus relationship due to the potential interfacing parties. Relationship D has been included for completeness in demonstrating the MDB relationships.

4.4.2. MDB Relationship Flow chart

The process flowchart below in Figure 9 depicts the path for each defined MDB Delivery relationship (A-D).

For more detail on the MDB relationships (A-D) and associated processes, see Appendix A: MDB Delivery Relationship and Process Mapping (MDB-RPM).

4.5. MDB Delivery Timeline Overview

Figure 10 demonstrates a high-level timeline of a MDB Delivery process, denoting the steps involved from a MDB request being made through to a MDB request being closed out.

5. MDB Delivery Benefits

MDB provides a more efficient, faster and convenient delivery service, minimising the rate of failed deliveries and reducing overall journey times required to complete a delivery process. The following is a list of key beneficiaries of the MDB Delivery. 5.1. The Environment

5.1.1. Reducing Emissions

5.1.1.1. Reduced Failed Deliveries

Due to MDB providing a guaranteed point of delivery this means couriers will experience less failed deliveries, thus will have to conduct less; repeat deliveries and return to sender journeys. Additionally, recipients will not have to retrieve failed delivered item/s from collection points.

5.1.1.2. Minimises Associated Travel Time for Deliveries

MDB Vendor and Sender Users are able to send items from their MDB, whereby the User places item/s in their MDB and a MDB registered courier collects item/s for onward delivery to a recipient address. The MDB process minimises the travel time associated with each delivery, especially when the recipient is also a registered MDB Recipient. For example, the travel associated with the sender taking an item to a local post office is not required.

MDB therefore minimises the potential travel associated with a delivery, making each delivery as efficient as possible. MDB also allows couriers to more efficiently plan their day-to-day delivery and collection routes as they are not obliged to work around the availability of the sender or recipient. Figure 11 below, demonstrates a traditional national delivery process, in six stages. Figure 12 below, demonstrates MDB national delivery process, in 5 stages. A comparison between Figure 11 and Figure 12 shows MDB has the ability to combine stages 1 and 2 of the Traditional Delivery Process. Whereby items are sent directly from the MDB Sender to the local sorting office in a coordinated route for onward dispatch to the recipient. This results in a more direct approach to dispatching item/s, whilst enhancing the speed of a delivery in reaching the recipient.

5.1.1.3. Sustainability Governance

As a minimum, MDB will promote sustainability efficiencies of the delivery process through providing a more direct delivery process by minimising the transit time per delivery. Furthermore, MDB can provide sustainability governance of its registered couriers regarding emissions, by setting minimum prequalification requirements for vehicle emissions.

5.2. Infrastructure

5.2.1. Congestion

Traditional Delivery Process methods are restricted to normal working and waking hours due to the requirement for having the recipient present to receive a delivery. Traditional Delivery Process services normally offer a maximum delivery window of 12 hours, for example 08:00-20:00hrs. Due to MDB being a guaranteed delivery point, MDB provides up to 24 hrs availability for couriers to make deliveries to recipients. This provides couriers with a large window of availability to make their deliveries. Due to the increased availability for deliveries, this will in turn reduce the level of congestion as deliveries can be made during more efficient times throughout the day. To further promote the cause for easing traffic congestion, MDB can restrict their registered couriers from making collection and delivery transactions during peak hours of travel. For example, no MDB deliveries to be made between 07:00-09:00hrs and 16:00-18:00hrs, therefore restricting delivery windows to 09:00-16:00hrs and 18:00hrs-(+1day) 07:00hrs. In this example, couriers would still have a 20-hour window per day to make deliveries, which is significantly more than current delivery window bestowed on Traditional Delivery Processes. Further infrastructure benefits from having reduced levels of congestion would be as follows:

• Increased efficiency and effectiveness of emergency services.

• More efficient public transport services.

• Reduced risk of road traffic accidents during peak hours.

• Promote the concept and lifestyle of cycling and walking between destinations due to a safer road transport culture.

• Overall better lifestyle. 5.3. Vendors

5.3.1. Convenience

MDB Vendor and Senders are not required to travel to a dispatch point when sending an item for delivery via their MDB. They simply place items due for dispatch into their MDB product and arrange courier pickup and delivery via the MDB online platform.

5.3.2. Faster Deliveries

Due to the increasing demand of customers and the global economy, Vendors are under pressure to achieve next day and same day deliveries for their customers. MDB provides the infrastructure and process required for Vendors to meet the growing demands and expectations of customers in achieving successful same day/next day deliveries. 5.3.3. Secure Process

The MDB assurance process reduces the risk of packages being interfered with during the delivery process. Additionally, MDB reduces the risk of any fraudulent activity and eliminates the risk of deliveries being intercepted when left in good will, outside a recipient’s property or premises. 5.4. Couriers

5.4.1. Reduced Failed Deliveries

MDB will provide couriers with a guaranteed point of dispatch and delivery. Meaning each MDB collection and delivery will be achievable regardless of whether the sender or recipient is present at the property.

5.4.2. Faster Delivery Process

Due to providing a guaranteed point of delivery, couriers are not obliged to wait for recipients to be present (such as waiting for a recipient to answer the door) or work around a time slotted delivery system. Couriers can simply undertake the swift MDB process and move onto the next collection or delivery. 5.4.3. Longer Delivery Window

As MDB is available 24hrs per day, this provides couriers with a longer window to make deliveries when compared to Traditional Delivery Processes.

5.4.4. Optimise Courier Routing

Due to MDB providing a guaranteed point for collection and delivery, couriers can further optimise their operations by more efficiently planning their day to day collection and delivery routes as well as being able to utilise a larger operational window. The courier will not need to make a collection or delivery for a specified window to suit the sender or recipient providing flexibility to their timetable, thus allowing them to optimise their routing. 5.5. Recipients

5.5.1. Convenience

Recipients are not required to be present to receive item/s for delivery. Items are delivered by couriers to recipients via the designated MDB product. This provides convenience to recipients, as they are not obliged to structure their day around receiving a delivery and equally are not at risk of missing a delivery.

5.5.2. Faster Deliveries

Due to a longer delivery window and other improvements to delivery efficiencies, MDB Users can receive items faster than Traditional Delivery Process methods.

5.5.3. Security

The MDB assurance process reduces the risk of packages being interfered with during the delivery process. Additionally, MDB eliminates the risk of deliveries being intercepted when left outside a recipient property. Appendix A: MDB Delivery - Relationship & Process Mapping (MDB-RPM)

6. Introduction

This section of the specification details the steps involved in a typical MDB delivery process for each potential MDB delivery relationship.

The matrix below demonstrates the potential MDB relationships between MDB Vendors (Senders) and MDB Recipients. There are 4 different relationships identifiable as A, B, C & D.

Relationships A & B provide MDB delivery assurance.

Relationship C can be facilitated by MDB but cannot provide an MDB assured delivery service as the recipient does not have a MDB product registered and enabled at their property.

Relationship D is a surplus relationship as a result of including all possible interfaces. This relationship demonstrates traditional person to person deliveries.

Refer to Figure 8 for more information regarding the MDB Interface Relationship Matrix.

Refer to Figure 9 for more information regarding MDB Relationship process for each defined MDB relationship in the form of a process flow chart.

6.1. MDB Relationship A Process

MDB Vendor and Sender - Delivering to - MDB Recipient:

MDB Delivery Relationship A is a delivery transaction between two MDB users, a sender and a recipient who both have a MDB product registered and enabled at their property or premises. These two users are known as; MDB Vendor and Sender, and MDB Recipient. The sending User sends item/s due for delivery via their MDB by unlocking their MDB with their encrypted contactless code or manual keypad entry and placing the item/s to be delivered inside, before closing and locking their MDB product. The sending User then initiates collection via their account on the MDB online platform. A designated MDB courier is then initiated via MDB to retrieve the item/s to be delivered. The MDB Courier subsequently collects the item/s to be delivered from the sending MDB. The courier then gains access to the Sending MDB through via their encrypted access code generated by MDB that is transmitted to the locking system interface from the couriers handheld device. The courier then transits the item/s for onward transit to the recipients address. A MDB Courier is then required to gain access to the receiving MDB product at the recipients address, again the MDB Courier uses their handheld device to transmit a contactless encrypted access code to the receiving MDB to gain access. The courier then deposits item/s into the receiving MDB, before closing and locking the receiving MDB.

The MDB Recipient can then securely collect their item/s from their MDB product at their own convenience by unlocking the MDB with the use of their own encrypted key or personal manual entry override code.

Registered and approved MDB Couriers are the only third party able to obtain encrypted codes from MDB Delivery, allowing access to a user’s MDB product.

6.2. MDB Relationship B Process

MDB Vendor Only - Sending to - MDB Recipient:

MDB Delivery Relationship B is a delivery transaction between a sending User that does not have a MDB product registered and enabled at their property or premises, and a recipient User that does have a MDB product registered and enabled at their property or premises. These two parties are known as: MDB Vendor Only, and MDB Recipient.

The sending User sends item/s due for delivery via the traditional delivery process dispatch method. A designated MDB courier then collects item/s from a sorting depot and transits item/s to the address of the MDB recipient. The MDB courier uses their handheld device to transmit an encrypted key to gain access to the receiving MDB product. The courier then deposits item/s into the receiving MDB, before closing and locking it.

The MDB Recipient can then securely collect their item/s from their MDB product at their own convenience by unlocking the MDB with the use of their own encrypted key or personal manual entry override code.

Registered and approved MDB Couriers are the only third party able to obtain encrypted codes from MDB Delivery, allowing access to a user’s MDB product.

6.3. MDB Relationship C Process

MDB Vendor and Sender - Sending to - Non MDB Recipient:

MDB Delivery Relationship C is a delivery transaction between a sending User that has a MDB product registered and enabled at their property or premises, and a User that does not have a MDB product registered and enabled at their property or premises. These two parties are known as MDB Vendor and Sender, and Non MDB Recipient.

The sending User sends item/s due for delivery via their MDB by unlocking their MDB product and placing the item/s to be delivered inside, the sending User then initiates collection via their account on the MDB online platform. A designated MDB courier is then initiated via MDB to retrieve the item/s to be delivered. The MDB courier then gains access to the Sending MDB via the use of an encrypted key generated by MDB that is transmitted to the MDB product via the MDB Courier’s handheld device. Once item/s are collected the courier will then transit the item/s to be delivered for onward forwarding to the recipient via the traditional delivery process.

The sending User is able to conveniently place items due for dispatch into their MDB product for onward dispatch to the recipient without having to transport personally to a dispatch point.

Registered and approved MDB Couriers are the only third party able to obtain encrypted codes from MDB Delivery, allowing access to a user’s MDB product.

Refer to the flow chart in Figure 9 for an overview of relationship C. 6.4. MDB Relationship D Process

MDB Delivery Relationship D demonstrates Traditional Delivery Process, there are no detailed MDB processes defined for this relationship. Relationship D has been included for the purposes of completeness in demonstrating the MDB Delivery process. Refer to the flow chart in Figure 9 for an overview of relationship D.

Appendix B: MDB Delivery - Encrypted Coding Structure

(MDB-ECS)

7. Introduction

This section of the specification outlines the information associated with the MDB encrypted coding requirements in order to provide secure validated MDB Courier access to a MDB product.

Assuring the delivery process is a key part of the MDB offering. To provide assurance, MDB generates a unique code for all transaction. The unique coding will provide secured access for all collections and deliveries made via MDB.

For security purposes, the coding generated for each delivery will be encrypted via information held by MDB for the interrelating parties within a MDB Delivery process.

7.1. MDB User IP’s

All MDB Users will require a MDB account to use MDB services. Through their MDB account, Users can select to register themselves as one, some or all of the possible MDB Delivery interfaces. Information provided by the user at the time of registration will be used to verify their account and approve the User to conduct each of the their selected MDB roles. For each party that a MDB User registers themselves as, unique codes will be generated and associated with their account. • (1) Vendor ID’s - a unique code associated with a MDB User making them identifiable as a registered and approved MDB Vendor, allowing them to dispatch items within the MDB process.

• (2) Courier ID’s - a unique code associated with a MDB User making them identifiable as a registered and approved MDB Courier. Only registered couriers will be able to make collections and deliveries from MDB products.

• (3) Recipient ID’s - a unique code associated with a MDB User making them identifiable as a registered MDB Recipient. For parties that are receiving deliveries but do not have a MDB product enabled and registered at their property or premises (Non-MDB Recipient), a simple Yes/No, or True/False formula will identify such a recipient.

7.2. MDB Encrypted Code Generation and Structure Templates

The ID’s outlined above will contribute to the encrypted coding required to gain secure access to a MDB product. The content within this section provide examples of the process for generating and structuring MDB encrypted codes for MDB relationships.

7.2.1. Example MDB ID Database

Figure 13 is an example of a MDB database that stores MDB User and MDB Courier ID codes:

7.2.2. Example MDB Coding Structure

The Figure 14 provides an example template of how the encrypted coding can be structured.

7.3. MDB Relationship Coding Examples

This section provides examples on how the MDB encrypted coding structure can be generated for each potential MDB relationship within a MDB process making each encrypted code unique. For more information on MDB relationships see document entitled MDB Delivery: Relationships and Process Mapping. Figure 9 shows a high- level overview of the possible MDB relationships and their interfacing parties. 7.3.1. MDB Relationship A

7.3.1.1. Example of Encrypted Coding Database (A)

The selection of data highlighted in green, in Figure 15, demonstrates the following:

1. A M DB Vendor and Sender (Mart- Wall) is dispatching item/s;

2. A MDB Courier (UDS) will both collect and deliver said item/s;

3. A MDB Recipient (Damazon) will receive said items via their MDB product.

7.3.1.2. Encrypted Coding Structure Example (A)

Figure 16 demonstrates the generation of the encrypted code based on the MDB database information for a MDB Relationship A.

7.3.2. MDB Relationship B

7.3.2.1. Example of Encrypted Coding Database (B)

The selection of data highlighted in green, in Figure 17, demonstrates the following:

1. A MDB Vendor Only (John Smith) is dispatching item/s;

2. A MDB Courier (UDS) will deliver said item/s;

3. A MDB Recipient (Kostkow) will receive said items via their MDB product.

7.3.2.2. Encrypted Coding Structure Example (B)

Figure 18 demonstrates the generation of the encrypted code based on the MDB database information for a MDB Relationship B.

7.3.3. MDB Relationship C

7.3.3.1. Example of Encrypted Coding Database (C)

The selection of data highlighted in green, in Figure 19 demonstrates the following:

1. A M DB Vendor and Sender (Damazon) is dispatching item/s;

2. A MDB Courier (DPL) can both collect and deliver said item/s;

3. A Non MDB Recipient (unknown) will receive said items at their postal

address via the Traditional Delivery Process. 7.3.3.2. Encrypted Coding Structure Example (C) Figure 9 (below) demonstrates the generation of the encrypted code based on the MDB database information for a MDB, Relationship C.

7.4. Transmitting of MDB Delivery Encrypted Code

All MDB Users are required to have an account with MDB to enable them to carry out their function within the MDB delivery process. Couriers accessing a MDB product will require access to their account when collecting or making a delivery to/from a MDB product. The account will retain and transmit the code when presented to the MDB locking system interface, correct codes will then allow unlocking of the MDB locking system for the courier to make collections and/or deliveries. Transmittal of the code to the locking system interface is done via Near Field Communication technology (NFC).

Patent Drawings:

Contents

Figure 1. 2

Figure 2: MDB Delivery Domestic Product . 2

Figure 3: MDB Delivery Multi Domestic Product . 3

Figure 4: MDB Delivery Commercial Product . 3

Figure 5: Lock System Interface . 3

Figure 6: Power Supply . 4

Figure 7: MDB Delivery Process Integration . 4

Figure 8: MDB Interface Relationship Matrix . 5

Figure 9: MDB Relationship Flow Chart . 5

Figure 10: MDB Delivery: timeline overview . 6

Figure 11: Traditional Delivery Process Dispatch Method (National Example) . 6

Figure 12: MDB Delivery Dispatch Method (National Example) . 7

Figure 13: MDB Database example information . 7

Figure 14: MDB Delivery encrypted coding structure template example . 8

Figure 15: Relationship A example of selected MDB database information . 8

Figure 16: Relationship A encrypted coding structure example . 9

Figure 17: Relationship B example of selected MDB database information . 9

Figure 18: Relationship B encrypted coding structure example . 10

Figure 19: Relationship C example of selected MDB database information . 10

Figure 20: Relationship C encrypted coding structure example . 11