Change in osmo-gsm-manuals[master]: chapters/gsup.adoc: document READY-FOR-SM message

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.org
Tue Dec 18 14:49:09 UTC 2018


Vadim Yanitskiy has submitted this change and it was merged. ( 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: (core) Ic37f3b2114b8095cfce22977e67133b9103942e3
Related Change-Id: (TTCN) If2256607527ecfcb10285583332fb8b0515d7c78
Related: OS#3587
---
M common/chapters/gsup.adoc
1 file changed, 73 insertions(+), 0 deletions(-)

Approvals:
  Jenkins Builder: Verified
  Neels Hofmeyr: Looks good to me, approved
  Stefan Sperling: Looks good to me, but someone else must approve



diff --git a/common/chapters/gsup.adoc b/common/chapters/gsup.adoc
index 56a6f9e..c48209d 100644
--- a/common/chapters/gsup.adoc
+++ b/common/chapters/gsup.adoc
@@ -611,6 +611,58 @@
 MT short message delivery. The corresponding MAP service is
 MAP-MT-FORWARD-SHORT-MESSAGE, see 3GPP TS 29.002, section 12.9.
 
+==== READY-FOR-SM Request
+
+Direction: MSC / SGSN => SMSC (via 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
+|46|SM Alert Reason|<<gsup-ie-sm-alert-rsn>>|M|TLV|1-...
+|===
+
+This message is used between the MSC / SGSN and an SMSC when a subscriber
+indicates memory available situation (see TS GSM 04.11, section 7.3.2).
+The corresponding MAP service is MAP-READY-FOR-SM,
+see 3GPP TS 29.002, section 12.4.
+
+==== READY-FOR-SM Error
+
+Direction: SMSC (via HLR) => MSC / SGSN
+
+[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 an earlier
+MO SMMA (Memory Available) indication. The corresponding MAP
+service is MAP-READY-FOR-SM, see 3GPP TS 29.002, section 12.4.
+
+==== READY-FOR-SM Result
+
+Direction: SMSC (via HLR) => MSC / SGSN
+
+[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 an earlier
+MO SMMA (Memory Available) indication. The corresponding MAP
+service is MAP-READY-FOR-SM, see 3GPP TS 29.002, section 12.4.
+
 === Information Elements
 
 [[gsup-ie-msgtype]]
@@ -647,6 +699,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]]
@@ -879,6 +934,7 @@
 |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-RP-MMS (More Messages to Send)|<<gsup-ie-sm-rp-mms>>
+|0x46|SM Alert Reason|<<gsup-ie-sm-alert-rsn>>
 |===
 
 [[gsup-ie-empty]]
@@ -1165,3 +1221,20 @@
 This is an optional IE of MT-ForwardSM-Req message, that is used by SMSC
 to indicate that there are more MT SMS messages to be sent, so the network
 should keep the RAN connection open. See 3GPP TS 29.002, section 7.6.8.7.
+
+[[gsup-ie-sm-alert-rsn]]
+==== 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, e.g. the MS has
+got some memory to store previously rejected incoming SMS.
+
+It can take one of the following values:
+
+.SM Alert Reason values
+[options="header",cols="15%,85%"]
+|===
+|Type|Description
+|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: merged
Gerrit-Change-Id: I549b6c8840a1e86caac09e77fb8bc5042d939e62
Gerrit-Change-Number: 11837
Gerrit-PatchSet: 8
Gerrit-Owner: Vadim Yanitskiy <axilirator at gmail.com>
Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org>
Gerrit-Reviewer: Jenkins Builder (1000002)
Gerrit-Reviewer: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Gerrit-Reviewer: Stefan Sperling <stsp at stsp.name>
Gerrit-Reviewer: Vadim Yanitskiy <axilirator at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20181218/98bb929d/attachment.htm>


More information about the gerrit-log mailing list