ictrun commited on
Commit
9b321b5
·
verified ·
1 Parent(s): 1f71db8

Add wireless vendor identifier metadata dataset

Browse files
README.md ADDED
@@ -0,0 +1,105 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: other
3
+ pretty_name: Wireless Vendor Identifier Metadata
4
+ tags:
5
+ - bluetooth
6
+ - ble
7
+ - wireless
8
+ - oui
9
+ - cybersecurity
10
+ - metadata
11
+ - vendor-identifiers
12
+ - tabular
13
+ size_categories:
14
+ - n<1K
15
+ configs:
16
+ - config_name: default
17
+ data_files:
18
+ - split: train
19
+ path: data/vendor_identifiers.csv
20
+ ---
21
+
22
+ # Wireless Vendor Identifier Metadata
23
+
24
+ This dataset contains public vendor identifier metadata relevant to wireless and
25
+ BLE research. It is designed for defensive analysis, asset classification,
26
+ literature support, and reproducible metadata lookup.
27
+
28
+ It deliberately excludes complete BLE advertisement payloads, packet templates,
29
+ radio timing recipes, device captures, effectiveness labels, and any instructions
30
+ for impersonation or nuisance testing.
31
+
32
+ ## Dataset Contents
33
+
34
+ - `data/vendor_identifiers.csv`: normalized identifier records from public
35
+ registries.
36
+ - `data/vendors.csv`: vendor group labels and ecosystem tags used during
37
+ curation.
38
+ - `data/source_manifest.csv`: source URLs, snapshot hashes, and row counts.
39
+ - `schema/vendor_identifiers.schema.json`: machine-readable column descriptions.
40
+
41
+ Current generated records: `6213`.
42
+
43
+ Snapshot date: `2026-05-25`.
44
+
45
+ ## Intended Use
46
+
47
+ Appropriate uses include:
48
+
49
+ - mapping observed public identifiers to likely vendor families;
50
+ - building defensive BLE inventory or wireless metadata analysis tools;
51
+ - supporting academic writing about BLE discovery, manufacturer identifiers,
52
+ and vendor ecosystems;
53
+ - training or evaluating classifiers on benign public registry metadata.
54
+
55
+ Do not use this dataset to generate, optimize, or test spoofed advertisements
56
+ against devices or people without explicit authorization. Do not combine it with
57
+ payload templates, timing profiles, or captured device identifiers to conduct
58
+ impersonation, spam, harassment, or availability attacks.
59
+
60
+ ## Sources
61
+
62
+ - IEEE Registration Authority OUI CSV:
63
+ `https://standards-oui.ieee.org/oui/oui.csv`
64
+ - Bluetooth SIG Assigned Numbers YAML repository:
65
+ `https://www.bluetooth.com/specifications/assigned-numbers/`
66
+
67
+ The curated dataset is provided for research convenience. Source registry terms
68
+ remain with the respective source authorities; verify current data against the
69
+ official registries before operational use.
70
+
71
+ ## Curation Method
72
+
73
+ Rows are selected from public registries by matching organization names against
74
+ vendor-family keyword rules in `tools/build_hf_dataset.py`. The vendor group is
75
+ therefore a convenience label, not an authoritative corporate ownership graph.
76
+ Some subsidiaries, renamed entities, or regional legal entities may be missing
77
+ or grouped conservatively.
78
+
79
+ ## Data Fields
80
+
81
+ See `schema/vendor_identifiers.schema.json` for column-level details.
82
+
83
+ ## Safety Boundary
84
+
85
+ This dataset is public identifier metadata only. It does not contain:
86
+
87
+ - complete BLE Manufacturer Specific Data values;
88
+ - Apple, Samsung, Android, or other proximity-pairing payloads;
89
+ - randomized device addresses, captured MAC addresses, RPAs, RSSI, timestamps,
90
+ or location data;
91
+ - tested trigger rates, success labels, or spam-tuning parameters.
92
+
93
+ ## Known Limitations
94
+
95
+ - The dataset is a registry snapshot, not a live registry mirror.
96
+ - Vendor grouping is keyword-based and may need refinement for narrow studies.
97
+ - Identifier ownership does not prove that a specific nearby radio device is
98
+ made by that vendor.
99
+ - The presence of a Bluetooth Company Identifier does not imply support for any
100
+ proximity-pairing protocol.
101
+
102
+ ## Citation
103
+
104
+ If you use this dataset, cite the Hugging Face dataset repository and the
105
+ underlying IEEE and Bluetooth SIG registries listed above.
data/source_manifest.csv ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ source_authority,source_url,snapshot_date,source_sha256,curated_records
2
+ IEEE Registration Authority,https://standards-oui.ieee.org/oui/oui.csv,2026-05-25,55527a201177f2ee5824bf84d9c6635dd346135a3c9feb08390ba89d96188a41,6189
3
+ Bluetooth SIG,https://bitbucket.org/bluetooth-SIG/public/raw/main/assigned_numbers/company_identifiers/company_identifiers.yaml,2026-05-25,2b2cce6cced2c8882d6215cbc2f3762f93eb0e621f95825557f28bee3652a083,24
data/vendor_identifiers.csv ADDED
The diff for this file is too large to render. See raw diff
 
data/vendors.csv ADDED
@@ -0,0 +1,14 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ vendor_slug,vendor_display_name,ecosystem_tags,keyword_hints
2
+ apple,Apple,ios|ipados|macos|watchos|tvos|find-my,apple inc|apple computer
3
+ samsung,Samsung,android|galaxy|smartthings|wearos,samsung
4
+ google_android,Google / Android,android|pixel|wearos|nearby-share|fast-pair,google|android
5
+ huawei,Huawei,android|harmonyos|wearables,huawei|honor device
6
+ xiaomi,Xiaomi,android|miui|hyperos|wearables|iot,xiaomi|huami|zepp
7
+ oppo_oneplus_realme,OPPO / OnePlus / realme,android|coloros|oxygenos|realme-ui,oppo|oneplus|realme
8
+ vivo,vivo,android|originos|funtouch-os,vivo
9
+ sony,Sony,android|audio|playstation|consumer-electronics,sony
10
+ lg,LG,android|webos|consumer-electronics,lg electronics|lge
11
+ motorola_lenovo,Motorola / Lenovo,android|wearables|pc,motorola|lenovo
12
+ microsoft,Microsoft,windows|xbox|surface,microsoft
13
+ amazon,Amazon,alexa|fire-tv|ring|iot,amazon|ring llc
14
+ meta,Meta,quest|vr|ar|social,meta platforms|facebook|oculus
schema/vendor_identifiers.schema.json ADDED
@@ -0,0 +1,69 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
3
+ "title": "Wireless Vendor Identifier Metadata",
4
+ "type": "object",
5
+ "properties": {
6
+ "record_id": {
7
+ "type": "string",
8
+ "description": "Stable row identifier."
9
+ },
10
+ "vendor_slug": {
11
+ "type": "string",
12
+ "description": "Curated vendor group key."
13
+ },
14
+ "vendor_display_name": {
15
+ "type": "string",
16
+ "description": "Human-readable vendor group label."
17
+ },
18
+ "ecosystem_tags": {
19
+ "type": "string",
20
+ "description": "Pipe-separated ecosystem tags."
21
+ },
22
+ "identifier_namespace": {
23
+ "type": "string",
24
+ "enum": [
25
+ "ieee_oui_ma_l",
26
+ "bluetooth_sig_company_identifier"
27
+ ]
28
+ },
29
+ "identifier_value": {
30
+ "type": "string",
31
+ "description": "Public identifier value from the source registry."
32
+ },
33
+ "identifier_format": {
34
+ "type": "string"
35
+ },
36
+ "assignment_name": {
37
+ "type": "string",
38
+ "description": "Organization name in the source registry."
39
+ },
40
+ "source_authority": {
41
+ "type": "string"
42
+ },
43
+ "source_url": {
44
+ "type": "string"
45
+ },
46
+ "source_snapshot_date": {
47
+ "type": "string",
48
+ "format": "date"
49
+ },
50
+ "source_sha256": {
51
+ "type": "string"
52
+ },
53
+ "safe_use_category": {
54
+ "type": "string"
55
+ },
56
+ "dual_use_notes": {
57
+ "type": "string"
58
+ }
59
+ },
60
+ "required": [
61
+ "record_id",
62
+ "vendor_slug",
63
+ "identifier_namespace",
64
+ "identifier_value",
65
+ "assignment_name",
66
+ "source_authority",
67
+ "source_url"
68
+ ]
69
+ }