The exPL Network Stack is defined from a generic model related to the OSI 7-layer model. The specific layout and terminology are closely related to the Zigbee standard specification. The stack model defines interworking interfaces where developers can "plug-in" new adaptations. The layer definitions also allow a developer to understand the expectations and interfaces of the layers above a new layer under development. By following the stack definitions the developer can ensure that when adding new network transports they get the most code reuse and extend the stack in a manor expected by other developers. The stack model also defines a common vocabulary for documentation and to use when discussing the code.
The exPL network stack specification defines how various physical layer connections are implemented. The ultimate goal of each stack is to accept and present xPL messages to the xPL application using a consistent interface regardless of the underlying physical layer. This allows the developer to build applications without considering how the end user might interconnect the devices.
The exPL network stack specification defines how various physical layer connections are implemented. The ultimate goal of each stack is to accept and present xPL messages to the xPL application using a consistent interface regardless of the underlying physical layer. This allows the developer to build applications without considering how the end user might interconnect the devices.
Table of contents
exPL Network Stack Reference Diagram
The stack model defines the following entities:- SAP: Service Access Point - The SAP specifies a well defined interface that upper layers use to communicate with the lower layers. This interface is typically implemented as a library function call and specifies the calling parameters, expected behavior, and the return values.
- DE: Data Entity - The DE specifies the service access point and behavior when forwarding data between stack layers.
- ME: Management Entity - The ME specifies the service access point and behavior for any functions that manage the layer. These functions may include configuration, querying the layer's information stores, retrieving and clearing statistics, etc.
- IB: Information Base - The IB specifies any static storage for the layer. This typically includes configuration, statistics counters, and caches used when forwarding data.
;){kind=link}
Last wiki comments