METHODS FOR COORDINATING THE DELIVERY OF PARCELS BY TRAVELERS

Methods for coordinating the delivery of parcels by travelers, which may include providing shipment data servers storing traveler records associated with potential travelers, receiving from senders traveler queries including desired destination entries associated with locations to which senders desires to send parcels, selecting traveler records including arrival location data consistent with the desired destination data, and providing to the sender contact data associated with suitable travelers. Some examples may include providing shipment data servers storing parcel records associated with potential senders, receiving from potential travelers parcel queries including arrival location entries, selecting parcel records including desired destination data consistent with the arrival location data, and providing to potential travelers contact data associated with suitable parcels. Some examples may include receiving parcels from senders, receiving desired destination locations from senders, receiving payment from senders, providing parcels to travelers, and providing to travelers at least portions of the payment.

DETAILED DESCRIPTION

In some examples, disclosed methods may connect people who are traveling or scheduled to travel with people who need to send a parcel, such as a document or a package. In some examples, the disclosed methods may facilitate those who urgently need to send a package, which may be impossible or too expensive to do with traditional courier services, such as FedEx®, UPS®, and national postal services. In particular, the disclosed methods may be included as part of a courier connecting service provided by a courier connecting service provider that coordinates transportation between those wanting to send parcels, referred to herein as senders, and those intending to travel, referred to herein as travelers.

In various examples, courier connecting service providers may be any party or service performs features of courier connecting services or other related methods. In some examples, courier connecting services may be independent companies or parties organized specifically to perform disclosed courier connecting services. In some examples, courier connecting services providers may be entities with interests in related markets, including traditional courier services such as FedEx® and UPS®, or other entities with interests that extend beyond providing courier connecting services.

In various examples, travelers may include couriers, frequent fliers, cabin crew members on common carriers, business travelers, or other persons intending to travel in the present or future.

In some examples, courier connecting service providers may establish booths or offices at airports or other transportation hubs. Courier connecting service providers having a presence at transportation hubs allow them to encourage travelers to be couriers and directly compete with traditional courier outposts at those hubs. At these booths or offices, the courier connecting service provider may provide incentives to travelers to transport documents while helping senders find travelers to deliver parcels.

Various disclosed examples may be implemented using electronic circuitry configured to perform one or more functions. For example, with some embodiments of the invention, the disclosed examples may be implemented using one or more application-specific integrated circuits (ASICs). More typically, however, components of various examples of the invention will be implemented using a programmable computing device executing firmware or software instructions, or by some combination of purpose-specific electronic circuitry and firmware or software instructions executing on a programmable computing device.

Accordingly,FIG. 1shows one illustrative example of a computer101that can be used to implement various embodiments of the invention. Computer101may be incorporated within a variety of consumer electronic devices, such as personal media players, cellular phones, smart phones, personal data assistants, global positioning system devices, and the like.

As seen in this figure, computer101has a computing unit103. Computing unit103typically includes a processing unit105and a system memory107. Processing unit105may be any type of processing device for executing software instructions, but will conventionally be a microprocessor device. System memory107may include both a read-only memory (ROM)109and a random access memory (RAM)111. As will be appreciated by those of ordinary skill in the art, both read-only memory (ROM)109and random access memory (RAM)111may store software instructions to be executed by processing unit105.

Processing unit105and system memory107are connected, either directly or indirectly, through a bus113or alternate communication structure to one or more peripheral devices. For example, processing unit105or system memory107may be directly or indirectly connected to additional memory storage, such as a hard disk drive117, a removable optical disk drive119, a removable magnetic disk drive125, and a flash memory card127. Processing unit105and system memory107also may be directly or indirectly connected to one or more input devices121and one or more output devices123. Input devices121may include, for example, a keyboard, touch screen, a remote control pad, a pointing device (such as a mouse, touchpad, stylus, trackball, or joystick), a scanner, a camera or a microphone. Output devices123may include, for example, a monitor display, an integrated display, television, printer, stereo, or speakers.

Still further, computing unit103will be directly or indirectly connected to one or more network interfaces115for communicating with a network. This type of network interface115, also sometimes referred to as a network adapter or network interface card (NIC), translates data and control signals from computing unit103into network messages according to one or more communication protocols, such as the Transmission Control Protocol (TCP), the Internet Protocol (IP), and the User Datagram Protocol (UDP). These protocols are well known in the art, and thus will not be discussed here in more detail. An interface115may employ any suitable connection agent for connecting to a network, including, for example, a wireless transceiver, a power line adapter, a modem, or an Ethernet connection.

It should be appreciated that, in addition to the input, output and storage peripheral devices specifically listed above, the computing device may be connected to a variety of other peripheral devices, including some that may perform input, output and storage functions, or some combination thereof. For example, the computer101may be connected to a digital music player, such as an IPOD® brand digital music player or iOS or Android based smartphone. As known in the art, this type of digital music player can serve as both an output device for a computer (e.g., outputting music from a sound file or pictures from an image file) and a storage device.

In addition to a digital music player, computer101may be connected to or otherwise include one or more other peripheral devices, such as a telephone. The telephone may be, for example, a wireless “smart phone,” such as those featuring the Android or iOS operating systems. As known in the art, this type of telephone communicates through a wireless network using radio frequency transmissions. In addition to simple communication functionality, a “smart phone” may also provide a user with one or more data management functions, such as sending, receiving and viewing electronic messages (e.g., electronic mail messages, SMS text messages, etc.), recording or playing back sound files, recording or playing back image files (e.g., still picture or moving video image files), viewing and editing files with text (e.g., Microsoft Word or Excel files, or Adobe Acrobat files), etc. Because of the data management capability of this type of telephone, a user may connect the telephone with computer101so that their data maintained may be synchronized.

Of course, still other peripheral devices may be included with or otherwise connected to a computer101of the type illustrated inFIG. 1, as is well known in the art. In some cases, a peripheral device may be permanently or semi-permanently connected to computing unit103. For example, with many computers, computing unit103, hard disk drive117, removable optical disk drive119and a display are semi-permanently encased in a single housing.

Still other peripheral devices may be removably connected to computer101, however. Computer101may include, for example, one or more communication ports through which a peripheral device can be connected to computing unit103(either directly or indirectly through bus113). These communication ports may thus include a parallel bus port or a serial bus port, such as a serial bus port using the Universal Serial Bus (USB) standard or the IEEE 1394 High Speed Serial Bus standard (e.g., a Firewire port). Alternately or additionally, computer101may include a wireless data “port,” such as a Bluetooth® interface, a Wi-Fi interface, an infrared data port, or the like.

It should be appreciated that a computing device employed according various examples of the invention may include more components than computer101illustrated inFIG. 1, fewer components than computer101, or a different combination of components than computer101. Some implementations of the invention, for example, may employ one or more computing devices that are intended to have a very specific functionality, such as a digital music player or server computer. These computing devices may thus omit unnecessary peripherals, such as the network interface115, removable optical disk drive119, printers, scanners, external hard drives, etc. Some implementations of the invention may alternately or additionally employ computing devices that are intended to be capable of a wide variety of functions, such as a desktop or laptop personal computer. These computing devices may have any combination of peripheral devices or additional components as desired.

In many examples, computing devices may define mobile electronic devices, such as smartphones, tablet computers, or portable music players, often operating the iOS, Symbian, Windows-based (including Windows Mobile and Windows 8), or Android operating systems.

With reference toFIG. 2, an exemplary mobile device, mobile device200, may include a processor unit203(e.g., CPU) configured to execute instructions and to carry out operations associated with the mobile device. For example, using instructions retrieved for example from memory, the controller may control the reception and manipulation of input and output data between components of the mobile device. The controller can be implemented on a single chip, multiple chips or multiple electrical components. For example, various architectures can be used for the controller, including dedicated or embedded processor, single purpose processor, controller, ASIC, etc. By way of example, the controller may include microprocessors, DSP, A/D converters, D/A converters, compression, decompression, etc.

In most cases, the controller together with an operating system operates to execute computer code and produce and use data. The operating system may correspond to well known operating systems such iOS, Symbian, Windows-based (including Windows Mobile and Windows 8), or Android operating systems, or alternatively to special purpose operating system, such as those used for limited purpose appliance-type devices. The operating system, other computer code and data may reside within a system memory207that is operatively coupled to the controller. System memory207generally provides a place to store computer code and data that are used by the mobile device. By way of example, system memory207may include read-only memory (ROM)209, random-access memory (RAM)211. Further, system memory207may retrieve data from storage units294, which may include a hard disk drive, flash memory, etc. In conjunction with system memory207, storage units294may include a removable storage device such as an optical disc player that receives and plays DVDs, or card slots for receiving mediums such as memory cards (or memory sticks).

Mobile device200also includes input devices221that are operatively coupled to processor unit203. Input devices221are configured to transfer data from the outside world into mobile device200. As shown, input devices221may correspond to both data entry mechanisms and data capture mechanisms. In particular, input devices221may include touch sensing devices232such as touch screens, touch pads and touch sensing surfaces, mechanical actuators234such as button or wheels or hold switches, motion sensing devices236such as accelerometers, location detecting devices238such as global positioning satellite receivers, WiFi based location detection functionality, or cellular radio based location detection functionality, force sensing devices such as force sensitive displays and housings, image sensors, and microphones. Input devices221may also include a clickable display actuator.

Mobile device200also includes various output devices223that are operatively coupled to processor unit203. Output devices233are configured to transfer data from mobile device200to the outside world. Output devices233may include a display unit292such as an LCD, speakers or jacks, audio/tactile feedback devices, light indicators, and the like.

Mobile device200also includes various communication devices246that are operatively coupled to the controller. Communication devices246may, for example, include both an I/O port connection247that may be wired or wirelessly connected to selected I/O ports such as IR, USB, or Firewire ports, a global positioning satellite receiver248, and a radio receiver250which may be configured to communicate over wireless phone and data connections. Communication devices246may also include a network interface252configured to communicate with a computer network through various means which may include wireless connectivity to a local wireless network, a wireless data connection to a cellular data network, a wired connection to a local or wide area computer network, or other suitable means for transmitting data over a computer network.

Mobile device200also includes a battery254and possibly a charging system. Battery254may be charged through a transformer and power cord or through a host device or through a docking station. In the cases of the docking station, the charging may be transmitted through electrical ports or possibly through an inductance charging means that does not require a physical electrical connection to be made.

The various aspects, features, embodiments or implementations of the invention described above can be used alone or in various combinations. The methods of this invention can be implemented by software, hardware or a combination of hardware and software. The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can thereafter be read by a computer system, including both transfer and non-transfer devices as defined above. Examples of the computer readable medium include read-only memory, random access memory, CD-ROMs, flash memory cards, DVDs, magnetic tape, optical data storage devices, and carrier waves. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

With reference toFIG. 3, some examples of the disclosed methods may include shipment data stored on a shipment data server.FIG. 3illustrates one example organization of shipment data, shipment dataset300that may be used in some example methods for coordinating the delivery of parcels by travelers. AsFIG. 3shows, shipment dataset300includes one or more parcel records310, one or more sender account records335, one or more traveler records355, and one or more traveler account records380.

In some examples, shipment dataset300may be hosted by a courier connecting service provider on one or more network-connected computing devices, often at a network location accessible to senders and travelers. Senders and travelers are often able to interface with the hosted shipment data on client computers by accessing this network location with a computing device, such as a client computer operating a web browser.

AsFIG. 3shows, parcel records310store data associated with parcels that senders have requested to be sent using the courier connecting service. Each parcel record310includes a desired departure location entry312, a desired departure time entry314, a desired destination entry316, a desired arrival time entry318, a parcel information entry320, a sender contact information entry322, a recipient contact information entry324, and a payment entry328.

Senders may be, for example, a private individual seeking lower cost or more urgent delivery services compared to commercial courier services (such as FedEx® or UPS®). In some examples, the sender may be businesses or employees thereof.

In some examples, senders may be traditional courier services, such as FedEx® or UPS®. The disclosed methods may allow senders to send parcels with more urgent delivery than traditional courier services' own delivery networks enable. In some examples, a traditional courier service may act as one or both of the sender and the courier connecting service provider. For example, traditional courier services may provide courier connecting services as an “urgent delivery” option.

Parcels may include any type of cargo transportable on commercial transportation carriers, particularly airlines. In some examples, parcels may define packages, documents, or other transportable items. Documents, in some examples, may be limited in size to fit in a substantially flat envelope. By distinguishing between packages and documents, travelers may find easy opportunities to transport documents when they do not have much excess storage capacity in their luggage, briefcases, or other personal items with which they are travelling.

Each desired departure location entry312includes desired departure location data defining a location from which the sender desires to send the associated parcel.

In some examples, the desired departure location may be the current or future location or the residence of the sender. In other examples, however, the desired departure location may be other locations. For example, senders, particularly businesses, may request that a remote agent or employee send a document on their behalf.

In various examples, locations may be defined, for example, as cities, states, countries, airports, mailing addresses, physical locations (such as those acquired using a location sensing device of a mobile electronic device), other commonly used geographic designations, or combinations thereof. In various examples, records may be queried or grouped based on locations of various breadths, such as those given above, to allow users to find senders or travelers within an acceptable range of locations.

AsFIG. 3shows, each desired departure time entry314includes desired departure location data defining the time at which the sender desires to send the associated parcel from the desired departure location. In some examples, the desired departure time may denote the soonest time that the sender is available to provide the parcel to a traveler.

Each desired destination entry316includes desired destination data associated with the location that the sender desires to send the associated parcel. In some examples, the desired destination simply defines a remote location. In some examples, however, the desired destination may be a courier connecting service location at a distant location, which may hold parcels until they are picked up by the recipient.

AsFIG. 3shows, each desired arrival time entry318defines the time in which the sender desires to arrive at the desired destination. In some examples, the desired arrival time may be the key factor in determining suitable travelers to transport a parcel. Setting a desired arrival time and desired destination location can, for example, set a deadline that limits suitable travelers to those arriving prior to the deadline.

Each parcel information entry320includes parcel data including information about the associated parcel. Parcel data may, for example, include physical characteristic data denoting the weight and geometric dimensions of the parcel.

Parcel data may, additionally or alternatively, include content data including information about the contents of the parcel. For example, the content data may include a description of the contents, whether the parcel is a document or a package, or other identifying criteria as tagging the contents “fragile” or “sensitive.” For parcels defining documents, the content data may additionally include the contained number of pages.

Parcel data may, additionally or alternatively, include parcel transit status data denoting the current transit status of the parcel. Current statuses may include status designations, such as “in transit,” “possessed by traveler,” “delivered,” etc. In some examples, senders may need to be logged in to access the parcel transit data associated with their parcels.

The parcel status transit data may additionally or alternatively include the estimated current location of the parcel. The estimated current location may be acquired by a location sensing device on a mobile electronic device possessed by a traveler or estimated based on published schedule data, such as published air traffic schedules.

AsFIG. 3shows, each sender contact information entry322includes sender contact data including the sender's contact information at which the traveler may contact the sender. In some examples, this information is provided to travelers upon agreeing to transport the associated sender's parcel and allows the two parties to further plan the transport.

For the purposes of this disclosure, contact information may include any address that may be used to contact or communicate with the associated party. In some examples, the contact information includes an electronic address to which a traveler may direct electronic communications to contact the sender, such as a phone number or an address on a digital protocol, such as e-mail, a social networking address (including, for example, Twitter® or Facebook® usernames). In additional or alternative examples, contact information includes physical addresses, such as home or business mailing addresses.

In some examples, the courier connecting service may include an electronic messaging service and allows its senders and travelers to communicate with one another. In some examples, senders and travelers may be addressed by their usernames on the associated courier connecting service. In such examples, contact information may of the username data used to address the user on the messaging service.

AsFIG. 3illustrates, recipient contact information entry324includes recipient contact data. Recipient contact data includes contact information or instructions directing travelers to a recipient receiving the parcel. In some examples, the contact information includes the address of a recipient or a meeting point, where the traveler is to meet the recipient. In some examples, the recipient contact data identifies a courier connecting service location where the traveler is to deposit the parcel, to be retrieved later.

AsFIG. 3shows, each payment entry328includes fee data defining the fee that the sender is willing to pay. In some examples, this is simply a monetary amount. In some examples, the courier connecting service automatically translates fees in foreign transactions according to current currency exchange rates, accepts exchange rate adjusted payments from senders, and/or distributes exchange rate adjusted payments to travelers.

Each payment entry328additionally or alternatively includes payment method data defining the sender's preferred method of payment. The payment method data may include credit card information, account information associated with an electronic wallet (such as PayPal®), bank account information, or information associated with other methods of payment commonly used online.

AsFIG. 3shows, shipment dataset300includes one or more sender account records335. AsFIG. 3illustrates, each sender account record335may be associated with one or more parcel records310and includes a sender username entry337. Sender account record335stores personal information about senders, allowing senders to easily manage their parcel records and simplify future requests to send parcels.

Each sender username entry337includes username data associated with the sender. Each sender account record335may include a password associated with the username, which may secure some or all of the features associated with the account, such as reviewing parcel records associated with the sender and reviewing the current locations of parcels.

Username data, in some examples, includes an alias, screen name, or other user-selected unique identifier associated with the sender's account. In some sender account examples, username data includes a computer-generated unique identifier, such as a database key.

AsFIG. 3shows, each parcel record310includes one or more traveler records355. Each traveler record355includes a departure location entry357, a departure time entry359, a arrival location entry361, a arrival time entry363, a capacity entry365, an itinerary entry367, and a traveler contact information entry369.

Each traveler record355is associated with a traveler who intends to travel from a departure location to an arrival location. In some examples, travelers may be passengers of airlines or other commercial transit services. In some examples, however, travelers may be intending to travel by car, foot, or other individual form of transport.

In some examples, travelers are agents hired by a traditional courier services to send parcels more urgently or cheaper than their transportation network currently allows. In some examples, traditional couriers serve as travelers, using courier connecting services to fill excess capacities on already-scheduled deliveries.

Though many disclosed examples discuss airline passengers, travelers in some examples may simply intend to travel within their city or neighborhood. In more local centered examples, courier connecting services operate as an alternative to document runners or personally delivering parcels locally.

AsFIG. 3shows, each departure location entry357includes departure location data associated with a departure location from which the traveler intends to travel. In some examples, the departure location may define the location at which the traveler intends to begin his travel on an associated trip.

In other examples, however, the departure location may define an interim location at which the traveler intends to stop during his travel. By allowing travelers to specify interim locations, courier connecting services may allow multiple travelers to collectively transport a sender's parcel. Travelers working together and traveling on a commercial airline may, for example, meet at an interim location midway through the traveler's trip and exchange the parcel. In some examples, this interim location may be behind a security checkpoint and/or at a courier connecting service location in a transportation hub.

In some examples, travelers' departure location may be automatically generated and updated by cross-referencing itinerary data in itinerary entry367with published scheduling data, such as published air traffic schedules.

AsFIG. 3shows, each departure time entry359includes departure time data associated with the time at which the traveler is scheduled to depart from his departure location. Like departure location entry357, this time may be manually entered or automatically generated and updated according to itinerary data in itinerary entry367.

AsFIG. 3shows, each arrival location entry361includes arrival location data associated with the location at which the traveler intends to arrive Like departure location entry357, arrival location entry361may be manually entered or automatically generated and updated according to itinerary data in itinerary entry367. Further, arrival location entry361may similarly define the traveler's final destination or an interim location.

Each arrival time entry363includes arrival time data associated with the time at which the traveler is scheduled to arrive Like departure time entry359, arrival time data may be manually entered or automatically generated and updated according to itinerary data in itinerary entry367.

AsFIG. 3shows, each capacity entry365includes capacity data related to the associated traveler's capacity to carry parcels. In some examples, capacity data may include information that directly corresponds to any category of data stored in parcel information entry320. For example, capacity data may denote the physical characteristics, content types, and additional information about suitable parcels.

In some examples, some travelers may be willing to check additional luggage to supplement their excess capacity. In such cases, capacity entries may include surcharge data denoting surcharges that travelers will charge to compensate for any airline surcharge for checking additional luggage and the added inconvenience.

Itinerary entry367includes itinerary data associated with a traveler's scheduled itinerary with a travel provider. The itinerary data may include travel information, such as flight numbers and schedules. In some examples, the itinerary data may be cross-referenced with published schedules, such as public air traffic schedules, and used to obtain accurate, updated scheduling data associated with departure and arrival locations and times. In some examples, the updated data provides departure location entry357, departure time entry359, arrival location entry361, and arrival time entry363with accurate, up to date information.

Each traveler contact information entry369includes traveler contact data associated with the traveler's contact information, substantially similar to sender contact information entry322.

AsFIG. 3shows, shipment dataset300includes one or more traveler account records380. AsFIG. 3illustrates, each traveler account record380may be associated with one or more traveler records355and includes a traveler username entry382and a traveler rating entry384. Traveler account record380stores personal information about travelers, allowing travelers to easily their traveler records and simplify future requests to add traveler records by storing and reusing their personal data.

AsFIG. 3illustrates, each traveler account record380includes a traveler username entry382, substantially similar to the senders' username data stored in sender username entry337.

Each traveler rating entry384includes rating data associated with senders' opinions of the traveler's reliability as a courier. In some examples, this rating data is generated in response to sender feedback provided after the associated traveler delivers (or, at least, is scheduled to deliver) a parcel for the sender.

In some examples, the traveler rating entry uses a rating methodology, which includes senders' feedback. The feedback may include a traveler-reviewable rating and optional textual commentary. In some examples, the rating methodology may consist of a binary “positive” or “negative” rating. In some examples, the ratings and commentary are publicly viewable, allowing both travelers and potential senders to quickly view past senders' levels of satisfaction with selected travelers' services.

In some examples, a single user account operates as both a sender account and a traveler account under a single username. In such examples, the resulting user account record includes all of the elements associated with traveler accounts and sender accounts.

With reference toFIGS. 4-6, some features of the disclosed methods may be implemented through one or more user interfaces.FIGS. 4-6illustrate example user interfaces, a sender form410, a traveler form450, and a quick search form490, each stored on the shipment data server and sent to users' computing devices to be displayed within web browser windows. These user interfaces allow senders and travelers to review available offers and travelers intending to travel in the future. Further, these user interfaces allow senders and travelers to create new records associated with future trips or offers to transport parcels.

User interface data may, for example, be hosted at a network location accessible to senders and travelers to be sent to users' devices and displayed on a display unit of users' computing devices. For example, the user interface data may be displayed as a standalone website or as an app integrated within a social networking web application. In other examples, user interfaces may be transmitted to users as part of a downloadable mobile or desktop application.

FIG. 4illustrates sender form410, one example of a user interface through which potential senders may interface with shipment dataset300. AsFIG. 4shows, sender form410includes a traveler table442, a login interface411, a sender name input414, a desired departure location input416, a desired departure time input417, a desired destination location input418, a desired arrival time input420, a parcel type entry424, a parcel weight entry428, a parcel dimension entry432, a parcel additional tag entry434, a parcel page entry438, a recipient information entry439, and a submit button440. In some examples, sender form410allows senders to enter data associated with parcels that the senders desire to send to recipients. AsFIG. 4shows, sender form410allows potential senders to review a list of traveler records consistent with data entered into sender form410and select a suitable traveler for transporting the sender's parcel.

AsFIGS. 4 and 5illustrate, both sender form410and traveler form450may be displayed on a single, dynamically-updating page that adjusts in response to the users on user type entry412. For example, sender form410may be displayed when a user selects “SENDING A DOCUMENT/PACKAGE” and traveler form450may be displayed when a user selects “FLYING.”

With reference to theFIG. 4example, traveler table442is a dynamically updated list of travelers available to send parcels. AsFIG. 4shows and will be described in more depth below, traveler table442is updated to reflect the data entered in sender form410, and sender may easily select a suitable traveler to transport her parcel from the listed travelers.

With reference to theFIG. 4example, login interface411allows users to enter user authentication data to access their accounts. In some examples, logging in may allow access to restricted features. Further, logging in may retrieve and use the user's personal information to automatically enter data. For example, sender name input414is automatically filled in with a logged-in sender's publicly viewed name, Young W.

With reference to theFIG. 4example, sender name input414allows senders to enter a publicly viewable name to publicly identify themselves in parcel records. In some examples, this public viewable name is viewable to travelers browsing offers for parcel transport on courier connecting services, as seen in offer table482inFIG. 5.

In some examples, senders may enter an alias or “private” into the sender form if the sender would like to remain anonymous until a traveler has agreed to transport his parcel. In such examples, parcel records are still linked to the sender's account, so travelers can still contact the sender upon agreeing to transport the parcel.FIG. 5illustrates an example of an offer table482including a parcel record where “PRIVATE” has been entered in this manner.

With reference to theFIG. 4example, desired departure location input416allows users to enter a departure location from which they desire to send a parcel. When using sender form410to create a new parcel record, this data may be stored in desired departure location entry312.

Further, asFIG. 4illustrates, traveler table442is updated when a user enters data in desired departure location input416. For example, “NEW YORK” is selected, which limits the results displayed in traveler table442to references to traveler records for travelers traveling from New York, US.

AsFIG. 4shows, desired departure location input416only allows users to select departure location based on a city to maintain an uncluttered interface. Additional or alternatively, some sender form examples allow senders to search based on various levels of geographic breadth, such as by country, airport, address, or neighborhood. In particular, searching by airport may be particularly useful for reviewing travelers travelling on commercial airlines.

With reference to theFIG. 4example, desired departure time input417allows users to enter a time at which they desire the parcel to be sent from the departure location. When using sender form410to create a new parcel record, this data may be stored in desired departure time entry314. In some examples, desired departure time input417defaults to the current date and time to limit displayed travelers to those leaving in the future.

AsFIG. 4shows, traveler table442is updated when a user enters data in desired departure time input417. AsFIG. 4illustrates, January 7 at 10:00 AM, is selected, which limits the results displayed in traveler table442to references to traveler records for travelers leaving after that date.

With reference to theFIG. 4example, desired destination location input418allows a sender to enter the destination to which a sender desires to send a parcel. When using sender form410to create a new parcel record, this data may be stored in desired destination entry316. Desired destination location input418is substantially similar to desired departure location input416and similarly updates traveler table442. For example, LONDON is selected inFIG. 4, which limits the results displayed in traveler table442to references to traveler records for travelers traveling to London, UK.

With reference to theFIG. 4example, desired arrival time input420allows a sender to enter the time at which he desires a parcel to arrive at its destination. When using sender form410to create a new parcel record, this data may be stored in desired arrival time entry318. Desired arrival time input420operates substantially similar to desired departure time input417, but limits results shown in traveler table442to those arriving prior to the desired arrival time. For example (asFIG. 4shows), selecting January 9 at 5:30 AM limits the results displayed in traveler table442to traveler records for travelers arriving in London, UK, prior to that time.

With reference to theFIG. 4example, parcel type entry424allows senders to identify parcels as packages or documents. When using sender form410to create a new parcel record, this data may be stored in parcel information entry320. AsFIG. 4illustrates, DOCUMENT is selected, which does not limit the results displayed in traveler table442. Because packages are larger than documents, it is assumed that any traveler with adequate space to carry a package has adequate space to carry documents. However, if PACKAGE had been selected, the results would eliminate any travelers who indicated that they only have adequate space to carry documents, such as by selecting DOCUMENTS ONLY in traveler form450when creating a traveler record.

With reference to theFIG. 4example, parcel weight entry428allows senders to enter the weight of the parcel. When using sender form410to create a new parcel record, this data may be stored in parcel information entry320. Though no data has been entered in parcel weight entry428, the results displayed would be limited to results with capacities greater than the weight entered in parcel weight entry428.

With reference to theFIG. 4example, parcel dimension entry432allows senders to enter the geometric dimensions of the entered parcel, including entries for length, width, and height. When using sender form410to create a new parcel record, this data may be stored in parcel information entry320. Though no data has been entered in parcel dimension entry432, the results displayed would be limited to results with capacities that define length, width, and height dimensions that are each greater than the associated entry in parcel dimension entry432.

With reference to theFIG. 4example, parcel additional tag entry434allows senders to enter additional information that may need to be conveyed to travelers, such as whether the parcel is “fragile” or “sensitive.” When using sender form410to create a new parcel record, this data may be stored in parcel information entry320. The additional information may be, in some examples, communicated to the traveler prior to transporting the sender's parcel.

With reference to theFIG. 4example, parcel page entry438allows senders to enter the page length of a document. When using sender form410to create a new parcel record, this data may be stored in parcel information entry320. Some examples may allow travelers to enter max numbers of pages for carried documents. In such examples, the results displayed in traveler table442may be limited to results with capacity data denoting a max number of pages greater than the number entered in parcel page entry438.

With reference to theFIG. 4example, recipient information entry439includes recipient contact data that informs the traveler how to contact the recipient. When using sender form410to create a new parcel record, this data may be stored in recipient contact information entry324. In some examples, the recipient contact data may include the recipient's contact information, but this is not required. For example, some recipient contact data may instead provide travelers with a meeting point.

If no traveler is selected in traveler table442, submit button440may submit the data entered in sender form410to create a new parcel record associated with the sender's parcel. If the sender has a sender account, the created parcel record may be linked with the sender's sender account record.

If a traveler is selected in traveler table442, the sender may use submit button440to select a traveler to transport his parcel. In such examples, the courier connecting service may provide the sender with contact information associated with the selected traveler.

FIG. 5illustrates traveler form450, which represents one example of a user interface that travelers may use to interface with shipment dataset300. AsFIG. 5shows, traveler form450includes an offer table482, a traveler name input454, a departure location input456, a departure time input457, a destination location input458, a arrival time input460, a capacity weight entry468, a capacity dimension entry472, a documents only entry474, and a submit button480.

Referring to theFIG. 5example, offer table482is substantially similar to traveler table442and dynamically updates to list offers from senders that are consistent with the data entered in traveler form450.

In theFIG. 5example, traveler name input454allows travelers to enter in a publicly viewable name to identify themselves in traveler records. In some examples, travelers may not be allowed to use aliases or anonymous names as senders may to ensure that senders can verify travelers' identities before entrusting them with their parcels. Similar to sender name input414, traveler name input454be automatically entered when a user is logged in.

In some examples, travelers are not allowed to use aliases or anonymous names like “Private,” as senders will want to know the identity of travelers before entrusting them with their parcels. Similar to sender name input414, traveler name input454automatically be entered when a user is logged in.

In theFIG. 5example, departure location input456is substantially similar to desired departure location input416. Departure location input456allows travelers to enter the location from which the traveler intends to travel on an associated trip. When using sender form410to create a new traveler record, this data may be stored in departure location entry357. When data is entered in departure location input456, offer table482is updated to reflect its contents. For example,FIG. 5illustrates a case where “NEW YORK” is selected, and the results displayed in offer table482are limited to offers with a desired departure location of New York, US.

In all traveler schedule-related fields (such as departure/arrival locations and times), the data entered in each input may be automatically generated or updated by receiving an traveler's itinerary for a chosen trip and cross-referencing the received itinerary information entered by the traveler with published schedules, such as air traffic schedules. The received itinerary information may additionally or alternatively be stored in itinerary entry367.

In theFIG. 5example, departure time input457is substantially similar to desired departure location input416. Departure time input457allows travelers to enter the time at which the traveler intends to depart on an associated trip. When using sender form410to create a new traveler record, this data may be stored in departure time entry359.

When data is entered in departure time input457, offer table482is updated to reflect its contents.FIG. 5illustrates an example with Jan. 7, 2013, at 5:00 PM, entered in departure time input457, which limits the results displayed in offer table482to references to offers with desired departure data denoting a time before that date.

In theFIG. 5example, destination location input458is substantially similar to desired destination location input418. Destination location input458allows travelers to enter the location to which they intend to travel on an associated trip. When using sender form410to create a new traveler record, this data may be stored in departure time entry359.

When data is entered in destination location input458, offer table482is updated to reflect its contents. AsFIG. 5illustrates, “NEW YORK” is selected, which limits the results displayed in offer table482to references to parcel records with desired destination location data associated with London, UK.

In theFIG. 5example, arrival time input460is substantially similar to desired arrival time input420. Arrival time input460allows travelers to enter the time at which the traveler intends to arrive at his destination. When using sender form410to create a new traveler record, this data may be stored in arrival time entry363.

When data is entered in arrival time input460, offer table482is updated to reflect its contents.FIG. 5illustrates an example where Jan. 8, 2013, at 8:00 AM, is entered, which limits the results displayed in offer table482to references to parcel records with a desired arrival time after that date.

AsFIG. 5shows, traveler form450includes capacity dimension entry472and capacity weight entry468, which allows travelers to specify the maximum geometric dimensions and weight of parcel that they would be willing to transport. When using sender form410to create a new traveler record, this data may be stored in capacity entry365. In some examples, the figures entered (or those stored in capacity entry365) may be automatically adjusted in response to the traveler accepting offers for the associated trip.

When data is entered in capacity dimension entry472, offer table482is updated to reflect its contents.FIG. 5illustrates an example wherein offer table482displays only parcel records with parcel data denoting geometric dimensions and weight lesser than the entered dimensions and weight.

In theFIG. 5example, a traveler may use documents only entry474to indicates that he has capacity to carry only documents and not packages. In some examples, the traveler is additionally able to specify the amount of pages he has capacity to transport when the traveler indicates that he is willing to transport documents. When selected, offer table482is adjusted to only include parcel records associated with documents.

In theFIG. 5example, submit button480. If no offer is selected in offer table482, a user may select submit button480to submit the data entered in traveler form450and create a new traveler record associated with the entered data. If the sender has a traveler account, the created parcel record may be linked with the traveler's account.

If an offer is selected in offer table482, the sender may use submit button480to agree to transport a sender's parcel for the offered price. In such examples, the courier connecting service may provide the traveler or the sender with contact information associated with the sender associated with a selected offer.

FIG. 6illustrates a third example of a user interface, quick search form490. AsFIG. 6illustrates, quick search form490's interactive elements consist of a login entry493, a user type entry491, a departure location entry492, an arrival location entry494, a quick time entry496, a submit button497, and a quick dynamically-updating table499.

Each of the elements of quick search form490act substantially similar to the corresponding elements in either sender form410or traveler form450. In particular, the behavior of each element may adjust to correlate with the user's selection in user type entry491. For example, departure location entry492, arrival location entry494, quick time entry496, submit button497, and quick dynamically-updating table499operate like the corresponding elements of sender form410when user selects “SENDING A DOCUMENT/PACKAGE” in user type entry491. Similarly, departure location entry492, arrival location entry494, quick time entry496, submit button497, and quick dynamically-updating table499operate like the corresponding elements of traveler form450when user selects “FLYING” in user type entry491.

Quick search form490provides a simple, intuitive, mobile friendly interface that allows users to quickly find available offers or travelers. Quick search form490's simple interface may, for example, make it easier for travelers to find offers near their departure time, perhaps even when at the airport.

Login entry493may further accelerate this process by, for example, instructing the courier connecting service to retrieve stored account data and auto-enter some of the required information. In particular, this may be useful for billing information.

With reference toFIG. 7, an example of a method for coordinating the delivery of parcels by travelers, method500, will now be described. By performing some or all of method500, a courier connecting service provider may facilitate senders in sending parcels to a destination by the senders a means for contacting travelers who has pre-existing intentions to travel to the destination.

AsFIG. 7illustrates, a shipment data server storing shipment data is provided at step505. The shipment data server may be hosted on one or more network connected computing devices. The shipment data server may, for example, store shipment data, such as shipment dataset300, and user interface data, such as the data configured to generate sender form410, traveler form450, and quick search form490.

In some examples, users connect to the shipment data server to interact with the shipment data using client computers displaying user interfaces, such as web pages, associated with the user interface data. Connected users may additionally or alternatively use downloadable mobile applications to connect and interface with the shipment data server.

AsFIG. 7shows, a traveler record is received at step510. In some examples, one or more traveler records may be received at step510. In some examples, the received traveler data may be received in response to user input entered on traveler form450. If the user is logged in, the traveler record may additionally be associated with the traveler's account.

AsFIG. 7illustrates, the received traveler record is stored in the shipment data at step515. Received traveler records are stored in an organization that reflects FIG.3's traveler dataset, including a plurality of traveler records. Each traveler record may be, but is not required to be, associated with a traveler account. In some examples, traveler accounts may be associated with one or more traveler records, but traveler records may only be associated with one traveler account. In some examples, travelers may associate multiple traveler records with regard to a single trip, such as when travelers accept multiple offers for delivery on that trip.

Further, multiple traveler records may be associated with a single parcel, allowing parcels to be exchanged at interim points during travelers' trips. These interim exchanges may include, for example, providing the parcel to a courier connecting service provider at the interim location, where it is held to be provided to a second traveler associated with the parcel.

AsFIG. 7shows, traveler query is received from a sender at step520. The traveler query may be entered into sender form410, as described above. Because traveler table442updates dynamically in response to data entered in sender form410, traveler queries may be persistently received as sender form410enters data into sender form410.

AsFIG. 7illustrates, queried traveler records consistent with the traveler query are selected at step525. In dynamically updating traveler table442in response to the traveler queries persistently received through sender form410, the shipment data server is persistently selecting queried traveler records consistent with the traveler query. AsFIG. 4shows, the records illustrated in traveler table442all include data that is consistent with the traveler query according to the strict criteria described above in the discussion of sender form410.

Records do not need to perfectly match each of filled entries on sender form410in the manner described above to be consistent with traveler queries. Rather, some examples may build in a reasonable margin of error on for each of the criteria limiting the queried traveler records. In other examples, sets of queried traveler records may fall outside the specific entered ranges but be close enough to define an acceptable difference. For example, a sender may request travelers with capacity for a 26 pound parcel and traveler table442may return, for example, travelers that denoted a 25 pound capacity. The values of reasonable margins of error may be by shipment data server administrators in some examples. In some examples, user interfaces may provide an entry that allows travelers or senders to expressly enter a reasonable margin of error value associated with one or more of traveler records' entries.

AsFIG. 7shows, one or more queried traveler records are displayed to the sender at step530. AsFIG. 4illustrates, the queried traveler records are dynamically updated in traveler table442, which is displayed to the sender on a display unit of a computing device operated by the sender.

AsFIG. 7illustrates, a traveler selection is received from the sender at step535.FIG. 4displays an example wherein the sender is able to select a traveler by selecting a queried traveler record in traveler table442and selecting submit button440.

AsFIG. 7shows, payment is received from the sender at step540. Payment may be received, for example, by charging a credit card associated with the sender's account, charging a credit card entered by the sender, receiving funds from a user's online wallet account (such as PayPal), or other methods commonly used to accept payment online. Payment may, in some examples, be received from the sender after selecting a traveler selection

In some examples, received funds may be held in escrow by the courier connecting service and withheld from the traveler until receiving confirmation that the parcel was satisfactorily delivered to the recipient. By withholding funds until receipt of the parcel is confirmed, courier connecting services may encourage travelers to perform satisfactory deliveries.

Payment may be, in some examples, non-monetary. For example, senders, or agents on their behalf, may provide payment in the form of flight upgrades, discounted flights, reward points or miles, or other forms of non-monetary payment, which may be conveyed to travelers upon satisfactory delivery.

The contact information associated with one of the queried traveler records is provided to the sender at step545. In some examples, providing the contact information may include providing the sender the contact information of a traveler selected in traveler table442. In some examples, the sender may use this contact information to initiate two-way communication with the traveler and allow the sender to coordinate the traveler's receipt and delivery of the parcel.

In some examples, providing the sender contact information may include or consist of automatically contacting a selected traveler, such as by sending an electronic communication to the selected traveler upon the sender's selection.

AsFIG. 7shows, an estimated parcel location is tracked while the parcel is in transit at step550. In some examples, tracking the estimated parcel location may include receiving from a traveler's mobile electronic device positional data acquired with a location sensing device of the mobile electronic device. In some examples, the location sensing device may define a GPS receiver or other common smartphone geolocating feature.

Additionally or alternatively, tracking the estimated parcel location may include electronically accessing and translating published schedule data associated with a common carrier with whom the traveler intended to travel. For example, the schedule data, such as published air traffic schedules, may be cross-referenced with a traveler record's itinerary data to determine the approximate location of the parcel when in transit. This may be particularly useful when mobile communication is unavailable, such as during air travel.

AsFIG. 7illustrates, the estimated parcel location is communicated to the sender at step555. In some examples, the user interface may have a tracking form associated with a parcel record configured to display the estimated location of the associated parcel. In some examples, senders may need to be logged in to view the tracking forms associated with their parcels in transit.

AsFIG. 7shows, confirmation that the parcel was delivered is received at step560. In some examples, this confirmation is sent to the courier connecting service by the recipient, such as by communicating an authentication code via a mobile electronic or other computing device. In other examples, this confirmation may be sent by a courier connecting service location at the destination location.

AsFIG. 7illustrates, payment is directed to the traveler at step565. Upon receiving proper notification that a parcel has been satisfactorily delivered, the courier connecting service directs the funds to the traveler in a traveler-directed manner. Often, payment is directed the traveler's bank account or to an electronic wallet (such as PayPal).

In some examples, the sender has no authority to prevent the funds from being transferred upon the delivery being accepted. In some examples, however, the sender may prevent payment from being completed upon discovering that the delivery was unsatisfactory.

With reference toFIG. 8, an example of a method for coordinating the delivery of parcels by travelers, method600, will now be described. Method600is similar, in many ways, to method500. Method600, however, focuses on using the courier connecting service from the traveler's perspective.

AsFIG. 8illustrates, a shipment data server storing shipment data is provided at step605. Step605is substantially similar to providing the shipment data server at step505.

AsFIG. 8shows, a parcel record is received from a sender at step610. The parcel record may be received from a user entering data on a user interface, such as sender form410. The created parcel record reflects the data entered in sender form410. If the user is logged in, the parcel record may additionally be associated with the sender's account.

AsFIG. 8illustrates, the parcel record is stored in the shipment data at step615. AsFIG. 3shows, parcel records are stored within a traveler dataset including a plurality of parcel records. Each parcel record may be, but is not required to be, associated with a sender account. In some examples, sender accounts may be associated with one or more parcel records, but parcel records may only be associated with one sender account.

AsFIG. 8shows, a parcel query is received from a traveler at step620. The parcel query may be entered in traveler form450, similar to the traveler query entered in sender form410in step520. Similarly, offer table482updates dynamically in response to input in traveler form450to illustrate a list of offers that are consistent with the values entered in traveler form450. As result, sender queries are received persistently as the traveler enters data into traveler form450

AsFIG. 8illustrates, queried parcel records consistent with the parcel query are selected at step625. Similar to traveler table442, offer table482is dynamically updated in response to the traveler queries persistently received through traveler form450and the shipment data server persistently selects and returns queried traveler records consistent with the traveler query.

Similar to method500, the values returned and displayed in traveler table442need not strictly follow the criteria discussed in association with traveler form450in all examples, and may in some examples account for a reasonable margin of error.

AsFIG. 8shows, one or more queried parcel records are displayed to the traveler at step630. AsFIG. 4illustrates, the queried parcel records are dynamically updated in offer table482, where they are displayed to the traveler.

AsFIG. 8illustrates, a parcel selection is received from the traveler at step635.FIG. 4displays, for example, a user interface allowing the traveler is able to select an offer by selecting a queried parcel record in offer table482and selecting submit button480.

AsFIG. 8shows, payment is received from the sender at step640. In some examples, the courier connecting service receives payment from the sender, to be held in escrow until delivery confirmation, similar to at step540. By accepting funds at the time that the sender submits a request for a parcel to be transported, the courier connecting service may ensure that funds are available to travelers when they agree to transport a parcel.

Sender contact data associated with one of the selected parcels is provided to the traveler at step645substantially similar to step545, but the traveler is provided with the sender's contact information. Thus, the traveler initiates communication in this instance, rather than the sender.

AsFIG. 8illustrates, confirmation that the parcel was delivered is received at step660, substantially similar to step560

AsFIG. 8shows, payment is directed to the traveler upon confirmation of delivery at step665, substantially similar to step565.

With reference toFIG. 9, an example of a method for coordinating the delivery of parcels by travelers, method700, will now be described. Method700is similar, in many ways, to method500and method600. Method700illustrates the use of courier connecting service locations at or near transportation hubs to further facilitate connecting senders with travelers. Method700additionally may illustrate that novel features of the disclosed invention may be used without computers and/or software.

AsFIG. 9illustrates, a courier connecting service location is hosted at or near a transportation hub at step705. The courier connecting service location may, for example, include a retail location, office, booth, etc., where employees of the courier connecting service provider may assist senders and travelers.

In some examples, courier connecting service locations are located at or near a transportation hub. In some examples, courier connecting service locations are located in airport lobbies or in retail locations located outside, but near, the airport. In particular, some courier connecting service locations may be located behind security checkpoints to facilitate interim exchanges.

In some examples, courier connecting service locations attempt to recruit travelers by, for example, offering incentives to nearby travelers to lure them to agree to transport parcels. In some examples, these incentives are additional to any fee that would be received for transporting a parcel.

In some examples, courier connecting service locations may possess parcels provided by senders that are ready to be provided to a suitable traveler. In such examples, courier connecting service locations serve as agents for the sender, finding last-minute, suitable travelers as they are in the airport for their departure.

In some examples, courier connecting service locations receive parcels on behalf of senders or recipients. Upon receipt, courier connecting service locations may hold the parcels until it is convenient for a recipient to collect the parcel. This may make scheduling easier on both the recipient and the traveler and relieve the traveler of the responsibility of finding the recipient.

In some examples, courier connecting service providers with courier connecting service locations provide courier connecting services that include host network accessible shipment data servers accessible through user interfaces, similar to shipment dataset300, sender form410, traveler form450, and quick search form490. In such examples, the courier connecting service provider may, at the courier connecting service location, collect and distribute parcels amongst senders and travelers who made previous arrangements through the shipment data server and associated interfaces.

Further, in some examples, courier connecting service locations may include courier connecting service terminals, such as network connected computing devices, which may be used by nearby parties to access shipment data servers and associated user interfaces. In particular, courier connecting services may include publicly accessible kiosks through which senders and travelers may access, view, and/or modify their associated accounts, parcel records, and/or traveler records. Additionally or alternatively, courier connecting service terminals may allow parties to access, display, and modify accounts and records on a courier connecting service hosted by a different courier connecting service provider.

AsFIG. 9shows, a desired destination location is received from a sender at step710. The desired destination location defines a location to which the sender desires to send a parcel. In some examples, this information may be received from a sender upon providing the courier connecting service location with the parcel.

AsFIG. 9shows, payment for delivering the parcel is received from the sender at step715. In some examples, courier connecting service locations may simply ask for a fee that the sender is willing to pay and receives cash or credit card payment from the sender. As with previously described examples, this amount may be held in escrow until the sender's parcel is finally delivered.

AsFIG. 9illustrates, the parcel is received from the sender at step720. In some examples, the parcel may be received by a courier connecting service location at a transportation hub, such as an airport. In other examples, the parcel may be received by a traveler located at or near a courier connecting service location. In some examples, the parcel may be held until a suitable traveler is found by the courier connecting service.

Around the time of receiving the parcel (or after receiving the parcel), the courier connecting service may also receive payment and a desired destination associated with the parcel.

AsFIG. 9shows, the parcel is provided to a traveler, who may have a pre-existing intention to travel to the desired destination location, at step725. In some examples, the parcel may be provided, at the transportation hub, at or near the courier connecting service location. In some examples, the sender may hand the parcel over directly to the traveler.

In some examples, the sender may have already selected a suitable traveler, and the courier connecting service holds the parcel until the suitable traveler arrives at the courier connecting service location. In other examples, the courier connecting service may select a suitable traveler on behalf of the sender.

AsFIG. 9illustrates, at least a portion of the payment is provided to the traveler for delivering the parcel upon receiving confirmation that the parcel was satisfactorily delivered at step730. In some examples, the traveler receives all of the payment. In other examples, however, the courier connecting service retains of portion of the payment as a service fee.

FIG. 10provides a diagram showing an example use case where features of the disclosed methods may be used. For example,FIG. 10illustrates a sender805, located in Los Angeles, who urgently needs to send a document to New York City, and a traveler810, also located in Los Angeles, who had intentions of flying to New York City on a commercial airline prior to ever meeting the sender.

In step A, the sender offers payment to the traveler to deliver the documents to a recipient815, who is located in New York City. In step B, the traveler agrees to deliver the documents, and subsequently receives the parcel from the sender. In step C, traveler travels to New York City, as he was already planning on doing, and delivers the documents to recipient815. At step D, recipient815confirms to sender805the parcel was delivered. At this point, sender805finalizes payment to traveler810. In this example, sender805may have been able to deliver his documents to New York City in a more timely fashion than traditional courier services may allow.

FIG. 11illustrates an additional flowchart illustrating one example method that incorporates some of the novel features of the disclosed methods.FIG. 11illustrates the interactions between a sender905, a traveler910, a recipient915, and a courier connecting service920. In a first step950, sender905offers payment to traveler910to deliver a parcel. In a second step955, traveler910accepts the offer. Upon the traveler accepting the offer, payment is transferred to courier connecting service920at step960, the payment to be held in escrow until receiving confirmation of delivery. Traveler910delivers the parcel to recipient915at step965. Recipient915confirms deliver to courier connecting service920at step970. Upon receiving confirmation of deliver, courier connecting service920directs at least a portion of the funds held in escrow to traveler910to pay for the delivery at step975.