01-02 short message service

HUAWEI MSOFTX3000 Feature Description Contents

Issue 02 (2007-06-10) Huawei Technologies Proprietary i

Contents

2 Short Message Service ..............................................................................................................2-1 2.1 Service Description .......................................................................................................................................2-2

2.1.1 Function Code......................................................................................................................................2-2 2.1.2 Definition .............................................................................................................................................2-2 2.1.3 Benefits ................................................................................................................................................2-3

2.2 Availability ....................................................................................................................................................2-4 2.2.1 Requirements for NEs..........................................................................................................................2-4 2.2.2 Requirements for License ....................................................................................................................2-4 2.2.3 Applicable Versions..............................................................................................................................2-4

2.3 Working Principle..........................................................................................................................................2-5 2.3.1 Networking Structure...........................................................................................................................2-5 2.3.2 Short Message Transfer Path................................................................................................................2-6

2.4 Service Flows................................................................................................................................................2-6 2.4.1 MAP Flows Related to SMS ................................................................................................................2-6 2.4.2 SM MO Flow .......................................................................................................................................2-9 2.4.3 SM MT Flow........................................................................................................................................2-9 2.4.4 Alert SMC Flows ...............................................................................................................................2-11

2.5 Data Configuration......................................................................................................................................2-13 2.5.1 Data Configuration of the MSOFTX3000 .........................................................................................2-13 2.5.2 Data Configuration of the HLR..........................................................................................................2-14

2.6 Service Management ...................................................................................................................................2-15 2.6.1 For Carrier..........................................................................................................................................2-15 2.6.2 For Mobile Subscriber .......................................................................................................................2-15

2.7 Charging and CDR......................................................................................................................................2-15 2.8 Service Interaction ......................................................................................................................................2-16 2.9 Reference ....................................................................................................................................................2-17

2.9.1 Protocols and Specifications ..............................................................................................................2-17 2.9.2 Acronyms and Abbreviations .............................................................................................................2-17

Figures HUAWEI MSOFTX3000

Feature Description

ii Huawei Technologies Proprietary Issue 02 (2007-06-10)

Figures

Figure 2-1 Location of the SMC in a mobile network........................................................................................2-5

Figure 2-2 MAP_SEND_ROUTING_INFO_FOR_SM flow ............................................................................2-7

Figure 2-3 MAP_REPORT_SM_DELIVERY_STATUS flow...........................................................................2-7

Figure 2-4 MAP_READY_FOR_SM flow ........................................................................................................2-8

Figure 2-5 MAP_ALERT_SERVICE_CENTRE flow .......................................................................................2-8

Figure 2-6 SM MO flow.....................................................................................................................................2-9

Figure 2-7 SM MT flow ...................................................................................................................................2-10

Figure 2-8 Flow of alert SMC mobile station reachable ...............................................................................2-11

Figure 2-9 Flow of alert SMC memory of MS ready ....................................................................................2-12

Figure 2-10 Flow of alert SMC SMS succeeds .............................................................................................2-13

HUAWEI MSOFTX3000 Feature Description Tables

Issue 02 (2007-06-10) Huawei Technologies Proprietary iii

Tables

Table 2-1 NEs required to realize the SMS ........................................................................................................2-4

Table 2-2 HUAWEI CS product versions that support the SMS ........................................................................2-4

Table 2-3 Functions of NEs in the transmission of SMs.....................................................................................2-5

Table 2-4 Functions of NEs in the transmission of SMs.....................................................................................2-6

Table 2-5 Interaction between the SMS and other services ..............................................................................2-16

HUAWEI MSOFTX3000 Feature Description 2 Short Message Service

Issue 02 (2007-06-10) Huawei Technologies Proprietary 2-1

2 Short Message Service About This Chapter

The following table lists the contents of this chapter.

Section Describes

2.1 Service Description The function code, function definition of this feature, and the benefits that carriers and mobile subscribers can obtain from this feature.

2.2 Availability The network elements (NEs) that are required for the feature, whether Licenses are required, and the version requirements of the NEs.

2.3 Working Principle The functions of the NEs, and networking requirements.

2.4 Service Flows The service flow of the network when providing this feature.

2.5 Data Configuration The data configurations that are required on the MSOFTX3000 and the UMG8900.

2.6 Service Management The service operations that carriers and mobile subscribers are required to implement when the network provides this feature.

2.7 Charging and CDR The charging and the generation of CDRs when the network provides this feature.

2.8 Service Interaction The relationships and restrictions between this feature and other services or features.

2.9 Reference The protocols and specifications that this feature must comply with, and the acronyms and abbreviations of this chapter.

2 Short Message Service HUAWEI MSOFTX3000

Feature Description

2-2 Huawei Technologies Proprietary Issue 02 (2007-06-10)

2.1 Service Description 2.1.1 Function Code

Name Code

Short message MO/PP (SMS-MO) WMFD-010201

Short message MT/PP (SMS-MT) WMFD-010202

2.1.2 Definition The short message service (SMS) allows subscribers to send or receive information through the short message center (SMC).The information can be texts, pictures, and voices.

"Short" means that the length of information sent in the SMS is short. A point to point (PTP) short message (SM) can have up to 140 bytes in size, that is, 160 ASCII characters or 70 Chinese characters. A broadcast SM can have 82 bytes per page, that is, 92 ASCII characters or 41 Chinese characters. A macro broadcast message can have up to 15 pages that are sent continuously. The PTP SMS allows subscribers to send or receive SMs at any time. The broadcast SMS allows subscribers to receive public information periodically and selectively.

The SMSs fall into two categories: PTP SMSs and PTM SMSs. PTM is short for point to multipoint. The PTM SMSs mainly refers to the cell broadcast SMSs. The PTP SMSs fall into two categories:

z SM MT service (TS21) z SM MO service (TS22)

This chapter describes only the PTP SMSs.

Name Definition

Mobile-Terminated Short Message (SM MT)

It refers to a process in which the SMC sends an SM to the mobile station (MS) and the MS returns a report indicating success or failure of the SMS. The following figure shows the process.

SMC MS

Short message delivery

report



Name Definition

Mobile-Originated Short Message (SM MO)

It refers to a process in which the MS sends an SM to another MS through the SMC and the SMC sends a report indicating success or failure of the SMS to the MS. The following figure shows the process.

SMC MS

Short message submission

report

Alert Service Centre (Alert SC)

z Alert SMC Mobile Station Reachable If the SMS in the SM MT flow fails because of paging no reply or subscriber no answer, the SMC sends an SM status report to the HLR, containing the MSISDN of the callee and the address of the MO SMC. The HLR stores the information in the message waiting data (MWD) list and enables the Mobile Station Not Reachable Flag (MNRF).The VLR also enables the MNRF. At the same time, the SMC temporarily stores the SM that fails to be sent. When the MS makes or receives a call, or re-registers with the network through a location update, the VLR sends an SM ready alert with the cause as mobile subscriber reachable to the HLR if the VLR detects that the MS interacts with the network and the MNRF flag stored in the VLR indicates subscriber not reachable. z Alert SMC Memory Ready If the SMS in the SM MT flow fails because of MS memory overflow, the SMC sends an SM status report to the HLR, containing the MSISDN of the callee and the address of the SMC. The HLR stores the information in the MWD list and enables the Mobile Station Memory Capacity Exceeded Flag (MCEF). At the same time, the SMC temporarily stores the SM that fails to be sent. If the MS deletes an SM and the memory released can be used to receive new messages, the MS sends a message indicating memory ready to the MSC server. Upon receipt of the message, the MSC server sends a message indicating memory of MS ready to the HLR. The HLR receives the message and checks the MCEF. The HLR sends an SM ready alert to the SMC specified in the MWD list.

2.1.3 Benefits Beneficiary Description

Carriers The SMS can help to provide value added services, information inquiry services, and services such as website SMS and pictures. It also expands service types and improves the average revenue per user (ARPU).


Feature Description


Beneficiary Description

Mobile subscribers The SMS can be used to send information. It can also be used to receive information such as stock prices, weather reports, sports news, and bank accounts. This eases information query and makes subscribers feel closer to carriers.

2.2 Availability 2.2.1 Requirements for NEs

The SMS is implemented through the interworking between the MS/UE, the radio access network (RAN), and the core network (CN). Table 2-1 lists the network elements (NEs) that are required to realize the SMS.

Table 2-1 NEs required to realize the SMS

MS/UE BTS/NodeB

BSC/RNC

MSC Server

MGW SGSN VLR HLR SMC

MS = Mobile Station; UE = User Equipment, BTS = Base Transceiver Station; BSC = Base Station Controller; RNC = Radio Network Controller; MSC = Mobile Switching Center; MGW = Media Gateway; SGSN = Serving GPRS Support Node; VLR = Visitor Location Register; HLR = Home Location Register; SMC = Short Message Center

The symbol indicates that the NE is required.

2.2.2 Requirements for License The SMS is an optional feature of the radio access network (RAN) provided by Huawei Technologies Co., Ltd. (called Huawei in this manual). To use the SMS, both a License of the MSOFTX3000 and that of the SMC are required.

2.2.3 Applicable Versions Table 2-2 lists the HUAWEI circuit switched (CS) domain product versions that support the SMS.

Table 2-2 HUAWEI CS product versions that support the SMS

NE Product Applicable Version

MSC server MSOFTX3000 V100R002 and later versions

MGW UMG8900 V200R002 and later versions



2.3 Working Principle 2.3.1 Networking Structure

As a service processing system independent of the GSM/UMTS network, the SMS system performs the following functions:

z Submitting, storing, and forwarding SMs z Interworking with the PSTN, ISDN, and PSPDN to transmit SMs from external short

message entities (ESMEs) such as manual stations and automatic stations

The SMC, as the SMS system provided by Huawei, brings together functions of the SMS-GMSC, SMS-interworking MSC (IWMSC), and service center (SC). Figure 2-1 shows the location of the SMC in a mobile network.

Figure 2-1 Location of the SMC in a mobile network

RAN

SMC InfoX

InternetSGSN GGSN

HLR

MSC/VLR

PSTN/ISDN/PSPDN

MSC/VLR: Mobile Switching Center/Visited Location Register HLR: Home Location Register SMC: Short Message Center Infox: Infox Integrated Gateway RAN: Radio Access Network SGSN: Serving GPRS Support Node GGSN: Gateway GPRS Support Node PSTN: Public Switched Telephone Network ISDN: Integrated Services Digital Network PSPDN: Packet Switched Public Data Network

In a CS core network, the NEs related to the SMS system are the MSC, VLR, SGSN, and HLR. Table 2-3 lists the functions of the NEs in the transmission of SMs.

Table 2-3 Functions of NEs in the transmission of SMs

NE Function

MSC z After an SM is sent from the MS to the MSC through the RAN, the MSC forwards the SM to the SMC.

z After an SM is sent from the SMC to the MSC, the MSC obtains the routing and subscriber information from the VLR and forwards the SM to the MS through the RAN.


Feature Description


NE Function

VLR z It authenticates the subscriber to whom the SMC sends an SM. z It provides routing for the MSC when the SMC sends an SM to the

subscriber through the MSC.

SGSN z When an SM sent by the MS reaches the SGSN through the RAN, the SGSN forwards it to the SMC.

z After receiving an SM sent from the SMC, the SGSN forwards it to the MS through the RAN.

HLR z Before the SMC sends an SM, the HLR searches the MSC that serves the subscriber.

z If authentication is required when the MSC sends an SM, the MSC requests the authentication set from the VLR. If there is no authentication set in the VLR, the MSC requests it from the HLR. In all other cases, the MSC does not request basic subscriber information from the HLR when sending an SM.

2.3.2 Short Message Transfer Path When different network access modes are used, the SM transfer paths are different. Table 2-4 lists the details.

Table 2-4 Functions of NEs in the transmission of SMs

Network Access Mode

Short Message Transfer Path

SGSN GMSC -> SGSN -> MS If the SGSN fails to forward an SM to the MS, the GMSC sends it to the VMSC. This is similar to the transfer means used in the GSM network.

MSC GMSC -> VMSC -> MS

2.4 Service Flows An SM can be transferred through the packet switched (PS) domain or the CS domain. This section described signaling flows of the CS domain only.

2.4.1 MAP Flows Related to SMS

MAP_SEND_ROUTING_INFO_FOR_SM The flow is started by the GMSC to query the location information (MSC number or SGSN number) of the subscriber from the HLR. Thus, the SM can be routed to the MSC or SGSN. Figure 2-2 shows the flow.



Figure 2-2 MAP_SEND_ROUTING_INFO_FOR_SM flow

HLR

MAP_SEND_ROUTING_INFO_FOR_SM

MAP_SEND_ROUTING_INFO_FOR_SM_ACK

GMSC

If the GMSC supports the general packet radio service (GPRS), the HLR may return two numbers: an SGSN number and an MSC number. If the GMSC does not support the GPRS, the HLR returns one number and whether the number is an SGSN number or an MSC number is determined by MOD SMDP.

MAP_REPORT_SM_DELIVERY_STATUS The flow is started by the GMSC to inform the HLR whether the SM sending succeeds or fails. Figure 2-3 shows the flow.

z If the message sending succeeds, the HLR clears the MNRF and MCEF of the subscriber and starts the Alert_Service_Centre flow to the SMC specified in the MWD list.

z If the message sending fails, the HLR saves the address of the SMC or the cause of MS not reachable to the MWD list.

Figure 2-3 MAP_REPORT_SM_DELIVERY_STATUS flow

HLR

MAP_REPORT_SM_DELIVERY_STATUS

MAP_REPORT_SM_DELIVERY_STATUS _ACK

GMSC

MAP_READY_FOR_SM The flow is started by the VLR/SGSN to inform the HLR that the MS memory is ready. Upon receipt of the message, the HLR clears the MCEF and starts the


Feature Description


MAP_ALERT_SERVICE_CENTRE flow to the SMC if the address of the SMC exists in the MWD list. If the HLR detects that the MCEF and the MNFG/MNRG of the subscriber are not enabled, which shows that the MAP_REPORT_SM_DELIVERY message is not sent to the HLR, the HLR sets a timer. After the message is received, the HLR sets the flag bits of the MCEF and the MNFG/MNRG to 0.

Figure 2-4 shows the flow.

Figure 2-4 MAP_READY_FOR_SM flow

HLR

MAP_READY_FOR_SM

MAP_READY_FOR_SM _ACK

VLR/SGSN

MAP_ALERT_SERVICE_CENTRE When processing the MAP_READY_FOR_SM flow, location update flow, or GPRS location update flow, the HLR starts the MAP_ALERT_SERVICE_CENTRE flow to the SMC and informs the SMC to resend the SM to the subscriber if the MNRF/MNRG of the subscriber is not reachable and the address of the SMC exists in the MWD list.


Figure 2-5 MAP_ALERT_SERVICE_CENTRE flow

SMC

MAP_ALERT_SERVICE_CENTRE

MAP_ALERT_SERVICE_CENTRE_ACK

HLR

As the SMC provides the functions of an IWMSC, the MAP_Alert_Service_Centre message is sent from the HLR to the IWMSC logically.



2.4.2 SM MO Flow In the SM MO flow, a subscriber uses the MS to send an SM to the SMC. Figure 2-6 shows an SM MO flow.

Figure 2-6 SM MO flow

MS VMSC/SGSN VLR SMC

2.SEND_INFO_FOR_MO_SMS (*)

3.SEND_INFO_FOR_MO_SMS_ACK (*)

4.MO_FORWARD_SHORT_MESSAGE(RP_DATA)

6.Short MessageAcknowledgement(RP_ACK)

7.ShortMessage Error(RP_ERROR)

1. ShortMessage(RP_Data)

5.MO_FORWARD_SHORT_MESSAGE_ACK(RP_ACK)

The messages with "(*)" are applicable to the MSC only, not the SGSN.

1. The MS sends an SM to the VMSC server or the SGSN through the A/Iu interface. 2. Upon receipt of the SMS request, the VMSC server sends a subscriber data check

request to the VLR based on the MSISDN of the MS. 3. The VLR checks the subscription information and whether the local office supports the

SMS, and sends the result to the VMSC server. 4. The VMSC server analyzes the result. If the local office does not support SM MO, or it

registers the outgoing call barring service, the VMSC server directly sends a reject message (RP_ERROR) to the MS. Otherwise, the VMSC server obtains the address of the SMC from the SM MO and transparently transmits the SM MO to the SMC.

5. Upon receipt of the request, the SMC checks whether the data is valid. If yes, the SMC sends a message to the VMSC server or the SGSN to acknowledge the transparent transmission of the SM MO.

6. Upon receipt of the message, the VMSC server or the SGSN sends the result of SM MO sending to the MS.

2.4.3 SM MT Flow In an SM MT flow, the SMC sends an SM to the MS. Figure 2-7 shows an SM MT flow.


Feature Description


Figure 2-7 SM MT flow

MS VMSC/SGSN VLR HLR SMC

(1) SEND_ROUTING_INFO_FOR_SM

(2) SEND_ROUTING_INFO_FOR_SM_ACK(3).MT_FORWARD_SHORT_MESSAGE

(RP_DATA)

(4) SEND_INFO_FOR_MT_SMS (*)

(6)Page

(7) Page response

(9) SEND_INFO_FOR_MT_SMS_ACK (*)

(12) MT_FORWARD_SHORT_MESSAGE_ACK(RP_ACK)

(5) PAGE/SEARCH_FOR_MOBILE_SUBSCRIBER (*)

(8) PROCESS_ACCESS_REQUEST_ACK/SEARCH_FOR_MOBILE_SUBSCRIBER_ACK

(*)

(11) Short Message Acknowledgemen t(RP_ACK)

(10).Short Message (RP_DATA)

The messages with "(*)" are applicable to the MSC only, not the SGSN.

1. Upon receipt of the SM MT, the SMC obtains the called number and uses it to request the routing information from the HLR.

2. Upon receipt of the routing information, the HLR returns a response.

When the priority of the SM MT is high, the HLR returns a normal response to the SMC even if the MNRF and the MCEF are enabled.

The HLR searches the information of the subscriber in the database and returns a message with a failure cause to the SMC if one of the following occurs:

z The subscriber does not exist. z Roaming is not allowed. z Carrier determined call barring barring of all incoming calls or SMs MT z The SM MT service is not supported. z The MNRF is enabled. z The MCEF is enabled. z The subscriber is deleted by the MSC server/VLR to which the subscriber roams.

If none of the preceding events occurs, the HLR sends the MSC number or the SGSN number to the SMC.

3. By using the MSC number, the SMC sends a transparent transmission request to the VMSC server.

4. Upon receipt of the request, the VMSC server sends a request for checking SM MT subscriber data to the VLR.

5. The VLR checks the subscription data and mobility management status:



If the subscriber cannot be paged because the subscriber does not support SM MT, the handset is powered off, the MNRF is enabled, or the roaming is not allowed, the VMSC server sends a failure response to the SMC.

If the location area of the MS is known, the VMSC server starts paging the MS in the specific location area.

If the location area of the MS is unknown, the VMSC server starts paging the entire area controlled by the MSC server.

6. The VMSC server pages the MS. 7. The MS sends a response to the VMSC server. 8. (8)(9)(10): Upon receipt of the response, the VMSC server starts the subscriber access

process. After the process is complete, the VMSC server sends the SM to the MS through the Iu interface.

9. (11)(12): After receiving the result from the MS, the VMSC server sends it to the SMC. 10. If there are multiple SMs, that is, the RP-MMS exists in the transparent transmission

request, the connections are maintained and (3), (10), (11), and (12) are repeated. 11. If no additional message is to be sent, all connections are released.

2.4.4 Alert SMC Flows There are two scenarios:

z The activated MS re-alerts the SMC after the SMS fails because of mobile subscriber not reachable.

z The MS alerts the SMC when its memory is ready.

Alert SMC Mobile Station Reachable Figure 2-8 shows the flow.

Figure 2-8 Flow of alert SMC mobile station reachable

MSC/SGSNMS VLR HLR SMC

(4) Ready_for_SM_ack

(5) Alert SC

(6) Alert SC ack

(3) Ready_For_SM/Update_Location

(2)Process_Access_Request/Update_Location_Area (*)

(1) CM Service Req (**),Page resp or Location

Updating

The flow (2) is not applicable to the SGSN. Alert SC: Alert_Service_Centre


Feature Description


1. The MS makes or receives a call or updates the location to re-connect with the network. 2. The MSC server sends an access request to the VLR if the MS makes or receives a call.

Or the MSC server checks the data of the subscriber who updates the location if the MS updates the location.

3. The VLR checks subscriber data. If the VLR detects that the MNRF of the subscriber is enabled, the VLR clears the MNRF and informs the HLR that the SM is ready with the cause as mobile subscriber reachable. The VLR directly sends a location update request to the HLR in the case of a location update flow.

4. If the HLR receives the SM ready alert, it checks the dynamic data of the subscriber. If the MNRF is enabled, the HLR clears it, sends an Alert_Service_Centre message to the SMC, and sends a message to the VLR to acknowledge the sending of the SM ready alert. If the HLR receives a location update request and the MNRF in the dynamic data of the subscriber is enabled, the HLR clears the MNRF, sends an Alert_Service_Centre message to the SMC, and continues the location update flow.

The HLR sends the Alert_Service_Centre message to all SMCs specified in the MWD list. The HLR sends the Alert_Service_Centre message only when the MCEF of the MS is set to False.

5. Upon receipt of the Alert_Service_Centre message, the SMC returns a response and tries to send SMs again.

Alert SMC Memory of MS Ready Figure 2-9 shows the flow.

Figure 2-9 Flow of alert SMC memory of MS ready

MS MSC/SGSN HLR SMC

(1) SM memory capacity available

(2) READY_FOR_SM

(3) READY_FOR_SM_ACK

(5) ALERT_SERVICE_CENTRE

(6) ALERT_SERVICE_CENTRE_ACK

(4) SM memory capacity available

1. The MS sends a memory ready message to the MSC server through the Iu interface. 2. The MSC server sends an SM ready message with the cause as memory of MS ready to

the HLR.



3. Upon receipt of the message, the HLR checks the dynamic data of the subscriber. If the MCEF of the subscriber is enabled, the HLR clears it, sends an Alert_Service_Centre message to the MSC server, and sends an SM ready message to the VLR. Upon receipt of the message, the MSC server returns a response to the MS.

4. Upon receipt of the Alert_Service_Centre message, the SMC returns a response and tries to resend the SM. The timing of the SM resending upon SMS failure is controlled by the SMC through the resending interval setting.

Alert SMC SMS Succeeds If the SMS succeeds, the HLR clears the MNRF and the MCEF and starts the Alert_Service_Centre flow to the SMC whose address is in the MWD list.


Figure 2-10 Flow of alert SMC SMS succeeds

GMSC HLR SMC

(1) REPORT_SM_DELIVERY_STATUS(Successful Transfer)

(2) REPORT_SM_DELIVERY_STATUS_ACK

(3) ALERT_SERVICE_CENTRE

(4) ALERT_SERVICE_CENTRE_ACK

1. The GMSC server sends an SMS succeeds message to the HLR. 2. Upon receipt of the message, the HLR returns a response. 3. The HLR sends an Alert_Service_Centre message to the SMC. 4. The SMC returns an Alert_Service_Centre_ACK message to the HLR.

2.5 Data Configuration The SMS is implemented through the signaling system. Therefore, you must configure data only on the MSC server and the HLR, not on the MGW.

2.5.1 Data Configuration of the MSOFTX3000 To implement the SMS, you must configure the signaling and service data of the MSOFTX3000 for interworking with the SMC.


Feature Description


Adding MTP Data To add MTP data, proceed as follows:

Step 1 Add an MTP destination signaling point (DSP) by using ADD N7DSP.

Step 2 Add an MTP linkset by using ADD N7LKS.

Step 3 Add an MTP route by using ADD N7RT.

Step 4 Add an MTP link by using ADD N7LNK.

----End

For details about the configuration steps and parameter descriptions, refer to the HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide.

Adding SCCP Data To add SCCP data, proceed as follows:

Step 1 Add an SCCP DSP by using ADD SCCPDSP. Set Network indicator to a value based on the actual requirements from the SMC to the SCCP DSP. You can set it to National network, for example.

Step 2 Add an SCCP sub-system number by using ADD SCCPSSN. Add the MSC and SCCP management subsystem (SCMG) to the remote SMC. The local MSC, VLR, SCMG are already configured in the office information data. Therefore, run LST SCCPSSN to list the values and there is no need to configure the data again.

Step 3 Add an SCCP GT group by using ADD SCCPGTG. Specify the GT group to which the SCCP GT group belongs during the configuration.

Step 4 Add an SCCP global title by using ADD SCCPGT. Select a general global title. Select a network indicator based on the actual requirements. Set Numbering Plan to ISDN/telephony numbering Plan. Enter an SMC number such as 8613900007 as the GT address information.

----End

Setting MAP Feature Configuration Step 1 Run LST MAPACCFG to see whether Support SMMO function and Support SMMT

function are set to Yes.

Step 2 If not, run SET MAPACCFG to set them to Yes.

----End

2.5.2 Data Configuration of the HLR To implement the SMS, you must configure the signaling and service data of the HLR for interworking with the SMC.

For details about the configuration steps and parameter descriptions, refer to related HLR manuals.



2.6 Service Management 2.6.1 For Carrier

The following operations can be performed on an HLR client:

z Enable or Disable the SMS. z List the path of an SM. z Modify the path of an SM.

For details, refer to related operation manuals of the HLR.

2.6.2 For Mobile Subscriber The address of the SMC can be configured.

2.7 Charging and CDR

Difference Between SMS CDR and Voice Call CDR In an SMS call detail record (CDR), there is no difference between an IN subscriber and an ordinary subscriber.

The SMS uses signaling or voice channels to send characters. An SMS CDR, different from an ordinary voice call CDR, contains the following elements:

z Number of bytes: It indicates the actual number of bytes of the UserPart in an SM. It is the actual length of an SM after decoding.

z Address of SMC: It indicates which SMC is used for communication.

SMS CDR of Caller If an SM is successfully sent to the SMC, the VMSC server that serves the subscriber who sends an SM generates an SMS CDR for the caller.

The SMS CDR contains the IMSI and MSISDN of the caller, the number of the caller, the SMC address in E.164 format, the charging flag, the additional charging flag, and the content of the SM.

The CDR files are saved in the iGWB. Based on FTAM or FTP, the iGWB sends the CDR files to the billing center through the TCP/IP connection. FTAM is short for File Transfer Access and Management Protocol.

SMS CDR of Callee When a subscriber receives an SM, the VMSC server that serves the subscriber generates an SMS CDR for the callee.

The SMS CDR contains the IMSI and MSISDN of the callee, the number of the caller, the SMC address in E.164 format, the charging flag, the additional charging flag, and the content of the SM.


Feature Description


The CDR files are saved in the iGWB. Based on FTAM or FTP, the iGWB sends the CDR files to the billing center through the TCP/IP connection.

2.8 Service Interaction Table 2-5 shows how the SMS interacts with other services.

Table 2-5 Interaction between the SMS and other services

Service Interaction

Call barring The SM MO service is related to the following services: z Barring of all outgoing calls (BAOC) z Barring of outgoing international calls (BOIC) z Barring of outgoing international calls except those directed to the

home PLMN (BOIC-exHC) The SM MT service is related to the following services: z Barring of all incoming calls (BAIC) z Barring of incoming calls when roaming outside the home PLMN

country (BICRoam)

Call forwarding It does not interact with the SMS. Hot billing It interacts with the SM MO service.

When a subscriber subscribes to the hot billing service, a hot billing flag is generated for each SM sent or received. The hot billing flag provides the charging data for all services of a subscriber. It is immediately sent to the billing center.

Handover No SM can be sent during an intra-MSC or inter-MSC handover. An SM can be sent after the handover is complete. A handover request is rejected when an SM is being transmitted. The handover continues after the transmission of an SM is complete.

IMSI attach/IMSI detach

It interacts with the SM MT service. When the VLR sets the subscriber to IMSI detach, the subscriber is not reachable. If the SM is sent to a subscriber who is in IMSI detach state, the SM is stored in the SMC. After the IMSI is attached, the SMC tries to resend the SM.



2.9 Reference 2.9.1 Protocols and Specifications

z MNRF: Mobile station Not Reachable Flag z MNRG: Mobile station Not Reachable for GPRS flag GPRS z MNRR: Mobile station Not Reachable Reason z MCEF: Memory Capability Exceed Flag z MWD-List: Message Waiting Data-List

2.9.2 Acronyms and Abbreviations Acronym/Abbreviation Full Name

ARPU Average Revenue Per User

BAIC Barring of All Incoming Calls

BAOC Barring of All Outgoing Calls

BICRoam Barring of Incoming Calls when Roaming Outside the Home PLMN Country

BOIC Barring of Outgoing International Calls

BOIC-exHC Barring of Outgoing International Calls except those directed to the Home PLMN Country

ESME External Short Message Entity

GGSN Gateway GPRS Support Node

GMSC Gateway Mobile Switching Center

GPRS General Packet Radio Service

GSM Global System for Mobile Communications

HLR Home Location Register

ISDN Integrated Services Digital Network

MS Mobile Station

MSC Mobile Switching Center

MSISDN Mobile Station International ISDN Number

PSPDN Packet Switched Public Data Network

PSTN Public Switched Telephone Network

RAN Radio Access Network

SGSN Serving GPRS Support Node


Feature Description


Acronym/Abbreviation Full Name

SMC Short Message Center

SM MT Mobile-Terminated Short Message

SM MO Mobile-Originated Short Message

SMS Short Message Service

UMTS Universal Mobile Telecommunication Services

ContentsFiguresTables2 Short Message ServiceAbout This Chapter2.1 Service Description2.1.1 Function Code2.1.2 Definition2.1.3 Benefits

2.2 Availability2.2.1 Requirements for NEs2.2.2 Requirements for License2.2.3 Applicable Versions

2.3 Working Principle2.3.1 Networking Structure2.3.2 Short Message Transfer Path

2.4 Service Flows2.4.1 MAP Flows Related to SMS2.4.2 SM MO Flow2.4.3 SM MT Flow2.4.4 Alert SMC Flows

2.5 Data Configuration2.5.1 Data Configuration of the MSOFTX30002.5.2 Data Configuration of the HLR

2.6 Service Management2.6.1 For Carrier2.6.2 For Mobile Subscriber

2.7 Charging and CDR2.8 Service Interaction2.9 Reference2.9.1 Protocols and Specifications2.9.2 Acronyms and Abbreviations

01-02 short message service

Documents