Channel structure for communication in wireless networks

• US 10,244,532 B2
• Filed: 12/30/2016
• Issued: 03/26/2019
• Est. Priority Date: 10/27/2016
• Status: Active Grant

• Current Assignee: Itron, Inc.
• Original Assignee: Itron, Inc.
• Inventors: Taylor, James Laurence, Bartier, Jerome, Barnes, Keith, Uhling, Thomas
• Primary Examiner(s): Wong, Warner
• Application Number:
  US15/395,743
• Publication Number:
  US 20180124785A1
• Time in Patent Office: 816 Days
• CPC Class Codes: H04B 1/713 using frequency hopping
• CPC Class Codes: H04B 1/7143 Arrangements for generation of hop patterns
• CPC Class Codes: H04B 1/7156 Arrangements for sequence synchronisation
• CPC Class Codes: H04L 12/1881 with schedule organisation, e.g. priority, sequence management
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04Q 2209/60 for transmitting utility meters data, i.e. transmission of data from the reader of the utility meter
• CPC Class Codes: H04Q 9/04 Arrangements for synchronous operation
• CPC Class Codes: H04W 36/20 for optimising the interference level
• CPC Class Codes: H04W 36/22 for handling the traffic
• CPC Class Codes: H04W 4/06 Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
• CPC Class Codes: H04W 48/18 Selecting a network or a communication service
• CPC Class Codes: H04W 48/20 Selecting an access point
• CPC Class Codes: H04W 52/0216 using a pre-established activity schedule, e.g. traffic indication frame
• CPC Class Codes: H04W 52/0219 where the power saving management affects multiple terminals
• CPC Class Codes: H04W 52/0274 by switching on or off the equipment or parts thereof
• CPC Class Codes: H04W 56/001 Synchronization between nodes
• CPC Class Codes: H04W 56/0015 one node acting as a reference for the others
• CPC Class Codes: H04W 56/002 Mutual synchronization
• CPC Class Codes: H04W 72/0446 Resources in time domain, e.g. slots or frames
• CPC Class Codes: H04W 72/0453 : Resources in frequency domain, e.g. a carrier in FDMA
• CPC Class Codes: H04W 72/121 : for groups of terminals or users
• CPC Class Codes: H04W 72/20 : Control channels or signalling for resource management
• CPC Class Codes: H04W 72/23 : in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 8/005 : Discovery of network devices, e.g. terminals
• CPC Class Codes: H04W 8/22 : Processing or transfer of terminal data, e.g. status or physical capabilities
• CPC Class Codes: H04W 84/20 : Master-slave selection or change arrangements
• CPC Class Codes: H04W 88/04 : adapted for relaying to or from another terminal or user
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Techniques for communicating channel data regarding a channel plan are described herein. For example, a device may communicate a channel information element that includes a tag indicating a first operating context to which to apply channel data regarding a channel plan. The channel information element may also include a reference tag to indicate whether the channel data is contained in the channel information element or has been previously received and/or to identify a second operating context associated with previously received channel data. If the reference tag indicates that the channel data is contained in the channel information element, the channel data may be extracted from the channel information element and applied to the first operating context. If the reference tag indicates that the channel data has been previously received, the previously received channel data may be accessed and applied to the first operating context.

Claims

1. One or more computer-readable media storing computer-readable instructions that, when executed, instruct a processing unit to perform operations comprising:

wirelessly receiving, by a first node of a wireless network and from a second node of the wireless network, a first communication including a channel information element, each of the first node and the second node comprising a full function device or a limited function device, the channel information element including;

a tag indicating a first operating context to which to apply channel data, the channel data indicating at least one of a channel plan, a generator function, a channel spacing, or a list of channels; and

a reference tag including one or more reference bits to (i) indicate whether the channel data is contained in the channel information element or has been previously received and/or (ii) identify a second operating context associated with previously received channel data to be used as the channel data;

in the event that the reference tag indicates that the channel data is contained in the channel information element, extracting the channel data from the channel information element and applying the extracted channel data to the first operating context;

in the event that the reference tag indicates that the channel data has been previously received, accessing the previously received channel data and applying the previously received channel data to the first operating context; and

based at least in part on the first operating context;

listening, by the first node, for a second communication from the second node;

or

sending, by the first node, the second communication to the second node.

2. The one or more computer-readable media of claim 1, wherein the operations further comprise:

receiving, by the first node, a third communication including a seed information element, the seed information element including;

a seed tag indicating a third operating context to which to apply seed data, the seed data indicating a seed value to input into the generator function; and

a seed reference tag including one or more seed reference bits to (i) indicate whether the seed data is contained in the seed information element or has been previously received and/or (ii) identify a fourth operating context associated with previously received seed data to be used as the seed data; and

using, by the first node, the seed information element to apply the seed data to the third operating context indicated by the seed tag, each of the third operating context and the fourth operating context comprising one of the first operating context, the second operating context, or an operating context that is different than the first operating context and the second operating context.

3. The one or more computer-readable media of claim 1, wherein the channel information element further includes a future transition element number that indicates when to apply the channel data to the first operating context, the future transition element number identifying a schedule element.

4. The one or more computer-readable media of claim 1, wherein the full function device comprises a mains powered device and the limited function device comprises a battery powered device.

5. The one or more computer-readable media of claim 1, wherein the wirelessly receiving is performed without receiving schedule data indicating a schedule active period or a schedule repetition interval.

6. A method of setting a channel structure, the method comprising:

wirelessly receiving, by a first node of a wireless network and from a second node of the wireless network, a first communication including a channel information element, each of the first node and the second node comprising a full function device or a limited function device, the channel information element including;

a tag indicating a first operating context to which to apply channel data, the channel data including at least one of a channel plan, a generator function, a channel spacing, or a list of channels; and

a reference tag including one or more reference bits to (i) indicate whether the channel data is contained in the channel information element or has been previously received and/or (ii) identify a second operating context associated with previously received channel data to be used as the channel data;

using, by the first node, the channel information element to apply the channel data to the first operating context; and

based at least in part on the first operating context;

listening, by the first node, for a second communication from the second node;

or

sending, by the first node, the second communication to the second node.

7. The method of claim 6, wherein the channel information element further includes a future transition element number that indicates when to apply the channel data to the first operating context, the future transition element number identifying a schedule element.

8. The method of claim 6, wherein:

the one or more reference bits of the reference tag indicate that the channel data is contained in the channel information element;

the channel information element further includes the channel data; and

the using the channel information to apply the channel data to the first operating context includes;

extracting the channel data from the channel information element; and

applying the extracted channel data to the first operating context.

9. The method of claim 6, wherein the one or more reference bits of the reference tag indicate that the channel data has been previously received;

and

wherein the using the channel information element to apply the channel data to the first operating context includes;

accessing the previously received channel data; and

applying the previously received channel data to the first operating context.

10. The method of claim 6, wherein the first communication further includes a seed information element that includes:

a seed tag indicating a third operating context to which to apply seed data, the seed data indicating a seed value to input into the generator function; and

a seed reference tag including one or more seed reference bits to (i) indicate whether the seed data is contained in the seed information element or has been previously received and/or (ii) identify a fourth operating context associated with previously received seed data to be used as the seed data; and

using, by the first node, the seed information element to apply the seed data to the third operating context indicated by the seed tag, each of the third operating context and the fourth operating context comprising one of the first operating context, the second operating context, or an operating context that is different than the first operating context and the second operating context.

11. The method of claim 10, wherein the seed information element further includes a future transition element number that indicates when to apply the seed data to the third operating context.

12. The method of claim 10, wherein:

the one or more seed reference bits of the seed reference tag indicate that the seed data is contained in the seed information element; and

the seed information element further includes the seed data.

13. The method of claim 6, wherein the using the channel information element to apply the channel data to the first operating context includes configuring a radio associated with the first node based at least in part on the first operating context.

14. The method of claim 6, wherein the using the channel information element to apply the channel data to the first operating context includes:

replacing at least one of a channel plan of the first operating context, a generator function of the first operating context, a channel spacing of the first operating context, or a list of channels of the first operating context.

15. A node comprising:

a radio configured to transmit a first communication including a channel information element, the node comprising a full function device or a limited function device;

one or more processors communicatively coupled to the radio; and

memory communicatively coupled to the one or more processors, the memory storing one or more instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising;

generating the channel information element, the channel information element including;

a tag indicating a first operating context to which to apply channel data; and

a reference tag including one or more reference bits to (i) indicate whether the channel data is contained in the channel information element or has been previously received and/or (ii) identify a second operating context associated with previously received channel data to be used as the channel data; and

causing the radio to listen for or transmit a second communication based at least in part on the first operating context and the channel data.

16. The node of claim 15, wherein the radio is configured to transmit the first communication during at least one of discovery, a Personal Area Network (PAN) configuration, a PAN configuration update, or a channel plan update.

17. The node of claim 15, wherein the first communication further includes a seed information element that includes:

a seed tag indicating a third operating context to which to apply seed data, the seed data indicating a seed value to input into a generator function; and

a seed reference tag including one or more seed reference bits to (i) indicate whether the seed data is contained in the seed information element or has been previously received and/or (ii) identify a fourth operating context associated with previously received seed data to be used as the seed data.

18. The node of claim 17, wherein the seed information element further includes a future transition element number that indicates when to apply the seed data to the third operating context.

19. The node of claim 17, wherein:

the one or more seed reference bits of the seed reference tag indicate that the seed data is contained in the seed information element; and

the seed information element further includes the seed data.

20. The node of claim 15, wherein the first operating context includes at least one of a channel plan, a generator function, a channel list, a schedule, an active or inactive period, a schedule repetition interval, a reference schedule element boundary element number, an event offset, an event repetition interval, or a seed value.