Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 43.869  Word version:  13.0.0

Top   Top   None   None   Next
0…   6…

 

0  IntroductionWord‑p. 4

The present document captures the results of the feasibility study on MTC power saving for GERAN.

1  ScopeWord‑p. 5

The present document contains the results from the feasibility study on power saving for Machine Type Communication (MTC) devices in GERAN.
The study should cover the following aspects:
  • Identification of use cases and traffic models that the study should target.
  • Identification of a set of attributes to be used for identifying specific use case scenarios of prime interest.
  • Identification of candidate GERAN enhancements to reduce the energy consumption of MTC devices for use case scenarios of prime interest.
  • Energy consumption evaluation of the identified candidate GERAN enhancements for scenarios of prime interest.
Up

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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TR 41.001: "GSM Specification set".
→ to date, withdrawn by 3GPP
[3]
TD GP-131136: "New SI proposal: Study of Power saving for MTC Devices (uPoD)".
[4]
TD GP-140361: "MS energy consumption model", source Ericsson, GERAN#62.
[5]
3GPP TSG GERAN Telco#2 on uPod: "Reference case definition", Huawei Technologies Co., Ltd., HiSilicon Technologies Co., Ltd.
[6]
TD GP-140324: "Proposed Working Assumptions on power consumption evaluation in idle mode for MTC devices", Huawei Technologies Co., Ltd., HiSilicon Technologies Co., Ltd., GERAN#62.
[7]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[8]
TD GP-150241: "pCR for Event-triggered Neighbour Cell Measurement", Huawei Technologies Co., Ltd., HiSilicon Technologies Co., Ltd., GERAN#65.
[9]
TD GP-150273: "Consolidated Ericsson uPoD pCRs", Ericsson LM, GERAN#65.
[10]
TD GP-130473: "Long Paging Cycle for MTC use case", source Telefon AB LM Ericson, ST-Ericsson SA. GERAN#58.
[11]
TD GP-140363: "Short and long sync up procedure", source Ericsson. GERAN#62.
[12]
TS 45.008: "Radio subsystem link control".
[13]
TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol".
[14]
TS 51.010-1: "Mobile Station (MS) conformance specification".
[15]
TS 45.002: "Multiplexing and multiple access on the radio path".
Up

3  Definitions and abbreviationsWord‑p. 6

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 apply.
A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

3.2  Abbreviations

For the purposes of the present document, the abbreviations given in TR 21.905 apply.
An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

4  Objectives

The general objectives of the study, is summarized in the following [3].
  • Identify MTC scenarios of prime interest and traffic models where MTC devices would benefit from power savings.
  • Identify a set of traffic model attributes required for analysing use case scenarios of prime interest.
  • Investigate possible GERAN enhancements to reduce the power consumption of MTC devices for the use case scenarios of prime interest.
  • Evaluate the possible gains of GERAN enhancements in terms of energy savings.
  • Evaluate the possible impacts of GERAN enhancements on device performance.
  • Avoid any negative impact on legacy voice and data services.
  • Avoid any hardware impact on infrastructure equipment.
  • Avoid any hardware impact on BTS and MTC devices.
Up

5  Use Cases

5.0  General

The study is targeting MTC devices and services that are expected to be widely used in GSM networks, and which could benefit from power saving studies. Smart gas meter is one important example for this kind of MTC device. To facilitate the study and to make the candidate GERAN enhancements general enough and future proof, general use cases are summarized.

5.1  Use Case 1 - Network triggered reportingWord‑p. 7

For this use case, the MTC device is triggered to send a report to the network entity, e.g. metering devices (sensors) that are monitored and controlled by entities outside or inside the operator's network wherein a device normally only sends a report when triggered to do so by the network. Such use case requires MTC device that can be reached (triggered) as a result of network paging. After sending a report a device will remain reachable at least during a time interval determined by the Ready timer (i.e. during the first part of this interval when non-DRX timer is running it continuously monitors AGCH/PCH blocks. After the non-DRX timer expires it then monitors its nominal paging block according to legacy DRX operation for the remainder of this interval). After expiration of the Ready timer, reachability will be supported based on monitoring the nominal PCH block within the context of a power savings state.
MTC devices that support this use case will make use of a power saving mechanism that introduces limitations on device reachability (e.g. either eDRX or PSM). In addition, these devices will go into a power saving state between each triggered report where the longer the device remains in the power saving state the larger the power savings.
Up

5.2  Use Case 2 - Mobile originated autonomous reporting

For this use case, the MTC device will autonomously detect the need to send a report, e.g. in a periodic manner or the report is sent in specified time period. The network may want to dynamically adjust the periodicity based on the actual network traffic load at a specific time. Reachability will be possible using either paging or reporting events as opportunities to send messages to these types of devices (determined based on use case attribute settings). After sending a report a device will remain reachable at least during a time interval determined by the Ready timer (i.e. during the first part of this interval it continuously monitors AGCH/PCH blocks according to the Non-DRX timer and it then monitors its nominal paging block according to legacy DRX operation for the remainder of this interval). After expiration of the Ready timer, reachability will not be possible until the next reporting event.
The class of devices operate according to this use case would benefit from being able to go into a power saving state between each report transmission - the longer time between the mobile originated reports the larger the power savings.
For both use cases the reachability of devices will therefore be possible during actual reporting events (i.e. while transmitting a report) and while the Ready timer is running. The option of using an Active timer (started immediately following expiration of the Ready timer) for a period of additional reachability is not seen to be needed.
Up

Up   Top   ToC