GSM 03.40规范：超长短信SMS PDU解析

5星 · 超过95%的资源需积分: 13 27 浏览量更新于2024-07-30 收藏 870KB PDF 举报

"GSM 03.40 手机短信 SMS PDU 标准是欧洲电信标准协会（ETSI）制定的一项行业规范，旨在规定全球系统移动通信（GSM）网络中短消息服务（SMS）的点对点（PP）传输技术实现。这个标准在1996年发布了第5.8.1版，适用于数字蜂窝通信系统（Phase2+）。它主要关注如何处理手机发送的超长短信，确保不同设备间的兼容性和高效传递。" GSM 03.40 标准是 GSM 短信服务的重要组成部分，它定义了 SMS 在 GPRS 和 GSM 网络中的协议数据单元（PDU）格式，这包括了短信编码、分段和重组过程。短信在传输时可能超过一个单一数据包的容量，因此必须被分割成多个部分，这些部分在接收端重新组合成原始消息。这一过程涉及到 SMS 的用户数据编码（如 7 位、8 位或 16 位编码），以及消息头的构建，用于指示消息的段数、序号以及是否是消息的最后一个部分。标准中的关键技术点包括： 1. **SMS PDU 模式**：PDU（Protocol Data Unit）模式是 SMS 传输的一种方式，它允许将短信数据以二进制格式编码，以便在网络中高效传输。PDU 包含控制信息和用户数据，控制信息用于指示短信的类型、目的地址、编码方式等。 2. **短信分段**：当短信内容过长时，需要将其分成若干个较小的数据段，每个数据段包含一部分消息内容。每个段都有一个段标识符，以便接收端按顺序重组。 3. **User Data Header (UDH)**：在 PDU 中，UDH 是一段额外的控制信息，用于指示消息的分段情况。它包含了段计数、顺序信息和可选的复用信息，帮助接收端正确地组合分段消息。 4. **编码方案**：GSM 03.40 规定了不同的编码方案，如 7 位编码（GSM 7），可以有效地压缩文本，但仅支持基本拉丁字符集；8 位编码（UCS-2）用于非 ASCII 字符，如特殊符号或非拉丁字母；16 位编码（UCS-2）则用于更广泛的语言支持。 5. **错误检测与纠正**：标准中还包含了错误检测机制，如奇偶校验位，以确保数据在传输过程中的完整性。 6. **兼容性**：GSM 03.40 确保了不同制造商的设备之间能够相互通信，无论短信是通过网络还是直接在手机之间发送。 GSM 03.40 标准是 SMS 技术的基础，它规定了短信在 GSM 网络中的传输方式，确保了不同设备间短信的可靠传递，特别是对于处理长短信的分段和重组。理解和掌握这个标准对于开发和维护 SMS 相关的应用和服务至关重要。

Page 16

ETS 300 901 (GSM 03.40 version 5.8.1 Release 1996): December 1998

MSIsdn-Alert

SC address

MNRF

MCEF

HLR;

MWD:

MNRF

VLR;

...

Figure 03.40/3: Example of how information on one MS can be put in relation to SC(s)

in order to fulfil the requirement of Alert-SC mechanism

The MWD shall contain a list of addresses (SC-Addr) of SCs which have made previous unsuccessful

delivery attempts of a message (see clause 5). In order to be able to send alert messages to every SC

which has made unsuccessful delivery attempts to an MS, the HLR shall store the MSIsdn-Alert (see

subclause 3.2.7) together with references to the SC addresses. The requirements placed upon the HLR

are specified in GSM 03.08. The description of how the HLR is provided with SC and MS address

information is given in GSM 09.02.

The Mobile-Station-Memory-Capacity-Exceeded-Flag (MCEF) within the HLR is a Boolean parameter with

the value TRUE when the list MWD contains one or more list elements because an attempt to deliver a

short message to an MS has failed with a cause of MS Memory Capacity Exceeded, and with the value

FALSE otherwise.

The Mobile-Station-Not-Reachable-Flag (MNRF) within the HLR and the VLR is a Boolean parameter with

the value TRUE when the list MWD contains one or more list elements because an attempt to deliver a

short message to an MS has failed with a cause of Absent Subscriber, and with the value FALSE

otherwise.

The Mobile-Station-Not-Reachable-Reason (MNRR) within the HLR stores the reason for the MS being

absent when an attempt to deliver a short message to an MS fails at the MSC with the cause Absent

Subscriber. The HLR updates the MNRR with the reason for absence when an absent subscriber

diagnostic information is received from the GMSC and the MNRF is set. The HLR clears the MNRR when

the MNRF is cleared. If the MNRF is set due to a failure at the MSC with cause Absent Subscriber and

information pertaining to the absence of the MS is not available from the GMSC, the MNRR will remain in

a cleared state. The MNRR shall either be in a cleared state or contain one of the following reasons:

No Paging Response

IMSI Detached

NOTE: When a short message delivery attempt fails at the HLR due to Roaming being

Restricted, the MS being Deregistered in HLR or the MS being Purged the absent

subscriber diagnostic reason is returned to the SC, however the reason is not stored in

the MNRR.

The MWD, MCEF, MNRR and MNRF are updated in the following way:

1a) When a mobile terminated short message delivery fails due to the MS being temporarily absent (i.e.

either IMSI DETACH flag is set or there is no response from the MS to a paging request), the SC

address is inserted into the MWD list (if it is not already present), the MNRF is set (if it is not already

set) and the MNRR is updated (if the information is available), as described in clause 10.

Page 17

ETS 300 901 (GSM 03.40 version 5.8.1 Release 1996): December 1998

1b) When a mobile terminated short message delivery fails due to the MS memory capacity being

exceeded, the SC address is inserted into the MWD list (if it is not already present) and the MCEF

is set (if it is not already set), as described in clause 10.

1c) If the MSIsdn used by the SC to address the recipient MS for alerting purposes is different from the

MSIsdn-Alert of the MS (see subclause 3.2.7), the HLR returns the MSIsdn-Alert to the SC within

the failure report, see "1c Failure report" in figures 03.40/15 and /16.

2a) When either the HLR or VLR detects that the MS (with a non-empty MWD and the MCEF clear in

the HLR and the MNRF set in the VLR) has recovered operation (e.g. has responded to a paging

request), the HLR directly or on request of the VLR will invoke operations to alert the SCs within the

MWD (see subclause 3.2.7 and clause 10). Once the Alert SC operations have been invoked, the

MNRF and MNRR are cleared. After each SC is alerted by the HLR, the address for that SC is

deleted from the MWD. If the MCEF is set in the HLR, the HLR clears the MNRF and MNRR, but

does not invoke operations to alert the SCs within the MWD and data are not cleared from the

MWD.

2b) When the HLR receives (via the MSC and the VLR) a notification that the MS (with a non-empty

MWD and the MCEF set in the HLR) has memory capacity available to receive one or more short

messages, the HLR will invoke operations to alert the SCs within the MWD (see subclause 3.2.7

and clause 10). Once the Alert SC operations have been invoked, the MNRF is cleared in the VLR

and the MCEF, MNRF and MNRR are cleared in the HLR. After each SC is alerted by the HLR, the

address for that SC is deleted from the MWD.

2c) When the HLR receives from the SMS-GMSC a notification that a short message has been

successfully delivered from an SC to an MS for which the MCEF is set and the MWD are not empty,

the HLR will invoke operations to alert other SCs within the MWD (see subclause 3.2.7 and

clause 10). Once the Alert SC operations have been invoked, the MCEF, MNRF and MNRR are

cleared in the HLR. After each SC is alerted by the HLR, the address for that SC is deleted from the

MWD. The SC which successfully delivered the message is also deleted from the MWD, if present.

2d) When the HLR receives (via the MSC and the VLR) a notification that the MS has memory capacity

available to receive one or more short messages but the MCEF is not set and the MWD are empty,

the HLR acknowledges the notification but does not alert any service centre.

3.2.7 Alert-SC

The Alert-SC is the service element, which may be provided by some GSM PLMNs, to inform the SC that

an MS

1) to which a delivery attempt has failed because the MS is not reachable or because the MS memory

capacity was exceeded;

and

2) which is now recognized by the PLMN:

a) to have resumed operation (e.g. to have responded to a paging request); or

b) to have memory newly available (which implies that the mobile is reachable).

is again ready to receive one or more short messages. The SC may - on reception of an Alert-SC - initiate

the delivery attempt procedure for the queued messages destined for this MS.

To each MS there may be allocated several MSIsdns. When the HLR is to alert an SC that an MS is again

attainable it will use a specific MSIsdn value for this purpose; in this specification called MSIsdn-Alert.

NOTE: Repeated delivery attempts from the SC may be of two types:

i) A repeated delivery attempt because the SC has been informed that the MS is

active and available to receive short messages.

ii) An autonomous repeated delivery attempt by the SC.

Page 18

ETS 300 901 (GSM 03.40 version 5.8.1 Release 1996): December 1998

The application of these two options is defined by the providers of the SC and the

network.

3.2.8 Options concerning MNRF, MNRR, MCEF and MWD

Setting the Mobile-Station-Not-Reachable-Flag (MNRF) in the VLR is mandatory. It is also mandatory for

the VLR to send the "MS Present" message (see clause 10) to the HLR when the MS has been detected

as becoming active and then to clear MWF.

The Messages-Waiting-Data (MWD, the Mobile-Station-Not-Reachable-Flag (MNRF), the Mobile-Station-

Not-Reachable-Reason (MNRR) and the Mobile-Station-Memory-Capacity-Exceeded-Flag (MCEF)) within

the HLR are optional, but if one is implemented all must be implemented. This is linked to the

transmission of the "Alert SC" message.

The following describes what happens when a delivery fails.

Case 1: MWD, MNRF, MNRR and MCEF are implemented in the HLR

In the case of a delivery failure (to an MS) with cause Absent Subscriber, the MSC requests the

HLR to add, if needed, a new entry in the MWD with cause Absent Subscriber. This new entry

contains the SC address. The HLR sets its copy of the MNRF and updates the MNRR (if the

information is available). The SC is notified of the failure, the reason for the MS being absent and

also of the MWD setting in the HLR within the Report message (see clause 10).

In the case of a delivery failure (to an MS) with cause Mobile Station Memory Capacity Exceeded,

the MSC requests the HLR to add, if needed, a new entry in the MWD with cause Mobile Station

Memory Capacity Exceeded. This new entry contains the SC address. The HLR sets the MCEF.

The SC is notified of the failure and also of the MWD setting in the HLR within the Report message

(see clause 10).

If the HLR indicates that it is able to store the SC address, then the SC will receive an Alert SC

message when the MS becomes active.

If the HLR indicates that it is unable to store the SC address (e.g. because MWD is full), then the

only way to ensure delivery is for the SC to try to retransmit the message periodically.

When the HLR receives the MS Present message, if the MCEF is clear it sends an Alert SC

message to the concerned SC and updates MWD.

When the HLR receives the MS Memory Capacity Available message, it sends an Alert SC

message to the concerned SC, updates MWD and clears the MCEF.

Case 2: MWD, MNRF, MNRR and MCEF are not implemented in the HLR

In the case of a delivery failure, the SC is notified that the HLR is unable to store its address in the

MWD. In case of a delivery failure (to a MS) with cause Absent Subscriber, the SC is notified of the

reason for the MS being absent (if the information is available). The SC must retransmit the short

message periodically in order to ensure delivery.

The HLR discards the MS Present message received from the VLR without any failure or error

report.

The HLR discards the MS Memory Capacity Available message received from the MS via the MSC

and the VLR without any failure or error report.

Page 19

ETS 300 901 (GSM 03.40 version 5.8.1 Release 1996): December 1998

3.2.9 Status report capabilities

The SMS also offers to the SC the capabilities of informing the MS of the status of a previously sent

mobile originated short message. The status of the message can be:

- Successfully delivered to the SME;

- The SC was not able to forward the message to the SME. The reason can be an error of permanent

or temporary nature. Permanent errors can be e.g. validity period expired, invalid SME address.

Errors of temporary nature can be e.g. SC-SME connection being down, SME temporarily

unavailable.

This is achieved by the SC returning a status report TPDU (SMS-STATUS-REPORT) to the originating

MS when the SC has concluded the status of the short message. The status report may be initiated by a

status report request within the mobile originated short message. The status report TPDU is treated as an

SMS-DELIVER TPDU by the SC when it comes to delivery procedures e.g. the alerting mechanism.

The SC may also return to a non-MS SME the status of a mobile terminated short message. This is

however outside the scope of this specification.

The status report capabilities of the SMS are optional, i.e. the choice of whether to offer status report or

not is left to the SC operator.

3.2.10 Reply Path

Reply Path specified in this specification provides a way of both requesting and indicating a service

centre's commitment to deliver a reply from the replying MS to the originating SME.

Annex D deals with MS procedures, which in general are outside the scope of GSM specifications.

However, for advanced use of the SMS, including both application level protocols and human responses,

it is of vital importance to guarantee that a reply-supporting MS is able to reply on every SM, to every SME

capable of receiving such reply short messages.

3.3 Unsuccessful short message TPDU transfer SC -> MS

Unsuccessful message transfer SC -> MS may be caused by a variety of different errors. The description

of the occurrence of the different errors and how to handle and transfer the error indications is given in

GSM 04.08, GSM 04.11 and GSM 09.02.

The different error indications which the SMS-GMSC shall be capable of returning to the SC following an

unsuccessful short message TPDU transfer SC -> MS, are given in table 03.40/1. In some cases,

additional diagnostic information may be provided.

3.3.1 Errors occurring during transfer of TPDU to MS

These errors are generally due to barring or unsupported service in the PLMN or MS. An error indication is

returned to the SC from the SMS-GMSC, but further diagnostic information from the MS will not be

available.

3.3.2 Errors occurring after TPDU arrives at MS

These errors may occur due to the MS not supporting optional short message service features, or in

connection with a short message application. An error indication shall be returned to the SC from the

SMS-GMSC. Additionally, a TPDU (SMS-DELIVER-REPORT) containing diagnostic information may be

conveyed from the MS to the originating SC, transparently through the PLMN, by means defined in

GSM 04.11 and GSM 09.02. The sending of the diagnostic information is optional at the MS, but when it is

sent, the PLMN shall convey the information to the SC, and the SC shall support reception of the

information.

Page 20

ETS 300 901 (GSM 03.40 version 5.8.1 Release 1996): December 1998

Table 03.40/1: Error indications related to mobile terminated short message transfer which may be

transferred to the originating SC.

Error indication S

Meaning

Unknown subscriber P The PLMN rejects the short message TPDU because there is not allocated

an IMSI or a directory number for the mobile subscriber in the HLR (see

GSM 09.02).

Teleservice not provisioned P The PLMN rejects the short message TPDU because the recipient MS has

no SMS subscription (see GSM 09.02).

Call barred T The PLMN rejects the short message TPDU due to barring of the MS (see

GSM 09.02, description of the Barring supplementary service, GSM 02.04

and 03.11), and description of Operator Determined Barring, GSM 02.41

and 03.15).

Facility not supported T The VPLMN rejects the short message TPDU due to no provision of the

SMS in the VPLMN (see GSM 09.02).

Absent subscriber T The PLMN rejects the short message TPDU because

- there was no paging response,

(see GSM 04.08 & GMS 09.02)

- the IMSI record is marked detached (see GSM 09.02),

- the MS is subject to roaming restrictions (see "Roaming not allowed",

GSM 09.02).

- deregistered in the HLR. The HLR does not have an MSC number stored

for the target MS, (see GSM 09.02)

- MS purged, (see GMS 09.02)

(The reasons for absence are assigned interger values in table 03.40/1a.

The appropriate integer value is sent with the absent subscriber error

indication as defined in GSM 09.02)

MS busy for MT SMS T The PLMN rejects the short message TPDU because of congestion

encountered at the visited MSC. Possible reasons include any of the

following events in progress:

- short message delivery from another SC

- IMSI detach

- Location Update

- paging

- emergency call

- call setup

SMS lower layers

capabilities not provisioned

T The PLMN rejects the short message TPDU due to MS not being able to

support the Short Message Service.

The short message transfer attempt is rejected either due to information

contained in the class-mark, or the MSC not being able to establish

connection at SAPI = 3 (see GSM 04.08 and GSM 09.02).

Error in MS T The PLMN rejects the short message TPDU due to an error occurring within

the MS at reception of a short message, e.g. lack of free memory capacity or

protocol error.

Illegal Subscriber P The PLMN rejects the short message TPDU because the MS failed

authentication

Illegal Equipment P The PLMN rejects the short message TPDU because the IMEI of the MS

was black-listed in the EIR

System failure T The PLMN rejects the short message TPDU due to network or protocol

failure others than those listed above (see GSM 09.02)

Memory Capacity Exceeded T The MS rejects the short message since it has no memory capacity

available to store the message

1) : Status (Permanent or Temporary)

The relation between the two sets of error indications is given in the table 03.40/1. Each error is classified

as either

Temporary

Permanent

. This classification gives an indication of whether or not it is

probable that the MS becomes attainable within a reasonable period, and so provides the recommended

action to be taken by the SC, i.e. either to store the message for later transfer, or to discard it.

剩余112页未读，继续阅读

zhenglidianqi

粉丝: 0
资源: 1

GSM 03.40规范：超长短信SMS PDU解析

GSM 03.40技术规范：短消息服务（SMS）实现详解

GSM SMS PDU模式详解

使用AT指令通过串口发送GSM短信的PDU模式详解

GSM.rar_gsm 协议_long sms_pdu_短信PDU_长短信

GSM.PDU.rar_GSM_pdu_pdu gsm _短信 pdu_短信收发

SMS_PDU-mode.rar_PDU mo_pdu_sms pdu_sms 协议_sms_pdu

SMS.rar_Vc_sms_sms 串口_smspdu_vc sms

SMS PDU中文说明及编解码程序

SMS短信编程代码(PDU)

GSM手机PDU模式收发短消息的编程实现

最新资源