Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 45.820  Word version:  13.1.0

Top   Top   None   None   Next
0…   5…   6…   6.3…   7…   7.3…   7A…

 

0  IntroductionWord‑p. 16

Machine to Machine (M2M) communication represents a significant growth opportunity for the 3GPP ecosystem. To support the so called 'Internet of Things' (IoT), 3GPP operators have to address usage scenarios with devices that are power efficient (with battery life of several years), can be reached in challenging coverage conditions e.g. indoor and basements and, more importantly, are cheap enough so that they can be deployed on a mass scale and even be disposable.
The study on which this technical report is based has considered both the possibility of evolving the current GERAN system and the design of a new access system to meet the requirements for a Cellular IoT system for the lower data rate end of the M2M market. A summary of deployment scenarios and requirements that are relevant for Cellular IoT is provided in Annex A.
Techniques captured in this report have been developed based on the assumption that Cellular IoT devices require very low throughput, do not have stringent delay requirements like those required for real time services, do not need to support circuit switched services, do not need to support Inter-RAT mobility and will perform intra-RAT mobility by cell reselection.
Up

1  ScopeWord‑p. 17

The present document contains the outcomes of the 3GPP study item on, 'Cellular System Support for Ultra Low Complexity and Low Throughput Internet of Things'.
The following are covered by the study:
  • Objectives of the study.
  • Evaluation methodology.
  • Summary of physical layer aspects and higher layer aspects for different candidate techniques proposed during the study to fulfil the objectives.
  • Common assumptions used in the evaluation of candidate techniques.
  • Evaluation of network architecture aspects. Link level and system level performance evaluations based on the objectives and evaluation methodology.
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]
TR 36.888: "Study on provision of low cost Machine-Type Communications (MTC) user Equipment (UEs) based on LTE (v12.0.0)".
[4]
TR 45.914: "Circuit switched voice capacity evolution for GSM/EDGE Radio Access Network (GERAN)".
[5]
TS 45.005: "Radio transmission and reception (v12.2.0) ".
[6]
TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[7]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[8]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC) protocol specification".
[9]
TS 36.212: "Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding".
[10]
TS 45.001: "Physical layer on the radio path; General description".
[11]
TS 45.002: "Multiplexing and multiple access on the radio path".
[12]
TS 45.003: " Channel coding".
[13]
TS 45.004: "Modulation".
[14]
TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol".
[15]
TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulations".
[16]
TR 33.863: "Study on battery efficient security for very low throughput Machine Type Communication Devices".
[17]
TR 33.860: "Study on Security aspect of cellular systems with support for ultra low complexity and low throughput Internet of Things".
[18]
TS 36.323: "Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification".
[19]
TS 24.007: "Mobile radio interface signalling layer 3; General Aspects".
[20]
TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[21]
TS 25.942: "Radio Frequency (RF) system scenarios".
[22]
TS 36.942: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Frequency (RF) system scenarios".
[23]
TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[24]
TS 27.007: "AT command set for User Equipment (UE)".
[25]
TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".
[26]
TS 45.010: "Radio subsystem synchronization".
[27]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 13).
[28]
TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification".
[29]
TS 37.104: "E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception".
[30]
TS 36.304: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); User Equipment (UE) procedures in idle mode".[31] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception".
[31]
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[32]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[33]
TR 25.816: "UMTS 900 MHz Work Item technical report".
[34]
TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)".
[35]
TS 25.104: "Base Station (BS) radio transmission and reception (FDD)".
[36]
TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception".
Up

3  Definitions and abbreviationsWord‑p. 19

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following 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 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.905.
ACK
Acknowledgement
BLER
Block Error Rate
BS
Base Station
CIoT
Cellular Internet of Things
CN
Core Network
CoAP
Constrained Application Protocol
CP
Cyclic Prefix
DL
Downlink
DSP
Digital Signal Processing
DTLS
Datagram Transport Layer Security
GWCN
Gateway Core Network
IC
Integrated Circuit
IP
Internet Protocol
IoT
Internet of Things
LDO
Low Differential Output
MAC
Medium Access Control
MCL
Maximum Coupling Loss
MOCN
Multi-Operator Core Network
MTC
Machine Type Communications
OFDMA
Orthogonal Frequency Domain Multiple Access
PA
Power Amplifier
PBCH
Physical Broadcast Channel
PCB
Printed Circuit Board
PCID
Physical Cell ID
PDCCH
Physical Downlink Control Channel
PDSCH
Physical Downlink Shared Channel
PRACH
Physical Random Access Channel
PSCH
Physical Synchronization Channel
PSS
Power Saving State
PUCCH
Physical Uplink Control Channel
PUSCH
Physical Uplink Shared Channel
RAM
Random Access Memory
RAU
Routing Area Update
RF
Radio Frequency
RTC
Real Time Clock
Rx
Receive
SAP
Service Access Point
SC-FDMA
Single Carrier Frequency Domain Multiple Access
SINR
Signal to Interference Plus Noise Ratio
SMS
Short Message Service
SNDCP
Subnetwork Dependent Convergence Protocol
TAU
Tracking Area Update
TCXO
Temperature Compensated Crystal Oscillator
TPSK
Tone-Phase-Shift-Keying
TU
Typical Urban
Tx
Transmit
UDP
User Datagram Protocol
UL
Uplink
Up

4  ObjectivesWord‑p. 20

4.1  Performance objectives

4.1.1  Improved indoor coverage

A number of applications require deployment of Machine Type Communication (MTC) devices indoor, e.g. in an apartment basement, or on indoor equipment that may be close to the ground floor etc. This effectively means that indoor coverage should be readily available and reliable. It should be possible to achieve an extended coverage of 20 dB compared to commercially available legacy GPRS (Non EGPRS) devices. The assumption of the MCL for legacy GPRS (Non EGPRS) is 144,0 dB (see Annex B). The extended coverage should allow delivery of a data rate of at least 160 bps on both the uplink and downlink at the (equivalent of) the Service Access Point (SAP) to the equivalent SubNetwork Dependent Convergence Protocol (SNDCP) layer.
Up

4.1.2  Support of massive number of low throughput devices

A system that can support a large number of devices, each generating a small amount of data is required. At cell level, it is expected that each household in a cell may have up to 40 MTC devices and the household density per cell is according to the assumptions in Annex A of TR 36.888. The resulting MTC device density per cell is provided in Annex E.

4.1.3  Reduced complexity

M2M applications require devices that are very cheap (so that they can be deployed on a mass scale or in a disposable manner). The study should take into consideration that MTC devices have very limited throughput requirement and may not need to support circuit switched services to develop techniques that can significantly reduce complexity and hence cost.

4.1.4  Improved power efficiency

The power consumption of MTC devices compared with legacy GPRS (non EGPRS) should be reduced so that they can have up to ten years battery life with battery capacity of 5 Wh (Watt-hours), even in locations with adverse coverage conditions, where up to 20 dB coverage extension over legacy GPRS might be needed.

4.1.5  Latency

M2M devices may in general support relaxed delay characteristics, and this may be taken into account when evaluating e.g. system capacity.
Certain applications (e.g. alarms) may however require a reasonably strict delay profile. For devices supporting such applications a delay requirement of 10 seconds is appropriate for the uplink when measured from the application 'trigger event' to the packet being ready for transmission from the base station towards the core network.

4.2  Compatibility objectives

4.2.1  Co-existence

The Cellular IoT system should avoid negative impacts to legacy GSM/WCDMA/LTE system(s) deployed in the same frequency band and adhere to the regulatory requirements which apply to the spectrum bands in which the system operates.

4.2.2  Implementation impact to base stationsWord‑p. 21

Impacts to the GPRS/EDGE base station hardware should be minimized.

4.2.3  Implementation impact to mobile station

Mobile stations for Cellular IoT need not be compatible with legacy GPRS networks.

Up   Top   ToC