Systems and methods for facilitating shipping of parcels for returning items

Information

  • Patent Grant
  • 10410165
  • Patent Number
    10,410,165
  • Date Filed
    Monday, November 16, 2015
    8 years ago
  • Date Issued
    Tuesday, September 10, 2019
    4 years ago
Abstract
An exemplary item return shipping system is configured to: receive a request to return an item to a retailer; provide the user with a unique identifier associated with the request; and receive an indication that the user has presented the parcel and the unique identifier at an access point. The system may then facilitate placement of a pre-printed machine-readable indicia (e.g., a barcode) on the parcel at the access point and associate it with the retailer information. The system then facilitates delivery of the parcel from the access point to a handling facility and facilitates placement of a shipping label (that includes the address of a returns processing facility that is determined using the retailer information) on the parcel at the handling facility. In various embodiments, the system then facilitates shipment of the parcel to the returns processing facility.
Description
BACKGROUND

Currently, there are few options for most customers to return items purchased from e-commerce stores. A customer may both obtain and fill out a traditional shipping label that is provided by a common carrier, the customer may use a suitable software program to print an appropriate shipping label on a computer printer, or the customer may utilize a preprinted shipping label provided by the e-commerce store. In any case, once the label is complete, the user typically affixes the label to the parcel and transfers the labeled parcel to the common carrier for shipment back to the e-commerce store by, for example, dropping the parcel off at a drop box or other pickup location associated with the common carrier. This process may be inconvenient for customers who, for example, may not have access to a computer printer, or for customers of e-commerce stores that do not provide preprinted return shipping labels. Accordingly, there is a need for providing shipping solutions that do not require customers to print a suitable label or to obtain pre-preprinted shipping labels in order to facilitate the return of an item to a retailer.


SUMMARY

A computer-implemented method of enabling a user to return an item to a retailer via an access point (e.g., an attended parcel pickup/delivery location), according to various embodiments, comprises: (1) receiving, by a processor, from a first entity computing device associated with a user, a request to ship a parcel containing the item, the request including shipping information associated with a retailer from which the item was purchased; (2) at least partially in response to receiving the request, generating, by a processor, a first unique identifier and associating, by a processor, the shipping information with the first unique identifier; (3) receiving, by a processor, confirmation of receipt of the parcel and presentation of the first unique identifier at an access point; (4) at least partially in response to receiving confirmation of the receipt of the parcel and the presentation of the first unique identifier, facilitating, by a processor, placement of a label (e.g., a pre-printed label) on the parcel that includes a second unique identifier which, for example, may be in the form of a barcode or other suitable machine-readable indicia; (5) associating, by a processor, the second unique identifier with the shipping information in a data store; (6) facilitating shipment, by a processor, of the parcel from the access point to a handling facility; (7) reading, by a processor, the label and using, by a processor, information from the label (e.g., the second unique identifier) to retrieve the shipping information from the data store; (8) at least partially in response to retrieving the shipping information, facilitating, by a processor, printing of a shipping label comprising the shipping information and placement of the shipping label on the parcel at the handling facility; and (9) facilitating, by the processor, delivery of the parcel from the handling facility to the retailer based at least in part on the shipping information. In particular embodiments, the first entity may be the user attempting to return the item. In other embodiments, the first entity may be the retailer initiating the return on behalf of a customer.


A non-transitory computer-readable medium, in particular embodiments, stores computer-executable instructions for: (1) receiving, from a user, a request to return an item purchased from a particular retailer; (2) at least partially in response to receiving the request, providing the user a selection of one or more retailers from which to select the particular retailer; (3) at least partially in response to receiving the selected particular retailer from the user: (a) generating a first unique identifier; (b) associating the first unique identifier with the particular retailer and/or a particular address associated with the particular retailer; and (c) providing the first unique identifier to the user. In various embodiments, the non-transitory computer-readable medium further stores computer-executable instructions for: (1) receiving an indication at an access point that the user has presented a parcel containing the item and the unique identifier; and (2) at least partially in response to receiving the indication: (a) associating a pre-printed barcode with the particular retailer (and/or particular address) and the request, and (b) facilitating placement of the pre-printed barcode on the parcel at the access point. In various embodiments, the non-transitory computer-readable medium further stores computer-executable instructions for: (1) facilitating delivery of the parcel from the access point to a shipping hub; (2) receiving confirmation of delivery of the parcel at the shipping hub; (3) at least partially in response to receiving confirmation of the delivery, facilitating placement of a shipping label on the parcel, the shipping label containing the shipping information associated with the particular retailer; and (4) facilitating shipment of the parcel from the shipping hub to a final destination, the final destination being based at least in part on the shipping information associated with the particular retailer.


A computer system, in various embodiments, comprises at least one processor. In various embodiments, the computer system is configured for: (1) receiving a request from a retailer to ship a parcel, the parcel containing one or more items purchased from the retailer by a customer; (2) associating the request with a unique identifier; (3) providing the unique identifier to the customer; (4) receiving the unique identifier at an access point; (5) facilitating placement of a barcode on the parcel; (6) associating the barcode with the unique identifier; (7) facilitating delivery of the parcel from the access point to a shipping hub; (8) receiving confirmation of the delivery of the parcel to the shipping hub; (9) at least partially in response to receiving confirmation of the delivery, facilitating placement of shipping information associated with the retailer on the parcel; and (10) facilitating delivery of the parcel to a final destination, where the final destination is based at least in part on the shipping information associated with the retailer.





BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of a system and method for returning of items are described below. In the course of this description, reference will be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:



FIG. 1 is a block diagram of a return shipping system in accordance with an embodiment of the present system;



FIG. 2 is a schematic diagram of a computer, such as the logistics server of FIG. 1, that is suitable for use in various embodiments;



FIGS. 3A and 3B depicts a flow chart that generally illustrates various steps executed by an exemplary Item Return Shipping Module; and



FIG. 4 depicts a transportation diagram depicting an exemplary transportation path that may be taken by a parcel shipped using the return shipping system.





DETAILED DESCRIPTION

Various embodiments now will be described more fully hereinafter with reference to the accompanying drawings. It should be understood that the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.


Overview

In various embodiments, a system and method for facilitating shipping a parcel in the context of an item return is configured to enable the user to return the item without having to print or otherwise fill out a shipping label for shipping a parcel containing the item to be returned. This may be useful, for example, in situations where the user does not have access to a printer or a stock of pre-printed shipping labels or where an online retailer has not provided a return shipping label as part of a shipment containing an item purchased from the retailer.


In an exemplary implementation of systems and methods according to various embodiments, a user may bring a parcel containing an item for return to an access point as described above and either: (1) inform the attendant at the access point that the user wishes to return the item in the parcel to a particular retailer; or (2) indicate, at a computing device at the access point, the retailer to whom the user wishes to return the item (e.g., by using a graphical user interface to select the retailer from a list of retailers that accept such returns). The system may then optionally generate a barcode associated with the retailer. The attendant may then place the system-generated barcode, or a pre-printed barcode that is associated with the retailer, on the parcel. The attendant or the user then coordinates a pickup of the parcel by a common carrier at the access point or other suitable location. After the common carrier receives the parcel, the common carrier reads the barcode and uses information associated with the barcode to retrieve consignee information for the parcel. The consignee information may include, for example, a street address of an entity that will process the return of the item. The common carrier then facilitates delivery of the parcel to the entity that will process the return of the item.


Exemplary Technical Platforms

As will be appreciated by one skilled in the relevant field, the present invention may be, for example, embodied as a computer system, a method, or a computer program product. Accordingly, various embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, particular embodiments may take the form of a computer program product stored on a computer-readable storage medium having computer-readable instructions (e.g., software) embodied in the storage medium. Various embodiments may take the form of web-implemented computer software. Any suitable computer-readable storage medium may be utilized including, for example, hard disks, compact disks, DVDs, optical storage devices, and/or magnetic storage devices.


Various embodiments are described below with reference to block diagrams and flowchart illustrations of methods, apparatuses (e.g., systems), and computer program products. It should be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by a computer executing computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus to create means for implementing the functions specified in the flowchart block or blocks.


These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner such that the instructions stored in the computer-readable memory produce an article of manufacture that is configured for implementing the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.


Accordingly, blocks of the block diagrams and flowchart illustrations support combinations of mechanisms for performing the specified functions, combinations of steps for performing the specified functions, and program instructions for performing the specified functions. It should also be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and other hardware executing appropriate computer instructions.


Example System Architecture


FIG. 1 is a block diagram of a Return Shipping System 100 according to a particular embodiment. As may be understood from this figure, the Return Shipping System 100 includes a Logistics Server 110, One or More Networks 115, One or More Remote Computing Devices 130 (e.g., such as a smart phone, a tablet computer, a wearable computing device, a laptop computer, a desktop computer, etc.), and a Database 140. In particular embodiments, the One or More Networks 115 facilitate communication between the One or More Remote Computing Devices 130 and the Logistics Server 110.


The One or More Networks 115 may include any of a variety of types of wired or wireless computer networks such as the Internet, a private intranet, a mesh network, a public switch telephone network (PSTN), or any other type of network (e.g., a network that uses Bluetooth or near field communications to facilitate communication between computing devices). The communication link between the One or More Remote Computing Devices 130 and the Logistics Server 110 may be, for example, implemented via a Local Area Network (LAN) or via the Internet.



FIG. 2 illustrates a diagrammatic representation of a computer architecture 105 that can be used within the Return Shipping System 100, for example, as a client computer (e.g., one of the One or More Remote Computing Devices 110 shown in FIG. 1), or as a server computer (e.g., the Logistics Server 110 shown in FIG. 1). In particular embodiments, the computer 105 may be suitable for use as a computer within the context of the Return Shipping System 100 that is configured for facilitating a shipment of a parcel by a user substantially without requiring the user to place a shipping label on the parcel.


In particular embodiments, the computing device 105 may be connected (e.g., networked) to other computing devices in a LAN, an intranet, an extranet, and/or the Internet. As noted above, the computing device 105 may operate in the capacity of a server or a client computing device in a client-server network environment, or as a peer computing device in a peer-to-peer (or distributed) network environment. The computing device 105 may be a desktop personal computing device (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, a switch or bridge, or any other computing device capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that computing device. Further, while only a single computing device is illustrated, the term “computing device” shall also be taken to include any collection of computing devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.


An exemplary computing device 105 includes a processing device 202, a main memory 204 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), a static memory 206 (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage device 218, which communicate with each other via a bus 232.


The processing device 202 represents one or more general-purpose or specific processing devices such as a microprocessor, a central processing unit, or the like. More particularly, the processing device 202 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or processor implementing other instruction sets, or processors implementing a combination of instruction sets. The processing device 202 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. The processing device 202 may be configured to execute processing logic 226 for performing various operations and steps discussed herein.


The computing device 105 may further include a network interface device 208. The computing device 105 also may include a video display unit 210 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device 212 (e.g., a keyboard), a cursor control device 214 (e.g., a mouse), and a signal generation device 216 (e.g., a speaker).


The data storage device 218 may include a non-transitory computing device-accessible storage medium 230 (also known as a non-transitory computing device-readable storage medium or a non-transitory computing device-readable medium) on which is stored one or more sets of instructions (e.g., software 222) embodying any one or more of the methodologies or functions described herein. The software 222 may also reside, completely or at least partially, within the main memory 204 and/or within the processing device 202 during execution thereof by the computing device 120—the main memory 204 and the processing device 202 also constituting computing device-accessible storage media. The software 222 may further be transmitted or received over a network 115 via a network interface device 208.


While the computing device-accessible storage medium 230 is shown in an exemplary embodiment to be a single medium, the terms “computing device-accessible storage medium” and “computer-readable medium” should be understood to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The terms “computing device-accessible storage medium” and “computer-readable medium” should also be understood to include any that is capable of storing, encoding or carrying a set of instructions for execution by the computing device and that cause the computing device to perform any one or more of the methodologies of the present invention. The terms “computing device-accessible storage medium” and “computer-readable medium” should accordingly be understood to include, but not be limited to, solid-state memories, optical and magnetic media, etc.


Exemplary Access Points

Logistics networks, according to various embodiments, use access points (e.g., attended pickup/delivery locations) to facilitate: (1) the convenient delivery of parcels and other items to individuals; and/or (2) the convenient pickup of parcels and other items from individuals who wish to send those items to others via a common carrier. In various embodiments, a shipping access point may include, for example, a retail store (e.g., including a gas station, grocery store, or pharmacy), a stand-alone kiosk, or any other suitable location for receiving and processing parcels for shipment. For example, a gas station, a convenience store, a flower shop, a magazine stand, a retail location associated with a common carrier, a kiosk at a mall (or other type of shopping center), or a retail department store (e.g., or other brick-and-mortar store) may enter into an agreement with a common carrier to accept and process parcels for later pickup by the common carrier for further handling and/or ultimate shipment to a final destination.


In certain embodiments, each access point is manned for at least some time during the week and is equipped with a computer system that is adapted to communicate both with: (1) one or more computer systems associated with the common carrier; (2) one or more computing devices associated with the sender of the parcel; and (3) one or more computing devices associated with the recipient of the parcel. An example of a suitable computer system is shown in FIG. 1 and is described in greater technical detail below.


In particular embodiments, a computer at the access point (e.g., an “access point computer”) is adapted to send suitable messages regarding the status of parcels handled by the access point. For example, when the access point receives a parcel, the access point computer may automatically transmit an e-mail, text, or other message to: (1) the common carrier's computer system; (2) the recipient's computing device; and/or (3) the sender's computing device indicating that the parcel has been received by the access point and is ready to be delivered to the recipient. The message may also include other suitable information, such as the name and location (e.g., address, GPS coordinates, etc.) of the access point and the days and hours of operation of the access point.


The access point may also automatically transmit an e-mail, text, or other message to: (1) the common carrier's computer system; (2) the recipient's computing device; (3) the sender's computing device; and/or (4) any other suitable computer in response to any suitable event including, for example: (1) the parcel being dropped off by the individual; (2) the parcel being sent to the recipient; (3) the parcel being transferred to another access point; or (4) any other suitable event.


In various embodiments, the system may be configured to facilitate the delivery of parcels directly to access points from, for example, e-commerce retailers from which users may order items for delivery. For example, the system may be configured to allow a user making purchases of items via the Internet to have those items delivered directly to the access points. In such embodiments, as well as in other embodiments, the system may be configured to present users with a selection of access points for items that the user orders. In other embodiments, the system may be configured to enable a user to have ordered items delivered to an access point by entering an address associated with the access point as the shipping address of the item.


In various embodiments, access points may be configured to enable users to drop off or deposit parcels for shipment. In particular embodiments, the system is configured to facilitate shipment of parcels from access point to any other location (e.g., business or residential addresses, other attended delivery/pickup locations, etc.). In some embodiments, access points are configured to hold parcels dropped off at the access point until a later time. In particular embodiments, access points may include secure compartments (e.g., lockers) for holding items for later pickup by a consignee or common carrier.


Exemplary System Platform

Various embodiments of a return shipping system are described below and may be implemented in any suitable context. For example, particular embodiments may be implemented within the context of a logistics service in order to provide users with simple methods for shipping parcels and, in particular, for returning items purchased from online retailers. Various aspects of the system's functionality may be executed by certain system modules, including an Item Return Shipping Module 300. This module is discussed more fully below. It should be understood that while the various steps of the Item Return Shipping Module 300 are described in a particular order, various embodiments of the Item Return Shipping Module 300 may perform the steps below in an order other than the order in which they are presented. Similarly, various embodiments may perform steps in addition to the steps described below or omit one or more of the described steps.


Item Return Shipping Module


Turning to FIGS. 3A and 3B, when executing the Item Return Shipping Module 300, the system begins, in various embodiments, at Step 310 by receiving, from a first entity, a request to ship a parcel, where the request includes shipping information and the parcel contains one or more items purchased from a retailer. In particular embodiments, the request is a request to return the one or more items to the retailer and the shipping information includes the retailer's name and/or address. In particular embodiments, the shipping information may also include: (1) the name of the parcel's consignee; (2) a destination address for the parcel (e.g., a shipping address); (3) a return address for the parcel (e.g., the user's address); (4) a preferred shipping method for the parcel (e.g., ground shipping, next day shipping, 2-day shipping, or any other suitable shipping method); and/or (5) any other suitable information related to the shipment such as, for example, insurance information for the parcel, special handling instructions for the parcel, etc. In some embodiments, the shipping information includes retailer information. In other embodiments, when the user makes the request to ship the parcel, the user may provide payment (e.g., via credit card, money order, debit card, wire transfer, etc.) for the shipment of the parcel, a cost of which the system may, for example, determine based at least in part on the destination address and/or preferred shipping method. In other embodiments, the retailer may provide payment for the shipment of the parcel.

    • In various embodiments, the system is a carrier system (e.g., a system associated with a common carrier or other logistics services provider). In such embodiments, the carrier system may comprise a network of one or more access points for facilitating shipment of parcels. In various embodiments, each particular access point may comprise one or more computing devices which may, for example, be connected to the carrier system via a suitable network (e.g., via the Internet). In other embodiments, the system may include a retailer system associated with a particular retailer (e.g., the retailer from which the one or more items for return were purchased). In various embodiments, the system may include a carrier system and a retailer system which may, for example, be connected via one or more suitable network. In such embodiments, the carrier system may be configured to communicate with the retailer system (e.g., via the network) in order to send and receive data. In particular embodiments, a carrier system may be configured to receive a request to return one or more items directly from a user. In other embodiments, a carrier system may be configured to receive the request from a retailer (e.g., via the retailer system) on the user's behalf.


In various embodiments, the first entity is a user that desires to return the one or more items purchased from the retailer, which the user may, for example, have purchased themselves, received as a gift, or may be returning on behalf of another person. In the case of the first entity being a user wishing to return an item, the user may place the request from any suitable computing device, such as, for example, any suitable smart phone, tablet computer, desktop computer, or other suitable computing device. In various embodiments, the system receives the request from a computing device associated with the user. In other embodiments, the system receives the request from a computing device associated with an access point, such as any access point discussed below (e.g., such as a computing device located at the access point). In various embodiments, the user may log into an account associated with a common carrier via the computing device in order to make the request and enter retailer information associated with the one or more items, as well as (optionally) other shipping information associated with the retailer. In particular embodiments, the system is configured to provide the user with a selection of one or more retailers in response to the request to return the one or more items. In particular embodiments, the system is configured to provide the selection of one or more retailers by displaying the one or more retailers on a display associated with a computing device associated with the access point. In such embodiments, the system may, for example, cause the computing device associated with the access point to display the one or more retailers. In various embodiments, the one or more retailers may include one or more retailers that have provided return shipping information to the system (e.g., a return shipping address). In other embodiments, the carrier system may send a request for shipping information to a particular retailer system in response to selection, by the user, of a particular retailer from the list of one or more retailers.


In various embodiments, the system is configured to receive the request based on receiving shipping information associated with an original delivery of the one or more items the user desires to return. For example, in an embodiment in which the user has made a purchase from an online retailer, and received delivery of the item, the system may be configured to determine the retailer to whom the item should be returned based at least in part on shipping information associated with the delivery of the item to the user. For example, the system may determine a return address, retailer name, etc. based on a tracking or shipping number associated with an original delivery of the item to the user.


In other embodiments, the system may be configured to receive a selection of the retailer from the user and, based at least part on the selection of the retailer, retrieve (e.g., from a suitable database) shipping or other return information for the retailer (e.g., an address to which the retailer desires to have returned items sent, one or more of the retailer's return policies, or specific return information for the item being returned). In various embodiments, the shipping or other return information may be received by the system for one or more retailers. For example, a retailer that wishes to allow their customers to return items purchased from the retailer via an access point may provide the system (e.g., a carrier system) with the shipping and other return information associated with the retailer. In such embodiments, the system may be able to retrieve the return information associated with a particular retailer when a user is requesting to return an item to the particular retailer via an access point without further input from the particular retailer or requiring the access point or system facilitating the return to request further information from the particular retailer in order to facilitate the return.


In particular embodiments, the user is a user that may be unable or unwilling to print a shipping label (e.g., because they do not own a printer). In particular embodiments, the request may come from a user that is not currently present at a location that is capable of accepting one or more parcels for shipment (e.g., the user may be at their home, office, or other location). In other embodiments, the system may receive the request from a user that is currently at a shipping access point (e.g., such as any suitable access point discussed herein, kiosk, drop box) or other location where the user may drop off one or more parcels for shipment.


In various embodiments, the system is further configured to enable the retailer to approve or deny the request to return the item before the item is shipped. For example, a retailer may deny the return if the user is attempting to return an un-returnable item (e.g., an item for which the return period has expired, a final sale item, etc.) or for any other suitable reason. In various embodiments, the system is configured to enable the retailer to authorize payment for the item return (e.g., so the user does not have to pay for return shipping of the one or more items). In various embodiments, the system is configured to request authorization for the return from the particular retailer. For example, in embodiments in which the user requests to make the return via a carrier system at an access point, the carrier system may, in response to the request to return the item, request authorization from the retailer to facilitate return of the item by: (1) transmitting a request to the retailer system for authorization via a network; and (2) receiving authorization from the retailer system via the network. In particular embodiments, the request for authorization may include information associated with the one or more items for return such as, for example, an order number, item name, item description, invoice number associated with the purchase of the item, etc. In various other embodiments, such as embodiments in which a user initiates a return of an item via a retailer system, the system may be configured to approve or deny a return request in response to receiving the request.


In still other embodiments, the system is configured to notify a retailer (e.g., by communicating over a network with a retailer system or server) of the user's request to return an item. In various embodiments, the system is configured to transmit, via a network, order information associated with the one or more items that the user is attempting to return to the retailer. In particular embodiments, the system is configured to receive this order information as part of the request to facilitate the return of the one or more items.


In other embodiments, the first entity is a retailer who may desire to facilitate the return of one or more items on behalf of a user. For example, a user that has purchased one or more items from a retailer (e.g., such as an online retailer or other retailer) may contact the retailer and express a desire to return one or more of the one or more items. The retailer may then initiate the return by requesting shipment of the item on behalf of the user. In such embodiments, the retailer may, for example, contact the carrier system via a network (e.g., the retailer system may contact the carrier system via the network). The retailer system may then transmit data over the network to the carrier system for facilitation of shipment of the one or more return items such as, for example, a destination address, etc.


In various embodiments, the system is configured to enable a user to make a request to facilitate a return of one or more items in a parcel without requiring the user to print any sort of label or shipping information associated with the return. In particular, the system may enable a user that does not own a printer to: (1) manifest a return shipment; and (2) drop off a parcel containing one or more items to return to a particular retailer, without having to print a shipping or other label.


The system continues, at Step 320 by, at least partially in response to receiving the request, associating the shipping information with a first unique identifier in the system's memory or in any other suitable memory. In particular embodiments, the first unique identifier includes any suitable alphanumeric code, such as a unique alphanumeric code that may, for example, be any machine-readable indicia such as a barcode (e.g., a linear barcode, a matrix barcode, a QR Code, etc.), RFID tag, unique identifier, or other electronic tag identification. In other embodiments, the first unique identifier may include any suitable unique identifier that may be presented by the user at an access point when dropping off the parcel for shipment (such as a confirmation code, etc.). In particular embodiments, the system is configured to provide the first unique identifier to the user, for example, by sending the first unique identifier to the user (e.g., via a suitable electronic transmission to the user, such as email, SMS, etc.) or by displaying the first unique identifier on a computing device associated with the user (e.g., on the user's smart phone). In various embodiments, the system providing the first unique identifier may include a carrier system or retailer system.


In particular embodiments, the system is configured to generate the first unique identifier in response to receiving the request at Step 310. For example, a carrier system may generate the unique identifier in response to receiving a request to facilitate the return of an item from a user via a handheld computing device associated with the user. In other embodiments, the unique identifier may include a pre-existing unique identifier. In a particular embodiments, the pre-existing unique identifier is a unique identifier that was provided to the user by the retailer. For example, when the customer ordered the one or more items from the retailer, the retailer may have included a unique ‘return’ identifier in any suitable manner (e.g., by including the unique identifier in a parcel when retailer shipped the one or more items to the customer, in an e-mail or other message, etc.). In particular embodiments, a carrier system may be configured to query a retailer system for shipping information related to the unique ‘return’ identifier in response to receiving a request to facilitate a return of one or more items. In such embodiments, the carrier system may then store the shipping information and memory and associate the shipping information with the unique ‘return’ identifier.


In various embodiments, the system is configured to facilitate a confirmation of the contents of the parcel containing the one or more items. The system may, for example, receive confirmation (e.g., from a computer associated with the access point) that the one or more items to be returned to the retailer are, in fact, contained in the parcel prior to coordinating delivery of the parcel to the handling facility from the access point. In particular embodiments, an attendant at the access point may manually confirm this and enter the confirmation into an access point computer when the attendant receives the parcel from the user. The confirmation may be a simple message indicating particular contents are present. In further embodiments, the message may include the serial number of the items being returned, a picture of the items, a return authorization number, or other identifying information.


In various embodiments, when the first entity is the retailer, the system is configured to provide the first unique identifier to the user (e.g., a customer of the retailer). In other embodiments, the system is configured to provide the first unique identifier to the retailer (e.g., the retailer system), so that the retailer can provide it to a customer attempting to return the one or more items. In various embodiments, the first unique identifier may include an identifier that the common carrier has utilized previously in association with a different shipment. For example, the common carrier may recycle (e.g., re-use) identifiers that have been previously associated with other shipping information at a later time. The time may be any time such as any suitable length of time after the particular identifier has been utilized by a user to initiate a shipment at an access point as discussed herein.


Continuing at Step 330, the system receives confirmation of receipt of the parcel and presentation of the first unique identifier at a shipping access point. In various embodiments, a shipping access point may include, for example, a retail store (e.g., including a gas station, grocery store, or pharmacy), a stand-alone kiosk, or any other suitable location for receiving and processing parcels for shipment. For example, a gas station, a convenience store, a flower shop, a magazine stand, a retail location associated with a common carrier, a kiosk at a mall (or other type of shopping center), or a retail department store (e.g., or other brick-and-mortar store) may enter into an agreement with a common carrier to accept and process parcels for later pickup by the common carrier for further handling and/or ultimate shipment to a final destination.


In certain embodiments, the access point is manned for at least some time during weekdays and/or weekends and is equipped with a computer system that is adapted to communicate with: (1) one or more computer systems associated with the common carrier; (2) one or more computing devices associated with the sender of the parcel (e.g., the user); (3) one or more computing devices or computing systems associated with one or more retailers; (4) etc. In particular embodiments, the communication may occur via any suitable network such as, for example, the Internet. In various other embodiments, the access point is unmanned and equipped with a computer system configured to enable the user to implement various functions described herein substantially without the help of a human attendant.


In particular embodiments, the system receives confirmation of receipt of the parcel and presentation of the first unique identifier at the access point in response to entry (e.g., by the user or an attendant at the access point) of the first unique identifier into a computing device associated with (e.g., located at) the access point. For example, the user or an attendant may: (1) enter the first unique identifier into the access point's computer system using a suitable alphanumeric entry device (e.g., keyboard); (2) provide the first unique identifier in a way that the system may interpret using suitable voice recognition techniques (e.g., by speaking the first unique identifier into one or more microphones associated with the system; (3) scan the first unique identifier (e.g., using a suitable barcode scanner, imaging device, or other suitable scanning device); and/or (4) use any other suitable method of providing the first unique identifier at the access point.


Next, at Step 340, at least partially in response to receiving the confirmation at Step 330, the system coordinates placement of a second unique identifier on the parcel. In various embodiments the second unique identifier comprises a pre-existing unique identifier such as, for example, a pre-printed barcode, RFID tag, electronic tag, flexible or rigid container with a unique identifier, etc.) This may be coordinate association of the second unique identifier with the parcel by, for example, displaying instructions on a display screen indicating that a human user should place a pre-printed label that includes the second unique identifier on the parcel, by printing the second unique identifier onto a label that is to be placed on the parcel, by generating the second unique identifier, or through any other suitable technique of coordinating placement of the second unique identifier on the parcel. Although the second unique identifier may be unique to the particular transaction (e.g., the return transaction), it may have been previously used by the system in a prior shipping transaction and re-used as discussed above.


In various embodiments, one or more labels may be provided (e.g., in rolls or sheets of stickers including a pre-printed barcode, RFID tags, electronic tags, flexible or rigid containers with unique identifiers, etc.) at the access point that may be placed on the parcel. The containers may be cardboard boxes, plastic boxes, bags or the like. In other embodiments, the system is configured to print (e.g., generate and print) a barcode, encode an electronic tag, etc. at the access point for placement on the parcel. This system may execute this step, for example, in response to receiving the confirmation at Step 330.


In particular embodiments, the system is configured to facilitate placement of any other suitable machine-readable indicia on the parcel (e.g., a machine-readable indicia other than a barcode) that includes (e.g., communicates) the second unique identifier. In particular embodiments, the system is configured to facilitate placement of the other suitable machine-readable indicia on the parcel (e.g., a unique identifier comprising one or more characters, one or more images, etc.) that are representative of the second unique identifier. In such embodiments, the system may be configured to read the unique identifier using suitable optical character recognition (OCR) techniques, image recognition techniques, etc. Other machine readable indicia may include, for example, electronic tags that can be programmed to broadcast a unique code (e.g., RFID tags).


As noted above, in particular embodiments, the system may be configured to facilitate placement of a barcode (e.g., or other unique identifier such as an electronic tag, RFID tag, etc.) by instructing (e.g., displaying instructions to) an access point attendant or the user to place the pre-printed barcode on the parcel. In other embodiments, the system may be configured to print a barcode or other indicia directly on the parcel, or otherwise substantially automatically place the barcode on the parcel (e.g., using a stamp or other suitable mechanism).


In various embodiments, the pre-printed barcode or other unique identifier may include space (e.g., blank space) where shipping information (e.g., such as a delivery address) for the parcel may later be provided (e.g., written or printed). In particular embodiments, the space may be selected and sized to enable the system to print the shipping information directly within the space. In other embodiments, the space may be sized to enable the system to affix shipping information substantially within the available space.


Returning to FIGS. 3A and 3B, the system next proceeds to Step 350, where it associates the second unique identifier with the shipping information in a data store (e.g., such as the Database 140). In particular embodiments, the system is configured to also associate the second unique identifier with additional information such as, for example, the parcel's weight, dimensions, etc. In various embodiments, the system is configured to receive information associated with the parcel (e.g., such as size, weight, etc.) from the access point. The access point may, for example, have one or more computer peripherals (e.g., scales, cameras, or other devices), or non-peripheral devices, that may be used to weigh and/or measure the parcel in order to enable the user (e.g., or another individual) to provide such information to the system. In other embodiments, the system may determine the dimensions of the parcel from one or more images that the system takes of the parcel.


In particular embodiments, the data store may include any suitable data store such as any of one or more suitable servers or other computer storage media suitable for the storage of and later retrieval of the information by the system. In particular embodiments, the data store may be located on one or more local or remote servers.


Next, at Step 360, the system coordinates shipment of the parcel from the access point to a parcel handling facility by, for example, transmitting an electronic or non-electronic message to a suitable common carrier or other logistics provider indicating that the parcel is available for pickup. In particular embodiments, the system is configured to facilitate the delivery via a particular common carrier, such as a common carrier to which the user made the request to ship the parcel. In various embodiments, the system is configured to execute a pickup of the parcel from the access point at least partially in response to receiving the confirmation at Step 330 for delivery to the handling facility. In particular embodiments, the system is configured to receive confirmation of delivery of the parcel to the handling facility. In various embodiments, the system is configured to receive confirmation of the delivery of the parcel to the handling facility by receiving a scan of the second unique identifier at the handling facility. In other embodiments, the system is configured to provide tracking information associated with the parcel (e.g., a current location of the parcel) to: (1) the user; (2) an intended parcel recipient; and/or (3) any other suitable individual or entity.


At the parcel handling facility (e.g., a parcel handling facility, or a shipping hub, associated with the common carrier handling the parcel), the system, at Step 370, receives the second unique identifier from the parcel (e.g., by using any suitable technique to read a pre-printed barcode or alphanumeric string that represents the second unique identifier from the surface of the parcel). The system then uses the second unique identifier to retrieve the shipping information from the data store. In various embodiments, the system is configured to read the second unique identifier using any suitable scanner, imaging device, interrogator, etc.


Continuing at Step 380, the system, at least partially in response to retrieving the shipping information, facilitates printing of a shipping label (e.g., comprising the shipping information) for placement on the parcel. In particular embodiments, the shipping label comprises the name of the handling facility and/or the retailer. In various embodiments, the shipping label comprises a shipping address for the parcel and/or other information related to the shipment of the parcel. In some embodiments, the shipping label may include return confirmation information such as a return merchandize authorization number, order number, or other suitable return confirmation information. In certain embodiments, the shipping label may include information concerning the contents of the parcel. In particular embodiments, the system facilitates printing of the shipping label on an adhesive-backed paper, which may, for example, be placed substantially automatically on the parcel or placed on the parcel by an employee or other individual at the handling facility.


In other embodiments, the system may utilize one or more other suitable techniques for directing a parcel to its ultimate destination (e.g., one or more techniques other than a shipping label). In various embodiments, the one or more other techniques may include, for example, placing the parcel in a secondary container, bag, or other parcel that contains one or more shipping indicators such as, for example, an existing shipping label, an RFID tag or other electronic tag, a machine-readable-indicia, etc.


In various embodiments, the system is configured to print shipping information substantially directly on the parcel (e.g., on an outer surface of the parcel, in the space on a pre-printed label affixed to the parcel discussed above, etc.). In other embodiments, the system is configured to facilitate attachment or application of the shipping information to the parcel in any suitable manner other than those described above.


The system then, at Step 390, coordinates delivery of the parcel from the handling facility to the parcel's final destination based at least in part on the shipping information. In various embodiments, the system is configured to facilitate delivery in a way that at least satisfies a shipping speed (e.g., overnight, second day, etc.) that is included in the shipping information received at Step 310. In other embodiments, the system is configured to facilitate delivery of the parcel in a manner that conforms to any special handling instructions (e.g., handle with care, signature required, cool storage required, etc.), which may, for example, have been provided within the shipping information.


Illustrative Example

As an illustrative example, a user may initiate shipment of a parcel by using a software application running on a suitable computing device (e.g., their computer, smartphone, etc.) in order to initiate a return of an item purchased at an online retail store. During this process, the user may select the online retailer from a selection of online retailers provided in response to the initiation of the return by the user (e.g., a selection of online retailers that have a partnership with, or have provided return information to, the common carrier such as an address to return items to and other shipping information, etc.). The system may then generate a first unique identifier in the form of a barcode, associate the first unique identifier with shipping information for the retailer (or other suitable item return processing facility) that is, for example, stored in the system's memory or provided by the user, and send the unique identifier to a mobile computing device associated with the user (e.g., the user's smartphone). The user may then take the parcel to an access point (such as a gas station that has contracted with a common carrier to serve as an access point for the common carrier), give the parcel to an access point representative, and present the unique identifier to the access point representative.


In various embodiments, enabling the user to initiate the return via a computing device and enabling the user to product the unique identifier by showing the unique identifier to a representative on their mobile computing device may solve the technical problem of enabling a user to return a purchased item without having to print any sort of shipping label or receipt. This may be especially useful, for example, if the user does not have access to a printer (e.g., because they do not own one). The access point representative may then use a barcode scanner associated with the system to first scan the unique identifier and then scan a label that includes a pre-printed barcode (or other pre-printed machine-readable indicia) that represents a second unique identifier. The system then uses the first and second unique identifiers to associate, within the system's memory, the second unique identifier with the shipping information and/or the first unique identifier. The attendant then places the label containing the pre-printed barcode on the parcel and places the parcel in a bin or other storage container for later pickup by a common carrier (which may pick items up from the access point according to a particular schedule).


Once picked up by the common carrier from the access point, the parcel is taken by the common carrier to a parcel handling facility where the pre-printed barcode is scanned by the system using a barcode scanner, or imaging device associated with the system, to determine the second unique identifier. The system then uses the second unique identifier to obtain the shipping information for the parcel (e.g., from a database associated with the system). The system, in this particular example, then generates and prints a shipping label for the parcel. In various embodiments, the shipping label includes the shipping information for the parcel (e.g., the destination address) that the user originally entered for the parcel. The system then facilitates shipment of the parcel to the destination address (e.g., the address associated with the retailer or a third party entity that the retailer has retained to process returns on behalf of the retailer).


Although the above example is described using a pre-printed barcode as a unique identifier, it should be understood that various embodiments of the system may use other suitable unique identifiers such as any suitable identifier discussed above. Similarly, although this example describes the placement of a printed shipping label, other various embodiments of the system may utilize other suitable techniques for directing a parcel to its ultimate destination.



FIG. 4 depicts a transportation diagram depicting an exemplary transportation path that may be taken by a parcel shipped via the above-described process. As may be understood from this figure, a user may place an item for shipping into a parcel at their home 400. The user may then access their account with a common carrier via a desktop computer in their home in order to provide shipping information and receive a generated unique identifier. The user may then take the parcel to an access point 410 (e.g., by driving, walking, etc.). After presenting the unique identifier at the access point and after a pre-printed barcode is placed on the parcel, a common carrier transports the parcel to a local distribution center 420 (e.g., a handling facility). At the local distribution center, the barcode is scanned to retrieve shipping information for the parcel, and a shipping label is printed and placed on the parcel. The system then facilitates shipment of the parcel to its final destination 430.


Conclusion

Many modifications and other embodiments of the invention will come to mind to one skilled in the art to which this invention pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. While examples discussed above cover the use of the invention in the context of a return shipping service, the invention may be used in any other suitable context. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for the purposes of limitation.

Claims
  • 1. A computer-implemented method of enabling a user to return an item to a retailer via an access point, the method comprising: receiving, by one or more processors, from a first entity, a request to ship a parcel, the request including shipping information associated with a retailer from which the item was purchased;at least partially in response to receiving the request, generating, by a processor, a unique identifier and associating, by the one or more processors, the shipping information with the unique identifier;receiving, by the one or more processors, confirmation of (a) receipt of the parcel and (b) presentation of the unique identifier at an access point;at least partially in response to receiving confirmation of the receipt of the parcel and the presentation of the unique identifier, facilitating, by the one or more processors, associating a second unique identifier with the parcel;associating, by the one or more processors, the second unique identifier with the shipping information in a data store;facilitating, by the one or more processors, shipment of the parcel from the access point to a handling facility;reading, by the one or more processors, the second unique identifier and using, by the one or more processors, information from the second unique identifier to retrieve the shipping information from the data store;at least partially in response to retrieving the shipping information, facilitating, by the one or more processors, placement of a shipping label on the parcel at the handling facility; andfacilitating, by the one or more processors, delivery of the parcel from the handling facility to the retailer based at least in part on the shipping information.
  • 2. The computer-implemented method of claim 1, wherein: the first entity is a representative associated with the retailer; andthe computer-implemented method further comprises providing, by the one or more processors, the unique identifier to the user desiring to return the item by: transmitting the unique identifier to a computing device associated with the user via one or more networks.
  • 3. The computer-implemented method of claim 2, wherein receiving confirmation of presentation of the unique identifier at the access point comprises receiving, by a computing device associated with the access point, input of the unique identifier.
  • 4. The computer-implemented method of claim 3, wherein the unique identifier is a unique identifier selected from a group consisting of: a machine-readable indicia; andan electronic tag.
  • 5. The computer-implemented method of claim 1, wherein the first entity is the user desiring to return the item.
  • 6. The computer-implemented method of claim 5, wherein the method further comprises providing, by the one or more processors, a selection of one or more retailers from which the user may select the retailer when making the request.
  • 7. The computer implemented method of claim 6, further comprising notifying the retailer, by the one or more processors, of the request.
  • 8. The computer-implemented method of claim 7, further comprising enabling, by the one or more processors, the retailer to approve or deny the request.
  • 9. The computer-implemented method of claim 1, wherein the unique identifier comprises a pre-printed barcode.
  • 10. A non-transitory computer-readable medium storing computer-executable instructions for: receiving, from a user, a request to return an item purchased from a particular retailer, wherein the request includes shipping information;at least partially in response to receiving the request, providing the user a selection of one or more retailers from which to select the particular retailer;at least partially in response to receiving the selected particular retailer from the user: generating a unique identifier;associating the unique identifier with the particular retailer; andproviding the unique identifier to the user;receiving an indication at an access point that the user has presented: a parcel containing the item; andthe unique identifier;at least partially in response to receiving the indication: associating a pre-printed barcode with the particular retailer and the request; andfacilitating placement of the pre-printed barcode on the parcel at the access point;facilitating delivery of the parcel from the access point to a shipping hub;receiving confirmation of delivery of the parcel at the shipping hub, wherein the confirmation is based at least partially on reading the pre-printed barcode;at least partially in response to receiving confirmation of the delivery, facilitating placement of a shipping label on the parcel, the shipping label containing the shipping information, which is associated with the particular retailer; andfacilitating shipment of the parcel from the shipping hub to a final destination, the final destination being based at least in part on the shipping information associated with the particular retailer.
  • 11. The non-transitory computer-readable medium of claim 10, further storing computer executable instructions for, at least partially in response to receiving the selected particular retailer from the user, enabling the particular retailer to approve or deny the request.
  • 12. The non-transitory computer-readable medium of claim 11, further storing computer executable instructions for, at least partially in response to receiving approval for the request from the particular retailer, enabling the particular retailer to authorize payment for the shipment by the particular retailer.
  • 13. The non-transitory computer-readable medium of claim 10, wherein receiving the request from the user comprises receiving the request from a computing device associated with the user.
  • 14. The non-transitory computer-readable medium of claim 10, wherein receiving the request from the user comprises receiving the request from a computing device associated with the access point.
  • 15. A computer system comprising: at least one processor, wherein the computer system is configured for: receiving a request including shipping information from a retailer to ship a parcel, the parcel containing one or more items purchased from the retailer by a customer;at least partially in response to receiving the request:associating the request with a unique identifier; andproviding the unique identifier to the customer;receiving the unique identifier at an access point;at least partially in response to receiving the unique identifier at the access point: facilitating placement of a barcode on the parcel; andassociating the barcode with the unique identifier;facilitating delivery of the parcel from the access point to a shipping hub;receiving confirmation of the delivery of the parcel to the shipping hub, wherein the confirmation is based at least partially on reading the barcode;at least partially in response to receiving confirmation of the delivery, facilitating placement of the shipping information associated with the retailer on the parcel; andfacilitating delivery of the parcel to a final destination, where the final destination is based at least in part on the shipping information associated with the retailer.
  • 16. The computer system of claim 15, wherein the computer system is further configured for facilitating confirmation that the parcel contains the one or more items before facilitating delivery of the parcel from the access point to the shipping hub.
  • 17. The computer system of claim 16, wherein the computer system is further configured for notifying the retailer of the confirmation that the parcel contains the one or more items.
  • 18. The computer system of claim 15, wherein the computer system is further configured for generating the unique identifier at least partially in response to the request.
  • 19. The computer system of claim 15, wherein the unique identifier comprises a barcode.
CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Application No. 62/080,130, filed Nov. 14, 2014, entitled “SYSTEMS AND METHODS FOR FACILITATING SHIPPING OF PARCELS FOR RETURNING ITEMS,” which is hereby incorporated by reference in its entirety.

US Referenced Citations (490)
Number Name Date Kind
3712468 Wenner et al. Jan 1973 A
5153842 Dlugos, Sr. et al. Oct 1992 A
5168444 Cukor et al. Dec 1992 A
5375240 Grundy Dec 1994 A
5400020 Jones et al. Mar 1995 A
5444444 Ross et al. Aug 1995 A
5623260 Jones et al. Apr 1997 A
5648770 Ross et al. Jul 1997 A
5656799 Ramsden et al. Aug 1997 A
5657010 Jones et al. Aug 1997 A
5668543 Jones et al. Sep 1997 A
5726435 Hara et al. Mar 1998 A
5774053 Porter Jun 1998 A
5786748 Nikolic et al. Jul 1998 A
5831220 Ramsden et al. Nov 1998 A
5831860 Foladare et al. Nov 1998 A
5979750 Kindell Nov 1999 A
6010064 Umeda et al. Jan 2000 A
6026375 Hall et al. Feb 2000 A
6028517 Sansone et al. Feb 2000 A
6047264 Fisher et al. Apr 2000 A
6085170 Tsukuda Jul 2000 A
6208980 Kara Mar 2001 B1
6211781 McDonald Apr 2001 B1
6220509 Byford Apr 2001 B1
6236972 Shkedy May 2001 B1
6278936 Jones Aug 2001 B1
6285916 Kadaba et al. Sep 2001 B1
6289323 Gordon et al. Sep 2001 B1
6304856 Soga et al. Oct 2001 B1
6313760 Jones Nov 2001 B1
6317060 Jones Nov 2001 B1
6323254 Weikard et al. Nov 2001 B1
6323782 Stephens et al. Nov 2001 B1
6343275 Wong Jan 2002 B1
6344796 Ogilvie et al. Feb 2002 B1
6356196 Wong Mar 2002 B1
6363323 Jones Mar 2002 B1
6411891 Jones Jun 2002 B1
6433732 Dutta et al. Aug 2002 B1
6442589 Takahashi et al. Aug 2002 B1
6456900 Kakuta Sep 2002 B1
6463420 Guidice et al. Oct 2002 B1
6480758 Stevens Nov 2002 B2
6486801 Jones Nov 2002 B1
6492912 Jones Dec 2002 B1
6510383 Jones Jan 2003 B1
6536659 Hauser Mar 2003 B1
6539360 Kadaba Mar 2003 B1
6570488 Kucharczyk et al. May 2003 B2
6595342 Maritzen et al. Jul 2003 B1
6606604 Dutta Aug 2003 B1
6612489 McCormick et al. Sep 2003 B2
6615092 Bickley et al. Sep 2003 B2
6618668 Laird Sep 2003 B1
6634551 Barta et al. Oct 2003 B2
6683542 Jones Jan 2004 B1
6688435 Will et al. Feb 2004 B1
6690997 Rivalto Feb 2004 B2
6694217 Bloom Feb 2004 B2
6700507 Jones Mar 2004 B2
6701299 Kraisser et al. Mar 2004 B2
6714859 Jones Mar 2004 B2
6725127 Stevens Apr 2004 B2
6741927 Jones May 2004 B2
6748295 Tilles et al. Jun 2004 B2
6748318 Jones Jun 2004 B1
6748320 Jones Jun 2004 B2
6756879 Shuster Jun 2004 B2
6763299 Jones Jul 2004 B2
6763300 Jones Jul 2004 B2
6772130 Karbowski et al. Aug 2004 B1
6791450 Gokcebay et al. Sep 2004 B2
6804606 Jones Oct 2004 B2
6820805 Stevens Nov 2004 B2
6845909 Bong et al. Jan 2005 B2
6859722 Jones Feb 2005 B2
6862576 Turner Mar 2005 B1
6882269 Moreno Apr 2005 B2
6902109 Barta et al. Jun 2005 B2
6904359 Jones Jun 2005 B2
6933832 Simms et al. Aug 2005 B1
6950803 Tiley et al. Sep 2005 B2
6952645 Jones Oct 2005 B1
6961711 Chee Nov 2005 B1
6967575 Dohrmann et al. Nov 2005 B1
6974928 Bloom Dec 2005 B2
6975998 Jones Dec 2005 B1
6976090 Ben-Shaul et al. Dec 2005 B2
6978929 Buie et al. Dec 2005 B2
6985871 Simon et al. Jan 2006 B2
6990467 Kwan Jan 2006 B1
6994253 Miller et al. Feb 2006 B2
7020623 Tiley et al. Mar 2006 B1
7028895 Ashaari Apr 2006 B2
7030781 Jones Apr 2006 B2
7031959 Garner et al. Apr 2006 B2
7055741 Bong et al. Jun 2006 B2
7068149 Lee et al. Jun 2006 B2
7075451 Yamada Jul 2006 B2
7110958 Yang Sep 2006 B2
7133743 Tilles et al. Nov 2006 B2
7158941 Thompson Jan 2007 B1
7158948 Rodriguez et al. Jan 2007 B1
7177825 Borders et al. Feb 2007 B1
7212829 Lau et al. May 2007 B1
7212984 Wolfe et al. May 2007 B2
7222081 Sone May 2007 B1
7225983 Park et al. Jun 2007 B2
7233907 Young Jun 2007 B2
7248160 Mangan et al. Jul 2007 B2
7249044 Kumar et al. Jul 2007 B2
7249087 Sharp et al. Jul 2007 B2
7254549 Bansal et al. Aug 2007 B1
7257552 Franco Aug 2007 B1
7267920 Nakazawa et al. Sep 2007 B2
7312702 Willms et al. Dec 2007 B1
7337944 Devar Mar 2008 B2
7341186 Mrozik et al. Mar 2008 B2
7358857 White Apr 2008 B1
7376598 Estes et al. May 2008 B2
7385499 Horton et al. Jun 2008 B2
7422149 Aptekar Sep 2008 B2
7426484 Joyce et al. Sep 2008 B2
7479899 Horstemeyer Jan 2009 B2
7501946 Lanigan et al. Mar 2009 B2
7509228 Bielefeld et al. Mar 2009 B2
7511617 Burman et al. Mar 2009 B2
7528722 Nelson May 2009 B2
7574366 Burman et al. Aug 2009 B2
7580845 Burman et al. Aug 2009 B2
7617133 Antony et al. Nov 2009 B1
7624024 Levis et al. Nov 2009 B2
7636696 Sigler, Jr. Dec 2009 B1
7647231 Kuebert et al. Jan 2010 B2
7653457 Bloom Jan 2010 B2
7653603 Holtkamp, Jr. et al. Jan 2010 B1
7657466 Klingenberg et al. Feb 2010 B2
7693723 Wade Apr 2010 B2
7711654 Schmidtberg et al. May 2010 B2
7712670 Sauerwein, Jr. et al. May 2010 B2
7742928 Reynolds et al. Jun 2010 B2
7752134 Spear Jul 2010 B2
7765131 Klingenberg et al. Jul 2010 B2
7769778 Snapp et al. Aug 2010 B2
7815112 Volpe et al. Oct 2010 B2
7822618 Kaneko Oct 2010 B2
7831439 Bryar et al. Nov 2010 B1
7848961 Estes et al. Dec 2010 B2
7853481 Johnson Dec 2010 B1
7868753 Jenkins et al. Jan 2011 B2
7925524 Florence Apr 2011 B2
7962422 Melechko et al. Jun 2011 B1
7969306 Ebert et al. Jun 2011 B2
7984289 Orbke et al. Jul 2011 B2
7996328 Lundberg et al. Aug 2011 B1
8010430 Chase et al. Aug 2011 B1
8010462 Kinory et al. Aug 2011 B2
8015023 Lee et al. Sep 2011 B1
8027933 Lou et al. Sep 2011 B2
8036993 Estes Oct 2011 B2
8073723 Bilibin et al. Dec 2011 B1
8086546 Spiegel et al. Dec 2011 B2
8103521 Kuebert et al. Jan 2012 B2
8103716 Boyce et al. Jan 2012 B2
8108265 Bonner et al. Jan 2012 B2
8117462 Snapp et al. Feb 2012 B2
8131652 Gullo et al. Mar 2012 B2
8140551 Garner et al. Mar 2012 B2
8140592 Scott et al. Mar 2012 B2
8156007 Anthony et al. Apr 2012 B1
8204799 Murray et al. Jun 2012 B1
8219490 Hammad et al. Jul 2012 B2
8225388 Vogel et al. Jul 2012 B2
8234275 Grant et al. Jul 2012 B2
8249998 Reynolds et al. Aug 2012 B2
8255235 Aldstadt Aug 2012 B2
8255339 Andrew Aug 2012 B2
8265947 Kuebert et al. Sep 2012 B2
8280824 Vermeulen et al. Oct 2012 B1
8291234 Snapp et al. Oct 2012 B2
8306923 Roache et al. Nov 2012 B1
8311895 Murugan et al. Nov 2012 B1
8340978 Wade Dec 2012 B2
8352551 Campbell et al. Jan 2013 B2
8356187 Cook et al. Jan 2013 B2
8364953 Bullard, Jr. Jan 2013 B2
8380641 Bennett et al. Feb 2013 B1
8392262 Mallick et al. Mar 2013 B2
8437742 Garskof May 2013 B2
8468062 Kamdar Jun 2013 B1
8489520 Kuebert et al. Jul 2013 B2
9141931 Ackerman Sep 2015 B2
9195950 Schenken Nov 2015 B2
9692738 Wenneman et al. Jun 2017 B1
9916557 Gillen et al. Mar 2018 B1
9984351 Antony May 2018 B1
10007712 Williams et al. Jun 2018 B1
20010040422 Gramlich Nov 2001 A1
20010042001 Goto et al. Nov 2001 A1
20010042024 Rogers Nov 2001 A1
20010051885 Nardulli et al. Dec 2001 A1
20020007299 Florence Jan 2002 A1
20020007353 Kornacki Jan 2002 A1
20020010634 Roman et al. Jan 2002 A1
20020013744 Tsunenari et al. Jan 2002 A1
20020016726 Ross Feb 2002 A1
20020019761 Lidow Feb 2002 A1
20020019777 Schwab et al. Feb 2002 A1
20020029194 Lewis et al. Mar 2002 A1
20020032612 Williams et al. Mar 2002 A1
20020032613 Buettgenbach et al. Mar 2002 A1
20020035515 Moreno Mar 2002 A1
20020038266 Tuttrup et al. Mar 2002 A1
20020040350 Shinzaki Apr 2002 A1
20020046056 Demarco et al. Apr 2002 A1
20020070882 Jones Jun 2002 A1
20020073039 Ogg et al. Jun 2002 A1
20020080030 Inomata Jun 2002 A1
20020082770 Jones Jun 2002 A1
20020087371 Abendroth Jul 2002 A1
20020103653 Huxter Aug 2002 A1
20020103724 Huxter Aug 2002 A1
20020107820 Huxter Aug 2002 A1
20020111914 Terada et al. Aug 2002 A1
20020120475 Morimoto Aug 2002 A1
20020128915 Haseltine Sep 2002 A1
20020130065 Bloom Sep 2002 A1
20020138173 Barta et al. Sep 2002 A1
20020143670 Cushing et al. Oct 2002 A1
20020147919 Gentry Oct 2002 A1
20020156645 Hansen Oct 2002 A1
20020156846 Rawat et al. Oct 2002 A1
20020165729 Kuebert Nov 2002 A1
20020177922 Bloom Nov 2002 A1
20020178016 McLellan Nov 2002 A1
20020178074 Bloom Nov 2002 A1
20020184497 Gage et al. Dec 2002 A1
20030003936 Tighe Jan 2003 A1
20030023963 Birkholz et al. Jan 2003 A1
20030025590 Gokcebay et al. Feb 2003 A1
20030037009 Tobin et al. Feb 2003 A1
20030040931 De Mol Van Otterloo et al. Feb 2003 A1
20030040980 Nakajima et al. Feb 2003 A1
20030046173 Benjier et al. Mar 2003 A1
20030093180 Stevens May 2003 A1
20030097287 Franz et al. May 2003 A1
20030110170 Matsuoka Jun 2003 A1
20030114206 Timothy et al. Jun 2003 A1
20030160097 Steiner Aug 2003 A1
20030171996 Chen et al. Sep 2003 A1
20030193414 Jones Oct 2003 A1
20030195784 Smith, Jr. Oct 2003 A1
20030225625 Chew et al. Dec 2003 A1
20040015393 Fong et al. Jan 2004 A1
20040030604 Young Feb 2004 A1
20040039712 Tartal et al. Feb 2004 A1
20040044582 Chowdhary et al. Mar 2004 A1
20040073449 Yang Apr 2004 A1
20040073499 Martin et al. Apr 2004 A1
20040088225 Foth et al. May 2004 A1
20040093312 Cordery et al. May 2004 A1
20040117276 Kettler, III Jun 2004 A1
20040117278 Dutta et al. Jun 2004 A1
20040117326 Amato Jun 2004 A1
20040133446 Myrick et al. Jul 2004 A1
20040134690 Norris et al. Jul 2004 A1
20040143518 Siegel Jul 2004 A1
20040149822 Stevens Aug 2004 A1
20040149824 Miller et al. Aug 2004 A1
20040153370 Yang Aug 2004 A1
20040158351 Rivalto Aug 2004 A1
20040172260 Junger et al. Sep 2004 A1
20040181310 Stashluk, Jr. et al. Sep 2004 A1
20040199284 Hara Oct 2004 A1
20040199656 Pintsov Oct 2004 A1
20040211834 Fleckenstein et al. Oct 2004 A1
20040215480 Kadaba Oct 2004 A1
20040215588 Cornelius Oct 2004 A1
20040254802 Miller Dec 2004 A1
20040254811 Horstemeyer Dec 2004 A1
20040260470 Rast Dec 2004 A1
20050004877 McLellan et al. Jan 2005 A1
20050006470 Mrozik et al. Jan 2005 A1
20050027607 Pearson Feb 2005 A1
20050038758 Hilbush et al. Feb 2005 A1
20050060164 Eli Berl Illion Mar 2005 A1
20050060228 Woo Mar 2005 A1
20050061877 Stevens Mar 2005 A1
20050068178 Lee et al. Mar 2005 A1
20050071258 Kumakawa Mar 2005 A1
20050075989 Biasi et al. Apr 2005 A1
20050080635 Groff et al. Apr 2005 A1
20050080638 Maseruka Apr 2005 A1
20050104716 Simms et al. May 2005 A1
20050116033 Moore Jun 2005 A1
20050119786 Kadaba Jun 2005 A1
20050120003 Drury et al. Jun 2005 A1
20050131774 Huxter Jun 2005 A1
20050137901 Siegel Jun 2005 A1
20050138382 Hougaard et al. Jun 2005 A1
20050149372 Kite et al. Jul 2005 A1
20050216553 Mallonee et al. Sep 2005 A1
20050218222 Nark et al. Oct 2005 A1
20050234911 Hess et al. Oct 2005 A1
20050251402 Olsen et al. Nov 2005 A1
20060010037 Angert Jan 2006 A1
20060010077 Dohrmann et al. Jan 2006 A1
20060020366 Bloom Jan 2006 A1
20060020489 Rivalto Jan 2006 A1
20060041481 Stowe Feb 2006 A1
20060047610 Parkos et al. Mar 2006 A1
20060069601 Simon et al. Mar 2006 A1
20060085273 Mayer et al. Apr 2006 A1
20060097896 Jones May 2006 A1
20060149577 Stashluk et al. Jul 2006 A1
20060224512 Kurakata Oct 2006 A1
20060229895 Kodger Oct 2006 A1
20060235739 Levis et al. Oct 2006 A1
20060238334 Mangan et al. Oct 2006 A1
20060282277 Ng Dec 2006 A1
20060287870 Mayer et al. Dec 2006 A1
20070005452 Klingenberg et al. Jan 2007 A1
20070016538 Bielefeld et al. Jan 2007 A1
20070036117 Taube et al. Feb 2007 A1
20070047459 Kadaba Mar 2007 A1
20070062851 Schulz et al. Mar 2007 A1
20070078797 Won et al. Apr 2007 A1
20070083410 Hanna Apr 2007 A1
20070095904 Barta et al. May 2007 A1
20070124295 Forman et al. May 2007 A1
20070143281 Smirin et al. Jun 2007 A1
20070150533 Krause et al. Jun 2007 A1
20070156415 Foth et al. Jul 2007 A1
20070185598 Ortega Aug 2007 A1
20070192191 Neal et al. Aug 2007 A1
20070198290 Kinory et al. Aug 2007 A1
20070266081 Murchison et al. Nov 2007 A1
20080004928 Trellevik et al. Jan 2008 A1
20080004957 Hildreth et al. Jan 2008 A1
20080004967 Gillen Jan 2008 A1
20080004995 Klingenberg et al. Jan 2008 A1
20080040246 Fukamachi Feb 2008 A1
20080051995 Lokshin et al. Feb 2008 A1
20080061966 Nelson Mar 2008 A1
20080082346 Hoopes et al. Apr 2008 A1
20080109246 Russell May 2008 A1
20080121682 Grim et al. May 2008 A1
20080133261 Ray Jun 2008 A1
20080154781 Kumar Jun 2008 A1
20080172305 Estes et al. Jul 2008 A1
20080210749 Skaaksrud et al. Sep 2008 A1
20080221913 Cook et al. Sep 2008 A1
20080249830 Gilman et al. Oct 2008 A1
20080313018 Kamm, IV et al. Dec 2008 A1
20080319970 Garner et al. Dec 2008 A1
20080320092 Campbell et al. Dec 2008 A1
20090001153 Lim Jan 2009 A1
20090012802 Pinney Jan 2009 A1
20090043552 Tomlinson, Jr. et al. Feb 2009 A1
20090046892 Avant et al. Feb 2009 A1
20090063215 Heise et al. Mar 2009 A1
20090106124 Yang Apr 2009 A1
20090138730 Cook et al. May 2009 A1
20090146832 Ebert et al. Jun 2009 A1
20090164295 Sion Jun 2009 A1
20090173672 Avant et al. Jul 2009 A1
20090187489 Mallick et al. Jul 2009 A1
20090240597 Oswald Sep 2009 A1
20090259509 Landvater Oct 2009 A1
20090281929 Boitet et al. Nov 2009 A1
20090314835 Jackson Dec 2009 A1
20090319078 Jackson Dec 2009 A1
20090326971 Piccinini et al. Dec 2009 A1
20100004960 Frankenberg et al. Jan 2010 A1
20100011238 Nakamura et al. Jan 2010 A1
20100012769 Alber et al. Jan 2010 A1
20100049536 Quine et al. Feb 2010 A1
20100057592 Moir et al. Mar 2010 A1
20100057593 Moir et al. Mar 2010 A1
20100076903 Klingenberg et al. Mar 2010 A1
20100100497 Kuebert et al. Apr 2010 A1
20100114678 Axe et al. May 2010 A1
20100121689 Wallace et al. May 2010 A1
20100138281 Zhang et al. Jun 2010 A1
20100162149 Sheleheda et al. Jun 2010 A1
20100185565 Wade Jul 2010 A1
20100211444 Spear Aug 2010 A1
20100223127 Bettez et al. Sep 2010 A1
20100223134 Lunenfeld Sep 2010 A1
20100235290 Junger et al. Sep 2010 A1
20100250291 Walker et al. Sep 2010 A1
20100280955 Ross et al. Nov 2010 A1
20110004562 Hennessy et al. Jan 2011 A1
20110084162 Goossen et al. Apr 2011 A1
20110093361 Morales Apr 2011 A1
20110125665 Kadaba May 2011 A1
20110153513 Erie et al. Jun 2011 A1
20110191697 Sumner et al. Aug 2011 A1
20110246323 Mehta et al. Oct 2011 A1
20110270714 Myrick et al. Nov 2011 A1
20110287748 Angel et al. Nov 2011 A1
20110288896 Dewey, Jr. et al. Nov 2011 A1
20120016948 Sinha Jan 2012 A1
20120030124 Cronkright, II et al. Feb 2012 A1
20120030133 Rademaker Feb 2012 A1
20120047084 Naghshineh et al. Feb 2012 A1
20120047085 Naghshineh et al. Feb 2012 A1
20120062362 Rudduck et al. Mar 2012 A1
20120089532 Kuebert et al. Apr 2012 A1
20120095934 Klingenberg et al. Apr 2012 A1
20120130625 Srivastava May 2012 A1
20120130916 Neal et al. May 2012 A1
20120166320 Junger Jun 2012 A1
20120179622 Amato Jul 2012 A1
20120185363 Gilbert Jul 2012 A1
20120235786 Rudduck et al. Sep 2012 A1
20120246077 Skaaksrud et al. Sep 2012 A1
20120303539 Marcus et al. Nov 2012 A1
20120303541 Marcus et al. Nov 2012 A1
20120303542 Marcus et al. Nov 2012 A1
20120310853 Aldstadt Dec 2012 A1
20120330774 Sadot et al. Dec 2012 A1
20130006731 Cook et al. Jan 2013 A1
20130006885 Kuebert et al. Jan 2013 A1
20130013101 Bonnell et al. Jan 2013 A1
20130013102 Bonnell et al. Jan 2013 A1
20130013350 McCullough et al. Jan 2013 A1
20130016636 Berger et al. Jan 2013 A1
20130018894 Qiao Jan 2013 A1
20130018999 Merrill et al. Jan 2013 A1
20130024307 Fuerstenberg et al. Jan 2013 A1
20130054054 Tollenaere et al. Feb 2013 A1
20130061337 Zimberoff et al. Mar 2013 A1
20130073336 Heath Mar 2013 A1
20130073605 Fosburgh et al. Mar 2013 A1
20130088323 Ryan Apr 2013 A1
20130144428 Irwin et al. Jun 2013 A1
20130151419 Hitchcock et al. Jun 2013 A1
20130166067 Irwin et al. Jun 2013 A1
20130202185 Irwin, Jr. et al. Aug 2013 A1
20130238599 Burris Sep 2013 A1
20130238658 Burris Sep 2013 A1
20130246396 Clare et al. Sep 2013 A1
20130262311 Buhrmann et al. Oct 2013 A1
20130262336 Wan et al. Oct 2013 A1
20130268437 Desai et al. Oct 2013 A1
20130338822 Gibson, Jr. et al. Dec 2013 A1
20140034727 Hancock et al. Feb 2014 A1
20140035721 Heppe et al. Feb 2014 A1
20140052661 Shakes et al. Feb 2014 A1
20140081677 Craig et al. Mar 2014 A1
20140180959 Gillen et al. Jun 2014 A1
20140222711 Tibbs et al. Aug 2014 A1
20140236688 Minter et al. Aug 2014 A1
20140258098 Felix et al. Sep 2014 A1
20140278602 Lievens et al. Sep 2014 A1
20140278603 Lievens et al. Sep 2014 A1
20140278843 Lievens et al. Sep 2014 A1
20140279648 Whitehouse Sep 2014 A1
20140279650 Lievens et al. Sep 2014 A1
20140279654 Lievens et al. Sep 2014 A1
20140279658 Lievens et al. Sep 2014 A1
20140279663 Lievens et al. Sep 2014 A1
20140279664 Lievens et al. Sep 2014 A1
20140279665 Lievens et al. Sep 2014 A1
20140279666 Lievens et al. Sep 2014 A1
20140279667 Gillen Sep 2014 A1
20140330407 Corder et al. Nov 2014 A1
20150058163 Lenahan et al. Feb 2015 A1
20150106291 Robinson et al. Apr 2015 A1
20150106292 Robinson et al. Apr 2015 A1
20150106293 Robinson et al. Apr 2015 A1
20150106294 Robinson et al. Apr 2015 A1
20150106295 Robinson et al. Apr 2015 A1
20150106296 Robinson et al. Apr 2015 A1
20150120602 Huffman et al. Apr 2015 A1
20150138382 Mao et al. May 2015 A1
20150193731 Stevens et al. Jul 2015 A1
20160071051 Tibbs et al. Mar 2016 A1
20160140486 Tibbs et al. May 2016 A1
20160140487 Tibbs et al. May 2016 A1
20160148154 Tibbs et al. May 2016 A1
20160189466 Gibson et al. Jun 2016 A1
20180005184 Schenken Jan 2018 A1
20180025319 Lievens et al. Jan 2018 A1
20180060800 Robinson Mar 2018 A1
20180060812 Robinson et al. Mar 2018 A1
20180253688 Schenken et al. Sep 2018 A1
20190172011 Robinson et al. Jun 2019 A1
Foreign Referenced Citations (89)
Number Date Country
2893502 Nov 2004 CA
2551885 Aug 2006 CA
1317758 Oct 2001 CN
1571975 Jan 2005 CN
1666214 Sep 2005 CN
1795461 Jun 2006 CN
101203873 Jun 2008 CN
101329752 Nov 2008 CN
101491051 Jul 2009 CN
101971201 Feb 2011 CN
102609783 Jul 2012 CN
102930655 Feb 2013 CN
202720725 Feb 2013 CN
1152356 Nov 2001 EP
1365198 Nov 2003 EP
2469291 Jun 2012 EP
S62121108 Jul 1987 JP
5-211684 Aug 1993 JP
H10207956 Aug 1998 JP
11139540 May 1999 JP
H11151154 Jun 1999 JP
2000339373 Dec 2000 JP
200114393 Jan 2001 JP
200122678 Jan 2001 JP
2001-282974 Oct 2001 JP
2001291027 Oct 2001 JP
2001338030 Dec 2001 JP
200256307 Feb 2002 JP
2002042008 Feb 2002 JP
2002092505 Mar 2002 JP
2002-109409 Apr 2002 JP
2002157541 May 2002 JP
2002259553 Sep 2002 JP
2002288562 Oct 2002 JP
2003196354 Jul 2003 JP
2003263599 Sep 2003 JP
2003321124 Nov 2003 JP
2004-030159 Jan 2004 JP
2004280468 Oct 2004 JP
2004338824 Dec 2004 JP
2005-43974 Feb 2005 JP
2006-512635 Apr 2006 JP
2008-542886 Jun 2006 JP
2006277199 Oct 2006 JP
2007153618 Jun 2007 JP
2008303069 Dec 2008 JP
2010128535 Jun 2010 JP
2011118611 Jun 2011 JP
2012138000 Jul 2012 JP
2001-0093768 Mar 2001 KR
0019170 Apr 2000 WO
0019171 Apr 2000 WO
0030014 May 2000 WO
0046726 Aug 2000 WO
0046728 Aug 2000 WO
0052422 Sep 2000 WO
0108071 Feb 2001 WO
0116889 Mar 2001 WO
0120423 Mar 2001 WO
0129778 Apr 2001 WO
0135344 May 2001 WO
0139031 May 2001 WO
0165451 Sep 2001 WO
0165454 Sep 2001 WO
0165523 Sep 2001 WO
0165524 Sep 2001 WO
0167344 Sep 2001 WO
0172109 Oct 2001 WO
0184359 Nov 2001 WO
0188831 Nov 2001 WO
0197101 Dec 2001 WO
0207104 Jan 2002 WO
0217045 Feb 2002 WO
02052378 Jul 2002 WO
02073369 Sep 2002 WO
WO02073369 Sep 2002 WO
02080436 Oct 2002 WO
WO02080436 Oct 2002 WO
03023688 Mar 2003 WO
03040979 May 2003 WO
2004015518 Feb 2004 WO
2004042523 May 2004 WO
2007055769 May 2007 WO
2010123611 Oct 2010 WO
2011074500 Jun 2011 WO
2012129529 Sep 2012 WO
2013106940 Jul 2013 WO
2014031691 Feb 2014 WO
2014164853 Oct 2014 WO
Non-Patent Literature Citations (56)
Entry
Notice of Allowance received for Singapore Patent Application No. 11201507536Q, dated Jul. 27, 2017, 6 pages.
Office Action received for Chinese Patent Application No. 201480026776.9, dated Jul. 4, 2017, 9 Pages (Official Copy Only) (See attached Communication 37 CFR § 1.98(a) (3)).
Office Action received for Japanese Patent Application No. 2016-501276, dated Jun. 27, 2017, 5 pages (Official Copy Only) (See attached Communication 37 CFR § 1.98(a) (3)).
Office Action received for Japanese Patent Application No. 2016-501304, dated Aug. 29, 2017, 4 Pages (Official Copy Only) (See attached Communication 37 CFR § 1.98(a) (3)).
Office Action received for Japanese Patent Application No. 2017-174116, dated Aug. 14, 2018, 3 Pages (Official Copy Only) (See attached Communication 37 CFR § 1.98(a) (3)).
PCT International Preliminary Report on Patentability, dated Apr. 28, 2016, from corresponding International Application Serial No. PCT/US2014/060482.
PCT International Search Report, dated May 2, 2016, from corresponding International Application Serial No. PCT/US2015/0060757.
Written Opinion of the International Searching Authority, dated May 2, 2016, from corresponding International Application Serial No. PCT/US2015/0060757.
Non-Final Office Action received for U.S. Appl. No. 14/514,228, dated Nov. 30, 2018, 45 pages.
Office Action received for Canadian Patent Application No. 2,905,338, dated Oct. 2, 2018, 8 pages.
McNamara, Paul, “‘Doorman’ kiosk accepts package deliveries when you're not home”, Network world, Available at: <https://www.networkworld.com/article/2348365/data-center/-doorman-kiosk-accepts-package-deliveries-when-you-re-not-home.html>, Aug. 8, 2007, 4 pages.
Non-Final Office Action received for U.S. Appl. No. 14/942,757, dated Jul. 19, 2018, 25 pages.
Notice of Allowance received for Singapore Patent Application No. 11201507531R, dated Jul. 19, 2018, 7 pages.
Final Office Action received for U.S. Appl. No. 14/514,000, dated Feb. 12, 2018, 43 pages.
Final Office Action received for U.S. Appl. No. 14/514,155, dated Oct. 20, 2016, 18 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/060525, completed on Dec. 10, 2015, 12 pages.
Non-Final Office Action received for U.S. Appl. No. 14/514,155, dated Jun. 11, 2018, 23 pages.
Non-Final Office Action received for U.S. Appl. No. 14/561,041, dated Mar. 30, 2018, 57 pages.
Non-Final Office Action received for U.S. Appl. No. 14/935,257, dated Apr. 20, 2017, 16 pages.
Non-Final Office Action received for U.S. Appl. No. 14/200,681, dated Jul. 25, 2016, 17 pages.
Office Action received for European Patent Application No. 14714534.6, dated May 26, 2017, 5 pages.
Office Action received for Japanese Patent Application No. 2016-501276, dated Nov. 1, 2016, 8 pages (4 pages of English Translation and 4 pages of Official Copy).
Office Action received for Japanese Patent Application No. 2016-501288, dated Nov. 1, 2016, 7 pages (3 pages of English Translation and 4 pages of Official copy).
Search Report and Written Opinion received for Singapore Patent Application No. 11201507531R, dated Jun. 27, 2016, 11 pages.
Search Report and Written Opinion received for Singapore Patent Application No. 11201507549S, dated May 31, 2016, 11 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 14854011.5, mailed on Apr. 3, 2018, 13 pages.
Pender, Lee, Hard Times Are the Best Times, Magazine, Aug. 15, 2001 (Retrieved on Apr. 25, 2003), p. 3, Paragraph 3, Retrieved from the Internet: <URL:http://www.cio.com/archive/081501/besttimes_contenl.html>.
Raco Industries, “Increase Delivery Visibility and Simplify Your Process,” retrieved from <http://www.racointeractive.com/media/834/raco_interactive-pd.pdf>, on Sep. 25, 2013, 2 pages.
SEP leads €26 million funding round for Kiala, http://www.sep.co.uklnews/story/sep-leads-e26-million-funding-round-for-kiala-2/, Nov. 30, 2007, SEP Scottish Equity Partners.
Van Huzien, Gordon, Messaging: The Transport Part ofThe XML Puzzle, Article, Jul. 2000 (Retrieved from the Internet Apr. 25, 2003: <URL:http:I/www-1 06.ibm.com/developerworks/library/xml-messaging/>.
ASP V16-System Walker List Works Manual (relevant part); p. 88, line 5, 3.4 Start up and termination of Lis! Works writer; one page.
Brewin, Bob and Rosencrance, Linda, Follow That Package!, Article, Mar. 19, 2001 (Retrieved from the Internet Apr. 25, 2003), p. 1-p. 5, Retrieved from the Internet: URL:http://www.computerworld.com./printth is/200 1/0,4814,58696, DO .him l, Computer World.
Caminiti et al., United Parcel Service Introduces Advanced Label Imaging System, Published by Business Wire on Nov. 29, 1989, Section 1, p. 1, Downloaded from the Internet on Sep. 19, 2005, 2 Pages.
De Marco, Donna, E-Tail Presents Can Be Tougher to Send Back Than Order, Journal, Dec. 28, 1999, Downloaded from the Internet on Oct. 3, 2002, Accession No. 08891512, Knight-Ridder/Tribune Business News, The Dialog Corporation, United States.
Descartes, Scheduling Software Helps Webvan Meet 3D-Minute Delivery Window, www.stores.org, Jul. 2000.
El Portal Del Transporte, Fed Ex Insight Empowers Customers with Enhanced Shipment Visibility and Control, Article, Apr. 11, 2001 (Retrieved on Apr. 25, 2003), p. 9, Paragraph 4—p. 10, Line 7, Retrieved from the Internet: <U RL:http://www. transportando. nel/newsabri 1_ completa .him>.
Fed Ex, “RPS Adds Automated Package Pick-Up to Redesigned Web Site,” www.fedex.com/us/aboul/gound/www.fedex.com/us/aboul/gound/ pressreleases/pressrelease111198.hlml?link=4, retrieved Sep. 10, 2003.
Fedex, “Fed Ex Mobile Ship”, retrieved from <hllp:l/www.fedex.com/us/mobile/label.hlml, redirected to http://mobilesolutions.fedex.com/shipping-label.hlml > on Sep. 25, 2013, 2 pages.
Frontline Solutions, Fed Ex Improves Internal, External Operations, Article, Apr. 5, 2001 (Retrieved from the Internet Apr. 25, 2003), p. 1 (last line) through p. 2, Paragraph 9, Retrieved from the Internet: <URL:http://www.frontlinemagazine.com/art_lh/o4052001.hlx>, Fairfax, Virginia and Memphis, Tennessee.
Gao, Huiji, et al., Cyber-Physical-Social Systems: Harnessing the Crowdsourcing Power of Social Media for Disaster Relief, IEEE Intelligent Systems, Copyright 2011, pp. 10-14, IEEE Computer Society.
Harrington, Lisa, The U.S. Postal Service Gets Serious About Serving Business in the New Economy, Journal, May 2000, Downloaded from the Internet on Oct. 3, 2002, p. 2, vol. 41, No. 5, Accession No. 01167257, Penton Publishing, Inc., United States of America.
Henderson, Timothy, Buy.com Boosts Returns Process Efficiency With New Solution, Periodical, Nov. 2000, Downloaded from the Internet on Oct. 3, 2002, pp. 72-76, vol. 82n11, Accession No. 02102731, ProQuest Info&Learning, United States of America.
IPventure, “Schedule Distribution Routes and Timeslots,” http://www.ipventure.com/onlineorder/distribution.php, retrieved on Apr. 16, 2008.
Kihon Kara Jissen Made Business Seikou No Tameno Kanpeki Guide—How to E-Commerce (relevant part); p. 60; one page.
Many Happy Returns—UPS Unvels Advanced Outline Returns Solution, Journal, Sep. 20, 2000, Downloaded from the Internet on Oct. 3, 2002, Accession No. 12921102, Business Wire, United States of America.
Outlook 2000 Handbook First Edition (relevant part); p. 95, last 9 lines; one page.
Lindsay, Bruce R., “Congressional Research Service, Social Media and Disasters: Current Uses, Future Options, and Policy Considerations,” CRS Report for Congress, Sep. 6, 2011, 10 pages, Congressional Research Service.
Notice of Allowance received for U.S. Appl. No. 14/200,432, dated Feb. 7, 2019, 22 pages.
Final Office Action received for U.S. Appl. No. 14/942,757, dated Mar. 21, 2019, 26 pages.
Office Action received for Chinese Patent Application No. 201480067863.9, dated Dec. 24, 2018, 39 pages (15 pages of English Translation and 24 pages of Official Copy).
Non-Final Office Action received for U.S. Appl. No. 14/514,155, dated Sep. 28, 2018, 29 pages.
Notice of Allowance received for U.S. Appl. No. 14/514,276, dated Oct. 3, 2018, 11 pages.
Office Action received for Chinese Patent Application No. 201480026789.6, dated Jul. 23, 2018, 17 pages (Official Copy Only) (See attached Communication 37 CFR § 1.98(a) (3)).
Chung et al., “Optimal Replenishment Policies for EOQ Inventory Model with Limited Storage Capacity Under Permissible Delay in Payments”, Opsearch 41.1, 2004, 23 pages.
Notice of Allowance received for U.S. Appl. No. 14/170,298, dated May 22, 2019, 10 pages.
Final Office Action received for U.S. Appl. No. 14/514,155, dated Jun. 21, 2019, 28 pages.
Related Publications (1)
Number Date Country
20160140487 A1 May 2016 US
Provisional Applications (1)
Number Date Country
62080130 Nov 2014 US