Demo Description of Short Message Services (SMS)

Ericssonwide Internal DEMO DESCRIPTION
Prepared (also subject responsible if other) No.
1 (14)
EEM/GLH R. Dominguez
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
Demo Description of Short Message Services (SMS)

Abstract This document is intended as an aid for Market Units (MU) when defining and preparing demonstrations for a feature. Remove demo cases for feature functionality not purchased by the customer or, if not edited, just perform the relevant parts during demo execution. Contents 1 General....................................................................................................2 1.1 Application..................................................................................2 1.2 Revision History .........................................................................2 1.3 Introduction ................................................................................2 1.4 References.................................................................................3 1.5 Terminology ...............................................................................3 1.6 Additional Information ................................................................4 1.7 Demo Execution Time................................................................4 Prerequisites ..........................................................................................4 2.1 Configuration and Settings.........................................................4 2.2 Tools ..........................................................................................9 Demo Cases............................................................................................9 3.1 Transfer of End-to-End User Data between Mobile Station and SMS-C........................................................................................9 3.2 Provision of Diagnostic Information for MS Not Reachable .....12 Helpful Hints .........................................................................................14 4.1 Feature Related Alarms ...........................................................14 4.2 Feature Related Counters........................................................14

2 (14)
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
1
1.1
General
Application
This document describes how to demonstrate feature: FAJ 122 66/6 Short Message Services (SMS) (MSC)
The following supporting features are needed: FAJ 122 67 R3 FAJ 122 922/5 FAJ 122 934 R3 Short Message Services in HLR Mobile Application Part (MAP) - (MSC) Mobile Application Part (MAP) - (HLR)
1.2
Revision History
Revision Comment A Demo description is reviewed and demo cases are verified. Document is stored in an official product document archive. Author Date ECERDV 2004-08-05
1.3
Introduction
This feature provides means to transfer mobile-originated short messages (SMSs) from the mobile terminal (phone) to a Short Message Service-Service Center (SMS-SC). Furthermore, it provides means to transfer mobileterminated SMSs from the SMS-SC to the recipients mobile terminal. This means that the SMSs follow a delivery procedure whereby they are stored in the SMS-SC and forwarded when the subscriber's terminal is able to receive them. After the terminal receives the SMS it can be stored on the Subscriber Identity Module (SIM) card or in the terminal. This feature includes mobile-terminated SMS (TS21) and mobile-originated SMS (TS22). The feature provides information about the delivery of the short message through either a delivery report or a failure report. The interworking MSC for SMS (SMS-IWMSC) can receive a mobileoriginated short message from within the PLMN and submit it to the recipient SMS-SC. The short message gateway MSC (SMS-GMSC) can receive a mobile-terminated short message from an SMS-SC and forward it to the MSC where the mobile subscriber is registered. The SMS-GMSC and SMS-IWMSC functionality can be located in all MSCs in the network. The MSC supports SMS Queuing. This means the MSC is able to queue terminated short messages until they can be delivered or until a pre-defined timer expires. Charging can be based on Call Data Records generated for mobile-originated short messages in the originating MSC and the SMS-IWMSC, and for mobileterminated short messages in the SMS-GMSC and the terminating MSC.

3 (14)
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
This functionality is applicable for both GSM and WCDMA. This demonstration focuses on the function enhancements included in new release CN4.0: o End-to-End user data may be exchanged in the message send in response to the SMS, i.e. in the Result/Acknowledgement or Error message. Provisioning of diagnostic information holding detailed information about the reason (e.g. no paging response, IMSI Detached, etc.) in the error message send to the SMS-GMSC, in case of MS not reachable for MT SMS.
1.4
References
[1] [2] [3] FD Optional New and Enhanced Features in MSC R11 EED/X/X-03:010 DD Demo Description of Short Message Services (SMS) 155 52-FAJ 122 66/6 FS Signalling System No.7, Mobile Application Part Version 3 For Short Message Service In MSC/VLR Server 178/155 17-FAY 112 131/1 Uen A MSC Product Management EED/X-02:021 TD CS Performance Management via OSS-RC1.1, CN3.0 NIV 22/15291-HSC 113 01/1A Uen
[1] [4]
1.5
Terminology
BSC GSM HLR IMSI MAPv3 MGW MO MS MSC MSISDN MT OPI OSS RBS SIM SMS Base Station Controller Group Special Mobile or Global System for Mobile Communication Home Location Register International Mobile Subscriber Identity Mobile Application Part version 3 Media Gateway Mobile Originated Mobile Station Mobile Switching Centre Mobile Station International ISDN Number Mobile Terminated Operational Instruction Operation Support System Radio Base Station Subscriber Identity Module Short Message Service

4 (14)
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
SMS-GMSC SMS-IWMSC SMS-SC VLR WCDMA
Gateway MSC for Short Message Service Interworking MSC for Short Message Service Short Message Service-Service Center Visitor Location Register Wideband Code Division Multiple Access
1.6
Additional Information
-
1.7
Demo Execution Time

Activity Preparation 3.1 3.2 Total Time Estimated Execution Time 240 min 30 min 20 min 4 hr 50 min
2
2.1
2.1.1
Prerequisites
Configuration and Settings
Environment This demonstration should be performed in lab environment. It is not suitable for being executed on real networks. OSS RC 2.1 should have been installed and configured to connect to the Network Elements. A Service Centre (SC) must be integrated in the network. Demo cases are suitable for GSM or WCDMA system, with layered or nonlayered network architecture. Note that this document describes a GSM network with non-layered architecture. The Mobile Application Part (MAP) version 3 is required to be used between the MSC/VLR and the SMS-C, and between the MSC/VLR and the HLR. The following information needs to be supplied prior to the demo execution: Parameter MSISDN_MS1 IMSI_ MS1 MSISDN_MS2 IMSI_MS2 MSISDN_MS3 IMSI_ MS3 Value Comment

5 (14)
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
2.1.2
Network Configuration Demo cases are suitable for WCDMA and GSM accesses, for layered and non-layered architecture. Note that this Demo Description has been designed using a non-layered network with GSM access and IOG20 as I/O system (as shown in Figure 1). Nodes SMS-IWMSC, SMS-GMSC and SC are co-located in the same node, a.k.a. SMS-C. The following nodes are used: o o o o o o One MSC/MGW node One HLR One BSC and one RBS One SMS-IWMSC, one SMS-GMSC and one SC node (co-located) Three mobile equipments OSS RC system
HLR GMSCMSC
MS1
SMS-IWMSC
BSC MS2 RBS SMS-GMSC MGw MS3 OSS-RC Signaling and data transfer interface Signaling interface
SC
Figure 1: Network Configuration used during this Demo Description (SMSIWMSC, SMS-GMSC and SC are collocated in the same node).

6 (14)
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
2.1.3
Parameter Settings The involved Features have to be activated before Demo execution. Associated Customer AXEPARS:
SETNAME
NAME
VALUE DESCRIPTION Mobile Application Part version to be used on the interface between VLR and HLR for the operations ReadyForSM and NoteMSPresent. Default value: 3 Value for this demonstration: 3
GSM1APTC MAPVERSIONHLRM Range: 1-3
GSM1APTC MAPVERSIM3
Range: 1-3
Mobile Application Part version to be used on the interface between MSC and SMS-IWMSC. Default value: 3 Value for this demonstration: 3
GSM1APTC TIMFSMO3M
Range: 15-30 sec.
Timer value (T-m1) used to supervise every operation MO-ForwardSM. Default value: 30 Value for this demonstration: 30

7 (14)
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
SETNAME
NAME
VALUE DESCRIPTION Range: 20-90 sec. Timer value (T-m1) used to supervise the dialogue establishment in the case of segmented MO-ForwardSM operation. Default value: 30 Value for this demonstration: 30
GSM1APTC TIMFSMO3SEGM
GSM1APTC TIMFSMT3SEGM
Range: 20-90 sec.
Timer value used to supervise the dialogue establishment in the case of segmented MT-ForwardSM Mobile Application Part version 3 operation. Default value: 30 Value for this demonstration: 30
GSM1APTC TIMFSMT3SUBM
Range: 30-180 sec.
Timer value used to supervise every subsequent Mobile Application Part version 3 operation MTForwardSM in case of multiple short message. Default value: 65 Value for this demonstration: 65
GSM1APTC TIMRFSM3M
Range: 15-30 sec.
Timer value used to supervise the operation ReadyForSM. Default value: 15 Value for this demonstration: 15

8 (14)
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
SETNAME GSMSHSC
NAME MAPRESTRICMTM
VALUE DESCRIPTION Range: 0-3 Determines if MAP V2 or MAP V3 or both operations are restricted or not. Default value: 0 Value for this demonstration: 0
OMSRF
MGS
Range: 0-2
Controls Media Gateway Selection Function. Default value: 0 Value for this demonstration: 1
GSMMSCF
COMBINODE
Range: 0-1
Activation of Combi-node feature. Default value: 0 Value for this demonstration: 0 (If Layered Architecture to be used) 1 (If Non-Layered Architecture to be used)
OMSRS
CORNET
Range: 0-2
Indicator of the environment/architecture of the switch. Default value: 0 Value for this demonstration: 1

9 (14)
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
2.2
2.2.1
Tools
Hardware Tools - Protocol Analyzers from Nethawk. - OSS RC 2.1 server and clients.
2.2.2
Software Tools - E-Module in Database PLEXVIEW. - ALEXSERV Database for CN4.0.
3
3.1
3.1.1
Demo Cases
Transfer of End-to-End User Data between Mobile Station and SMS-C
Objective Demonstrate that End-to-End Data is returned in response to the SMS, whether successful or unsuccessful delivery of the SMS. This applies for MO and MT SMS procedures.
3.1.2
Pass/Fail Criteria For Mobile Terminated SMS, the MSC sends towards the SMS-C MAP Result with SM-RP-UI in successful case, or MAP Error SM-Delivery Failure with Diagnostic Info in unsuccessful case. These operations can be seen with a Protocol Analyzer.
3.1.3
Parameter Setting -
3.1.4
Preconditions MS1, MS2 & MS3 must be registered in HLR and located in MSC. MS1, MS2 & MS3 must have TS21 and TS22 provided for SMS sending and receiving. MS3 must have memory capacity exceeded. SMS-SC co-located with SMS-GMSC and SMS-IWMSC, a.k.a. SMS-C. Protocol Analyser is connected between MSC/VLR and SMS-C.

10 (14)
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
3.1.5 1.
Demo Execution Action: Provide teleservices for Short Message Service (mobile originated and mobile terminated). HGSDC:MSISDN=msisdn_MS1,SUD=TS21-1; HGSDC:MSISDN=msisdn_MS1,SUD=TS22-1; HGSDC:MSISDN=msisdn_MS2,SUD=TS21-1; HGSDC:MSISDN=msisdn_MS2,SUD=TS22-1; HGSDC:MSISDN=msisdn_MS3,SUD=TS21-1; HGSDC:MSISDN=msisdn_MS3,SUD=TS22-1; Result: 2. Action: TS21 and TS22 provided. Check that the subscribers are registered in HLR and located in MSC. HGSDP:IMSI=imsi_MS1, ALL; HGSDP:IMSI=imsi_MS2, ALL; HGSDP:IMSI=imsi_MS3, ALL; Result: 3. Action: TS21 and TS22 provided. Check in MSC/VLR that MAPv3 is allowed to be used. HGEPP: ID=MV3RESTRICTION; Result: MAPv3 provided if MV3RESTRICTION-2.
Comment: Refer to OPI: Home Location Register, Exchange Property, Change if you need to change the MV3RESTRICTION value. 4. Action: Check in MSC/VLR if the communication with HLR in MAPv3 is allowed. EXROP:DETY=GRI; Result: Value for RSV parameter should have Bit4=1 and Bit5=1 to allow MAPv3 communication.
Comment: Refer to OPI: Route Data, Change if you need to change the value for RSV parameter of the route towards the HLR to allow MAPv3 communication. 5. Action: Check that MAPv3 is defined in the IMSI Series Analysis. MGISP:IMSIS=imsis; Result: Parameter ANRES includes MAPVER-2.
Comment: Refer to OPI: Mobile Telephony, IMSI Number Series Analysis Data, Change if you need to change the MAPVER value.

11 (14)
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
6.
Action: Result:
Send a SMS from MS1 to MS2. Message sent. Check in the protocol analyser that MT-ForwardSM operation is received in the MSC. MAP Operation MT-ForwardSM with SM-RP-UI received in the MSC (Operation Code = 44). Check in the protocol analyser that MAP Result with SM-RP-UI is sent towards the SMS-C. MAP Result with SM-RP-UI sent towards the SMS-C. Check in the mobile terminal that MS3 has memory capacity exceeded. MS3 has memory capacity exceeded. Send a SMS from MS1 to MS3. Message sent. Check in the protocol analyser that MT-ForwardSM operation is received in the MSC. MAP Operation MT-ForwardSM received in the MSC (Operation Code = 44). Check in the protocol analyser that MAP Error SMDeliveryFailure with diagnosticInfo is sent towards the SMS-C. MAP Error SM-DeliveryFailure (Error Code Value = 32) with diagnosticInfo (the RP-User data received in the MSC/VLR in an RP-ERROR message from the MS, will convey transparently as diagnostic information within the 'SM-DeliveryFailure') sent towards the SMS-C.
7.
Action:
Result:
8.
Action:
Result: 9. Action:
Result: 10. Action: Result: 11. Action:
Result:
12.
Action:
Result:

12 (14)
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
3.2
3.2.1
Provision of Diagnostic Information for MS Not Reachable

Objective Demonstrate that if the mobile is not reachable at Mobile Terminated SMS, the MSC provides diagnostic information holding detailed information about the reason (e.g. no paging response, IMSI Detached, etc.) in response to the SMS delivery request.
3.2.2
Pass/Fail Criteria The MT-ForwardSM message is received in the MSC from the SMS-C and as the MS is not reachable (IMSI Detached), the MSC sends towards the SMS-C the MAP Error AbsentSubscriberSM with AbsentSubscriberDiagnosticSM. These operations can be seen with a Protocol Analyzer.
3.2.3
Parameter Setting -
3.2.4
Preconditions MS1 & MS2 must be registered in HLR and located in MSC. MS1 & MS2 must have TS21 and TS22 provided for SMS sending and receiving. SMS-SC co-located with SMS-GMSC and SMS-IWMSC, a.k.a. SMS-C. Protocol Analyser is connected between MSC/VLR and SMS-C.
3.2.5 1.
Demo Execution Action: Provide teleservices for Short Message Service (mobile originated and mobile terminated). HGSDC:MSISDN=msisdn_MS1,SUD=TS21-1; HGSDC:MSISDN=msisdn_MS1,SUD=TS22-1; HGSDC:MSISDN=msisdn_MS2,SUD=TS21-1; HGSDC:MSISDN=msisdn_MS2,SUD=TS22-1; Result: 2. Action: TS21 and TS22 provided. Check that the subscribers are registered in HLR and located in MSC. HGSDP:IMSI=imsi_MS1, ALL; HGSDP:IMSI=imsi_MS2, ALL; Result: TS21 and TS22 provided.

13 (14)
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
3.
Action:
Check in MSC/VLR that MAPv3 is allowed to be used. HGEPP: ID=MV3RESTRICTION;
Result:
MAPv3 provided if MV3RESTRICTION-2.
Comment: Refer to OPI: Home Location Register, Exchange Property, Change if you need to change the MV3RESTRICTION value. 4. Action: Check in MSC/VLR if the communication with HLR in MAPv3 is allowed. EXROP:DETY=GRI; Result: Value for RSV parameter should have Bit4=1 and Bit5=1 to allow MAPv3 communication.
Comment: Refer to OPI: Route Data, Change if you need to change the value for RSV parameter of the route towards the HLR to allow MAPv3 communication. 5. Action: Check that MAPv3 is defined in the IMSI Series Analysis. MGISP:IMSIS=imsis; Result: Parameter ANRES includes MAPVER-2.
Comment: Refer to OPI: Mobile Telephony, IMSI Number Series Analysis Data, Change if you need to change the MAPVER value. 6. Action: Check automatic deregistration supervision time. MGADP; Result: 7. Action: Result: 8. Action: Time duration indicated in days is printed. Detach one subscriber (i.e.: MS2) by switching off the phone. Phone switched off. Check that the subscriber is deregistered. MGSSP: IMSI=imsi_MS2; Result: 9. Action: Result: MS2 is detached. Send a SMS from MS1 to MS2. Message sent.

14 (14)
Approved Checked
155 52-FAJ 122 66/6

Date Rev Reference
2004-08-05
10.
Action:
Check in the protocol analyser that MT-ForwardSM operation is received in the MSC. MAP Operation MT-ForwardSM received in the MSC (Operation Code = 44). Check in the protocol analyser that MAP Error AbsentSubscriberSM with AbsentSubcriberDiagnosticSM is sent towards the SMS-C. MAP Error AbsentSubscriberSM (Error Code value = 6) with AbsentSubcriberDiagnosticSM IMSI Detached (value = 1) sent towards the SMS-C.
Result:
11.
Action:
12.
Result:
4
4.1
Helpful Hints
Feature Related Alarms
-
4.2
Feature Related Counters

-

Demo Description of Short Message Services (SMS)

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Demo Description of Short Message Services (SMS)

Transféré par

Droits d'auteur :

Formats disponibles

Ericssonwide Internal DEMO DESCRIPTION

Prepared (also subject responsible if other) No.

155 52-FAJ 122 66/6