Skip to main content
For the complete documentation index, see llms.txt.

Hubble Network developer documentation: integrate Bluetooth devices with terrestrial and satellite connectivity.

Register with Bluetooth®

Complete these steps to register your Hubble-connected product with the Bluetooth Special Interest Group (SIG).

Bluetooth Requirement​

The Bluetooth Launch Studio requirement is the formal qualification and declaration process mandated by the Bluetooth SIG. The process ensures technical compliance with Bluetooth Low Energy (LE) advertising, and grants permission to use the Bluetooth brand in bringing your product to market.

Hubble Network Inc. is a Bluetooth Member Company.

The Hubble Network SDK has completed the Bluetooth Qualification Process:

Hubble's qualification covers non-connectable BLE advertising only. Customers integrating the Hubble SDK do not need to reference Q369913 in their own Bluetooth qualification submissions — your silicon vendor's certified Core Design Numbers (DNs) are sufficient.

Pre-Requisites​

The registration process is completed via the Bluetooth Launch Studio online platform.

You will need the following to get started:

  • An active Bluetooth SIG company account. You may create one on the site.
  • Your product's chipset vendor's Core Design Number(s) (DNs). Note that this is either a single Complete Core DN or the pair: Core-Controller DN + Core-Host DN.
  • The TCRL (Test Case Reference List) – typically the default offered by Launch Studio.

Process Overview​

  1. Start a new product in Launch Studio
  2. Add your vendor's Core Design Numbers (DNs)
  3. Confirm implementation conformance
  4. Add required product text
  5. Confirm testing conformance
  6. Confirm product listing and submit

Steps to Register​

1. New Product in Launch Studio​

  • Log in to Bluetooth Launch Studio.
  • Click Create Product and choose Bluetooth LE.
  • When asked, "Do you include any existing Design(s)?", select Yes. You will use your product's chipset vendor's Core DN(s).

2. Required Design Numbers​

  • Add your chipset's Core DN(s). This is either the complete Core DN, or the pair Core-Host DN + Core-Controller DN.

Your vendor's Core DN(s) are sufficient to cover Hubble SDK integration. Hubble's SDK uses non-connectable BLE advertising only (ADV_NONCONN_IND), which is standard BLE GAP behavior already covered by your vendor's qualification. You do not need to add Hubble's DN (Q369913) to your product listing.

3. Implementation Conformance​

Since you are inheriting the Core features from your vendor's existing qualified design, you generally do not need to claim new Core features. If prompted for an Implementation Conformance (ICS) import, select No. Do not claim new Core features.

Note that Hubble's SDK only covers advertising and does not add any GATT services, Mesh, or LE Audio features. You do not need to add those claims.

4. Product Description​

You must provide a specific description of your product's implementation.

  • Product Name: Enter Your Product Name + "BLE with Hubble SDK".
  • Product Description: Use the suggested content to define how Hubble Network SDK is integrated to your product.

We've provided the following template below:

FieldSuggested Content
Product NameMy Product - BLE with Hubble SDK
Product DescriptionThis product uses a qualified Bluetooth® Core implementation from the chipset vendor and integrates the Hubble Network SDK for non-connectable LE advertising. The SDK broadcasts ADV_NONCONN_IND frames using Service Data – 16-bit UUID (0x16) with Hubble's member-assigned Service UUID 0xA6FC. No GATT services, connections, or pairing are implemented by the SDK. Core-Host and Core-Controller are inherited from the vendor's qualified designs.

5. Testing Conformance​

Because you reference existing, qualified Core DNs, you do not need to re-test the Core layer. Hubble's SDK is scoped to GAP Broadcaster advertising only and does not require additional profile test plans.

We recommend that you use the latest TCRL offered by Launch Studio (the default).

6. Submit Product Listing​

Before submitting your Product listing, confirm the following:

  • ✅ Product lists vendor Core DN(s) (Complete Core, or Host+Controller).
  • ✅ Description mentions ADV_NONCONN_IND, Service Data (0x16), UUID 0xA6FC, and no GATT/connection.
  • ✅ TCRL is the latest (default).
  • ✅ No extraneous ICS claims were added.