Fred;
>> Sorry but I'm quite lost with all difference BLE / Classic bluetooth :)
I restated point 4 for Ming and the bluetooth-dev list on 11/20…
The key is the “iOS: Supported Bluetooth profiles”, identified on http://support.apple.com/kb/HT3647.
These Bluetooth profiles are available to all iOS developers, without any requirement for a MFi license. These are “Bluetooth v2.1+EDR” profiles (what Jeff is calling “classic Bluetooth”)… not Bluetooth LE.
Bluetooth devices that implement these “iOS-supported” profiles can communicate with iOS facilities on an iOS device. This allows communications between the Bluetooth device and relevant built-in apps included with the iOS operating system. However, the iOS environment prevents any direct communication between user-developed apps and Bluetooth devices using these “classic Bluetooth” profiles.
With CoreBluetooth, Apple has provided a mechanism for user-developed apps to communicate directly with Bluetooth LE devices, but this is independent of “Bluetooth v2.1+EDR” (“classic Bluetooth”) functionality.
If you want to develop a Bluetooth accessory that requires performance or features that can’t be accomplished with Bluetooth LE, and that must communicate directly with a user-developed iOS app, then the accessory must be developed and manufactured under a MFi license agreement.
“Bluetooth SMART” is the Bluetooth SIG branding for Bluetooth products made possible with the introduction of Bluetooth 4.0 / Bluetooth Low Energy technology. Because Bluetooth SMART is Bluetooth LE, this functionality is available to OS-X and iOS developers through the corebluetooth framework, without any requirement for a MFi license. However, user-developed apps on iOS devices are strictly limited to accessing Bluetooth SMART accessories through the facilities exposed by the iOS corebluetooth framework. Even if you found some way to circumvent this restrictiction, the App Store is unlikely to approve an app that implemented such a work-around.
The “Classic Bluetooth Profiles” listed on the Apple “iOS: Supported Bluetooth profiles” page are part of the separate specification. These profiles are -not- directly from user-developed apps… the “Classic Bluetooth Profiles” supported by any particular iOS device and/or iOS version can only be accessed through the functionality provided by the published iOS frameworks.
Apple developed the iOS “external accessory framework” to allow user-developed apps to communicate directly with “Bluetooth v2.1+EDR” accessory devices. However, to work with the external accessory framework, the accessory device must implement iAP (iPod Accessory Protocol), and the technical details of this protocol are only available to holders of a MFi Developer License. Furthermore, under recent changes in the MFi License structure (see mfi.apple.com/faqs), new MFi accessories can only be submitted for official MFi certification, and subsequently manufactured, by a company that is a “MFi Manufacturing Licensee”.
>> Is iPhone4S or later able to send this kind of "alert notification" when incoming call or incoming SMS?
According to Alexander Traud’s 11/20 post on the bluetooth-dev list, “MAP offers MMS and SMS (no E-Mail access)”… MAP is one of the iOS Supported Bluetooth profiles, so user-developed apps only have access to MAP through published iOS frameworks. Unless the functionality you need is provided in one of the iOS frameworks (other than the external accessory framework), there isn’t be any way to accomplish this in an Apple-approved manner.
Regards,
Mark Davis
From: bluetooth-dev- Frederic Visticot
Sent: Thursday, December 06, 2012 11:04 AM
To: email@hidden
Subject: Re: Bluetooth-dev Digest, Vol 9, Issue 255
4. The Bluetooth Smart "Alert Notification Profile" is a perfect fit for BLE-based notification accessories, but using this requires that you have access to the data in the first place, which we do not.
Is there any Apple documentation regarding Alert Notification Profile ?
Is iPhone4S or later able to send this kind of "alert notification" when incoming call or incoming SMS?
Sorry but I'm quite lost with all difference BLE / Classic bluetooth :)