Many developers are developing BLE peripheral devices, which often contain the device Information Service (DIS) services that this article is anxious to introduce , It is a very good way for the maker of equipment, software and hardware version control, production information disclosure. It is therefore recommended that you include this Standard service defined by the SIG at the time of development.
On the bluetooth SIG official website, check the Device information Service to display the following information.
Specification Name |
Specification Type |
Assign number |
Specification level |
Deviceinformation |
Org.bluetooth.service.device_information |
0x180a |
Adopted |
Its short UUID is 0x180a, which exposes the device manufacturer's information and does not rely on any other services to exist independently. There can be only one instance on a device. Supported on both classic Bluetooth and LE .
The DIS service contains the following characteristic values
Number |
Characteristic value |
Uuid |
Instance |
Describe |
1 |
Manufacturer Name |
0x2a29 |
Newbit Studio |
The name of the device manufacturer, the name of the device manufacturer familiar to the outside world |
2 |
Model number |
0x2a24 |
Mi_scale |
defined by the device manufacturer, recommended as a model for a product |
3 |
Serial number |
0x2a25 |
aaaa-s032-4321 |
The product number defined by the manufacturer, which assigns a unique number to each product , can be used to define the format of its own product SN , as it is actually applied . |
4 |
Hardware Revision |
0x2a27 |
0.9.0 |
Hardware number of the product, it is recommended to use three digits separated by dots, representing the major version number, the sub-version number, the release number (even distribution, odd debugging) |
5 |
Firmware Revision |
0x2a26 |
BLE-1.4.0 |
The BLE protocol stack is usually provided by the IC manufacturer, and it is recommended that you write the application to build the protocol stack version used |
6 |
Software Revision |
0x2a27 |
0.9.0 |
Application version number, it is recommended to use three digits separated by dots, representing the major version number, the sub-version number, the release number (even distribution, odd debugging) |
7 |
System ID |
0x2a23 |
- |
Contains OUI (oranizationally unique Identifier) and a unique number that is orchestrated by the manufacturer for the product |
8 |
IEEE 11073-20601 Regulatory Certification Data List |
0x2a2a |
- |
The device requires a mixed structure, varying in length. The data here is usually used for regulatory or certification. |
9 |
PnP ID |
0x2a50 |
- |
Contains the number issued by the GB organization to the manufacturer, the product ID defined by the manufacturer , and the product version information defined by the manufacturer |
The above 9 eigenvalues are not all included on the device, but the more comprehensive the better, if limited by the code space, or the company has not joined the international organization, you can give priority to manufacturer Name, Model number, Serial Number, HW Revision, SW Revision, System ID included, OUI in other system IDs can be useless The number of the original IC. such as TI Company's OUI will be desirable 0x000d.
For more details, please read here (English)
The GATT device Information Service