SIST ES 201 986 V1.2.1:2005

SLOVENSKI STANDARD
01-januar-2005
6WRULWYHLQSURWRNROL]DQDSUHGQDRPUHåMD63$1±6WRULWHYNUDWNLKVSRURþLO606
]D,6'13671±2SLVVWRULWYH
Services and Protocols for Advanced Networks (SPAN); Short Message Service (SMS)
for PSTN/ISDN; Service description
Ta slovenski standard je istoveten z: ES 201 986 Version 1.2.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI Standard
Services and Protocols for Advanced Networks (SPAN);
Short Message Service (SMS) for PSTN/ISDN;
Service description
2 ETSI ES 201 986 V1.2.1 (2003-04)

Reference
RES/SPAN-110109
Keywords
ISDN, PSTN, stage 1, SMS,
supplementary service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
editor@etsi.org
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 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI ES 201 986 V1.2.1 (2003-04)
Content
Intellectual Property Rights.6
Foreword.6
Introduction .6
1 Scope.7
2 References.8
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.9
4 Description.10
4.1 Core service features .11
4.1.1 Short Message Service Centre (SM-SC) capabilities.11
4.1.2 Outgoing message (from the originating SM-TE) .11
4.1.3 Submit report.12
4.1.4 Incoming message (to the destination SM-TE).12
4.1.5 Deliver report.13
4.1.6 Message length.13
4.1.7 Character set.14
4.1.8 Terminal memory.14
4.1.9 Service Centre Time Stamp .14
4.2 Optional service features.14
4.2.1 Reply path.14
4.2.2 Validity period.15
4.2.3 Encryption or protection .15
4.2.4 Destination media.15
4.2.5 Replace short message function.15
4.2.6 Anonymous Short Message.16
4.3 Other features.16
4.3.1 SM Sending User Identification Restriction (SMSUIR).16
4.3.2 SM Forwarding (SMF) .16
4.3.3 Anonymous SM Rejection (ASMR).16
4.3.4 Malicious SM IDentification (MSMID) .17
4.3.5 Outgoing SM White List/Black List (OSMWL/OSMBL).17
4.3.6 Incoming SM White List/Black List (ISMWL/ISMBL).17
4.3.7 SM Distribution List (SMDL) (Multi Messaging).17
5 Procedures.18
5.1 Provision and withdrawal.18
5.2 Normal procedures.19
5.2.1 Registration and erasure.19
5.2.1.1 Core requirements.19
5.2.1.2 Optional requirements.19
5.2.2 Activation and deactivation .19
5.2.2.1 Core requirements.19
5.2.2.2 Optional requirements.20
5.2.3 Invocation and operation .20
5.2.3.1 Outgoing message.20
5.2.3.1.1 Core requirements.20
5.2.3.1.2 Optional requirements.21
5.2.3.2 Submit report.21
5.2.3.2.1 Core requirements.21
5.2.3.2.2 Optional requirements.21
5.2.3.3 Incoming message.22
5.2.3.3.1 Core requirements.22
5.2.3.3.2 Optional requirements.22
ETSI
4 ETSI ES 201 986 V1.2.1 (2003-04)
5.2.3.4 Deliver report.23
5.2.3.4.1 Core requirements.23
5.2.3.4.2 Optional requirements.23
5.2.3.5 Status report.23
5.2.3.5.1 Core requirements.23
5.2.3.5.2 Optional requirements.24
5.2.4 Interrogation.24
5.2.4.1 Core requirements.24
5.2.4.2 Optional requirements.24
5.3 Exceptional procedures.25
5.3.1 Registration and erasure.25
5.3.2 Activation and deactivation .25
5.3.3 Invocation and operation .25
5.3.3.1 Core requirements.25
5.3.3.1.1 Outgoing message.25
5.3.3.1.2 Submit report.26
5.3.3.1.3 Incoming message.26
5.3.3.1.4 Deliver report.27
5.3.3.2 Optional requirements.27
5.3.4 Interrogation.27
6 Interworking requirements.27
6.1 Interworking between the SMS service provider's equipment and other networks.27
6.2 Interworking between public networks providing the transfer of short messages between the Service
Centre and the terminal .27
6.3 Interworking with private networks .28
6.4 Interworking with other types of services .28
7 Interaction with supplementary services .28
Annex A (normative): Interaction with ISDN supplementary services .29
A.1 Advice Of Charge services (AOC-S, AOC-D, AOC-E) .29
A.2 Call Waiting (CW).29
A.3 Call HOLD (HOLD) .29
A.4 Explicit Call Transfer (ECT).29
A.5 Calling Line Identification Presentation (CLIP) .29
A.6 Calling Line Identification Restriction (CLIR) .30
A.7 COnnected Line identification Presentation (COLP).30
A.8 COnnected Line identification Restriction (COLR).30
A.9 Closed User Group (CUG).30
A.10 Completion of Calls to Busy Subscriber (CCBS) .30
A.11 Completion of Calls on No Reply (CCNR).30
A.12 CONFerence call, add-on (CONF).30
A.13 Call Forwarding Unconditional (CFU) .31
A.14 Call Forwarding Busy (CFB) .31
A.15 Call Forwarding No Reply (CFNR) .31
A.16 Call Deflection (CD) .31
A.17 Selective Call Forwarding (SCF) .31
A.18 Malicious Call IDentification (MCID).31
A.19 Three ParTY (3PTY).31
ETSI
5 ETSI ES 201 986 V1.2.1 (2003-04)
A.20 User-to-User Signalling (UUS).31
A.21 Fixed Outgoing Call Barring (OCB-F) .31
A.22 User Controlled Outgoing Call Barring (OCB-UC).32
A.23 Message Waiting Indication (MWI).32
A.24 Meet-Me Conference (MMC) .32
A.25 Direct Dialling In (DDI).32
A.26 Multiple Subscriber Number (MSN).32
A.27 SUB addressing (SUB).32
A.28 Terminal Portability (TP) .32
A.29 Line Hunting (LH) .32
A.30 Anonymous Call Rejection (ACR).32
Annex B (normative): Interaction with PSTN supplementary services.33
B.1 Calling Line Identification Presentation (CLIP) .33
B.2 Calling Line Identification Restriction (CLIR) .33
Annex C (informative): Interaction with PSTN supplementary services.34
C.1 Advice Of Charge services (AOC-S, AOC-D, AOC-E) .34
C.2 Call Waiting (CW).34
C.3 Call HOLD (HOLD) .34
C.4 Completion of Calls to Busy Subscriber (CCBS) .34
C.5 Completion of Calls on No Reply (CCNR).34
C.6 Call Forwarding Unconditional (CFU) .35
C.7 Call Forwarding Busy (CFB) .35
C.8 Call Forwarding No Reply (CFNR) .35
C.9 Selective Call Forwarding (SCF) .35
C.10 Malicious Call IDentification (MCID).35
C.11 Three ParTY (3PTY).35
C.12 Fixed Outgoing Call Barring (OCB-F) .35
C.13 User Controlled Outgoing Call Barring (OCB-UC).35
C.14 Message Waiting Indication (MWI).36
C.15 Multiple Subscriber Number (MSN).36
C.16 SUB addressing (SUB).36
C.17 Anonymous Call Rejection (ACR).36
Annex D (informative): Definition of registration, erasure, activation, deactivation,
invocation and interrogation procedures for a network based
solution.37
Annex E (informative): Bibliography.38
History .39

ETSI
6 ETSI ES 201 986 V1.2.1 (2003-04)
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://webapp.etsi.org/IPR/home.asp).
All published ETSI deliverables shall include information which directs the reader to the above source of information.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Services and Protocols for Advanced
Networks (SPAN).
In accordance with ITU-T Recommendation I.130 [1] the following three level structure is used to describe the
supplementary telecommunication services as provided by European public telecommunications operators under the
pan-European Integrated Services Digital Network (ISDN):
• Stage 1: is an overall service description, from the user's stand-point;
• Stage 2: identifies the functional capabilities and information flows needed to support the service described in
stage 1; and
• Stage 3: defines the signalling system protocols and switching functions needed to implement the service
described in stage 1.
The present document details the stage 1 aspects (overall service description) for the Short Message Service (SMS).
Introduction
The Short Message Service (SMS) is a service that shall make it possible to offer seamless SMS over different networks
(PSTN, ISDN, PLMN).
In the following of the present document it is assumed that both the sending and receiving Terminal Equipment (TE)
have appropriate capabilities to send, receive, store, display and delete short messages.
ETSI
7 ETSI ES 201 986 V1.2.1 (2003-04)
1 Scope
The present document defines the stage 1 service description of the Short Message Service (SMS). Stage 1 is an overall
service description, primarily from the service subscriber's and user's point of view, but does not deal with the details of
the human interface itself.
The SMS can be provided via ISDN and PSTN accesses. The present document includes information applicable to
service providers and equipment manufacturers. Where the text indicates the status of a requirement, (i.e. as strict
command or prohibition, as authorization leaving freedom or, as a capability or possibility), this shall be reflected in the
text of the relevant stage two and stage three standards.
The present document describes only the short message service between Terminal Equipment (TE) and a Short Message
Service Centre (SM-SC). The kind of protocols for sending and receiving a Short Message (SM) as well as charging
principles are outside the scope of the present document.
Interactions with supplementary services not mentioned in clause 7 and the respective annexes are outside the scope of
the present document.
The present document contains the core service features and also optional service features for the Short Message
Service. A service may be provided on the basis of the core requirements alone. The present document does not deal
with a Short Message Service Broadcast.
Furthermore, additional functionalities not covered in the present document may be implemented. The requirements of
which are considered outside of the scope of the present document are consequently outside the scope of the
corresponding stage 2 and stage 3 standards. Such additional functionalities may be on a network-wide basis, or
particular to one user or a group of users. Such additional functionalities do not compromise conformance to the core
requirements of the service.
Furthermore, conformance to the present document is met by conforming to the stage three standards with the field of
application appropriate to the equipment being implemented. Therefore no method of testing is provided for the present
document.
The SMS can be realized in two ways, either as a network based solution or as a user based solution using the basic call
procedures only. The sending and/or receiving part can be preceded in the same or in a different way.
1) Network Based Solution: a service offered as part of a function within the public network.
2) User Based Solution: a service offered as part of a function within the end-user equipment, which does not
require any specific short message transfer function inside the public network.
The present document covers in general both possibilities but if different or specific descriptions are necessary, the
relevant clauses are marked as "NBS" (Network Based Solution) or "UBS" (User Based Solution). Clauses that are
valid for both realizations are marked as "UBS/NBS".
There are two different protocols known for the UBS (protocol 1 and protocol 2; see ES 201 912 [3]) and a third one for
NBS. The handling between terminals with different protocols on the same subscriber line and service centres should be
managed within the service centres or the terminals. These handling matters are outside the scope of the present
document.
ETSI
8 ETSI ES 201 986 V1.2.1 (2003-04)
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 and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
[1] ITU-T Recommendation I.130: "Method for the characterization of telecommunication services
supported by an ISDN and network capabilities of an ISDN".
[2] Void.
[3] ETSI ES 201 912: "Access and Terminals (AT); Short Message Service (SMS) for PSTN/ISDN;
Short Message Communication between a fixed network Short Message Terminal Equipment and
a Short Message Service Centre".
[4] ETSI ETS 300 345: "Integrated Services Digital Network (ISDN); Interworking between public
ISDNs and private ISDNs for the provision of telecommunication services; General aspects".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
deliver report: response from the destination terminal to the SM-SC indicating that an SM has been accepted or not
with the appropriate cause, if rejected
destination SM-TE: terminal with short message functionalities on the receiving user's side, connected to the
subscriber line which receives an incoming message
originating SM-TE: terminal with short message functionalities on the sending user's side, connected to the subscriber
line which initiates an outgoing message
receiving user: user who receives an incoming message on his/her SM-TE from the SM-SC via the subscriber line
replace Short Message Function: optional function of the SM-SC and the SM-TE that enables the automatic replacing
of a Short Message by a new one
NOTE: The replacement indication is transmitted in conjunction with the Short Message. See Replace Short
Message Type.
replace short message type: indication to be sent with a short message (in both submission and delivery cases) that the
short message is of a particular type allowing the destination SM-TE or SM-SC to replace an existing message of the
same type held in the SM-TE or SM-SC provided it comes:
• in SM delivery cases: from the same SM-SC and originating address;
• in SM submission cases: from the same SM-TE.
ETSI
9 ETSI ES 201 986 V1.2.1 (2003-04)
reply path procedure: mechanism which allows an SM-TE to request that an SM-SC should be permitted to handle a
reply sent in response to a message previously sent from that SM-TE to another SM-TE
NOTE: This may happen even though the SM-SC may be unknown to the SM-TE that received the initial
message.
sending user: user who sends an outgoing message from his/her SM-TE to the SM-SC via the subscriber line
Service Centre Time Stamp (SCTS): information element offering the destination SM-TE of an SM the information
of when the message arrived at the SM-SC
Short Message (SM): information that may be conveyed by means of the SMS described in ES 201 986
Short Message Service Centre (SM-SC): function unit, which is responsible for the relaying and store-and-forwarding
of a short message (SM) between two SM-TEs
NOTE: The SM-SC can functionally be separated from or integrated in the network.
Short Message Terminal Equipment (SM-TE): terminal that may send or receive short messages
SM data: contains all the information which is needed by the SM-SC (e.g. destination address, text, etc.)
status report: information used to inform the originating SM-TE of the status of a short message previously submitted
by this SM-TE, e.g. whether the SM-SC was able to successfully forward the message or not, or whether the message
was stored in the SM-SC for later delivery
submit report: response from the SM-SC to the originating SM-TE indicating that an SM has been accepted or not
with the appropriate cause, if rejected
Validity Period (VP): information element enabling the originating SM-TE to indicate the time period during which
the sending user considers the SM to be valid
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
3PTY Three ParTY
ACR Anonymous Call Rejection
ASMR Anonymous SM Rejection
CCBS Completion of Calls to Busy Subscriber
CCNR Completion of Calls on No Reply
CD Call Deflection
CFB Call Forwarding Busy
CFNR Call Forwarding No Reply
CFU Call Forwarding Unconditional
CLIP Calling Line Identification Presentation
CLIR Calling Line Identification Restriction
COLP COnnected Line identification Presentation
COLR COnnected Line identification Restriction
CONF CONFerence call, add-on
CUG Closed User Group
DDI Direct Dialling In
FSK Frequency Shift Keying
GSM Global System for Mobile communications
ISDN Integrated Services Digital Network
ISMBL Incoming SM Black List
ISMWL Incoming SM White List
LH Line Hunting
MCID Malicious Call IDentification
MMC Meet-Me Conference
MSMID Malicious SM IDentification
MSN Multiple Subscriber Number
MWI Message Waiting Indication
ETSI
10 ETSI ES 201 986 V1.2.1 (2003-04)
NBS Network Based Solution
OCB-F Fixed Outgoing Call Barring
OCB-UC User Controlled Outgoing Call Barring
OSMBL Outgoing SM Black List
OSMWL Outgoing SM White List
PIN Personal Identification Number
PLMN Public Land Mobile Network
PSTN Public Switched Telephone Network
SCF Selective Call Forwarding
SCTS Service Centre Time Stamp
SM Short Message
SMDL SM Distribution List
SMF SM Forwarding
SMS Short Message Service
SM-SC Short Message Service Centre
SMSUIR SM Sending User Identification Restriction
SMSUIR SM Sending User Identification Restriction
SM-TE Short Message Terminal Equipment
SUB SUB addressing
TE Terminal Equipment
TP Terminal Portability
UBS User Based Solution
UMTS Universal Mobile Telecommunications System
UUS User-to-User Signalling
VP Validity Period
xDSL x Digital Subscriber Line
4 Description
UBS/NBS:
The Short Message Service (SMS) enables a sending user to send a SM of a limited size to a receiving user via an
SM-SC.
The Short Message Service described in the present document applies to PSTN and ISDN accesses. In case of ISDN the
SMS shall be possible on a number basis.
A short message can be initiated upon a request of the sending user or by the service provider itself, and shall be sent to
the receiving user. An SM is always conveyed via an SM-SC. The SM-SC receives the SM from an originating SM-TE
(sending user), converts the message if necessary, and relays the SM to the destination SM-TE (receiving user).
Having received one or more SM, the receiving user can subsequently read, store or delete the messages on its terminal.
If the SM-TE supports the optional Replace Short Message Function, Short Messages with the respective Replace Short
Message Type indication held in the SM-TE are automatically replaced by received new ones.
The SMS shall support "core service features", available to all SMS users. In addition "optional service features" may
be provided.
The means by which the receiving user manages these features are outside the scope of the present document.
The preparation of an SM as well as the kind of data transmission between the sending or receiving users and the
SM-SC are outside the scope of the present document.
UBS:
The annexes describe the interactions with PSTN and ISDN supplementary services.
NBS:
None.
ETSI
11 ETSI ES 201 986 V1.2.1 (2003-04)
4.1 Core service features
4.1.1 Short Message Service Centre (SM-SC) capabilities
Time
SM-SC
(fixed network)
Submit
(Outgoing message)
Network other SM-SCs
Submit report
(e.g. GSM)
Deliver
Originating SM-TE
Network
(Incoming message)
(Sending user)
Status report
Deliver report
Destination SM-TE
Deliver report
(Receiving user)
Figure 1: SM-SC capabilities
UBS/NBS:
For both, outgoing and incoming messages, the SM-SC acts as a store and forward centre. The SM-SC can be
functionally separated from the network (PSTN/ISDN) although this does not preclude an integrated implementation.
More than one SM-SC may be connected to a network (PSTN/ISDN). Each SM-SC may have connections to other
SM-SC (e.g. PLMN SM-SC). In case that the sending user has required a status report in conjunction with an outgoing
message, a report (positive or negative) shall be sent to the originating SM-TE as soon as this information is available.
As a service provider option, an SM-SC may serve multiple types of accesses.
NOTE 1: The SM-SC shall deliver SM in an appropriate format to the destination SM-TE, this format depends on
the protocol the destination SM-TE is using.
NOTE 2: Speech, telex, facsimile, etc., or a message from a mobile network customer may be input to the SM-SC
by means of a suitable telecommunication service.
UBS:
None.
NBS:
None.
4.1.2 Outgoing message (from the originating SM-TE)
UBS:
The outgoing message from the originating SM-TE shall be sent to the SM-SC and shall contain the address of the
receiving user. The SM-SC shall send a submit report to the originating SM-TE.
NBS:
To initiate an outgoing message the originating SM-TE has to provide the SM text, the sending user's number and the
receiving user's number; further information may be provided by the sending user (e.g. SM-SC number, status report
request, etc.).
ETSI
12 ETSI ES 201 986 V1.2.1 (2003-04)
The outgoing message from the originating SM-TE shall be transferred to the network. The network shall forward this
SM to the SM-SC.
The SM-SC shall send a submit report via the network to the originating SM-TE.
If feasible, any SM may be sent when the originating SM-TE is engaged on a call (e.g. voice or data), or in idle mode.
However, messages which overlap the boundary of such a call, or being manually interrupted by the user, may be lost;
in that case the SM may be sent again.
Submit
(Outgoing message)
Originating SM-TE
Network
Sending user
Submit Report
SM-SC
Figure 2: Outgoing message
4.1.3 Submit report
UBS/NBS:
A submit report is sent to an SM-TE from an SM-SC and may be either a positive report, which confirms the correct
submission of an SM to the SM-SC, or a negative report, which informs the SM-TE that the SM was not successfully
submitted and gives the reason why.
In case of a negative or no submit report, the SM-TE may re-attempt submission of the SM.
UBS:
None.
NBS:
None.
4.1.4 Incoming message (to the destination SM-TE)
UBS/NBS:
The destination SM-TE should store the incoming messages in an appropriate memory. These messages should be
displayed, modified and deleted under control of the user. These functions are out of the scope of the present document.
The incoming message from the SM-SC shall include the date and time when the SM was submitted to the SM-SC.
UBS:
The destination SM-TE shall send a deliver report to the SM-SC.
In case of non-delivery, the SM-SC re-attempts delivery. The timing and the number of repetitions are service provider
options.
ETSI
13 ETSI ES 201 986 V1.2.1 (2003-04)
NBS:
The incoming message shall be transferred from the SM-SC to the receiving user's network. The network shall deliver
this SM to the destination SM-TE. The destination SM-TE shall send a deliver report via the network to the SM-SC.
If feasible, any SM may be received when the destination SM-TE is engaged in a call (e.g. voice or data), or in idle
mode. However, messages which overlap the boundary of such a call, or being manually interrupted by the user, may be
lost; in that case the SM may be sent again.
Deliver
Destination
(Incoming message)
SM-TE
Network
Receiving user
Deliver Report
SM-SC
Figure 3: Incoming message
4.1.5 Deliver report
UBS/NBS:
A deliver report is sent to an SM-SC and may be either a positive report, which confirms the correct delivery of an SM
to the destination SM-TE, or a negative report, which informs the SM-SC that the SM was not successfully delivered
and gives the reason why.
A positive deliver report confirms the correct receipt of an SM at the SM-TE, but not the delivery of the SM to the user.
If a status report has been requested by the sending user and the status report has been delivered, a deliver report is sent
from the originating SM-TE to the SM-SC to acknowledge the receipt of the status report.
In case of a negative or no deliver report, the SM-SC re-attempts delivery of the SM. The timing and the number of
repetitions are service options.
UBS:
None.
NBS:
None.
4.1.6 Message length
UBS/NBS:
A message length of up to 140 octets shall be guaranteed. Longer messages may optionally be allowed; in these cases
interworking with existing message services should be considered.
UBS:
None.
NBS:
None.
ETSI
14 ETSI ES 201 986 V1.2.1 (2003-04)
4.1.7 Character set
UBS/NBS:
The used character set for the short message service is out of the scope of the present document.
UBS:
None.
NBS:
None.
4.1.8 Terminal memory
UBS/NBS:
A terminal that provides SMS capabilities shall be able to store at least one short message with a length of 140 octets.
UBS:
None.
NBS:
None.
4.1.9 Service Centre Time Stamp
UBS/NBS:
The SM-SC shall inform the destination SM-TE about the time of arrival of that SM at the SM-SC. The time value shall
be included in each short message being delivered to the destination SM-TE.
UBS:
None.
NBS:
None.
4.2 Optional service features
4.2.1 Reply path
UBS/NBS:
In conjunction with an outgoing message, the sending user may request the SM-SC to guarantee to forward a single
reply regarding to this message back to him (Reply Path).
As a result of a "Reply Path" request of the sending user, the receiving user of this SM shall get an indication by the
SM-SC that a reply via this SM-SC can be accepted on a non-subscription basis (Reply Path Procedure). The receiving
user may then submit a reply to this SM-SC (within a period of time defined by the SM-SC operator), which is then
forwarded to the originating SM-TE.
No subscription with the service provider is needed by the replying user. The costs, if any, for the reply path are
allocated to the originator.
UBS:
None.
ETSI
15 ETSI ES 201 986 V1.2.1 (2003-04)
NBS:
None.
4.2.2 Validity period
UBS/NBS:
In conjunction with an outgoing message to an SM-SC the sending user may enter, as an additional information, a
specific time period for the validity of the message; i.e. for how long the SM-SC shall guarantee its existence in the
SM-SC memory before delivery to the receiving user has been carried out.
UBS:
None.
NBS:
None.
4.2.3 Encryption or protection
UBS/NBS:
UBS:
To guarantee the privacy of the communication, the originating user may be able to use an encryption or protection on
an outgoing message.
NBS:
None.
4.2.4 Destination m
...