Null (00h)

Isotropic Sensor Network Specifications, Null: Ping and Padding Layer

OSI: Transport Layer

Keywords: keep-alive, padding in framing, encapsulation, low communication overhead, sensors, internet of things, embedded systems, sensor networks

Document: ISN-Null-1.0 released on September 15, 2018 by Isotel, (c) All Rights Reserved

Creative Commons License
Isotropic Network Specifications: Null Layer 1.0 by Isotel is licensed under a Creative Commons Attribution-NoDerivatives 4.0 International License.
Permissions beyond the scope of this license may be available at http://isotel.net/ref/ISN-Permissions.

Note: Any adaptations to this specifications made by groups, individuals or companies are according to the license not allowed for general publication, but we strongly encourage you to send your modifications back to us for further consideration for the next releases.

Scope

The scope of this project is to define the Isotropic Sensor Network User layers for broadcast and peer to peer connection in distributed sensor area network, wired or wireless, low and high data rate devices, battery powered devices, short-range devices with short operational space, low-cost devices to support trivial sensors, besides the fully featured devices.

Purpose

The purpose of this specifications is to provide a standard for low complexity, low cost, and low power (aware) consumption devices (sensors) to provide keep alive capability and padding for frame and packet alignment.

Definitions, Acronyms and Abbreviations

device
An entity containing this protocol implementation. Also referred as sensor device or just sensor or device.
frame
The format of aggregated bits that are transmitted together in time.
packet
The format of aggregated bits that are transmitted together in time across the physical medium.

Packet Format

Fields Protocol ID
Bits 8
Value 00h
Protocol ID:
defines the unique protocol identification number of the application protocol specific format

Keep alive

In many cases the underlying media cannot provide information whether a device is alive or not, or looking from a device side, whether host (peer) is connected or does it exist.

The device and host should thus support keep-alive capability in which, after reception of the packet with Null protocol only, then the queried device should respond either with some valid message or Null.

Padding

Some devices may due to internal optimization require padding bytes to align data structure to i.e. 32-bit boundaries. And in other cases packets may need to be filled to account a fixed size. In such cases the Null is used as a padding byte.

Document Changes

Date Release Changes
September 15, 2018 1.0 Initial Specifications

References

Disclaimer

Use of an ISOTEL specification is wholly voluntary. The ISOTEL disclaims liability for any personal injury, property or other damage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, or reliance upon this, or any other ISOTEL specification document.

The ISOTEL does not warrant or represent the accuracy or content of the material contained herein, and expressly disclaims any express or implied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or that the use of the material contained herein is free from patent infringement. ISOTEL specifications documents are supplied AS IS.

The existence of an ISOTEL specification does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the ISOTEL specification. Furthermore, the viewpoint expressed at the time a specification is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the specification. Every ISOTEL specification is subjected to review at least every five years for revision or reaffirmation. When a document is more than five years old and has not been reaffirmed, it is reasonable to conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any ISOTEL specification.

In publishing and making this document available, the ISOTEL is not suggesting or rendering professional or other services for, or on behalf of, any person or entity. Nor is the ISOTEL undertaking to perform any duty owed by any other person or entity to another. Any person utilizing this, and any other ISOTEL specifications document, should rely upon the advice of a competent professional in determining the exercise of reasonable care in any given circumstances.

Interpretations: Occasionally questions may arise regarding the meaning of portions of specifications as they relate to specific applications. When the need for interpretations is brought to the attention of ISOTEL, the ISOTEL will initiate action to prepare appropriate responses. Since ISOTEL specifications represent a consensus of concerned interests, it is important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason, ISOTEL and the members of its societies are not able to provide an instant response to interpretation requests except in those cases where the matter has previously received formal consideration.

Comments for revision of ISOTEL specifications are welcome from any interested party, regardless of membership affiliation with ISOTEL. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Comments on specifications and requests for interpretations should be addressed to Isotel d.o.o., Slovenia.

Attention is called to the possibility that implementation of this specification may require use of subject matter covered by patent rights. By publication of this specification, no position is taken with respect to the existence or validity of any patent rights in connection therewith. The ISOTEL shall not be responsible for identifying patents for which a license may be required by an ISOTEL specification or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention.