|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Specification approved 2008-06-26.
|
|
3.
|
Justification for the specific reference:
|
|
|
MCAP defines a simple protocol for communicating with devices as if they were connected over a locally attached cable. The specification defines the protocol and generic procedures that can be used by compatible profiles to fulfil a wide variety of usage models.
This protocol enables the following capabilities:
• Provisions for a standardized, structured approach for using a Control Channel to connect and coordinate necessary Data Channels, offering a capability for retaining state references between reconnections. This approach provides structured management of a group of related channels between a given pair of devices which support this protocol and a compatible profile.
• Permits multiple simultaneous data channels.
• Connection-oriented [see Section 3]; which is likely to ensure more reliable behavior when a device moves out of range or disconnects (either inadvertently or intentionally), because the device can recognize the condition and make appropriate decisions.
• Facilitates re-establishment of wireless connections that have been disconnected (intentionally or unintentionally) by associating context identifiers with connections, and allowing success or failure of a reconnect operation to be agreed by the two endpoints.
• Defines a standardized Clock Synchronization Protocol that uses the Control Channel and the shared Bluetooth Master Clock to coordinate local clocks.
• Designed to operate specifically with designated Data Exchange Specifications, which define the base data protocol and command set and device data formats for various supported devices. This facilitates genuine interoperability between data Sources and Sinks minimizing the need for proprietary drivers on either side to format and interpret the data. The specific Data Exchange Specifications are defined in profiles that reference MCAP.
• Allows profiles which reference MCAP to make use of elements of new L2CAP features [1] such as Enhanced Retransmission Mode, Streaming Mode and optional FCS for improved reliability and flexibility.
• Inexpensive to implement due to small list of relatively simple control commands and low code-space requirements.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
N/A.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Specification approved 2008-06-26 and many many qualified devices implementing this version of the specification exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Specification approved 2008-06-26 and many many qualified devices implementing this version of the specification exist.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
See item 8 below and specific reference [5]. This specification utilized the modeling of a blood pressure devices medical system based on the domain information model defined within reference [5].
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
References below are normative unless otherwise specified./
[1]/
Bluetooth Core Specification version 2.0 + EDR or later versions of the Bluetooth Core Specification/
[2]/
Bluetooth SIG member web site, Bluetooth Assigned Numbers, http://www.bluetooth.org/
[3]/
IEEE Standards Style Manual, http://standards.ieee.org/guides/style/2000Style.pdf/
[4]/
1003.1-2001/COR 1-2002 IEEE Standard for Information Technology - Portable Operating System Interface (POSIX) (Informative)/
[5]/
Bluetooth Core Specification 2.0 + EDR or 2.1 + EDR with Volume 3, Part A of Core Specification Addendum 1 or later versions of the Bluetooth Core Specification
|
|
9.
|
Qualification of
Bluetooth:
|
|
|
Bluetooth SIG meets the qualifying criteria for normative referencing as per Recommendation ITU-T A.5.
|
|
10.
|
Other (for any supplementary information):
|
|
|
N/A
|
