06-sms

OPEN INFORMATIONDESCRIPTION 1 (23)

SG//ERA//FZ/BIFE Fredrik Thyden 2001-10-03 F 44/190 46-FAD 104 08 Uen

ERA//FZ/BIFC (Mikael Österberg)

Uppgjord — Prepared Datum — Date Rev Dokumentnr — Document no

Godkänd — Approved Kontr — Checked Tillhör/referens — File/reference

E

Short Message Service

Abstract

The purpose of this document is to describe Short Message Service (SMS) from a datatranscript point of view.

Contents Page

1 Revision Information 2

2 Description 22.1 Abbreviations 22.2 Concerned Nodes 32.3 General 32.4 Traffic Cases 4

3 Data Transcript Impacts 123.1 General 123.2 Subfile 10000 - APT Size Alterations (MSC/VLR) 133.3 Subfile 10000 - APT Size Alterations (HLR) 153.4 Subfile 13000 - Exchange Properties 153.5 Subfile 15100 - Charging 193.6 Subfile 15200 - C7 - Data 193.7 Subfile 15300 - Route Characteristics 193.8 Subfile 15350 - Route Allocation 203.9 Subfile 15600 - B-Number Analysis 203.10 Subfile 15700 - Pre B-Number Analysis 203.11 203.12 Subfile 15900 - Special Purpose Digit Analysis 203.13 Subfile 16100 - Telecommunication Service Analysis 213.14 Subfile 75200 - Semipermanent Connections 213.15 Subfile 75300 - Deblocking C7 213.16 Subfile 75500 - SCCP Data (MSC/VLR) 213.17 Subfile 75500 - SCCP Data (HLR) 22

4 Miscellaneous Information 224.1 Class 22

SEIF v2.3,


2001-10-03 F 44/190 46-FAD 104 08 UenDatum — Date Rev Dokumentnr — Document no

E

1 Revision Information

Revi-sion

Impacts Prepared Date

A New document ERAJOGI 96-09-10

B - Minor changes in language ERADINN 97-05-26

- Updated DT to suit example inInfo-Model

C Updated document to SS R7 ETOTRRE 98-09-21

PD1 Update document to SS R8s ETOSADO 99-06-2

PD2 Minor R8s updates ERAMACI 99-10-14

D Updated to R8.0, minor changes QRAINHA 00-02-14

E Updated to R8.1, minor changes ERATYDE 01-08-20

F Reviewed for CN 1.5, Minorchanges

ERATYDE 01-10-03

2 Description

2.1 Abbreviations

AS Application System

BNT B-Number Type

CC Charging Case

GPRS General Packet Radio Service system

IWMSC Interworking Mobile Switching Centre

MO Mobile Originated

MT Mobile Terminated

NAPI Number Plan Indicator

SC Service Center

SM Short Message

SMS Short Message Service

TON Type Of Number

DSO Digit Series Origin



E

2.2 Concerned Nodes

• MSC/VLR

• HLR

2.3 General

The SMS function makes it possible to send text strings with up to 160characters between mobiles.

Starting with R8s, we have an option of sending SMS through either CircuitSwitching (GSM) or Packet Switching (GPRS) network.

The messages is only sent on MAP level (C7-signalling) and no speech/dataconnection is needed.

The Short Message Service involves the Service Center (SC), GSMS (SMSGateway-MSC) and IWSMS (SMS InterWorking MSC). In an AXE system arethe GSMS and IWSMS located in MSC/VLR whilst the SC is located in theMXE-node. GSMS and IWSMS consist of central software only.

HLR and VLR will be used during different MO-SMS and/or MT-SMS steps.

When first using the service MO-SMS, the subscriber stores the address tohis/her home-SC manually in the MS. Note, the address is not stored in theSIM-card and must therefore be re-entered when changing mobile.

The SC requires the SC address in international format (BNT=1). If theaddress is entered in another format by the subscriber this will have to beconverted to international format in the B number analysis. See DT Impacts.

For the feature Mobile subscriber priority level for channel allocation (seedoc. 64/190 46-FAD 104 08) there are four new Exchange properties ofconcern for SMS.



E

2.4 Traffic Cases

2.4.1 Mobile Originated SMS

1

MSC

VLRBSC

SC

GMSC

IWMSC

SC=46 70 702 xxxx

TT=0,SC#

FWD SM

EXROI:R=IWSMSSMSFMOSMTRTYPE-1C7GSI:TT=1

EXROI:R=MSMO...C7GSI:TT=0...

SC# + BnumberMO-SM

HLR

HGSDC:MSISDN=4670...,SUD=TS22-1;

TT=1, SC

#

FWD

SM

2

3

Figure 1 Mobile originating SMS

2.4.1.1 From Mobile Station to MSC/VLRArrow 1 (figure 1)

A subscriber wants to make a Mobile Originated SM (MO-SM). The MSsends up the SC-address and the B-number (the receiver of the message)together with the actual message.

A check to see if the service is provided by the system (see subfile 16100)is made in the MSC.

Example 1 MML command definitions

MGTEI:TEC=SMSMO, TSC=3;MGTCI:TSC=3, WSIG=NOIS.....

The TEC=SMSMO is received from the MS in the call set up message.

A subscription check is made in the VLR for MO-SM. The subscriber serviceis corresponding to Telecommunication Service 22 (TS22). A normalauthentication check is also made.

2.4.1.2 From MSC/VLR to IWSMSArrow 2 (figure 1)



E

The block MSMO receives and handles the originating of SM. An internalsoftware route MSMO is used. Here we derive the B origin in which to analysethe SC-address and get the charging case for this first leg of the call.


EXROI: R=MSMO, DETY=MSMO;EXRBC: R=MSMO,

MIS3=0, (BO in use, charging performed)BO=93; (BO used to get CC)

The Pre B-number analysis is used to diversify between different BNT valuesof the received SC address.


PNBSI:BO=93, BNT=1, OBA=93;PNBSI:BO=93, BNT=2&4, OBA=80;

BNT Unknown and National are modified into BNT=1 International.


ANBSI:B=80-00946, BNT=1, M=3, F=OR;ANBSI:B=80-070, BNT=1, M=1-46, F=OR;ANBSI:B=80-70, BNT=1, M=0-46, F=OR;

Charging is performed, here separating international SM from national.


ANBSI:B=93-44, CC=8, D=9-9; (Charging depending)ANBSI:B=93-46, CC=7, D=9-9; (on SC-address)ANBSI:B=93-49, CC=8, D=9-9;

Barring analysis is performed in the same way as in mobile originating callexcept that the service centre number is analysed to point out the destinationcode instead of the called subscriber number.

The VLR is using the SC-address in the SCCP analysis to find the InterWorking MSC (IWMSC). The IWMSC is the interface towards the SC.


C7GSI: TT=0,NP=1,NA=4,NS=46 70 702.., (SC-address)GTRC=8; (GTRC for terminating)

C7GCI:GTRC=8, PSP=OWNSP; (IWMSC in same node)

In SS R7 it is not longer possible to set the parameter TERM in C7GSI. That’swhy we have to send it to a GTRC. In the GTRC the PSP is set to “OWN”,witch indicates that the IWSMS is "located" in the same node. The IWMSCmight be located in another node/network.



E

2.4.1.3 From IWSMS to SCArrow 3 (figure 1)

Forwarding of the SM is controlled by the IWSMS. The charging leg towardsthe SC is derived from the software route IWSMS.


EXROI:R=IWSMS, DETY=IWSMS;EXRBC:R=IWSMS,

MIS3=1, (BO in use, charging performed)BO=92; (BO used to get CC)

ANBSI:B=92-46, CC=7;

SC-address is analysed in international format. For International subscribers,the IWSMS function in their respective country will be used.

IWSMS is using the SCCP to find the SC. To be able to separate theSC-address from the IWSMS, another Translation Type (TT) is used. Theused TT is set with Exchange-properties. The SC can not handle all TTvalues. TT=1 is recommended.


MGEPC:PROP=SMSFMOSMTRTYPE-1; (TT=1 will be used)

C7GSI: TT=1,NP=1,NA=4,NS=46 70 702.., (Part of SC-address)GTRC=3; (GTRC towards SC)

The GTRC towards the SC is defined.


C7GCI:GTRC=3, PSP=2-800, PTERM;

The subsystem number is defined.


C7NPI:SP=2-800, CON;C7NSI:SP=2-800, SSN=12;

The subsystem number for the SC is 12.

A signalling route and a C7 connection is defined. The C7-link to the SC musthave a high T7MS value (Time supervision for delay of acknowledgement).Recommended value is 2000 (normal is 500).


C7LPC:PARMG=1, T7MS=2000;C7SLI:LS=2-800, PARMG=1,.......C7RSI:DEST=2-800,......



E

EXROI:R=SMSO...EXSCI:NAME=SMS...

In our example, the signalling is performed on Timeslot 1 towards the SC. Iftwo Signalling Links (SL) are to be used, two PCM have to be defined. Note,the SC can only be connected to one node, even if more than one SL is used.

The message and the B-number are delivered to the SC. The SC sends backa successful sending of SMS message to the MS. The message is stored inthe SC until the sending/termination is completed or rejected/expired. Neitherthe sender or the receiver (B-number) of the SMS have any subscriber recordsin the SC. A subscriber record will be included in a later revision of the MXE.

It is possible to restrict originating SM for mobile subscriber which havelocal/regional subscription (see doc. 59/190 46-FAD 104 08).

2.4.2 Mobile Terminating SMS

1

HLR

HGSDC:MSISDN=4670...,SUD=TS21-1;2

3

MSCBSC

MT-SM

B-NUMBER

B NU

MBER

, TT=0

EXROI:R=MSMTC7GSI:TT=0 SM

VLR-ADDRESS

B.NUMBER, TT-0

EXROI:R=GSMS,...C7GSI:TT=0...

SMS-IWMSC

SC

SMS-GMSC

VLR

MT-SM

MT-SM

MT-SM

4

5

Figure 2 Mobile terminating SMS

2.4.2.1 From SC to GSMS

Arrow 1 (figure 2)

The SC delivers a terminating SM to the Gateway SMS (SMS-GMSC). TheSC always sends terminating SM to the same GMSC. The SM is routed onthe B-number.



E

2.4.2.2 From GSMS to HLR

Arrow 2 (figure 2)

The GSMS makes an interrogation to the HLR (routed on the B-number in theSCCP-analysis) to locate the subscriber.

Note, if there is no valid HLR for the B-number, absent number-series in theSCCP-analysis, the AXE will send the signal System failure to the SC. The SCregards this as a temporary failure and will continue try to send the messageuntil a time release in the SC triggers. The time-release is normally set to 24h.


C7GSI: TT=0,NP=1,NA=4,NS=4670 75.., (B-number)GTRC=1; (HLR in external node)

The called address (NS) is the B-number (MSISDN).

The GTRC towards HLR is defined:



A charging case is derived from the software route GSMS.


EXROI:R=GSMS, DETY=GSMS;EXRBC:R=GSMS, MIS3=1, (BO in use, charging performed)

BO=91; (BO used to get CC)

ANBSI:B=91-44, CC=8; (Charging depending on B-number)ANBSI:B=91-46, CC=7;ANBSI:B=91-49, CC=8;

The number analysed is the B-number, MSISDN.

2.4.2.3 From HLR to GSMS

Arrow 3 (figure 2)

The HLR checks if the subscriber has subscription of the service "terminatingSMS". The service corresponds to the Telecommunication service 21(SUD=TS21).

If no IMSI is connected to the B-number, the AXE will send the signal"Unknown Subscriber" to the SC, the SC will then release the message.

The HLR checks where the subscriber is located, i.e. in which VLR. Instead ofsending a roaming number back to the GMSC (no speech channel is needed),the HLR sends back the VLR-address to the GMSC.



E

The calling address (VLR/GMSC-address) is used to route the messageback to the GSMS.


C7GSI:TT=0,....NS=4670757, GTRC=1;C7GCI:GTRC=1, PSP=2-300, PTERM;

2.4.2.4 From GSMS to MSC/VLR (MSMT)

Arrow 4 (figure 2)

The GMSC sends the SM to the VLR where the subscriber is roaming (usingthe VLR address received from HLR).


C7GSI:TT=0,....NS=46707670, GTRC=2; (To MSC2)

2.4.2.5 From MSC/VLR to MSArrow 5 (figure 2)

The VLR receives the SM and analyse it.


C7GSI:TT=0,NP=1,NA=4,NS=46707670;GTRC=8;

C7GCI:GTRC=8, PSP=OWNSP;

The VLR terminates the SM.

A check is made to see if the service is provided by the system (see subfile16100).


MGTEI:TEC=SMSMT, TSC=4;MGTCI:TSC=4, WSIG=NOIS.....

The TEC=SMSMT is received from the GSMS in the set-up message.

A charging case is derived from the software route MSMT.


EXROI:R=MSMT, DETY=MSMT;EXRBC:R=MSMT, MIS3=0, (BO in use, charging performed)

BO=94; (BO used to get CC)

ANBSI:B=94-44, CC=8; (Charging depending on B-number)ANBSI:B=94-46, CC=7;ANBSI:B=94-49, CC=8;



E

The terminating charging leg is based on the B-number.

If the MS is reachable, the SM is sent. A SM-complete message is sent backto the SC (on SCCP level).

It is possible to restrict terminating SM for mobile subscribers which havelocal/regional subscription (see doc. 59/190 46-FAD 104 08)

2.4.3 Service Centre Alert

HGSDC:MSISDN=4670...,SUD=TS21-1;

SMBSC

MSCVLR

9

HLR

GMSC

SC

SMS-IWMSC

SMSALERTTRTYPE-1C7GSI:TT=1...

ALERT, TT=0

ALERT,

TT=

1

SC=46 70 702xxxx

B.NO, TT-0

C7GSI:TT0...

ATTACH

ALE

RT

, TT

=0

B-NU

MBER

, TT=0

8

7

6

5

4

3

2

1

Figure 3 Service Centre Alert, re-transmitting of SMS

If the transmission of the SM is not successful, the VLR informs the GSMSand the GSMS sends a "set message waiting data" message back to the HLR(on SCCP level). A flag is set in the HLR and the SC-address is stored in themessage data waiting list (in HLR). The SC is also informed and the SM isstored. The SC then retransmits the SM with certain intervals (SC depending).

The VLR also sets a flag telling that as soon as the MS is available again,the HLR will be informed.



E

2.4.3.1 From MSC/VLR to HLRArrow 1-2 (figure 3)

When the MS gets available again (attach, periodic LU, etc.), the VLR informsthe HLR (on SCCP level).


C7GSI:TT=0,...NS=46707579, GTRC=1;C7GCI:GTRC=1, PSP=2-700, PTERM;

2.4.3.2 From HLR to IWSMSArrow 3 (figure 3)

The HLR has stored the SC-address (Message Data Waiting list, MDW) andsends the "SC-alert" to the IWSMS.


C7GSI:TT=0,NP=1,NA=4,NS=46 70 702..,GTRC=1;

The message is terminated in that MSC/VLR where the IWSMS is located.The called address (NS) is the IWSMS-address (SC-address). TT=0 is used.


C7NPI:SP=2-300, CON;C7NSI:SP=2-300, SSN=7&8;

Subsystem 7&8 is used due to that the information is sent to the IWSMS inthe MSC/VLR and not to the SC (Subsystem 12).

2.4.3.3 From IWSMS to SCArrow 4 (figure 3)

The IWSMS sends the message "service center alert" to the SC. The routingis based on the SC-address derived from the HLR. To distinguish betweensending a message to the IWMSC and the SC, different Translation Types(TT) are needed. The TT for the alert is set with VLR properties. TT=1 isrecommended (see 1.4.1.3).


MGEPC:PROP=SMSALERTTYPE-1;

C7GSI:TT=1,NP=1,NA=4,NS=46 70 702..,GTRC=3;

The called address is the SC-address. The GTRC points out the SC.



E



2.4.3.4 From SC to MSArrow 5-9 (figure 3)

The SC receives the alert and retransmits the SM. The terminating part of theretransmission works the same as described in paragraph 2.4.2.

2.4.3.5 From GPRS to GSMThe SMS-GMSC and SMS-IWMSC are not affected by the introduction ofSMS over GPRS. This means that a terminal attached to GPRS has thepossibility to perform the same SM services as a GSM attached one.

2.4.4 Charging

The Charging Cases derived from the four different software routes areanalysed in the Traffic dependant charging analysis (Initial charging caseanalysis). Due to that the originated part shall be paid by the A-subscriber andthe terminating part shall be paid by the B-subscriber, we have to branch inthe analysis. The charging can be performed, depending on traffic case,


CHIPI:CC=7;CHISI:BC=CI-9&-10, NCC=7,CHISI:BC=CI-11&-12, NCC=8;CHIPE;

CI=9 => Originating SMS in MSC/VLR, MSMO

CI=10 => Originating SMS in SMS-IWMSC

CI=11 => Terminating SMS in MSC/VLR, MSMT

CI=12 => Terminating SMS in SMS-GMSC

The new charging (NCC) is analysed in the charging analysis.


CHASI:CC=7 => AP (A-party)CHASI:CC=8 => BP (B-party)

Note There is also a possibility to branch on the TSC value derivedfrom the Telecommunication Service analysis, in the initialcharging analysis.

3 Data Transcript Impacts

3.1 General

The Data Transcript commands are divided into different chapters dependingon where in the loading sequence they belong to.



E

All subfiles, both in MSC/VLR and HLR, that are affected by the function ShortMessage Service, SMS, are mentioned in this document. The NI parametervalues are typical values calculated in AI.

3.2 Subfile 10000 - APT Size Alterations (MSC/VLR)


!***********!!*** SHS ***!!***********!

SAAII:SAE=500, NI= 200, BLOCK=GSCTAP;

! Number of SM-MT transfer requests. !! Typical value: 1278 !! -------------------------------------------------------------- !

SAAII:SAE=500, NI= 200, BLOCK=GSMOSAP;

! Number of SM-MT transfer requests. !! Typical value: Same value as SAE=500, BLOCK=GSCTAP. !! -------------------------------------------------------------- !

SAAII:SAE=500, NI= 64, BLOCK=HASCAP2;

! Handles the sending of the "Alert Service Centre" !! MAP v2 message to a IWMSC. !! Typical value: 35 !! -------------------------------------------------------------- !

SAAII:SAE=500, NI= 64, BLOCK=HRSMAP2;

! Receives the "Send Routing Information for Short Message" !! MAP v2 message from SMS-GMSC and sends the response to !! SMS-GMSC. !! Typical value: 14 !! -------------------------------------------------------------- !

SAAII:SAE=500, NI= 200, BLOCK=IWASCAP;

! Number of SM-ASC transfer requests. !! Typical value: Same value as SAE=500, BLOCK=IWMOAP. !! -------------------------------------------------------------- !

SAAII:SAE=500, NI=200, BLOCK=MSMTAP;

! Number of SM-MT procedures. !! Typical value: 344 !! -------------------------------------------------------------- !

SAAII:SAE=500, NI= 53, BLOCK=MSMPAP;

! Number of task individuals for "note MS present" towards HLR. !! Typical value: 106 !! -------------------------------------------------------------- !



E

SAAII:SAE=500, NI=200, BLOCK=MSMMH;

! Number of short message transfer requests. !! Typical value: 659 !! -------------------------------------------------------------- !

SAAII:SAE=500, NI=119, BLOCK=MSMO;

! Number of individuals for SM-MO transfer requests. !! Typical value: 238 !! --------------------------------------------------------------- !

SAAII:SAE=500, NI=172, BLOCK=MSMT;

! Number of individuals for SM-MO transfer requests. !! Typical value: 344 !! --------------------------------------------------------------- !

SAAII:SAE=500, NI=119, BLOCK=MSMOAP;

! Number of individuals for SM-MO transfer requests. !! Recommended value: The same as for SAE=500, BLOCK=MSMO. !! --------------------------------------------------------------- !

SAAII:SAE=500, NI= 200, BLOCK=GSMS;

! Number of individuals for SM-MT in SMS-GMSC. !! Recommended value: The same as for SAE=500, BLOCK=GSCTAP. !! --------------------------------------------------------------- !

SAAII:SAE=500, NI= 200, BLOCK=IWMOAP;

! Number of individuals for MAP dialogues related to SM-MO in !! SMS-IWMSC. !! Typical value: 1278 !! --------------------------------------------------------------- !

SAAII:SAE=500, NI= 200, BLOCK=IWSCAP;

! Number of individuals for SM-MO transfer requests. !! Recommended value: Same as SAE=500, BLOCK=IWMOAP. !! --------------------------------------------------------------- !

SAAII:SAE=500, NI= 200, BLOCK=IWSMS;

! Number of individuals for SM-MO transfer requests in SMS-IWMSC.!! Recommended value: Same as SAE=500, BLOCK=IWMOAP. !! --------------------------------------------------------------- !

SAAII:SAE=527, NI=18, BLOCK=MSMMH;

! No of individuals for packing/unpacking SM transfer requests !! Typical value: 35 !! --------------------------------------------------------------- !



E

3.3 Subfile 10000 - APT Size Alterations (HLR)


SAAII:SAE=279, NI= 5;! The number of Service Center adresses that can be stored in !! message waiting list. !! Master block: HSCAD !! Typical value: 25 !! -------------------------------------------------------------- !

SAAII:SAE=500, BLOCK=HASCAP, NI=64;

! Each individual of this file processes the alerting of all !! the service centers whose addresses are stored in the message !! waiting data list of one subscriber. !! Typical value: 64 !! -------------------------------------------------------------- !

SAAII:SAE=500, BLOCK=HNMSPAP, NI=140;

! Number of task individuals. The block receives the message !! "NOTE MS PRESENT" from the VLR. !! Typical value: 64 !! -------------------------------------------------------------- !

SAAII:SAE=500, BLOCK=HRSMAP, NI=51;

! Each individual of this file handles one Send Routing !! Information V1 for Short Messages. !! Typical value: 51 !! -------------------------------------------------------------- !

SAAII:SAE=500, BLOCK=HSMWDAP, NI=140;

! Number of task individuals. The block handles the "SET !! MESSAGE WAITING DATA" received from SMS-GMSC. !! Typical value: - !! -------------------------------------------------------------- !

SAAII:SAE=786, BLOCK=HSD, NI=2500;

! Number of Message Waiting Data Lists. !! Typical value: 2500 !! -------------------------------------------------------------- !

3.4 Subfile 13000 - Exchange Properties


MGEPC:PROP=SMOASSIGN-1;! ASSIGNMENT REQUEST TO BSC. !! INDICATES IF MESSAGE ’ASSIGNMENT !! REQUEST’ IS SENT TO BSC FOR A SHORT !! MESSAGE ORIGINATED TRANSACTION. !! 0 = MESSAGE IS NOT SENT. !



E

! 1 = MESSAGE IS SENT. !! PARAMETER IS OPTIONAL WITH DEFAULT !! VALUE = 0. !! THIS PARAMETER CAN BE GIVEN ONLY WHEN !! THE FUNCTION ’SHORT MESSAGE SERVICE, !! MOBILE ORIGINATED, POINT TO POINT, !! IN MSC/VLR’ IS IN THE APPLICATION !! SYSTEM OF THE EXCHANGE. !! THE PARAMETER IS OWNED BY THE BLOCK !! MSMO. !

MGEPC:PROP=SMOTIMER-30;!TIME SUPERVISION FOR THE RECEPTION OF !! THE ORIGINATING SHORT MESSAGE FROM !! THE MS. !! THE PARAMETER DEFINES TIME BETWEEN !! ’CIPHERMODE COMPLETE’ AND ’CP_DATA’ !! MESSAGES IN SHORT MESSAGE ORIGINATED !! IN MSC/VLR. !! AFTER EXPIRATION OF THIS TIMER !! THE MESSAGE ’CLEAR COMMAND’ IS !! SENT TO THE MS AND THE CONNECTION !! RELEASED. !! THE VALUE IS SPECIFIED IN SECONDS !! (STEPS ON 1S). !! PARAMETER IS OPTIONAL WITH DEFAULT !! VALUE = 30. !! THE PARAMETER IS OWNED BY THE !! BLOCK MSMO. !

MGEPC:PROP=SMSALERTTRTYPE-1;! TRANSLATION TYPE FOR ROUTING OF !! THE MESSAGE ’SERVICE CENTRE ALERT’. !! THE PARAMETER IS USED IN THE SCCP !! LEVEL FOR ROUTING OF THE MESSAGE !! ’SERVICE CENTRE ALERT’ FROM SMS-IWMSC !! TO SERVICE CENTRE OUTSIDE THE GSM !! NETWORK. !! THE MESSAGE IS USED TO INFORM SERVICE !! CENTRE, THAT THE MOBILE SUBSCRIBER IS !! AVAILABLE AGAIN AND CAN RECEIVE !! SHORT MESSAGES. !! THE GLOBAL TITLE TRANSLATION TABLES !! SHALL BE DEFINED BY COMMANDS IN SCCP !! FOR THE GIVEN TRANSLATION TYPE. !! PARAMETER IS MANDATORY WITH APPLICA- !! TION DEPENDENT VALUE. !! FOR DETAILS SEE APPLICATION !! INFORMATION FOR BLOCK C7GT IN SCCP. !! THE PARAMETER IS OWNED BY THE !! BLOCK IWASCAP. !

MGEPC:PROP=SMTASSIGN-1;! ASSIGNMENT REQUEST TO BSC. !! INDICATES IF MESSAGE ’ASSIGNMENT !! REQUEST’ IS SENT TO BSC FOR A SHORT !! MESSAGE TERMINATING TRANSACTION. !



E

! 0 = MESSAGE IS NOT SENT. !! 1 = MESSAGE IS SENT. !! PARAMETER IS OPTIONAL WITH DEFAULT !! VALUE = 0. !! THIS PARAMETER CAN BE GIVEN ONLY WHEN !! THE FUNCTION ’SHORT MESSAGE SERVICE, !! MOBILE TERMINATED, POINT TO POINT, !! IN MSC/VLR’ IS IN THE APPLICATION !! SYSTEM OF THE EXCHANGE. !! THE PARAMETER IS OWNED BY THE !! BLOCK MSMT. !

MGEPC:PROP=SMSFMOSMTRTYPE-1;! TRANSLATION TYPE FOR ROUTING OF THE !! ’FORWARD MOBILE ORIGINATED SHORT !! MESSAGE’. !! THE PARAMETER IS USED IN THE SCCP !! LEVEL FOR ROUTING OF ’FORWARD MOBILE !! ORIGINATED SHORT MESSAGE’ FROM !! SMS-IWMSC TO SERVICE CENTRE OUTSIDE !! THE GSM NETWORK. !! THE MESSAGE IS USED TO SUBMIT MOBILE !! ORIGINATED SHORT MESSAGE TO SERVICE !! CENTRE. !! THE GLOBAL TITLE TRANSLATION TABLES !! SHALL BE DEFINED BY COMMANDS IN SCCP !! FOR THE GIVEN TRANSLATION TYPE. !! PARAMETER IS MANDATORY WITH APPLICA- !! TION DEPENDENT VALUE, IF THE FUNCTION !! ’OUTGOING MO-SM IN SMS-IWMSC’ IS IN !! THE APPLICATION SYSTEM OF THE !! EXCHANGE. !! IF THE FUNCTION IS NOT IN THE !! APPLICATION SYSTEM THE PARAMETER !! CANNOT BE GIVEN. !! FOR DETAILS SEE APPLICATION INFORMA- !! TION FOR BLOCK C7GT IN SCCP. !! THE PARAMETER IS OWNED BY THE BLOCK !! IWSCAP. !

MGEPC:PROP=LSSMSMOALLOW-1;!Allowance of Short Message Service Mobile !!Originated (SMSMO) outside the !!local subscription area. !!Indicates if mobile originated short !!message service accesses are allowed !!outside the local subscription area for !!mobile subscribers having a local !!subscription. !!Parameter is MANDATORY with !!application dependent values: !!0 = Not allowed. !!1 = Allowed. !!The parameter is owned by the block !!MZONE. !

MGEPC:PROP=LSSMSMTALLOW-1;



E

!Allowance of Short Message Service Mobile !!Terminated (SMSMT) outside the !!local subscription area. !!Indicates if mobile terminated short !!message service accesses are allowed !!outside the local subscription area for !!mobile subscribers having a local !!subscription. !!Parameter is MANDATORY with !!application dependent values: !!0 = Not allowed. !!1 = Allowed. !!The parameter is owned by the block !!MZONE. !

3.4.1 Subfile 14000 - AXE PARAMETERS


DBTRI;DBTSC:TAB=AXEPARS, SETNAME=name, NAME=name, VALUE=value;DBTRE:COM;

The following parameters are introduced:

Parameter ------------- Parameter Set----------------

Range-------

MAPVERHLRSG GSM1APTC 1-2

MAPVERHLRM GSM1APTC 1-2

MAPVERSIM GSM1APTC 1-2

TIMSRISM2SG GSM1APTC 15-30

TIMRSMDS2SG GSM1APTC 3-10

TIMRFDM2M GSM1APTC 15-30

TIMFSMO2M GSM1APTC 15-30

TIMFSMO2SEGM GSM1APTC 20-90

TIMFSMO2SEGSI GWM1APTC 20-90

MAPRESTSI GSMSHSC 0-1



E

3.5 Subfile 15100 - Charging


CHTSI:T=7, NSP=0;CHTSI:T=8, NSP=0;

CHCSI:TC=7, T=7;CHCSI:TC=8, T=8;

CHASI:CC=7, CD=3, TT, AP, IS=1, TC=7; !SWE subscriber!CHASI:CC=8, CD=3, TT, BP, IS=1, TC=7; !SWE subscriber!CHASI:CC=11, CD=3, TT, AP, IS=1, TC=8; !INT. subscriber!CHASI:CC=12, CD=3, TT, BP, IS=1, TC=8; !INT. subscriber!

CHIPI:CC=7; ! SWE subscriber !CHISI:BC=CI-9&-10, NCC=7; ! Originated !CHISI:BC=CI-11&-12, NCC=8; ! Terminated !CHIPE;CHIPI:CC=8; ! INT. Subscriber !CHISI:BC=CI-9&-10, NCC=11; ! Originated !CHISI:BC=CI-11&-12, NCC=12; ! Terminated !CHIPE;

3.6 Subfile 15200 - C7 - Data


C7SPI:SP=2-800;C7PNC:SP=2-800, SPID=SMSSC;

C7STI:ST=C7ST2C-10,ITYPE=14;C7STI:ST=C7ST2C-14,ITYPE=14;

C7LDI:LS=2-800;

C7LPC:PARMG=1, T7MS=2000; ! Time supervision for SL towards SMS-SC !

C7SLI:LS=2-800,SLC=0,ST=C7ST2C-10,ACL=A1,SDL="SMS-0,UPD-193", PARMG=1;C7SLI:LS=2-800,SLC=1,ST=C7ST2C-14,ACL=A1,SDL="SMS-1,UPD-225", PARMG=1;

C7RSI:DEST=2-800, LS=2-800, PRIO=1;

3.7 Subfile 15300 - Route Characteristics


EXROI:R=MSMO, DETY=MSMO;EXRBC:R=MSMO, BO=93, MIS3=0;EXROI:R=MSMT, DETY=MSMT;EXRBC:R=MSMT, BO=94, MIS3=0;EXROI:R=GSMS, DETY=GSMS;EXRBC:R=GSMS, BO=91, MIS3=1;EXROI:R=IWSMS, DETY=IWSMS;EXRBC:R=IWSMS, BO=92, MIS3=1;



E

EXROI:R=SMSCSO&SMSCSI, DETY=UPD, FNC=7;

3.8 Subfile 15350 - Route Allocation


EXDRI:R=SMSCSO&SMSCSI, DEV=UPD-193&-225;

3.9 Subfile 15600 - B-Number Analysis


!MODIFICATION OF SC-ADDRESS TO BNT=1!ANBSI:B=80-00946, M=3, L=14, BNT=1, F=OR;ANBSI:B=80-070, M=1-46, L=10, BNT=1, F=OR;ANBSI:B=80-70, M=0-46, L=9, BNT=1, F=OR;

!GSMS (CHARGING DEPENDING ON B-NUMBER)!ANBSI:B=91-44, CC=8;ANBSI:B=91-46, CC=7;ANBSI:B=91-49, CC=8;

!IWSMS (CHARGING DEPENDING ON SC-ADDRESS)!ANBSI:B=92-46, CC=7;

MSMO (CHARGING DEPENDING ON SC-ADDRESS)!

ANBSI:B=93-44, D=9-9, CC=8;ANBSI:B=93-46, D=9-9, CC=7;ANBSI:B=93-49, D=9-9, CC=8;

!MSMT (CHARGING DEPENDING ON B-NUMBER)!ANBSI:B=94-44, CC=8;ANBSI:B=94-46, CC=7;ANBSI:B=91-49, CC=8;

3.10 Subfile 15700 - Pre B-Number Analysis


PNBSI:BO=91, OBA=91;PNBSI:BO=92, OBA=92;PNBSI:BO=93, BNT=1, OBA=93;PNBSI:BO=93, BNT=2, OBA=80;PNBSI:BO=93, BNT=4, OBA=80;PNBSI:BO=94, OBA=94;

3.11

3.12 Subfile 15900 - Special Purpose Digit Analysis


ANGSI:DSO=19, S=46707570000, RES=MAP-2;



E

DSO 19 is used to select the MAP version to be used by the SMS-GMSC for signal ltowards the MSC, when the signalling protocol on the interface towards the Ser vis Ericsson propietary MAP version 2.S is the digit series (MSC number).MAP indicates the MAP version used in the MSC for the SM-MT procedure, where M Aand MAP-2 is MAP version 2.

3.13 Subfile 16100 - Telecommunication Service Analysis


MGTCI:TSC=3, WSIG=NOIS, TBP=NO, NOTE="SMSMO";MGTCI:TSC=4, WSIG=NOIS, TBP=NO, NOTE="SMSTE";MGTEI:TEC=SMSMO, TSC=3;MGTEI:TEC=SMSMT, TSC=4;

3.14 Subfile 75200 - Semipermanent Connections


EXSPI:NAME=SMS-0;EXSSI:DEV1=UPD-193;EXSSI:DEV2=C7ST2C-10;EXSPE;EXSCI:NAME=SMS-0,DEV=UPD-193;

EXSPI:NAME=SMS-1;EXSSI:DEV1=UPD-225;EXSSI:DEV2=C7ST2C-14;EXSPE;EXSCI:NAME=SMS-1,DEV=UPD-225;

3.15 Subfile 75300 - Deblocking C7


C7RAI:DEST=2-800, LS=2-800;

C7LAI:LS=2-800, SLC=0;C7LAI:LS=2-800, SLC=1;

3.16 Subfile 75500 - SCCP Data (MSC/VLR)


C7NPI:SP=2-800, CON;

C7NSI:SP=2-800, SSN=12;

C7GCI:GTRC=3, PSP=2-800, PTERM;C7GCI:GTRC=8, PSP=OWNSP;C7GSI:TT=0, NP=1, NA=4, NS=4670702, GTRC=8;C7GSI:TT=1, NP=1, NA=4, NS=4670702, GTRC=3;



E

3.17 Subfile 75500 - SCCP Data (HLR)


C7NPI:SP=2-300, CON;

C7NSI:SP=2-300, SSN=7&8; ! The VLR with the IWSMS !

C7GCI:GTRC=1, PSP=2-300, PTERM; ! TERM in VLR !

C7GSI:TT=0,NP=1,NA=4,NS=4670702,GTRC=1; ! TO SC via IWSMS in VLR !

4 Miscellaneous Information

4.1 Class

SMS is a "Standard - Optional" function.

For SMS all blocks needed will be on the AS for that particular market. TheDT needed in each subfile is described above.

The SMS functionality requires that a SMS-SC is implemented in the network.The Ericsson SMS-SC is integrated in the MXE node also containing VoiceMail service.



E

References

11737/FF-1/APT210 15/6 A Handling of SC address with type of number unknown inMSC/VLR

5/155 17-ANT 295 01/1 B Short Message Service, Mobile originated, point-to-point, inMSC/VLR

19/155 16-ANT 295 01/1 A Short Message Service, Mobile originated, point-to-point,function on access side

2/155 18-CNT 295 0031 C GSMS, GMSC Short Message Service Coordinator

1/190 82-CNT 238 0034 C HGSDC

2/155 18-CNT 238 0047 PN10 HTRAN

109 21-CNT 238 0047-9 Block HTRAN

06-sms

Documents

short message service

service mosms

service center sc

sc address

b minor changes

c7 data

iwsms sms interworking

sccp data mscvlr