Universal Short Message Service (uSMS) - IN architecture and functionality

To develop functional architectures and information flows relating to the delivert of the universal short message service.  To identify required enhancements to existing signalling protocols. Candidate networks are ISDN and private networks.

Univerzalna storitev kratkih sporočil (uSMS) - Arhitektura in funkcionalnost IN

General Information

Status
Published
Publication Date
31-Oct-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Nov-2003
Due Date
01-Nov-2003
Completion Date
01-Nov-2003

Buy Standard

Guide
V ETSI/EG 201 780 V1.1.1:2003
English language
21 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST-V ETSI/EG 201 780 V1.1.1:2003
01-november-2003
8QLYHU]DOQDVWRULWHYNUDWNLKVSRURþLO X606 $UKLWHNWXUDLQIXQNFLRQDOQRVW,1
Universal Short Message Service (uSMS) - IN architecture and functionality
Ta slovenski standard je istoveten z: EG 201 780 Version 1.1.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST-V ETSI/EG 201 780 V1.1.1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST-V ETSI/EG 201 780 V1.1.1:2003

---------------------- Page: 2 ----------------------

SIST-V ETSI/EG 201 780 V1.1.1:2003
ETSI EG 201 780 V1.1.1 (2000-08)
ETSI Guide
Universal Short Message Service (uSMS);
IN architecture and functionality

---------------------- Page: 3 ----------------------

SIST-V ETSI/EG 201 780 V1.1.1:2003
2 ETSI EG 201 780 V1.1.1 (2000-08)
Reference
DEG/SPAN-061310
Keywords
ISDN, IN, SMS, architecture, stage 2
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.:+33492944200 Fax:+33 493654716
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
editor@etsi.fr
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2000.
All rights reserved.
ETSI

---------------------- Page: 4 ----------------------

SIST-V ETSI/EG 201 780 V1.1.1:2003
3 ETSI EG 201 780 V1.1.1 (2000-08)
Contents
Intellectual Property Rights.4
Foreword.4
1 Scope .5
2 References .5
3 Definitions and abbreviations.5
3.1 Definitions.5
3.2 Abbreviations .6
4 uSMS service requirements.6
5 uSMS Functional Architecture.7
5.1 ISDN/IN Infrastructure.7
5.2 Packet Service Infrastructure.7
6 Point-Point uSMS Procedures and Information Flows .7
6.1 Terminal originated uSMS normal transfer procedure.8
6.2 Terminal terminated uSMS normal transfer procedure .9
6.3 Terminal originated uSMS exception transfer procedure.10
6.4 Terminal terminated uSMS exception transfer procedure.11
6.4.1 Exception handling transfer procedure .11
6.4.2 Exception handling terminal not reachable.12
6.4.2.1 Terminal terminated uSMS transfer attempt on terminal not reachable.12
6.4.2.2 uSMS alert procedure initiated by the network (terminal is present).14
6.4.3 Exception handling memory not available.16
6.4.3.1 Terminal terminated uSMS transfer attempt on memory not available .16
6.4.3.2 uSMS alert procedure initiated by the Terminal (memory available) .17
6.5 uSMS delivery notification.18
7 Cell Broadcast uSMS Procedures and Information Flows .18
8 Interworking scenarios and Feature Interaction .18
Annex A (informative): Universal Short Message Service via PSTN .19
Bibliography.20
History .21
ETSI

---------------------- Page: 5 ----------------------

SIST-V ETSI/EG 201 780 V1.1.1:2003
4 ETSI EG 201 780 V1.1.1 (2000-08)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This ETSI Guide (EG) has been produced by ETSI Technical Committee Services and Protocols for Advanced
Networks (SPAN).
ETSI

---------------------- Page: 6 ----------------------

SIST-V ETSI/EG 201 780 V1.1.1:2003
5 ETSI EG 201 780 V1.1.1 (2000-08)
1 Scope
The present document gives guidance on the network architecture and functionality to support a Point-Point Short
Message Service (PP-SMS) feature to users access network services via PSTN, ISDN, PLMN and IP as it is defined in
DES/SPAN-110093 (see Bibliography).
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] GSM 09.02: "European digital telecommunications system; Mobile Application Part (MAP)
specification".
[2] GSM 03.40: "Technical realization of the Short Message Service (SMS) Point-to-Point (PP)".
[3] CCITT Recommendation E.213: "Telephone and ISDN numbering plan for land mobile stations in
public land mobile networks (PLMN)".
[4] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in GSM 09.02 [1] apply.
msIsdn: this parameter refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with CCITT
Recommendation E.213 [3]
sm-RP-PRI: this parameter is used to indicate whether or not delivery of the short message shall be attempted when a
service centre address is already contained in the Message Waiting Data file
ServiceCentreAddress: this parameter represents the address of a Short Message Service Centre
Sm-RP-UI: this parameter represents the user data field carried by the short message service relay sub-layer protocol
MoreMessagesToSend: this parameter is used to indicate whether or not the service centre has more short messages to
send
MwStatus: this parameter indicates whether or not the address of the originator service centre is already contained in
the Message Waiting Data file. In addition, it contains the status of the Memory Capacity Exceeded Flag (MCEF) and
the status of the Mobile subscriber Not Reachable Flag (MNRF)
ETSI

---------------------- Page: 7 ----------------------

SIST-V ETSI/EG 201 780 V1.1.1:2003
6 ETSI EG 201 780 V1.1.1 (2000-08)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CLI Calling Line Identity
CUSF Call Unrelated Service Function
FT Fixed Terminal
GSM Global System for Mobile communication
HLR Home Location Register
INAP Intelligent Network Application Protocol
IWF InterWorking Function
IWU InterWorking Unit
MAP Mobile Application Protocol
MCEF Mobile Station Memory Capacity Exceeded Flag
MNRF Mobile Not Reachable Flag
MWD Message Waiting Data
PT Portable Terminal
SC Service Control
SCF Service Control Function
SCFh SCF home (network)
SCFv SCF visited (network)
SCUAF Service Call Unrelated Agent Function
SDF Service Data Function
SMS Short Message Service
SMSC Short Message Service Centre
VLR Visited Location Register
4 uSMS service requirements
The uSMS service requirements are specified in DES/SPAN-110093 (see Bibliography).
In line with the HLR in GSM networks, the supporting network shall have some predefined data fields for uSMS
parameters. For example,
The HLR contains (optional):
• Message Waiting Data (MWD):
- MSIsdn-Alert;
- SC address 1;
- SC address 2;
-…;
- SC address n;
• Mobile Not Reachable Flag (MNRF);
• Mobile Station Memory Capacity Exceeded Flag (MCEF).
The VLR contains (optional):
• Mobile Not Reachable Flag (MNRF).
The case where MWD, MNRF and MCEF are not implemented in the HLR is also described in GSM 03.40 [2].
ETSI

---------------------- Page: 8 ----------------------

SIST-V ETSI/EG 201 780 V1.1.1:2003
7 ETSI EG 201 780 V1.1.1 (2000-08)
5 uSMS Functional Architecture
5.1 ISDN/IN Infrastructure
This section describes the architecture for uSMS based on an ISDN/IN suporting infrastructure. It covers these cases
where the user is in his/her home network or in a visited network. The implementation of uSMS should deliver the SMS
with the same (or higher) QoS as for the GSM SMS.
Visited network Home network
SDFv SDFh
SCFv SCFh
IWF SMSC
INAP SMS-MAP
SCUAF CUSF
Figure 1: Architecture for uSMS in ISDN/IN
5.2 Packet Service Infrastructure
This is for further study.
6 Point-Point uSMS Procedures and Information Flows
This section displays for each procedure information flows; the mapping of these flows to specific protocol messages is
outside the scope of the present document.
The following procedures are relevant for the uSMS service:
• Short Message terminal originated (normal and exception procedure);
• Short Message terminal terminated (normal and exception procedure);
• Short Message delivery notification.
NOTE: In the present document the SMS is defined following the GSM procedures (i. e. it is assumed that the
terminals are able to store SMS messages).
ETSI

---------------------- Page: 9 ----------------------

SIST-V ETSI/EG 201 780 V1.1.1:2003
8 ETSI EG 201 780 V1.1.1 (2000-08)
6.1 Terminal originated uSMS normal transfer procedure
In the terminal originated case, a short message is sent from the terminal (portable or fixed) towards the short message
service centre. This short message is sent along with the E.164 [4] number of the recipient, and possibly the Calling
Line Identity of the originating terminal (CLI) in case the recipient should receive this information as in the GSM SMS
service. The CLI may be replaced by the calling user number e.g. in the case of virtual calling card, UPT.
SCUAF CUSF SCFv SDFv SCFh SDFh IWU SMSC
Short message
Short message
Retrieve info
for SMS
SMS info
hort message
Search (CLI)
Search Result
Forward
Terminal
Originated
Short message
Short Message
Ack
Ack
Ack
Ack
Ack
Figure 2: Terminal originated short message transfer
Information flow Interface Parameters needed
Short message SCUAF-CUSF • Called Party E.164 [4]
• Calling Party E.164 [4] (CLI)
• ServiceCentreAddress
• sm-RP-UI
Short message CUSF-SCFv • Called Party E.164 [4]
• Calling Party E.164 [4] (CLI)
• ServiceCentreAddress
• sm-RP-UI
Retrieve info for SMS SCFv-SDv
• CLI
SMS info SDFv-SCFv
• SCFh id (Note 2)
Short message SCFv-SCFh
• Called Party E.164 [4]
• Calling Party E.164 [4] (CLI)
• ServiceCentreAddress
• sm-RP-UI
Search SCFh-SDFh • CLI (Note 1)
Search Result SDFh-SCFh • Ack (ServiceCentreAddress)
Short message SCFh-IWU
• Called Party E.164 [4]
• Calling Party E.164 [4] (CLI)
• ServiceCentreAddress
• sm-RP-UI
ForwardMOShortMessage IWU-SMSC
• Called Party E.164 [4]
• Calling Party E.164 [4] (CLI)
• ServiceCentreAddress (optional)
• sm-RP-UI
ETSI

---------------------- Page: 10 ----------------------

SIST-V ETSI/EG 201 780 V1.1.1:2003
9 ETSI EG 201 780 V1.1.1 (2000-08)
NOTE 1: In order to retrieve and check the SMS access rights of the user, when the user originates a uSMS
procedure, the SCFh queries the SDFh.
NOTE 2: Another possibility could be to use serviceCentreAddress, and forward the short message directly to the
IWU, and bypass the SCFsl.
6.2 Terminal terminated uSMS normal transfer procedure
In the terminal terminated case, a short message is sent from the short message service centre toward
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.