Communications are coordinated between different respective wireless communication device groups in a multiple delivery traffic indication map (dtim) per device signaling scheme. Different respective wireless communication devices (e.g., wireless stations (STAs)) may communicate with a manager/coordinator wireless communication device (e.g., access point (AP)) at different times and for different reasons. The manager/coordinator wireless communication device generates and transmits beacons to the wireless communication devices specifying times during which communications may be supported with the manager/coordinator wireless communication device. A restricted access window (raw) information element (IE) within a beacon includes at least one restricted access window (raw) to specify a wireless communication device authorized to communicate with the manager/coordinator wireless communication device. Different wireless communication device groups may communicate with the manager/coordinator wireless communication device at different periodicities, and any one wireless communication device may be included in more than one wireless communication device group.
|
14. A method for execution by a communication device, the method comprising:
generating a plurality of beacons having a plurality of restricted access window (raw) information elements (IEs) that specify a plurality of raws for a plurality of wireless communication device groups to communicate with the wireless communication device; and
operating a communication interface for:
transmitting the plurality of beacons to a plurality of wireless communication devices; and
supporting first communications with a first wireless communication device group during first raws having a first delivery traffic indication message (dtim) periodicity; and
supporting second communications with a second wireless communication device group during second raws having a second dtim periodicity.
9. A wireless communication device comprising:
a communication interface; and
a processor, at least one of the processor or the communication interface configured to:
generate a plurality of beacons having a plurality of restricted access window (raw) information elements (IEs) that specify a plurality of raws for a plurality of smart meter station (smsta) groups to communicate with the wireless communication device;
transmit the plurality of beacons to a plurality of smstas;
support first communications with a first smsta group during first raws having a first delivery traffic indication message (dtim) periodicity; and
support second communications with a second smsta group during second raws having a second dtim periodicity that is an integer multiple of the first dtim periodicity.
1. A wireless communication device comprising:
a communication interface; and
a processor, at least one of the processor or the communication interface configured to:
generate a plurality of beacons having a plurality of restricted access window (raw) information elements (IEs) that specify a plurality of raws for a plurality of wireless communication device groups to communicate with the wireless communication device;
transmit the plurality of beacons to a plurality of wireless communication devices;
support first communications with a first wireless communication device group during first raws having a first delivery traffic indication message (dtim) periodicity; and
support second communications with a second wireless communication device group during second raws having a second dtim periodicity.
2. The wireless communication device of
3. The wireless communication device of
a first beacon includes a first raw IE that specifies a first raw for the first wireless communication device group; and
a second beacon includes a second raw IE that specifies a second raw for the second wireless communication device group.
4. The wireless communication device of
a first beacon includes a first raw IE that specifies a first raw for the first wireless communication device group; and
a second beacon includes a second raw IE that specifies a second raw for the second wireless communication device group and a third raw for a third or the first wireless communication device group.
5. The wireless communication device of
6. The wireless communication device of
the first dtim periodicity is a base dtim periodicity;
the second dtim periodicity is a first integer multiple of the base dtim periodicity; and
the third dtim periodicity is a second integer multiple of the base dtim periodicity.
7. The wireless communication device of
8. The wireless communication device of
an access point (AP), wherein the plurality of wireless communication devices including at least one of a wireless station (STA) or a smart meter station (smsta).
10. The wireless communication device of
11. The wireless communication device of
a first beacon includes a first raw IE that specifies a first raw for the first smsta group; and
a second beacon includes a second raw IE that specifies a second raw for the second smsta group and a third raw for a third or the first smsta group.
12. The wireless communication device of
the first dtim periodicity is a base dtim periodicity;
the second dtim periodicity is a first integer multiple of the base dtim periodicity; and
the third dtim periodicity is a second integer multiple of the base dtim periodicity.
13. The wireless communication device of
15. The method of
operating the communication interface for supporting the first communications and the second communications during the first raws and the second raws, respectively, with at least one common wireless communication device included in both the first wireless communication device group and the second wireless communication device group.
16. The method of
a first beacon includes a first raw IE that specifies a first raw for the first wireless communication device group; and
a second beacon includes a second raw IE that specifies a second raw for the second wireless communication device group and a third raw for a third or the first wireless communication device group.
17. The method of
18. The method of
operating a communication interface for supporting third communications with a third wireless communication device group during third raws having a third dtim periodicity, wherein:
the first dtim periodicity is a base dtim periodicity;
the second dtim periodicity is a first integer multiple of the base dtim periodicity; and
the third dtim periodicity is a second integer multiple of the base dtim periodicity.
19. The method of
20. The method of
|
The present U.S. Utility Patent Application claims priority pursuant to 35 U.S.C. §119(e) to the following U.S. Provisional Patent Applications which are hereby incorporated herein by reference in their entirety and made part of the present U.S. Utility Patent Application for all purposes:
1. U.S. Provisional Patent Application Ser. No. 61/660,789, entitled “Multiple delivery traffic indication map (DTIM) per device within single user, multiple user, multiple access, and/or MIMO wireless communications,” filed Jun. 17, 2012, pending.
2. U.S. Provisional Patent Application Ser. No. 61/826,744, entitled “Multiple delivery traffic indication map (DTIM) per device within single user, multiple user, multiple access, and/or MIMO wireless communications,” filed May 23, 2013, pending.
1. Technical Field
The present disclosure relates generally to communication systems; and, more particularly, to signaling within single user, multiple user, multiple access, and/or MIMO wireless communications.
2. Description of Related Art
Communication systems support wireless and wire lined communications between wireless and/or wire lined communication devices. The systems can range from national and/or international cellular telephone systems, to the Internet, to point-to-point in-home wireless networks and can operate in accordance with one or more communication standards. For example, wireless communication systems may operate in accordance with one or more standards including, but not limited to, IEEE 802.11x (where x may be various extensions such as a, b, n, g, etc.), Bluetooth, advanced mobile phone services (AMPS), digital AMPS, global system for mobile communications (GSM), etc., and/or variations thereof.
In some instances, wireless communication is made between a transmitter (TX) and receiver (RX) using single-input-single-output (SISO) communication. Another type of wireless communication is single-input-multiple-output (SIMO) in which a single TX processes data into RF signals that are transmitted to a RX that includes two or more antennae and two or more RX paths.
Yet an alternative type of wireless communication is multiple-input-single-output (MISO) in which a TX includes two or more transmission paths that each respectively converts a corresponding portion of baseband signals into RF signals, which are transmitted via corresponding antennae to a RX. Another type of wireless communication is multiple-input-multiple-output (MIMO) in which a TX and RX each respectively includes multiple paths such that a TX parallel processes data using a spatial and time encoding function to produce two or more streams of data and a RX receives the multiple RF signals via multiple RX paths that recapture the streams of data utilizing a spatial and time decoding function.
A manager or coordinator wireless communication device (such as an access point (AP)) may support communications with different respective wireless communication devices (e.g., wireless stations (STAs)) at different respective times. Also, a manager or coordinator wireless communication device may support communications with any one wireless communication device for very different reasons at different times. Ineffective coordination of such communications within a wireless communication system reduces the overall system's throughput and performance. Also, an individual wireless communication device's performance also suffers with inefficient and poorly coordinated use of the communication medium (e.g., air in a wireless context).
The base stations (BSs) or access points (APs) 112-116 are operably coupled to the network hardware 134 via local area network connections 136, 138, and 140. The network hardware 134, which may be a router, switch, bridge, modem, system controller, etc., provides a wide area network connection 142 for the communication system 100. Each of the base stations or access points 112-116 has an associated antenna or antenna array to communicate with the wireless communication devices in its area. Typically, the wireless communication devices register with a particular base station or access point 112-116 to receive services from the communication system 100. For direct connections (i.e., point-to-point communications), wireless communication devices communicate directly via an allocated channel.
Within such a wireless communication system 100, a manager or coordinator wireless communication device may support different communications with other wireless communication devices. The manager or coordinator wireless communication device can support different devices at different times as well as communicate with any one or more devices for different purposes at different times. Generally, such communications between wireless communication devices may be referred to as streams or flows.
Multiple respective streams or data flows are supported between a manager or coordinator wireless communication device and various other wireless communication devices (e.g., wireless stations (STAs), smart meter stations (SMSTAs), etc.) within a given wireless communication network (e.g., a basic services set (BSS), etc.). In addition, a singular other wireless communication device can support communications using more than one respective stream or data flow (e.g., different flows for different purposes). Streams or data flows correspond to upstream and/or downstream communications made at appropriate times and/or in response to or based on various considerations, events, and/or conditions.
For example, a given SMSTA may operate by waking up periodically (e.g., every N seconds) to receive a given downlink stream from the manager or coordinator wireless communication device. Alternatively, a given SMSTA may operate by waking up every N1 seconds to receive a first downlink stream, every N2 seconds to receive a second downlink stream, etc. Different streams can be supported between wireless communication devices for different reasons (e.g., metering/sensing uplink data transfers, downlink metering/sensing instructions, management frame exchanges, etc.).
In another example, a given SMSTA may operate by waking up every N1 seconds to receive a first downlink stream, every N2 seconds to receive a second downlink stream, and every N3 seconds to transmit an uplink stream (e.g., to an access point (AP)), etc. Again, any one wireless communication device may support communications with a manager or coordinator wireless communication device via different streams (e.g., using and supporting different functionalities associated with different streams).
Differentiation and coordination of such communications between the manager or coordinator wireless communication device and the various wireless communication devices ensures effective use of the communication medium (e.g., one or more communication channels of a frequency spectrum that is conveyed via air) as well as ensures effective operation of the respective wireless communication devices. Some SMSTAs are energy constrained (e.g., battery powered) and proper scheduling to enter into and exit from sleep or reduced power state can extend a device's operational cycle.
Considering an example with respect to the diagram, BS or AP 116 includes per group DTIM functionality to support communications with different respective devices 126, 128, 130, and 132 at different times and for different reasons. Communications with any one of these devices may be supported using different streams or data flows. The BS or AP 116 generates and transmits beacons to the devices 126, 128, 130, and 132. These beacons include restricted access window (RAW) information elements (IEs) that specify a number of RAWs during which the devices 126, 128, 130, and 132 communicate with a BS or AP 116. Different delivery traffic indication message (DTIM) parameters may be provided for each respective RAW. For example, a beacon may include an information element that is a RAW IE. Such a RAW IE specifies one or more RAWs during which different respective groups of the devices 126, 128, 130, and 132 communicate with the BS or AP 116.
The BS or AP 116 communicates with one or more of the devices 126, 128, 130, and 132 (e.g., a first group of devices) during the respective RAWs that occur within the beacons at a first DTIM periodicity, and with one or more of the devices 126, 128, 130, and 132 (e.g., a second group of devices) during the respective RAWs that occur within the beacons at a second DTIM periodicity. Considering an example, the BS or AP 116 communicates with the first group of devices during RAWs indicated in every Nth beacon (e.g., where N is an integer), and the BS or AP 116 communicates with the second group of devices during RAWs indicated in every Mth beacon (e.g., where M is an integer). Generally, the BS or AP 116 communicates with different respective groups of devices (uplink and/or downlink) in the various RAWs. A wireless communication device group may include as few as one device, and a device may be in more than one wireless communication device group. Also, there may be instances in which a given RAW may be repeated within a beacon interval, such as when a given wireless communication device group may need more than one RAW within a single DTIM period. The different respective DTIM periodicities may be integer multiples of one of the DTIM periods or a base DTIM period.
As the BS or AP 116 transmits beacons to the devices 126, 128, 130, and 132, communications between the BS or AP 116 and different respective groups of those devices 126, 128, 130, and 132 are supported during those RAWs specified within the RAW IEs of the beacons. This allows for coordination of uplink and/or downlink communication between the BS or AP 116 and the devices 126, 128, 130, and 132, as well as an effective usage of the communication medium.
The interfaces 254 and 262 (e.g., buses, connectors, IC traces, IC pins, etc.) allow for data to be communicated between the computing core 225 and the radio 260. For data from the radio 260 to the computing core 225 (e.g., inbound data), the interface 254 provides the data to the processing module 250 for further processing and/or routing to the output interface 256. The output interface 256 provides connectivity to one or more output display devices such as a display, monitor, speakers, etc. such that the received data may be displayed. The interface 254 also provides data from the processing module 250 to the radio 260. The processing module 250 may receive the outbound data from one or more input devices such as a keyboard, keypad, microphone, etc. via the input interface 258 or generate the data itself.
The baseband processing module 264 of the radio, in combination with operational instructions stored in memory 266, execute digital receiver functions and digital transmitter functions, respectively. The digital receiver functions include, but are not limited to, digital intermediate frequency to baseband conversion, demodulation, constellation demapping, decoding, de-interleaving, fast Fourier transform, cyclic prefix removal, space and time decoding, and/or descrambling. The digital transmitter functions, as will be described in greater detail with reference to later Figures, include, but are not limited to, scrambling, encoding, interleaving, constellation mapping, modulation, inverse fast Fourier transform, cyclic prefix addition, space and time encoding, and/or digital baseband to IF conversion.
In an example of operation, the radio 260 receives outbound data 288 from the computing core and, based on a mode selection signal 202, produces one or more outbound symbol streams 290. For example, the mode selection signal 202 may indicate a frequency band of 2.4 GHz or 5 GHz, a channel bandwidth of 20 or 22 MHz (e.g., channels of 20 or 22 MHz width) and a maximum bit rate of 54 megabits-per-second. In other embodiments, the channel bandwidth may extend up to 1.28 GHz or wider with supported maximum bit rates extending to 1 gigabit-per-second or greater. In this general category, the mode selection signal will further indicate a particular rate ranging from 1 megabit-per-second to 54 megabits-per-second. In addition, the mode selection signal will indicate a particular type of modulation, which includes, but is not limited to, Barker Code Modulation, BPSK, QPSK, CCK, 16 QAM and/or 64 QAM. Also, in such mode selection tables, a code rate is supplied as well as number of coded bits per subcarrier (NBPSC), coded bits per OFDM symbol (NCBPS), data bits per OFDM symbol (NDBPS). The mode selection signal may also indicate a particular channelization for the corresponding mode, which for the information in one of the mode selection tables with reference to another of the mode selection tables. Other types of channels, having different bandwidths, may be employed in other embodiments.
The baseband processing module 264, based on the mode selection signal 202 produces the one or more outbound symbol streams 290 from the output data 288. For example, if the mode selection signal 202 indicates that a single transmit antenna is being utilized for the particular mode that has been selected, the baseband processing module 264 will produce a single outbound symbol stream 290. Alternatively, if the mode selection signal indicates 2, 3 or 4 antennae, the baseband processing module 264 will produce 2, 3 or 4 outbound symbol streams 290 corresponding to the number of antennae from the output data 288.
Depending on the number of outbound streams 290 produced by the baseband module 264, a corresponding number of the RF transmitters 268-272 will be enabled to convert the outbound symbol streams 290 into outbound RF signals 292. The transmit/receive module 274 receives the outbound RF signals 292 and provides each outbound RF signal to a corresponding antenna 282-286.
When the radio 260 is in the receive mode, the transmit/receive module 274 receives one or more inbound RF signals via the antennae 282-286. The T/R module 274 provides the inbound RF signals 294 to one or more RF receivers 276-280. The RF receiver 276-280 converts the inbound RF signals 294 into a corresponding number of inbound symbol streams 296. The number of inbound symbol streams 296 will correspond to the particular mode in which the data was received. The baseband processing module 264 receives the inbound symbol streams 296 and converts them into inbound data 298, which is provided to the computing core 225.
In an embodiment, the radio 260 includes a transmitter and a receiver. The transmitter may include a MAC module, a PLCP module, and a PMD module. The Medium Access Control (MAC) module, which may be implemented with the baseband processing module 264, is operably coupled to convert a MAC Service Data Unit (MSDU) into a MAC Protocol Data Unit (MPDU) in accordance with a WLAN protocol. The Physical Layer Convergence Procedure (PLCP) Module, which may be implemented in the baseband processing module 264, is operably coupled to convert the MPDU into a PLCP Protocol Data Unit (PPDU) in accordance with the WLAN protocol. The Physical Medium Dependent (PMD) module is operably coupled to convert the PPDU into radio frequency (RF) signals in accordance with one of the operating modes of the WLAN protocol, wherein the operating modes includes multiple input and multiple output combinations.
An embodiment of the Physical Medium Dependent (PMD) module includes an error protection module, a demultiplexing module, and direction conversion modules. The error protection module, which may be implemented in the processing module 264, is operably coupled to restructure a PPDU (PLCP (Physical Layer Convergence Procedure) Protocol Data Unit) to reduce transmission errors producing error protected data. The demultiplexing module is operably coupled to divide the error protected data into error protected data streams. The direct conversion modules are operably coupled to convert the error protected data streams into radio frequency (RF) signals.
The wireless communication device of
For example, a wireless communication device may be implemented as a smart meter station (SMSTA). A SMSTA has communication functionality similar to a wireless station (STA) and is also operative to perform communication of monitoring and/or sensing related information. In certain applications, such devices may operate only very rarely. For example, when compared to the periods of time in which such a device is in power savings mode (e.g., a sleep mode, a reduced functionality operational mode, a lowered power operational mode, etc.), the operational periods of time may be miniscule in comparison (e.g., only a few percentage of the periods of time in which the device is in such a power savings mode).
An SMSTA may awaken from such a power savings mode only to perform certain operations. For example, such a device may awaken from such a power savings mode to perform sensing and/or measurement of one or more parameters, conditions, constraints, etc. During such an operational period (e.g., in which the device is not in a power savings mode), the device may also perform transmission of such information to another wireless communication device (e.g., an access point (AP), another SMSTA, a wireless station (STA), or such an SMSTA or STA operating as an AP, etc.).
In addition and/or in the alternative, a device may enter into an operational mode for performing sensing and/or monitoring at a frequency that is different than (e.g., greater than) the frequency at which the device enters into an operational mode for performing transmissions. For example, such a device may awaken a certain number of times to make successive respective sensing and/or monitoring operations, and such data acquired during those operations may be stored (e.g., in a memory storage component within the device). Then, during a subsequent operational mode dedicated for transmission of the data, multiple data portions corresponding to multiple respective sensing and/or monitoring operations may be transmitted during that operational mode dedicated for transmission of the data.
In this diagram, multiple respective wireless communication devices are implemented to forward information related to monitoring and/or sensing to one particular wireless communication device that may be operating as a manager, coordinator, etc. such as may be implemented by an access point (AP) or a wireless station (STA) operating as an AP. Generally speaking, such wireless communication devices may be implemented to perform any of a number of data forwarding, monitoring and/or sensing operations. For example, in the context of a building or structure, there may be a number of services that are provided to that building or structure, including natural gas service, electrical service, television service, Internet service, etc. Alternatively, different respective monitors and/or sensors may be implemented throughout the environment to perform monitoring and/or sensing related to parameters not specifically related to services. As some examples, motion detection, door ajar detection, temperature measurement (and/or other atmospheric and/or environmental measurements), etc. may be performed by different respective monitors and/or sensors implemented in various locations and for various purposes.
Different respective monitors and/or sensors may be implemented to provide information related to such monitoring and/or sensing functions wirelessly to the manager/coordinator wireless communication device. Such information may be provided continuously, sporadically, intermittently, etc. as may be desired in certain applications.
In addition, communications between a manager/coordinator wireless communication device of the different respective monitors and/or sensors may be cooperative in accordance with such bidirectional communications, in that, the manager/coordinator wireless communication device may direct the respective monitors and/or sensors to perform certain related functions at subsequent times.
Different monitoring/sensing operations may need to be performed at different respective times. For example, gas line metering or sensing may be performed relatively less frequently than electric service metering or sensing. Also, security based sensing, such as detection of a door or window being ajar, may be critical in nature and preferably be performed almost continuously. A variety of different communications are provided to the manager/coordinator wireless communication device from different sensing devices (e.g., SMSTAs) that perform different operations and functions. In this diagram, a manager/coordinator wireless communication device generates beacons that include RAW IEs and transmits them to other wireless communication devices (e.g., SMSTAs) in the system.
The manager/coordinator wireless communication device supports subsequent communications with the other wireless communication devices (e.g., SMSTAs) on a per group basis. A given group may include as few as one wireless communication device (e.g., one SMSTA). Alternatively, a group may include more than one wireless communication device, and different groups may include a common wireless communication device. The manager/coordinator wireless communication device supports subsequent communications with the other wireless communication devices (e.g., SMSTAs) based upon the RAWs specified within the RAW IEs of the beacons according to different respective DTIM periodicities.
The following four diagrams show communication between an AP and a number of STAs at different respective times. The AP communicates with different respective groups of STAs during each of the respective times. It is noted that a group may include as few as one STA, as many as all STAs, or any number of the STAs in between.
In
In an example of using beacons, any one or more respective wireless communication devices (e.g., STAs) within a wireless communication network (e.g., a basic services set (BSS), etc.) may operate to listen for a beacon before a listen interval, and the network coordinator or manager (e.g., an access point (AP)) may periodically send such a bitmap on one or more of its respective begins as an information element (IE). The bit mask is called the traffic indication map (TIM) and may consist of a particular number of bits (e.g., 2008 in one embodiment), such that each respective bit represents the association ID (AID) of a particular one of the wireless communication devices (e.g., STAs). In certain embodiments, a smaller TIM bitmap may be employed if it is expected that less than all of the wireless communication devices (e.g., STAs) will be awake such that certain of them may be asleep. In certain situations, bitmap values passed within the TIM information element may be referred to as a partial virtual bitmap, and in such situations in which transmission of only a partial bitmap is employed, additional fields (e.g., bitmap control in length) of the TIM information element may optionally be employed to accommodate this particular operational mode.
In another example of using beacons, when a wireless communication device awakens from a sleep or reduced power state, it may determine whether or not a corresponding AID value associated therewith (e.g., within the TIM) is set that indicates the AP has one or more buffered frames intended for it. Also, a delivery traffic indication message (DTIM) may employed so that a given wireless communication device is provided a suggested wait time, and such a suggested wait time may be viewed as being a multiple integer of the beacon interval. For example, a given wireless communication device may be directed to awaken every Nth beacon interval (e.g., where N=2, 3, 4, and/or any other integer value etc., for awakening at suggested times) so that that particular wireless communication device need not necessarily awaken each and every beacon interval and attempt to process information associated with the beacon (e.g., such as monitoring its respective AID value therein). The bottom portion of the diagram shows four different wireless communication device groups that will communicate with the AP at different respective times. Each respective beacon may include more than one DTIM sub-structure to indicate more than one wireless communication device group that is to communicate within that beacon interval. Such a beacon will include a RAW IE that specifies the appropriate RAWs during which the wireless communication device groups may communicate with the AP.
As also mentioned above, there may be multiple respective streams or data flows (upstream and/or downstream) associated with the various wireless communication devices (e.g., STAs, SMSTAs, etc.) within a given wireless communication network (e.g., a basic services set (BSS), etc.). Also, different respective streams or data flows may have different respective characteristics (e.g., periodicities which may be greater than or less than a beacon interval (BI), different respective offsets, etc.). With different respective periodicities associated with different respective streams, more than one respective stream may align together at any given DTIM. Also, since different respective streams may have different respective offsets (e.g., even if such different respective streams have the same periodicity), streams having a common periodicity may be relatively offset with respect to each other. This DTIM related information is included within a RAW of a RAW IE.
Moreover, different respective streams may be made in different respective directions (e.g., some streams uplink only, others streams downlink only, while other streams corresponding to both uplink and downlink). Also, different respective communications may have different respective packet durations (e.g., depending on the amount of information to be conveyed in one or both directions).
For example, when operating in accordance with DTIM functionality associated with one or more beacons, a given wireless communication device will awaken at those particular beacon times or beacon intervals corresponding thereto.
Referring again to the bottom portion of the diagram, more than one respective DTIM sub-structure may be included within a beacon, and a given wireless communication device may be associated with more than one respective DTIM sub-structure. As such, a given wireless communication device may awaken based upon different respective DTIM sub-structures (e.g., awaken based upon a first DTIM sub-structure having a first periodicity, and also awaken based upon a second DTIM sub-structure having a second periodicity, etc.). As may be understood, for different respective operations which may be associated with different respective streams, the use of employing more than one different respective DTIM sub-structures within a given beacon allows for great selectivity and adaptability in terms of ensuring that any of a number of respective streams may be appropriately serviced by one or more wireless communication devices.
Considering the bottom portion of the diagram, looking at the beacon at the left-hand side of the diagram, two (2) DTIM sub-structures are included within the beacon each corresponding to different respective periodicities. A DTIM sub-structure having a periodicity of 1 (e.g., T=1 group) occurs at every single beacon or beacon interval. However, the DTIM sub-structure having a periodicity of 3 (e.g., T=3 group 1) occurs only at every third beacon or beacon interval. Also, in the second leftmost beacon at the left-hand side of the diagram, three (3) DTIM sub-structures are included within the beacon each corresponding to different respective periodicities [e.g., the DTIM sub-structure having a periodicity of 1 (e.g., T=1 group), a DTIM sub-structure having a periodicity of 7 (e.g., T=7 group), as well as a second DTIM sub-structure having a periodicity of 3 (e.g., T=3 group 2) that is relatively offset with respect to the DTIM sub-structure having a periodicity of 3 (e.g., T=3 group 1)].
Also, given the different respective periodicities of different respective DTIM groups as well as different respective offsets which may sometimes be associated with different respective DTIM groups, there may be some instances in which more than one DTIM group coincides at any given DTIM, beacon or beacon interval (e.g., for example, the DTIM sub-structure having a periodicity of 1 (e.g., T=1 group) will actually coincide or intersect with each and every other DTIM substructure group). Analogously, the DTIM sub-structure having a periodicity of 7 (e.g., T=7 group) will coincide or intersect with the DTIM sub-structure having a periodicity of 3 (e.g., T=3 group 1) every 21st DTIM, beacon or beacon interval.
Generally speaking, at least one restricted access window (RAW) information element (IE) is included in the beacon frame body to specify any number of restricted access windows (RAWs) as well as the corresponding DTIM sub-structure associated therewith. As may be understood, a given DTIM has an associated sub-structure associated with it, and each one also is associated with a given wireless communication device group (or stream group). Correlation between those wireless communication devices associated with a given group ensures communications are performed appropriately so that all associated streams related to a given DTIM group are appropriately serviced. Also, one or more DTIM parameters may be included for each respective restricted access window (RAW). For example, GDP is the count of BIs between successive DTIMs for this group. If GDP=1, then this group has a RAW every target beacon transmission time (TBTT). If GDP=2, then this group has a RAW every other TBTT. Group ID (or GROUP ID) for a RAW implies that this is a DTIM, no DTIM count needed.
Again, each RAW corresponds to one respective wireless communication device group. For example, in certain embodiments, for each respective RAW, one respective association ID (AID) or group AID (e.g., a wireless communication device group) may be employed such that each respective group will have a RAW following the corresponding and associated beacon including the DTIM sub-structure associated therewith. As such, DTIM information may be associated on a per group basis among the respective wireless communication devices within the system.
It is noted within this particular diagram as well as with respect to others, any desired respective sizes of the respective fields therein may be employed in various embodiments (e.g., a great deal of latitude is left to implementation design and selection such as may be determined by a designer or implementer of such functionality within one or more respective wireless communication devices within a wireless communication system). For example, in one possible embodiment, the group DTIM period (GDP) may include 15 bits, the group repetition count (GRC) may include 4 bits, and the group repetition period (GRP) may include 8 bits. The GRC is a count of group RAW repetitions for this BI. For example, if GRC=0, there is one repetition (1×) of RAW within this BI. If GRC=1, 2× of RAW within this BI, and so on. GRP is the period of group RAW repetitions for this BI.
An example of the size of GDP (Group DTIM Period) field being 15 bits is shown below:
Considering this example above, if the beacon interval (BI) were to increase, then the GDP field may also need to increase correspondingly.
An example of the size of GRC (Group Repetition Count) field being 4 bits is shown below:
Considering this example above as well, if the BI were to increase, then the GRC field may also need to increase.
Also, an example of the size of GRP (Group Repetition Period) field being 8 bits is shown below:
Similarly, considering this example above as well, if the BI were to increase, then the GRP field may also need to increase.
In certain possible embodiments, four (4) respective bytes may be added per RAW description; however, not all respective RAWs necessarily need this description. In one possible embodiment, one respective bit may be added to the RAW description to indicate a presence of GRC and GRP fields so that those respective fields may be appropriately handled in those situations in which they do in fact occur.
The method 900 then continues by supporting first communications with a first wireless communication device group during first RAWs having a first delivery traffic indication message (DTIM) periodicity, as shown in a block 930. Also, the method 900 operates by supporting second communications with a second wireless communication device group during second RAWs having a second DTIM periodicity, as shown in a block 940.
It is noted that the various operations and functions described within various methods herein may be performed within a wireless communication device (e.g., such as by the baseband processing module 264, the processing module 250 as described with reference to
Examples of some components may include one of more baseband processing modules, one or more media access control (MAC) layers, one or more physical layers (PHYs), and/or other components, etc. For example, such a baseband processing module (sometimes in conjunction with a radio, analog front end (AFE), etc.) can generate such signals, frames, etc. as described herein as well as perform various operations described herein and/or their respective equivalents.
In some embodiments, such a baseband processing module and/or a processing module (which may be implemented in the same device or separate devices) can perform such processing to generate signals for transmission to another wireless communication device using any number of radios and antennae. In some embodiments, such processing is performed cooperatively by a processor in a first device and another processor within a second device. In other embodiments, such processing is performed wholly by a processor within one device.
The present invention has been described herein with reference to at least one embodiment. Such embodiment(s) of the present invention have been described with the aid of structural components illustrating physical and/or logical components and with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claims that follow. Further, the boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality. To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claimed invention. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof.
As may also be used herein, the terms “processing module,” “processing circuit,” “processing circuitry,” “processing unit” and/or “processor” may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module, module, processing circuit, and/or processing unit may be, or further include, memory and/or an integrated memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of another processing module, module, processing circuit, and/or processing unit. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that if the processing module, module, processing circuit, and/or processing unit implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Still further note that, the memory element may store, and the processing module, module, processing circuit, and/or processing unit executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the Figures. Such a memory device or memory element can be included in an article of manufacture.
As may also be used herein, the term(s) “configured to”, “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for an example of indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “configured to”, “operable to”, “coupled to”, or “operably coupled to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform, when activated, one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item.
Unless specifically stated to the contra, signals to, from, and/or between elements in a figure of any of the figures presented herein may be analog or digital, continuous time or discrete time, and single-ended or differential. For instance, if a signal path is shown as a single-ended path, it also represents a differential signal path. Similarly, if a signal path is shown as a differential path, it also represents a single-ended signal path. While one or more particular architectures are described herein, other architectures can likewise be implemented that use one or more data buses not expressly shown, direct connectivity between elements, and/or indirect coupling between other elements as recognized by one of average skill in the art.
The term “module” is used in the description of one or more of the embodiments. A module includes a processing module, a functional block, hardware, and/or software stored on memory for performing one or more functions as may be described herein. Note that, if the module is implemented via hardware, the hardware may operate independently and/or in conjunction with software and/or firmware. As also used herein, a module may contain one or more sub-modules, each of which may be one or more modules.
While particular combinations of various functions and features of the one or more embodiments have been expressly described herein, other combinations of these features and functions are likewise possible. The present disclosure of an invention is not limited by the particular examples disclosed herein and expressly incorporates these other combinations.
Patent | Priority | Assignee | Title |
10039018, | Oct 27 2011 | Mueller International, LLC | Systems and methods for recovering an out-of-service node in a hierarchical network |
10070403, | Mar 09 2016 | Mueller International, LLC | Time beacons |
10097411, | May 23 2016 | Mueller International, LLC | Node migration |
10178617, | May 01 2017 | Mueller International, LLC | Hail and acceptance for battery-powered devices |
10200947, | Jul 11 2016 | Mueller International, LLC | Asymmetrical hail timing |
10267652, | Jan 23 2018 | Mueller International, LLC | Node communication with unknown network ID |
10582347, | Apr 14 2016 | Mueller International, LLC | SMS communication for cellular node |
10582463, | Mar 09 2016 | Mueller International, LLC | Time beacons |
10623833, | May 23 2016 | Mueller International, LLC | Node migration |
10638419, | Jul 11 2016 | Mueller International, LLC | Asymmetrical hail timing |
10768016, | Jan 23 2018 | Mueller International, LLC | Node communication with unknown network ID |
11272266, | May 23 2016 | Mueller International, LLC | Node migration |
9807793, | Jun 17 2012 | AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LIMITED | Multiple delivery traffic indication map (DTIM) per device within single user, multiple user, multiple access, and/or MIMO wireless communications |
Patent | Priority | Assignee | Title |
7379435, | Apr 28 2005 | Cisco Technology, Inc. | Determining broadcast message transmit times for a wireless device having a plurality of WLAN MAC addresses |
20070195727, | |||
20100165963, | |||
20110205998, | |||
20120120892, | |||
20130128798, | |||
20140119268, | |||
20140328238, | |||
20150003367, | |||
JP2011217026, | |||
KR1020080083086, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Jun 06 2013 | Broadcom Corporation | (assignment on the face of the patent) | / | |||
Jun 06 2013 | FISCHER, MATTHEW JAMES | Broadcom Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 030563 | /0430 | |
Feb 01 2016 | Broadcom Corporation | BANK OF AMERICA, N A , AS COLLATERAL AGENT | PATENT SECURITY AGREEMENT | 037806 | /0001 | |
Jan 19 2017 | BANK OF AMERICA, N A , AS COLLATERAL AGENT | Broadcom Corporation | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS | 041712 | /0001 | |
Jan 20 2017 | Broadcom Corporation | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 041706 | /0001 | |
May 09 2018 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LIMITED | MERGER SEE DOCUMENT FOR DETAILS | 047229 | /0408 | |
Sep 05 2018 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LIMITED | CORRECTIVE ASSIGNMENT TO CORRECT THE PATENT NUMBER 9,385,856 TO 9,385,756 PREVIOUSLY RECORDED AT REEL: 47349 FRAME: 001 ASSIGNOR S HEREBY CONFIRMS THE MERGER | 051144 | /0648 | |
Sep 05 2018 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LIMITED | CORRECTIVE ASSIGNMENT TO CORRECT THE EFFECTIVE DATE PREVIOUSLY RECORDED ON REEL 047229 FRAME 0408 ASSIGNOR S HEREBY CONFIRMS THE THE EFFECTIVE DATE IS 09 05 2018 | 047349 | /0001 |
Date | Maintenance Fee Events |
May 03 2019 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Apr 28 2023 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Date | Maintenance Schedule |
Nov 03 2018 | 4 years fee payment window open |
May 03 2019 | 6 months grace period start (w surcharge) |
Nov 03 2019 | patent expiry (for year 4) |
Nov 03 2021 | 2 years to revive unintentionally abandoned end. (for year 4) |
Nov 03 2022 | 8 years fee payment window open |
May 03 2023 | 6 months grace period start (w surcharge) |
Nov 03 2023 | patent expiry (for year 8) |
Nov 03 2025 | 2 years to revive unintentionally abandoned end. (for year 8) |
Nov 03 2026 | 12 years fee payment window open |
May 03 2027 | 6 months grace period start (w surcharge) |
Nov 03 2027 | patent expiry (for year 12) |
Nov 03 2029 | 2 years to revive unintentionally abandoned end. (for year 12) |