I've been looking at iOS 7's new P2P networking framework, MultipeerConnectivity, and from the description, it seems to me that it uses a combination of some kind of Wi-Fi Direct technology and Bluetooth PANs.
我一直在关注iOS 7的新P2P网络框架，MultipeerConnectivity，从描述中，我觉得它使用了某种Wi-Fi Direct技术和蓝牙PAN的组合。
Is the Wi-Fi Direct technology in this framework compatible with Android's Wi-Fi Direct? Can this framework actually be used for cross-platform P2P networking?
此框架中的Wi-Fi Direct技术是否与Android的Wi-Fi Direct兼容？这个框架实际上可以用于跨平台的P2P网络吗？
6 个解决方案
#1
10
The device is not found by either when advertising or browsing with MultipeerConnectivity. Tried on Galaxy Tab 2:
在使用MultipeerConnectivity进行广告或浏览时，找不到该设备。试过Galaxy Tab 2：
#2
24
This is what we know:
这就是我们所知道的：
- There's no BTLE/Bluetooth 4.0 advertisement visible on my Texas Instruments Bluetooth Low energy scanner.
- 我的德州仪器蓝牙低功耗扫描仪上没有可见的BTLE /蓝牙4.0广告。
- No WiFi Direct activity seen by JuJoDi.
- JuJoDi没有看到WiFi Direct活动。
- Talkkr app can connect while WiFi is off and the connection takes about 10 seconds.
- Talkkr应用程序可以在WiFi关闭时连接，连接大约需要10秒钟。
My working theory: the MultiPeer uses Bluetooth Classic, based on the above.
我的工作理论：MultiPeer使用蓝牙经典，基于以上。
iOS Bluetooth Classic is known to be under the Apple MFA Accessory API's tight control and lockdown, including the MFA authentication challenge-response. Apple controls the MFA encryption keys (either in software or by the accessory authentication chips). It makes it inaccessible to other platforms.
众所周知，iOS Bluetooth Classic受到Apple MFA Accessory API的严格控制和锁定，包括MFA身份验证质询 - 响应。 Apple控制MFA加密密钥（在软件中或通过附件认证芯片）。它使其他平台无法访问。
#3
2
No, the two are not compatible.
不，两者不兼容。
The MultipeerConnectivity documentation you linked to explicitly states (emphasis mine):
您链接到的MultipeerConnectivity文档明确说明（强调我的）：
The Multipeer Connectivity framework provides support for discovering services provided by nearby iOS devices
Multipeer Connectivity框架为发现附近iOS设备提供的服务提供支持
Although you may be able to hack together a workaround akin to the short-lived iMessage app for Android, I wouldn't recommend it.
虽然您可能会破解类似于Android的短期iMessage应用程序的解决方法，但我不推荐它。
#4
1
Based on my experimentation with iOS 7 AirDrop, it doesn't seem to be using WiFi Direct.
The transfer rates are very low indicating that it may only be legacy Adhoc WiFi (capped at 11 Mbps).
Did you ever read Apple claiming to support Wifi Direct explicitly?
Please read my blog post for details.
根据我对iOS 7 AirDrop的实验，它似乎没有使用WiFi Direct。传输速率非常低，表明它可能只是传统的Adhoc WiFi（上限为11 Mbps）。你有没有读过Apple声称明确支持Wifi Direct？请阅读我的博客文章了解详情。
#5
1
I am very interested in this subject as well and I came across these rather old links
我对这个主题也非常感兴趣，我遇到了这些相当古老的链接
AllJoyn
AllJoyn
AllJoyn® is a collaborative open-source software framework that makes it easy for developers to write applications that can discover nearby devices, and communicate with each other directly regardless of brands, categories, transports, and OSes without the need of the cloud Source: https://allseenalliance.org/developers/learn OpenPeer SDK
AllJoyn®是一个协作的开源软件框架，使开发人员可以轻松编写可以发现附近设备的应用程序，无需品牌，类别，传输和操作系统直接相互通信，无需云端源：https ：//allseenalliance.org/developers/learn OpenPeer SDK
Open Peer is an open P2P signalling protocol Source: http://openpeer.org/open-peer-sdk-for-ios/ I haven't used any of these libraries but I am interested to add them to my simple game for the fun of it.
Open Peer是一个开放的P2P信令协议来源：http：//openpeer.org/open-peer-sdk-for-ios/我没有使用任何这些库，但我有兴趣将它们添加到我的简单游戏中它的乐趣。
source Peer to peer android and iOS with Wifi direct (multipeer connectivity?)
源码同行Android和iOS与Wifi直接（多重连接？）
#6
0
Maybe a bit delayed, but technologies have evolved since so there is certainly new info around.
也许有点延迟，但技术已经发展，所以肯定有新的信息。
As iOS has yet to open up an API for WiFi Direct and Multipeer Connectivity is iOS only, I believe the best way to approach this is to use BLE, which is supported by both platforms (some better than others).
由于iOS还没有打开WiFi Direct和Multipeer Connectivity的API，我认为最好的方法是使用BLE，这两个平台都支持（有些比其他平台更好）。
On iOS a device can act both as a BLE Central and BLE Peripheral at the same time, on Android the situation is more complex as not all devices support the BLE Peripheral state. Also the Android BLE stack is very unstable (to date).
在iOS上，设备可以同时充当BLE中心和BLE外设，在Android上情况更复杂，因为并非所有设备都支持BLE外设状态。此外，Android BLE堆栈非常不稳定（迄今为止）。
If your use case is feature driven, I would suggest to look at Frameworks and Libraries that can achieve this for you, without you needing to build it up from scratch.
如果您的用例是功能驱动的，我建议您查看可以为您实现此功能的框架和库，而无需您从头开始构建它。
For example: p2pkit.io or google nearby
例如：p2pkit.io或google附近
Disclaimer: I work for Uepaa, developing p2pkit.io for Android and iOS.
免责声明：我为Uepaa工作，为Android和iOS开发p2pkit.io。
#1
10
The device is not found by either when advertising or browsing with MultipeerConnectivity. Tried on Galaxy Tab 2:
在使用MultipeerConnectivity进行广告或浏览时，找不到该设备。试过Galaxy Tab 2：
#2
24
This is what we know:
这就是我们所知道的：
- There's no BTLE/Bluetooth 4.0 advertisement visible on my Texas Instruments Bluetooth Low energy scanner.
- 我的德州仪器蓝牙低功耗扫描仪上没有可见的BTLE /蓝牙4.0广告。
- No WiFi Direct activity seen by JuJoDi.
- JuJoDi没有看到WiFi Direct活动。
- Talkkr app can connect while WiFi is off and the connection takes about 10 seconds.
- Talkkr应用程序可以在WiFi关闭时连接，连接大约需要10秒钟。
My working theory: the MultiPeer uses Bluetooth Classic, based on the above.
我的工作理论：MultiPeer使用蓝牙经典，基于以上。
iOS Bluetooth Classic is known to be under the Apple MFA Accessory API's tight control and lockdown, including the MFA authentication challenge-response. Apple controls the MFA encryption keys (either in software or by the accessory authentication chips). It makes it inaccessible to other platforms.
众所周知，iOS Bluetooth Classic受到Apple MFA Accessory API的严格控制和锁定，包括MFA身份验证质询 - 响应。 Apple控制MFA加密密钥（在软件中或通过附件认证芯片）。它使其他平台无法访问。
#3
2
No, the two are not compatible.
不，两者不兼容。
The MultipeerConnectivity documentation you linked to explicitly states (emphasis mine):
您链接到的MultipeerConnectivity文档明确说明（强调我的）：
The Multipeer Connectivity framework provides support for discovering services provided by nearby iOS devices
Multipeer Connectivity框架为发现附近iOS设备提供的服务提供支持
Although you may be able to hack together a workaround akin to the short-lived iMessage app for Android, I wouldn't recommend it.
虽然您可能会破解类似于Android的短期iMessage应用程序的解决方法，但我不推荐它。
#4
1
Based on my experimentation with iOS 7 AirDrop, it doesn't seem to be using WiFi Direct.
The transfer rates are very low indicating that it may only be legacy Adhoc WiFi (capped at 11 Mbps).
Did you ever read Apple claiming to support Wifi Direct explicitly?
Please read my blog post for details.
根据我对iOS 7 AirDrop的实验，它似乎没有使用WiFi Direct。传输速率非常低，表明它可能只是传统的Adhoc WiFi（上限为11 Mbps）。你有没有读过Apple声称明确支持Wifi Direct？请阅读我的博客文章了解详情。
#5
1
I am very interested in this subject as well and I came across these rather old links
我对这个主题也非常感兴趣，我遇到了这些相当古老的链接
AllJoyn
AllJoyn
AllJoyn® is a collaborative open-source software framework that makes it easy for developers to write applications that can discover nearby devices, and communicate with each other directly regardless of brands, categories, transports, and OSes without the need of the cloud Source: https://allseenalliance.org/developers/learn OpenPeer SDK
AllJoyn®是一个协作的开源软件框架，使开发人员可以轻松编写可以发现附近设备的应用程序，无需品牌，类别，传输和操作系统直接相互通信，无需云端源：https ：//allseenalliance.org/developers/learn OpenPeer SDK
Open Peer is an open P2P signalling protocol Source: http://openpeer.org/open-peer-sdk-for-ios/ I haven't used any of these libraries but I am interested to add them to my simple game for the fun of it.
Open Peer是一个开放的P2P信令协议来源：http：//openpeer.org/open-peer-sdk-for-ios/我没有使用任何这些库，但我有兴趣将它们添加到我的简单游戏中它的乐趣。
source Peer to peer android and iOS with Wifi direct (multipeer connectivity?)
源码同行Android和iOS与Wifi直接（多重连接？）
#6
0
Maybe a bit delayed, but technologies have evolved since so there is certainly new info around.
也许有点延迟，但技术已经发展，所以肯定有新的信息。
As iOS has yet to open up an API for WiFi Direct and Multipeer Connectivity is iOS only, I believe the best way to approach this is to use BLE, which is supported by both platforms (some better than others).
由于iOS还没有打开WiFi Direct和Multipeer Connectivity的API，我认为最好的方法是使用BLE，这两个平台都支持（有些比其他平台更好）。
On iOS a device can act both as a BLE Central and BLE Peripheral at the same time, on Android the situation is more complex as not all devices support the BLE Peripheral state. Also the Android BLE stack is very unstable (to date).
在iOS上，设备可以同时充当BLE中心和BLE外设，在Android上情况更复杂，因为并非所有设备都支持BLE外设状态。此外，Android BLE堆栈非常不稳定（迄今为止）。
If your use case is feature driven, I would suggest to look at Frameworks and Libraries that can achieve this for you, without you needing to build it up from scratch.
如果您的用例是功能驱动的，我建议您查看可以为您实现此功能的框架和库，而无需您从头开始构建它。
For example: p2pkit.io or google nearby
例如：p2pkit.io或google附近
Disclaimer: I work for Uepaa, developing p2pkit.io for Android and iOS.
免责声明：我为Uepaa工作，为Android和iOS开发p2pkit.io。