GSM 03.40通信标准：短消息服务技术实现

5星 · 超过95%的资源需积分: 35 50 浏览量更新于2024-08-02 收藏 339KB PDF 举报

"GSM_03.40_5.3.0 - 该文档是关于GSM 03.40通信标准的版本5.3.0的技术规范，主要涉及数字蜂窝通信系统（Phase2+）中短消息服务（SMS）的点对点（PP）实现。文档由欧洲电信标准协会（ETSI）发布，详细阐述了GSM网络中短信服务的技术实现细节。" GSM（Global System for Mobile Communications），即全球移动通信系统，是一种广泛使用的数字蜂窝通信标准，旨在提供全球漫游和互操作性。GSM 03.40 规范是这个系统的一个关键部分，它详细定义了短消息服务（SMS）在GSM网络中的技术实现，特别是点对点（PP）消息传递的流程和协议。在GSM 03.40 v5.3.0版本中，可能涵盖了以下核心知识点： 1. **短消息服务（SMS）**：SMS允许用户通过手机发送和接收文本消息，它是GSM网络中的一个基本服务。这个规范详细规定了消息的编码、传输、存储和路由机制，确保消息能够在不同的网络节点间正确传递。 2. **点对点（PP）消息**：点对点消息是指消息直接从一个用户设备发送到另一个用户设备，不经过中间服务器。GSM 03.40规范解释了PP消息的建立、维护和释放过程，以及错误处理和重传机制。 3. **协议栈**：文档可能包含了SMS在GSM协议栈中的位置，包括与分组数据业务（GPRS）、电路交换数据（CSD）和其他服务的交互。 4. **消息格式**：描述了短信的结构，包括控制信息、用户数据编码和长度，以及如何将这些信息封装到无线接口的数据包中。 5. **网络操作**：可能包含网络侧的处理，如短信中心（SMSC）的功能，以及短信的存储、转发和确认机制。 6. **安全性**：可能涉及到短信传输的安全措施，如加密和身份验证，防止未经授权的访问或篡改。 7. **兼容性和互操作性**：确保不同制造商的设备和网络可以无缝地交换短信，这是GSM标准的一个关键目标。 8. **错误处理**：定义了在传输过程中遇到问题时的恢复策略，例如网络故障或消息丢失。此规范的5.3.0版本更新可能包含了一些新特性、增强功能或对先前版本的修订，以适应不断发展的通信需求和技术进步。虽然文档的发布日期为1996年，但GSM 03.40规范的重要性并未因时间推移而减弱，因为即使在4G和5G时代，SMS仍然是许多应用和服务的基础，特别是在通知、验证码和紧急通信等方面。 GSM 03.40是理解GSM网络中短信服务实施的关键参考资料，对于网络运营商、设备制造商、软件开发者和电信工程师来说，都是不可或缺的工具。

Page 16

GSM 03.40 Version 5.3.0: July 1996

+/5

¸¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¹

·0:'·

·¸¶¶¶¶¶¶¶¶¶¶¶¶¶¶¾¶¶¶¶¶¶¶¶¶¶¶¶¶¾¶¶¶¶¶¶¶¶¶¶¶¶¶¾¾¶¶¶¶¶¶¶¶¶¶¶¶¶¹·

········

··06,VGQ$OHUW·6&DGGUHVV



·6&DGGUHVV



··6&DGGUHVV

··

········

·º¶¶¶¶¶¶¶¶¶¶¶¶¶¶¿¶¶¶¶¶¶¶¶¶¶¶¶¶¿¶¶¶¶¶¶¶¶¶¶¶¶¶¿¿¶¶¶¶¶¶¶¶¶¶¶¶¶»·

·¸¶¶¶¶¶¶¶¶¶¶¹¸¶¶¶¶¶¶¶¶¶¶¶¹·

······

··015)··0&()··

·º¶¶¶¶¶¶¶¶¶¶»º¶¶¶¶¶¶¶¶¶¶¶»·

··

º¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶»

9/5

¸¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¹

··

·¸¶¶¶¶¶¶¶¶¶¹·

····

··015)··

·º¶¶¶¶¶¶¶¶¶»·

º¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶»

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 section 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

section 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 MWD, MCEF 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) and the MNRF is set (if it is not

already set), as described in section 10.

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 section 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 section 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.

Page 17

GSM 03.40 Version 5.3.0: July 1996

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 section 3.2.7 and section 10). Once the Alert SC operations have been invoked, the

MNRF is 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, 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 section 3.2.7 and

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

the MCEF and MNRF 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 section 3.2.7 and section

10). Once the Alert SC operations have been invoked, the MCEF and MNRF 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.

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

network.

Page 18

GSM 03.40 Version 5.3.0: July 1996

3.2.8 Options concerning MNRF, 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 section 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) 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 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. The SC is notified of the failure and

also of the MWD setting in the HLR within the Report message (see section 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 section 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 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. 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.

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.

剩余108页未读，继续阅读

hellangel603

粉丝: 0
资源: 1

GSM 03.40通信标准：短消息服务技术实现

GSM协议（gsm03.40 gsm03.38 gsm11.11）

GSM_03.40规范_v7.5.0

GSM 03.40中文版

GSM_DATA.rar_GSM_GSM SMS_SMS GSM PDF_SMS-CP-da

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

gsm.zip_LED GSM_LED点阵屏_gsm led_gsm 点阵_点阵屏

GSM 规范 含GSM03.38 GSM03.39 GSM03.40等

短信息收发有关的规范主要包括GSM_03

GSM规范03.40：3GPP TS SMS短消息服务技术实现

GSM 07.07、GSM03.39、GSM 03.40 协议

最新资源

GSM 规范含GSM03.38 GSM03.39 GSM03.40等