This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
Vadim Yanitskiy gerrit-no-reply at lists.osmocom.orgVadim Yanitskiy has uploaded this change for review. ( https://gerrit.osmocom.org/11837 Change subject: chapters/gsup.adoc: document READY-FOR-SM message ...................................................................... chapters/gsup.adoc: document READY-FOR-SM message Change-Id: I549b6c8840a1e86caac09e77fb8bc5042d939e62 Related Change-Id: Ic37f3b2114b8095cfce22977e67133b9103942e3 Related Change-Id: If2256607527ecfcb10285583332fb8b0515d7c78 Related: OS#3587 --- M common/chapters/gsup.adoc 1 file changed, 77 insertions(+), 0 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/37/11837/1 diff --git a/common/chapters/gsup.adoc b/common/chapters/gsup.adoc index 7568fe2..237a4fd 100644 --- a/common/chapters/gsup.adoc +++ b/common/chapters/gsup.adoc @@ -627,6 +627,63 @@ _MT-forwardSM Result_ is triggered by _RP-ACK_ on the _SM-RL (Relay Layer)_. +==== READY-FOR-SM Request + +Direction: SGSN / MSC => ESME (through VLR and HLR) + +[options="header",cols="5%,45%,20%,10%,10%,10%"] +|=== +|IEI|IE|Type|Presence|Format|Length +| |Message Type|<<gsup-ie-msgtype>>|M|V|1 +|01|IMSI|<<gsup-ie-imsi>>|M|TLV|2-10 +|40|SM-RP-MR (Message Reference)|<<gsup-ie-sm-rp-mr>>|M|TLV|1 +|45|SM Alert Reason|<<gsup-ie-sm-al-reas>>|M|TLV|1-... +|=== + +This message is used between the SGSN (PS domain) / MSC (CS domain) +and an ESME (External Short Message Entity) when a subscriber indicates +memory available situation (see TS GSM 04.11, section 7.3.2) using the +_RP-SMMA_ message. The corresponding MAP service (defined in 3GPP TS 29.002) +is *MAP-READY-FOR-SM*, described in section 12.4. + +==== READY-FOR-SM Error + +Direction: ESME / HLR / VLR => SGSN / MSC + +[options="header",cols="5%,45%,20%,10%,10%,10%"] +|=== +|IEI|IE|Type|Presence|Format|Length +| |Message Type|<<gsup-ie-msgtype>>|M|V|1 +|01|IMSI|<<gsup-ie-imsi>>|M|TLV|2-10 +|40|SM-RP-MR (Message Reference)|<<gsup-ie-sm-rp-mr>>|M|TLV|1 +|44|SM-RP-Cause (Cause value)|<<gsup-ie-sm-rp-cause>>|M|TLV|1 +|43|SM-RP-UI (diagnostic field)|<<gsup-ie-sm-rp-ui>>|O|TLV|1-... +|=== + +This message is used to indicate a negative result of a _MO (Mobile Originated)_ +_SMMA (SM Memory Available)_ notification from SGSN (PS domain) / MSC (CS domain) +to an ESME (External Short Message Entity). Thus it triggers an _RP-ERROR_ on +the _SM-RL (Relay Layer)_ of SGSN (PS domain) / MSC (CS domain). The corresponding MAP +service (defined in 3GPP TS 29.002) is *MAP-READY-FOR-SM*, described in section 12.4. + +==== READY-FOR-SM Result + +Direction: ESME / HLR / VLR => SGSN / MSC + +[options="header",cols="5%,45%,20%,10%,10%,10%"] +|=== +|IEI|IE|Type|Presence|Format|Length +| |Message Type|<<gsup-ie-msgtype>>|M|V|1 +|01|IMSI|<<gsup-ie-imsi>>|M|TLV|2-10 +|40|SM-RP-MR (Message Reference)|<<gsup-ie-sm-rp-mr>>|M|TLV|1 +|=== + +This message is used to indicate a successful result of a _MO (Mobile Originated)_ +_SMMA (SM Memory Available)_ notification from SGSN (PS domain) / MSC (CS domain) +to an ESME (External Short Message Entity). Thus it triggers an _RP-ERROR_ on +the _SM-RL (Relay Layer)_ of SGSN (PS domain) / MSC (CS domain). The corresponding MAP +service (defined in 3GPP TS 29.002) is *MAP-READY-FOR-SM*, described in section 12.4. + === Information Elements [[gsup-ie-msgtype]] @@ -663,6 +720,9 @@ |0x28|MT-forwardSM Request |0x29|MT-forwardSM Error |0x2a|MT-forwardSM Result +|0x2c|READY-FOR-SM Request +|0x2d|READY-FOR-SM Error +|0x2e|READY-FOR-SM Result |=== [[gsup-ie-ipaddr]] @@ -894,6 +954,7 @@ |0x42|SM-RP-OA (Originating Address)|<<gsup-ie-sm-rp-oa>> |0x43|SM-RP-UI (SM TPDU)|<<gsup-ie-sm-rp-ui>> |0x44|SM-RP-Cause (RP Cause value)|<<gsup-ie-sm-rp-cause>> +|0x45|SM Alert Reason|<<gsup-ie-sm-al-reas>> |=== [[gsup-ie-empty]] @@ -1177,3 +1238,19 @@ is specified in TS GSM 03.40. But since GSUP has no generic _User Error IE_, and it is not required for other applications (other than SMS), a special <<gsup-ie-sm-rp-cause>> is used to carry the cause value \'as-is'. + +[[gsup-ie-sm-al-reas]] +==== SM Alert Reason + +According to 3GPP TS 29.002, section 7.6.8.8, Alert Reason is used to +indicate the reason why the service centre is alerted. It can take one +of the following values: + +.SM Alert Reason values +[options="header",cols="15%,85%"] +|=== +|Type|Description +|0x00|Special value in libosmocore's API +|0x01|MS present +|0x02|Memory Available +|=== -- To view, visit https://gerrit.osmocom.org/11837 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-MessageType: newchange Gerrit-Change-Id: I549b6c8840a1e86caac09e77fb8bc5042d939e62 Gerrit-Change-Number: 11837 Gerrit-PatchSet: 1 Gerrit-Owner: Vadim Yanitskiy <axilirator at gmail.com> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20181119/45724fd1/attachment.htm>