If you read the final rule on remote ID, the means of compliance is pretty broad it just says:
“(1) The
unmanned aircraft must be capable of broadcasting the message elements in
§ 89.305 using a non-proprietary broadcast specification and using radio frequency spectrum compatible with personal wireless devices in accordance with
47 CFR part 15, where operations may occur without an FCC individual license.”
It doesn’t say you need to make the information to decode the message public just that you aren’t preventing someone from doing that is how I read it.
§ 89.305 Minimum message elements broadcast by standard remote identification unmanned aircraft.
A standard remote identification unmanned aircraft must be capable of broadcasting the following remote identification message elements:
(a) The identity of the unmanned aircraft, consisting of:
(1) A serial number assigned to the unmanned aircraft by the person responsible for the production of the standard remote identification unmanned aircraft; or
(2) A session ID.
(b) An indication of the latitude and longitude of the control station.
(c) An indication of the geometric altitude of the control station.
(d) An indication of the latitude and longitude of the unmanned aircraft.
(e) An indication of the geometric altitude of the unmanned aircraft.
(f) An indication of the velocity of the unmanned aircraft.
(g) A time mark identifying the Coordinated Universal Time (UTC) time of applicability of a position source output.
(h) An indication of the emergency status of the unmanned aircraft.
The session id was more tied to the network remote id but you had to have a connection to the utms to derive it. So a broadcast module is only broadcasting a serial number?
The Mavic pro can have the wifi module turned on in ap mode at the same time the rc mode is running. But getting the elements in (2) broadcasted will be a trick. If it's only necessary for the serial number in (1) that could be done relatively easily.
If all it broadcasts is serial number on a broadcast module, that's basically useless information. Doesn't give any information about the flight itself, and does nothing useful.
But the session id is broadcast on the network module instead of the serial number, so that's all they get directly. But on the utms connection all of the flight information is broadcast all over the internet.
That 'or' at the end of (1) makes it serial number or session ID. The paragraph starts with (a) and continues with (b) under (2). That's kind of strange. Like it still has to broadcast all of the flight information regardless of whether it is serial number or session id.