mirror of
https://github.com/espressif/esp-idf.git
synced 2026-10-18 19:43:17 +03:00
yangfeng
818b887f73
- Add Bluedroid Object Push (OPP 1.2.1) client and server over GOEP. Object Push is implemented; Business Card Pull/Exchange are not supported. - Transport follows GOEP 2.0 backward compatibility: the server listens on RFCOMM (stack-allocated SCN) and OBEX-over-L2CAP; SDP always publishes RFCOMM and adds GoepL2CapPsm when L2CAP is up. The client uses L2CAP if the peer advertises GoepL2CapPsm, otherwise RFCOMM, with no connect fallback. - Also add GOEP server, OPP VFS, unified Classic BT security masks in esp_bt_defs.h, and bt_opp_client / bt_opp_server examples.
21 lines
799 B
ReStructuredText
21 lines
799 B
ReStructuredText
Bluetooth® OPP API
|
|
==================
|
|
|
|
:link_to_translation:`zh_CN:[中文]`
|
|
|
|
Overview
|
|
--------
|
|
|
|
OPP (Object Push Profile) enables pushing objects such as vCards and other files between Bluetooth devices over OBEX. It is commonly used for contact exchange, file sharing, and similar one-way object transfer scenarios. The OPP API provides functionality for both server and client roles.
|
|
|
|
Application Examples
|
|
--------------------
|
|
|
|
- :example:`bluetooth/bluedroid/classic_bt/bt_opp_server` demonstrates how to implement an OPP server that receives objects.
|
|
- :example:`bluetooth/bluedroid/classic_bt/bt_opp_client` demonstrates how to implement an OPP client that discovers the server by device name and sends sample vCards.
|
|
|
|
API Reference
|
|
-------------
|
|
|
|
.. include-build-file:: inc/esp_opp_api.inc
|