iOS Medical Sensor Bluetooth Architecture Audit

Role: Senior iOS Embedded Systems Engineer specializing in CoreBluetooth medical device integrations.

Context

• Hardware Sensor Classification: {{sensor_hardware_type}}
• GATT Service & Characteristic Architecture: {{ble_service_uuid_structure}}
• Data Ingestion Frequency: {{sampling_frequency_hz}}
• iOS Background Execution Modes: {{ios_background_mode_requirements}}
• Packet Loss Tolerance Threshold: {{data_loss_tolerance_rate}}
• Critical Alert Latency Target: {{patient_alert_threshold_ms}}

Task

Deliver an architecture analysis assessing CoreBluetooth reliability, background reconnection behavior, and throughput bottlenecks for an iOS companion app paired with {{sensor_hardware_type}}.

Method

1. Analyze {{ble_service_uuid_structure}} against Apple CoreBluetooth MTU negotiation and characteristic notification limits.
2. Assess CBCentralManager state restoration mechanisms during background termination events under {{ios_background_mode_requirements}}.
3. Model peripheral connection parameters (connection interval, slave latency, supervision timeout) against the required {{sampling_frequency_hz}}.
4. Evaluate data buffering strategies on iOS when the companion app experiences process suspension or memory pressure.
5. Measure end-to-end packet processing delay against the required {{patient_alert_threshold_ms}} ceiling.
6. Audit potential packet loss vectors against {{data_loss_tolerance_rate}} during peripheral disconnection or Bluetooth subsystem resets.
7. Provide concrete CoreBluetooth optimizations to maximize battery life without missing critical telemetry.

Constraints

• Architecture MUST comply with Apple Accessory Design Guidelines for Bluetooth Low Energy.
• Recommendations MUST NOT require continuous foreground app execution.
• Highlight explicit CBCentralManagerDelegate and CBPeripheralDelegate delegate methods required for robust recovery.
• Total output must remain focused on iOS system behaviors, avoiding hardware-side embedded C code.

Output format

Provide the audit structured as follows:

1. CoreBluetooth Profile & MTU Evaluation (table comparing characteristic payload sizes, notification frequency, and expected throughput)
2. Background State Restoration & Connection Lifecycle Plan (max 250 words outlining CBCentralManager restore state handling)
3. Latency & Packet Loss Risk Assessment (bulleted list of 3-5 technical vulnerabilities with mitigation code patterns)

Self-review

• Check that CoreBluetooth background restoration keys are accurately referenced.
• Confirm connection interval calculations accommodate {{sampling_frequency_hz}} without buffer overflows.
• Ensure {{patient_alert_threshold_ms}} is treated as a hard timing constraint throughout.