US20110307361A1 - Enhanced payments for shipping - Google Patents
Enhanced payments for shipping Download PDFInfo
- Publication number
- US20110307361A1 US20110307361A1 US12/813,998 US81399810A US2011307361A1 US 20110307361 A1 US20110307361 A1 US 20110307361A1 US 81399810 A US81399810 A US 81399810A US 2011307361 A1 US2011307361 A1 US 2011307361A1
- Authority
- US
- United States
- Prior art keywords
- parcel
- account
- shipment
- authorization code
- shipping
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000013475 authorization Methods 0.000 claims abstract description 81
- 238000000034 method Methods 0.000 claims abstract description 48
- 238000004590 computer program Methods 0.000 claims abstract description 34
- 230000000977 initiatory effect Effects 0.000 claims abstract description 5
- 230000004044 response Effects 0.000 claims description 43
- 238000012011 method of payment Methods 0.000 claims description 34
- 238000003860 storage Methods 0.000 claims description 19
- 238000004891 communication Methods 0.000 claims description 16
- 238000012545 processing Methods 0.000 description 13
- 238000013459 approach Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 12
- 230000000875 corresponding effect Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 238000003384 imaging method Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 2
- 230000002596 correlated effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012015 optical character recognition Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 239000000853 adhesive Substances 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000000383 hazardous chemical Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
- 238000005303 weighing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/083—Shipping
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/083—Shipping
- G06Q10/0833—Tracking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/18—Payment architectures involving self-service terminals [SST], vending machines, kiosks or multimedia terminals
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
- G06Q20/202—Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/327—Short range or proximity payments by means of M-devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/385—Payment protocols; Details thereof using an alias or single-use codes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/018—Certifying business or products
- G06Q30/0185—Product, service or business identity fraud
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
Definitions
- embodiments of the present invention provide systems, methods, apparatus, and computer program products for the shipment of parcels.
- a method for shipping a parcel comprises (1) receiving a first message transmitted from a user device requesting shipment of a parcel; (2) in response to receiving the first message, identifying an account identifier based at least in part on the first message, wherein the account identifier corresponds to an account associated with a user of the user device; (3) determining whether the account is valid; and (4) in response to a determination that the account is valid, generating and transmitting a second message to the user device, wherein the second message comprises an authorization code.
- the method may also comprise (5) receiving shipping information that is generated as the parcel is transported within a carrier's transportation and logistics network, wherein the shipping information comprises a tracking identifier and the authorization code; (6) in response to receiving the shipping information, determining whether the parcel is approved for shipment based at least in part on the authorization code; (7) in response to a determination that the parcel is approved for shipment, storing at least a portion of the shipment information in association with the tracking identifier, the authorization code, and the account identifier; (8) electronically determining shipping charges for shipment of the parcel; and (9) electronically charging the shipping charges to the account.
- the method comprises (1) receiving a first message transmitted from a user device requesting shipment of a parcel; (2) in response to receiving the first message, identifying an account identifier based at least in part on the first message, wherein the account identifier corresponds to an account associated with a user of the user device; and (3) determining whether the account is valid.
- the method also comprises (4) in response to a determination that the account is valid, generating and transmitting a second message to the user device, wherein the second message comprises an authorization code; (5) receiving shipping information that is generated as the parcel is transported within a carrier's transportation and logistics network, wherein the shipping information comprises a tracking identifier and the authorization code; and (6) electronically charging shipping charges to the account.
- a computer program product for shipping a parcel may comprise at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising executable portions configured to (1) receive a first message transmitted from a user device requesting shipment of a parcel; (2) in response to receiving the first message, identify an account identifier based at least in part on the first message, wherein the account identifier corresponds to an account associated with a user of the user device; (3) determine whether the account is valid; and (4) in response to a determination that the account is valid, generate and transmit a second message to the user device, wherein the second message comprises an authorization code.
- the computer-readable program code portions may also comprise executable portions configured to (5) receive shipping information that is generated as the parcel is transported within a carrier's transportation and logistics network, wherein the shipping information comprises a tracking identifier and the authorization code; (6) in response to receiving the shipping information, determine whether the parcel is approved for shipment based at least in part on the authorization code; (7) in response to a determination that the parcel is approved for shipment, store at least a portion of the shipment information in association with the tracking identifier, the authorization code, and the account identifier; (8) determine shipping charges for shipment of the parcel; and (9) charge the shipping charges to the account.
- a computer program product for shipping a parcel may comprise at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising executable portions configured to (1) receive a first message transmitted from a user device requesting shipment of a parcel; (2) in response to receiving the first message, identify an account identifier based at least in part on the first message, wherein the account identifier corresponds to an account associated with a user of the user device; and (3) determine whether the account is valid.
- the computer-readable program code portions may also comprise executable portions configured to (4) in response to a determination that the account is valid, generate and transmit a second message to the user device, wherein the second message comprises an authorization code; (5) receive shipping information that is generated as the parcel is transported within a carrier's transportation and logistics network, wherein the shipping information comprises a tracking identifier and the authorization code; and (6) charge shipping charges to the account.
- a method for shipping a parcel comprises (1) receiving input from a user requesting shipment of a parcel; (2) causing display of a request for input identifying a method of payment for shipment of the parcel; (3) in response to causing display of the request for input of the method of payment for shipment of the parcel, receiving input (a) identifying an account for wireless services as the method of payment and (b) a phone number associated with the account for wireless services; and (4) determining whether the account for wireless services is valid.
- the method also comprises (5) in response to a determination that the account for wireless services is valid, generating and transmitting a message to a mobile device associated with the phone number, wherein the message comprises an authorization code; (6) causing display of a request for input of the authorization code transmitted to the mobile device; and (7) receiving input from the user identifying the authorization code.
- the method comprises (1) receiving input from a user requesting shipment of a parcel; (2) causing display of a request for input identifying a method of payment for shipment of the parcel; (3) in response causing display of the request for input of the method of payment for shipment of the parcel, receiving input identifying an account for wireless services as the method of payment; (4) in response to receiving input identifying the account for wireless services as the method of payment, automatically initiating communication with a mobile device associated with the account for wireless services; and (5) determining whether the account for wireless services is valid.
- a computer program product for shipping a parcel may comprise at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising executable portions configured to (1) receive input from a user requesting shipment of a parcel; (2) cause display of a request for input identifying a method of payment for shipment of the parcel; (3) in response to causing display of the request for input of the method of payment for shipment of the parcel, receive input identifying (a) an account for wireless services as the method of payment and (b) a phone number associated with the account for wireless services; and (4) determine whether the account for wireless services is valid.
- the computer-readable program code portions may also comprise executable portions configured to (5) in response to a determination that the account for wireless services is valid, generate and transmit a message to a mobile device associated with the phone number, wherein the message comprises an authorization code; (6) cause display of a request for input of the authorization code transmitted to the mobile device; and (7) receive input from the user identifying the authorization code.
- the computer program product may comprise at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising executable portions configured to (1) receive input from a user requesting shipment of a parcel; (2) cause display of a request for input identifying a method of payment for shipment of the parcel; (3) in response causing display of the request for input of the method of payment for shipment of the parcel, receive input identifying an account for wireless services as the method of payment; (4) in response to receiving input identifying the account for wireless services as the method of payment, automatically initiate communication with a mobile device associated with the account for wireless services; and (5) determine whether the account for wireless services is valid.
- FIG. 1 is an overview of a system that can be used to practice various embodiments of the present invention.
- FIG. 2 is an exemplary schematic diagram of a carrier system according to one embodiment of the present invention.
- FIG. 3 is an exemplary schematic diagram of a mobile device according to one embodiment of the present invention.
- FIGS. 4-5 are flowcharts illustrating operations and processes that can be used in accordance with various embodiments of the present invention.
- FIG. 6 is an exemplary drop-box according to one embodiment of the present invention.
- FIG. 7 shows exemplary input/output that can be produced via a mobile device according to one embodiment of the present invention.
- various embodiments may be implemented in various ways, including as methods, apparatus, systems, or computer program products. Accordingly, various embodiments may take the form of an entirely hardware embodiment or an embodiment in which a processor is programmed to perform certain steps. Furthermore, various implementations may take the form of a computer program product on a computer-readable storage medium having computer-readable program instructions embodied in the storage medium. Any suitable computer-readable storage medium may be utilized including hard disks, CD-ROMs, optical storage devices, or magnetic storage devices.
- 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 including computer-readable instructions for implementing the functionality 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 operations for implementing the functions specified in the flowchart block or blocks.
- blocks of the block diagrams and flowchart illustrations support various combinations for performing the specified functions, combinations of operations 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 operations, or combinations of special purpose hardware and computer instructions.
- FIG. 1 provides an illustration of a system that can be used in conjunction with various embodiments of the present invention.
- the system may include one or more carrier systems 100 , one or more networks 105 , one or more mobile devices 110 , one or more user computing devices 115 , and one or more kiosks 120 .
- Each of the components of the system may be in electronic communication with, for example, one another over the same or different wireless or wired networks including, for example, a wired or wireless Personal Area Network (“PAN”), Local Area Network (“LAN”), Metropolitan Area Network (“MAN”), Wide Area Network (“WAN”), or the like.
- PAN Personal Area Network
- LAN Local Area Network
- MAN Metropolitan Area Network
- WAN Wide Area Network
- FIG. 1 illustrates certain system entities as separate, standalone entities, the various embodiments are not limited to this particular architecture.
- FIG. 2 provides a schematic of a carrier system 100 according to one embodiment of the present invention.
- the term “system” may refer to, for example, any computer, computing device, mobile phone, desktop, notebook or laptop, distributed system, server, blade, gateway, switch, processing device, or combination of processing devices adapted to perform the functions described herein.
- the carrier system 100 includes a processor 205 that communicates with other elements within the carrier system 100 via a system interface or bus 261 .
- the processor 205 may be embodied in a number of different ways.
- the processor 205 may be embodied as a processing element, a coprocessor, a controller or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (“ASIC”), a field programmable gate array (“FPGA”), a hardware accelerator, or the like.
- ASIC application specific integrated circuit
- FPGA field programmable gate array
- the processor 205 may be configured to execute instructions stored in the device memory or otherwise accessible to the processor 205 . As such, whether configured by hardware or software methods, or by a combination thereof, the processor 205 may represent an entity capable of performing operations according to embodiments of the present invention when configured accordingly.
- a display device/input device 264 for receiving and displaying data may also be included in the carrier system 100 . This display device/input device 264 may be, for example, a keyboard or pointing device that is used in combination with a monitor.
- the carrier system 100 further includes memory 263 , which may include both read only memory (“ROM”) 265 and random access memory (“RAM”) 267 .
- the carrier system's ROM 265 may be used to store a basic input/output system (“BIOS”) 226 containing the basic routines that help to transfer information to the different elements within the carrier system 100 .
- BIOS basic input/output system
- the carrier system 100 includes at least one storage device 268 , such as a hard disk drive, a CD drive, and/or an optical disk drive for storing information on various computer-readable media.
- the storage device(s) 268 and its associated computer-readable media may provide nonvolatile storage.
- the computer-readable media described above could be replaced by any other type of computer-readable media, such as embedded or removable multimedia memory cards (“MMCs”), secure digital (“SD”) memory cards, Memory Sticks, electrically erasable programmable read-only memory (“EEPROM”), flash memory, hard disk, or the like.
- MMCs embedded or removable multimedia memory cards
- SD secure digital
- EEPROM electrically erasable programmable read-only memory
- flash memory hard disk, or the like.
- each of these storage devices 268 may be connected to the system bus 261 by an appropriate interface.
- program modules may be stored by the various storage devices 268 and/or within RAM 267 .
- Such program modules may include an operating system 280 , a billing module 270 , a tracking module 260 , and an authorization module 250 .
- These modules may control certain aspects of the operation of the carrier system 100 with the assistance of the processor 205 and operating system 280 —although their functionality need not be modularized.
- the carrier system 100 may store or be connected to one or more databases (e.g., database 240 ) with one or more tables stored therein.
- a network interface 274 for interfacing with various computing entities.
- This communication may be via the same or different wired or wireless networks (or a combination of wired and wireless networks), as discussed above.
- the communication may be executed using a wired data transmission protocol, such as fiber distributed data interface (“FDDI”), digital subscriber line (“DSL”), Ethernet, asynchronous transfer mode (“ATM”), frame relay, data over cable service interface specification (“DOCSIS”), or any other wired transmission protocol.
- the carrier system 100 may be configured to communicate via wireless external communication networks using any of a variety of protocols, such as 802.11, general packet radio service (“GPRS”), wideband code division multiple access (“W-CDMA”), or any other wireless protocol.
- the carrier system 100 may be capable of sending and receiving text messages and/or instant messages.
- one or more of the carrier system's 100 components may be located remotely from other carrier system 100 components. Furthermore, one or more of the components may be combined and additional components performing functions described herein may be included in the carrier system 100 .
- FIG. 3 provides an illustrative schematic representative of a mobile device 110 that can be used in conjunction with the embodiments of the present invention.
- the mobile device 110 can include an antenna 312 , a transmitter 304 , a receiver 306 , and a processing device 308 (e.g., a processor, controller, and/or the like) that provides signals to and receives signals from the transmitter 304 and receiver 306 , respectively.
- a processing device 308 e.g., a processor, controller, and/or the like
- the signals provided to and received from the transmitter 304 and the receiver 306 , respectively, may include signaling information in accordance with an air interface standard of applicable wireless systems.
- the mobile device 110 may be capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. More particularly, the mobile device 110 may operate in accordance with any of a number of second-generation (“2G”) communication protocols, third-generation (“3G”) communication protocols, fourth-generation (“4G”) communication protocols, and/or the like. Further, for example, the mobile device 110 may operate in accordance with any of a number of different wireless networking techniques, including Bluetooth, IEEE 802.11 (“Wi-Fi”), 802.16 (“WiMAX”), ultra wideband (“UWB”), and/or the like.
- Wi-Fi IEEE 802.11
- WiMAX 802.16
- UWB ultra wideband
- the mobile device 110 can communicate with the carrier system 100 and/or various other entities (e.g., user computing devices 110 or telephones 120 ).
- the mobile device 110 can also download changes, add-ons, and updates, for instance, to its firmware, software (e.g., including modules), and operating system.
- the mobile device 110 may also comprise a user interface (that can include a display 316 coupled to a processing device 308 ) and/or a user input interface (coupled to the processing device 308 ).
- the user input interface can comprise any of a number of devices allowing the mobile device 110 to receive data, such as a keypad 318 , a touch display, voice or motion interfaces, or other input device.
- the keypad 318 can include the conventional numeric (0-9) and related keys (#, *), and other keys used for operating the mobile device 110 and may include a full set of alphabetic keys or set of keys that may be activated to provide a full set of alphanumeric keys.
- the user input interface can be used, for example, to activate or deactivate certain functions, such as screen savers and/or sleep modes.
- the mobile device 110 may also include a battery, such as a vibrating battery pack, for powering the various circuits that are required to operate the mobile device 110 , as well as optionally providing mechanical vibration as a detectable output.
- the mobile device 110 can also include volatile memory 322 and/or non-volatile memory 324 , which can be embedded and/or may be removable.
- the non-volatile memory may be embedded or removable multimedia memory cards (“MMCs”), secure digital (“SD”) memory cards, Memory Sticks, EEPROM, flash memory, hard disk, or the like.
- MMCs multimedia memory cards
- SD secure digital
- EEPROM electrically erasable programmable read-only memory
- flash memory hard disk, or the like.
- the memory can store any of a number of pieces or amount of information and data used by the mobile device 110 to implement the functions of the mobile device 110 .
- the memory can also store content, such as computer program code for an application and/or other computer programs.
- the system may include a kiosk 120 .
- the kiosk 120 may include one or more components that are functionally similar to those of the carrier system 100 .
- a kiosk 120 may include: (1) a processor that communicates with elements via a system interface or bus; (2) a display device/input device; (3) memory including both ROM and RAM; (4) a storage device; (5) a network interface (including near field communication capabilities such as Bluetooth and capabilities for sending and receiving text messages and/or instant messages); (6) weighing mechanisms, such as scales; and/or (7) imaging devices.
- a network interface including near field communication capabilities such as Bluetooth and capabilities for sending and receiving text messages and/or instant messages
- (6) weighing mechanisms, such as scales and/or (7) imaging devices.
- the user computing devices 115 may each include one or more components that are functionally similar to those of the carrier system 100 .
- each user computing device 115 may include: (1) a processor that communicates with other elements via a system interface or bus; (2) a display device/input device; (3) memory including both ROM and RAM; (4) a storage device; and (5) a network interface.
- These architectures are provided for exemplary purposes only and are not limiting to the various embodiments.
- the term “computing device” is used generically to refer to any computer, mobile phone, computing device, desktop, notebook or laptop, distributed system, server, gateway, switch, or other processing device adapted to perform the functions described herein.
- FIGS. 4-5 provide flowcharts illustrating operations that may be performed for shipping parcels.
- FIG. 6 is an exemplary drop-box 600 at which parcels can be dropped off for a carrier (e.g., United Parcel Service of America, Inc.).
- FIG. 7 shows exemplary input/output that can be produced via a mobile device 110 .
- a carrier e.g., United Parcel Service of America, Inc.
- customers/users can use electronic messages to initiate shipment of and payment for shipping a parcel.
- a customer/user can use, for example, a drop-box 600 (such as the one shown in FIG. 6 ) to initiate shipment of a parcel (e.g., envelope, bag, package, bundled item, box with information pre-printed thereon, and/or the like) by a carrier (e.g., United Parcel Service of America, Inc.).
- a carrier e.g., United Parcel Service of America, Inc.
- the user can retrieve a shipping form (or a box or envelope with information pre-printed thereon) that may be stored proximate the drop-box 600 (or other shipping location) and fill out the shipping form (or box or envelope with information pre-printed thereon) with shipping information.
- the shipping information may include information such as (a) the consignor's name, address, phone number, and charge card number (or a portion thereof), (b) the contents, weight, and dimensions of the parcel, (c) the consignee's name, address, and phone number, (d) the class of service of the parcel (e.g., Ground, Next Day Air, etc.), and/or (e) a variety of other information.
- the shipping form (or box or envelope with information pre-printed thereon) may also include a unique, pre-printed tracking number.
- the tracking number may be, for example, a progressive number (“PRO number”), a purchase order number, and/or a set of alphanumeric characters (e.g., “1Z23456789”).
- the tracking number may be used by the carrier to identify and track the parcel as it travels through the carrier's transportation and logistics network.
- the shipping form may have a self-adhesive portion, for example, that can be used to adhere the shipping form to the parcel or adhere a label portion of the shipping form to the parcel.
- the customer/user can initiate shipment of the parcel with carrier.
- the customer/user may send a message (e.g., a first message) via a user device (e.g., a mobile device 110 or a user computing device 115 ) to the carrier.
- a user device e.g., a mobile device 110 or a user computing device 115
- the shipping form, drop-box 600 , box, or envelope may indicate that to initiate shipment of a parcel, a text message should be sent to 555-555-5555 with the tracking number printed on the shipping form as the body of the message.
- the customer/user sends a text message to 555-555-5555 with 1Z23456789 as the body of the message.
- the message may be any type of message, such as a text message, an instant message, an email message, and/or the like.
- the message may include a variety of shipping information, such as the pre-printed tracking number listed on the shipping form, a charge card number (or a portion thereof), and/or a carrier account number (or a portion thereof).
- a carrier entity e.g., a carrier system 100
- can receive the first message (e.g., text message) sent from the user device (e.g., mobile device 110 or user computing device 115 ) requesting shipment of the parcel.
- the carrier system 100 can identify an account identifier based at least in part on the first message.
- the account identifier may correspond to an account associated with the customer/user (Block 405 ).
- the account identifier may be, for example, a phone number of the mobile device 110 from which the first message originates, the phone number associated with an application executing on a user computing device 115 from which the first message originates, a credit card number (or a portion thereof) within the body of the first message, and/or a carrier account number (or a portion thereof) within the body of the first message.
- the account corresponding to the account identifier may be (a) an account for wireless services (e.g., phone and/or data services), (b) an account for a charge card, (c) a shipping account with the carrier, and/or (d) a variety of other accounts.
- the carrier system 100 can determine whether the account is valid. Determining whether the account is valid may include a variety of techniques and/or approaches. For example, in one embodiment, the carrier system 100 determines whether the account associated with the phone number is valid by electronically communicating with the wireless services provider to determine whether the account is active, in good standing, and/or available for mobile payments. For instance, a phone number in a family plan may be blocked for mobile payments via parental controls provided by the wireless services provider. Similarly, the wireless services provider may block messages to certain prefixes, such as 900 numbers. In another embodiment, the carrier system 100 may determine whether the carrier has “blacklisted” the phone number, for example, corresponding to the account. In another embodiment, the carrier system 100 may determine whether the account corresponding to the charge card number is valid by determining whether the charge card account is active and in good standing.
- the carrier system 100 can execute various other validation/confirmation techniques and/or approaches. For example, the carrier system 100 can determine whether the tracking number in the body of the first message has been used previously. Or, the carrier system 100 can access (a) the transaction history of the customer's/user's interactions with the carrier and/or (b) any customer/user configured parameters. For example, a customer/user can register mobile phone numbers with carrier (e.g., via the carrier's website) to configure usage parameters.
- the usage parameters may, for example, (a) limit a phone number to one shipment per day, (b) not allow for international shipments using the phone number, and/or (c) limit the mobile payments for shipping to $100 per day.
- a limit a phone number to one shipment per day
- b not allow for international shipments using the phone number
- c limit the mobile payments for shipping to $100 per day.
- the carrier system 100 in response to a determination that the account is invalid, can generate and transmit a message (e.g., a second message) to the user device (e.g., mobile device 110 or user computing device 115 ).
- a message e.g., a second message
- the second message may be any type of message, such as a text message, an instant message, an email message, and/or the like.
- the second message may indicate that the customer/user cannot use the selected method of payment for shipping the parcel.
- the carrier system 100 in response to a determination that the account is valid, can generate and transmit a message (e.g., a second message) to the user device (e.g., mobile device 110 or user computing device 115 ).
- the second message may be any type of message, such as a text message, an instant message, an email message, and/or the like.
- the second message may comprise an authorization code for shipment of the parcel.
- the authorization code may be, for example, an alphanumeric code (e.g., “A254”) that has been correlated with the tracking number and/or the shipping information provided by the customer/user.
- the authorization code may also be associated with various predefined parameters.
- the authorization code may be associated with predefined parameters that define (a) a time period in which the authorization code is valid and/or (b) the number of times the authorization code can be used for shipments. For instance, the authorization code may only be valid for a single shipment. Similarly, the authorization code may be valid for a certain period of time (e.g., 7 days) after issuance. As will be recognized, a variety of other approaches and techniques may be used.
- the user device e.g., mobile device 110 or user computing device 115
- the user device can cause display of the second message to the customer/user, as shown in FIG. 7 .
- the customer/user can write the authorization code on the parcel, label, or shipping form, for example.
- the customer/user can then deliver the parcel to a drop-box 600 or other carrier location/facility.
- the customer/user may request that a carrier vehicle be dispatched to pick up the parcel from the customer/user.
- the carrier Upon receipt of the parcel, the carrier can use the shipping information and/or authorization code in transporting the parcel through the carrier's transportation and logistics network.
- the carrier can begin transport of the parcel through the carrier's transportation and logistics network.
- Parcels moving through the carrier's transportation and logistics network are typically tracked by scanning a label (e.g., barcode, radio frequency identification (“RFID”) tag, etc.), shipping form, or other indicia associated with the parcel at one or more scan points.
- a label e.g., barcode, radio frequency identification (“RFID”) tag, etc.
- RFID radio frequency identification
- shipping form e.g., shipping form, or other indicia associated with the parcel at one or more scan points.
- one or more scanning devices may be used to scan a label associated with the parcel (or box or envelope) to capture shipping information from the parcel.
- an image of the label on the parcel for instance, may be captured by one or more imaging devices.
- the image of the label on the parcel may comprise shipping information (such as the tracking identifier and/or the authorization code) that may be human readable and/or machine readable.
- the image of the parcel can then be transmitted to and received by the carrier system 100 (Block 425 ).
- the carrier system 100 can then receive/identify shipping information contained in the image.
- the carrier system 100 (e.g., via the tracking module 260 ) can receive/identify the shipping information using a variety of techniques and approaches.
- a user e.g., a carrier employee
- OCR optical character recognition
- a variety of other techniques and approaches can be used.
- the carrier system 100 can determine whether the parcel is approved for shipment (Block 430 ). In determining whether the parcel is approved for shipment, the carrier system 100 can, for example, determine whether the authorization code used to ship the parcel is valid. The carrier system 100 may also determine whether the authorization code and/or parcel are in compliance with any predefined parameters associated with the authorization code (e.g., time period or usage parameters). Determining whether the parcel is approved for shipment may also include determining whether the account is still valid.
- this may include electronically communicating with the wireless services provider or charge card company to determine whether (a) the account associated with the phone number is still active, in good standing, and/or available for mobile payments and/or (b) the account corresponding to the charge card is still active and in good standing. Similarly, this may include determining, for example, whether the carrier has blacklisted the phone number corresponding to the account.
- the carrier system 100 in response to a determination that the parcel is approved for shipment, can store the shipment information in association with the tracking identifier, the authorization code, and/or the account identifier (Block 435 ). In one embodiment, this may include automatically creating a parcel level detail (“PLD”) record.
- the PLD record may include shipping information, such as the consignor's address, the consignor's mobile phone number, the authorization code, the tracking number, the consignee's address, the class of service, and/or the method of payment. As will be recognized, the storage of this information may occur at any point during the process, such as after receiving the first message transmitted from the user device.
- the parcel if the parcel is approved for shipment, the parcel continues to be transported through the carrier's transportation and logistics network to the consignee and/or destination address. If the parcel is not approved for shipment (e.g., the account associated with wireless phone number is not active and/or in good standing), the parcel can be held by the carrier or returned to the consignor. For example, a flag (e.g., an exception event) may be stored in the PLD record indicating that shipment of the parcel should be held or returned to the consignor. In the event the parcel is held by the carrier, carrier representative's can contact the consignor to receive an alternative means of payment for shipment of the parcel.
- a flag e.g., an exception event
- the shipping charges for shipment of the parcel may be automatically determined.
- the parcel may pass through automatic scanners, imaging devices, scales, and/or the like within the carrier's transportation and logistics network.
- the weight of the parcel can automatically be determined.
- imaging devices such as digital cameras, can capture images of the parcel.
- the carrier system 100 can use the images of the parcel to, for example, determine the dimensions of the parcel. With the weight, dimensions, and class of service of the parcel, the carrier system 100 (e.g., via the billing module 270 ) can determine the appropriate shipping charges for shipment of the parcel (Block 440 ).
- the carrier system 100 after determining the shipping charges for the parcel, can charge the appropriate account for shipment of the parcel (Block 445 ).
- the account may be (a) an account for wireless services (e.g., phone and/or data services), (b) an account for a charge card, (c) a shipping account with the carrier, and/or (d) a variety of other accounts.
- the carrier system 100 e.g., via the billing module 270
- the carrier system 100 (e.g., via the billing module 270 ) can charge the appropriate accounts in real time or near real time.
- the customer/user can be billed, for example, by his wireless services provider for the shipping charges at the end of his billing cycle.
- the wireless services provider can also settle the charges with the carrier.
- the carrier system 100 may provide additional information (e.g., the tracking number and/or the authorization code) to the appropriate entity (e.g., wireless service provider, charge card company, etc.) when charging the account.
- the appropriate entity e.g., wireless service provider, charge card company, etc.
- This information may be included, for example, on the customer's/user's bill.
- the wireless services provider can use this additional information to provide the details of the shipment on the customer's/user's bill for wireless services.
- the carrier system 100 can store a charge card number in association with a phone number for the customer/user.
- the customer/user can provide a phone number as the account identifier in the first message, but the charge card account could be charged for the shipment of the parcel—instead of the account with the wireless services provider.
- the carrier system 100 can store a carrier account number in association with a phone number. This may allow the customer/user to provide a phone number as the account identifier in the first message, but the carrier account could be charged for the shipment of the parcel—instead of the account with the wireless services provider.
- a customer/user can use an apparatus, such as a kiosk 120 , to initiate shipment of and payment for shipping a parcel.
- an apparatus such as a kiosk 120
- a customer/user can use a kiosk 120 , for example, to initiate shipment of a parcel (e.g., envelope, bag, package, bundled item, box with information pre-printed thereon, and/or the like) by a carrier.
- the kiosk 120 may have key entry and display features that allow customers/users to interact with the kiosk 120 .
- the process beings with the kiosk 120 receiving input requesting shipment of a parcel, e.g., via a customer/user inputting information into the kiosk 120 (Block 500 ).
- the kiosk 120 can cause display of a request for input of shipping information and/or a method of payment for shipping the parcel (Block 505 ).
- the shipping information may include information such as (a) the consignor's name, address, phone number, and charge card number (or a portion thereof), (b) the contents, weight, and dimensions of the parcel, (c) the consignee's name, address, and phone number, (d) the class of service of the parcel (e.g., Ground, Next Day Air, etc.), and/or (e) a variety of other information.
- the payment options may include paying for the shipment via (a) a charge card, (b) an account for wireless services, (c) an account with the carrier, (d) a physical form of currency, and/or (e) the like.
- the kiosk 120 may receive input (a) indicating that the customer/user desires to pay for the shipment via an account for wireless services (Block 510 ) and (b) identifying a particular phone number associated with the account for wireless services.
- the carrier system 100 in response to receiving input indicating that the customer/user desires to pay for shipment via the account for wireless services and the corresponding phone number, the carrier system 100 can determine whether the account for wireless services is valid (Block 515 ). As discussed above, determining whether the account is valid may include a variety of techniques and/or approaches. For example, in one embodiment, the carrier system 100 determines whether the account associated with the phone number is valid by electronically communicating with the wireless services provider to determine whether the account is active, in good standing, and/or available for mobile payments. For instance, a phone number in a family plan may be blocked for mobile payments via parental controls provided by the wireless services provider. Similarly, the wireless services provider may block messages to certain prefixes, such as 900 numbers.
- the carrier system 100 may determine whether the carrier has blacklisted the phone number, for example, corresponding to the account. In another embodiment, the carrier system 100 may determine whether the account corresponding to the charge card number is valid by determining whether the charge card account is active and in good standing.
- the kiosk 120 /carrier system 100 in response to a determination that the account is invalid, can generate and transmit a message to the user device (e.g., mobile device 110 or user computing device 115 ).
- the message may be any type of message and indicate that the customer/user cannot use the selected method of payment for shipping the parcel.
- the kiosk 120 /carrier system 100 in response to a determination that the account is valid, can generate and transmit a message comprising an authorization code to the user device.
- the message may be any type of message and include an authorization code.
- the authorization code may be, for example, an alphanumeric code (e.g., “A254”) that has been correlated with the tracking number and/or the shipping information.
- the authorization code may also be associated with various predefined parameters. For example, the authorization code may be associated with predefined parameters that define (a) a time period in which the authorization code is valid and/or (b) the number of times the authorization code can be used for shipments.
- the authorization code may be valid for a single shipment or multiple shipments.
- the authorization code may be valid for a certain period of time (e.g., 7 days) after issuance.
- a certain period of time e.g. 7 days
- the kiosk 120 in addition to generating and transmitting a message to the user device (or an account, such as Gmail, Skype, etc.), can cause display of a request for input of the authorization code transmitted to the user device (Block 530 ).
- the customer's/user's user device e.g., mobile device 110
- the authorization code e.g., see FIG. 7
- the customer/user can input the authorization code into the kiosk 120 (Block 535 ).
- the kiosk 120 in response to receiving input of the correct authorization code, can cause display of additional requests for input, for example, to properly classify the parcel. For instance, the kiosk 120 can cause display of text instructing the customer/user to place the parcel on a scale proximate (or disposed on) the kiosk 120 . By doing so, the kiosk 120 can determine the actual weight of the parcel.
- the kiosk 120 can also cause display of text instructing the customer/user to input (e.g., via key entry) the dimensions of the parcel. For example, the customer/user may input the dimension of the parcel in appropriate length, width, and height fields. As will be recognized, a variety of approaches and techniques may be used.
- the kiosk 120 after receiving the appropriate input (e.g., weight, dimensions, and class of service of the parcel), the kiosk 120 (or carrier system 100 ) can determine the appropriate shipping charges for shipment of the parcel (Block 540 ). For example, if a customer/user enters the dimensions of the parcel as 10 ⁇ 10 ⁇ 10 (e.g., length, width, and height) and the kiosk 120 determines the parcel weighs 2 pounds, the kiosk 120 may provide a notification to the customer/user that the parcel is classified as being a high volume, low weight parcel and cause display of the corresponding shipping charge. Additionally, the kiosk 120 may add a surcharge for certain destinations (e.g., rural areas) or contents (e.g., hazardous materials) of the parcel. As will be recognized, a variety of approaches and techniques may be used.
- the kiosk 120 may store the shipping information associated with the parcel and/or the customer/user (Block 545 ).
- the kiosk 120 /carrier system 100 may create a PLD record to store the shipping information, such as the consignor's address, the consignor's mobile phone number, the authorization code, the consignee's address, tracking number, class of service, and/or method of payment.
- the kiosk 120 may automatically print a shipping label to be affixed to the parcel (Block 545 ). After the kiosk 120 prints the shipping label, the customer/user can adhere the shipping label to the parcel. The customer/user can then deliver the parcel to the kiosk 120 , a drop-box 600 , or other carrier location/facility. Upon receipt of the parcel, the carrier can transport the parcel through the carrier's transportation and logistics network to the consignee and/or destination address.
- the kiosk 120 /carrier system 100 (e.g., via the billing module 270 ) can charge the appropriate account for shipment of the parcel (Block 550 ).
- the account may be an account for wireless services (e.g., phone and/or data services) and/or a variety of other accounts as described above.
- the customer/user can be billed by his wireless services provider for the shipping charges at the end of his billing cycle.
- the wireless services provider can then settle the shipping charges with the carrier.
- the carrier system 100 may provide additional information (e.g., the tracking number and/or the authorization code) to the appropriate entity (e.g., wireless service provider, charge card company, etc.) when charging the account.
- the appropriate entity e.g., wireless service provider, charge card company, etc.
- This information may be included, for example, on the customer's/user's bill.
- the wireless services provider can use this additional information to provide the details of the shipment on the customer's/user's bill for wireless services.
- the kiosk 120 may automatically initiate communication with a mobile device 110 associated with the account for wireless services.
- the kiosk 120 can communicate via a communication standard/protocol (e.g., Bluetooth) to confirm that the customer/user is currently in possession of the user device.
- a communication standard/protocol e.g., Bluetooth
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Economics (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Development Economics (AREA)
- Finance (AREA)
- Marketing (AREA)
- Entrepreneurship & Innovation (AREA)
- Operations Research (AREA)
- Human Resources & Organizations (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Technology Law (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
Description
- This application is a continuation application of U.S. application Ser. No. 12/813,096, filed Jun. 10, 2010, which is hereby incorporated herein in its entirety by reference.
- With an ever-increasing desire for customer-friendly shipping options, a need exits for a solution that allows customers to pay for shipping services using a mobile device.
- In general, embodiments of the present invention provide systems, methods, apparatus, and computer program products for the shipment of parcels.
- In accordance with one aspect, a method for shipping a parcel is provided. In one embodiment, the method comprises (1) receiving a first message transmitted from a user device requesting shipment of a parcel; (2) in response to receiving the first message, identifying an account identifier based at least in part on the first message, wherein the account identifier corresponds to an account associated with a user of the user device; (3) determining whether the account is valid; and (4) in response to a determination that the account is valid, generating and transmitting a second message to the user device, wherein the second message comprises an authorization code. In one embodiment, the method may also comprise (5) receiving shipping information that is generated as the parcel is transported within a carrier's transportation and logistics network, wherein the shipping information comprises a tracking identifier and the authorization code; (6) in response to receiving the shipping information, determining whether the parcel is approved for shipment based at least in part on the authorization code; (7) in response to a determination that the parcel is approved for shipment, storing at least a portion of the shipment information in association with the tracking identifier, the authorization code, and the account identifier; (8) electronically determining shipping charges for shipment of the parcel; and (9) electronically charging the shipping charges to the account.
- In accordance with another aspect, another method for shipping a parcel is provided. In one embodiment, the method comprises (1) receiving a first message transmitted from a user device requesting shipment of a parcel; (2) in response to receiving the first message, identifying an account identifier based at least in part on the first message, wherein the account identifier corresponds to an account associated with a user of the user device; and (3) determining whether the account is valid. In one embodiment, the method also comprises (4) in response to a determination that the account is valid, generating and transmitting a second message to the user device, wherein the second message comprises an authorization code; (5) receiving shipping information that is generated as the parcel is transported within a carrier's transportation and logistics network, wherein the shipping information comprises a tracking identifier and the authorization code; and (6) electronically charging shipping charges to the account.
- In accordance with yet another aspect, a computer program product for shipping a parcel is provided. The computer program product may comprise at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising executable portions configured to (1) receive a first message transmitted from a user device requesting shipment of a parcel; (2) in response to receiving the first message, identify an account identifier based at least in part on the first message, wherein the account identifier corresponds to an account associated with a user of the user device; (3) determine whether the account is valid; and (4) in response to a determination that the account is valid, generate and transmit a second message to the user device, wherein the second message comprises an authorization code. The computer-readable program code portions may also comprise executable portions configured to (5) receive shipping information that is generated as the parcel is transported within a carrier's transportation and logistics network, wherein the shipping information comprises a tracking identifier and the authorization code; (6) in response to receiving the shipping information, determine whether the parcel is approved for shipment based at least in part on the authorization code; (7) in response to a determination that the parcel is approved for shipment, store at least a portion of the shipment information in association with the tracking identifier, the authorization code, and the account identifier; (8) determine shipping charges for shipment of the parcel; and (9) charge the shipping charges to the account.
- In accordance with still another aspect, a computer program product for shipping a parcel is provided. The computer program product may comprise at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising executable portions configured to (1) receive a first message transmitted from a user device requesting shipment of a parcel; (2) in response to receiving the first message, identify an account identifier based at least in part on the first message, wherein the account identifier corresponds to an account associated with a user of the user device; and (3) determine whether the account is valid. The computer-readable program code portions may also comprise executable portions configured to (4) in response to a determination that the account is valid, generate and transmit a second message to the user device, wherein the second message comprises an authorization code; (5) receive shipping information that is generated as the parcel is transported within a carrier's transportation and logistics network, wherein the shipping information comprises a tracking identifier and the authorization code; and (6) charge shipping charges to the account.
- In accordance with another aspect, a method for shipping a parcel is provided. In one embodiment, the method comprises (1) receiving input from a user requesting shipment of a parcel; (2) causing display of a request for input identifying a method of payment for shipment of the parcel; (3) in response to causing display of the request for input of the method of payment for shipment of the parcel, receiving input (a) identifying an account for wireless services as the method of payment and (b) a phone number associated with the account for wireless services; and (4) determining whether the account for wireless services is valid. In one embodiment, the method also comprises (5) in response to a determination that the account for wireless services is valid, generating and transmitting a message to a mobile device associated with the phone number, wherein the message comprises an authorization code; (6) causing display of a request for input of the authorization code transmitted to the mobile device; and (7) receiving input from the user identifying the authorization code.
- In accordance with another aspect, another method for shipping a parcel is provided. In one embodiment, the method comprises (1) receiving input from a user requesting shipment of a parcel; (2) causing display of a request for input identifying a method of payment for shipment of the parcel; (3) in response causing display of the request for input of the method of payment for shipment of the parcel, receiving input identifying an account for wireless services as the method of payment; (4) in response to receiving input identifying the account for wireless services as the method of payment, automatically initiating communication with a mobile device associated with the account for wireless services; and (5) determining whether the account for wireless services is valid.
- In accordance with still another aspect, a computer program product for shipping a parcel is provided. The computer program product may comprise at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising executable portions configured to (1) receive input from a user requesting shipment of a parcel; (2) cause display of a request for input identifying a method of payment for shipment of the parcel; (3) in response to causing display of the request for input of the method of payment for shipment of the parcel, receive input identifying (a) an account for wireless services as the method of payment and (b) a phone number associated with the account for wireless services; and (4) determine whether the account for wireless services is valid. The computer-readable program code portions may also comprise executable portions configured to (5) in response to a determination that the account for wireless services is valid, generate and transmit a message to a mobile device associated with the phone number, wherein the message comprises an authorization code; (6) cause display of a request for input of the authorization code transmitted to the mobile device; and (7) receive input from the user identifying the authorization code.
- In accordance with yet another aspect, another computer program product for shipping a parcel is provided. The computer program product may comprise at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising executable portions configured to (1) receive input from a user requesting shipment of a parcel; (2) cause display of a request for input identifying a method of payment for shipment of the parcel; (3) in response causing display of the request for input of the method of payment for shipment of the parcel, receive input identifying an account for wireless services as the method of payment; (4) in response to receiving input identifying the account for wireless services as the method of payment, automatically initiate communication with a mobile device associated with the account for wireless services; and (5) determine whether the account for wireless services is valid.
- Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
-
FIG. 1 is an overview of a system that can be used to practice various embodiments of the present invention. -
FIG. 2 is an exemplary schematic diagram of a carrier system according to one embodiment of the present invention. -
FIG. 3 is an exemplary schematic diagram of a mobile device according to one embodiment of the present invention. -
FIGS. 4-5 are flowcharts illustrating operations and processes that can be used in accordance with various embodiments of the present invention. -
FIG. 6 is an exemplary drop-box according to one embodiment of the present invention. -
FIG. 7 shows exemplary input/output that can be produced via a mobile device according to one embodiment of the present invention. - Various embodiments of the present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the inventions are shown. Indeed, these inventions 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 satisfy applicable legal requirements. The term “or” is used herein in both the alternative and conjunctive sense, unless otherwise indicated. Like numbers refer to like elements throughout.
- As should be appreciated, various embodiments may be implemented in various ways, including as methods, apparatus, systems, or computer program products. Accordingly, various embodiments may take the form of an entirely hardware embodiment or an embodiment in which a processor is programmed to perform certain steps. Furthermore, various implementations may take the form of a computer program product on a computer-readable storage medium having computer-readable program instructions embodied in the storage medium. Any suitable computer-readable storage medium may be utilized including hard disks, CD-ROMs, optical storage devices, or magnetic storage devices.
- Various embodiments are described below with reference to block diagrams and flowchart illustrations of methods, apparatus, systems, and computer program products. It should be understood that each block of the block diagrams and flowchart illustrations, respectively, may be implemented in part by computer program instructions, e.g., as logical steps or operations executing on a processor in a computing system. These computer program instructions may be loaded onto a computer, such as a special purpose computer or other programmable data processing apparatus to produce a specifically-configured machine, such that the instructions which execute on the computer or other programmable data processing apparatus implement 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 including computer-readable instructions for implementing the functionality 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 operations for implementing the functions specified in the flowchart block or blocks.
- Accordingly, blocks of the block diagrams and flowchart illustrations support various combinations for performing the specified functions, combinations of operations 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 operations, or combinations of special purpose hardware and computer instructions.
-
FIG. 1 provides an illustration of a system that can be used in conjunction with various embodiments of the present invention. As shown inFIG. 1 , the system may include one ormore carrier systems 100, one ormore networks 105, one or moremobile devices 110, one or moreuser computing devices 115, and one ormore kiosks 120. Each of the components of the system may be in electronic communication with, for example, one another over the same or different wireless or wired networks including, for example, a wired or wireless Personal Area Network (“PAN”), Local Area Network (“LAN”), Metropolitan Area Network (“MAN”), Wide Area Network (“WAN”), or the like. Additionally, whileFIG. 1 illustrates certain system entities as separate, standalone entities, the various embodiments are not limited to this particular architecture. -
FIG. 2 provides a schematic of acarrier system 100 according to one embodiment of the present invention. In general, the term “system” may refer to, for example, any computer, computing device, mobile phone, desktop, notebook or laptop, distributed system, server, blade, gateway, switch, processing device, or combination of processing devices adapted to perform the functions described herein. As will be understood from this figure, in one embodiment, thecarrier system 100 includes aprocessor 205 that communicates with other elements within thecarrier system 100 via a system interface or bus 261. Theprocessor 205 may be embodied in a number of different ways. For example, theprocessor 205 may be embodied as a processing element, a coprocessor, a controller or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (“ASIC”), a field programmable gate array (“FPGA”), a hardware accelerator, or the like. - In an exemplary embodiment, the
processor 205 may be configured to execute instructions stored in the device memory or otherwise accessible to theprocessor 205. As such, whether configured by hardware or software methods, or by a combination thereof, theprocessor 205 may represent an entity capable of performing operations according to embodiments of the present invention when configured accordingly. A display device/input device 264 for receiving and displaying data may also be included in thecarrier system 100. This display device/input device 264 may be, for example, a keyboard or pointing device that is used in combination with a monitor. Thecarrier system 100 further includesmemory 263, which may include both read only memory (“ROM”) 265 and random access memory (“RAM”) 267. The carrier system'sROM 265 may be used to store a basic input/output system (“BIOS”) 226 containing the basic routines that help to transfer information to the different elements within thecarrier system 100. - In addition, in one embodiment, the
carrier system 100 includes at least onestorage device 268, such as a hard disk drive, a CD drive, and/or an optical disk drive for storing information on various computer-readable media. The storage device(s) 268 and its associated computer-readable media may provide nonvolatile storage. The computer-readable media described above could be replaced by any other type of computer-readable media, such as embedded or removable multimedia memory cards (“MMCs”), secure digital (“SD”) memory cards, Memory Sticks, electrically erasable programmable read-only memory (“EEPROM”), flash memory, hard disk, or the like. Additionally, each of thesestorage devices 268 may be connected to the system bus 261 by an appropriate interface. - Furthermore, a number of program modules may be stored by the
various storage devices 268 and/or withinRAM 267. Such program modules may include anoperating system 280, abilling module 270, atracking module 260, and anauthorization module 250. These modules may control certain aspects of the operation of thecarrier system 100 with the assistance of theprocessor 205 andoperating system 280—although their functionality need not be modularized. In addition to the program modules, thecarrier system 100 may store or be connected to one or more databases (e.g., database 240) with one or more tables stored therein. - Also located within the
carrier system 100, in one embodiment, is anetwork interface 274 for interfacing with various computing entities. This communication may be via the same or different wired or wireless networks (or a combination of wired and wireless networks), as discussed above. For instance, the communication may be executed using a wired data transmission protocol, such as fiber distributed data interface (“FDDI”), digital subscriber line (“DSL”), Ethernet, asynchronous transfer mode (“ATM”), frame relay, data over cable service interface specification (“DOCSIS”), or any other wired transmission protocol. Similarly, thecarrier system 100 may be configured to communicate via wireless external communication networks using any of a variety of protocols, such as 802.11, general packet radio service (“GPRS”), wideband code division multiple access (“W-CDMA”), or any other wireless protocol. Via thenetwork interface 274, thecarrier system 100 may be capable of sending and receiving text messages and/or instant messages. - It will be appreciated that one or more of the carrier system's 100 components may be located remotely from
other carrier system 100 components. Furthermore, one or more of the components may be combined and additional components performing functions described herein may be included in thecarrier system 100. -
FIG. 3 provides an illustrative schematic representative of amobile device 110 that can be used in conjunction with the embodiments of the present invention. As shown inFIG. 3 , themobile device 110 can include anantenna 312, atransmitter 304, areceiver 306, and a processing device 308 (e.g., a processor, controller, and/or the like) that provides signals to and receives signals from thetransmitter 304 andreceiver 306, respectively. - The signals provided to and received from the
transmitter 304 and thereceiver 306, respectively, may include signaling information in accordance with an air interface standard of applicable wireless systems. In this regard, themobile device 110 may be capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. More particularly, themobile device 110 may operate in accordance with any of a number of second-generation (“2G”) communication protocols, third-generation (“3G”) communication protocols, fourth-generation (“4G”) communication protocols, and/or the like. Further, for example, themobile device 110 may operate in accordance with any of a number of different wireless networking techniques, including Bluetooth, IEEE 802.11 (“Wi-Fi”), 802.16 (“WiMAX”), ultra wideband (“UWB”), and/or the like. Via these communication standards and protocols, themobile device 110 can communicate with thecarrier system 100 and/or various other entities (e.g.,user computing devices 110 or telephones 120). Themobile device 110 can also download changes, add-ons, and updates, for instance, to its firmware, software (e.g., including modules), and operating system. - The
mobile device 110 may also comprise a user interface (that can include adisplay 316 coupled to a processing device 308) and/or a user input interface (coupled to the processing device 308). The user input interface can comprise any of a number of devices allowing themobile device 110 to receive data, such as akeypad 318, a touch display, voice or motion interfaces, or other input device. In embodiments including akeypad 318, thekeypad 318 can include the conventional numeric (0-9) and related keys (#, *), and other keys used for operating themobile device 110 and may include a full set of alphabetic keys or set of keys that may be activated to provide a full set of alphanumeric keys. In addition to providing input, the user input interface can be used, for example, to activate or deactivate certain functions, such as screen savers and/or sleep modes. Although not shown, themobile device 110 may also include a battery, such as a vibrating battery pack, for powering the various circuits that are required to operate themobile device 110, as well as optionally providing mechanical vibration as a detectable output. - The
mobile device 110 can also includevolatile memory 322 and/ornon-volatile memory 324, which can be embedded and/or may be removable. For example, the non-volatile memory may be embedded or removable multimedia memory cards (“MMCs”), secure digital (“SD”) memory cards, Memory Sticks, EEPROM, flash memory, hard disk, or the like. The memory can store any of a number of pieces or amount of information and data used by themobile device 110 to implement the functions of themobile device 110. The memory can also store content, such as computer program code for an application and/or other computer programs. - As shown in
FIG. 1 , the system may include akiosk 120. Thekiosk 120 may include one or more components that are functionally similar to those of thecarrier system 100. For example, akiosk 120 may include: (1) a processor that communicates with elements via a system interface or bus; (2) a display device/input device; (3) memory including both ROM and RAM; (4) a storage device; (5) a network interface (including near field communication capabilities such as Bluetooth and capabilities for sending and receiving text messages and/or instant messages); (6) weighing mechanisms, such as scales; and/or (7) imaging devices. These architectures are provided for exemplary purposes only and are not limiting to the various embodiments. - The
user computing devices 115 may each include one or more components that are functionally similar to those of thecarrier system 100. For example, in one embodiment, eachuser computing device 115 may include: (1) a processor that communicates with other elements via a system interface or bus; (2) a display device/input device; (3) memory including both ROM and RAM; (4) a storage device; and (5) a network interface. These architectures are provided for exemplary purposes only and are not limiting to the various embodiments. The term “computing device” is used generically to refer to any computer, mobile phone, computing device, desktop, notebook or laptop, distributed system, server, gateway, switch, or other processing device adapted to perform the functions described herein. - Reference will now be made to
FIGS. 4-7 .FIGS. 4-5 provide flowcharts illustrating operations that may be performed for shipping parcels.FIG. 6 is an exemplary drop-box 600 at which parcels can be dropped off for a carrier (e.g., United Parcel Service of America, Inc.). AndFIG. 7 shows exemplary input/output that can be produced via amobile device 110. - In one embodiment, customers/users can use electronic messages to initiate shipment of and payment for shipping a parcel.
- a. Initiation of Shipment
- In one embodiment, a customer/user can use, for example, a drop-box 600 (such as the one shown in
FIG. 6 ) to initiate shipment of a parcel (e.g., envelope, bag, package, bundled item, box with information pre-printed thereon, and/or the like) by a carrier (e.g., United Parcel Service of America, Inc.). For instance, the user can retrieve a shipping form (or a box or envelope with information pre-printed thereon) that may be stored proximate the drop-box 600 (or other shipping location) and fill out the shipping form (or box or envelope with information pre-printed thereon) with shipping information. The shipping information may include information such as (a) the consignor's name, address, phone number, and charge card number (or a portion thereof), (b) the contents, weight, and dimensions of the parcel, (c) the consignee's name, address, and phone number, (d) the class of service of the parcel (e.g., Ground, Next Day Air, etc.), and/or (e) a variety of other information. The shipping form (or box or envelope with information pre-printed thereon) may also include a unique, pre-printed tracking number. The tracking number may be, for example, a progressive number (“PRO number”), a purchase order number, and/or a set of alphanumeric characters (e.g., “1Z23456789”). The tracking number may be used by the carrier to identify and track the parcel as it travels through the carrier's transportation and logistics network. To that end, the shipping form may have a self-adhesive portion, for example, that can be used to adhere the shipping form to the parcel or adhere a label portion of the shipping form to the parcel. - As shown in
FIG. 4 , in one embodiment, after (or in some cases before) filing out the shipping form (or box or envelope with information pre-printed thereon), the customer/user can initiate shipment of the parcel with carrier. To do so, the customer/user may send a message (e.g., a first message) via a user device (e.g., amobile device 110 or a user computing device 115) to the carrier. For example, the shipping form, drop-box 600, box, or envelope may indicate that to initiate shipment of a parcel, a text message should be sent to 555-555-5555 with the tracking number printed on the shipping form as the body of the message. Thus, in one embodiment, the customer/user (e.g., via operation of user device such as amobile device 110 or user computing device 115) sends a text message to 555-555-5555 with 1Z23456789 as the body of the message. As will be recognized, though, the message may be any type of message, such as a text message, an instant message, an email message, and/or the like. Similarly, the message may include a variety of shipping information, such as the pre-printed tracking number listed on the shipping form, a charge card number (or a portion thereof), and/or a carrier account number (or a portion thereof). - As indicated in
Block 400, in one embodiment, a carrier entity (e.g., a carrier system 100) can receive the first message (e.g., text message) sent from the user device (e.g.,mobile device 110 or user computing device 115) requesting shipment of the parcel. In response to receiving the first message, thecarrier system 100, for example, can identify an account identifier based at least in part on the first message. In one embodiment, the account identifier may correspond to an account associated with the customer/user (Block 405). The account identifier may be, for example, a phone number of themobile device 110 from which the first message originates, the phone number associated with an application executing on auser computing device 115 from which the first message originates, a credit card number (or a portion thereof) within the body of the first message, and/or a carrier account number (or a portion thereof) within the body of the first message. Accordingly, the account corresponding to the account identifier may be (a) an account for wireless services (e.g., phone and/or data services), (b) an account for a charge card, (c) a shipping account with the carrier, and/or (d) a variety of other accounts. - As shown in
Block 410, after identifying the account identifier, thecarrier system 100 can determine whether the account is valid. Determining whether the account is valid may include a variety of techniques and/or approaches. For example, in one embodiment, thecarrier system 100 determines whether the account associated with the phone number is valid by electronically communicating with the wireless services provider to determine whether the account is active, in good standing, and/or available for mobile payments. For instance, a phone number in a family plan may be blocked for mobile payments via parental controls provided by the wireless services provider. Similarly, the wireless services provider may block messages to certain prefixes, such as 900 numbers. In another embodiment, thecarrier system 100 may determine whether the carrier has “blacklisted” the phone number, for example, corresponding to the account. In another embodiment, thecarrier system 100 may determine whether the account corresponding to the charge card number is valid by determining whether the charge card account is active and in good standing. - In addition to the determining whether the account is valid, the carrier system 100 (e.g., via the authorization module 250) can execute various other validation/confirmation techniques and/or approaches. For example, the
carrier system 100 can determine whether the tracking number in the body of the first message has been used previously. Or, thecarrier system 100 can access (a) the transaction history of the customer's/user's interactions with the carrier and/or (b) any customer/user configured parameters. For example, a customer/user can register mobile phone numbers with carrier (e.g., via the carrier's website) to configure usage parameters. The usage parameters may, for example, (a) limit a phone number to one shipment per day, (b) not allow for international shipments using the phone number, and/or (c) limit the mobile payments for shipping to $100 per day. As will be recognized, a variety of approaches and/or techniques may be used. - In one embodiment, as indicated in
Block 415, in response to a determination that the account is invalid, the carrier system 100 (e.g., via the authorization module 250) can generate and transmit a message (e.g., a second message) to the user device (e.g.,mobile device 110 or user computing device 115). As with the first message, the second message may be any type of message, such as a text message, an instant message, an email message, and/or the like. In an embodiment in which the account is invalid, the second message may indicate that the customer/user cannot use the selected method of payment for shipping the parcel. - In one embodiment, as indicated in
Block 420, in response to a determination that the account is valid, thecarrier system 100 can generate and transmit a message (e.g., a second message) to the user device (e.g.,mobile device 110 or user computing device 115). As indicated, the second message may be any type of message, such as a text message, an instant message, an email message, and/or the like. In an embodiment in which the account is valid, the second message may comprise an authorization code for shipment of the parcel. The authorization code may be, for example, an alphanumeric code (e.g., “A254”) that has been correlated with the tracking number and/or the shipping information provided by the customer/user. - In one embodiment, the authorization code may also be associated with various predefined parameters. For example, the authorization code may be associated with predefined parameters that define (a) a time period in which the authorization code is valid and/or (b) the number of times the authorization code can be used for shipments. For instance, the authorization code may only be valid for a single shipment. Similarly, the authorization code may be valid for a certain period of time (e.g., 7 days) after issuance. As will be recognized, a variety of other approaches and techniques may be used.
- In one embodiment, after the user device (e.g.,
mobile device 110 or user computing device 115) receives the second message, the user device (e.g.,mobile device 110 or user computing device 115) can cause display of the second message to the customer/user, as shown inFIG. 7 . The customer/user can write the authorization code on the parcel, label, or shipping form, for example. The customer/user can then deliver the parcel to a drop-box 600 or other carrier location/facility. Alternatively, the customer/user may request that a carrier vehicle be dispatched to pick up the parcel from the customer/user. Upon receipt of the parcel, the carrier can use the shipping information and/or authorization code in transporting the parcel through the carrier's transportation and logistics network. - b. Shipment
- In one embodiment, after the carrier receives the parcel from the customer/user (consignee), the carrier can begin transport of the parcel through the carrier's transportation and logistics network. Parcels moving through the carrier's transportation and logistics network are typically tracked by scanning a label (e.g., barcode, radio frequency identification (“RFID”) tag, etc.), shipping form, or other indicia associated with the parcel at one or more scan points. For example, at a transportation hub, one or more scanning devices may be used to scan a label associated with the parcel (or box or envelope) to capture shipping information from the parcel. Additionally or alternatively, an image of the label on the parcel, for instance, may be captured by one or more imaging devices. As with scanning the parcel, the image of the label on the parcel may comprise shipping information (such as the tracking identifier and/or the authorization code) that may be human readable and/or machine readable.
- In one embodiment, the image of the parcel can then be transmitted to and received by the carrier system 100 (Block 425). The
carrier system 100 can then receive/identify shipping information contained in the image. The carrier system 100 (e.g., via the tracking module 260) can receive/identify the shipping information using a variety of techniques and approaches. For example, a user (e.g., a carrier employee) can read the shipping information from the image and input the same via an interface into thecarrier system 100. In another embodiment, an optical character recognition (“OCR”) feature can be used to extract the shipping information from the image. As will be recognized, a variety of other techniques and approaches can be used. - As a result of receiving/identifying the shipping information as the parcel is transported within a carrier's transportation and logistics network, the
carrier system 100 can determine whether the parcel is approved for shipment (Block 430). In determining whether the parcel is approved for shipment, thecarrier system 100 can, for example, determine whether the authorization code used to ship the parcel is valid. Thecarrier system 100 may also determine whether the authorization code and/or parcel are in compliance with any predefined parameters associated with the authorization code (e.g., time period or usage parameters). Determining whether the parcel is approved for shipment may also include determining whether the account is still valid. As discussed above, this may include electronically communicating with the wireless services provider or charge card company to determine whether (a) the account associated with the phone number is still active, in good standing, and/or available for mobile payments and/or (b) the account corresponding to the charge card is still active and in good standing. Similarly, this may include determining, for example, whether the carrier has blacklisted the phone number corresponding to the account. - In one embodiment, in response to a determination that the parcel is approved for shipment, the
carrier system 100 can store the shipment information in association with the tracking identifier, the authorization code, and/or the account identifier (Block 435). In one embodiment, this may include automatically creating a parcel level detail (“PLD”) record. The PLD record may include shipping information, such as the consignor's address, the consignor's mobile phone number, the authorization code, the tracking number, the consignee's address, the class of service, and/or the method of payment. As will be recognized, the storage of this information may occur at any point during the process, such as after receiving the first message transmitted from the user device. - In one embodiment, if the parcel is approved for shipment, the parcel continues to be transported through the carrier's transportation and logistics network to the consignee and/or destination address. If the parcel is not approved for shipment (e.g., the account associated with wireless phone number is not active and/or in good standing), the parcel can be held by the carrier or returned to the consignor. For example, a flag (e.g., an exception event) may be stored in the PLD record indicating that shipment of the parcel should be held or returned to the consignor. In the event the parcel is held by the carrier, carrier representative's can contact the consignor to receive an alternative means of payment for shipment of the parcel.
- c. Payment for Shipment
- In one embodiment, as the parcel is transported through the carrier's transportation and logistics network to the consignee and/or destination address, the shipping charges for shipment of the parcel may be automatically determined. For example, the parcel may pass through automatic scanners, imaging devices, scales, and/or the like within the carrier's transportation and logistics network. Thus, for instance, as the parcel passes over a scale, the weight of the parcel can automatically be determined. Additionally, imaging devices, such as digital cameras, can capture images of the parcel. The
carrier system 100 can use the images of the parcel to, for example, determine the dimensions of the parcel. With the weight, dimensions, and class of service of the parcel, the carrier system 100 (e.g., via the billing module 270) can determine the appropriate shipping charges for shipment of the parcel (Block 440). - In one embodiment, after determining the shipping charges for the parcel, the carrier system 100 (e.g., via the billing module 270) can charge the appropriate account for shipment of the parcel (Block 445). As discussed above, the account may be (a) an account for wireless services (e.g., phone and/or data services), (b) an account for a charge card, (c) a shipping account with the carrier, and/or (d) a variety of other accounts. In one embodiment, the carrier system 100 (e.g., via the billing module 270) can charge (e.g., process) the shipping charges to accounts in batch, such as batch processing the transaction hourly or nightly. In another embodiment, the carrier system 100 (e.g., via the billing module 270) can charge the appropriate accounts in real time or near real time. Thus, after the
carrier system 100 charges the appropriate account, the customer/user can be billed, for example, by his wireless services provider for the shipping charges at the end of his billing cycle. The wireless services provider can also settle the charges with the carrier. - In one embodiment, in addition to charging the appropriate account, the
carrier system 100 may provide additional information (e.g., the tracking number and/or the authorization code) to the appropriate entity (e.g., wireless service provider, charge card company, etc.) when charging the account. This information may be included, for example, on the customer's/user's bill. For instance, the wireless services provider can use this additional information to provide the details of the shipment on the customer's/user's bill for wireless services. - d. Additional Concepts
- As will be recognized, a variety of other approaches and techniques may be used. For example, in one embodiment, the
carrier system 100 can store a charge card number in association with a phone number for the customer/user. Thus, the customer/user can provide a phone number as the account identifier in the first message, but the charge card account could be charged for the shipment of the parcel—instead of the account with the wireless services provider. Similarly, thecarrier system 100 can store a carrier account number in association with a phone number. This may allow the customer/user to provide a phone number as the account identifier in the first message, but the carrier account could be charged for the shipment of the parcel—instead of the account with the wireless services provider. - In one embodiment, a customer/user can use an apparatus, such as a
kiosk 120, to initiate shipment of and payment for shipping a parcel. - a. Initiation of Shipment and Shipment
- In one embodiment, a customer/user can use a
kiosk 120, for example, to initiate shipment of a parcel (e.g., envelope, bag, package, bundled item, box with information pre-printed thereon, and/or the like) by a carrier. As indicated, thekiosk 120 may have key entry and display features that allow customers/users to interact with thekiosk 120. In one embodiment, the process beings with thekiosk 120 receiving input requesting shipment of a parcel, e.g., via a customer/user inputting information into the kiosk 120 (Block 500). In response to receiving this input, thekiosk 120 can cause display of a request for input of shipping information and/or a method of payment for shipping the parcel (Block 505). As discussed previously, the shipping information may include information such as (a) the consignor's name, address, phone number, and charge card number (or a portion thereof), (b) the contents, weight, and dimensions of the parcel, (c) the consignee's name, address, and phone number, (d) the class of service of the parcel (e.g., Ground, Next Day Air, etc.), and/or (e) a variety of other information. The payment options may include paying for the shipment via (a) a charge card, (b) an account for wireless services, (c) an account with the carrier, (d) a physical form of currency, and/or (e) the like. In one embodiment, in response to causing display of the request for the method of payment for shipment of the parcel, thekiosk 120 may receive input (a) indicating that the customer/user desires to pay for the shipment via an account for wireless services (Block 510) and (b) identifying a particular phone number associated with the account for wireless services. - In one embodiment, in response to receiving input indicating that the customer/user desires to pay for shipment via the account for wireless services and the corresponding phone number, the
carrier system 100 can determine whether the account for wireless services is valid (Block 515). As discussed above, determining whether the account is valid may include a variety of techniques and/or approaches. For example, in one embodiment, thecarrier system 100 determines whether the account associated with the phone number is valid by electronically communicating with the wireless services provider to determine whether the account is active, in good standing, and/or available for mobile payments. For instance, a phone number in a family plan may be blocked for mobile payments via parental controls provided by the wireless services provider. Similarly, the wireless services provider may block messages to certain prefixes, such as 900 numbers. In another embodiment, thecarrier system 100 may determine whether the carrier has blacklisted the phone number, for example, corresponding to the account. In another embodiment, thecarrier system 100 may determine whether the account corresponding to the charge card number is valid by determining whether the charge card account is active and in good standing. - In one embodiment, as indicated in
Block 520, in response to a determination that the account is invalid, thekiosk 120/carrier system 100 (e.g., via the authorization module 250) can generate and transmit a message to the user device (e.g.,mobile device 110 or user computing device 115). As discussed above, the message may be any type of message and indicate that the customer/user cannot use the selected method of payment for shipping the parcel. - In one embodiment, as indicated in
Block 525, in response to a determination that the account is valid, thekiosk 120/carrier system 100 (e.g., via the authorization module 250) can generate and transmit a message comprising an authorization code to the user device. As discussed above, the message may be any type of message and include an authorization code. The authorization code may be, for example, an alphanumeric code (e.g., “A254”) that has been correlated with the tracking number and/or the shipping information. The authorization code may also be associated with various predefined parameters. For example, the authorization code may be associated with predefined parameters that define (a) a time period in which the authorization code is valid and/or (b) the number of times the authorization code can be used for shipments. For instance, the authorization code may be valid for a single shipment or multiple shipments. Similarly, the authorization code may be valid for a certain period of time (e.g., 7 days) after issuance. As will be recognized, a variety of other approaches and techniques may be used. - In one embodiment, in addition to generating and transmitting a message to the user device (or an account, such as Gmail, Skype, etc.), the
kiosk 120 can cause display of a request for input of the authorization code transmitted to the user device (Block 530). Thus, after the customer's/user's user device (e.g., mobile device 110) receives the message with the authorization code (e.g., seeFIG. 7 ), the customer/user can input the authorization code into the kiosk 120 (Block 535). - In one embodiment, in response to receiving input of the correct authorization code, the
kiosk 120 can cause display of additional requests for input, for example, to properly classify the parcel. For instance, thekiosk 120 can cause display of text instructing the customer/user to place the parcel on a scale proximate (or disposed on) thekiosk 120. By doing so, thekiosk 120 can determine the actual weight of the parcel. Thekiosk 120 can also cause display of text instructing the customer/user to input (e.g., via key entry) the dimensions of the parcel. For example, the customer/user may input the dimension of the parcel in appropriate length, width, and height fields. As will be recognized, a variety of approaches and techniques may be used. - In one embodiment, after receiving the appropriate input (e.g., weight, dimensions, and class of service of the parcel), the kiosk 120 (or carrier system 100) can determine the appropriate shipping charges for shipment of the parcel (Block 540). For example, if a customer/user enters the dimensions of the parcel as 10×10×10 (e.g., length, width, and height) and the
kiosk 120 determines the parcel weighs 2 pounds, thekiosk 120 may provide a notification to the customer/user that the parcel is classified as being a high volume, low weight parcel and cause display of the corresponding shipping charge. Additionally, thekiosk 120 may add a surcharge for certain destinations (e.g., rural areas) or contents (e.g., hazardous materials) of the parcel. As will be recognized, a variety of approaches and techniques may be used. - In addition to determining the shipping charges, the kiosk 120 (or carrier system 100) may store the shipping information associated with the parcel and/or the customer/user (Block 545). For example, the
kiosk 120/carrier system 100 may create a PLD record to store the shipping information, such as the consignor's address, the consignor's mobile phone number, the authorization code, the consignee's address, tracking number, class of service, and/or method of payment. - In one embodiment, in addition to storing the shipping information, the
kiosk 120 may automatically print a shipping label to be affixed to the parcel (Block 545). After thekiosk 120 prints the shipping label, the customer/user can adhere the shipping label to the parcel. The customer/user can then deliver the parcel to thekiosk 120, a drop-box 600, or other carrier location/facility. Upon receipt of the parcel, the carrier can transport the parcel through the carrier's transportation and logistics network to the consignee and/or destination address. - b. Payment for Shipment
- In one embodiment, the
kiosk 120/carrier system 100 (e.g., via the billing module 270) can charge the appropriate account for shipment of the parcel (Block 550). As discussed above, the account may be an account for wireless services (e.g., phone and/or data services) and/or a variety of other accounts as described above. Thus, the customer/user can be billed by his wireless services provider for the shipping charges at the end of his billing cycle. Correspondingly, the wireless services provider can then settle the shipping charges with the carrier. - In one embodiment, in addition to charging the appropriate account, the
carrier system 100 may provide additional information (e.g., the tracking number and/or the authorization code) to the appropriate entity (e.g., wireless service provider, charge card company, etc.) when charging the account. This information may be included, for example, on the customer's/user's bill. For instance, the wireless services provider can use this additional information to provide the details of the shipment on the customer's/user's bill for wireless services. - c. Additional Concepts
- As will be recognized, a variety of other approaches and techniques may be used. For example, in one embodiment, in response to a determination that the account is valid, the
kiosk 120 may automatically initiate communication with amobile device 110 associated with the account for wireless services. Thus, in lieu of sending a message with an authorization code to the user device (e.g., mobile device 110), thekiosk 120 can communicate via a communication standard/protocol (e.g., Bluetooth) to confirm that the customer/user is currently in possession of the user device. - Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are 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 purposes of limitation.
Claims (24)
Priority Applications (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/813,998 US9082096B2 (en) | 2010-06-10 | 2010-06-11 | Enhanced payments for shipping |
CA2798793A CA2798793C (en) | 2010-06-10 | 2011-03-02 | Enhanced payments for shipping |
EP11714145.7A EP2580727A4 (en) | 2010-06-10 | 2011-03-02 | Enhanced payments for shipping |
CA2798791A CA2798791C (en) | 2010-06-10 | 2011-03-02 | Enhanced payments for shipping |
PCT/US2011/026770 WO2011156023A2 (en) | 2010-06-10 | 2011-03-02 | Enhanced payments for shipping |
EP11709527.3A EP2580725A4 (en) | 2010-06-10 | 2011-03-02 | Enhanced payments for shipping |
PCT/US2011/026769 WO2011156022A1 (en) | 2010-06-10 | 2011-03-02 | Enhanced payments for shipping |
US14/728,569 US10643293B2 (en) | 2010-06-10 | 2015-06-02 | Enhanced payments for shipping |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/813,096 US10032239B2 (en) | 2010-06-10 | 2010-06-10 | Enhanced payments for shipping |
US12/813,998 US9082096B2 (en) | 2010-06-10 | 2010-06-11 | Enhanced payments for shipping |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/813,096 Continuation US10032239B2 (en) | 2010-06-10 | 2010-06-10 | Enhanced payments for shipping |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/728,569 Continuation US10643293B2 (en) | 2010-06-10 | 2015-06-02 | Enhanced payments for shipping |
Publications (2)
Publication Number | Publication Date |
---|---|
US20110307361A1 true US20110307361A1 (en) | 2011-12-15 |
US9082096B2 US9082096B2 (en) | 2015-07-14 |
Family
ID=45096995
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/813,096 Active 2030-07-19 US10032239B2 (en) | 2010-06-10 | 2010-06-10 | Enhanced payments for shipping |
US12/813,998 Active 2030-08-27 US9082096B2 (en) | 2010-06-10 | 2010-06-11 | Enhanced payments for shipping |
US14/728,569 Active 2030-12-03 US10643293B2 (en) | 2010-06-10 | 2015-06-02 | Enhanced payments for shipping |
US16/043,649 Active 2031-02-15 US11170458B2 (en) | 2010-06-10 | 2018-07-24 | Enhanced payments for shipping |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/813,096 Active 2030-07-19 US10032239B2 (en) | 2010-06-10 | 2010-06-10 | Enhanced payments for shipping |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/728,569 Active 2030-12-03 US10643293B2 (en) | 2010-06-10 | 2015-06-02 | Enhanced payments for shipping |
US16/043,649 Active 2031-02-15 US11170458B2 (en) | 2010-06-10 | 2018-07-24 | Enhanced payments for shipping |
Country Status (4)
Country | Link |
---|---|
US (4) | US10032239B2 (en) |
EP (2) | EP2580725A4 (en) |
CA (2) | CA2798793C (en) |
WO (2) | WO2011156023A2 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130151411A1 (en) * | 2011-12-09 | 2013-06-13 | Worldpasskey, Inc. | Digital authentication and security method and system |
WO2013148706A1 (en) * | 2012-03-26 | 2013-10-03 | Ebay Inc. | Unified service for providing shipping services |
US20150066797A1 (en) * | 2013-09-04 | 2015-03-05 | Christopher Scott Outwater | System and method for enhancing delivery security and preventing fraud |
US9082099B1 (en) * | 2014-07-18 | 2015-07-14 | Dmitriy Kolchin | System and method for context-sensitive delivery notification |
US11281850B2 (en) * | 2017-12-28 | 2022-03-22 | A9.Com, Inc. | System and method for self-filing customs entry forms |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10032239B2 (en) | 2010-06-10 | 2018-07-24 | United Parcel Service Of America, Inc. | Enhanced payments for shipping |
US9479390B2 (en) | 2012-11-14 | 2016-10-25 | Accuzip, Inc. | Automatic initiation of a response action when an event associated with an item in transit is based on logistical node scan data |
US11153146B2 (en) | 2012-11-14 | 2021-10-19 | Accuzip, Inc. | Hardware server and technical method to optimize bulk printing of mailing items |
WO2015021482A1 (en) | 2013-08-09 | 2015-02-12 | KLATU Networks, LLC | System-independent data logging |
US10719804B1 (en) * | 2014-01-31 | 2020-07-21 | Advanced Technology & Research Corp. | Smartphone-controlled mailbox system |
EP2933825B1 (en) * | 2014-03-31 | 2017-07-05 | Flosfia Inc. | Crystalline multilayer structure and semiconductor device |
US20160232487A1 (en) * | 2015-02-11 | 2016-08-11 | Ben Yonker | Package Delivery System, Service, Method and Application |
US11023846B2 (en) | 2015-04-24 | 2021-06-01 | United Parcel Service Of America, Inc. | Location-based pick up and delivery services |
US10182305B2 (en) | 2015-04-24 | 2019-01-15 | United Parcel Service Of America, Inc. | Secure location-based events and notifications |
US11829927B2 (en) | 2016-05-04 | 2023-11-28 | United Parcel Service Of America, Inc. | Remote initiation of interaction by a computing entity |
US10872089B2 (en) | 2017-10-24 | 2020-12-22 | United Parcel Service Of America, Inc. | Automated occupant tracking systems and methods |
CN110166461B (en) * | 2019-05-24 | 2022-09-20 | 中国银联股份有限公司 | User unified identification processing method, device, equipment and storage medium |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020035515A1 (en) * | 2000-07-14 | 2002-03-21 | Eli Moreno | System and method for remotely coordinating the secure delivery of goods |
US20020156645A1 (en) * | 2001-01-31 | 2002-10-24 | Hansen Paul E. | Network-based solution for secure parcel delivery and pick-up |
US20050139650A1 (en) * | 1999-09-20 | 2005-06-30 | Gonzalo Steven M. | Method and system for configuring a publicly accessible computer system |
US7062471B1 (en) * | 1999-06-07 | 2006-06-13 | Nippon Telegraph And Telephone Corporation | Electronic rights information processing system, method and apparatus for carrying out same and recorded medium for program carrying out the method |
US20060163345A1 (en) * | 2005-01-21 | 2006-07-27 | Visa U.S.A. | Wireless payment methods and systems |
US20070011099A1 (en) * | 2005-07-11 | 2007-01-11 | Conrad Sheehan | SECURE ELECTRONIC TRANSACTIONS BETWEEN A MOBILE DEVICE AND OTHER MOBILE, FIXED, or VIRTUAL DEVICES |
US20080085698A1 (en) * | 2006-10-09 | 2008-04-10 | James Gamm | Device with unique identifier capability for purchasing wireless communication service |
US20080299970A1 (en) * | 2007-05-30 | 2008-12-04 | Shoptext, Inc. | Consumer Registration Via Mobile Device |
US20080313079A1 (en) * | 2007-06-14 | 2008-12-18 | Motorola, Inc. | System and method for proximity payment transaction between a wireless communication device and a point of sale terminal in conjunction with a trusted party |
US20090314835A1 (en) * | 2008-06-23 | 2009-12-24 | United Parcel Services Of America, Inc. | System for shipping an item using an electronic envelope |
US7647249B2 (en) * | 2005-02-25 | 2010-01-12 | United Parcel Service Of America, Inc. | Method for providing a shipping label via an intermediary's website |
Family Cites Families (116)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040089482A1 (en) * | 1991-04-10 | 2004-05-13 | Uship Intellectual Properties, Llc | Automated package shipping machine |
US7035832B1 (en) * | 1994-01-03 | 2006-04-25 | Stamps.Com Inc. | System and method for automatically providing shipping/transportation fees |
US5655023A (en) * | 1994-05-13 | 1997-08-05 | Pitney Bowes Inc. | Advanced postage payment system employing pre-computed digital tokens and with enhanced security |
US5774053A (en) | 1996-05-02 | 1998-06-30 | Porter; David | Storage device for the delivery and pickup of goods |
JP3752021B2 (en) | 1996-07-11 | 2006-03-08 | 株式会社イツモ | Locker device for goods distribution |
US5979750A (en) | 1996-09-12 | 1999-11-09 | Kindell; Gary J. | Computerized delivery acceptance system |
US8396811B1 (en) * | 1999-02-26 | 2013-03-12 | Syncada Llc | Validation approach for auditing a vendor-based transaction |
JPH10162065A (en) | 1996-11-28 | 1998-06-19 | Hitachi Ltd | Delivery management system |
US6010156A (en) * | 1997-09-24 | 2000-01-04 | Costar Corporation | Combined address and postage label and system for producing the same |
US6332098B2 (en) * | 1998-08-07 | 2001-12-18 | Fedex Corporation | Methods for shipping freight |
US6028517A (en) | 1998-12-23 | 2000-02-22 | Pitney Bowes Inc. | Status indicating system for indicating the deposit and withdrawal of items in a receptacle |
DE60005335T2 (en) * | 1999-02-08 | 2004-07-08 | United Parcel Service Of America, Inc. | SYSTEMS AND METHODS FOR INTERNET-CONTROLLED PACKAGE TRANSPORT |
EP2272596B1 (en) | 1999-04-07 | 2015-06-03 | Federal Express Corporation | System and method for dimensioning objects |
EP1191869A2 (en) | 1999-06-16 | 2002-04-03 | Reinhold Holtkamp | Network connected delivery box using access codes and methods for providing same |
US6323782B1 (en) | 1999-06-21 | 2001-11-27 | Freight Locker, Inc. | Unattended item delivery system |
GB2352073B (en) | 1999-07-10 | 2003-09-03 | Int Computers Ltd | Secure locker system |
SG94334A1 (en) | 1999-09-15 | 2003-02-18 | First Cube Pte Ltd | A method and system for facilitating delivery and pickup of goods |
US6300873B1 (en) | 1999-09-16 | 2001-10-09 | Atlantes Services, Inc. | Locking mechanism for use with one-time access code |
US7359887B1 (en) * | 1999-10-06 | 2008-04-15 | Stamps.Com Inc. | Apparatus, systems and methods for interfacing with digital scales configured with remote client computer devices |
US6344796B1 (en) | 1999-10-28 | 2002-02-05 | Brivo Systems, Inc. | Unattended package delivery cross-docking apparatus and method |
US6933832B1 (en) | 1999-11-09 | 2005-08-23 | Noel Simms | Automated receiving and delivery system and method |
US7158941B1 (en) | 1999-12-03 | 2007-01-02 | Thompson Clifford C | Residential and business logistics system and method |
US6950803B2 (en) | 1999-12-30 | 2005-09-27 | Tiley Stephen D | Method of providing an automated package receptacle for the receipt, storage and pickup of a package at a retail site and for providing marketing and other communications to package recipients |
US6612489B2 (en) | 2000-01-31 | 2003-09-02 | Deliverez, Llc. | System for secured delivery of packages or other items |
IL134828A0 (en) | 2000-03-01 | 2001-05-20 | Eship 4U Com Inc | System for delivery and receipt of dispatches especially useful for e-commerce |
CA2340823A1 (en) * | 2000-03-15 | 2001-09-15 | Dennis Kornacki | Pricing and costing system, method and computer program product |
US7774284B2 (en) * | 2000-03-27 | 2010-08-10 | Stamps.Com Inc. | Apparatus, systems and methods for online, multi-parcel, multi-carrier, multi-service enterprise parcel shipping management |
EP1277148A1 (en) * | 2000-03-28 | 2003-01-22 | Stamps.Com Inc. | Apparatus, systems and methods for online, multi-parcel, multi-carrier, multi-service parcel returns shipping management |
US20010040422A1 (en) | 2000-04-06 | 2001-11-15 | Gramlich Jeffrey D. | Method and system for providing and using a parcel keeper |
US20010049636A1 (en) | 2000-04-17 | 2001-12-06 | Amir Hudda | System and method for wireless purchases of goods and services |
US20020032613A1 (en) | 2000-04-18 | 2002-03-14 | Buettgenbach Thomas H. | Methods and systems for the physical delivery of goods ordered through an electronic network |
US6967575B1 (en) | 2000-04-28 | 2005-11-22 | Intel Corporation | Methods and apparatus for unattended pickups and deliveries |
US20040211834A1 (en) * | 2000-05-11 | 2004-10-28 | United Parcel Service Of America, Inc. | Systems and methods of modifying item delivery utilizing linking |
US20020016726A1 (en) | 2000-05-15 | 2002-02-07 | Ross Kenneth J. | Package delivery systems and methods |
US6480758B2 (en) | 2000-05-25 | 2002-11-12 | Ebox Inc. | Package delivery system |
US6820805B2 (en) | 2000-06-03 | 2004-11-23 | Ebox Usa Inc. | Computerized recording and notification of the delivery and pickup of retail goods |
US6678666B1 (en) * | 2000-06-05 | 2004-01-13 | Van W. Boulware | Method of conducting anti-fraud electronic bank security transactions having price-date-time variables and calculating apparatus thereof |
US6756879B2 (en) | 2000-07-11 | 2004-06-29 | Ideaflood, Inc. | Method and apparatus for securing delivery of goods |
US6748295B2 (en) | 2000-07-26 | 2004-06-08 | Northrop Grumman Corporation | Item delivery and retrieval system |
SG98425A1 (en) | 2000-09-13 | 2003-09-19 | First Cube Pte Ltd | A method and system using sms notification for facilitating delivery of goods |
JP2002117455A (en) | 2000-10-10 | 2002-04-19 | Fujitsu Ltd | Locker type commodity delivery system |
US6688435B1 (en) | 2000-11-01 | 2004-02-10 | Craig Alexander Will | Electronic ordering of goods with delivery by automatic drive-up storage device |
US20020103724A1 (en) | 2000-12-01 | 2002-08-01 | Stephen Huxter | Courier independent system and method for the delivery of goods ordered by the internet |
US20020107820A1 (en) | 2000-12-01 | 2002-08-08 | Stephen Huxter | Single courier model for the delivery of goods ordered by the internet |
US6595342B1 (en) | 2000-12-07 | 2003-07-22 | Sony Corporation | Method and apparatus for a biometrically-secured self-service kiosk system for guaranteed product delivery and return |
US7110958B2 (en) | 2000-12-08 | 2006-09-19 | Ping Yang | Method and apparatus for mobile pickup stations |
US6950944B2 (en) * | 2000-12-18 | 2005-09-27 | David Frank Yager | Security code activated access control system |
US20020184497A1 (en) | 2000-12-28 | 2002-12-05 | Gage Michael J. | Automated multi-user package retrieval and storage system |
US7343317B2 (en) | 2001-01-18 | 2008-03-11 | Nokia Corporation | Real-time wireless e-coupon (promotion) definition based on available segment |
US20020147919A1 (en) | 2001-02-03 | 2002-10-10 | Gentry Daniel W. | Secured delivery system for unattended receiving and shipping of parcels and letters |
WO2002066344A1 (en) | 2001-02-20 | 2002-08-29 | United States Postal Service | Universal delivery and collection box unit (udcbu) |
US6974928B2 (en) | 2001-03-16 | 2005-12-13 | Breakthrough Logistics Corporation | Method and apparatus for efficient package delivery and storage |
US7653457B2 (en) | 2001-03-16 | 2010-01-26 | Breakthrough Logistics Corporation | Method and system for efficient package delivery and storage |
US6694217B2 (en) | 2001-05-24 | 2004-02-17 | Breakthrough Logistics Corporation | Automated system for efficient article storage and self-service retrieval |
US20020178074A1 (en) | 2001-05-24 | 2002-11-28 | Gregg Bloom | Method and apparatus for efficient package delivery and storage |
US20050061877A1 (en) | 2001-05-21 | 2005-03-24 | John Stevens | System and method for unattended delivery |
US20020178016A1 (en) | 2001-05-23 | 2002-11-28 | Mclellan Kerry | Method and apparatus for distributing parcels |
JP3748790B2 (en) | 2001-06-12 | 2006-02-22 | 喜久雄 金子 | Courier delivery system and method thereof |
DE10131304A1 (en) | 2001-07-02 | 2003-01-23 | Thomas Brandner | Location independent postal system uses code obtained by telephoning that is entered on item |
US6791450B2 (en) | 2001-07-31 | 2004-09-14 | Security People, Inc. | Networked digital locker lock system |
JP2003058790A (en) | 2001-08-20 | 2003-02-28 | Ibm Japan Ltd | Article delivery method and system, locker management server, locker opening and closing controller, and article delivery request reception device |
US6690997B2 (en) | 2001-09-13 | 2004-02-10 | M.A. Rivalto, Inc. | System for automated package-pick up and delivery |
SG114505A1 (en) | 2001-10-17 | 2005-09-28 | First Cube Pte Ltd | System and method for facilitating delivery and return service |
GB2382421A (en) | 2001-11-26 | 2003-05-28 | Bybox Holdings Ltd | Collection and delivery system |
US20030172028A1 (en) * | 2002-03-07 | 2003-09-11 | International Business Machines Corporation | Authorization of payment for a commercial transaction via a bluetooth enabled device |
GB2387259A (en) | 2002-04-02 | 2003-10-08 | Sendo Int Ltd | Method for obtaining a postage verification code |
US20040149822A1 (en) | 2002-05-03 | 2004-08-05 | John Stevens | Delivery system and method using an electronic tag |
US20030217018A1 (en) | 2002-05-17 | 2003-11-20 | Groff Jason J. | System and method for conducting a shipping transaction |
US20040230601A1 (en) * | 2002-09-09 | 2004-11-18 | Joao Raymond A. | Apparatus and method for facilitating shipping commerce |
US6845909B2 (en) | 2002-10-31 | 2005-01-25 | United Parcel Service Of America, Inc. | Systems and methods of inventory management utilizing unattended facilities |
US20040133446A1 (en) | 2002-11-01 | 2004-07-08 | United Parcel Service Of America, Inc. | Alternate delivery location methods and systems |
SE0300585L (en) * | 2003-03-04 | 2004-09-05 | Anna Karin Saetherblom | Mailbox |
US20050027608A1 (en) | 2003-07-29 | 2005-02-03 | Andreas Wiesmuller | System and method for providing commercial services over a wireless communication network |
DE10340904A1 (en) | 2003-09-02 | 2005-03-31 | Deutsche Post Ag | Method and arrangement for delivery of a shipment |
US20050075989A1 (en) | 2003-10-07 | 2005-04-07 | Pitney Bowes Incorporated | Method for securely storing objects |
US20050080749A1 (en) * | 2003-10-08 | 2005-04-14 | Pitney Bowes Incorporated | System and method for real time adaptive class and special services determination |
US7075451B2 (en) | 2003-10-20 | 2006-07-11 | X-Cube Co., Ltd. | Delivery box system and reserving method and charging method therefor |
US20050114221A1 (en) * | 2003-11-21 | 2005-05-26 | United Parcel Service Of America, Inc. | Systems and methods for using a web portal to integrate into a carrier return system |
US7757946B2 (en) * | 2004-04-16 | 2010-07-20 | Acme Scale Company, Inc. | Material transport in-motion product dimensioning system and method |
US20050278263A1 (en) | 2004-06-11 | 2005-12-15 | Hollander Alan R | System and method for variable price postage stamp and billing |
DE102004036191A1 (en) * | 2004-07-26 | 2006-03-23 | Deutsche Post Ag | Method and device for creating and selling payment stamps for sending mail |
US20060089883A1 (en) | 2004-10-26 | 2006-04-27 | James Jeffery Peoples | Apparatus and method for facilitating and augmenting delivery confirmation |
EP1677258A3 (en) * | 2004-12-15 | 2007-12-19 | Die Schweizerische Post | Device for creating franking for postage |
US8700729B2 (en) * | 2005-01-21 | 2014-04-15 | Robin Dua | Method and apparatus for managing credentials through a wireless network |
FR2881250B1 (en) | 2005-01-27 | 2007-06-15 | Jean Luc Jouvin | PRE-POSTAGE METHOD FOR FOLLOWING COURRIERS |
US20060173797A1 (en) * | 2005-01-31 | 2006-08-03 | Robert Sheehan | Method for tracking mail piece data |
FR2888024B1 (en) | 2005-06-30 | 2007-10-12 | Neopost Ind Sa | METHOD OF AUTOMATICALLY PAYING A POSTAGE SERVICE |
EP1907943A4 (en) * | 2005-07-13 | 2011-04-06 | United Parcel Service Inc | Systems and methods for forecasting container density |
FR2890770B1 (en) | 2005-09-09 | 2007-12-07 | Neopost Ind Sa | METHOD FOR DELIVERING POSTAGE SERVICE THROUGH A COMMUNICATION NETWORK |
FR2890769B1 (en) | 2005-09-09 | 2008-03-28 | Neopost Ind Sa | METHOD FOR OBTAINING POSTAGE CREDIT THROUGH A TELECOMMUNICATION NETWORK |
US8108321B2 (en) | 2006-01-12 | 2012-01-31 | Urbissimo, Inc. | System and method for shipping and delivering parcels to a virtual address |
FR2896606B1 (en) | 2006-01-23 | 2008-06-06 | Neopost Technologies Sa | POSTAGE PAYMENT METHOD THROUGH A TELECOMMUNICATION NETWORK |
JP4812089B2 (en) * | 2006-02-24 | 2011-11-09 | キヤノン株式会社 | Printing apparatus and connection method thereof |
US8662384B2 (en) | 2006-02-28 | 2014-03-04 | Google Inc. | Text message payment |
CA2647074A1 (en) | 2006-03-21 | 2007-09-27 | Phone1, Inc. | Financial transactions using a communication device |
US8010463B2 (en) | 2006-06-19 | 2011-08-30 | United Parcel Services Of America, Inc. | Method, system, carrier server and mobile device for shipping a package without the shipper being required to apply a shipping label |
EP2800065B1 (en) * | 2006-10-27 | 2017-05-10 | Deutsche Post AG | Method for creating a label, computer program product and system for carrying out the method |
EP1921586A1 (en) | 2006-11-13 | 2008-05-14 | Deutsche Post AG | Method and arrangement of devices for operating an electronic package mailbox |
US20080121682A1 (en) | 2006-11-29 | 2008-05-29 | International Business Machines Corporation | System and method to enhance security surrounding package delivery |
WO2008107003A1 (en) | 2007-03-08 | 2008-09-12 | Joseph Bramante | Method and apparatus for buying items, particularly cds or dvds or similar products |
CA2687386A1 (en) * | 2007-05-15 | 2008-11-20 | 8D Technologies Inc. | A method and apparatus for managing shipping and advertisement information in a communications environment |
WO2009052143A1 (en) * | 2007-10-16 | 2009-04-23 | Accu-Sort Systems, Inc. | Dimensioning and barcode reading system |
US20090132438A1 (en) | 2007-11-20 | 2009-05-21 | At&T Knowledge Ventures, L.P. | Parcel carrier billing service |
US7409353B1 (en) * | 2007-12-07 | 2008-08-05 | Z-Firm Llc | Methods and systems for producing shipping labels |
US7815112B2 (en) | 2007-12-27 | 2010-10-19 | Robert Bosch Gmbh | Secure parcel delivery in the absence of the intended recipient |
US8596541B2 (en) * | 2008-02-22 | 2013-12-03 | Qualcomm Incorporated | Image capture device with integrated barcode scanning |
US20090259556A1 (en) * | 2008-04-08 | 2009-10-15 | Restaurant Technology, Inc. | System and method for enhanced customer kiosk ordering |
US20100293065A1 (en) | 2008-08-14 | 2010-11-18 | Mike Brody | System and method for paying a merchant using a cellular telephone account |
US8521653B2 (en) * | 2008-11-21 | 2013-08-27 | Psi Systems, Inc. | System and method for providing postage indicia |
US8466380B2 (en) * | 2008-11-27 | 2013-06-18 | Teraoka Seiko Co., Ltd. | Apparatus and method for measuring articles including conveyor-weighers supported on weighing unit |
US20100257065A1 (en) * | 2009-04-02 | 2010-10-07 | Shekhar Gupta | Enhanced fraud protection systems and methods |
US8284988B2 (en) * | 2009-05-13 | 2012-10-09 | Applied Vision Corporation | System and method for dimensioning objects using stereoscopic imaging |
US9697510B2 (en) | 2009-07-23 | 2017-07-04 | Boku, Inc. | Systems and methods to facilitate retail transactions |
US8407155B2 (en) * | 2009-12-11 | 2013-03-26 | Pitney Bowes Inc. | On-line mail processing system and mobile device application therefor |
US10032239B2 (en) | 2010-06-10 | 2018-07-24 | United Parcel Service Of America, Inc. | Enhanced payments for shipping |
CA3081497A1 (en) * | 2014-10-02 | 2016-04-07 | Ecoatm, Llc | Wireless-enabled kiosk for recycling consumer devices |
-
2010
- 2010-06-10 US US12/813,096 patent/US10032239B2/en active Active
- 2010-06-11 US US12/813,998 patent/US9082096B2/en active Active
-
2011
- 2011-03-02 WO PCT/US2011/026770 patent/WO2011156023A2/en active Application Filing
- 2011-03-02 EP EP11709527.3A patent/EP2580725A4/en not_active Ceased
- 2011-03-02 CA CA2798793A patent/CA2798793C/en active Active
- 2011-03-02 WO PCT/US2011/026769 patent/WO2011156022A1/en active Application Filing
- 2011-03-02 CA CA2798791A patent/CA2798791C/en active Active
- 2011-03-02 EP EP11714145.7A patent/EP2580727A4/en not_active Ceased
-
2015
- 2015-06-02 US US14/728,569 patent/US10643293B2/en active Active
-
2018
- 2018-07-24 US US16/043,649 patent/US11170458B2/en active Active
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7062471B1 (en) * | 1999-06-07 | 2006-06-13 | Nippon Telegraph And Telephone Corporation | Electronic rights information processing system, method and apparatus for carrying out same and recorded medium for program carrying out the method |
US20050139650A1 (en) * | 1999-09-20 | 2005-06-30 | Gonzalo Steven M. | Method and system for configuring a publicly accessible computer system |
US20020035515A1 (en) * | 2000-07-14 | 2002-03-21 | Eli Moreno | System and method for remotely coordinating the secure delivery of goods |
US20020156645A1 (en) * | 2001-01-31 | 2002-10-24 | Hansen Paul E. | Network-based solution for secure parcel delivery and pick-up |
US20060163345A1 (en) * | 2005-01-21 | 2006-07-27 | Visa U.S.A. | Wireless payment methods and systems |
US7647249B2 (en) * | 2005-02-25 | 2010-01-12 | United Parcel Service Of America, Inc. | Method for providing a shipping label via an intermediary's website |
US20070011099A1 (en) * | 2005-07-11 | 2007-01-11 | Conrad Sheehan | SECURE ELECTRONIC TRANSACTIONS BETWEEN A MOBILE DEVICE AND OTHER MOBILE, FIXED, or VIRTUAL DEVICES |
US20080085698A1 (en) * | 2006-10-09 | 2008-04-10 | James Gamm | Device with unique identifier capability for purchasing wireless communication service |
US20080299970A1 (en) * | 2007-05-30 | 2008-12-04 | Shoptext, Inc. | Consumer Registration Via Mobile Device |
US20080313079A1 (en) * | 2007-06-14 | 2008-12-18 | Motorola, Inc. | System and method for proximity payment transaction between a wireless communication device and a point of sale terminal in conjunction with a trusted party |
US20090314835A1 (en) * | 2008-06-23 | 2009-12-24 | United Parcel Services Of America, Inc. | System for shipping an item using an electronic envelope |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130151411A1 (en) * | 2011-12-09 | 2013-06-13 | Worldpasskey, Inc. | Digital authentication and security method and system |
WO2013148706A1 (en) * | 2012-03-26 | 2013-10-03 | Ebay Inc. | Unified service for providing shipping services |
US20150066797A1 (en) * | 2013-09-04 | 2015-03-05 | Christopher Scott Outwater | System and method for enhancing delivery security and preventing fraud |
US9082099B1 (en) * | 2014-07-18 | 2015-07-14 | Dmitriy Kolchin | System and method for context-sensitive delivery notification |
US11281850B2 (en) * | 2017-12-28 | 2022-03-22 | A9.Com, Inc. | System and method for self-filing customs entry forms |
Also Published As
Publication number | Publication date |
---|---|
CA2798793C (en) | 2017-08-01 |
US10032239B2 (en) | 2018-07-24 |
CA2798793A1 (en) | 2011-12-15 |
US11170458B2 (en) | 2021-11-09 |
CA2798791A1 (en) | 2011-12-15 |
CA2798791C (en) | 2019-02-26 |
US10643293B2 (en) | 2020-05-05 |
EP2580725A4 (en) | 2017-07-26 |
US20150262320A1 (en) | 2015-09-17 |
WO2011156022A1 (en) | 2011-12-15 |
US9082096B2 (en) | 2015-07-14 |
WO2011156023A2 (en) | 2011-12-15 |
US20180330463A1 (en) | 2018-11-15 |
EP2580727A1 (en) | 2013-04-17 |
EP2580727A4 (en) | 2014-04-30 |
WO2011156023A3 (en) | 2016-08-11 |
US20110307357A1 (en) | 2011-12-15 |
EP2580725A2 (en) | 2013-04-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11170458B2 (en) | Enhanced payments for shipping | |
US11907896B2 (en) | Methods, apparatuses and computer program products for facilitating label less returns | |
CN107408235B (en) | System and method for facilitating the delivery of packages of returned merchandise | |
US10664787B2 (en) | Customer controlled management of shipments | |
US9916557B1 (en) | Systems and methods for item delivery and pick-up using social networks | |
US20100036674A1 (en) | Method for shipping deliveries; shipping station and logistics system | |
WO2012161728A1 (en) | Customer controlled management of shipments | |
WO2012161732A2 (en) | Customer controlled management of shipments | |
WO2012161729A2 (en) | Customer controlled management of shipments | |
WO2014146169A1 (en) | Systems and methods for managing sending of items | |
WO2012161731A2 (en) | Customer controlled management of shipments | |
WO2012161730A2 (en) | Customer controlled management of shipments | |
US20140344180A1 (en) | Systems and methods for importing items | |
US20150371183A1 (en) | Systems and methods for confidential shipping | |
CA2715193A1 (en) | Method for operating a shipping process within a logistics system | |
JP4949784B2 (en) | Delivery information processing terminal and information processing program | |
CN111815246A (en) | Sending cabinet machine, method and computer readable storage medium | |
US20090182639A1 (en) | Shipping station and logistics system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: UNITED PARCEL SERVICE OF AMERICA, INC., GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PARAMESWARAN, SATHIYAN;BESSERER, BRUCE;COSTIDES, NICHOLAS;AND OTHERS;REEL/FRAME:029105/0880 Effective date: 20100609 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
CC | Certificate of correction | ||
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |