User's Manual

U
M10936
P
N7150 User Manual
UM
10936 All information provided in this document is subject to legal disclaimers.
U
ser manual
CO
MPANY PUBLIC
Rev. 2.0 — 6 November 2020
348120
16 of 127
2.
3.2 Control Packets
T
he Control Packet structure is detailed below.
Fig 12. Control Packet Format
E
ach Control Packet SHALL have a 3 octet Packet Header and MAY have additional
payload for carrying a Control Message or a segment of Control Message.
NOTE In the case of an ‘empty’ Control Message, only the Packet Header is sent.
 Message Type (MT)
Refer to section 2.3.1 for details of the MT field.
 Packet Boundary Flag (PBF)
Refer to section 2.3.1 for details of the PBF field.
 Group Identifier (GID)
The NCI supports Commands, Responses and Notifications which are categorized
according their individual groups. The Group Identifier (GID) indicates the categorization
of the message and SHALL be a 4 bit field containing one of the values listed in [NCI]
specification.
All GID values not defined in [NCI] specification are RFU.
 Opcode Identifier (OID)
The Opcode Identifier (OID) indicates the identification of the Control Message and
SHALL be a 6 bit field which is a unique identification of a set of Command, Response or
Notification Messages within the group (GID). OID values are defined along with the
definition of the respective Control Messages described in [NCI] specification.
 Payload Length (L)
The Payload Length SHALL indicate the number of octets present in the payload. The
Payload Length field SHALL be an 8 bit field containing a value from 0 to 255.
Payload Length (L)
MT
GID
3
4
6 8
Octet 0 Octet 1
Octet 2
P
B
F
1
1
1
Payload
L bytes
Octet 3... Octet (2+L)
Packet Header
R
F
U
OID
R
F
U