Method and apparatus for addressing in a resource-constrained network

• US 9,497,715 B2
• Filed: 02/29/2012
• Issued: 11/15/2016
• Est. Priority Date: 03/02/2011
• Status: Active Grant

• Current Assignee: Multi-Flex Circuits Pty., Ltd.
• Original Assignee: Blackbird Technology Holdings, Inc (Haystack Technologies, Inc.)
• Inventors: Norair, John Peter
• Primary Examiner(s): Gillis, Brian J
• Assistant Examiner(s): Keller, Michael A
• Application Number:
  US13/408,461
• Publication Number:
  US 20120226822A1
• Time in Patent Office: 1,721 Days
• Field of Search: 709/245
• US Class Current: 1/1
• CPC Class Codes: H04B 17/318 Received signal strength
• CPC Class Codes: H04L 1/0061 Error detection codes
• CPC Class Codes: H04L 1/0083 Formatting with frames or packets; Protocol or part of protocol for error control
• CPC Class Codes: H04L 43/0847 Transmission error
• CPC Class Codes: H04L 43/0882 Utilisation of link capacity
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 47/822 Collecting or measuring resource availability data
• CPC Class Codes: H04L 49/555 Error detection
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04W 28/0205 at the air interface dynamic wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 28/04 Error control
• CPC Class Codes: H04W 4/023 using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 40/023 Limited or focused flooding to selected areas of a network
• CPC Class Codes: H04W 48/08 Access restriction or access information delivery, e.g. discovery data delivery signalling during connection H04W76/00
• CPC Class Codes: H04W 52/0235 where the received signal is a power saving command
• CPC Class Codes: H04W 52/06 TPC algorithms
• CPC Class Codes: H04W 52/242 taking into account path loss
• CPC Class Codes: H04W 52/243 taking into account interferences
• CPC Class Codes: H04W 52/245 taking into account received signal strength
• CPC Class Codes: H04W 52/36 : with a discrete range or set of values, e.g. step size, ramping or offsets
• CPC Class Codes: H04W 52/54 : Signalisation aspects of the TPC commands, e.g. frame structure
• CPC Class Codes: H04W 56/001 : Synchronization between nodes
• CPC Class Codes: H04W 56/002 : Mutual synchronization
• CPC Class Codes: H04W 56/0025 : synchronizing potentially movable access points
• CPC Class Codes: H04W 72/0446 : Resources in time domain, e.g. slots or frames
• CPC Class Codes: H04W 72/0473 : the resource being transmission power
• CPC Class Codes: H04W 74/0808 : using carrier sensing, e.g. carrier sense multiple access [CSMA]
• CPC Class Codes: H04W 74/0816 : with collision avoidance
• CPC Class Codes: H04W 74/085 : collision avoidance
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

An electronic device may receive a protocol data unit (PDU) comprising a plurality of addressing bits. Data-link-layer processing of the PDU may be based on each of the addressing bits. Network layer processing of the PDU may be based on a first subset of the plurality of addressing bits. Transport-layer processing of the PDU may be based on a second subset of plurality of addressing bits. The data-link-layer processing may comprise determining whether the PDU is unicast-addressed or non-unicast-addressed. For a unicast-addressed PDU, the data-link-layer processing may comprise determining whether the PDU is destined for the electronic device based on a comparison of a Target ID field of the PDU and a device ID of the electronic device. For a non-unicast-addressed PDU, the Target ID field may not be present, and whether the PDU is destined for the electronic device may be determined based on other criteria.

Claims

1. A method performed by an electronic device, the method comprising:

receiving a protocol data unit (PDU) comprising a plurality of addressing bits;

performing data-link-layer processing of said PDU based on each of said plurality of addressing bits;

performing network layer processing of said PDU based on a first subset of said plurality of addressing bits; and

performing transport-layer processing of said PDU based on a second subset of said plurality of addressing bits; and

wherein said data-link-layer processing of said PDU comprises determining whether said PDU is a unicast-addressed PDU or non-unicast-addressed PDU; and

wherein, in instances that said PDU is a unicast-addressed PDU, said data-link-layer processing comprises determining whether said PDU is destined for said electronic device based on a comparison of a Target ID field of said PDU and a device ID of said electronic device; and

wherein, in instances that said PDU is a non-unicast-addressed PDU, said Target ID field is not present in said PDU and whether said PDU is destined for said electronic device is determined based on criteria other than a device ID of said electronic device.

2. The method of claim 1, wherein, in instances that said PDU is a non-unicast-addressed PDU, said network-layer processing of said PDU comprises determining whether said PDU comprises a Routing Header field.

3. The method of claim 1, wherein, in instances that said PDU is a non-unicast-addressed PDU, said transport-layer processing of said PDU comprises determining whether said PDU comprises a Query Template field.

4. The method of claim 3, wherein, during said transport-layer processing of said PDU, said electronic device compares data in said Query Template field to data stored in said electronic device.

5. The method of claim 4, wherein, during said transport-layer processing of said PDU, a result of said comparison is utilized to determine whether said electronic device is an intended recipient of said PDU.

6. The method of claim 4, wherein, during said transport-layer processing of said PDU, a result of said comparison is utilized to determine whether to forward said PDU to another electronic device.

7. A communication system comprising:

an electronic device operable to;

receive a protocol data unit (PDU) comprising a plurality of addressing bits;

perform data-link-layer processing of said PDU based on each of said plurality of addressing bits;

perform network layer processing of said PDU based on a first subset of said plurality of addressing bits; and

perform transport-layer processing of said PDU based on a second subset of said plurality of addressing bits; and

wherein said data-link-layer processing of said PDU comprises determining whether said PDU is unicast-addressed or non-unicast-addressed PDU; and

wherein, in instances that said PDU is a unicast-addressed PDU, said data-link-layer processing comprises determining whether said PDU is destined for said electronic device based on a comparison of a Target ID field of said PDU and a device ID of said electronic device; and

wherein, in instances that said PDU is a non-unicast-addressed PDU, said Target ID field is not present in said PDU and whether said PDU is destined for said electronic device is determined based on criteria other than a device ID of said electronic device.

8. The communication system of claim 7, wherein, in instances that said PDU is a non-unicast-addressed PDU, said network-layer processing of said PDU comprises determining whether said PDU comprises a Routing Header field.

9. The communication system of claim 7, wherein, in instances that said PDU is a non-unicast-addressed PDU, said transport-layer processing of said PDU comprises determining whether said PDU comprises a Query Template field.

10. The communication system of claim 9, wherein, during said transport-layer processing of said PDU, said electronic device compares data in said Query Template field to data stored in said electronic device.

11. The communication system of claim 10, wherein, during said transport-layer processing of said PDU, a result of said comparison is utilized to determine whether said electronic device is an intended recipient of said PDU.

12. The communication system of claim 10, wherein, during said transport-layer processing of said PDU, a result of said comparison is utilized to determine whether to forward said PDU to another electronic device.