ETSI TR 131 970-2017 Universal Mobile Telecommunications System (UMTS) LTE UICC power optimisation for Machine-Type Communication (V14 0 0 3GPP TR 31 970 version 14 0 0 Release 14).pdf

1、 ETSI TR 131 970 V14.0.0 (2017-06) Universal Mobile Telecommunications System (UMTS); LTE UICC power optimisation for Machine-Type Communication (3GPP TR 31.970 version 14.0.0 Release 14) TECHNICAL REPORT ETSI ETSI TR 131 970 V14.0.0 (2017-06)13GPP TR 31.970 version 14.0.0 Release 14Reference DTR/TS

2、GC-0631970ve00 Keywords 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 The present do

3、cument 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 authorization of ETSI. In

4、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 doc

5、ument 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 services: https:/

6、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 shall not be mo

7、dified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 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

8、Marks 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 Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 131 970 V14.0.0 (2017-06)23GPP TR 31.970 version 14.

9、0.0 Release 14Intellectual 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 publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intelle

10、ctual 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, includi

11、ng 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. Foreword This Technical Report (TR) has been pr

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

13、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 “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 Draft

14、ing 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 TR 131 970 V14.0.0 (2017-06)33GPP TR 31.970 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs

15、 terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Use cases 6g35 Power considerations related to the UICC . 7g35.1 Causes of power consumption related to the UICC 7g35.1.1 Introduction. 7g35.1.2 Presence

16、 detection polling 7g35.1.3 Proactive polling . 7g35.1.4 Power absorbed by the UICC in idle state 8g35.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 10g36 Proposed solution . 10g36.1 UICC suspension 10

17、g36.1.1 Overview 10g36.1.2 New commands 10g36.1.2.1 Introduction . 10g36.1.2.2 SUSPEND UICC 10g36.1.2.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 Secur

18、ity . 11g37.1.3 Toolkit 12g37.1.3.1 Proactive UICC session . 12g37.1.3.2 BIP session 12g37.1.3.3 Timers . 12g37.1.3.4 Other events 12g37.1.4 Internal events. 12g37.1.5 Duration 13g37.1.6 Impact on ME . 13g38 Conclusions 13g38.1 UICC platform 13g38.2 Impact on 3GPP network access applications 13g3Ann

19、ex A: Change history 14g3History 15g3ETSI ETSI TR 131 970 V14.0.0 (2017-06)43GPP TR 31.970 version 14.0.0 Release 14Foreword 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

20、 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

21、; 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 incorpo

22、rated in the document. ETSI ETSI TR 131 970 V14.0.0 (2017-06)53GPP TR 31.970 version 14.0.0 Release 141 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 pow

23、er supply in order to save power when the UICC is not required for long periods of time. This document 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 th

24、e 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 3

25、GPP 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 Release specifications“. 3 3GPP TS 31.101 V13.0.0: “U

26、ICC-terminal interface; UICC-terminal interface; Physical and logical characteristics“. 4 3GPP TS 31.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 ETS

27、I TS 102 221 V13.0.0: “Smart Cards; UICC-Terminal interface; Physical and logical characteristics“. 7 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

28、Machine-Type Communications (MTC) and other mobile data applications communications enhancements“ 10 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 o

29、f 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. ETSI ETSI TR 131 970 V14.0.0 (2017-06)63GPP TR 31.970 version 14.0.0 Release

30、 143.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. An 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 c

31、ases Use cases are described in Annex A of TS 22.368 8. Some examples are copied below: Extra Low Power 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 i

32、mpossible to replace the battery or recharge the battery for animal tracking MTC device. Compared to 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 tracki

33、ng, the cargo with a tracking MTC device could move very fast such as on a train or lorry and could stand 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 a

34、re also required. For prisoner tracking MTC devices are already used by police, prisoners will not cooperate 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

35、who have memory problem, children or pets, even the batteries of these MTC devices could be replaced 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 cas

36、e, the gas meter MTC devices must be battery powered. Extra low power consumption for gas MTC devices 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-define

37、d periods may be operated in one or more modes that minimize power consumption. An MTC Device may be 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 co

38、ntrolled periods. The MTC Device should minimize power consumption while in a mode to support this. If 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 consumptio

39、n level to extend battery life should be achieved. Such use cases justify the overall system requirement 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

40、within 3GPP, as described in TR 23.887 9 clause 7. These include: - Extended DRX cycle, introduced in Rel-13, as described in TS 23.682 10 clause 4.5.13. ETSI ETSI TR 131 970 V14.0.0 (2017-06)73GPP TR 31.970 version 14.0.0 Release 145 Power considerations related to the UICC 5.1 Causes of power cons

41、umption 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 and that activity normally occurs in bursts. Examples of this include: The ME reads configuration parameters set by the MN

42、O and stored in the UICC The ME performs authentication command The ME reads data stored in the UICC 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

43、 not actively used by the terminal. There are three distinct causes of power consumption that are related 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 refer

44、enced by 3GPP TS 31.101 3: If an application present on the UICC has the requirement to ensure that 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 shal

45、l be issued within a period of inactivity on the UICC-terminal interface. . This procedure shall be 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,

46、 including active PDP context, and can be suspended if the ME has not exchanged any data with the network 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 c

47、ontext, but has not exchanged any data with the network within a 30s period of inactivity on the UICC-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 Wo

48、rk 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 s

49、end STATUS commands to the UICC at intervals no longer than the interval negotiated with the UICC (see TS 102 223 7). During a call the UICC presence detection applies. The default value for the proactive polling is the same as for the presence detection procedure. The interval of the proactive polling can be negotiated between UICC and ME: the UICC can completely disable proactive polling using the POLLING OFF proactive command, defined in TS 31.111 5; ETSI ETSI TR 131 970 V14.0.0 (2017-06)83GPP TR 31.