ETSI TR 131 970-2018 Universal Mobile Telecommunications System (UMTS) LTE 5G UICC power optimisation for Machine-Type Communication (MTC) (V15 0 0 3GPP TR 31 970 version 15 0 0 Re.pdf

1、 ETSI TR 131 970 V15.0.0 (2018-07) Universal Mobile Telecommunications System (UMTS); LTE; 5G; UICC power optimisation for Machine-Type Communication (MTC) (3GPP TR 31.970 version 15.0.0 Release 15) TECHNICAL REPORT ETSI ETSI TR 131 970 V15.0.0 (2018-07)13GPP TR 31.970 version 15.0.0 Release 15Refer

2、ence RTR/TSGC-0631970vf00 Keywords 5G,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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice

3、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 versions of the present document shall not be modified without the prior written authorizatio

4、n 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 awar

5、e 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 find errors in the present document, please send your comment to one of the following ser

6、vices: 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 microfilm except as authorized by written permission of ETSI. The content of the PDF version s

7、hall 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. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and L

8、TETMare 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. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TR 131 970 V15.0.0 (2018-07)23GPP TR 31.970

9、 version 15.0.0 Release 15Intellectual 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 fo

10、und 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 P

11、olicy, 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

12、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 thos

13、e 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 technica

14、l 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.a

15、sp. 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

16、ETSI deliverables except when used in direct citation. ETSI ETSI TR 131 970 V15.0.0 (2018-07)33GPP TR 31.970 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations .

17、5g33.1 Definitions 5g33.2 Abbreviations . 5g34 Use cases 6g35 Power considerations related to the UICC . 6g35.1 Causes of power consumption related to the UICC 6g35.1.1 Introduction. 6g35.1.2 Presence detection polling 7g35.1.3 Proactive polling . 7g35.1.4 Power absorbed by the UICC in idle state 8g

18、35.2 Comparisons . 8g35.2.1 Introduction. 8g35.2.2 Power required to initialize a UICC 8g35.2.3 Comparison . 9g35.2.4 Conclusions. 9g35.3 Objective 9g36 Proposed solution . 10g36.1 UICC suspension 10g36.1.1 Overview 10g36.1.2 New commands 10g36.1.2.1 Introduction . 10g36.1.2.2 SUSPEND UICC 10g36.1.2

19、.2.1 Functional description . 10g36.1.2.3 RESUME UICC 11g36.1.2.3.1 Functional description . 11g37 Considerations on proposed solutions 11g37.1 UICC suspension 11g37.1.1 Introduction. 11g37.1.2 Security . 11g37.1.3 Toolkit 11g37.1.3.1 Proactive UICC session . 11g37.1.3.2 BIP session 12g37.1.3.3 Time

20、rs . 12g37.1.3.4 Other events 12g37.1.4 Internal events. 12g37.1.5 Duration 12g37.1.6 Impact on ME . 12g38 Conclusions 13g38.1 UICC platform 13g38.2 Impact on 3GPP network access applications 13g3Annex A: Change history 14g3History 15g3ETSI ETSI TR 131 970 V15.0.0 (2018-07)43GPP TR 31.970 version 15

21、.0.0 Release 15Foreword This Technical Report 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 modify the contents of the present document

22、, 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.

23、 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 TR 131 970 V15.0.0 (2018-07)53GPP TR 31.970 version 15.0.0 Release 1

24、51 Scope The present document has the objective to describe the power consumption caused by UICC when it is idle and identify the potential solutions to allow the reduction or removal of the UICC power supply in order to save power when the UICC is not required for long periods of time. This documen

25、t identifies conditions which might need to be applied to the UICC platform. 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 numb

26、er, 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 ver

27、sion 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 Release specifications“. 3 3GPP TS 31.101 V13.0.0: “UICC-terminal interface; UICC-terminal interface; Physical and logical characteristics“. 4 3GPP TS 31.

28、102 V13.1.0: “Characteristics of the Universal Subscriber Identity Module (USIM) application“. 5 3GPP TS 31.111 V13.1.0: “Universal Subscriber Identity Module (USIM) Application Toolkit (USAT)“ 6 ETSI TS 102 221 V13.0.0: “Smart Cards; UICC-Terminal interface; Physical and logical characteristics“. 7

29、 ETSI TS 102 223 V12.3.0: “Smart Cards; Card Application Toolkit“. 8 3GPP TS 22.368 V13.1.0: “Service requirements for Machine-Type Communications (MTC); Stage 1“ 9 3GPP TR 23.887 V12.0.0: “Study on Machine-Type Communications (MTC) and other mobile data applications communications enhancements“ 10

30、3GPP TS 23.682 V13.4.0: “Architecture enhancements to facilitate communications with packet data networks and applications“ 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.

31、A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1, in 3GPP TS 31.102 4 and the following apply. ETSI ETSI TR 131 970 V15.0.

32、0 (2018-07)63GPP TR 31.970 version 15.0.0 Release 15An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. 4 Use cases Use cases are described in Annex A of TS 22.368 8. Some examples are copied below: Extra Low Pow

33、er Consumption Use Case For high mobility case, tracking MTC devices such as animal tracking MTC devices in natural world with high mobility require extra low power consumption because it is almost impossible to replace the battery or recharge the battery for animal tracking MTC device. Compared to

34、the tracking devices installed in the cars and trucks because cars and trucks could generate electricity by themselves, extra low power consumption for these MTC devices is required. For cargo tracking, the cargo with a tracking MTC device could move very fast such as on a train or lorry and could s

35、tand still such as in the dock before loading or unloading. It is not desired to either change its battery or replace battery during the transport period, so extra low power consumption MTC devices are also required. For prisoner tracking MTC devices are already used by police, prisoners will not co

36、operate with police and would wish the MTC devices have flat batteries; therefore, extra low power consumption feature is required for these MTC devices. For the tracking MTC devices of elder people who have memory problem, children or pets, even the batteries of these MTC devices could be replaced

37、or charged, however, considering the worst scenario if they are missing, it requires the MTC devices with extra low power consumption and long working time in order to find them. For low mobility case, the gas meter MTC devices must be battery powered. Extra low power consumption for gas MTC devices

38、 is much more critical than electricity meters. Extra Low Power Consumption with Time Controlled MTC Devices Use Case Time Controlled MTC Devices which send or receive data only at certain pre-defined periods may be operated in one or more modes that minimize power consumption. An MTC Device may be

39、operated in a mode where it is expected to receive non-periodic messages (e.g. emergency messages or notifications of altered access period as with the MTC Feature Time Controlled outside the time controlled periods. The MTC Device should minimize power consumption while in a mode to support this. I

40、f the application requires the MTC Device to send or receive data within pre-defined periods and receive non-periodic messages outside these periods, operation at the lowest possible power consumption level to extend battery life should be achieved. Such use cases justify the overall system requirem

41、ent present in TS 22.368 8: The system shall provide mechanisms to lower power consumption of MTC Devices. Some solutions to lower the overall power consumption in such scenarios are already defined within 3GPP, as described in TR 23.887 9 clause 7. These include: - Extended DRX cycle, introduced in

42、 Rel-13, as described in TS 23.682 10 clause 4.5.13. 5 Power considerations related to the UICC 5.1 Causes of power consumption related to the UICC 5.1.1 Introduction During the power cycle of the ME, there are only some short periods of time during which the UICC is actively used by the terminal an

43、d that activity normally occurs in bursts. Examples of this include: ETSI ETSI TR 131 970 V15.0.0 (2018-07)73GPP TR 31.970 version 15.0.0 Release 15 The ME reads configuration parameters set by the MNO and stored in the UICC The ME performs authentication command The ME reads data stored in the UICC

44、 by the end user (i.e. phonebook or SMS) The ME writes data to the UICC Proactive sessions, as defined in TS 31.111 5 Toolkit events, as defined in TS 31.111 5 During the rest of the time, the UICC is not actively used by the terminal. There are three distinct causes of power consumption that are re

45、lated to the presence of the UICC that contains a USIM when not actively used. 5.1.2 Presence detection polling The presence detection mechanism is defined in ETSI TS 102 221 6 clause 14.5.2 and referenced by 3GPP TS 31.101 3: If an application present on the UICC has the requirement to ensure that

46、the UICC has not been removed during a card session the following procedure applies. The terminal sends, at frequent intervals, a STATUS command on the UICC-terminal interface. The STATUS command shall be issued within a period of inactivity on the UICC-terminal interface. . This procedure shall be

47、used in addition to a mechanical or other device used to detect the removal of a UICC. According to TS 31.102 4 clause 5.1.9, presence detection polling is required by the USIM only in case of a call, including active PDP context, and can be suspended if the ME has not exchanged any data with the ne

48、twork within a 30s period of inactivity on the UICC-ME interface. The ME may suspend the UICC presence detection based on STATUS commands in case it has an active PDP context or an active EPS bearer context, but has not exchanged any data with the network within a 30s period of inactivity on the UIC

49、C-ME interface, and resume it as soon as data is exchanged with the network, sending immediately a new STATUS command. As a consequence of changes agreed in Release 12 as part of the MTCe-UEPCOP-CT Work Item, the presence detection polling is not a concern for devices that are not actively exchanging data with the network. 5.1.3 Proactive polling The proactive polling mechanism is defined in ETSI TS 102 221 6 clause 14.6.2 and referenced by 3GPP TS 31.101 3: During idle mode the terminal shall send STATUS comma