Architecture
The SDK architecture is built on modularity and extensibility, accommodating a broad range of implementation requirements. The diagram below illustrates the role of the Hubble Network SDK within an embedded application:
Hubble Network SDK Architecture
The following sections summarize its primary components.
Service Modules
The Services Layer contains the core functionality of the SDK, including the satellite and BLE network modules. Applications interface with the SDK through these components, leveraging a high-level API that streamlines satellite and BLE communication.
Satellite Module
Warning
The satellite module is currently in pre-production and is not yet ready for production deployments.
Provides APIs to transmit data to the Hubble Network. Because satellite communication relies on Hubble Network, this module assumes ownership of the target radio and possibly other devices when in use.
BLE Network Module
Offers APIs to generate Bluetooth® advertisement packets, enabling connections to the Hubble Bluetooth Low Energy (BLE) Network. This module uses the standard Bluetooth protocol and does not assume ownership of any hardware. The application is responsible for managing the Bluetooth stack.
Note
Hubble Network Inc. is a Bluetooth Member Company.
The Hubble Network SDK has completed the Bluetooth Qualification Process:
Hubble Design Number: Q369913
Qualified Product Details: https://qualification.bluetooth.com/ListingDetails/307489
Port Layer
The Port Layer acts as an abstraction between the Service Modules and RTOS-specific implementations. It defines an API that simplifies porting the SDK to various RTOS environments beyond those natively supported.
The Project Organization page describes how these layers map onto the source tree, the naming conventions used throughout, and where new code should go.