# US 2017/0289320 A1 · Method and apparatus for addressing in a resource-constrained network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0289320 A1
- Document ID: US20170289320A1
- Status: Published application
- Kind: A1
- Application number: 15/630,440
- Filed: 2017-06-22
- Published: 2017-10-05
- Earliest claimed: 2011-03-02
- Assignees: Blackbird Technology Holdings, Inc.
- Applicants: Blackbird Technology Holdings, Inc.
- Inventors: John Peter Norair
- Web page: https://patentgrep.com/patent/US20170289320A1

## CPC

- H04W 56/002: {Mutual synchronization}
- H04B 17/318: Received signal strength
- H04L 1/0061: {Error detection codes}
- H04L 1/0083: {Formatting with frames or packets; Protocol or part of protocol for error control}
- H04L 43/0847: {Transmission error}
- H04L 43/16: Threshold monitoring
- H04L 47/822: {Collecting or measuring resource availability data}
- H04L 49/555: {Error detection}
- H04L 69/22: Parsing or analysis of headers
- H04W 4/023: {using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds}
- H04W 28/0205: {at the air interface (dynamic wireless traffic scheduling H04W72/12)}
- H04W 28/04: Error control
- H04W 40/023: {Limited or focused flooding to selected areas of a network}
- H04W 48/08: Access restriction or access information delivery, e.g. discovery data delivery (signalling during connection H04W76/00)
- H04W 52/0235: {where the received signal is a power saving command}
- H04W 52/06: TPC algorithms
- H04W 52/242: {taking into account path loss}
- H04W 52/243: {taking into account interferences}
- H04W 52/245: {taking into account received signal strength}
- H04W 52/36: with a discrete range or set of values, e.g. step size, ramping or offsets
- H04W 52/54: Signalisation aspects of the TPC commands, e.g. frame structure
- H04W 56/001: {Synchronization between nodes}
- H04W 56/0025: {synchronizing potentially movable access points}
- H04W 72/0446: Resources in time domain, e.g. slots or frames
- H04W 72/0473: {the resource being transmission power}
- H04W 74/0808: using carrier sensing, e.g. carrier sense multiple access [CSMA]
- H04W 74/0816: with collision avoidance
- H04W 74/085: {collision avoidance}
- H04L 43/0882: Utilisation of link capacity
- Y02D 30/70: in wireless communication networks
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04B: TRANSMISSION
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## 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

### Claim 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.

### Claim 2 (depends on 1)

The method of claim 1, wherein said data-link-layer processing of said PDU comprises determining whether said PDU is a unicast-addressed PDU or non-unicast-addressed PDU.

### Claim 3 (depends on 2)

The method of claim 2, 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.

### Claim 4 (depends on 3)

The method of claim 3, 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.

### Claim 5 (depends on 2)

The method of claim 2, 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.

### Claim 6 (depends on 5)

The method of claim 5, 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.

### Claim 7 (depends on 6)

The method of claim 6, 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.

### Claim 8 (depends on 7)

The method of claim 7, 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.

### Claim 9 (depends on 7)

The method of claim 7, 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.

### Claim 10

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.

### Claim 11 (depends on 10)

The communication system of claim 10, wherein said data-link-layer processing of said PDU comprises determining whether said PDU is unicast-addressed or non-unicast-addressed PDU.

### Claim 12 (depends on 11)

The communication system of claim 11, 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.

### Claim 13 (depends on 12)

The communication system of claim 12, 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.

### Claim 14 (depends on 11)

The communication system of claim 11, 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.

### Claim 15 (depends on 14)

The communication system of claim 14, 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.

### Claim 16 (depends on 15)

The communication system of claim 15, 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.

### Claim 17 (depends on 16)

The communication system of claim 16, 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.

### Claim 18 (depends on 17)

The communication system of claim 17, 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.

### Claim 19

A communication system comprising:
an electronic device operable to:
receive a protocol data unit (PDU) comprising a plurality of addressing bits;
determine whether said received PDU is unicast-addressed, anycast-addressed, multicast-addressed, or broadcast-addressed PDU based on said plurality of addressing bits;
if said PDU is unicast-addressed, determine whether said PDU is destined for said electronic device during data-link-layer processing of said PDU; and
if said PDU is anycast-addressed or multicast-addressed, determine whether said PDU is destined for said device during transport-layer processing of said PDU.

### Claim 20 (depends on 19)

The communication system of claim 19, wherein:
said transport-layer processing comprises comparing a search token contained in said PDU to data stored in said electronic device; and
determining that said PDU is intended for said electronic device if a correlation between said search token and said data stored in said electronic device is above a threshold.
