blocks|key|2586929|text|你问的问题太笼统了。也许你需要通过这个链接来理解Android+BLE流程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2586930|See+this+tutorial+on+BLE|offset|length|2586931|GATT数据库实现一个或多个profiles(Heart+Rate,+Audio+etc)，每个profile由一个或多个services组成，每个服务由一个或多个characteristics组成。|style|CODE|2586932|为了让您大致了解一下，characteristics是属性，您可以在其中定义要用于读取或写入的属性。|2586933|descriptors是在其上写入数据以启用/发送数据的对象。|2586934|UUID你用来发送和接收数据的东西在客户端和服务器上应该是一样的。|2586935|entityMap|0|LINK|mutability|MUTABLE|url|https://medium.com/@avigezerit/bluetooth-low-energy-on-android-22bc7310387a^0|0|0|O|0|0|0|4|E|V|1P|8|2A|F|0|B|F|0|0|B|0|0|4|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|F|3|G|5|6|7|12|8|@$D|13|E|14|H|I]|$D|15|E|16|H|I]|$D|17|E|18|H|I]|$D|19|E|1A|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1B|8|@$D|1C|E|1D|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1E|8|@$D|1F|E|1G|H|I]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1H|8|@$D|1I|E|1J|H|I]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]]]

You have asked too generic question. May be you need to understand the Android BLE flow from this link.

<a href="https://medium.com/@avigezerit/bluetooth-low-energy-on-android-22bc7310387a" rel="nofollow noreferrer">See this tutorial on BLE</a>

A <code>GATT</code> database implements one or more <code>profiles(Heart Rate, Audio etc)</code>, and each profile is made up of one or more <code>services</code>, and each service is made up of one or more <code>characteristics</code>.

Just to give you glimpse, <code>characteristics</code> are the properties, where you define which one you want to use for read or write.

<code>descriptors</code> are the object on which you write the data to enable/send data.

<code>UUID</code> what you use to send and receive data should be same across client and Server.

blocks|key|2587016|text|尝试解析扫描记录，您可能会在那里找到一些信息|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2587017|Kotlin代码|2587018|++++enum+class+EBLE+{

++++EBLE_ZERO,+//+Zero+element
++++EBLE_FLAGS,+//«Flags»+++Bluetooth+Core+Specification:
++++EBLE_16BitUUIDInc,+//«Incomplete+List+of+16-bit+Service+Class+UUIDs»++++Bluetooth+Core+Specification:
++++EBLE_16BitUUIDCom,+//«Complete+List+of+16-bit+Service+Class+UUIDs»++Bluetooth+Core+Specification:
++++EBLE_32BitUUIDInc,//«Incomplete+List+of+32-bit+Service+Class+UUIDs»+Bluetooth+Core+Specification:
++++EBLE_32BitUUIDCom,//«Complete+List+of+32-bit+Service+Class+UUIDs»+++Bluetooth+Core+Specification:
++++EBLE_128BitUUIDInc,//«Incomplete+List+of+128-bit+Service+Class+UUIDs»+++Bluetooth+Core+Specification:
++++EBLE_128BitUUIDCom,//«Complete+List+of+128-bit+Service+Class+UUIDs»+Bluetooth+Core+Specification:
++++EBLE_SHORTNAME,//«Shortened+Local+Name»+Bluetooth+Core+Specification:
++++EBLE_LOCALNAME,//«Complete+Local+Name»++Bluetooth+Core+Specification:
++++EBLE_TXPOWERLEVEL,//«Tx+Power+Level»++++Bluetooth+Core+Specification:
++++EBLE_DEVICECLASS,//«Class+of+Device»++++Bluetooth+Core+Specification:
++++EBLE_SIMPLEPAIRHASH,//«Simple+Pairing+Hash+C»+++Bluetooth+Core+Specification:​«Simple+Pairing+Hash+C-192»+++​Core+Specification+Supplement,+Part+A,+section+1.6
++++EBLE_SIMPLEPAIRRAND,//«Simple+Pairing+Randomizer+R»+Bluetooth+Core+Specification:​«Simple+Pairing+Randomizer+R-192»+​Core+Specification+Supplement,+Part+A,+section+1.6
++++EBLE_DEVICEID,//«Device+ID»+Device+ID+Profile+v1.3+or+later,«Security+Manager+TK+Value»+Bluetooth+Core+Specification:
++++EBLE_SECURITYMANAGER,//«Security+Manager+Out+of+Band+Flags»+Bluetooth+Core+Specification:
++++EBLE_SLAVEINTERVALRA,//«Slave+Connection+Interval+Range»++++Bluetooth+Core+Specification:
++++EBLE_16BitSSUUID,//«List+of+16-bit+Service+Solicitation+UUIDs»++Bluetooth+Core+Specification:
++++EBLE_128BitSSUUID,+//«List+of+128-bit+Service+Solicitation+UUIDs»+++Bluetooth+Core+Specification:
++++EBLE_SERVICEDATA,//«Service+Data»+++Bluetooth+Core+Specification:​«Service+Data+-+16-bit+UUID»++​Core+Specification+Supplement,+Part+A,+section+1.11
++++EBLE_PTADDRESS,//«Public+Target+Address»++++Bluetooth+Core+Specification:
++++EBLE_RTADDRESS,//«Random+Target+Address»++++Bluetooth+Core+Specification:
++++EBLE_APPEARANCE,//«Appearance»++Bluetooth+Core+Specification:
++++EBLE_DEVADDRESS,//«​LE+Bluetooth+Device+Address»++++​Core+Specification+Supplement,+Part+A,+section+1.16
++++EBLE_LEROLE,//«​LE+Role»++++​Core+Specification+Supplement,+Part+A,+section+1.17
++++EBLE_PAIRINGHASH,//«​Simple+Pairing+Hash+C-256»+​Core+Specification+Supplement,+Part+A,+section+1.6
++++EBLE_PAIRINGRAND,//«​Simple+Pairing+Randomizer+R-256»+++​Core+Specification+Supplement,+Part+A,+section+1.6
++++EBLE_32BitSSUUID,//​«List+of+32-bit+Service+Solicitation+UUIDs»+​Core+Specification+Supplement,+Part+A,+section+1.10
++++EBLE_32BitSERDATA,//​«Service+Data+-+32-bit+UUID»+++​Core+Specification+Supplement,+Part+A,+section+1.11
++++EBLE_128BitSERDATA,//​«Service+Data+-+128-bit+UUID»+​Core+Specification+Supplement,+Part+A,+section+1.11
++++EBLE_SECCONCONF,//​«​LE+Secure+Connections+Confirmation+Value»++​Core+Specification+Supplement+Part+A,+Section+1.6
++++EBLE_SECCONRAND,//​​«​LE+Secure+Connections+Random+Value»+++​Core+Specification+Supplement+Part+A,+Section+1.6​
++++EBLE_3DINFDATA,+//​​«3D+Information+Data»+++​3D+Synchronization+Profile,+v1.0+or+later
++++EBLE_MANDATA;+//«Manufacturer+Specific+Data»++++Bluetooth+Core+Specification:

++++companion+object+{
++++++++private+val+map+=+EBLE.values()
++++++++fun+fromInt(type:+Int)+=+if+(type+>+0)+map[type]+else+EBLE_MANDATA

++++++++fun+getDistance(rssi:+Int,+txPower:+Int)+=+{
++++++++++++/*
+++++++++++++*+RSSI+=+TxPower+-+10+*+n+*+lg(d)
+++++++++++++*+n+=+2+(in+free+space)
+++++++++++++*
+++++++++++++*+d+=+10+%5E+((TxPower+-+RSSI)+/+(10+*+n))
++++++++++++*/

+++++++++++++Math.pow(10.0,+(txPower.toDouble()+-+rssi)+/+(10+*+2))
++++++++}
++++++++/*
+++++BLE+Scan+record+parsing
++++*/
++++fun+ParseRecord(scanRecord:+ByteArray):+Map<EBLE,+ByteArray>+{
++++++++val+ret+=+HashMap<EBLE,+ByteArray>()
++++++++var+index+=+0
++++++++while+(index+<+scanRecord.size)+{
++++++++++++val+length+=+scanRecord[index%2B%2B].toInt()
++++++++++++//Zero+value+indicates+that+we+are+done+with+the+record+now
++++++++++++if+(length+==+0)+break

++++++++++++val+type+=+scanRecord[index].toInt()
++++++++++++//if+the+type+is+zero,+then+we+are+pass+the+significant+section+of+the+data,
++++++++++++//+and+we+are+thud+done
++++++++++++if+(type+==+0)+break

++++++++++++Arrays.copyOfRange(scanRecord,+index+%2B+1,+index+%2B+length)?.let+{
++++++++++++++++ret[EBLE.fromInt(type)]+=+it+//HexUtil.formatHexString(it)
++++++++++++}

++++++++++++index+%2B=+length
++++++++}

++++++++return+ret
++++}
++++}
}|code-block|syntax|javascript|2587019|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Try to parse Scan Record, you may find some information there

Kotlin Code

<pre><code> enum class EBLE {

 EBLE_ZERO, // Zero element
 EBLE_FLAGS, //«Flags» Bluetooth Core Specification:
 EBLE_16BitUUIDInc, //«Incomplete List of 16-bit Service Class UUIDs» Bluetooth Core Specification:
 EBLE_16BitUUIDCom, //«Complete List of 16-bit Service Class UUIDs» Bluetooth Core Specification:
 EBLE_32BitUUIDInc,//«Incomplete List of 32-bit Service Class UUIDs» Bluetooth Core Specification:
 EBLE_32BitUUIDCom,//«Complete List of 32-bit Service Class UUIDs» Bluetooth Core Specification:
 EBLE_128BitUUIDInc,//«Incomplete List of 128-bit Service Class UUIDs» Bluetooth Core Specification:
 EBLE_128BitUUIDCom,//«Complete List of 128-bit Service Class UUIDs» Bluetooth Core Specification:
 EBLE_SHORTNAME,//«Shortened Local Name» Bluetooth Core Specification:
 EBLE_LOCALNAME,//«Complete Local Name» Bluetooth Core Specification:
 EBLE_TXPOWERLEVEL,//«Tx Power Level» Bluetooth Core Specification:
 EBLE_DEVICECLASS,//«Class of Device» Bluetooth Core Specification:
 EBLE_SIMPLEPAIRHASH,//«Simple Pairing Hash C» Bluetooth Core Specification:​«Simple Pairing Hash C-192» ​Core Specification Supplement, Part A, section 1.6
 EBLE_SIMPLEPAIRRAND,//«Simple Pairing Randomizer R» Bluetooth Core Specification:​«Simple Pairing Randomizer R-192» ​Core Specification Supplement, Part A, section 1.6
 EBLE_DEVICEID,//«Device ID» Device ID Profile v1.3 or later,«Security Manager TK Value» Bluetooth Core Specification:
 EBLE_SECURITYMANAGER,//«Security Manager Out of Band Flags» Bluetooth Core Specification:
 EBLE_SLAVEINTERVALRA,//«Slave Connection Interval Range» Bluetooth Core Specification:
 EBLE_16BitSSUUID,//«List of 16-bit Service Solicitation UUIDs» Bluetooth Core Specification:
 EBLE_128BitSSUUID, //«List of 128-bit Service Solicitation UUIDs» Bluetooth Core Specification:
 EBLE_SERVICEDATA,//«Service Data» Bluetooth Core Specification:​«Service Data - 16-bit UUID» ​Core Specification Supplement, Part A, section 1.11
 EBLE_PTADDRESS,//«Public Target Address» Bluetooth Core Specification:
 EBLE_RTADDRESS,//«Random Target Address» Bluetooth Core Specification:
 EBLE_APPEARANCE,//«Appearance» Bluetooth Core Specification:
 EBLE_DEVADDRESS,//«​LE Bluetooth Device Address» ​Core Specification Supplement, Part A, section 1.16
 EBLE_LEROLE,//«​LE Role» ​Core Specification Supplement, Part A, section 1.17
 EBLE_PAIRINGHASH,//«​Simple Pairing Hash C-256» ​Core Specification Supplement, Part A, section 1.6
 EBLE_PAIRINGRAND,//«​Simple Pairing Randomizer R-256» ​Core Specification Supplement, Part A, section 1.6
 EBLE_32BitSSUUID,//​«List of 32-bit Service Solicitation UUIDs» ​Core Specification Supplement, Part A, section 1.10
 EBLE_32BitSERDATA,//​«Service Data - 32-bit UUID» ​Core Specification Supplement, Part A, section 1.11
 EBLE_128BitSERDATA,//​«Service Data - 128-bit UUID» ​Core Specification Supplement, Part A, section 1.11
 EBLE_SECCONCONF,//​«​LE Secure Connections Confirmation Value» ​Core Specification Supplement Part A, Section 1.6
 EBLE_SECCONRAND,//​​«​LE Secure Connections Random Value» ​Core Specification Supplement Part A, Section 1.6​
 EBLE_3DINFDATA, //​​«3D Information Data» ​3D Synchronization Profile, v1.0 or later
 EBLE_MANDATA; //«Manufacturer Specific Data» Bluetooth Core Specification:

 companion object {
 private val map = EBLE.values()
 fun fromInt(type: Int) = if (type &gt; 0) map[type] else EBLE_MANDATA

 fun getDistance(rssi: Int, txPower: Int) = {
 /*
 * RSSI = TxPower - 10 * n * lg(d)
 * n = 2 (in free space)
 *
 * d = 10 ^ ((TxPower - RSSI) / (10 * n))
 */

 Math.pow(10.0, (txPower.toDouble() - rssi) / (10 * 2))
 }
 /*
 BLE Scan record parsing
 */
 fun ParseRecord(scanRecord: ByteArray): Map&lt;EBLE, ByteArray&gt; {
 val ret = HashMap&lt;EBLE, ByteArray&gt;()
 var index = 0
 while (index &lt; scanRecord.size) {
 val length = scanRecord[index++].toInt()
 //Zero value indicates that we are done with the record now
 if (length == 0) break

 val type = scanRecord[index].toInt()
 //if the type is zero, then we are pass the significant section of the data,
 // and we are thud done
 if (type == 0) break

 Arrays.copyOfRange(scanRecord, index + 1, index + length)?.let {
 ret[EBLE.fromInt(type)] = it //HexUtil.formatHexString(it)
 }

 index += length
 }

 return ret
 }
 }
}
</code></pre>

I am not able to get the values(Systolic, Diastolic and Pulse from a Blood Pressure Measurement machine) after getting all the characteristics of Blood Pressure Service (uuid: 00002a35-0000-1000-8000-00805f9b34fb) and also I am not getting the point about all these characteristics and descriptors. So please, anyone, help me with this issue in BLE device.

How to get actual values from BLE device in android?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在获得血压服务的所有特征(uuid: 00002a35-0000-1000-8000-00805f9b34fb)之后，我无法从血压仪获得这些值(收缩压、舒张压和脉搏)，而且我也不了解所有这些特征和描述符的要点。所以，请大家帮助我解决BLE设备中的这个问题。

问如何在android中从BLE设备中获取实际值？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在android中从BLE设备中获取实际值？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在android中从BLE设备中获取实际值？
EN