Communication scheduling
First Claim
Patent Images
1. A method for scheduling a network communication, the method comprising:
- receiving, at a communication scheduling apparatus, a network communication request in a downlink request from an operator or an application server;
determining, by the communication scheduling apparatus, a scheduling priority based on the network communication request;
assigning, by the communication scheduling apparatus, a communication time specifying when the network communication will be available for a Machine-to-Machine (M2M) device based on the scheduling priority and network resource utilization; and
initiating a sleep operational mode to the M2M device if the assigned communication time has not yet occurred,wherein the network resource utilization is based on statistics on network traffic and/or network control signaling,wherein the communication time for the M2M device is specifically assigned to correspond to a future time in which the communication scheduling apparatus determines a network capacity is expected to be sufficient to satisfy the network communication request based on the statistics on network traffic and/or network control signaling,wherein the network communication is intended for the M2M device, andwherein the step of assigning the communication time comprises assigning the communication time for the M2M device using a bottom-up approach in which time slots corresponding to lower expected network traffic are assigned prior to time slots corresponding to higher expected network traffic.
1 Assignment
0 Petitions
Accused Products
Abstract
A method and device for network communication request scheduling is presented. Example embodiments are directed towards the dynamic scheduling of communications based on real time network resource utilization and associated stored statistics.
23 Citations
40 Claims
-
1. A method for scheduling a network communication, the method comprising:
-
receiving, at a communication scheduling apparatus, a network communication request in a downlink request from an operator or an application server; determining, by the communication scheduling apparatus, a scheduling priority based on the network communication request; assigning, by the communication scheduling apparatus, a communication time specifying when the network communication will be available for a Machine-to-Machine (M2M) device based on the scheduling priority and network resource utilization; and initiating a sleep operational mode to the M2M device if the assigned communication time has not yet occurred, wherein the network resource utilization is based on statistics on network traffic and/or network control signaling, wherein the communication time for the M2M device is specifically assigned to correspond to a future time in which the communication scheduling apparatus determines a network capacity is expected to be sufficient to satisfy the network communication request based on the statistics on network traffic and/or network control signaling, wherein the network communication is intended for the M2M device, and wherein the step of assigning the communication time comprises assigning the communication time for the M2M device using a bottom-up approach in which time slots corresponding to lower expected network traffic are assigned prior to time slots corresponding to higher expected network traffic. - View Dependent Claims (2, 3, 4, 5, 6, 7, 36, 37)
-
-
8. A method for scheduling a network communication, the method comprising:
-
retrieving, by a communication scheduling apparatus, a network communication priority and/or a parameter associated with a network communication request in a downlink request from an operator or application server; determining, by the communication scheduling apparatus, a scheduling priority based on the network communication priority and/or the parameter; pre-emptively assigning, by the communication scheduling apparatus, a communication time, based on the scheduling priority and resource utilization, specifying when the network communication will be available for a Machine-to-Machine (M2M) device based on the scheduling priority and network resource utilization; and initiating a sleep operational mode to the M2M device if the assigned communication time has not yet occurred, wherein the communication time for the M2M device is specifically assigned to correspond to a future time in which the communication scheduling apparatus determines a network capacity is expected to be sufficient to satisfy the network communication request based on the statistics on network traffic and/or network control signaling, wherein the network resource utilization is based on statistics on network traffic and/or network control signaling, wherein the network communication is intended for the M2M device, and wherein the step of pre-emptively assigning the communication time comprises pre-emptively assigning the communication time for the M2M device using a bottom-up approach in which time slots corresponding to lower expected network traffic are assigned prior to time slots corresponding to higher expected network traffic. - View Dependent Claims (9, 10, 11, 38)
-
-
12. A communication scheduling apparatus, comprising:
-
a communications port configured to receive a network communication request in a downlink request from an operator or an application server; and a processor configured to determine a scheduling priority based on the network communication request, assign a communication time specifying when network communication will be available for a Machine-to-Machine (M2M) device based on the scheduling priority and network resource utilization; and initiate a sleep operational mode to the M2M device if the assigned communication time has not yet occurred, wherein the resource utilization is based on statistics on network traffic and/or network control signaling, wherein the network communication is intended for the M2M device, wherein the communication time for the M2M device is specifically assigned to correspond to a future time in which the communication scheduling apparatus determines a network capacity is expected to be sufficient to satisfy the network communication request based on the statistics on network traffic and/or network control signaling, and wherein the processor is configured to assign the communication time for the M2M device using a bottom-up approach in which time slots corresponding to lower expected network traffic are assigned prior to time slots corresponding to higher expected network traffic. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 39)
-
-
24. A communication scheduling apparatus comprising:
-
a communications port configured to retrieve a network communication priority and/or parameter; and a processor configured to determine a scheduling priority based on the network communication priority and/or the parameter, pre-emptively assign a communication time, based on the scheduling priority and resource utilization, specifying when network communication will be available for a Machine-to-Machine (M2M) device based on the scheduling priority and network resource utilization; and initiate a sleep operational mode to the M2M device if the assigned communication time has not yet occurred, wherein the network resource utilization is based on statistics on network traffic and network control signaling, wherein receiving a network communication request further comprises receiving the network communication request in the form of a downlink request from an operator or application, the network communication being intended for the M2M device, wherein the assigned communication time corresponds to a future time in which the communication scheduling apparatus determines a network capacity is expected to be sufficient to satisfy the network communication request based on the statistics on network traffic and/or network control signaling, and wherein the processor is configured to pre-emptively assign the communication time for the M2M device using a bottom-up approach in which time slots corresponding to lower expected network traffic are assigned prior to time slots corresponding to higher expected network traffic. - View Dependent Claims (25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 40)
-
Specification