IP Library Granted Patent US 12,603,855
Granted Patent B2
US 12,603,855 · App. 18/389,226 · Granted Apr 14, 2026

Apparatus, system and methods for managing private content delivery in association with a shipment

Inventor: Antonio D. Young (Naperville, IL)
H04L51/10G06Q10/0833H04L51/046H04L51/52
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,603,855
App. No.
18/389,226
Granted
Apr 14, 2026
Kind
B2
Abstract

A client-server computer system includes a client-side application executing on a computing device, operative to communicate with a native application executing on the computing device to obtain and store a multi-media content file generated using the native application in a native content file format. A server includes a server-side application operative to communicate with the client-side application, and operative to: create an association between the multi-media content file, a recipient computing device, and a courier tracking number; determine that delivery of a parcel associated with the courier tracking number has occurred; and transmit the multi-media content file in the native content file format to the recipient device in response to determining that delivery of the parcel has occurred.

Claims (60)

1 . A cloud server computer system comprising:

a message content management service application server comprising at least one hardware processor, operative to:

communicate with a plurality of on-demand delivery service servers to obtain information related to a plurality of deliveries;

provide an instance of a message content management service application to a client device via a web browser executed on the client device;

receive a first portion of delivery data from the instance of the message content management service application for a scheduled delivery;

receive a second portion of the delivery data from an on-demand delivery service server, by using the first portion of the delivery data to identify an on-demand delivery service associated with the on-demand delivery service server, and to identify the second portion of the delivery data;

obtain, via the instance of the message content management service application, a user generated multi-media content file generated by a content creation application executed on the client device, the user generated multi-media content file associated with the first portion of delivery data via user input received via the instance of the message content management service application;

determine that the scheduled delivery has occurred using at least the first portion of delivery data, by communicating with the on-demand delivery service server; and

transmit the user generated multi-media content file, to a recipient device of a recipient of the scheduled delivery, in response to determining that the scheduled delivery has occurred, wherein the recipient device is capable of using the user generated multi-media content file independently without interaction between the recipient device and the message content management service application server.

2 . The cloud server computer system of claim 1 , wherein the message content management service application server is further operative to:

transmit the user generated multi-media content file to the recipient device at a location specified for the scheduled delivery within the second portion of delivery data, in response to determining that the scheduled delivery has occurred.

3 . The cloud server computer system of claim 1 , wherein the message content management service application server is further operative to:

receive the first portion of delivery data from the instance of a message content management service application comprising recipient contact information, and the user generated multi-media content file.

4 . The cloud server computer system of claim 1 , wherein the message content management service application server is further operative to:

receive the first portion of delivery data from the instance of a message content management service application comprising recipient location coordinates.

5 . The cloud server computer system of claim 1 , wherein the message content management service application server is further operative to:

determine that the scheduled delivery has occurred using the second portion of delivery data comprising location coordinates of a delivery agent delivering the scheduled delivery.

6 . The cloud server computer system of claim 1 , wherein the message content management service application server is further operative to:

create an association between the user generated multi-media content file, the client device, a recipient device, and a tracking number provided by the on-demand delivery service server.

7 . The cloud server computer system of claim 1 , wherein the message content management service application server is further operative to:

provide a graphical user interface (GUI) for display on the client device, the GUI corresponding to the instance of the message content management service application.

8 . The cloud server computer system of claim 1 , wherein the message content management service application server is further operative to:

provide a link to the recipient device to access the user generated multi-media content file on a social media server.

9 . The cloud server computer system of claim 1 , wherein message content management service application server is further operative to:

access a social media server to transmit the user generated multi-media content file to the recipient device via a social media platform.

10 . A method of operating a message content management service application server comprising:

communicating with a plurality of on-demand delivery service servers to obtain information related to a plurality of deliveries;

providing an instance of a message content management service application to a client device via a web browser executed on the client device;

receiving a first portion of delivery data from the instance of the message content management service application for a scheduled delivery;

receiving a second portion of the delivery data from an on-demand delivery service server, by using the first portion of the delivery data to identify an on-demand delivery service associated with the on-demand delivery service server, and to identify the second portion of the delivery data;

obtaining, via the instance of the message content management service application, a user generated multi-media content file generated by a content creation application executed on the client device, the user generated multi-media content file associated with the first portion of delivery data via user input received via the instance of the message content management service application;

determining that the scheduled delivery has occurred using at least the first portion of delivery data, by communicating with the on-demand delivery service server; and

transmitting the user generated multi-media content file, to a recipient device of a recipient of the scheduled delivery, in response to determining that the scheduled delivery has occurred, wherein the recipient device is capable of using the user generated multi-media content file independently without interaction between the recipient device and the message content management service application server.

11 . The method of claim 10 , further comprising:

transmitting the user generated multi-media content file to the recipient device at a location specified for the scheduled delivery within the second portion of delivery data, in response to determining that the scheduled delivery has occurred.

12 . The method of claim 10 , further comprising:

receiving the first portion of delivery data from the instance of a message content management service application comprising recipient contact information, and the user generated multi-media content file.

13 . The method of claim 10 , further comprising:

receiving the first portion of delivery data from the instance of a message content management service application comprising recipient location coordinates.

14 . The method of claim 10 , further comprising:

determining that the scheduled delivery has occurred using the second portion of delivery data comprising location coordinates of a delivery agent delivering the scheduled delivery.

15 . The method of claim 10 , further comprising:

creating an association between the user generated multi-media content file, the client device, a recipient device, and a tracking number provided by on-demand delivery service server.

16 . The method of claim 10 , further comprising:

providing a graphical user interface (GUI) for display on the client device, the GUI corresponding to the instance of the message content management service application.

17 . A non-transitory, non-volatile computer readable memory comprising:

executable instructions for execution by at least one processor, that when executed cause the at least one processor to:

communicate with a plurality of on-demand delivery service servers to obtain information related to a plurality of deliveries;

provide an instance of a message content management service application to a client device via a web browser executed on the client device;

receive a first portion of delivery data from the instance of the message content management service application for a scheduled delivery;

receive a second portion of the delivery data from an on-demand delivery service server, by using the first portion of the delivery data to identify an on-demand delivery service associated with the on-demand delivery service server, and to identify the second portion of the delivery data;

obtain, via the instance of the message content management service application, a user generated multi-media content file generated by a content creation application executed on the client device, the user generated multi-media content file associated with the first portion of delivery data via user input received via the instance of the message content management service application;

determine that the scheduled delivery has occurred using at least the first portion of delivery data, by communicating with the on-demand delivery service server; and

transmit the user generated multi-media content file, to a recipient device of a recipient of the scheduled delivery, in response to determining that the scheduled delivery has occurred, wherein the recipient device is capable of using the user generated multi-media content file independently without interaction between the recipient device and the message content management service application server.

18 . The non-transitory, non-volatile computer readable memory of claim 17 , wherein the executable instructions when executed, cause the at least one processor to:

transmit the user generated multi-media content file to the recipient device at a location specified for the scheduled delivery within the second portion of delivery data, in response to determining that the scheduled delivery has occurred.

19 . The non-transitory, non-volatile computer readable memory of claim 17 , wherein the executable instructions when executed, cause the at least one processor to:

receive the first portion of delivery data from the instance of a message content management service application comprising recipient contact information, and the user generated multi-media content file.

20 . The non-transitory, non-volatile computer readable memory of claim 17 , wherein the executable instructions when executed, cause the at least one processor to:

receive the first portion of delivery data from the instance of a message content management service application comprising recipient location coordinates.

Continuity (2)
Continuation 17866266 · Jul 15, 2022
Related Publication 20240080290A1 · Mar 7, 2024
References Cited (33)
US 8046266B1 · Geller et al. · 2011 [cited by applicant]
US 9105016B2 · Briggman et al. · 2015 [cited by applicant]
US 9619955B2 · Eichenblatt · 2017 [cited by applicant]
US 9830628B1 · Sayre, III · 2017 [cited by applicant]
US 9990626B1 · Labanca, Jr. et al. · 2018 [cited by applicant]
US 10078808B1 · Sibon · 2018 [cited by applicant]
US 10354216B2 · Gillen et al. · 2019 [cited by applicant]
US 10373096B2 · Duquene et al. · 2019 [cited by applicant]
US 10592849B2 · Daoura et al. · 2020 [cited by applicant]
US 11115629B1 · Lemberger · 2021 [cited by examiner]
US 20090076918A1 · Blanchet · 2009 [cited by examiner]
US 20100004935A1 · Wain · 2010 [cited by applicant]
US 20120089529A1 · Uslontsev et al. · 2012 [cited by applicant]
US 20120303539A1 · Marcus et al. · 2012 [cited by applicant]
US 20130024525A1 · Brady et al. · 2013 [cited by applicant]
US 20130226728A1 · Oghittu · 2013 [cited by examiner]
US 20130226740A1 · Biliosa · 2013 [cited by applicant]
US 20130346337A1 · O'Donnell et al. · 2013 [cited by applicant]
US 20140172734A1 · Ginda · 2014 [cited by examiner]
US 20140258424A1 · Ganesh · 2014 [cited by examiner]
US 20150088781A1 · Gillen et al. · 2015 [cited by applicant]
US 20150227883A1 · Murphy, Jr. · 2015 [cited by examiner]
US 20160026974A1 · Zhao · 2016 [cited by examiner]
US 20160036739A1 · Glass et al. · 2016 [cited by applicant]
US 20160171427A1 · Cao · 2016 [cited by applicant]
US 20160323218A1 · Sadanandan · 2016 [cited by examiner]
US 20160328669A1 · Droege · 2016 [cited by examiner]
US 20180247252A1 · Duquene et al. · 2018 [cited by applicant]
US 20190019141A1 · Torii et al. · 2019 [cited by applicant]
US 20190354931A1 · Amato · 2019 [cited by examiner]
US 20200051015A1 · Davis et al. · 2020 [cited by applicant]
US 20200082334A1 · Dotterweich et al. · 2020 [cited by applicant]
CA 2917314A1 · 2017 [cited by applicant]