1、 ETSI TS 122 282 V14.3.0 (2017-03) LTE; Mission Critical Data over LTE (3GPP TS 22.282 version 14.3.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 122 282 V14.3.0 (2017-03)13GPP TS 22.282 version 14.3.0 Release 14Reference DTS/TSGS-0122282ve30 Keywords LTE ETSI 650 Route des Lucioles F-06921 Sop
2、hia 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The p
3、resent 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 ve
4、rsions 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
5、 current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification
6、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
7、foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for
8、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 ETSI TS 122 282 V14.3.0 (2017-03)23GPP TS 22.282 version 14.3.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to
9、 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 E
10、TSI 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 ex
11、istence 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 The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM i
12、dentities. 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. Modal verbs terminology In the present document “shall“, “shall not“, “should
13、“, “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
14、 ETSI TS 122 282 V14.3.0 (2017-03)33GPP TS 22.282 version 14.3.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Overview 7g3
15、5 MCData generic capability requirements common for on-network and off-network 7g35.1 Introduction 7g35.2 SDS feature 7g35.2.1 General 7g35.2.2 Requirements 8g35.2.3 Remote Start Requirements Using SDS 8g35.3 File distribution capability 9g35.3.1 General 9g35.3.2 Requirements 9g35.4 Data streaming c
16、apability . 9g35.4.1 General 9g35.4.2 Requirements 9g35.5 IP connectivity 10g35.5.1 Service description 10g35.5.2 Requirements 10g36 MCData specific requirements . 10g36.1 MCData Services common for on network and off network 10g36.1.1 Conversation management including delivery notification 10g36.1.
17、1.1 Service description 10g36.1.1.2 Service requirements . 11g36.1.2 Robots . 11g36.1.2.1 Robots remote control . 11g36.1.2.1.1 Service description 11g36.1.2.1.2 Requirements . 11g36.1.2.2 Robot identification . 12g36.1.2.2.1 Service description 12g36.1.2.2.2 Requirements . 12g36.1.3 MCData enhanced
18、 status 12g36.1.3.1 Service description 12g36.1.3.2 Requirements 13g36.2 MCData Services requirements specific to on-network use . 13g36.2.1 Database enquiries and secured internet access 13g36.2.1.1 Service description 13g36.2.1.2 Requirements 13g36.2.2 Transmission control requirements . 13g36.2.2
19、.1 General 13g36.2.2.2 Receiving data . 14g36.2.2.3 Accessing data . 14g36.2.2.4 Data reconfiguration and termination 14g36.2.3 Communication termination . 14g36.3 MCData Services requirements specific to off-network use 15g36.3.1 Private Communication Off-Network . 15g3ETSI ETSI TS 122 282 V14.3.0
20、(2017-03)43GPP TS 22.282 version 14.3.0 Release 146.3.1.1 Overview . 15g36.3.1.2 Requirements 15g36.3.2 MCData Transmission Control Off-Network . 16g36.3.2.1 Overview . 16g36.3.2.2 General Aspects 16g36.3.2.3 Requesting Permission to Transmit . 16g36.3.2.4 Override 16g36.3.2.5 Terminating Permission
21、 to Transmit . 17g36.3.2.6 Transmit Time Limit . 17g37 Interworking . 17g37.1 Interworking with non LTE data systems . 17g3Annex A (informative): Change history . 18g3History 19g3ETSI ETSI TS 122 282 V14.3.0 (2017-03)53GPP TS 22.282 version 14.3.0 Release 14Foreword This Technical Specification (TS)
22、 has been produced by ETSI 3rd 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
23、 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
24、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 ETSI TS 122 282 V14.3.0 (2017-03)63GPP TS 22.282 version 14.3.0 Release 141 Scope The present document provides the
25、service requirements for operation of the MCData service. MCData makes use of capabilities included in Group Communication System Enablers for LTE (GCSE_LTE), Proximity Services (ProSe), Isolated E-UTRAN operation for Public Safety (IOPS) and Mission Critical Services Common Requirements (MCCoRe) wi
26、th 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). 2 References The following documents contain provisions which, through reference in this text,
27、 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 th
28、e 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 3GP
29、P TS 22.280: “Mission Critical Services Common Requirements“. 4 3GPP TS 22.179: “Mission Critical Push to Talk (MCPTT) over LTE; 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 serv
30、ices over LTE“. 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 3GP
31、P 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 th
32、e 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
33、 ETSI TS 122 282 V14.3.0 (2017-03)73GPP TS 22.282 version 14.3.0 Release 143.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
34、 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, incl
35、uding 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 r
36、elevant 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 LTE networks will allow mission critical users to operate current and new data services whilst relying on the fundamental capabilities of mis
37、sion 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 function
38、s 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 MC
39、Data 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
40、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 en
41、ablers 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 combi
42、ned 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 exist
43、ing 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
44、be marked for extensible purposes including short binary ETSI ETSI TS 122 282 V14.3.0 (2017-03)83GPP TS 22.282 version 14.3.0 Release 14messages for application communication. Messaging could be one-to-one messaging or could be group messaging using groups as specified in MCCoRe. 5.2.2 Requirements
45、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
46、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 MCD
47、ata 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
48、 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
49、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.
