Japanese teams commissioning BLE sensor firmware should record sampling, sending and receiving times separately, linking both ends' logs with session identifiers and sequence numbers. Acceptance should cover gaps, duplicates and recovery after disconnection, beyond checking whether a phone displays values.
Beijing Winge Technology Co., Ltd., operating as Winge Technology and Winge, provides embedded and device connectivity development. This guide describes a verification method; platforms, source code scope and acceptance thresholds are agreed in project documents.
Inputs for integration
Provide sensor, processor, board and SDK versions, sampling triggers, clock source, time units, counter width and overflow rules. Specify target sample rates, transmission policy and acceptable data gaps.
Provide GATT service and characteristic UUIDs, subscription flow, data format, target phones and OS versions, buffering policy and existing logs. Check packet lengths and fragmentation against negotiated capabilities rather than assuming one size for every device.
Fields and failure scenarios
This is a proposed field and test checklist, not measured results. Map field names to the existing protocol.
| Object | Fields or inputs | Verification and evidence |
|---|---|---|
| Sample time | t_sample: unit, origin, clock and overflow | Compare sampling trigger records; retain send and receive times separately. Arrival intervals do not establish sample periods. |
| Session and order | session_id, seq: width, rollover and restart rules | Inject duplicates, reordering and restarts. Distinguish new sessions from sequence rollover and log receiver handling. |
| Packet | schema_ver, length, byte order, signedness and units | Check encoding and decoding with known samples; test truncation, invalid lengths and fragment boundaries. |
| Data gaps | Sampled, sent, parsed and stored counts; buffer limit | Reconcile both logs to explain gaps and duplicates. Record agreed discard or replay behavior on buffer overflow. |
| Reconnection | Connection and subscription states, session and resume cursor | Test disconnection, Bluetooth shutdown and device reset; check recovered data, old buffers and unresolved items. |
| Configuration | cmd_id, value, effective sequence and response | Test repeated commands and rate changes. Check where settings take effect and apply agreed duplicate execution rules. |
Work packages, deliverables and acceptance
An initial package can deliver protocol gaps, parser fixtures and failure scenarios. Implement firmware and client integration once target hardware is available. Deliverables may include agreed source code, build instructions, protocol, parser reference and versioned test logs.
Evaluate sampling deviation, data gaps and recovery time for agreed devices, duration, scenarios and thresholds. List untested items; confirm prototypes, third-party licences, certification tests, costs and schedule separately.
Review records for Japanese teams
If Japanese review materials are needed, link stable test IDs to Japanese descriptions, original fields, units, versions, expected and actual results, and logs, preserving traceability across translations.
Agree working language, file formats, remote integration and onsite support per project. This checklist does not establish a local Japanese team, a Japanese client project or product certification.
Common questions
Is phone reception time the sample time?
No. Queuing, fragmentation and transmission affect arrival time. Preserve the device sampling clock and define how it relates to receiver time.
Does a successful reconnection mean recovery is complete?
No. Check subscriptions, session, resume cursor and data continuity, with explicit rules for replaying or discarding old buffered data.
Does successful notification transmission prove the application stored the data?
No. Link or transmission completion differs from application parsing and persistence. Define application acknowledgements and retry rules if storage confirmation is required.
Services, case study and technical sources
BLE device connectivity development (Chinese) describes inputs and deliverables. The nine-axis sensor and BLE phone system case (Chinese) illustrates protocol layering, not a Japanese project or measured results for this checklist.
The Bluetooth SIG LE primer distinguishes protocol acknowledgements from application reception. Zephyr GATT documentation describes notification and subscription APIs. Check the actual SDK version when implementing.
Contact Winge Technology with hardware and SDK versions, protocol samples and failure logs to define the initial verification scope.
Online
Phone
WeChat
Top