L1CTL: Correctly parse L1CTL messages with zero-length payload

Some messages can happen with zero-length payload section,
e.g. a DL_DATA_IND with CRC errors.

Change-Id: Ice1d872c12fb33bc4e2d285870fdb877f6efe355
This commit is contained in:
Harald Welte 2018-04-15 10:58:43 +02:00
parent a28dce1021
commit f56cc49d75
1 changed files with 3 additions and 3 deletions

View File

@ -170,7 +170,7 @@ module L1CTL_Types {
type record L1ctlDlMessage {
L1ctlHeader header,
L1ctlDlInfo dl_info optional,
L1ctlDlPayload payload
L1ctlDlPayload payload optional
} with { variant (dl_info) "PRESENCE(header.msg_type = L1CTL_FBSB_CONF,
header.msg_type = L1CTL_RACH_CONF,
header.msg_type = L1CTL_DATA_IND,
@ -442,7 +442,7 @@ module L1CTL_Types {
template L1ctlDlMessage tr_L1CTL_MsgType(template L1ctlMsgType msg_type) := {
header := tr_L1ctlHeader(msg_type),
dl_info := *,
payload := ?
payload := *
}
template L1ctlDlMessage tr_L1CTL_CCCH_MODE_CONF := tr_L1CTL_MsgType(L1CTL_CCCH_MODE_CONF);
@ -604,7 +604,7 @@ module L1CTL_Types {
template L1ctlDlMessage tr_L1CTL_RACH_CONF := {
header := tr_L1ctlHeader(L1CTL_RACH_CONF),
dl_info := ?,
payload := ?
payload := *
};
/* for matching against incoming DATA_IND */