Patent Application
20120178464
The present application relates generally to wireless communications and, more specifically, to a method and apparatus to support efficient and reliable machine to machine communications.
Machine-to-machine (M2M) communication refers to communication involving one or more entities that do not necessarily need human interaction. The M2M communication can include collection of data by M2M devices, transmission of collected and selected data through a communication network (e.g., via a cellular network), assessment of the data received by a network entity such as server in the network, and automation of the flow of data to systems or people who need to know them. M2M communication can also include the system or the network communicating with the M2M devices, to give the devices system updates, instructions, configurations, paging information, etc. Exemplary use cases of M2M communications include metering, road security, cargo tracking, remote sensing and monitoring, and consumer electronic and devices. One example of M2M communication is a smart electrical meter communicating with a server at the electric power utility company. However, the current IEEE 802.16m specification has limited support for M2M communication.
For use in a machine device, a method to support machine-to-machine communications over a network is provided. The method includes acquiring system information from the network. The method also includes determining a ranging channel during a ranging back-off window. The method further includes performing ranging based on the determined ranging channel. The method still further includes communicating over the d network. The ranging channel is determined according to a ranging priority of the machine device.
A machine device configured to support machine-to-machine communications is provided. The machine device includes a processor configured to acquire system information from the network. The processor is also configured to determine a ranging channel during a ranging back-off window. The processor is also configured to perform ranging based on the determined ranging channel. The processor is further configured to communicate over the network. The ranging channel is determined according to a ranging priority of the machine device.
For use in a base station, a method to support machine-to-machine communications is provided. The method includes providing system information from the network to a machine device. The method also includes determining a ranging channel during a ranging back-off window. The method further includes receiving a signal from the machine device on the determined ranging channel. The method still further includes communicating with the machine device over the network. The ranging channel is determined according to a ranging priority of the machine device.
A base station configured to support machine-to-machine communications is provided. The base station includes a processor configured to provide system information from the network to a machine device. The processor is also configured to determine a ranging channel during a ranging back-off window. The processor is further configured to receive a signal from the machine device on the determined ranging channel. The processor is still further configured to communicate with the machine device over the network. The ranging channel is determined according to a ranging priority of the machine device.
Before undertaking the DETAILED DESCRIPTION OF THE INVENTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document: the terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation; the term “or,” is inclusive, meaning and/or; the phrases “associated with” and “associated therewith,” as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, or the like; and the term “controller” means any device, system or part thereof that controls at least one operation, such a device may be implemented in hardware, firmware or software, or some combination of at least two of the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.
For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:
The following document is hereby incorporated into the present disclosure as if fully set forth herein:
In accordance with this disclosure, an apparatus and methods support efficient and reliable machine to machine (M2M) communications is provided. Throughout the disclosure, various terms are used which may be associated with an IEEE 802.16m system. However, the ideas and solutions in this disclosure are not limited to a IEEE 802.16m system. It will be understood that the ideas and solutions disclosed herein may be used in other communication systems and networks, with the various terms identified in various ways according to the associated system or network.
As used herein, deregistration with context retention (DCR) mode is a mode in which an advanced mobile station (AMS) is deregistered from the network while its context is maintained in a network entity until a context retention timer expires.
The context retention timer (CR timer) is a global value defined in the system, such as described in the REF1 document. However, given the possible different requirements of the AMS on the frequency of entering or exiting the DCR mode, it may be beneficial to make the CR timer flexible, according to different deployment scenarios. While the CR timer is valid (i.e., unexpired), the network retains the AMS's information which is used to expedite AMS's network reentry.
An identifier referred to as the context retention identifier (CRID) may be used to uniquely identify the DCR mode AMSs.
As used herein, CR timer may refer to the value of the CR timer, which could be an absolute value in units of seconds, minutes, hours, superframes, and the like. CR timer may also refer to an index associated with a particular CR timer, for those systems with multiple preconfigured timers, where the index indicates a particular entry in a list of CR timer values available for the system. CR timer may also refer to other information associated with the CR timer.
Throughout this disclosure, embodiments are described using M2M communications as exemplary use cases or applications. However, it will be understood that the embodiments in this disclosure may be used in other use cases or applications besides M2M communications.
In one embodiment of the current invention, a machine device acquires system information from a base station, e.g., via a synchronization channel and broadcast channel of the base station. As used herein, a machine device is a device configured for M2M communication. The machine device may be, e.g., a mobile station, a smart utility meter, a home alarm monitor, a personal medical monitor, or any other suitable device.
The machine device establishes synchronization with the base station via the synchronization channel, obtains the cell identifier or the preamble code of the base station, and obtains the downlink and uplink parameters or the system information on the broadcast channel. The machine device then selects a network. That is, the machine device selects which base station to access. After the machine device selects a network, the machine device waits for a ranging opportunity, which is defined as a ranging channel with a given resource allocation (i.e., time and frequency). The resource information associated with the ranging channel (i.e., which time and frequency resource is allocated for the ranging channel) may be derived or obtained by the system information that the machine device obtains from the base station. The derivation may be a mapping function of the system information to the indices of the resource blocks (time and frequency) which define the ranging channel.
The machine device then starts a back-off window, and randomly selects a ranging opportunity which occurs during the back-off window. After the ranging channel is chosen, the machine device randomly selects a ranging code or ranging sequence, and transmits the chosen code or sequence over the chosen ranging channel. If the base station detects the signal on the ranging channel, the base station may continue the network access procedure, such as by sending the machine device an acknowledgement (ACK) that includes the ranging code detected on the ranging channel (the ranging ACK may include an adjustment of the power, timing, etc., of the machine device), or by allocating a resource to the machine device so that the machine device may further send a ranging request message, etc.
The back-off window that the machine device uses can be defined by a back-off window start point and a back-off window end point. Alternatively, the back-off window can be defined by a back-off window start point and a back-off window size. In another alternative, the back-off window can be defined according to an initial back-off window size, a maximum window size, and a rule for changing the window size (e.g., in one rule, upon every collision, the window size is doubled until the maximum window size is reached).
In certain embodiments, machine devices may have different priorities in ranging. For example, some devices that do not communicate with the network frequently may have a lower priority in ranging. An example of such a device is an electric utility meter that typically only reports to the grid once a day or once a month. Such meters may have a lower priority in ranging. In contrast, a standard mobile station (i.e., mobile phone) may have a higher priority in ranging compared with an electric utility meter, due to the mobile station's frequent communication with the network (e.g., dozens of times each day for calls, texts, data service, and the like).
Machine devices such as utility meters often include a backup battery for use during events such as a power outage. A utility meter without little or no buffered battery power may have a higher priority in ranging in some situations, such as at an occurrence of a power outage, and the meter has to report the power outage. A meter with little remaining backup battery life may have a higher priority in ranging, due to a higher urgency in reporting before the battery is depleted. In contrast, a meter with good battery life may have a lower priority in ranging, due to the meter having a lower urgency in reporting.
Support for different priorities in ranging may be achieved using different approaches. The different approaches include use of different sets of the back-off timing, back-off windows (e.g., different start time of the back-off window, different back-off window size, etc.), and so forth; scheduling the devices to wait for a period of time before the devices start the back-off window, where the period of time is of different lengths; and using different starting times for sending a bandwidth request for a resource to carry a ranging request message, etc. These different approaches are discussed in greater detail below.
Throughout this disclosure, a network controlled procedure may be used as an example of how the parameters related to a ranging process such as back-off timing, back-off window start, back-off window size, etc., are determined. In other words, the network may configure these parameters and give the instructions to the machine type devices. However, the disclosure is applicable to other situations, such as where a machine type device determines the ranging related parameters, such as back-off timing, back-off window start, back-off window size, etc. The machine type device can determine the parameters based on its status, e.g., the battery life time, reserved battery level, urgency level, etc. For example, if the battery level of a machine type device is low, the device may use a smaller back-off window size or a longer waiting time to start the back-off window. Conversely, if the batter level is high, the device may use a larger window size or a shorter waiting time to start the back-off window. The disclosure also includes the combination of the methods in the embodiments. For example, both the network and the machine type device can decide together (e.g., by negotiation, handshaking, etc.) on the configuration of the parameters associated with the ranging process.
Throughout this disclosure, a power outage is used as an example situation where many machine devices may communicate with the network at the same time. For example, at the occurrence of a power outage, every utility meter in the geographical area affected by the power outage may attempt at approximately the same time to inform the utility company of the power outage. However, it will be understood that this disclosure is not limited to the case of a power outage. Instead, the embodiments of this disclosure may be applicable for many use cases. Other example situations include recovery from a power outage, many devices moving to a new area (i.e., a mass location update), many devices receiving a group based paging communication, and so forth. To avoid possible congestion on ranging in network entry, the devices can be scheduled to start the ranging process at different times. The communication with the network can be, for example, sending alarms to the network about a failure such as a power outage, sending a report, sending a location update, sending an ACK/NACK, and so forth.
In one example, the scheduling can be achieved by hashing the identifier of the device (i.e., a mobile station identifier (MSID), CRID, etc.) to the different access time offsets to start the ranging. In another example, different machine devices are associated with different initial back-off windows, such that an urgent machine device is associated with a smaller back-off window, while the non-urgent machine device may use a larger back-off window.
The rules for scheduling the devices for network entry timing can be predefined, or the rules can be configured and updated in certain messages. The network can send the rules to the machine device, and the machine device uses the rule to derive or obtain the related timing for network entry. Alternatively, the network may signal the machine device directly with the related timing for network entry. The scheduling rules or approaches can be different in different scenarios. For example, particular scheduling rules may be set up for particular scenarios, such as a power outage, a recovery of a power outage, a reception of a group based paging, etc. The scheduling rules used in particular scenarios are provided to avoid congestion during network entry due to simultaneous attempts by many machine devices for network access.
In order to enable the scheduling rules, the machine device may indicate its device type (e.g., whether or not the device is a machine type device, what kind of reporting periodicity the device employs, what kind of delay requirement the machine uses, etc.) to the network. For example, the machine device may indicate its device type in a capability negotiation procedure. The indication may be in a message such as a basic capability negotiation request message. The network may provide to the machine device one or more scheduling rules associated with network entry (e.g., rules for how to schedule the ranging, how to schedule the bandwidth request, how to set up the timing related to the random back-off or the timing related to the back-off window, the initial size of the back-off window, the maximum size of the back-off window, and the like). The rules may be unicasted, multicasted, or broadcasted to the machine device. For example, the network can unicast the rules for the machine device to follow, after the machine device provides its device type, capability, etc., to the network, e.g., in the capability negotiation response message.
The urgency requirement can be related to the battery reserve level. For example, MTD 1 can be a device which may have a lower battery reserve level, and MTD2 can be a device which may have a higher battery reserve level. In a situation such as the power outage where MTD1 and MTD2 lose the power-line power supply, MTD1 and MTD2 use the reserved battery or backup battery to communicate with the network. MTD1 with a lower battery reserve level may use a smaller back-off window size or shorter waiting time to start the back-off window. Conversely, MTD2 with a higher battery reserve level may use a larger back-off window size or longer waiting time to start the back-off window, as long as the remaining battery power is enough for the devices to have a communication with the network.
In another embodiment, MTD1 and MTD2 choose the back-off window size or the waiting time to start the back-off window to be as long as possible, within the constraint that the device would have enough remaining battery power to have the communication with the network. The machine type device can make such a decision on the parameters of the back-off window size, or the start time of the back-off window, based on its battery reserve, etc. The MTD can also have a rule pre-determined and programmed by the network, where the rule can be stored in the MTD, and the MTD can determine the parameters based on the rule. The rule can be, for example, related to the reserved battery level. In another embodiment, the network can communicate the configured parameters to the MTD, e.g., by sending messages. It will be understood that these embodiments are not limited to MTDs; these embodiments also can be applicable to mobile devices in general.
In certain embodiments, the machine device may indicate its type to the network. The type may be indicated, e.g., in a capability negotiation request message. In one embodiment, a “device type indication” field in the capability negotiation request message is used to indicate the type of the device. For example, the following values may be assigned to the “device type indication” field:
‘0000’: non-machine-type device (e.g., a mobile phone)
‘0001’: machine type device, type 1, with delay requirement less than T1
‘0010’: machine type device, type 2, with delay requirement less than T2
Other values: reserved.
After receiving or determining the machine device type, the base station or the network may indicate a rule associated with the scheduling for the timing of the network entry. The rule may be indicated, e.g., in a capability negotiation response message. In one embodiment, a “network entry scheduling rule indication” field in the capability negotiation response message is used to indicate the back-off window length. For example, the following values may be assigned to the “network entry scheduling rule indication” field:
‘0000’: initial back-off window length L0
‘0001’: initial back-off window length L1
‘0010’: initial back-off window length L2
Other values: reserved.
In one embodiment, the base station indicates the scheduling rule as follows. If the received machine device type indication is ‘0000’, then the base station indicates ‘0000’ as the scheduling rule. If the received machine device type indication is ‘0001’, then the base station indicates ‘0001’ as the scheduling rule. If the received machine device type indication is ‘0010’, then the base station indicates ‘0010’ as the scheduling rule. Other device type values may map to other scheduling rule values in a similar way.
In some embodiments, the scheduling can be associated with a maximum back-off window length. Different devices may have a different maximum back-off window length. For example, a device with a stringent requirement on delay may be assigned a smaller maximum back-off window length, while a device with a looser requirement on delay may be assigned a larger maximum back-off window length.
The machine device remembers the rule assigned to the device after the rule is received. The machine device then applies the rule every time the machine device performs network entry. Such rules may be pre-provisioned as well. When the rule is pre-provisioned, the machine device can use the assigned timing for network entry, even without a capability negotiation procedure.
A pre-provisioned rule is a mapping or a function that both the base station (or network) and the machine device know ahead of time, e.g., the rule is pre-defined. For example, in one embodiment, the mapping function is
IWL=DT
where IWL is the index of initial back-off window lengths, and DT is the index of the device type indications.
In certain embodiments, the machine device may indicate its type to the network. For example, the machine device may indicate its type to the network in a “device type indication” field in a capability negotiation request message, such as described above in the example in
After receiving or determining the machine device type, the BS or the network may indicate a rule associated with the scheduling for the timing of the network entry. The rule may be indicated, e.g., in a capability negation response message. In one embodiment, a “network entry scheduling rule indication” field is used to indicate the waiting time before the back-off window starts. For example, the following values may be assigned to the “network entry scheduling rule indication” field:
‘0000’: Waiting time 0
‘0001’: Waiting time WT1
‘0010’: Waiting time WT2
Other values: reserved.
In one embodiment, the base station indicates the scheduling rule as follows. If the received machine device type indication is ‘0000’, then the base station indicates ‘0000’ as the scheduling rule. If the received machine device type indication is ‘0001’, then the base station indicates ‘0001’ as the scheduling rule. If the received machine device type indication is ‘0010’, then the base station indicates ‘0010’ as the scheduling rule. Other device type values may map to other scheduling rule values in a similar way.
In another embodiment of this disclosure, if many machine devices (e.g., utility meters) may communicate with the network at the same time (due to reasons such as a power outage, recovery of a power outage, receiving a group based paging, and so forth), to avoid possible congestion on ranging in network entry, the machine devices may be scheduled to start the ranging process at different times.
For example, in a geographic area, a power outage (blackout) may occur, and all the meters in the affected attempt to report the outage to the network right after the outage. Likewise, when the power is restored, all the meters attempt to get back to the network. In these situations, the network may be congested by a large number of devices trying to communicate with the network at the same time. In this embodiment, the power outage is used as one example of the reasons that the devices may attempt network entry at the same time.
Upon an occurrence of an event that may cause many devices to attempt network entry at the same time (e.g., power outage, recovery of power outage, etc.), when such an event is detected, the device can apply one or more rules to try to avoid congestion. The rules may include using a different timing on the back-off window, a different size of the back-off window, a different waiting time to start the process of ranging, and the like.
Similar to the previous embodiments, the base station, system, or network may maintain and manage the scheduling rules and configurations, device type indications, scheduling rule indications, delivery methods of such indications, delivery methods of scheduling rules, and so forth. The rules and associated information may be communicated from the network to the associated machine devices. In embodiments where the waiting time is long such that the scheduling information may be changed, then the machine devices may obtain updated scheduling information, e.g., via periodically monitoring the broadcast channel, monitoring the change count of the broadcast channel, monitoring the preamble or sync channel, and so forth.
The base station or the network may indicate a rule associated with the scheduling for the timing of the network entry. The rule may be indicated, e.g., in a message such as a capability negotiation response message. In one embodiment, a “network entry scheduling rule indication for reasons such as power outage” field in the capability negotiation response message is used to indicate the scheduling. The field may have the following values:
‘0000’: Waiting time to start back-off window: 0
‘0001’: Waiting time to start back-off window: WT1
‘0010’: Waiting time to start back-off window: WT2
‘0011’: Waiting time to start back-off window: Infinity (i.e., no need to report power outage)
Other values: reserved.
In another embodiment of this disclosure, the base station or network may indicate a rule associated with the scheduling for the timing of the network entry. The rule may be indicated, e.g., in a message such as a capability negotiation response message. In one embodiment, a “network entry scheduling rule indication for reasons such as power outage” field in the capability negotiation response message is used to indicate the waiting time. For example, the following values may be assigned to the “network entry scheduling rule indication, for reasons such as power outage” field:
‘0000’: Waiting time to start network entry procedure: 0
‘0001’: Waiting time to start network entry procedure: WT1
‘0010’: Waiting time to start network entry procedure: WT2
‘0011’: Waiting time to start network entry procedure: Infinity (i.e., no need to report power outage)
Other values: reserved.
In another embodiment of the current invention, different rules of scheduling may be applied according to the different events that trigger network entry of many devices at the same time. The indication of the scheduling rules due to different events, scenarios, and use cases (e.g., different causes, different device capability, different service requirements, etc.) can be combined, jointly coded, and so forth.
For example, the base station or the network may indicate a rule associated with the scheduling for the timing of the network entry. The rule may be indicated, e.g., in a message such as a capability negotiation response message or another downlink message. In one embodiment, a “network entry scheduling rule indication for reasons such as power outage” field in the downlink message is used to indicate the scheduling rule. For example, the following values may be assigned to the “network entry scheduling rule indication for reasons such as power outage” field:
‘0000’: Waiting time to start back-off window: 0
‘0001’: Waiting time to start back-off window: WT1
‘0010’: Waiting time to start back-off window: WT2
‘0011’: Waiting time to start back-off window: Infinity (i.e., no need to report power outage), for reasons such as power outage
‘0100’: Waiting time to start network entry procedure: 0
‘0101’: Waiting time to start network entry procedure: WT1
‘0110’: Waiting time to start network entry procedure: WT2
Other values: reserved.
The downlink message may also include a “network entry scheduling rule indication for reasons such as power outage recovery” field with the following possible values:
‘0000’: Waiting time to start back-off window: 0
‘0001’: Waiting time to start back-off window: WT1
‘0010’: Waiting time to start back-off window: WT2
Other values: reserved.
The downlink message may also include a “network entry scheduling rule indication for reasons such as receiving a group based paging” field with the following possible values:
‘0000’: Waiting time to start back-off window: 0, response needed
‘0001’: Waiting time to start back-off window: WT1, response needed
‘0010’: Waiting time to start back-off window: WT2, response needed
‘0011’: Waiting time to start back-off window: Infinity, response NOT needed after receiving group based paging
Other values: reserved.
Similar indications (i.e., additional fields in the downlink message) may be implemented for “waiting time to start the procedure of network entry”. These indications can be combined or jointly coded with the other indications. In certain embodiments, the indications are predefined, pre-provisioned, or signaled from the network to the machine device.
In accordance with another embodiment of this disclosure, in the event of a power outage, the base station or the network may select some of the machine devices to report the power outage, and select some of the devices not to report the power outage. The base station or network may make the selection based on the battery capability of the devices.
The machine device may indicate its type to the network, e.g., in a message such as capability negotiation request message. In one embodiment, the machine device may indicate its type in a “device type indication” field in the capability negotiation request message. For example, the following values may be assigned to the “device type indication” field:
‘0000’: non-machine-type device
‘0001’: machine type device
Other values: reserved.
The machine device may also indicate its battery configuration in a “device battery indication” field in the capability negotiation request message. The “device battery indication” field may have the following values:
‘0000’: no backup battery, no battery buffer
‘0001’: no backup battery, with battery buffer
‘0010’: backup battery present
Other values: reserved.
Depending on the device type and battery indication from the machine device, the network assigns a network entry schedule to the machine device. For example, the network may assign an immediate network entry without any waiting time (e.g., a code ‘0000’ for a power outage case) if the battery indication indicates the machine device does not have a backup battery but has some battery buffer, if the device is indicated to report a power outage. The network may determine not to request those devices that do not have a backup battery to report a power outage, if there are other devices with backup battery available.
In accordance with another embodiment of this disclosure, in the event of a power outage, the base station or the network may select some of the machine devices to report the power outage, and select some of the devices not to report the power outage. In this embodiment, the base station or network may make the selection based on the location information of the devices.
For example, if the machine devices (e.g., utility meters) are not moving and have a fixed location, the base station or network may sample the geographical area using a small number of utility meters that would report when a power outage occurs. In such an embodiment, a power outage does not trigger a surge in network access because only a few meters would report the outage. The meters selected for the sampling may indicate if a neighborhood, a street, or an entire city has lost power. Location information is useful in determining if there is sufficient geographical coverage of the selected devices so that any outage can be immediately identified. The negotiations between the base station or network and the device indicate whether or not the device is to report an outage.
In addition to location information, there are other metrics that the base station can use to determine if the device should report outage. These other metrics include (but are not limited to) device geometry (link status), device capability (supplemental battery availability), and priority of the device in the network.
In certain embodiments of this disclosure, some system information, such as MSID, CRID, group ID, etc, can be mapped or hashed (via a mapping function) to the parameters or configuration of the scheduling rules. Here, the scheduling parameters may include the waiting time configuration indices, the initial back-off window size configuration indices, configuration parameters associated with whether meters report an outage (e.g., setting the waiting time as a very large number or infinity), and the like. The mapping may be predefined and stored by the machine device and the network, or the network may send the mapping to the machine device in one or more downlink messages. In one example, the mapping function is:
WT—i=mod(MSID—i,N)
where WT_i is the waiting time of the i-th device, MSID_i is the MSID of the i-th device, and N is a parameter (e.g., N can be the number of configurations of the waiting time).
In another example, the mapping function is:
WT—i=mod(CRID—i,N)
where WT_i is the waiting time of the i-th device, CRID_i is the CRID of the i-th device, and N is a parameter (e.g., N can be the number of configurations of the waiting time).
In certain embodiments, the mapping function can be used by all of the devices that perform network entry, particularly in situations where the network entry of many devices may happen at approximately the same time. The devices may have the same or similar level of capability, such as the same level of delay/latency requirement, etc. The devices may use the above approaches (e.g., negotiation with the network regarding the assignment of the scheduling rule, based on the device capability), then use a mapping function to provide further staggering or offsetting in the scheduling rule within the devices having the same level of device capability.
In certain embodiments, if a power outage occurs and then the power is restored before a machine device achieves access to report the power outage, then the device may follow a procedure for a power outage recovery.
In an example, a device (e.g., mobile station 1) attempts to access the network early, due to one or more reasons such as the device does not have a backup battery or has a very poor battery. Thus, mobile station 1 may have a more urgent need to report than other devices. The system may require device to obey the rules, and set up the configuration during capability negotiation. For example, a device indicates its capability (e.g., indication of a machine type device access level) using the following values:
0000: regular MS
0001: MTD (machine type device) with battery backup
0010: MTD without a battery backup
0011: MTD with low urgency level
0100: MTD with medium urgency level
0101: MTD with high urgency level.
The set up can be according to the following reason bits:
00: power outage. The ranging starts the back-off window after waiting WT0 time.
00: power outage. MS with MTD access level 0001 starts the back-off window after waiting WT0 time.
01: power outage recovery. MS with MTD access level 0101 starts the back-off window after waiting WT0 time.
Accordingly, the device starts to acquire system information after waiting the designated time after the power outage.
In certain embodiments, some ranging channels may be reserved for the purpose of supporting the ranging in certain situations, such as a power outage. As another example, mobile phones may use one set of ranging channels, while machine type devices (MTD) use a different set of ranging channels. The ranging channels can be of different periodicity/timing for different usage. That is, the periodicity/timing of a ranging channel for a mobile phone may be different from a periodicity/timing of a ranging channel for a MTD. Similarly the ranging code may be partitioned and each set may be allocated according to different usage.
In certain embodiments, paging messages may include paging for a group of machine devices. A paging message may carry some information such as system update information to a group of machine devices, and the message may indicate whether response such as ACK/NACK is needed. After receiving paging information if an ACK/NACK is needed, then the offset for starting the back-off window can apply.
In certain embodiments, machine devices can use different timings for sending a bandwidth request for the resource to send uplink information to the base station, such as a ranging request message, etc. For the bandwidth request, the machine device may also have the random back-off approach if it collides with other machine device's bandwidth request. The principles described in above embodiments can be applied to the timing of the sending bandwidth request, such as offsetting the starting time of a back-off window based on different requirements of the delay or latency, offsetting the start time of sending the bandwidth request, etc.
In certain embodiments, for devices that are in a DCR mode, the uplink message (a utility meter's report) may be included in another message, such as a ranging request message. The network may send downlink messages in the ranging response message.
A machine device in a DCR mode can send a message (e.g., a short message (SMS)) by sending another message (e.g., a ranging request message) with a ranging purpose indication having a predefined value (a specific value assigned to such purpose) in combination with a CRID before the device's context retention timer expires. When the base station receives the message with SMS, the base station sends a response message, such as a ranging response message, as a confirmation of the SMS.
The indication of the SMS in DCR mode may use the same ranging purpose indication for CR timer extension (i.e., the ranging purpose indication value assigned for CR timer extension) combined with a further indication for SMS within the ranging purpose.
For example, in the language of IEEE 802.16, an AMS in DCR mode can send an SMS by sending an AAI-RNG-REQ message with a ranging purpose indication having a value ‘0b1110’ in combination with a CRID before the AMS's context retention timer expires. When the base station receives the AAI-RNG-REQ message with SMS, the base station sends an AAI-RNG-RSP message as a confirmation of the SMS.
When an AAI-RNG-RSP message includes a downlink (DL) SMS, an AAI-MSG-ACK message is sent as a confirmation of the DL SMS. The base station grants a CDMA Allocation A-MAP IE for the AAI-MSG-ACK in unsolicited manner by an ACK timer, where MCRC is masked with the same RA-ID as in CDMA Allocation A-MAP IE for the AAI-RNG-REQ message. When the AMS receives the AAI-RNG-RSP with the DL SMS, the AMS starts the ACK timer and waits the CDMA Allocation A-MAP IE to send the AAI-MSG-ACK message.
The indication of the SMS in DCR mode may use the same indication for CR timer extension, i.e., the ranging purpose indication value ‘0b0100’, combined with a further indication for SMS. The response AAI-RNG-RSP would be changed accordingly.
All the embodiments described in this disclosure can be used in other scenarios. For example, the method of offsetting devices to wait for different periods of time may be applied after an initial attempt of regular ranging (no additional waiting time). Then, if a collision occurs, the proposed approaches described in this disclosure may be used.
Those skilled in the art will recognize that the full construction and operation of a machine device configured for M2M communication is not described herein or depicted in the drawings. Instead, for simplicity and clarity, only so much of the construction and operation of a machine device as is unique to the present invention or necessary for an understanding of the present invention is depicted and described. It will be understood that the functions of the machine device described herein may be executed by one or more processors, controllers, memories, interfaces, and circuitries contained in, on, or associated with the machine device.
Although the present disclosure has been described with an exemplary embodiment, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.
The present application is related to U.S. Provisional Patent Application No. 61/430,915, filed Jan. 7, 2011, entitled “METHODS AND APPARATUS TO SUPPORT EFFICIENT AND RELIABLE MACHINE TO MACHINE COMMUNICATIONS”. Provisional Patent Application No. 61/430,915 is assigned to the assignee of the present application and is hereby incorporated by reference into the present application as if fully set forth herein. The present application hereby claims priority under 35 U.S.C. §119(e) to U.S. Provisional Patent Application No. 61/430,915.
| Number | Date | Country | |
|---|---|---|---|
| 61430915 | Jan 2011 | US |
