|
|
|
|
@ -657,6 +657,21 @@ The payload for a DMR protocol data message is formatted:
|
|
|
|
|
| BER | RSSI |
|
|
|
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
|
|
|
|
|
|
|
|
|
[discrete]
|
|
|
|
|
==== Control Flags
|
|
|
|
|
[cols="2,1,2"]
|
|
|
|
|
|===
|
|
|
|
|
|Name |Flag |Description
|
|
|
|
|
|
|
|
|
|
|Grant Demand
|
|
|
|
|
|$80 (0x80)
|
|
|
|
|
|This control flag indicates the packet contains a remote grant demand request.
|
|
|
|
|
|
|
|
|
|
|Unit to Unit
|
|
|
|
|
|$01 (0x01)
|
|
|
|
|
|This control flag indicates any included control request is a unit-to-unit request.
|
|
|
|
|
|===
|
|
|
|
|
|
|
|
|
|
=== 3.3 P25 Protocol Data
|
|
|
|
|
For both reception and transmission of P25 protocol data on the network, simple packets are formed using the Protocol function and P25 sub-function.
|
|
|
|
|
|
|
|
|
|
@ -703,6 +718,29 @@ All messages (with the exception of PDUs) carry this message header:
|
|
|
|
|
| |
|
|
|
|
|
+-+-+-+-+-+-+-+-+
|
|
|
|
|
|
|
|
|
|
[discrete]
|
|
|
|
|
==== Control Flags
|
|
|
|
|
[cols="2,1,2"]
|
|
|
|
|
|===
|
|
|
|
|
|Name |Flag |Description
|
|
|
|
|
|
|
|
|
|
|Grant Demand
|
|
|
|
|
|$80 (0x80)
|
|
|
|
|
|This control flag indicates the packet contains a remote grant demand request.
|
|
|
|
|
|
|
|
|
|
|Grant Denial
|
|
|
|
|
|$40 (0x40)
|
|
|
|
|
|This control flag indicates any included grant demand request is to be denied.
|
|
|
|
|
|
|
|
|
|
|Encrypted
|
|
|
|
|
|$08 (0x08)
|
|
|
|
|
|This control flag indicates any included control request is for encrypted traffic to follow.
|
|
|
|
|
|
|
|
|
|
|Unit to Unit
|
|
|
|
|
|$01 (0x01)
|
|
|
|
|
|This control flag indicates any included control request is a unit-to-unit request.
|
|
|
|
|
|===
|
|
|
|
|
|
|
|
|
|
==== 3.3.2 PDU Message Header
|
|
|
|
|
[listing]
|
|
|
|
|
Below is the representation of the data layout for the P25 frame
|
|
|
|
|
|