ETSI TS 122 368-2017 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Service requirements for Machine-Type Communi_1.pdf

1、 ETSI TS 1Digital cellular telecommUniversal Mobile TelSerfor Machine-T(3GPP TS 22.3TECHNICAL SPECIFICATION122 368 V13.2.0 (2017mmunications system (Phase elecommunications System (LTE; ervice requirements Type Communications (MTC)Stage 1 .368 version 13.2.0 Release 1317-01) e 2+) (GSM); (UMTS); C);

2、 13) ETSI ETSI TS 122 368 V13.2.0 (2017-01)13GPP TS 22.368 version 13.2.0 Release 13Reference RTS/TSGS-0122368vd20 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 Associatio

3、n 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 present document may be made available in electronic versions and/or in print. The content of any electronic and/or print ver

4、sions 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 sp

5、ecific 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you

6、 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 No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and micr

7、ofilm 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. European Telecommunications Standards Institute 2017. All rights

8、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 the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owne

9、d by the GSM Association. ETSI ETSI TS 122 368 V13.2.0 (2017-01)23GPP TS 22.368 version 13.2.0 Release 13Intellectual 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 publicl

10、y 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 We

11、b 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

12、 become, essential to the present document. 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 shou

13、ld 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“, “should not“, “may

14、“, “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 ETSI TS 122 368 V13.

15、2.0 (2017-01)33GPP TS 22.368 version 13.2.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Overview of system optimizations for machi

16、ne-type communications . 6g35 MTC communication aspects . 7g35.1 MTC communication scenarios 7g35.1.1 Introduction. 7g35.1.2 MTC devices communicating with one or more MTC servers . 7g35.1.3 MTC devices communicating with each other 8g35.2 (void) 8g36 Categories of features for Machine-Type Communic

17、ations. 9g37 Service requirements 10g37.1 Common service requirements . 10g37.1.1 General 10g37.1.2 MTC Device triggering . 11g37.1.3 Addressing 11g37.1.4 Identifiers 12g37.1.5 Charging requirements 12g37.1.6 Security requirements . 13g37.1.7 Remote MTC device management 13g37.2. Specific service re

18、quirements MTC Features 13g37.2.1 Low Mobility 13g37.2.2 Void 13g37.2.3 Void 13g37.2.4 Void 13g37.2.5 Small Data Transmissions 13g37.2.6 Void 13g37.2.7 Infrequent Mobile Terminated 13g37.2.8 MTC Monitoring 14g37.2.9 Void 14g37.2.10 Secure Connection 14g37.2.11 Void 15g37.2.12 Void 15g37.2.13 Void 15

19、g37.2.14 Group Based MTC Features . 15g37.2.14.1 General 15g37.2.14.2 Void. 15g37.2.14.3 Group Based Addressing . 15g3Annex A (informative): Use cases . 16g3Annex B (informative): Examples of MTC applications. 20g3Annex C (informative): Change history . 21g3History 24 ETSI ETSI TS 122 368 V13.2.0 (2

20、017-01)43GPP TS 22.368 version 13.2.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration 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 mod

21、ify 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

22、 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 ETSI TS 122 368 V13.2.0 (2017-01)

23、53GPP TS 22.368 version 13.2.0 Release 131 Scope The present document specifies the service requirements for Network Improvements for Machine Type Communications. In particular it will: - identify and specify general requirements for machine type communications; - identify service aspects where netw

24、ork improvements (compared to the current human-to-human oriented services) are needed to cater for the specific nature of machine-type communications; - specify machine type communication requirements for these service aspects where network improvements are needed for machine type communication. 2

25、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 r

26、evisions 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:

27、“Vocabulary for 3GPP Specifications“. 2 3GPP TS 22.011: “ Service accessibility“. 3 3GPP TS 23.682: “Architecture enhancements to facilitate communications with packet data networks and applications“. 4 ETSI TS 102 690: “Machine-to-Machine communications (M2M); functional architecture“. 5 ETSI TS 10

28、2 921: “ Machine-to-Machine communications (M2M); mla, dla, and mld interfaces“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following apply. A term defined in the present document takes precedence o

29、ver the definition of the same term, if any, in TR 21.905 1. MTC Device: A MTC Device is a UE equipped for Machine Type Communication, which communicates through a PLMN with MTC Server(s) and/or other MTC Device(s). Note 1: A MTC Device might also communicate locally (wirelessly, possibly through a

30、Personal Area Network, or hardwired) with other entities which provide the MTC Device “raw data“ for processing and communication to the MTC Server(s) and/or other MTC Device(s). Local communication between MTC Device(s) and other entities is out of scope of the present document. MTC Feature: MTC Fe

31、atures are network functions to optimize the network for use by M2M applications. MTC Group: A MTC Group is a group of MTC Devices that share one or more MTC Features and that belong to the same MTC Subscriber. ETSI ETSI TS 122 368 V13.2.0 (2017-01)63GPP TS 22.368 version 13.2.0 Release 13MTC Server

32、: A MTC Server is a server, which communicates to the PLMN itself, and to MTC Devices through the PLMN. The MTC Server can also have an interface which can be accessed by the MTC User. The MTC Server can: - Provide services for other servers (e.g. The MTC Server is a Services Capability Server 3GPP

33、TS 23.682 3 for an Application Server 3), and/or - Provide services for applications and can host the application (e.g. The MTC Server is an Application Server 3). MTC User: A MTC User uses the service provided by the MTC Server. MTC Subscriber: A MTC Subscriber is a legal entity having a contractua

34、l relationship with the network operator to provide service to one or more MTC Devices. Note 2: Typically a M2M service provider is the party holding subscriptions in order to provide connectivity between MTC Devices and the MTC Server. In practise certain roles can collapse, e.g. the network operat

35、or acts as the same time as service provider. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 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 TR 21.90

36、5 1. NIMTC Network Improvements for Machine Type Communications MNO Mobile Network Operator MTC Machine-Type Communications 4 Overview of system optimizations for machine-type communications Machine-type communication is a form of data communication which involves one or more entities that do not ne

37、cessarily need human interaction. A service optimized for machine type communications differs from a service optimized for Human to Human communications. Machine-type communications is different to current mobile network communication services as it involves: a) different market scenarios, b) data c

38、ommunications, c) lower costs and effort, d) a potentially very large number of communicating terminals with, e) to a large extent, little traffic per terminal. For the purpose of the present document, the term MTC is used for the purpose to describe use-cases and illustrate the diverse characterist

39、ics of machine-type communication services. The informative annex A gives an overview of MTC use-cases which also illustrate different overload scenarios which will require overload control functions to prevent overload and to differentiate between services offered to different subscribers with diff

40、erent service requirements. In particular, certain MTC services and MTC applications, as exemplified in annex B, are more tolerant and can accept a lower level of performance requirements for its communication services. However, some MTC services will have similar service requirements as current mob

41、ile network communication services. ETSI ETSI TS 122 368 V13.2.0 (2017-01)73GPP TS 22.368 version 13.2.0 Release 135 MTC communication aspects 5.1 MTC communication scenarios 5.1.1 Introduction For MTC communication the following communication scenarios can be identified: a) MTC Devices communicatin

42、g with one or more MTC Server; b) MTC Devices communicating with each other. 5.1.2 MTC devices communicating with one or more MTC servers The network operator provides network connectivity to MTC Server(s). This applies to MTC Server(s) controlled by the network operator (refer to figure 5-1) or to

43、MTC Server(s) not controlled by the network operator (refer to figure 5-2.) Figure 5-1: Communication scenario with MTC devices communicating with MTC server. MTC server is located in the operator domain. Figure 5-2: Communication scenario with MTC devices communicating with MTC server. MTC server i

44、s located outside the operator domain. Operator domain MTC Device MTC Device MTC Device MTC Device MTC Server Operator domainMTC Server MTC User MTC Device MTC Device MTC Device MTC Device MTC User ETSI ETSI TS 122 368 V13.2.0 (2017-01)83GPP TS 22.368 version 13.2.0 Release 13The MTC Device and the

45、MTC Server it is communicating with may implement a service enablement framework (e.g. as specified in 4 and 5) to provide generic functionality for applications. The MTC Device may implement multiple instances of service enablement frameworks, each communicating with a different MTC Server. Note 1:

46、 the standardization of service enablement frameworks is out of scope of 3GPP. Note 2: as an example, a device can have two (or more) service enablement frameworks, both compliant to the same specific standard or belonging to the same proprietary implementation. Each one has to be peered to a differ

47、ent MTC server. 5.1.3 MTC devices communicating with each other The communication scenario where the MTC Devices communicate directly without intermediate MTC Server (refer to figure 5-3) is not considered in this release of the specification. Figure 5-3: MTC Devices communicating directly with each

48、 other without intermediate MTC server 5.2 (void) MTC Device MTC Device MTC Device MTC Device Operator domain AOperator domain BMTC Device MTC Device MTC Device MTC Device ETSI ETSI TS 122 368 V13.2.0 (2017-01)93GPP TS 22.368 version 13.2.0 Release 136 Categories of features for Machine-Type Communi

49、cations Machine-Type Communication (MTC) applications do not all have the same characteristics. This implies that not every system optimization is suitable for every MTC application. Therefore, MTC Features are defined to provide structure for the different system optimization possibilities that can be invoked. MTC Features provided to a particular subscriber are identified in the subscription. MTC Features can be individually activated. The following MTC Features have been defined: - Low Mobility; - Small Data Transmissions; - Infrequent M