|
TECHNICAL REPORT
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Study of haptic services requirements
(3GPP TR 22.987 version 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TR 22.987 version 15.0.0 Release 15 1 ETSI TR 122 987 V15.0.0 (2018-07)
Reference
RTR/TSGS-0122987vf00
Keywords
GSM,LTE,UMTS
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
The present document can be downloaded from:
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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
If you find errors in the present document, please send your comment to one of the following services:
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TR 22.987 version 15.0.0 Release 15 2 ETSI TR 122 987 V15.0.0 (2018-07)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 (https://ipr.etsi.org/).
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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
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
.
Modal verbs terminology
In the present document "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be
interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TR 22.987 version 15.0.0 Release 15 3 ETSI TR 122 987 V15.0.0 (2018-07)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 4
1 Scope . 5
2 References . 5
3 Definitions . 5
4 General description. 6
4.1 Introduction . 6
4.2 Benefits . 6
4.3 Haptic technology. 6
4.3.1 Overview . 6
4.3.2 User equipments . 7
4.3.3 Haptic information format . 7
4.3.4 Telecommunication networks . 7
4.4 Service Concept . 7
5 Use Case . 8
5.1 Haptic Emoticon Delivery Service . 8
5.1.1 Description . 8
5.1.2 Procedure . 8
5.1.3 Requirements . 9
5.1.4 Benefits . 9
5.2 Customized Alerting Haptic Service . 9
5.2.1 Description . 9
5.2.2 Procedure . 9
5.2.3 Requirements . 9
5.2.4 Benefits . 10
5.3 Call Waiting Alerting Haptic Service . 10
5.3.1 Description . 10
5.3.2 Procedure . 10
5.3.3 Requirements . 11
5.3.4 Benefits . 11
5.4 Accident or Health Crisis Haptic Service . 11
5.4.1 Description . 11
5.4.2 Procedure . 11
5.4.3 Requirements . 12
5.4.4 Benefits . 12
6 High level service requirements . 12
6.1 General requirements . 12
6.2 Network requirements . 13
6.3 UE requirements . 13
6.4 Interworking requirements . 13
6.5 Data description requirements . 13
6.6 Charging requirements . 13
7 Relation to Open Mobile Allicance (OMA) . 14
8 Conclusion . 14
Annex A: Change history . 15
History . 16
ETSI
---------------------- Page: 4 ----------------------
3GPP TR 22.987 version 15.0.0 Release 15 4 ETSI TR 122 987 V15.0.0 (2018-07)
Foreword
rd
This Technical Report has been produced by the 3 Generation Partnership Project (3GPP) Secretariat on behalf of the
3GPP Technical Specification Groups (TSGs).
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.
The present document is based ISO/IEC Directives. Most clauses of the ISO/IEC document have been retained, while
some clauses have been modified or deleted. Additional material has been inserted.
Items concerning word-processor specific layout and formatting matters when using the Microsoft Word for Windows
based skeleton documents and templates are shown with shaded background. Boiler plate text (i.e. text which shall be
directly used in 3GPP specifications) is represented by italic characters.
ETSI
---------------------- Page: 5 ----------------------
3GPP TR 22.987 version 15.0.0 Release 15 5 ETSI TR 122 987 V15.0.0 (2018-07)
1 Scope
This Technical Report aims to present use cases in telecommunication services that are developed by applying haptic
technology. It also justifies accepting haptic technology in telecommunication services by investigating readiness for its
use in the telecommunication system and the level of benefit for the user experience.
For such purpose this document investigates following questions:
- Provide the overview of current haptic technology which might be deployed in telecommunication
- Identify any adaption required for existing services enhanced by supporting the delivery of haptic sense
- Identify key aspects of new services built on capabilities provided by haptic technology
- Identify and specify general requirements for delivery of haptic sense in telecommunication networks
- Identify the scope and roles of 3GPP for mobile haptic services and consult with OMA to coordinate on the
development of mobile haptic services
Note that this Technical Report considers all types of telecommunication networks within the scope of 3GPP, including
mobile networks and IMS-based fixed networks, etc.
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 22.101: "Service Principles".
3 Definitions
For the purposes of the present document, the following terms and definitions apply.
Haptic (Haptic Sense): Haptic is a sense perceived by touching an object. It involves tactile senses, (from the Latin,
tangere, to touch), which refers to the touching of surfaces, and kinaesthetic senses (from the Greek, kinesis, movement
and aesthesis, perception), or the sensing of movement in the body.
Haptic Information: Haptic Information is signal that is delivered over telecommunication networks to generate
Haptic Feedback in the UE. Haptic Information may contain sender and receiver addresses, data types, haptic feedback
data, and others.
Haptic Feedback: Haptic Feedback is a haptic sense generated in the UE.
Haptic Service: A Haptic Service indicates any communication-related services that involve delivering haptic. The
haptic can be initiated either by the network or the user.
Local Party (Sender): the local party is the entity that sends Haptic Information.
Remote Party (Receiver): the remote party is the entity to which Haptic Information is sent.
ETSI
---------------------- Page: 6 ----------------------
3GPP TR 22.987 version 15.0.0 Release 15 6 ETSI TR 122 987 V15.0.0 (2018-07)
4 General description
4.1 Introduction
Telecommunication has evolved over time by expanding the variety of senses it can deliver. Originally supporting voice
calls, the telecommunication system conveyed auditory sense stimulation. After SMS, and then MMS introduction,
users were provided visual sense stimulation by conveying messages in a written and image/graphical form. Recent
telecommunication systems have extended the visual stimulation by adding motion video capabilities. In spite of these
service enhancements, telecommunication is yet to provide a full range of sensory expression and input, used in human
face to face communication and activities.
One sense that has drawn attention rapidly is haptic. The word ‘Haptic’ originated from Greek haptesthai, which means
“to touch.” Haptic involves tactile senses, (from the Latin, tangere, to touch), which refers to the touching of surfaces,
and kinaesthetic senses (from the Greek, kinesis, movement and aesthesis, perception), or the sensing of movement in
the body.
Haptic has been one of major sources for human being to collect information in the external environment and has also
been used in communication between people, such as expressing intimacy by touch. Recent development in haptic
feedback devices made it possible to provide haptic feedback to users and has been applied in a wide range of fields.
For example, game controllers such as joysticks and steering wheels are able to provide haptic feedback that simulates
the tactile sense and/or kinaesthetic sense (i.e. force feedback) a player in the game might experience in the virtual
environment.
Contrary to the examples above, in telecommunication systems, haptic has been neglected as the UEs are not ready for
haptic services. Even though most mobile devices support vibration, it was not programmable, and thus its use is
confined to playing silent ring tones. But recent devices are beginning to adopt a more advanced haptic feature that
supports programmable vibrations varying in length, frequency and magnitude. Moreover, it is expected that in the near
future mobile devices is expected to adopt various haptic feedback other than vibrotactile device enabling the delivery
of temperature, texture or electronic stimulus more apparent. With the introduction of haptic enabled devices, it is now
timely to evaluate the benefits of deploying haptic services in telecommunication networks, and evaluate the feasibility
and efforts to implementing them.
4.2 Benefits
By supporting the delivery of haptic sense in telecommunication networks, network operators can provide a more
enhanced way of communication in terms of information accessibility and receptiveness to subscribers.
From subscribers’ point of view, haptic sense is an appropriate medium through which distinctive and intuitive
messages can be conveyed. Alert messages in haptic sense can help reduce cognitive load and provide additional
information compared to the messages transferred via sound. Also, it can also be used in distractive and loud
environments. Moreover, when haptic sense combines with auditory or visual sense, the multimodal feedback is known
to reinforce the receptiveness of messages. Such multimodal feedback can also help users with visual or hearing
disabilities understand messages more clearly.
From network operators’ viewpoint, the most obvious benefit is that it enables to provide new services built upon haptic
sense, which has not been utilized in previous telecommunication services. Note that in addition to providing new
services based solely on haptic sense, it is also possible to add haptic sense to existing supplementary services. For
example, warning, alert or confirmation messages that have been delivered through audio channel can be delivered with
a combination of sound and haptic sense. By introducing new services and/or extending existing services with haptic
sense, operators can have additional source of revenue. In summary, the addition of haptic sense helps operators enrich
existing services, as well as to develop new services.
4.3 Haptic technology
4.3.1 Overview
The prerequisite for providing mobile haptic service is that the UEs should be able to generate appropriate haptic sense
based on the haptic information delivered through the network. To this end, three components should be prepared: 1)
UEs that generate haptic senses, 2) haptic information format that both UEs and networks can understand, and 3)
telecommunication networks that deliver haptic information for haptic senses.
ETSI
---------------------- Page: 7 ----------------------
3GPP TR 22.987 version 15.0.0 Release 15 7 ETSI TR 122 987 V15.0.0 (2018-07)
4.3.2 User equipments
A number of UEs already support the generation of haptic feedback due to the rapid development of haptic components
that are simple and small enough to be adopted in mobile devices. Until now the most of available haptic devices are
those with high-fidelity vibration. Such devices usually include vibration actuators that provide high-fidelity vibration
effects and a vibration player that controls the operation of the actuator. Moreover, given the trend of fast developing
haptic feedback devices such as thermal display, electrostatic feedback device or tactile display, the number of UEs
supporting haptic service and the variety of senses they support are likely to increase quickly.
4.3.3 Haptic information format
While more and more handsets supporting haptic senses are available, a standardized haptic information representation
formats should be developed for haptic services. The absence of standardized haptic information representation formats
has prevented possible applications from being developed in telecommunication networks. While there are some
standardization activities outside 3GPP, efficient and clear representation for telecommunication services need to be
1
defined.
4.3.4 Telecommunication networks
Without the standardized haptic information format and the related protocols, telecommunication networks are not yet
ready support haptic service. Therefore the haptic information representation formats and the protocols for their
delivery through telecommunication networks should be the main focus of standardization.
4.4 Service Concept
Haptic service requires the delivery of haptic information from the sending party, either user or the network, to the
receiving party(s). An application in the receiving party’s UE converts haptic information to perceivable haptic
feedback.
The kind of haptic sense is not limited, as long as the UE is able to generate the sense. Examples of haptic senses
include, but are not limited to, vibrotactile sense, shear sense, thermal sense, and pneumatic sense.
As haptic can be combined with other senses or can even replace other senses that have been used in delivering
messages, theoretically every service in telecommunication can incorporate haptic.
Below several categorizations of haptic services are introduced.
1. By the timing of haptic information delivery:
- Asynchronous (alert message, SMS enriched with haptic information, …)
- Synchronous (haptic information shared in real time during communication between two persons)
2. By the entity that initiates the delivery of haptic information:
- Network-initiated services
- User-initiated services
3. By the stage of communication:
1
For example, the International Organization for Standardization (ISO) Technical Committee on Ergonomics (TC159) has started to standardize
haptic technology in Working Group 9 “Tactile and Haptic Interaction since 2005. A more detailed introduction can be found in this
publication: http://www.springerlink.com/content/u25hw52p50488180/
ETSI
---------------------- Page: 8 ----------------------
3GPP TR 22.987 version 15.0.0 Release 15 8 ETSI TR 122 987 V15.0.0 (2018-07)
Table 1: Category of Haptic Service
Category Description Expected Needs Examples
1. Idle Status when a subscriber does not engage - Receive relevant, but not
Status in any communication activity through critical information, in not
telecommunication network intrusive way
2. The status when a calling subscriber is - Express unique identity - Customized alerting haptic
Connecting establishing connection to a receiving when calling or identify the service
Status subscriber, caller without directly
checking the screen or
sound through speaker
3. Calling The status when a subscriber is engaged in - Express one’s message - Haptic emoticon delivery
Status a communication activity through and sentiment in a richer service
telecommunication network, such as voice and more delicate way - Call waiting haptic service
call or SMS through haptic information
- Receive important signals
from the network during the
call
5 Use Case
5.1 Haptic Emoticon Delivery Service
5.1.1 Description
The Haptic Emoticon Delivery Service is a service that delivers haptic information or ‘haptic emoticon’ during
communication. According to the type of communication, the Haptic Emoticon Delivery Service can be divided into
synchronous service and asynchronous service. An example of synchronous service is the Haptic Emoticon Delivery
Service in a voice/video call, and that of asynchronous service is the Haptic Emoticon Delivery Service in messaging
services, such as SMS, MMS, and IM service.
Firstly in a voice or video call, the Haptic Emoticon Delivery Service helps the sending party to express a certain
feeling, emotion, or other information implicitly by the haptic feedback generated in the receiving party, while talking
during the voice or video call. The example of such haptic feedback includes a heartbeat or laughter.
Secondly when a subscriber is communicating via SMS, MMS or IM service, the Haptic Emoticon Delivery Service
allows the sending party to express a certain feeling, emotion, or other information implicitly by the haptic feedback
generated in the receiving party when the receiving party checks the message. The example of such haptic feedback
includes a heartbeat or laughter.
5.1.2 Procedure
For an illustrative purpose, suppose two subscribers, Joe and Sally, are engaged in a voice or video call.
- While talking, Joe wants to express his joy by generating haptic feedback that represents ‘laughter’ in Sally’s UE.
- Joe initiates the intended Haptic Emoticon Delivery Service by shaking his UE vertically for example.
- An application in the Joe’s UE recognizes the movement, and notifies the network that it should deliver haptic
information that represents laughter to Sally’s UE.
- The network delivers the haptic information to Sally’s UE.
- When Sally’s UE receives the incoming haptic information from the network, the application in the Sally’s UE
generates haptic feedback based on the haptic information.
- As a consequence, Sally receives the haptic feedback representing Joe’s emotion while talking.
The service procedure in messaging is slightly different.
- While sending SMS or MMS or talking through the IM service, Joe wants to express his joy by generating haptic
feedback that represents ‘laughter’ in Sally’s UE when Sally checks the message.
ETSI
---------------------- Page: 9 ----------------------
3GPP TR 22.987 version 15.0.0 Release 15 9 ETSI TR 122 987 V15.0.0 (2018-07)
- In order for the network to deliver to the Sally’s UE the haptic information that represents ‘laughter’, Joe attaches
the text string such as ‘/laughter/’ within the message.
- The network delivers the haptic information to Sally’s UE.
- When Sally checks the message, the application in the Sally’s UE generates haptic feedback based on the incoming
haptic information from the network.
- As a consequence, Sally receives the haptic feedback representing Joe’s emotion while receiving SMS, MMS, or
IM message.
5.1.3 Requirements
When the sending party attempts to send haptic information to the receiving party(s), for example by shaking the UE or
mobile-initiated USSD operation, the network should support the delivery of the haptic information.
When the sending party wants the receiving party’s UE to generate haptic feedback, the network should deliver the
haptic info
...