Revision history [back]

click to hide/show revision 1
initial version

AllJoyn is a message-based communication mechanism and applications using AllJoyn exchange messages between one another. AllJoyn Core framework consists of AllJoyn Client library (of which there are two implementations available, namely Standard and Thin) and AllJoyn Routing node. Applications built using AllJoyn Client library are termed as Leaf nodes and a leaf node connects to a Routing node.

AllJoyn Routing node handles discovery, connectivity, session management, forwarding and delivery of messages to applications among other functions. One of the crucial functions of an AllJoyn Routing node is to discover and connect to other routing nodes (such a mesh of connected routing nodes is termed as AllJoyn Bus). Further, AllJoyn Routing node also makes itself discoverable to leaf nodes. Discovery between nodes takes place via an IP-multicast based mechanism termed as NGNS.

Base Services are a set of useful abstractions built on top of AllJoyn Core framework. Base Services consist of functionalities that are common requirements for IoT scenarios. Onboarding service is one such base service.

To reiterate, Discovery is a core functionality provided by AllJoyn Routing node. Discovery is completely different from and independent of Onboarding service.

For instance, most IoT devices are headless (do not have elaborate screens) and require some form of Wireless configuration to connect them to a personal network. Onboarding service is a useful means of achieving this. Consider a SmartPlug, which is a headless IoT device. This SmartPlug would run an application that implements Onboarding service and is termed as the Onboardee _(the entity which we want to onboard onto the personal network)_. A smartphone or a tablet would run an application that implements Onboarding client and is termed as the Onboarder _(the entity which will assist the Onboardee with wireless configuration)_.

As mentioned at the link:

  1. Onboardee starts a small/temporary wireless network and broadcasts the SSID. Onboardee (SmartPlug) waits for the Onboarder (Smartphone) at this step.
  2. Onboarder connects to Onboardee, and in this small/temporary wireless network discovery between Onboarder and Onboardee takes place (via the earlier mentioned NGNS).

Because transfer of personal network credentials takes place during Onboarding, some form of human interaction is usually involved.

AllJoyn is a message-based communication mechanism and applications using AllJoyn exchange messages between one another. AllJoyn Core framework consists of AllJoyn Client library (of which there are two implementations available, namely Standard and Thin) and AllJoyn Routing node. Applications built using AllJoyn Client library are termed as Leaf nodes and a leaf node connects to a Routing node.

AllJoyn Routing node handles discovery, connectivity, session management, forwarding and delivery of messages to applications among other functions. One of the crucial functions of an AllJoyn Routing node is to discover and connect to other routing nodes (such a mesh of connected routing nodes is termed as AllJoyn Bus). Further, AllJoyn Routing node also makes itself discoverable to leaf nodes. Discovery between nodes takes place via an IP-multicast based mechanism termed as NGNS.

Base Services are a set of useful abstractions built on top of AllJoyn Core framework. Base Services consist of functionalities that are common requirements for IoT scenarios. Onboarding service is one such base service.

To reiterate, Discovery is a core functionality provided by AllJoyn Routing node. Discovery is completely different from and independent of Onboarding service.

For instance, most IoT devices are headless (do not have elaborate screens) and require some form of Wireless configuration to connect them to a personal network. Onboarding service is a useful means of achieving this. Consider a SmartPlug, which is a headless IoT device. This SmartPlug would run an application that implements Onboarding service and is termed as the Onboardee _(the entity which we want to onboard onto the personal network)_. A smartphone or a tablet would run an application that implements Onboarding client and is termed as the Onboarder _(the entity which will assist the Onboardee with wireless configuration)_.

As mentioned at the link:

  1. Onboardee starts a small/temporary wireless network and broadcasts the SSID. Onboardee (SmartPlug) waits for the Onboarder (Smartphone) at this step.
  2. Onboarder connects to Onboardee, and in this small/temporary wireless network discovery between Onboarder and Onboardee takes place (via the earlier mentioned NGNS).

Because transfer of personal network credentials takes place during Onboarding, some form of human interaction is usually involved.

AllJoyn is a message-based communication mechanism and applications using AllJoyn exchange messages between one another. AllJoyn Core framework consists of AllJoyn Client library (of which there are two implementations available, namely Standard and Thin) and AllJoyn Routing node. Applications built using AllJoyn Client library are termed as Leaf nodes and a leaf node connects to a Routing node.

AllJoyn Routing node handles discovery, connectivity, session management, forwarding and delivery of messages to applications among other functions. One of the crucial functions of an AllJoyn Routing node is to discover and connect to other routing nodes (such a mesh of connected routing nodes is termed as AllJoyn Bus). Further, AllJoyn Routing node also makes itself discoverable to leaf nodes. Discovery between nodes takes place via an IP-multicast based mechanism termed as NGNS.

Base Services are a set of useful abstractions built on top of AllJoyn Core framework. Base Services consist of functionalities that are common requirements for IoT scenarios. Onboarding service is one such base service.

To reiterate, Discovery is a core functionality provided by AllJoyn Routing node. Discovery is completely different from and independent of Onboarding service.

For instance, most IoT devices are headless (do not have elaborate screens) and require some form of Wireless configuration to connect them to a personal network. Onboarding service is a useful means of achieving this. Consider a SmartPlug, which is a headless IoT device. This SmartPlug would run an application that implements Onboarding service and is termed as the Onboardee _(the (the entity which we want to onboard onto the personal network)_. network). A smartphone or a tablet would run an application that implements Onboarding client and is termed as the Onboarder _(the (the entity which will assist the Onboardee with wireless configuration)_.configuration).

As mentioned at the link:

  1. Onboardee starts a small/temporary wireless network and broadcasts the SSID. Onboardee (SmartPlug) waits for the Onboarder (Smartphone) at this step.
  2. Onboarder connects to Onboardee, and in this small/temporary wireless network discovery between Onboarder and Onboardee takes place (via the earlier mentioned NGNS).

Because transfer of personal network credentials takes place during Onboarding, some form of human interaction is usually involved.