Prepared By
Date / Year-Month-Day Approved Revision Document No
2014-10-21
E-mail Address
Adopted V1.0.0 BCS_SPEC
N.B.
SF WG
sf-main@bluetooth.org
BODY COMPOSITION SERVICE
Abstract:
This service exposes data related to body composition from a body composition analyzer intended for consumer healthcare and sports/fitness applications.
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
Page 2 of 16
Revision History
Revision V1.0.0
Date
(yyyy-mm-dd) 2014-10-21
Comments
Adopted by the Bluetooth SIG BoD
Contributors
Name
Robert Hughes
Company Intel Corporation
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
Page 3 of 16
Copyright © 2013 - 2014. The Bluetooth word mark and logos are owned by Bluetooth SIG, Inc. All copyrights in the Bluetooth Specifications themselves are owned by Ericsson AB, Lenovo (Singapore) Pte. Ltd., Intel Corporation, Microsoft Corporation, Motorola Mobility, LLC, Nokia Corporation and Toshiba Corporation. Other third-party brands and names are the property of their respective owners.
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
Page 4 of 16
Document Terminology
Bluetooth SIG has adopted Section 13.1 of the IEEE Standards Style Manual, which dictates use of the words “shall”, “should”, “may”, and “can” in the development of documentation, as follows:
The word shall is used to indicate mandatory requirements strictly to be followed in order to conform to the standard and from which no deviation is permitted (shall equals is required to). The use of the word must is deprecated and shall not be used when stating mandatory requirements; must is used only to describe unavoidable situations.
The use of the word will is deprecated and shall not be used when stating mandatory requirements; will is only used in statements of fact.
The word should is used to indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain course of action is deprecated but not prohibited (should equals is recommended that).
The word may is used to indicate a course of action permissible within the limits of the standard (may equals is permitted).
The word can is used for statements of possibility and capability, whether material, physical, or causal (can equals is able to).
The term Reserved for Future Use (RFU) is used to indicate Bluetooth SIG assigned values that are reserved by the Bluetooth SIG and are not otherwise available for use by implementations.
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
Page 5 of 16
Table of Contents
1
Introduction .................................................................................................................................... 6 1.1 Conformance ............................................................................................................................. 6 1.2 Service Dependency ................................................................................................................. 6 1.3 Bluetooth Specification Release Compatibility .......................................................................... 6 1.4 GATT Sub-Procedure Requirements ........................................................................................ 6 1.5 Error Codes ............................................................................................................................... 6 1.6 Byte Transmission Order ........................................................................................................... 6
Service Declaration ........................................................................................................................ 7 Service Characteristics ................................................................................................................. 8 3.1 Body Composition Feature ........................................................................................................ 8
3.1.1 Characteristic Behavior ....................................................................................................... 8 3.2 Body Composition Measurement .............................................................................................. 9
3.2.1 Characteristic Behavior ....................................................................................................... 9
3.2.1.1 Flags Field .................................................................................................................... 9 3.2.1.2 Body Fat Percentage Field ......................................................................................... 10 3.2.1.3 Time Stamp Field ....................................................................................................... 11 3.2.1.4 User ID Field ............................................................................................................... 11 3.2.1.5 Basal Metabolism ....................................................................................................... 11 3.2.1.6 Muscle Percentage ..................................................................................................... 12 3.2.1.7 Muscle Mass ............................................................................................................... 12 3.2.1.8 Fat Free Mass ............................................................................................................ 12 3.2.1.9 Soft Lean Mass ........................................................................................................... 12 3.2.1.10 Body Water Mass ................................................................................................... 12 3.2.1.11 Impedance .............................................................................................................. 12 3.2.1.12 Weight..................................................................................................................... 12 3.2.1.13 Height ..................................................................................................................... 12
3.3 Requirements for Time-Sensitive Data ................................................................................... 13
SDP Interoperability ..................................................................................................................... 14 Acronyms and Abbreviations ..................................................................................................... 15 References .................................................................................................................................... 16
2 3
4 5 6
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
Page 6 of 16
1 Introduction
The Body Composition Service (BCS) exposes data related to body composition from a body composition analyzer (Server) intended for consumer healthcare as well as sports/fitness applications.
1.1 Conformance
If a device claims conformance to this service, all capabilities indicated as mandatory for this service shall be supported in the specified manner (process-mandatory). This also applies to all optional and conditional capabilities for which support is indicated. All mandatory capabilities, and optional and conditional capabilities for which support is indicated, are subject to verification as part of the Bluetooth qualification program.
1.2 Service Dependency
This service is not dependent upon any other services.
1.3 Bluetooth Specification Release Compatibility
This specification is compatible with Bluetooth Core Specification 4.0 or later version of the Core Specification [1].
1.4 GATT Sub-Procedure Requirements
Requirements in this section represent a minimum set of requirements for a Server. Other GATT sub-procedures may be used if supported by both Client and Server. Table 1.1 summarizes additional GATT sub-procedure requirements beyond those required by all GATT Servers.
GATT Sub-Procedure Indications
Read Characteristic Descriptors
Write Characteristic Descriptors
Table 1.1: GATT Sub-procedure Requirements
Requirements M M M
There are no transport restrictions imposed by this service specification. Where the term BR/EDR is used throughout this document, this also includes the optional use of AMP.
1.5 Error Codes
This service does not define any Attribute Protocol Application Error codes.
1.6 Byte Transmission Order
All characteristics used with this service shall be transmitted with the least significant octet first (i.e., little endian). The least significant octet is identified in the characteristic definitions in [2].
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
Page 7 of 16
2 Service Declaration
In most cases, the Body Composition Service should be instantiated as a «Primary Service»; however this is defined in an higher level specification. The service UUID shall be set to «Body Composition» defined in [2].
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
Page 8 of 16
3 Service Characteristics
The following characteristics are exposed in the Body Composition Service. Only one instance of each characteristic is permitted within this service. The characteristic formats and UUIDs are defined in [2].
Where a characteristic can be indicated, a Client Characteristic Configuration descriptor shall be included in that characteristic as required by the Core Specification [1].
Characteristic Name
Body Composition Feature
Requirement M
Mandatory Properties Read
Optional Properties
Security
Permissions None None
Body Composition M Indicate Measurement
Table 3.1: Body Composition Service Characteristics Notes:
• •
Properties not listed as Mandatory or Optional are excluded for this version of this service Security Permissions of “None” means that this service does not impose any requirements
3.1 Body Composition Feature
The Body Composition Feature characteristic shall be used to describe the supported features of the Server.
Reserved for Future Use (RFU) bits in the Body Composition Feature characteristic value shall be set to 0.
3.1.1 Characteristic Behavior
When read, the Body Composition Feature characteristic returns a value that is used by a Client to determine the supported features of the Server.
The bits of the Body Composition Feature characteristic may either be static for the lifetime of the device (i.e., static permanently or until Service Changed is indicated) or guaranteed to be static only during a connection. This requirement is defined in the table below on a bit-by-bit basis. Although all defined bits in this version of this
specification are required to be static during the lifetime of a device, it is possible that some future bits will be defined as being static only during a connection.
Bit 0 to 17 18-31
Body Composition Feature Bit Various
Reserved for Future Use
Static Requirement Lifetime Not defined.
Table 3.2: Static Requirements for Body Composition Feature Bits
When the Server supports a feature, the associated bit of the Body Composition
Feature characteristic shall be set to 1 (Feature supported), otherwise, the associated bit shall be set to 0 (Feature not supported). The feature bits are defined in [2].
If the Height field of the Body Composition Measurement characteristic is not supported, then the corresponding resolution bits shall be set to 0.
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
Page 9 of 16
3.2 Body Composition Measurement
The Body Composition Measurement characteristic is used to send body composition-related data to the Client. Included in the characteristic value are a Flags field (for showing the presence of optional fields and measurement units), a Body Fat
Percentage field, and depending upon the contents of the Flags field, may include one or more optional fields defined in [2]. 3.2.1 Characteristic Behavior
When the Body Composition Measurement characteristic is configured for indications via the Client Characteristic Configuration descriptor, the following applies:
If a connection to a Client is not established and a new value for the Body
Composition Measurement characteristic becomes available for this Client, the Server shall become connectable to allow the Client to create a link. Once
connected, the Server shall indicate this characteristic and other unsent stored characteristics to the Client.
If a connection to a Client is established and a new value for the Body
Composition Measurement characteristic becomes available for this Client, the Server shall indicate this characteristic to the Client.
For LE, not all the fields of this characteristic can be indicated simultaneously if using a default MTU size. If the required data exceeds the current MTU size, the remaining optional fields shall be sent in the subsequent indication (also known as a ‘continuation packet’) and shall not include the Time Stamp field or the User ID field. Where the measurement is required to be split across two separate packets, the Multiple Packet Measurement bit in the Flags field of both packets shall be set to 1. For BR/EDR, this restriction does not exist due to a larger MTU size.
Once transfer of a measurement is successful, the measurement shall not be
retransmitted. As such, the design of this Service is only suited to sending indications to a single Client for a given user.
The Body Composition Measurement characteristic contains time-sensitive data, thus the requirements for time-sensitive data and data storage defined in Section 3.3 apply.
3.2.1.1 Flags Field
The Flags field shall be included in the Body Composition Measurement characteristic. Reserved for Future Use (RFU) bits in the Flags fields shall be set to 0. The bits of the Flags field, their function, and relationship to bits in the Body Composition Feature characteristic are shown in Table 3.3.
Flags Bit Name
Measurement Units (bit 0)
When Set to 0 SI (Weight and Mass in units of kilogram (kg) and Height in units of
When Set to 1
Corresponding Body Composition Feature
Support bit (see Section 3.1)
Imperial (Weight Mass Measurement
and Mass in units Resolution bits (11-14) and of pound (lb) and Height Measurement Height in units of Resolution bits (15-17)
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
meter )
Time Stamp Present (bit 1), see Section 3.2.1.3
User ID Present (bit 2), see Section 3.2.1.4
Basal Metabolism Present (bit 3), see Section 3.2.1.5 Muscle Percentage Present (bit 4), see Section 3.2.1.6 Muscle Mass Present (bit 5), see Section 3.2.1.7
Fat Free Mass Present (bit 6), see Section 3.2.1.8
Soft Lean Mass Present (bit 7), see Section 3.2.1.9 Body Water Mass Present (bit 8), see Section 3.2.1.10 Impedance Present (bit 9), see Section 3.2.1.11
Weight Present (bit 10), see Section 3.2.1.12
Height Present (bit 11), see Section 3.2.1.13 Multiple Packet
Measurement (bit 12)
Corresponding field not present Corresponding field not present Corresponding field not present Corresponding field not present Corresponding field not present Corresponding field not present Corresponding field not present Corresponding field not present Corresponding field not present Corresponding field not present Corresponding field not present Measurement contained in single packet
inch (in))
Page 10 of 16
Corresponding Time Stamp Supported (bit 0) field present Corresponding Multiple Users Supported (bit field present 1) Corresponding Basal Metabolism Supported field present (bit 2) Corresponding Muscle Percentage Supported field present (bit 3) Corresponding Muscle Mass Supported (bit 4) field present Corresponding Fat Free Mass Supported (bit field present 5) Corresponding Soft Lean Mass Supported (bit field present 6) Corresponding Body Water Mass Supported field present (bit 7) Corresponding Impedance Supported (bit 8) field present Corresponding Weight Supported (bit 9) field present Corresponding Height Supported (bit 10) field present Measurement None split across two consecutive packets
Table 3.3: Bit Definitions for the Body Composition Measurement Characteristic
The term ‘mass’ refers collectively to the following fields: Muscle Mass, Fat Free Mass, Soft Lean Mass, Body Water Mass.
Flags bits in the table above, other than the Time Stamp Present bit and User ID Present bit, may change during a connection if the corresponding support bit in the Body Composition Feature characteristic is set to 1, indicating that the feature is
supported. However, if the corresponding Body Composition Feature support bit is set to 0, then the corresponding Flags bit shall also be set to 0 since the feature is not supported.
The Mass Measurement Resolution bits are only for the purpose of allowing the Client to determine the resolution of the Weight and Mass measurements. All supported
Weight and Mass fields are assumed to have the same resolution. Similarly, the Height Measurement Resolution bits are only for the purpose of allowing the Client to
determine the resolution of the Height measurements. The use of these bits may be required by some Clients that need to know the approximate precision of the data. Note that value of these bits has no impact on the value of 1 bit of the Weight, Mass or Height fields.
3.2.1.2 Body Fat Percentage Field
The Body Fat Percentage field shall be included in the Body Composition Measurement characteristic.
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
Page 11 of 16
See Table 3.3 for details on the relation between the unit of weight, mass and height, and bit 0 of the Flags field.
The special value of 0xFFFF can be used to indicate ‘Measurement Unsuccessful’ to the Client. If this is used, all optional fields other than the Time Stamp field and the User ID field shall be disabled.
3.2.1.3 Time Stamp Field
The Time Stamp field is optional, but shall be included in the Body Composition
Measurement characteristic if the Server supports the Time Stamp feature (see Table 3.3) with the exception that it shall not be included in continuation packets (see Section 3.2.1). The Time Stamp feature shall be supported if the device supports the storing of data.
The Time Stamp field is defined to use the same format as the Date Time characteristic defined in [2]. However, a value of 0 for the year, month or day fields (meaning
unknown) shall not be used for this service. It is left to the implementation to ensure the user sets the correct date and time before the Server is used.
The value of the Time Stamp field is derived from a source of date and time within the device at the time of measurement. If the Time Stamp feature is supported, a source of date and time is mandatory. The date and time of the device may be updated by various means such as via a simple user interface on the device, via the Current Time Service [3] or other method. Regardless of the method of updating the date and time, a method should be provided to allow the Client to verify the accuracy of the time base in the Server. This is a requirement for implementations needing to be compliant with
guidelines set forth by the Continua Health Alliance (and hence those needing data to be transcoded to a format compliant with IEEE 11073-10420 [4]).
3.2.1.4 User ID Field
The User ID field shall be included in the Body Composition Measurement characteristic if the device supports the Multiple Users feature (see Table 3.3) with the exception that it shall not be included in continuation packets (see Section 3.2.1). This field shall not be included if the Multiple Users feature is not supported.
The values used for User ID shall be unique per Server, but are otherwise left to the implementation. For example, if the Server supports two User IDs to distinguish
between two users, the Server may use User ID 1 and 2 or User ID 35 and 97 or other unique combinations.
A special User ID value of 0xFF represents “unknown user”. This can be used for cases where a Body Composition Analyzer can be used for Guests.
3.2.1.5 Basal Metabolism
The Basal Metabolism field may be included in the Body Composition Measurement characteristic if the device supports the Basal Metabolism feature (see Table 3.3).
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service 3.2.1.6 Muscle Percentage
Page 12 of 16
The Muscle Percentage field may be included in the Body Composition Measurement characteristic if the device supports the Muscle Percentage feature (see Table 3.3).
3.2.1.7 Muscle Mass
The Muscle Mass field may be included in the Body Composition Measurement characteristic if the device supports the Muscle Mass feature (see Table 3.3).
See Table 3.3 for details on the relation between the units of weight and height, and bit 0 of the Flags field.
3.2.1.8 Fat Free Mass
The Fat Free Mass field may be included in the Body Composition Measurement characteristic if the device supports the Fat Free Mass feature (see Table 3.3). See Table 3.3 for details on the relation between the units of weight and height, and bit 0 of the Flags field.
3.2.1.9 Soft Lean Mass
The Soft Lean Mass field may be included in the Body Composition Measurement characteristic if the device supports the Soft Lean Mass feature (see Table 3.3). See Table 3.3 for details on the relation between the units of weight and height, and bit 0 of the Flags field.
3.2.1.10 Body Water Mass
The Body Water Mass field may be included in the Body Composition Measurement characteristic if the device supports the Body Water Mass feature (see Table 3.3). See Table 3.3 for details on the relation between the units of weight and height, and bit 0 of the Flags field.
3.2.1.11 Impedance
The Impedance field may be included in the Body Composition Measurement characteristic if the device supports the Impedance feature (see Table 3.3).
3.2.1.12 Weight
The Weight field may be included in the Body Composition Measurement characteristic if the device supports the Weight feature (see Table 3.3).
See Table 3.3 for details on the relation between the units of weight and height, and bit 0 of the Flags field.
3.2.1.13 Height
The Height field may be included in the Body Composition Measurement characteristic if the device supports the Height feature (see Table 3.3).
See Table 3.3 for details on the relation between the units of weight and height, and bit 0 of the Flags field.
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
Page 13 of 16
3.3 Requirements for Time-Sensitive Data
The Body Composition Measurement characteristic contains time-sensitive data (i.e., the Body Composition values) and is considered a time-sensitive characteristic, thus the following requirements apply:
If the Time Stamp feature is not supported:
• The value of a time-sensitive characteristic shall be discarded either if the connection does not get established or if the indication is not successfully
acknowledged by the Client in a timely manner as decided by the implementation (e.g., if the Server cannot send the data within 5 minutes of taking the measurement). If the Time Stamp feature is supported:
• It is recommended that the value of a time-sensitive characteristic be stored if
either the connection does not get established or if the indication is not successfully acknowledged by the Client during the connection.
• For basic scenarios, the Server should be able to store at least 25 data
measurements (i.e., the Body Composition values). Multi-user devices should be able to store that number of measurements per supported user.
• If the maximum storage capacity in the Server is reached, the Server should overwrite the oldest measurement data first when acquiring new measurement data and should inform the user (e.g., via the UI of the device). For multi-user devices, the Server should purge the oldest data for a given user to make room for the most recent data for that user.
• When transmitting stored data, the oldest data shall be sent first followed by the next oldest data (in FIFO order) until all stored data (as controlled by the Client) has been transferred.
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
Page 14 of 16
4 SDP Interoperability
If this service is exposed over BR/EDR then it shall have the following SDP record.
Item
Service Class ID List
Service Class #0 Protocol Descriptor List Protocol #0 Parameter #0 for Protocol #0 Protocol #1 Parameter #0 for Protocol #1 Parameter #1 for Protocol #1
Definition PSM
GATT Start Handle GATT End Handle
Type UUID UUID Uint16 UUID Uint16 Uint16
Value
«Body Composition» L2CAP PSM = ATT ATT
First handle of this service in the GATT database Last handle of this service in the GATT database PublicBrowseRoot*
Status M M M M M M M M M
BrowseGroupList Table 4.1: SDP Record
* PublicBrowseRoot shall be present; however, other browse UUIDs may also be included in the list.
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
Page 15 of 16
5 Acronyms and Abbreviations
Acronyms and Abbreviations AMP BCA BR/EDR GAP GATT LE MTU RFU SDP
Meaning
Alternate MAC/PHY Body Composition Analyzer Basic Rate / Enhanced Data Rate Generic Access Profile Generic Attribute Profile Low Energy
Maximum Transmission Unit Reserved for Future Use Service Discovery Protocol
UUID Universally Unique Identifier Table 5.1: Acronyms and Abbreviations
Bluetooth SIG Proprietary
BLUETOOTH SERVICE SPECIFICATION Body Composition Service
Page 16 of 16
6 References
[1] [2] [3] [4]
Bluetooth Core Specification v4.0 or later version of the Core Specification.
Characteristic and Descriptor descriptions are accessible via the Bluetooth SIG Assigned Numbers. Current Time Service Specification v1.1 or later
IEEE 11073-10420 - 2010 (Health informatics—Personal health device communication - Part 10420: Device specialization— Body Composition Analyzer)
Bluetooth SIG Proprietary
因篇幅问题不能全部显示，请点此查看更多更全内容