gsm0480: copy the raw USSD data, its DCS and length
As it was already documented before, the 'ss_request' struct has
a rudiment of deprecated 'ussd_request' struct - the 'ussd_text'
field. It represents the data either of an INVOKE component,
either of a RETURN_RESULT component, encoded as ASCII in case
if DCS is 0x0f (i.e. decoded by the code itself), otherwise
raw bytes 'as is'.
Previously, there was no possibility to distinguish between
ASCII and raw bytes with different DCS. Moreover, the payload
decoding is not desired in some cases.
Let's introduce the new fields, which will carry the raw
unmodified payload, its length and DCS (Data Coding Scheme).
Change-Id: Ia193d175021e145bb3b131290231f307dbefc64a
diff --git a/include/osmocom/gsm/gsm0480.h b/include/osmocom/gsm/gsm0480.h
index 05c26df..b0b6aa2 100644
--- a/include/osmocom/gsm/gsm0480.h
+++ b/include/osmocom/gsm/gsm0480.h
@@ -67,6 +67,18 @@
uint8_t ussd_text[GSM0480_USSD_OCTET_STRING_LEN];
/**
+ * Represents the data of either an INVOKE, either
+ * a RETURN_RESULT component 'as is'. Useful when
+ * decoding is not supported or not desired.
+ *
+ * Shall be always followed by its length (in bytes)
+ * and DCS (Data Coding Scheme).
+ */
+ uint8_t ussd_data[GSM0480_USSD_OCTET_STRING_LEN];
+ uint8_t ussd_data_len; /* Length in bytes */
+ uint8_t ussd_data_dcs; /* Data Coding Scheme */
+
+ /**
* GSM TS 04.80, section 3.3 "Transaction identifier"
* See GSM TS 04.07, section 11.2.3 for details.
*/