Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.040  Word version:  17.3.0

Top   Top   Up   Prev   Next
0…   3…   3.3…   4…   8…   9…   9.2…   9.2.2.2…   9.2.2.3…   9.2.3…   9.2.3.12…   9.2.3.24   9.2.3.24.1…   9.2.3.24.10…   9.2.3.24.10.1.12…   9.2.3.24.10.2…   9.2.3.24.11…   9.2.3.25…   9.3…   10…   10.1.1…   10.1.3…   10.1.5…   10.1.7…   10.1.9…   10.1.11…   10.1.13…   10.1.15…   10.1.17…   10.2   10.2.1…   10.2.3…   10.2.5…   10.2.7…   10.3   11…   A…   C   C.1…   C.3…   C.5…   C.7…   C.9…   C.11…   C.13…   C.15…   D…   E…   F…   G…   G.2…   G.6   G.7   H…   I…   J…   K…

 

9.3  Service provided by the SM-RLp. 109

9.3.1  Generalp. 109

The Short Message Relay Layer (SM-RL) provides a service to the Short Message Transfer Layer (SM-TL). This service enables the SM-TL to send Transfer Protocol Data Units (TPDUs) to its peer entity, receive TPDUs from its peer entity and receive reports about earlier requests for TPDUs to be transferred.
In order to keep track of TPDUs and reports about those TPDUs, primitives between the SM-TL and SM-RL contain a Short Message Identifier (SMI), which is a reference number for the TPDU associated with the primitive. This Short Message Identifier is not carried via the SM-RL protocol of clause 9.3.2. It is carried via the relay layer service between the SC and GMSC. It is also carried by SM-RL of TS 24.011, between the visited MSC and MS. The parameter is not carried by MAP but is mapped to and from the TCAP dialogue Identifier (see CCITT Recommendation Q.771, "Blue Book" [19]) at the GMSC and the visited MSC (therefore the Message Identifier at the SC/GMSC interface is not the same as at the visited MSC/MS interface).
The SM-RL communicates with its peer entity by the protocol described in the following clauses.
Up

9.3.2  Protocol element repertoire at SM-RLp. 109

Different protocols are required between different pairs of SM-RL entities. Those are described in other GSM/UMTS specifications. This clause gives a survey of the different information elements which have to be conveyed between those entities. (Note that the notation of the protocol and information elements may vary between different GSM/UMTS specifications).
The SM-RL comprises the following 6 protocol elements:
RP-MO-DATA
for transferring a TPDU from MS to SC
RP-MT-DATA
for transferring a TPDU from SC to MS
RP-ACK
for acknowledging an RP-MO-DATA, an RP-MT-DATA or an RP-SM-MEMORY-AVAILABLE
RP-ERROR
for informing of an unsuccessful RP-MO-DATA or an RP-MT-DATA transfer attempt
RP-ALERT-SC
for alerting the SC that the MS has recovered operation (information sent from the HLR to the SC)
RP-SM-MEMORY-AVAILABLE
for notifying the network that the MS has memory available to accept one or more short messages (information sent from the MS to the HLR)
Up

9.3.2.1  RP-MO-DATAp. 109

Basic elements of the RP-MO-DATA type.
Abbr. Reference P
(Note 1)
Description
RP-OARP-Originating-Address++-Address of the originating MS.
RP-DARP-Destination-Address-++Address of the destination SC.
RP-UDRP-User-Data+++Parameter containing the TPDU
NOTE 1:
Provision on the links SC↔MSC, MSC↔MSC or MSC↔SGSN, and MSC↔MS or SGSN↔MS indicated by "xxx", where x may be either "+" or "-", dependent on whether the parameter is mandatory or not on the respective link.
Up

9.3.2.2  RP-MT-DATAp. 110

Basic elements of the RP-MT-DATA type.
Abbr. Reference P
(Note 1)
Description
RP-PRIRP-Priority-Request+--Parameter indicating whether or not the short message transfer should be stopped if the originator SC address is already contained in the MWD.
RP-MMSRP-More-Messages-To-SendOO-Parameter indicating that there are more messages waiting in the SC
RP-OARP-Originating-Address+++Address of the originating SC.
RP-DARP-Destination-Address++-Address of the destination MS.
RP-UDRP-User-Data+++Parameter containing the TPDU
RP-MTIRP-Message Type IndicatorO--Parameter indicating if the TPDU is a SMS Deliver or a SMS Status Report (Note 2)
RP-SMEARP-originating SME-AddressO--Address of the originating SME (Note 2)
NOTE 1:
Provision on the links SC↔MSC, MSC↔MSC or MSC↔SGSN, and MSC↔MS or SGSN↔MS indicated by "xxx", where x may be "+", "-" or "O", dependent on whether the parameter is mandatory, not present or optional on the respective link.
NOTE 2:
These information elements may be included in the "Send Routing Information for SM" sent by the SMS-GMSC to the HLR.
When transmitted, the RP-SMEA shall take the TP-OA value.
When transmitted, the RP-MTI shall be given the following values: 0
SMS Deliver.
1
SMS Status Report.
This may be used by the HLR to distinguish the two cases in order not to apply any filtering mechanism based on the RP-SMEA value in case of a SMS-Status Report transmission.
Up

9.3.2.3  RP-ACKp. 110

The RP-ACK contains the RP-User-Data which is a parameter containing the TPDU (see clauses 9.2.2.1a and 9.2.2.2a).

9.3.2.4  RP-ERRORp. 110

Basic elements of the RP-ERROR type.
Abbr. Reference P
(Note 1)
Description
RP-MSIRP-MW-Set-Indication+--Parameter indicating whether or not the MWI has been up-dated. (Note 2)
RP-CSRP-Cause+++ Parameter identifying the error type. The RP-Cause parameter gives the reason why a short message transfer attempt fails. In practice three relay layer protocols are used - SC to GMSC/IWMSC (see Annex A), MAP (see TS 29.002) and via the radio interface (see TS 24.011)
RP-MSIsdnRP-international--MS-ISDN-number+--MSIsdn-Alert or IMSI-Alert of the MS, see clause 3.2.7 (Note 3)
RP-UDRP-User-DataOO OParameter containing a TPDU
NOTE 1:
Provision on the links SC↔MSC, MSC↔MSC or MSC↔SGSN, and MSC↔MS or SGSN↔MS indicated by "xxx", where x may be "+", "-" or "O" dependent on whether the parameter is mandatory, not present or optional on the respective link.
NOTE 2:
Only present when the RP-ERROR is transferred from the SMS-GMSC to the SC.
NOTE 3:
Only present when the RP-MT-DATA transfer attempt failed because the MS is not reachable or because the MS memory capacity was exceeded and the MSIsdn-Alert or IMSI-Alert is different from the MSIsdn or IMSI used by the SC to address the recipient MS.
Up

9.3.2.5  RP-ALERT-SCp. 111

Basic elements of the RP-ALERT-SC type:
Abbr. Reference P
(Note 1)
Description
RP-MSIsdnRP-International-MS-ISDN-NumberOMSIsdn of the MS.
RP-IMSIRP-International-Mobile-Subscriber-IdentityOIMSI of the MS
NOTE 1:
Provision:
Optional (O).
NOTE 2:
It is mandatory to include either RP-MSIsdn or RP-IMSI.
Up

9.3.2.6  RP-SM-MEMORY-AVAILABLEp. 111

Basic elements of the RP-SM-MEMORY-AVAILABLE type:
Abbr. Reference P
(Note 1)
Description
RP-IMSIRP-International-Mobile-Subscriber-Identity++-IMSI of the MS.
NOTE 1:
Provision on the links HLR↔VLR or HLR↔SGSN, VLR↔MSC and MSC↔MS or SGSN↔MS indicated by "xxx", where x may be either "+" or "-", dependent on whether the parameter is mandatory or not present on the respective link.
Up

Up   Top   ToC