GSUP/SMS: introduce READY-FOR-SM message
According to 3GPP TS 29.002, section 12.4, MAP-READY-FOR-SM is
used between the MSC and VLR as well as between the VLR and the
HLR to indicate that a subscriber has memory available for SMS.
This change replicates this service in GSUP as READY_FOR_SM_*.
The only mandatory IE for this service (excluding Invoke ID) is
'Alert Reason' that is replicated by OSMO_GSUP_SM_ALERT_RSN_IE.
Change-Id: Ic37f3b2114b8095cfce22977e67133b9103942e3
Related Change-Id: (docs) I549b6c8840a1e86caac09e77fb8bc5042d939e62
Related Change-Id: (TTCN) If2256607527ecfcb10285583332fb8b0515d7c78
Related: OS#3587
diff --git a/include/osmocom/gsm/gsup.h b/include/osmocom/gsm/gsup.h
index 192b877..51871e4 100644
--- a/include/osmocom/gsm/gsup.h
+++ b/include/osmocom/gsm/gsup.h
@@ -97,6 +97,7 @@
OSMO_GSUP_SM_RP_UI_IE = 0x43,
OSMO_GSUP_SM_RP_CAUSE_IE = 0x44,
OSMO_GSUP_SM_RP_MMS_IE = 0x45,
+ OSMO_GSUP_SM_ALERT_RSN_IE = 0x46,
};
/*! GSUP message type */
@@ -138,6 +139,10 @@
OSMO_GSUP_MSGT_MT_FORWARD_SM_REQUEST = 0b00101000,
OSMO_GSUP_MSGT_MT_FORWARD_SM_ERROR = 0b00101001,
OSMO_GSUP_MSGT_MT_FORWARD_SM_RESULT = 0b00101010,
+
+ OSMO_GSUP_MSGT_READY_FOR_SM_REQUEST = 0b00101100,
+ OSMO_GSUP_MSGT_READY_FOR_SM_ERROR = 0b00101101,
+ OSMO_GSUP_MSGT_READY_FOR_SM_RESULT = 0b00101110,
};
#define OSMO_GSUP_IS_MSGT_REQUEST(msgt) (((msgt) & 0b00000011) == 0b00)
@@ -250,6 +255,8 @@
const uint8_t *sm_rp_cause;
/*! SM-RP-MMS (More Messages to Send), section 7.6.8.7 */
const uint8_t *sm_rp_mms;
+ /*! Alert reason (see 3GPP TS 29.002, 7.6.8.8) */
+ enum osmo_gsup_sms_sm_alert_rsn_t sm_alert_rsn;
};
int osmo_gsup_decode(const uint8_t *data, size_t data_len,