IP Library Granted Patent US 10,686,933
Granted Patent B2
US 10,686,933 · App. 16/037,132 · Granted Jun 16, 2020

Systems, methods, and computer-readable media for timer-based management of communication devices

Inventor: John David Putman (Olive Branch, MS)
Assignee: FedEx Corporate Services, Inc.
H04M1/72577H04W4/40H04W4/42H04W52/0254H04W52/0274H04M1/72566Y02D70/00
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 10,686,933
App. No.
16/037,132
Granted
Jun 16, 2020
Kind
B2
Abstract

A method of management of a communication device in an aircraft may include transitioning the communication device from a normal mode to a disabled mode based on a calculated device sleep time based on data associated with transportation information of the device. One of these modes may be a state of the device in which a transceiver of the device is deactivated and the other mode may be a state of the device in which the transceiver is activated. Therefore, the device sleep time determines when the wireless device's transceiver may not be activated.

Claims (38)

1. A device, comprising:

a transceiver;

a memory device configured to store a set of instructions; and

a processor configured to execute the set of instructions to:

calculate a device sleep time based on data relating to transportation of the device, the device sleep time including a time buffer;

transition the device from a first mode in which the transceiver is powered on, to a second mode in which the transceiver is powered off; and

transition the device from the second mode to the first mode after expiry of the device sleep time.

2. The device of claim 1 , wherein the time buffer is based on a change in a time zone between an origin and a destination associated with the transportation of the device.

3. The device of claim 1 , wherein the time buffer is a predetermined amount of time.

4. The device of claim 1 , wherein the time buffer is based on a statistical analysis of schedules associated with historical route information for the transportation of the device.

5. The device of claim 1 , wherein the time buffer is based on a user input.

6. The device of claim 1 , wherein the processor is further configured to execute the set of instructions to:

receive the data relating to transportation of the device from a remote device; and

determine the time buffer based on the received data.

7. The device of claim 1 , wherein the time buffer includes an adjustment for daylight savings time.

8. The device of claim 1 , wherein the time buffer is based on at least one of a holiday or a weekend day.

9. The device of claim 1 , wherein the time buffer is based on a duration of time between midnight and a subsequent delivery time.

10. The device of claim 1 , wherein the time buffer is based on a schedule delay associated with the transportation of the device.

11. The device of claim 10 , wherein the schedule delay is associated with an aircraft carrying the device.

12. The device of claim 11 , wherein the processor is further configured to execute the set of instructions to:

determine, upon expiration of the device sleep time, whether the aircraft is in flight;

calculate a device re-sleep time when the aircraft is determined to be in flight;

transition the device from the first mode to the second mode; and

transition the device from the second mode to the first mode after expiration of the device re-sleep time.

13. The device of claim 12 , wherein the processor is further configured to execute the set of instructions to calculate the device re-sleep time based on average flight times between an origin and a destination associated with the flight.

14. The device of claim 1 , wherein the processor is further configured to execute the set of instructions to:

receive, upon expiration of the device sleep time, information regarding a change in the delivery schedule;

calculate a device re-sleep time based on the received information;

transition the device from the first mode to the second mode; and

transition the device from the second mode to the first mode after expiration of the device re-sleep time.

15. The device of claim 1 , wherein the data relating to the transportation of the device is stored in the memory.

16. The device of claim 1 , wherein the data relating to the transportation of the device includes at least one of a location of an origin, a location of a destination, an expected duration of travel from the origin to the destination, an origin time zone, a destination time zone, an expected delivery time of the device, or schedule details of at least one transport vehicle associated with transportation of the device.

17. The device of claim 1 , wherein the processor is further configured to execute the set of instructions to receive transportation data after a predetermined interval of time.

18. The device of claim 1 , wherein the processor is further configured to execute the set of instructions to transition the device from the first mode to the second mode upon detection of a takeoff of an aircraft associated with the transportation of the device.

19. The device of claim 18 , further including a sensor configured to detect the takeoff of the aircraft.

20. The device of claim 18 , wherein the processor is further configured to execute the set of instructions to:

receive data indicative of the takeoff from an external source; and

transition the device from the first mode to the second mode in response to the received data.

Assignments (2)
MERGER Recorded Jul 22, 2024
From: FEDEX CORPORATE SERVICES, INC.
To: FEDERAL EXPRESS CORPORATION
Reel/Frame 068042/0510 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 17, 2018
From: PUTMAN, JOHN DAVID
To: FEDEX CORPORATE SERVICES, INC.
Reel/Frame 046367/0813 →
Continuity (6)
Continuation 15658646 · Jul 25, 2017
Continuation 15238274 · Aug 16, 2016
Continuation 14794921 · Jul 9, 2015
Continuation 13868770 · Apr 23, 2013
Provisional Application 61642723 · May 4, 2012
Related Publication 20180367664A1 · Dec 20, 2018