Three regulatory events landed in the same eight-week window:
- May 1, 2026 — China's civil aviation authority activated GB46750-2025, the mandatory dual-channel drone identification standard, backed by the nationwide UOM (Unmanned Aircraft Operation Management) platform.
- July 4, 2026 — Russian state media announced that a domestic consortium (Element + GLONASS JSC) had built the first field-tested "Red Button" identification system, capable of remotely forcing any compliant civil drone to land on regulator command. (Xinhua)
- July 7, 2026 — NATO Secretary General Mark Rutte, at the Ankara Summit Defence Industry Forum, framed the entire Alliance's counter-UAS doctrine around three verbs: "detect, identify, and neutralise drones." (NATO)
At first glance these look like three unrelated news items. They are not. Read together, they are the three coordinates of a single global fracture.
The world is quietly splitting into three architectural paths for how drones will be identified. Every OEM, every counter-UAS integrator, every airport, and every drone-fleet operator is going to spend the next five years choosing which combination of the three they can afford to comply with.
This article maps the three paths side by side — no politics, no ideology, just architecture, standards, and cost.
For the first eight years of the modern civil drone era (roughly 2015-2023), the world moved toward what looked like a shared technical answer: a "digital license plate" broadcast over Wi-Fi or Bluetooth, following an ASTM-anchored protocol, receivable by anyone.
That consensus is now visibly fragmenting.
The reason is not technology. The reason is that drone identification is now a national security question, not just an aviation safety question. Once identification became a matter of state-level airspace sovereignty, three very different design philosophies emerged — each optimizing for different threats, different institutional trust models, and different industrial policies.
For OEMs targeting export markets, this fragmentation is expensive. It multiplies certification workload, splinters your bill of materials, and forces uncomfortable decisions about which markets you can ship into with a single SKU. But for the ones who read the map correctly, it also opens a very specific window: hardware that can span two or all three paths with a single core module is now a real competitive moat.
Reference implementation: Russia's "Red Button" identification platform.
- Joint development by GLONASS JSC and the Element consortium, confirmed by Vedomosti as the first Russian "trusted platform" for civilian UAS identification.
- Built on domestic electronic component base and domestic cryptographic protection, integrated with the state emergency-response system ERA-GLONASS.
- Positioning driven by GLONASS (not GPS) — critical, because it means the tracking chain runs end-to-end on sovereign-controlled positioning infrastructure.
- Works without cellular coverage, using GLONASS satellite backhaul as the primary channel.
- Encrypted command channel — regulators can push a landing command to a specific tail number, and the drone must comply.
- Underlying legal mandate: Russian government decree effective March 1, 2026, requiring all civil UAS operating in Russian airspace to carry hardware that is either "identifiable, or capable of being intercepted by air-defence units."
Separately,
Ruselectronics / NPP Pulsar has fielded a miniature "friend-or-foe" transponder for military UAS, integrated with the Russian
"Password" IFF radar identification system. Working range up to 5 km altitude and 100 km slant; unit weight around 150 g. This is the military twin of the civil "Red Button" architecture — same design philosophy, different threat model.
Sovereign & closed loop treats drone identification as a state-controlled channel. The identification stack runs on domestic silicon, domestic GNSS, domestic cryptography, and a state-operated backhaul. The command channel is bidirectional: regulators can force compliant aircraft to land. Anyone outside the trusted domestic ecosystem cannot decode, cannot spoof, and cannot easily manufacture compatible hardware.
- Domestic-only components — cannot be supplied from non-aligned foreign silicon
- Sovereign GNSS backbone — GLONASS in Russia's case; other nations would substitute BeiDou, IRNSS, etc.
- State-issued cryptographic keys
- Bidirectional command capability (forced landing, geofence push)
- Not internationally interoperable by design
Path A is optimal against threats where the primary risk is external interference in the domestic drone ecosystem. It is very poorly suited to cross-border commercial drone traffic.
Reference implementation: The FAA + EASA + IETF DRIP standards stack.
Path B is the technology architecture that dominates in North America, the European Union, the United Kingdom, Australia, Japan, and most of Latin America. Its design philosophy is inverted from Path A: identification is a publicly readable public safety utility, not a state-controlled channel.
Every drone broadcasts its identity in the open, on standard consumer radio bands (Wi-Fi and Bluetooth). Anyone with a compatible receiver — police officer, airport security team, curious neighbour with a smartphone — can decode the broadcast. The trust anchor is the cryptographic serial number, not the state's control over the transmission path.
- ASTM F3411 — the anchor standard, defining 6 basic message types and the once-per-second broadcast frequency. Called out by name in FAA 14 CFR §89.315.
- ASD-STAN EN 4709-002 — the European equivalent, technically aligned with ASTM F3411 but with its own conformity assessment path. Anchors EASA's Direct Remote Identification (DRI) requirement under Regulation (EU) 2019/947.
- IETF DRIP working group — a series of RFCs including RFC 9153, RFC 9374, and RFC 9575, specifying cryptographically trustable drone identifiers on top of the ASTM broadcast layer. The stated goal is trustworthy, tamper-evident identification that works over constrained mobile wireless links.
- ICAO coordination — ICAO has been designated to maintain codepoints for Specific Session ID Types and Specific Authentication Methods under the ASTM F3411 framework. ICAO's target is to complete first-phase SARPs (Standards and Recommended Practices) for international drone operations by 2026.
Open standard treats drone identification as a cooperative civil aviation function. Anyone can read the broadcast. The cryptography protects the identifier itself against forgery, but not the transmission path against inspection. Compliance is achieved through mandatory hardware standards, third-party conformity certification, and open publication of the specification — the exact opposite architectural model to Path A.
- Global commodity component supply — any conformity-certified silicon works
- Standard commercial GNSS — GPS, plus Galileo, GLONASS, BeiDou multi-band as available
- Public cryptographic protocol — signed serial numbers, not encrypted channels
- Unidirectional broadcast — regulators cannot force landing; enforcement is via post-flight legal action based on captured identification
- Internationally interoperable by design
Path B is optimal for cross-border commercial airspace, multi-vendor integration, and law-enforcement scenarios where "who is that drone?" needs to be answered by anyone within 500 m to 1 km.
Reference implementation: China's GB46750-2025 + UOM platform.
Between the two extremes sits a third architecture — one that takes technical elements from Path B, but layers them under sovereign network control. This is the model China put into force on May 1, 2026.
- Dual identification — every compliant drone must broadcast (like ASTM F3411) and upload directly to the state UOM platform.
- Reporting frequency — at least once per second, sending identity, position, altitude, velocity, and status.
- The transmission cannot be turned off. By regulatory design, there is no user-facing "off switch" for identification.
- Tamper detection is mechanical. If the identification module is physically removed, (i) the drone body must retain visible evidence of the removal, (ii) the module must self-invalidate immediately, and (iii) the unbinding event must be reported to UOM in real time.
- Real-name registration + activation. Drones without completed real-name registration have their motors locked and cannot take off. This was mandated separately under GB46761-2025, effective the same day.
- Firmware retrofit obligation. Manufacturers must publish retrofit paths for pre-2026 inventory; where firmware retrofit is not feasible, a physical add-on module must be provided (the "small module" or xiaofang class).
- Public Security enforcement integration. Under the revised Public Security Administration Punishment Law (effective January 1, 2026), non-compliant flights are classified as endangering public safety, with detention and fines.
Hybrid sovereign-open borrows the broadcast layer from Path B (so any local receiver can read a drone's identity) and pairs it with a mandatory always-on network layer that flows directly to a state platform. The state does not encrypt the broadcast — but the state does mandate the network channel, prohibits its disablement, and integrates enforcement into criminal law. In effect: openness at the local level, sovereignty at the aggregation level.
- Broadcast layer is technically compatible with ASTM F3411 design principles
- Mandatory network upload to a state platform (UOM)
- No off-switch by design
- Real-name registration coupled to motor activation (physical enforcement, not just regulatory)
- Domestic silicon preference but not exclusion
- BeiDou-primary GNSS, GPS-compatible
Path C is optimal for a large domestic drone market where the state wants both industrial-scale openness (to enable commercial drone services and manufacturing exports) and airspace-level accountability (to ensure enforceable oversight over millions of aircraft).
| Dimension |
Path A — Sovereign & Closed |
Path B — Open Standard |
Path C — Hybrid |
| Reference regulation |
RF gov decree, Mar 1, 2026 |
FAA §89 + EASA 2019/947 |
GB46750-2025, May 1, 2026 |
| Reference platform |
ERA-GLONASS / "Red Button" |
FAA registry / EASA U-space |
UOM |
| Broadcast channel |
Encrypted, domestic protocol |
ASTM F3411 (Wi-Fi/BT) |
ASTM-aligned broadcast + state network upload |
| GNSS backbone |
Sovereign (GLONASS) |
Commercial multi-GNSS (GPS + Galileo + …) |
BeiDou primary, GPS compatible |
| Cryptography |
State-issued keys |
Public standards (RFC 9374 / 9575) |
State-managed at network layer |
| Command channel |
Bidirectional — remote forced landing |
Unidirectional — broadcast only |
Unidirectional broadcast + mandatory network reporting |
| Off-switch permitted? |
N/A (state controls transmission) |
Effectively no — RID must be operational takeoff-to-shutdown |
Explicitly prohibited by regulation |
| Motor lock on non-compliance |
No |
No |
Yes — GB46761-2025 |
| International interoperability |
None by design |
Full — global commodity supply |
Partial — broadcast is readable, network is walled |
| Certification burden per OEM |
Very high — domestic-only sourcing |
Moderate — one DoC per market |
High — dual-channel + retrofit + real-name integration |
| Best fit |
Sovereign airspace control |
Commercial cross-border operations |
Large domestic markets with strong enforcement |
ICAO is the natural candidate to harmonize the three paths. But at the current state of play, ICAO is a coordination body, not a binding one.
ICAO's expected 2026 milestone is completion of first-phase SARPs (Standards and Recommended Practices) enabling members to authorize international drone operations. Under the
ASTM F3411 framework itself, ICAO is designated to maintain codepoints for Specific Session ID Types and Specific Authentication Methods.
But — and this is the critical point — SARPs are recommendations, not treaties. Member States retain full sovereign discretion over how they implement identification in their own airspace. A
2026 ICAO working paper frankly acknowledges that "no fully harmonized global drone traffic management (UTM) system exists" and that "enforcement capabilities differ significantly" across member states.
Translation: the three paths are going to coexist for the foreseeable future. ICAO helps with the seams between Path B countries. It does not — and cannot — bridge to Path A or fully absorb Path C. OEMs planning export strategy should not assume a global harmonization event will bail them out of dual- or triple-certification cost.
If you are building or specifying a drone identification module in 2026, the honest procurement position is:
1. Assume the three paths are permanent.
Design your bill of materials so that the GNSS chipset supports multi-constellation (GPS + Galileo + GLONASS + BeiDou), the cryptographic identity layer can carry either public-standard signed identifiers (Path B) or state-issued credentials (Path A/C), and the network stack can be either off (Path B), always-on to a state endpoint (Path C), or state-controlled backhaul (Path A).
2. Cost your certification workload realistically.
FAA + EASA dual conformity is one certification project. Adding GB46750-2025 conformity is a second, non-trivial project — different test labs, different filing language, different real-name integration hooks. Adding a Path A market is an entirely different discussion involving domestic partnership, silicon sourcing, and cryptographic key management under a foreign sovereign framework.
3. The commercial sweet spot right now is dual-certified for Path B and Path C.
A module that is FAA + EASA + GB46750-2025 compliant addresses roughly 80 %+ of the addressable global civil drone market by unit volume. It is technically feasible with a single core silicon platform and firmware fork. This is where the export-oriented Chinese and European OEMs are converging in 2026.
4. Do not build for one path only unless your business is locked to that market.
Regulatory posture can shift under an OEM's feet in a single legislative session. A drone-fleet operator that specs single-path hardware in 2026 will face a fleet refresh problem when a downstream customer country updates its rules — and every counter-UAS integrator will inherit the same refresh cost on the receiver side.
5. Retrofit is not a nice-to-have. It's a market entry requirement.
GB46750-2025 explicitly requires manufacturers to publish retrofit paths for pre-2026 inventory. EASA and FAA both accommodate broadcast-module retrofits for legacy drones. Path A's Russian counterpart, per the March 2026 decree, requires compliance across the existing installed base. A retrofit-friendly external module — sub-100 g, low power, tamper-evident — is now a standard checklist item for procurement, not an optional line.
The 2026 Remote ID story was never "one global standard vs one hold-out." It is three coherent architectures, each rational within its own security model, none of them going away.
The next twelve months will decide which OEMs made the right silicon and firmware bets in 2025-2026 to serve two or three of those paths from a single hardware core. The ones that got it right will scale with the counter-UAS market YIBO documented in
our companion analysis of the NATO $40 billion Drone Edge investment. The ones that bet on a single path may find themselves rebuilding their platform when the next major market moves.
Detection tells you a drone is there. Identification tells you what to do about it. And in 2026, which identification protocol you're speaking to determines whether "what to do about it" is a phone call to the operator, a network command from a state platform, or a forced-landing signal from a sovereign satellite constellation.
YIBO is a Chinese specialized-and-refined enterprise (专精特新) focused on lightweight Remote ID and drone detection technology. Our product line is deliberately architected to serve two of the three paths from a single silicon core:
- Xiaofang RID Module — dual-certified under FAA (ASTM F3411) and EASA (EN 4709-002 / DRI) , and design-aligned with China's GB46750-2025 dual-channel identification requirements. One core silicon platform, three regulatory markets addressed with firmware forks.
- 58 g Shoulder-Lamp Detector — the wearable single-operator identification receiver built for the front-line law-enforcement and event-security operator role. 1 km detection radius, Bluetooth-linked app, all-day battery.
- Waist-Mounted Portable Detector — extended-range single-operator unit for anti-terror and mass-event operations.
- Airborne Detection Module — cooperative-drone sensor payload extending the identification layer aloft.
- Ground Station System — fixed-site fusion platform aggregating YIBO product lines and third-party sensors into a single operational picture.
For OEMs, integrators, and airspace authorities planning a two-path or three-path identification deployment in 2026-2027, we would like to discuss architecture and specifications. Reach out via [our official channels] for a technical briefing.
- Civil Aviation Administration of China, Announcement 2026-5, "Network Operational Identification for Civil UAS" (March 2026). http://www.caac.gov.cn/XXGK/XXGK/TZTG/202603/P020260306730349409250.pdf
- Xinhua, "Russia's new identification system can force civilian drones to land" (July 5, 2026). http://www.xinhuanet.com/world/20260705/920688d371234731b3f467aba0cb1d7e/c.html
- Vedomosti, "In Russia, they have created their own platform for the identification of unmanned aerial vehicles" (May 13, 2026). https://www.vedomosti.ru/business/articles/2026/05/13/1196833-v-rossii-sozdali-sobstvennuyu-platformu-identifikatsii-bespilotnikov
- UAS Vision, "Russia Creates Miniature 'Friend or Foe' System to Identify Drones" (December 2023). https://www.uasvision.com/2023/12/04/russia-creates-miniature-friend-or-foe-system-to-identify-drones/
- FAA, "Remote Identification of Unmanned Aircraft — Final Rule." https://www.faa.gov/sites/faa.gov/files/2021-08/RemoteID_Final_Rule.pdf
- eCFR, "14 CFR Part 89 — Remote Identification of Unmanned Aircraft." https://www.ecfr.gov/current/title-14/chapter-I/subchapter-F/part-89
- AirHub Knowledge Series, "Remote ID in 2026 — EASA vs UK." https://www.airhub.app/de/resources/news/remote-id-easa-vs-uk-2026
- IETF DRIP working group, draft-wiethuechter-drip-det-moc-02 (July 2025). https://www.ietf.org/archive/id/draft-wiethuechter-drip-det-moc-02.txt
- NATO, Remarks by NATO Secretary General Mark Rutte on NATO Drone Edge (July 7, 2026). https://www.nato.int/en/news-and-events/events/transcripts/2026/07/07/remarks-by-nato-secretary-general-mark-rutte-on-nato-drone-edge-at-the-nato-summit-defence-industry-forum
- Shootin China, "2026 China Drone Regulations — Complete Guide" (2026). https://www.shootinchina.com/shanghai-china/2026-china-drone-regulations/
- TechPhant, "Is Drone RID a Global Standard?" (January 2026). https://www.techphant.cn/blog/106913.html
- Nelly-Sachs, "ICAO Research Report: Addressing the Rise of Unregulated Private and Commercial Drone Activity" (February 2026). https://www.nellysachs.de/wp-content/uploads/2026/02/ICAO_Day2-Addressing-the-Rise-of-Unregulated-Private-.Airspace-Safety.pdf
