2.2.1 IrDial Message Formats
As specified in [IRTTP] section 2.2.1, the maximum size of a single Data-Carrying TinyTP PDUs packet for a given connection is negotiated by the IrDA Link Access Protocol, as specified in [IRLAP].
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Delta Credit |
M |
IrDial Message (variable) |
|||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
Delta Credit (7 bits): The Delta Credit field MUST specify the number (0-127) of additional Data-Carrying TinyTP PDUs that can be sent in the reverse direction, as specified in [IRTTP] section 2.3.1.
M (1 bit): The M field MUST be set to zero, as specified in [IRTTP] section 2.3.1, to denote that this is a single TinyTP PDU.
IrDial Message (variable): Each IrDial message is a sequence of ASCII characters and MUST conform to the definitions in section 2.2.1. Messages of this form are often referred to as AT Command Sets. The IrDial message MUST NOT exceed the maximum size of a TinyTP PDU, which is negotiated by the IrDA Link Access Protocol, as specified in [IRLAP]. For further details, see [IRTTP] section 2.2.1.