|
TECHNICAL SPECIFICATION
LTE;
Mission Critical Data over LTE
(3GPP TS 22.282 version 15.1.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 22.282 version 15.1.0 Release 15 1 ETSI TS 122 282 V15.1.0 (2018-07)
Reference
RTS/TSGS-0122282vf10
Keywords
LTE
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 TS 22.282 version 15.1.0 Release 15 2 ETSI TS 122 282 V15.1.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 Specification (TS) 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 "shall", "shall not", "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 TS 22.282 version 15.1.0 Release 15 3 ETSI TS 122 282 V15.1.0 (2018-07)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 7
4 Overview . 7
5 MCData generic capability requirements common for on-network and off-network . 7
5.1 Introduction . 7
5.2 SDS feature . 7
5.2.1 General . 7
5.2.2 Requirements . 8
5.2.3 Remote Start Requirements Using SDS. 8
5.3 File distribution capability . 8
5.3.1 General . 8
5.3.2 Requirements . 9
5.4 Data streaming capability . 9
5.4.1 General . 9
5.4.2 Requirements . 9
5.5 IP connectivity . 10
5.5.1 Service description . 10
5.5.2 Requirements . 10
6 MCData specific requirements . 10
6.1 MCData Services common for on network and off network . 10
6.1.1 Conversation management including delivery notification . 10
6.1.1.1 Service description . 10
6.1.1.2 Service requirements . 10
6.1.2 Robots . 11
6.1.2.1 Robots remote control . 11
6.1.2.1.1 Service description . 11
6.1.2.1.2 Requirements . 11
6.1.2.2 Robot identification . 12
6.1.2.2.1 Service description . 12
6.1.2.2.2 Requirements . 12
6.1.3 MCData enhanced status . 12
6.1.3.1 Service description . 12
6.1.3.2 Requirements . 12
6.2 MCData Services requirements specific to on-network use . 13
6.2.1 Database enquiries and secured internet access . 13
6.2.1.1 Service description . 13
6.2.1.2 Requirements . 13
6.2.2 Transmission control requirements . 13
6.2.2.1 General . 13
6.2.2.2 Receiving data . 14
6.2.2.3 Accessing data . 14
6.2.2.4 Data reconfiguration and termination. 14
6.2.3 Communication termination . 14
6.3 MCData Services requirements specific to off-network use . 15
6.3.1 Private Communication Off-Network . 15
6.3.1.1 Overview . 15
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 22.282 version 15.1.0 Release 15 4 ETSI TS 122 282 V15.1.0 (2018-07)
6.3.1.2 Requirements . 15
6.3.2 MCData Transmission Control Off-Network . 15
6.3.2.1 Overview . 15
6.3.2.2 General Aspects . 16
6.3.2.3 Requesting Permission to Transmit . 16
6.3.2.4 Override . 16
6.3.2.5 Terminating Permission to Transmit . 17
6.3.2.6 Transmit Time Limit . 17
7 Interworking . 17
7.1 Interworking with non 3GPP data systems . 17
Annex A (informative): Change history . 18
History . 19
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 22.282 version 15.1.0 Release 15 5 ETSI TS 122 282 V15.1.0 (2018-07)
Foreword
rd
This Technical Specification 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 TS 22.282 version 15.1.0 Release 15 6 ETSI TS 122 282 V15.1.0 (2018-07)
1 Scope
The present document provides the service requirements for operation of the MCData service. MCData makes use of
capabilities included in Group Communication System Enablers, Proximity Services, Isolated E-UTRAN operation for
Public Safety and Mission Critical Services Common Requirements with additional requirements specific to the
MCData Service. The MCData Service can be used for public safety applications and also for general commercial
applications (e.g., utility companies and railways). The requirements in this specifications do not apply to GSM or
UMTS.
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 TR 41.001: "GSM Specification set".
[3] 3GPP TS 22.280: "Mission Critical Services Common Requirements".
[4] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
[5] ETSI TS 100 392-2 v.3.7.1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 2:
Air Interface (AI)
[6] 3GPP TS 22.281: "Mission Critical Video services".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP
TR 21.905 [1].
Conversation: A series of messages that are linked to the same topic within a group or one-to-one data communication.
Conversation ID: An identifier that uniquely identifies a conversation within a group or one-to-one data
communication.
MCData Conversation Hang Time: The time from the transmission of an MCData message after which a subsequent
MCData message is no longer considered to be linked to the previous one.
MCData System: The collection of applications, services, and enabling capabilities required to provide Mission
Critical Data for a Mission Critical Organization.
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 22.282 version 15.1.0 Release 15 7 ETSI TS 122 282 V15.1.0 (2018-07)
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
IOPS Isolated E-UTRAN Operation for Public Safety
SDS Short Data Service
4 Overview
MCData defines a service for Mission Critical Data services. As well as voice services, current mission critical users
have been increasing their use of data services, including low throughput services on legacy networks and data services
on commercial networks. This need will continue to grow with the creation of the new multimedia services. The
MCData service needs to provide a means to manage all data connections of mission critical users in the field and
provide relevant resources to the ones who need it. For example mission critical users already use event manager
software along with the voice system. The migration to 3GPP networks will allow mission critical users to operate
current and new data services whilst relying on the fundamental capabilities of mission critical communication such as
defined for MCPTT in [4] and included into MCCoRe [3].
The MCData Service provides a set of communication services that will be directly used by the user or functions that
will be called by external applications in control rooms.
The MCData Service will reuse functions including end-to-end encryption, key management, authentication of the
sender, etc. defined in [3] in order to provide group communications for data services. As for all mission critical
services, users affiliate to groups in order to receive communications directed to the group.
In addition, the MCData Service will provide a set of generic capabilities such as: messaging, file distribution, data
streaming, IP proxy, etc. Also, the MCData Service will provide specific services such as conversation management,
data base enquiries, internet access, robots control.
The MCData Service is expected to have open interfaces in the network. It needs also to provide an opportunity for a
variety of multimedia applications using the MCData Service.
5 MCData generic capability requirements common for
on-network and off-network
5.1 Introduction
MCData makes frequent use of a set of capabilities and enablers that allows for many end user services to be built on a
common foundation. Several generic capabilities are defined for use in the MCData Service. These capabilities can be
used on their own to transfer files, messages and other content to individuals and affiliated members of groups or
combined with other services, through an application, to provide complete end users services as determined by the
authorities implementing the service. The MCData generic capabilities are common for on-network and off-network.
It is not intended to invent new protocols for the MCData Service. Where existing protocols are efficient and sufficient,
the service should make use of these protocols.
5.2 SDS feature
5.2.1 General
The SDS feature of the MCData Service could be considered as a basic protocol carrying a limited size, but variable
content, payload message. This message could be text or could be marked for extensible purposes including short binary
messages for application communication. Messaging could be one-to-one messaging or could be group messaging using
groups as specified in MCCoRe.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 22.282 version 15.1.0 Release 15 8 ETSI TS 122 282 V15.1.0 (2018-07)
5.2.2 Requirements
[R-5.2.2-001] The MCData Service shall provide an SDS feature for conveyance of limited size, variable content,
messages.
[R-5.2.2-002] The MCData SDS shall provide a group service to affiliated members with policy assertion capabilities
(e.g. certain types of message or content may only be relevant to certain members of a group due, for example, to
location).
[R-5.2.2-003] The MCData SDS shall provide a one to one service with policy assertion capabilities (e.g. policy to limit
certain types of message or content to certain users due, for example, to location or user privilege).
[R-5.2.2-004] The MCData SDS shall provide the option to include a content payload of at least [1000] characters of 8
bit text or [500] characters of 16 bit text or [250] characters of 32 bit text and the necessary character encoding
information (for example to identify alphabet used).
[R-5.2.2-005] The MCData SDS shall provide the option to include a content payload of at least [1000] characters of
hyperlink or interleaved text and hyperlink(s) to allow subsequent access to linked content (which may be a large file).
[R-5.2.2-006] The MCData SDS shall provide the option to include a content payload of at least [1000] bytes of binary
data to be used by a local running application and the necessary addressing detail to identify the intended application.
[R-5.2.2-007] The MCData SDS shall provide a message thread indication so that multiple message flows can be
managed independently.
[R-5.2.2-008] When replying to a message on the MCData SDS or sending any message which should be coupled with
previously sent or received messages or message flows; the message thread indication shall use the same indication as
was used for those previous messages.
[R-5.2.2-009] The MCData SDS shall provide a selectable read receipt indication. When requested, the receiving entity
shall provide receipt indication for delivered and read messages as appropriate.
NOTE 1: The read indication will implicitly indicate delivered as well.
[R-5.2.2-010] The MCData SDS shall provide a configurable read receipt indication. When configured, the receiving
entity shall provide receipt indication addressed to the application for delivered and read messages as appropriate.
NOTE 2: The read indication will implicitly indicate delivered as well.
[R-5.2.2-011] The MCData SDS shall permit delivery history interrogation for suitably authorized users.
[R-5.2.2-012] The MCData SDS shall provide the option to add a field indicating location of the sending user/UE.
[R-5.2.2-013] The MCData SDS shall allow empty messages including only a field indicating location of the sending
user/UE.
5.2.3 Remote Start Requirements Using SDS
[R-5.2.3-001] SDS content received in a UE, addressed to a known local application that is not yet running shall cause
the UE to start the local application and pass the content to the application. This could be used to start an application
and pass to it the initial data.
[R-5.2.3-002] The MCData SDS shall provide the capability to remotely start a local application (e.g. situational
awareness). This may be through specific use of binary payload on theSDS.
5.3 File distribution capability
5.3.1 General
File distribution is a fundamental capability of the MCData Service. File distribution can be used to provide a
standalone file transfer capability or can be invoked by a controlling application to support the purpose of the
application.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 22.282 version 15.1.0 Release 15 9 ETSI TS 122 282 V15.1.0 (2018-07)
5.3.2 Requirements
[R-5.3.2-001] The MCData Service shall provide a file distribution capability.
[R-5.3.2-002] The MCData file distribution capability shall provide a service to allow a user to send a file to any
combination of individual users and/or affiliated groups.
[R-5.3.2-003] The MCData file distribution capability shall provide an option for each recipient to choose to receive the
file or not (e.g. by storing the file and sending a link (URL) to all relevant members).
NOTE 1: By using this capability a user can choose when to receive the file.
[R-5.3.2-004] The MCData file distribution capability shall allow a user to reject to receive the file where appropriate.
[R-5.3.2-005] The MCData file distribution capability shall provide a sending user selectable indication for mandatory
download so that the UE, for all relevant receiving members, will automatically download the file.
NOTE 2: The mandatory indication provides a system level capability and could be invoked automatically by need
of the application or might be provided for selection by the user.
[R-5.3.2-006] The MCData file distribution capability shall provide download complete indications for each recipient
successfully downloading the file.
[R-5.3.2-007] The MCData file distribution capability shall allow the sender to select to send the file immediately to all
chosen users.
[R-5.3.2-008] The MCData file distribution capability shall make use of available system delivery efficiencies for
distribution of common information to users within a specific geographic area and able to receive at the same time.
[R-5.3.2-009] The MCData file distribution capability shall allow a user to cancel distribution of files they have sent,
but have not been delivered.
[R-5.3.2-010] The MCData file distribution capability shall allow an authorised user to cancel distribution of files being
sent or waiting to be sent.
5.4 Data streaming capability
5.4.1 General
Data streaming is a fundamental capability of the MCData Service. Data streaming can be used to provide a standalone
data streaming capability or can be invoked by a controlling application to support the purpose of the application.
5.4.2 Requirements
[R-5.4.2-001] The MCData Service shall provide a data streaming capability.
[R-5.4.2-002] The MCData data streaming capability shall provide an option that allows each recipient to choose to
receive the data stream or not (e.g. by sending a link (URL) to all relevant members).
[R-5.4.2-003] The MCData data streaming capability shall allow a user to reject to receive the datastream.
[R-5.4.2-004] The MCData data streaming capability shall provide a sending user selectable indication for automatic
reception by the UE.
[R-5.4.2-005] The MCData data streaming capability shall provide start and stop records to the sender for each recipient
successfully receiving the data stream.
[R-5.4.2-006] The MCData data streaming capability shall make use of available system delivery efficiencies for
streaming of common information to users within the same relevant area and able to receive at the same time.
[R-5.4.2-007] The MCData data streaming capability shall allow a user to cancel streaming of data they have initiated
including data remaining buffered in the system waiting to be streamed.
[R-5.4.2-008] The MCData data streaming capability shall allow an authorised user to terminate streaming of data being
sent and cancel streaming of data remaining buffered in the system waiting to be streamed.
ETSI
---------------------- Page:
...