1.5.1 G3 Coordinator Access

This protocol consists of the serialization of the G3 coordinator API different primitives.
Figure 1-9. G3 COORD API USI Frame Format
The following two fields are available within the general MESSAGE DATA field:
  • G3 COORD API COMMAND (1 byte): Available commands are enumerated in Table 1-3 and in the G3.h file.
  • Primitive function parameters: The serialization of each primitive concatenates the different parameters included in the function. This serialization order matches with the parameter order indicated in the G3 specification for each primitive. Its type and length can be seen in the examples provided.
Table 1-3. G3 Coordinator API Commands
G3 Coordinator API CommandID
G3_SERIAL_MSG_COORD_INITIALIZE0x01
G3_SERIAL_MSG_COORD_SET_REQUEST0x02
G3_SERIAL_MSG_COORD_GET_REQUEST0x03
G3_SERIAL_MSG_COORD_KICK_REQUEST0x04
G3_SERIAL_MSG_COORD_REKEYING_REQUEST0x05
G3_SERIAL_MSG_COORD_SET_CONFIRM0x06
G3_SERIAL_MSG_COORD_GET_CONFIRM0x07
G3_SERIAL_MSG_COORD_JOIN_INDICATION0x08
G3_SERIAL_MSG_COORD_LEAVE_INDICATION0x09
Note: All the primitives described above have similar names to the functions described in the G3 specification.