Case Study: Wearable AI Audio Pendant with Local Wake Word & Encrypted Audio Wearable IoT audio pendant development using Apollo510B, nRF54H20, and Anker THUS. Features 4-mic beamforming, local wake word detection, AES-256 encrypted rolling buffer, and secure BLE connectivity for privacy-first voice interaction.

Wearable IoT Audio Pendant Design & Development with Apollo510B & nRF54H20

At Adequate Infosoft, we develop intelligent wearable systems that combine embedded engineering, AI, and secure connectivity. This case study presents our work on an AI powered audio pendant built for real time voice interaction with strong privacy controls.

We handled the complete system including hardware integration, firmware development, audio processing, encryption, and cloud pipeline design. The result is a production ready prototype with local wake word detection, a 4 microphone beamforming system, an encrypted rolling buffer, and reliable end to end transcription.

Client: The client is a stealth mode, consumer-focused AI business producing a voice-enabled pendant with local artificial intelligence processing, secure MCU wearables and BLE connectivity.

Role: The team's role is the lead embedded systems developer (full stack by providing hardware integration, firmware, audio pipeline, security, and cloud back).

Outcome: The work effort is six months at full time equivalents. The team's output is a production-ready prototype (including a local wake word, a 4-mic beamforming system, encrypted audio buffers, and an end-to-end transcription pipeline).

Executive Summary

This project involved developing a sophisticated voice-activated pendant from silicon to cloud.

The device captures high-quality audio from a 4-mic array, performs local wake word detection and command recognition using the Anker THUS AI chip, manages security and power with the Apollo510B, and handles BLE communication via the nRF54H20.

The pendant is provided with high-quality audio through a microphone array of four microphones for local/remote audio recording. The device utilizes an Anker THUS AI chip for detecting wake words and recognizing commands; this chip also manages security and power through Apollo510B. The device transmits data to a mobile application via nRF54H20 using BLE.

Through the use of an encrypted rolling buffer, all recorded audio is stored and is transmitted to an associated mobile application for Cloud Transcription Services.

The final version of the device is ready for mass production and provides users with the capability to retain their privacy (because it processes data locally), their security (because all data is encrypted during storage/transfer), and their ability for complex searches (using Cloud Transcription Services).

Audio pendant with Apollo510B and nRF54H20 voice AI.

Hardware Architecture: Core Components

Processor Triad Overview

ComponentRoleKey Specifications
Anker THUS Local audio AI processing Wake word detection, command recognition, neural inference engine
Apollo510B Secure wearable MCU Arm Cortex-M55 @ 192MHz, 4MB NVM, 3.75MB RAM, secureSPOT 3.0, TrustZone
Nordic nRF54H20 BLE connectivity Dual Cortex-M33 @ 320MHz, 2MB flash, 1MB RAM, Bluetooth 5.4, -100dBm sensitivity

The features and capabilities available on this combination of three devices represent the intelligently-designed architecture for the secure master-controller-based wearable function of a pendant.

The Apollo510B serves as the primary, secure master controller by providing the critical functions of power management, encryption and orchestration for the complete operated system.

The ultra-low power architecture of the Apollo510B processor (30X more efficient than the Cortex-M4) is also critical for a pendant to provide one full day of use on a single small battery.

The nRF54H20 provides the ability to perform wireless communication independently due to its dedicated 48MHz wireless coprocessor, allowing the Apollo510B processor to enter a safe sleep state (while continuing BLE advertising) to conserve power.

This type of dual-processor architecture is essential for low-power wearables. The THUS Audio System (from Anker) offloads all audio AI processing from the nRF54H20 and provides secure location of sensitive voice data (in addition, provides a reduction in overall power consumption due to not streaming raw audio continuously).

Alternative considered: Using the nRF54H20 alone for both audio and BLE. Rejected because the Apollo510B's secureSPOT 3.0 provides hardware-isolated security domains essential for handling encrypted personal data.

4-Mic Array Integration

Microphone Selection & Placement

ParameterSpecification
Microphone typePDM digital MEMS (Knowles SPH0645LM4H or equivalent)
Array configuration4x omnidirectional, circular arrangement (90° spacing)
Sampling rate16 kHz (wake word), 48 kHz (command capture)
BeamformingFixed beamforming + Direction of Arrival (DOA) estimation

The 4-mic array connects to the Apollo510B via its stereo digital microphone PDM interfaces. The Apollo510B supports up to 4 PDM channels simultaneously, making it ideal for this configuration.

Audio Processing Pipeline

Audio Processing Pipeline

(Pipeline diagram placeholder)

Implementation notes:

  • The Apollo510B records raw PDM, then processes in PCM format. The audio is streamed to THUS from Anker via I2S at 16kHz for the wake word detection.
  • When the wake word is detected, an interrupt is triggered in Apollo510B from Anker THUS.
  • When Apollo510B receives the interrupt; it gets the last two seconds of the pre-roll buffer and continues to record until the end of the command.
  • AES-256 encryption is used via the Apollo510B's hardware crypto accelerator (secureSPOT 3.0).

Local Wake Word + Local Commands

Anker THUS Integration

The Anker THUS chip is primarily a neural inference engine optimized for audio AI tasks. Configuration includes:

FeatureConfiguration
Wake wordCustom "Hey Pendant" (trained with 2,000+ samples)
Local commands"Stop", "Save note", "Remind me", "What did I say?" (3-5 commands)
Model formatQuantized int8 TensorFlow Lite for Microcontrollers
Inference time< 50 ms for wake word detection
Power consumption~5mW active, ~0.5mW listening (always-on)

The training process was:

  • Collected 500 wake word samples from 20 different speakers (varied accents and genders)
  • Collected 2000 negative samples (ambient noise, other speech and other words)
  • Trained using anker's machine learning (ML) training pipeline (details provided under NDA)
  • Deployed as a 200 KB model file on THUS's internal memory directly.

The Apollo510B Cortex-M55 contains Helium (vector processing), which allows it to perform lightweight keyword spotting for a secondary (fallback) keyword trigger should the THUS be busy or in low power mode.

Encrypted Rolling Audio Buffer

Architecture

The encrypted rolling buffer is a core privacy feature. Audio is never stored in plaintext — even on the device.

ParameterValue
Buffer duration30 seconds (rolling)
EncryptionAES-256-GCM (Galois/Counter Mode for authenticity)
Key storageApollo510B secureSPOT 3.0 hardware secure element
Key derivationECDH P-256 (paired with phone during setup)
ZeroizationOn device power loss or phone disconnect

Implementation

The Apollo510B's secureSPOT 3.0 provides:

  • Hardware-isolated key storage (inaccessible to firmware)
  • True random number generator for IV/nonce generation
  • Side-channel attack protection (timing/power analysis countermeasures)

Buffer operation:

  • Audio is continuously captured (even before wake word)
  • Each 256-byte chunk is encrypted with AES-256-GCM using a unique IV
  • Encrypted data + auth tag (16 bytes) is stored in a circular buffer
  • When buffer fills, oldest data is overwritten (rolling)
  • On wake word, pre-roll (2 seconds before wake) + command (until silence) is extracted

Security benefit: If device is lost or stolen, audio cannot be recovered without the phone's private key (which never leaves the paired phone).

Key Exchange Protocol (BLE)

Exchange Protocol

(Key exchange diagram placeholder)

BLE Connectivity (Nordic nRF54H20)

Architecture

The nRF54H20 connects to the Apollo510B via SPI (high-speed, up to 32 MHz).

InterfacePurpose
SPI (master/slave)Audio data transfer (encrypted chunks)
UARTCommand/control, status updates
Interrupt (GPIO)Wake notification from nRF54H20

Advantages of using the Nordic nRF54H20 in the project:

  • It features a dedicated 48MHz network processor, allowing for the BLE stack to run independently from the Apollo510B.
  • It boasts a sensitivity rating of -100dBm when transmitting at 1Mbps, ensuring a reliable connection when the pendant is worn under clothing.
  • The transmitter provides a maximum power output level of +10dBm, producing longer transmission distances and improved performance when worn as a body-worn device.
  • It has earned PSA Level 3 certification, providing IoT users with the most secure method available, and matching the Apollo510B's security standards.

BLE Services Implemented

ServiceUUIDCharacteristics
Audio Stream0000FFE0-0000-1000-8000-00805F9B34FBEncrypted audio chunks, sequence number, ACK
Command0000FFE1-0000-1000-8000-00805F9B34FBWake word status, battery level, errors
Configuration0000FFE2-0000-1000-8000-00805F9B34FBCloud API keys, wake word sensitivity

Performance Metrics:

  • Audio Transfer Rate: 16 kB/s (16kHz/16-bit PCM)
  • Achieved Throughput: ~25 kB/s (including overhead)
  • BLE Connection Interval: 15 ms (low latency mode) and 200 ms (power save mode)
  • nRF54H20 Tx Peak Current: ~4 mA
  • Connected But No Data (Idle) Current: ~15 µA

Phone/Cloud Transcription Pipeline

Architecture

Pendant → BLE → Phone App → (optional) Cloud API → Transcription

Phone App Responsibilities (iOS & Android)

  • Management of BLE Connections
  • Decryption of Audio Chunks Using AES-256-GCM
  • Reassembly of Command Files (audio format WAV) From Audio
  • Optional Local Transcription Of Audio Chunk = On Device ASR
  • Optional Cloud Transcription Of Audio Chunk = OpenAI Whisper, Google Speech-to-Text, or Custom

Cloud transcription flow (when used):

Phone → HTTPS/TLS → Cloud API → Transcription → Text returned to phone → Notification

The phone app handles all cloud interactions, not the pendant. This keeps the pendant off the internet entirely (privacy/compliance benefit).

Local vs Cloud Decision

ConditionAction
Command recognized locallyExecute immediately, no cloud round trip
Unrecognized commandSend audio to cloud for full transcription
No cell/Wi-Fi (but BLE connected)Store encrypted audio on phone for later upload
Sensitive query (user configurable)Never leave device — local processing only

Power Management

System Power States

StateActive ComponentsPowerDuration
Deep sleepApollo510B (RTC only), nRF54H20 (advertising)~5 µAMost of day
ListeningApollo510B PDM + THUS (wake word detection)~3 mAAlways-on
RecordingApollo510B + THUS + nRF54H20 (Tx)~25 mA< 30 seconds per command
BLE streamingnRF54H20 (Tx) + Apollo510B (encryption)~15 mADuring transfer

250 mAh Li-Polymer powered (small-sized pendant)

Battery Approximate runtime: approximately one day (full day equals approximately 12+ hours usage with typical usage of 50 commands/day)

Low power features supported by the Apollo510B

TurboSPOT technology supports "always-on" listening with Apollo510B.

  • Subthreshold voltage operation that reduces leakage current
  • 30 times better AI power efficiency than Cortex-M4
  • By providing additional processing 16 times faster than if executing a wake word command as part of the Apollo510B's normal operation, back-up processing of wake words will complete faster.

Problems and Solutions

Challenge 1: Synchronizing Audio between THUS and Apollo510B

Symptom: Each device has its independent audio capture path which causes them to lose their synchronization by a few samples over time.

Resolution: The PDM clock used by the Apollo510B is also used by the THUS (master clock of 12.288 MHz, divided down to generate 16kHz). An interrupt generated by the THUS on frame sync is used by the Apollo510B's rolling index of the buffer to keep the rolling indexes aligned to one another.

Challenge 2: Performance of Encrypted Buffers

Symptom: AES-256 encryption of each audio chunk introduced approximately 8 ms of latency per each audio chunk (256 bytes), which caused buffer overruns.

Resolution: The Apollo510B's hardware crypto engine (secureSPOT 3.0) can process an AES-256 encryption in less than 100 µs for each audio chunk. When switching AES from a software implementation to a hardware implementation, the encryption overhead was reduced by approximately 98%.

Challenge 3: Bluetooth Low Energy (BLE) Throughput with Encryption

Symptom: Due to the authentication tag (16 bytes) used by the AES-256 encryption of each audio chunk (256 bytes), that exceeds the BLE maximum transmission unit (MTU)(maximum of 256 bytes) causing audio chunks to be fragmented and sent over multiple packets.

Resolution: The BLE MTU was increased from 256 bytes to 512 bytes (this is supported by the Bluetooth 5.2 specification and nRF54H20 device). Therefore, each audio chunk fits into a single packet, reducing the overhead associated with multiple packets by ~40%.

Production Testing & Validation

Test CategoryScopeResult
Wake word accuracy10,000 test utterances, 20 speakers98.7% detection, 0.5% false positives/hour
Battery lifeContinuous listening + 50 commands/day14 hours (exceeds 12-hour requirement)
BLE rangeBody-worn, phone in pocket99.9% packet success (no drops)
Encryption validationNIST test vectorsPass (all encryption modes)
Rolling buffer integrityPower cycle during recordingNo audio loss, successful recovery
Cloud transcription latencyTypical command1.2 seconds (4G), 0.8 seconds (Wi-Fi)

Deliverables Summary

ComponentDeliverable
HardwareFully assembled pendant prototype (10 units)
FirmwareApollo510B codebase (C, Ambiq SDK), nRF54H20 codebase (Zephyr RTOS)
ML modelsAnker THUS wake word + command model files
Phone SDKiOS (Swift) and Android (Kotlin) BLE audio streaming libraries
Cloud backendReference implementation (Node.js + OpenAI Whisper)
DocumentationFull design files (schematics, PCB layout, BOM), API documentation, test reports

Conclusion

The "dream version" audio pendant was successfully delivered as a fully functional production prototype. This prototype allows for:

  • Privacy first architecture - capable of wake word detection on a local AI chip, sound never leaves the necklace in plaintext
  • Security hardened - AES-256 encryption, secure keys stored in a hardware isolated manner (Apollo510B secureSPOT)
  • Professional audio quality - has 4 microphones which form a beamforming array to attenuate background noise
  • Seamless connectivity - nRF54H20 has a low power, robust Bluetooth low energy connection even when worn under clothing
  • Scalable intelligence - local commands will provide low-latency capability and; cloud transcription will provide response capability to more complicated spoken requests

This has validated that the component triad of (Anker THUS + Apollo510B + nRF54H20 + 4-mic array) is not only a theoretical "dream" but also a practical and buildable system with established leading levels of security, power efficiency and audio quality.

Additionally, the AES-256 encrypted rolling buffer has also addressed the most significant consumer privacy issue with respect to always listening devices and, overall, the local-first architecture helps to minimize reliance on the cloud whilst preserving advanced features and benefits.

What Our Clients Say About Us

Client satisfaction is our ultimate goal. Here are some kind words of our precious clients they have used to express their satisfaction with our service.

Leadership That Leads Worldwide

With a physical presence in over 15 countries and a global footprint spanning 25+ countries, we are ready to serve you anywhere. Location, language, or culture is never a barrier, because our global team can work with you in your language. Our strong international team ensures seamless collaboration across borders We have a strong tech team, highly recognized in their domains, with extensive technical expertise.