libosmocore/include/osmocom/gsm/gsup_sms.h

46 lines
1.3 KiB
C
Raw Normal View History

GSUP/SMS: introduce MO-/MT-FORWARD-SM messages According to 3GPP TS 29.002, there are two services: - MAP-MO-FORWARD-SHORT-MESSAGE (see 12.2), - MAP-MT-FORWARD-SHORT-MESSAGE (see 12.9), which are used to forward MO/MT short messages. This change replicates both services as GSUP messages: - OSMO_GSUP_MSGT_MO_FORWARD_SM_*, - OSMO_GSUP_MSGT_MT_FORWARD_SM_*. Please note, that only the 'must-have' IEs are introduced by this change, in particular the following: - OSMO_GSUP_SM_RP_MR_IE (see note below), - OSMO_GSUP_SM_RP_DA_IE (see 7.6.8.1), - OSMO_GSUP_SM_RP_OA_IE (see 7.6.8.2), - OSMO_GSUP_SM_RP_UI_IE (see 7.6.8.4), - OSMO_GSUP_SM_RP_MMS_IE (see 7.6.8.7), - OSMO_GSUP_SM_RP_CAUSE_IE (see GSM TS 04.11, 8.2.5.4), where both SM_RP_DA and SM_RP_OA IEs basically contain a single nested TV of the following format: - T: identity type (see 'osmo_gsup_sms_sm_rp_oda_t'), - V: encoded identity itself (optional). According to GSM TS 04.11, every single message on the SM-RL has an unique message reference (see 8.2.3), that is used to link an RP-ACK or RP-ERROR message to the associated (preceding) RP-DATA or RP-SMMA message transfer attempt. In case of TCAP/MAP, this message reference is being mapped to the Invoke ID. But since GSUP has no 'Invoke ID' IE, and it is not required for other applications (other than SMS), this change introduces a special 'SM_RP_MR' IE that doesn't exist in MAP. Change-Id: Ibe325c64ae2d6c626b232533bb4cbc65fc2b5d71 Related Change-Id: (docs) Ie0150756c33c1352bc4eb49421824542c711175c Related Change-Id: (TTCN) Ibf49474a81235096c032ea21f217170f523bd94e Related: OS#3587
2018-09-25 16:03:13 +00:00
#pragma once
/*! \addtogroup gsup
* @{
*
* This header defines SMS (Short Message Service) extensions for
* Osmocom GSUP (Generic Subscriber Update Protocol). The scope of
* this module is defined by 3GPP TS 29.002, section 12.
*
* \file gsup_sms.h
* SMS (Short Message Service) extensions for Osmocom GSUP. */
#include <stdint.h>
/*! Possible identity types for SM-RP-{OA|DA} */
enum osmo_gsup_sms_sm_rp_oda_t {
OSMO_GSUP_SMS_SM_RP_ODA_NONE = 0x00,
OSMO_GSUP_SMS_SM_RP_ODA_IMSI = 0x01,
OSMO_GSUP_SMS_SM_RP_ODA_MSISDN = 0x02,
OSMO_GSUP_SMS_SM_RP_ODA_SMSC_ADDR = 0x03,
/*! Special value for noSM-RP-DA and noSM-RP-OA */
OSMO_GSUP_SMS_SM_RP_ODA_NULL = 0xff,
};
/*! Alert reason values, see 7.6.8.8 */
enum osmo_gsup_sms_sm_alert_rsn_t {
OSMO_GSUP_SMS_SM_ALERT_RSN_NONE = 0x00,
OSMO_GSUP_SMS_SM_ALERT_RSN_MS_PRESENT = 0x01,
OSMO_GSUP_SMS_SM_ALERT_RSN_MEM_AVAIL = 0x02,
};
GSUP/SMS: introduce MO-/MT-FORWARD-SM messages According to 3GPP TS 29.002, there are two services: - MAP-MO-FORWARD-SHORT-MESSAGE (see 12.2), - MAP-MT-FORWARD-SHORT-MESSAGE (see 12.9), which are used to forward MO/MT short messages. This change replicates both services as GSUP messages: - OSMO_GSUP_MSGT_MO_FORWARD_SM_*, - OSMO_GSUP_MSGT_MT_FORWARD_SM_*. Please note, that only the 'must-have' IEs are introduced by this change, in particular the following: - OSMO_GSUP_SM_RP_MR_IE (see note below), - OSMO_GSUP_SM_RP_DA_IE (see 7.6.8.1), - OSMO_GSUP_SM_RP_OA_IE (see 7.6.8.2), - OSMO_GSUP_SM_RP_UI_IE (see 7.6.8.4), - OSMO_GSUP_SM_RP_MMS_IE (see 7.6.8.7), - OSMO_GSUP_SM_RP_CAUSE_IE (see GSM TS 04.11, 8.2.5.4), where both SM_RP_DA and SM_RP_OA IEs basically contain a single nested TV of the following format: - T: identity type (see 'osmo_gsup_sms_sm_rp_oda_t'), - V: encoded identity itself (optional). According to GSM TS 04.11, every single message on the SM-RL has an unique message reference (see 8.2.3), that is used to link an RP-ACK or RP-ERROR message to the associated (preceding) RP-DATA or RP-SMMA message transfer attempt. In case of TCAP/MAP, this message reference is being mapped to the Invoke ID. But since GSUP has no 'Invoke ID' IE, and it is not required for other applications (other than SMS), this change introduces a special 'SM_RP_MR' IE that doesn't exist in MAP. Change-Id: Ibe325c64ae2d6c626b232533bb4cbc65fc2b5d71 Related Change-Id: (docs) Ie0150756c33c1352bc4eb49421824542c711175c Related Change-Id: (TTCN) Ibf49474a81235096c032ea21f217170f523bd94e Related: OS#3587
2018-09-25 16:03:13 +00:00
struct osmo_gsup_message;
struct msgb;
int osmo_gsup_sms_encode_sm_rp_da(struct msgb *msg,
const struct osmo_gsup_message *gsup_msg);
int osmo_gsup_sms_decode_sm_rp_da(struct osmo_gsup_message *gsup_msg,
uint8_t *data, size_t data_len);
int osmo_gsup_sms_encode_sm_rp_oa(struct msgb *msg,
const struct osmo_gsup_message *gsup_msg);
int osmo_gsup_sms_decode_sm_rp_oa(struct osmo_gsup_message *gsup_msg,
uint8_t *data, size_t data_len);
/*! @} */