New Tizen Bluetooth Framework

Transcription

1 New Tizen Bluetooth Framework

2 Agenda Tizen Bluetooth Stack Overview Why we need Bluetooth Framework? Current Bluetooth Framework Desgin New Tizen Bluetooth Framework New Tizen Bluetooth Framework PoC 0.1 release

3 Some Concepts OSP/Native Apps WRT(Web Run Time) Apps In House/(System) Apps CAPI Tizen Service

4 Tizen Bluetooth Stack Tizen BT APIs Web Run Time Plugin In House Bluetooth apps Bluetooth-UG Native Apps CAPI Bluetooth-service Bluetoothd Obexd Bluetooth Framework Kernel

5 The Role of Bluetooth Framework in Tizen Provides Simple, Uniform, Stable CAPI interfac e for Apps/UI Integrates BlueZ into Tizen elegantly and Han dles Tizen specific Bluetooth operations Easy to maintain, extend High performance, low memory consumption Easily to port to different verticals/branch/plat form

6 Bluetooth Framework and BlueZ Integrate BlueZ into Tizen elegantly Focus on Tizen specific operation And by no means replacing and modify any logics of BlueZ 5

7 Current Bluetooth Framework Design Bluetooth Share UI Bluetooth UI Gadget Music App. Contact, , Message Framework Bluetooth Share System Popup System popup Bluetooth Core Call App. Bluetooth Service Bluetooth Phonebook/ MAP Agent EFL check logic (Call System popup or Send the event to application) Bluetooth HFP Agent Multimedia Framework ObexD BluetoothD PulseAudio User space Bluetooth Subsystem Bluetooth Driver (UART) INPUT Mouse, Keyboard, AVRCP ALSA Driver Kernel space BlueZ Project UI Gadget Daemon API/Callback DBUS Application Framework System Call/Events IPC

8 Where We Can Improve (2-1) Over complicated, performance issue, maintaining issue Bluetooth-Service daemon should not wrap entire BlueZ and proxy all the BlueZ operations and events. That makes Bluetooth-Service daemon over complicated And difficult to maintain and migrate to latest version of BlueZ Impact performance a lot Apps should access BlueZ directly in most situations Non-UI operations should be merged into Bluetooth-Service To reduce memory consumption and improve performance Easy to maintain Difficult to migrate to new version of BlueZ Difficult to port to other Tizen verticals or branches Verticals/branches may have different apps/ui, vconf, configure

9 Where We Can Improve (2-2) No unified interface for apps/ui Some apps call CAPI; while others access Bluetooth-service daemon Apps/UI are not easy to write and maintain Bluetooth-Service uses Dbus-glib, which has been replaced by GDbus lib Please see Tizen Telephony core code Also see

10 New Tizen Bluetooth Framework Bluetooth Share UI Bluetooth UI Gadget Paring/OPP server UI (System Popup) Call App. Music App. Bluetooth CAPI PBAP/ MAP Agent Manager(Bluetooth Core) OPP Relay HFP Agent SPP Paring Relay Vertical Plugin (Vertical specific operation Call System popup Send the event to application) Bluetooth Service Daemon Multimedia Framework BlueZ Lib Obexd Bluetoothd Bluetooth Framework PulseAudio BlueZ Project UI Gadget Daemon API/Callback DBUS Application Framework System Call/Events Lib/API

11 New Design Philosophy (2-1) Unified CAPI for Apps/UI All Tizen specific non-ui functions are merged in Bluetoothservice daemon Apps/UI access BlueZ directly with help functions CAPI/BlueZ-lib Bluetooth-Service only proxy paring and OPP operations for BlueZ BlueZ-lib facilitates BlueZ services access Hide the DBus operation detail Easily to migrate to new version of BlueZ

12 New Design Philosophy (2-2) Vertical plugin Easy to port to other vertical/platform Bluetooth-Service is modulated Easy to add new feature Module load/unload runtime A2DP(Pulse Audio) uses upstream solution Pulse Audio accesses BlueZ directly and independent from the Bluetooth Framework NAP/Panu Using ConnMan based tethering over bluetooth ConnMan accesses BlueZ dreictly and independnt from Bl uetooth Framwork

13 New Design Saves >50% Memory 6,000 5,000 5,390 5,070 4,000 3,793 3,000 2,775 Bluetooth Framework New Generation 2,000 1,900 2,014 Bluetooth Tizen 2.x 1,000 0 Adapter On(KBytes) OPP Send File(KBytes) Paring(KBytes) New Design Memory Consumption Breakdown Adapter ON Bluetooth-service 1,170k Bluetoothd 730k Sum 1,900k OPP Send File Bluetooth-service 1,499k Bluetoothd 754k Obexd 522k Sum 2,775k OPP Receive File Bluetooth-service 1,582k Bluetoothd 956k Obexd 515k Sum 3,053k Paring Bluetooth-service 1,262k Bluetoothd 752k Sum 2,014k Old Design Memory Consumption Breakdown Adapter ON Bt-service 760k Bt-core 290k Bluetooth-share 1614k Bluetooth-hfp-agent 1129k Bluetoothd 718k Sum 3,793k OPP Send File Bt-service 774k Bt-core 289k Bluetooth-share 1,848k Bluetooth-hfp-agent 1,129k Bluetoothd 884k Obexd-client 466k Sum 5,390k Paring Bt-service 763k Bt-core 289k Bluetooth-share 1,875k Bluetooth-hfp-agent 1,120k Bluetoothd 1023k Sum 5,070k

14 Operation Simplified Bluetooth Framework NG Bluetooth Framework BlueZ UG/UI Other-Service Bluetooth-Service BlueZ UG/UI CAPI/BlueZ-lib DBus Request api() DBus Request DBus Request DBus Request CallBack() DBus Response DBus Response DBus Response signal DBus Response

15 Upgrading BlueZ more easily Upgrading to BlueZ 5.x Bluetooth Framework NG Bluetooth Framework 2 person week Touch 2 files 2 person month ~60 patches

16 New Tizen Bluetooth Framework PoC 0.1 Release We have finished 0.1 PoC release This release includes: Software framework Enhanced CAPI Refined Bluetooth service Daemon Bluez lib basic Bluetooth Profiles Adapter functionality Device functionality Paring Data share(opp client/server) SDP HID New Bluetooth-UG(UI Gadget) New Paring/OPP apps (system popup) Basing on latest upstream BlueZ(5.x)

17 Q/A

18 Backup

19 Bluetooth Service: Manager Module (Bluetooth Core) Bluetooth Service: Manager module replaces Bluetooth Core Manager Main Function: void EnableBluetoothService() Starts bluetooth service daemons like Bluetoothd and Obexd Power on the default adapter. Loads the service objects of bluetooth-servcie. After property InService changes to ture, bluetooth service will be ready for use. Bluetooth Service Daemon only loads manager module on system start up. And all the other daemon including Bluetoothd Obexd will be started through Dbus after apps/ui call EnableBluetoothService(), So Bluetooth subsystem will not impact system boot up time. And almost consume no resource when Bluetooth is not used Bluetooth core system() trigged startup script is abandoned Use built in driver, not to load/unload driver runtime Load/unload driver runtime is dangerous

20 Bluetooth Service Startup Bluetooth-Service UG/UI CAPI Bt_adpater_enable() EnableBluetoothService() Manager Invoke BlueZ Services Request Power On Adapter Adapter On signal Obexd/Bluetoothd Load Function Modules

21 General Operations: Access BlueZ Service Directly Obexd/Bluetoothd UG/UI CAPI/BlueZ-lib api() DBus Request CallBack() DBus Response

22 Paring: PoPup/Paring UI-> Bluetooth Service -> Bluetoothd UG CAPI Bluetooth-Service Bluetoothd bt_device_create_bound() paring.pare() Paring Relay Paring agent Request Paring UI/ Sys Popup CAPI Invoke Paring APP/UI Vertical Plugin Paring.RegisterRelayAgent() Relay Paring agent Operation Paring Relay Paring agent Response

23 OPP Send File: UG->Bluetooth Service->Obexd UG CAPI Bluetooth-Service Obexd Notification bt_opp_client_push_file() opp.send_file() OPP Relay Transfer State Vertical Plugin Notify transfer state

24 Bluetooth Share UI/Cancel Transfer BT-Share-UI CAPI Bluetooth-Service Obexd Transfer State bt_opp_transfer_state_cb() bt_opp_transfer_cancel() opp.canceltransfer () OPP Relay

25 OPP Server: Obexd->Bluetooth Service-> Syspop/OPP UI Obexd Bluetooth-Service Obex agent Request Sending file OPP Relay Vertical Plugin Invoke OPP_Service APP/UI (System Popup) CAPI OPP/syspopup UI OPP Relay Obex agent Response Sending file Opp.RegisterOPPAgent() OPP relay agent operation