ETSI TR 122 942 V8.1.0 (2009-01)

Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Study on Value Added Services (VAS) for Short Message Service (SMS) (3GPP TR 22.942 version 8.1.0 Release 8)

DTR/TSGS-0122942v810

General Information

• Status: Published
• Publication Date: 29-Jan-2009
• Technical Committee: 3GPP SA 1 - Services
• Current Stage: 12 - Completion
• Due Date: 27-Jan-2009
• Completion Date: 30-Jan-2009

Standards Content (Sample)

ETSI TR 122 942 V8.1.0 (2009-01)
Technical Report

Digital cellular telecommunications system (Phase 2+);
Universal Mobile Telecommunications System (UMTS);
LTE;
Study on Value Added Services (VAS)
for Short Message Service (SMS)
(3GPP TR 22.942 version 8.1.0 Release 8)

---------------------- Page: 1 ----------------------
3GPP TR 22.942 version 8.1.0 Release 8 1 ETSI TR 122 942 V8.1.0 (2009-01)



Reference
DTR/TSGS-0122942v810
Keywords
GSM, LTE, UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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 2009.
All rights reserved.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
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.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TR 22.942 version 8.1.0 Release 8 2 ETSI TR 122 942 V8.1.0 (2009-01)
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).
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 Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
ETSI

---------------------- Page: 3 ----------------------
3GPP TR 22.942 version 8.1.0 Release 8 3 ETSI TR 122 942 V8.1.0 (2009-01)
Contents
Intellectual Property Rights.2
Foreword.2
Foreword.5
1 Scope.6
2 References.6
3 Definitions, symbols and abbreviations .6
3.1 Definitions.6
3.2 Abbreviations.7
4 Use cases.7
4.1 Short Message forwarding.7
4.1.1 Short description.7
4.1.2 Actors.7
4.1.2.1 Actor specific issues.7
4.1.2.2 Actor specific benefits.7
4.1.3 Pre-conditions.7
4.1.4 Post-conditions.7
4.1.5 Normal flow.7
4.1.6 Operational and quality of experience requirements.8
4.2 Short Message forwarding multiple subscriptions .8
4.2.1 Short description.8
4.2.2 Actors.8
4.2.2.1 Actor specific issues.8
4.2.2.2 Actor specific benefits.8
4.2.3 Pre-conditions.8
4.2.4 Post-conditions.8
4.2.5 Normal flow.8
4.2.6 Operational and quality of experience requirements.8
4.3 Short Message filtering .9
4.3.1 Short description.9
4.3.2 Actors.9
4.3.2.1 Actor specific issues.9
4.3.2.2 Actor specific benefits.9
4.3.3 Pre-conditions.9
4.3.4 Post-conditions.9
4.3.5 Normal flow.9
4.3.6 Operational and quality of experience requirements.10
4.4 Short Message receipt .10
4.4.1 Short description.10
4.4.2 Actors.10
4.4.2.1 Actor specific issues.10
4.4.2.2 Actor specific benefits.10
4.4.3 Pre-conditions.10
4.4.4 Post-conditions.10
4.4.5 Normal flow.10
4.4.6 Operational and quality of experience requirements.10
4.5 Short Message network storage.11
4.5.1 Short description.11
4.5.2 Actors.11
4.5.2.1 Actor specific issues.11
4.5.2.2 Actor specific benefits.11
4.5.3 Pre-conditions.11
4.5.4 Post-conditions.11
4.5.5 Normal flow.11
ETSI

---------------------- Page: 4 ----------------------
3GPP TR 22.942 version 8.1.0 Release 8 4 ETSI TR 122 942 V8.1.0 (2009-01)
4.5.6 Operational and quality of experience requirements.11
4.6 Short Message to multiple destinations .12
4.6.1 Short description.12
4.6.2 Actors.12
4.6.2.1a Actor specific issues.12
4.6.2.1b Actor specific issues (recipients privacy protection).12
4.6.2.2a Actor specific benefits.12
4.6.2.2b Actor specific benefits (recipients privacy protection).12
4.6.3 Pre-conditions.12
4.6.4a Post-conditions .12
4.6.4b Post-conditions (recipient privacy protection).13
4.6.5a Normal flow.13
4.6.5b Normal flow (recipient privacy protecting) .13
4.6.6 Operational and quality of experience requirements.13
5 Requirements.16
5.1 Suggested high level requirements.16
5.2 Overall system requirements .16
5.2.1 Management of service information .16
5.2.2 Short Message processing.17
5.2.3 Short Message forwarding.17
5.2.4 Short Message network storage .17
5.2.5 Short Message to multiple destinations .17
5.2.6 Management and control of network based repository.17
5.2.7 Addressing.18
6 Requirements for service priority and interaction.18
7 Quality of service .18
8 Charging aspects for VAS-SMS.19
9 Security.19
10 Interworking.19
11 Roaming.20
12 Conclusions.20
Annex A: Change history .21
History .22


ETSI

---------------------- Page: 5 ----------------------
3GPP TR 22.942 version 8.1.0 Release 8 5 ETSI TR 122 942 V8.1.0 (2009-01)
Foreword
rd
This Technical Report has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI

---------------------- Page: 6 ----------------------
3GPP TR 22.942 version 8.1.0 Release 8 6 ETSI TR 122 942 V8.1.0 (2009-01)
1 Scope
The present document studies the service requirements associated with series of value-added features for short message
service (SMS). Specifically, the objective of this document is to study potential new value-added services for SMS in
3GPP that need to be standardized.
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. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[3] ITU-T E.164 (1997): "The International Public Telecommunications Numbering Plan".
[4] IETF STD 0011 (RFC 2822): "Internet Message Format"
URL: http://www.ietf.org/rfc/rfc2822.txt.
[5] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol
(IP) access".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in [1] and the following apply:
Short Message Forwarding: The service permits the network to send all incoming short messages addressed to the
called mobile subscriber's directory number to another directory number.
Short Message Filtering: The service permits the network to filter certain short messages on behalf of a called party
based on the called party’s preferences.
Short Message Receipt: The service permits the network to send one or more receipts to inform a calling party the
status of sent message.
Short Message Network Storage: The service permits the network to help the subscriber store messages that the
subscriber has sent or received.
SMS VPN service enables exchange of SMS messages between VPN (Virtual Private Network) members by using a
short number, usually similar to the receiver fixed extension number, instead of using the full mobile number of the
recipient.
SMS Auto Reply: The SMS Auto Reply service enables the subscriber to activate an automatic SMS reply in response
to incoming SMS messages, both from in network subscribers as well as from foreign networks subscribers (incoming
MT messages from foreign networks).
ETSI

---------------------- Page: 7 ----------------------
3GPP TR 22.942 version 8.1.0 Release 8 7 ETSI TR 122 942 V8.1.0 (2009-01)
SMS Personal Signature: The service allows the end user to personalize its outgoing messages either with a personal
remark or a business title. The service enables a user to pre-define a text that will automatically be added to all outgoing
SMS messages
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply in addition to [1]:
SMS-SC Short Message Service - Service Centre
SM Short Message
VAS-SMS Value-added Services for SMS
4 Use cases
4.1 Short Message forwarding
4.1.1 Short description
This use case describes a scenario where a called mobile subscriber forward incoming messages to another mobile
phone.
4.1.2 Actors
Joe is an SMS user of Operator A.
Sally is an SMS user of Operator B.
Note: Operator A and Operator B may be the same
4.1.2.1 Actor specific issues
Joe wants to send an SM to Sally.
Sally is roaming outside of Operator B. She brings another mobile phone with her.
4.1.2.2 Actor specific benefits
Sally can take advantage of Short Message Forwarding Service.
4.1.3 Pre-conditions
Joe is an SMS subscriber.
Sally is subscribed to the Short Message Forwarding Service on her home network.
She sets the SM forwarding number for her original mobile phone, and wants to use another mobile phone to receive
incoming SM.
4.1.4 Post-conditions
All incoming messages addressed to Sally’s original mobile phone number are forwarded to another mobile phone.
4.1.5 Normal flow
- Sally prepares to travel outside coverage of Operator B.
- She sets the SM forwarding number of her original mobile phone.
ETSI

---------------------- Page: 8 ----------------------
3GPP TR 22.942 version 8.1.0 Release 8 8 ETSI TR 122 942 V8.1.0 (2009-01)
- Joe sends an SM to Sally with receiving number as Sally’s original number.
- Sally receives the message by using another mobile phone.
4.1.6 Operational and quality of experience requirements
It shall be supported that users can set certain conditions (e.g., different time periods) for message forwarding. There are
no significant delays to any part of the service.
4.2 Short Message forwarding multiple subscriptions
4.2.1 Short description
This use case describes a scenario where an SM to a mobile subscriber may be forwarded to an alternative address,
depending on the original delivery address being registered on the network or not.
4.2.2 Actors
Joe is an SMS user with home operator A.
Sally is an SMS user with home operator B.
4.2.2.1 Actor specific issues
Joe wants to send an SM to Sally.
Sally can use two different subscriptions with different MSISDNs[3], and she wants to receive SMs on the subscription
that is in use (active). She may use two different phones or two different subscriptions from the same operator.
4.2.2.2 Actor specific benefits
The called party will have the SM delivered to the phone/subscription that is in use.
4.2.3 Pre-conditions
Joe is an SMS subscriber.
Sally has subscribed to the Short Message Forwarding ("multiple subscriptions") Service.
Sally has activated SM forwarding from her first phone/subscription to the second phone/subscription.
Sally’s second phone/subscription is in use. The first phone/subscription is switched off/not active.
4.2.4 Post-conditions
All incoming messages addressed to Sally’s first mobile phone number are forwarded to her second phone/subscription.
4.2.5 Normal flow
- Joe sends an SM addressed to Sally’s first number.
- Sally receives the message on the phone/subscription that is in use.
4.2.6 Operational and quality of experience requirements
It may be supported that an operator can set a group of subscriptions for which SM are forwarded to the active/last
activated subscription of that group, under the condition that the delivery address of the SM is associated to a
subscription of that group and that address is not registered on the network.
ETSI

---------------------- Page: 9 ----------------------
3GPP TR 22.942 version 8.1.0 Release 8 9 ETSI TR 122 942 V8.1.0 (2009-01)
4.3 Short Message filtering
4.3.1 Short description
The users do not want to receive trash or malicious messages. Some users are not allowed to send messages to premium
numbers.
This use case describes how a network can help the user filter SM based on the users’ (called/calling party) preferences
(e.g. calling/called party’s number, time to send message etc.).
4.3.2 Actors
Alice is an SMS user of Operator A. Bob is an SMS user of Operator A.
Sally is an SMS user of Operator B.
Tom is an SMS user. He is a youngster.
4.3.2.1 Actor specific issues
Alice sends an SM to Sally at 13:30PM.
Bob sends an SM to Sally.
Sally doesn’t want to receive any messages from Bob and these are identified as "not wanted". Neither does she want to
receive any messages from 13:00 to 14:00. Any messages sent during this period and that are not marked as "not
wanted" should be stored and/or sent to Sally after the period defined by Sally. She sets the SMS filtering function via
her mobile phone.
Tom is not allowed to send SMS to pre-defined numbers
4.3.2.2 Actor specific benefits
The called party, Sally can take advantage of SM Filtering Service.
The calling party, Tom takes advantage of SMS filtering service
4.3.3 Pre-conditions
Alice and Bob are SMS subscribers.
Sally is subscribed to the SM Filtering Service.
Sally adds Bob’s phone number to the black list for the SM Filtering Service.
Tom’s parents subscribed Tom to the SMS filtering services.
4.3.4 Post-conditions
Sally doesn’t receive any messages from Bob.
Sally doesn’t receive any messages during time period from 13:00 to 14:00.
Tom is not able to send SMS to pre-defined numbers
4.3.5 Normal flow
- Sally doesn’t want to receive Bob’s messages.
- Sally adds Bob’s phone number to her black list for the SM Filtering Service.
ETSI

---------------------- Page: 10 ----------------------
3GPP TR 22.942 version 8.1.0 Release 8 10 ETSI TR 122 942 V8.1.0 (2009-01)
- Bob sends SMs to Sally.
- Sallys' home network doesn’t forward Bobs messages to Sally.
4.3.6 Operational and quality of experience requirements
It shall be supported that users can set certain conditions for message filtering.
4.4 Short Message receipt
4.4.1 Short description
This use case describes a scenario where Joe receives two SM Receipts after he sent an SM to Sally. One message
receipt (aka. caller message receipt) is requested by Joe to indicate the transmit status of the message; the other message
receipt (aka. callee message receipt) is from Sally, customized for Joe.
4.4.2 Actors
Both Joe and Sally are SMS users.
4.4.2.1 Actor specific issues
Joe sends an SM to Sally.
4.4.2.2 Actor specific benefits
Joe can know the sent messages’ transmitting status (e.g., successful, failure, temporarily failure) in time. Sally can set a
specific quick response for messages from Joe.
4.4.3 Pre-conditions
Joe is an SMS subscriber.
Joe is subscribed to the SM Receipt (caller message receipt) Service on his home network.
Sally is subscribed to the SM Receipt (callee message receipt) Service on her home network and sets a callee message
receipt for Joe.
4.4.4 Post-conditions
Joe can obtain the status of all messages he has sent.
4.4.5 Normal flow
- Joe sends a message to Sally.
- Joe receives a caller message receipt: Your message sent to Sally is successful.
- Sally receives the message Joe has sent.
- The network sends the receipt to Joe with the following content: "Joe, I am now in the meeting, and I will phone
you later". No interaction with Sally (or her UE) is required.
- Joe receives Sally’s callee message receipt.
4.4.6 Operational and quality of experience requirements
It shall be supported that the callee can set different content of the receipt for different callers.
ETSI

---------------------- Page: 11 ----------------------
3GPP TR 22.942 version 8.1.0 Release 8 11 ETSI TR 122 942 V8.1.0 (2009-01)
The SMS receipt can be accompanied by a newly generated SM with the content provided by the operator.
4.5 Short Message network storage
4.5.1 Short description
Users want to store their daily messages (either sent or received), but there is limited storage in their mobile phone. The
network helps to store the users’ messages. The network duplicates the user
...