SlideShare a Scribd company logo
1 of 48
Download to read offline
All material is Copyright © Informa Telecoms & Media
IoT M2M Case study
Real network projects
2 2
Case study 1
LTE TDD RURAL COVERAGE for M2M services
3 3
Project scenario
Provide LTE coverage for M2M forest surveillance over mountainous
rural areas
Technical project requests:
1. Check for high temperature/gas/fire alerts
2. Check for video confirmations on alerting
3. All in one board architecture
4. Autonomous power – solar or PoE
5. Connect through LTE to a main server
6. Use C-RAN connectivity to minimize implementation
4 4
Project scenario
Provide LTE coverage for M2M forest surveillance over mountainous
rural areas
Technical project requests:
1. Check for high temperature/gas/fire alerts
5 5
Project scenario
Provide LTE coverage for M2M forest surveillance over mountainous
rural areas
Technical project requests:
2. check for video confirmations on alerting
6 6
Project scenario
Provide LTE coverage for M2M forest surveillance over mountainous
rural areas
Technical project requests:
3. All in one board architecture
The solution
7 7
Project scenario
Provide LTE coverage for M2M forest surveillance over mountainous
rural areas
Technical project requests:
4. Autonomous plug and play
Sensor probes can be easily attached
by just screwing them into the bottom
sockets
8 8
Project scenario
Provide LTE coverage for M2M forest surveillance over mountainous
rural areas
Technical project requests:
4. Autonomous power – solar or PoE
Sensor probes can be easily attached
by just screwing them into the bottom
sockets
9 9
Project scenario
Provide LTE coverage for M2M forest surveillance over mountainous
rural areas
Technical project requests:
5. Connect through LTE to a main server
The Sensor data gathered by the Waspmote Plug & Sense! nodes is sent to the Cloud
by Meshlium it is a Gateway router specially designed to connect Waspmote sensor
networks to the Internet via Ethernet, WiFi and 3G interfaces
Meshlium
LoRAWAN
10 10
Project scenario
Provide LTE coverage for M2M forest surveillance over mountainous
rural areas
Technical project requests:
5. Connect through LTE (3.6 GHz) to a main server
The Sensor data gathered by the Waspmote Plug & Sense! nodes is sent to the Cloud
by Meshlium it is a Gateway router specially designed to connect Waspmote sensor
networks to the Internet via Ethernet, WiFi and 3G interfaces
Meshlium
11 11
Project scenario
Technical project requests:
5. Connect through LTE (3.6 GHz) to a main server
Forest shelter – local aggregator
Indoor shelter VoIP,
data/internet and O&M
services
12 12
Project scenario
Technical project requests:
5. Connect through LTE (3.6 GHz) to a main server
Why LTE ???
Among proposed 3GPP technologies with non-dominant standardized
solution so the most popular due to its cost effectiveness and simplicity
on network implementation is the LTE-A.
13 13
Project scenario
Technical project requests:
5. Connect through LTE (3.6 GHz) to a main server
Why LTE 3.6 GHz ??
In Greece LTE 3,6 GHz is an unused band
Project has been supported by government, through EU funding.
Greek frequency authorities (EETT) has allocated the 3.6 GHz band free
of charge to the Rural project since it is unused so far
Two channel bandwidths have been reserved:
- 3.6 GHz 30 MHz channel bandwidth
- 3.8 GHz 30 MHz channel bandwidth
14 14
Project scenario
Technical project requests:
5. Connect through LTE (3.6 GHz) to a main server
Why LTE 3.6 GHz TDD???
In Greece LTE 3.6 GHz TDD is an unused band, leaving other TDD sub-
bands available for other future services
15 15
Project scenario
Technical project requests:
6. Use C-RAN connectivity to minimize implementation
Why LTE C-RAN ???
Most world dominant vendors are proposing the LTE-A network
architecture and functionality to support the C-RAN approach and to
migrate towards 5G.
C-RAN concept is proposed to be based on a centralized baseband
processing pool equipment serving a number of clustered distributed
radio access nodes (RRUs).
Furthermore in legacy operator networks such as LTE-A and
Heterogeneous Networks, where coordinated functionality and real-time
processing is essential to performance interference as well as mobility
and synchronization improvements, the cloud RAN approach is easily
accommodated.
16 16
Project scenario
Technical project requests:
6. Use C-RAN connectivity to minimize implementation
Why LTE C-RAN ???
cell planning principles are quite similar to LTE-A with extra restrictions
and demands adapting to the specific traffic and service.
Ericsson & Huawei have lately (early 2016) proposed a combination of
powerful software features to combine cloud RAN with LTE-A technology
and deliver extreme application coverage with huge peak cell
throughputs over existing 4G operator infrastructures, in an effort
towards 5G networks aligned with 3GPP and 5GPPP standards and
proposals.
17 17
The project architecture
C-RAN architecture  use Huawei eA360 Customer Premise
Equipment (CPE) at 3.6-3.8 GHz
Meshlium
18 18
The project architecture
C-RAN architecture  use Huawei DBS3900 eNodeB technology with
RRU3232 at 3.6-3.8 GHz
19 19
The project architecture
C-RAN architecture  use Huawei DBS3900 eNodeB technology with
RRU3232 at 3.6-3.8 GHz
20 20
The project architecture
C-RAN architecture  use Huawei DBS3900 eNodeB technology with
BBU3232 at 3.6-3.8 GHz
21 21
The project architecture
C-RAN architecture  use Huawei eA360 Customer Premise
Equipment (CPE) at 3.6-3.8 GHz
In such architectures a large number of remote Remote Radio
Handlers/Remote Radio Units (RRH/RRU) are deployed over a large
geographical area, all connected over front haul fibre links (dark fibre
links), towards a centralized pool Base Band Unit (BBU) on cloud server
with typical cell coverage ranges of 15-20 Km over fibre links for LTE-A
solutions.
It is widely accepted that using RRH/RRU distributed units over radio
interface introduces advanced technologies over radio access network,
moving processing load functions to the cell edge devices (Mobile Edge
Computing solutions) and exploiting IP/ethernet with emphasis to MPLS
over optical network technology for the RAN transmission and backhaul
network topology.
22 22
The project architecture
C-RAN architecture  use Huawei eA360 Customer Premise
Equipment (CPE) at 3.6-3.8 GHz
Such a design facilitates any kind of traffic over a well-planned LTE-A
network including traditional IP subscriber web traffic, cloud services,
sensor based traffic as well as generic IoT services of any kind.
23 23
The project architecture
C-RAN settings  activate TTI bundling
What is TTI bundling?
TTI bundling is signaled by rrcConnectionReconfigution.
You can see in 3GPP TS36.331 6.3.2. Key word is ttiBundling and MAC-
MainConfig
There are thresholds defined at the eNB,
This trigger condition shall be checked with every UL transmission of the
UEs and if the trigger condition is fulfilled, the eNB shall inititate the
process to start TTI bundling for the UE.
24 24
The project architecture
C-RAN settings  activate TTI bundling
What is TTI bundling?
This feature is activated in eNB as RRCReconfigurationRequest during
the intial PDP context for default bearer established.
Again device must be supported as device capabilities message. After
that UL will be automatically group every 4 TTI.
Re-transmittion of NACK is corrected at 9 sub-frames later. Basically
when device is moved around at cell edge the errors of PUSCH is
overwhelming therefore TTI bundling is reduced the overhead and
resources of HARQ - MAC layer.
Note: in Rel 10 it might not be allowed to enable both Semi-Persistent
Scheduling and TTI bundling at the same time.
25 25
The project architecture
C-RAN settings  activate TTI bundling
What is TTI bundling?
Like If the UE has gone in bad radio condition or cell edge where the
Current Modulation and coding scheme has gone below or equal to the
threshold defined for triggerring the TTI bundling.
If TTI bundling measurements are ongoing and the percentage of
NACKed transmissions is greater than Bler threshold for TTI bundling.
Based on these criterion, eNB can trigger the TTI bundling for the UE.
Similarly if the UE moves back again to good radio condition the eNB will
ask the TTI bundlng to be turned off.
26 26
The project architecture
C-RAN settings  activate TTI bundling
Check also
beside the options present above one could consider using additional
triggers (at the eNB side to start RRC reconfig).
For example:
1. PHR (power headroom) report in addition to measured UE power in
the up-link.
2. Using known eNB tx power and maximal UE power to configure A1
and A2 measurement event (36.331 A1/A2=Serving becomes
better/worst than threshold).
27 27
The project architecture
C-RAN settings  activate TTI bundling
Remarks
1. improving the data part (PUSCH) by TTI bundling is not enough, one
need to look on the control channel send over PUCCH (e.g. use
repetition).
2.
2. The implications on the MAC design are all by trivial, for example
how the MAC scheduler works in both UL and DL (if PUCCH
repetition is used) when combining UEs with bundling and few w/o.
28 28
The project architecture
C-RAN settings  RRC connected users ???
There is RRC connected user license limit provided by vendor. By
default, this is 60 (as per my knowledge and experience).
As users increase in network, you need to buy license allowing more
users from vendor.
If you guide me which vendor you are working ,I might be able to send
you the license parameter to check.
Secondly, there is product capacity provided by the
Again this can be identified if product version is known.
29 29
The project architecture
C-RAN settings  RRC connected users ???
Do not confuse it with applicability while considering 1 ms TTI and 20
MHz BW.
There is difference between theoretical and practical limitations. Specific
equipment has its limitation in processing the load.
This is the reason you are observing challenge in understanding this.
RRC connected user capacity is provided at eNB level.
This is the number of UEs in connected mode at an instance.
30 30
LoRAWAN RAN planning considerations
 LoRAWAN technical specs.
31 31
LoRAWAN RAN planning considerations
 LoRAWAN technical specs.
32 32
LoRAWAN RAN planning considerations
 LoRAWAN technical specs.
Our project scenario
33 33
LoRAWAN RAN planning considerations
 LoRAWAN technical specs.
Our surveillance scenario
34 34
C-RAN Design considerations
 SINR considerations: The major concern is related to the uplink cell
planning & optimization issues in such a way to guarantee adequate
SINR for accepted service accessibility as well as integrity
(throughput) performance.
35 35
C-RAN Design considerations
 SINR considerations
assure the signal-to-noise ration over the uplink receiving levels so that
uplink
RRH = arg
uplink
t et on
RRH/RRU unit, otherwise several severe side effects might take place
Suppose that CPE outdoor unit transmits on power level , arg
UE
o t etP and the receiving RRH unit
receives a signal strength RRHSE = ,min
UL
RP , then RRH receiving unit will be able to successfully
decode the received signal under a noisy and interference channel link.
Receiving sensitivity RRHSE is defined as the minimum receiving signal level
min
UL
RP ,
depending on the requested CPE outdoor unit transmitted power , arg
UE
o t etP and is given by the
following formula:
, arg
min
( ) ( )UE T R
o t et o o o oUL
R RRH
pathloss j LNA f C
P G G
P SE
L L L L L
 
 
where jL are the jumper losses on RRH antenna unit, LNAL is the LNA losses if
used, fL are the waveguide (feeder) losses, CL are the feeder connector losses
over LNA.
(1)
36 36
C-RAN Design considerations
 SINR considerations
The ideal condition for successful decoding on the receiving RRH unit is:
  1R feeder
f pathlossLNA
RRH t BW f
LNA
N L
SE N RB N
G
 
    
 
 
Check next slide
(2)
37 37
C-RAN Design considerations
 SINR considerations
38 38
C-RAN Design considerations
 SINR considerations
Substituting (2) on (1) will contribute into the sufficient uplink sensitivity condition on RRH receiving unit
 , arg
1( ) ( )
R feederUE T R
f pathlosso t et o o o o LNA
RRH t BW f
pathloss j LNA f C LNA
N LP G G
SE N RB N
L L L L L G
   
      
 
 
 
, arg
1
( ) ( )
R feeder
f pathlossLNA
t BW f pathloss j LNA f C
LNAUE
o t et T R
o o o o
N L
N RB N L L L L L
G
P
G G 
 
   
 
 

(3)
39 39
C-RAN Design considerations
 SINR considerations
LTE-A for C-RAN has a superior power control algorithm to compensate for adequate power for
the received level of however there should be further considerations regarding some extra
restrictions since maintaining always condition on equation (3) is not always feasible.
This is because CPE outdoor unit has predefined hardware restrictions on the maximum allowed
transmitted power
Moreover than that there is a maximum allowed uplink power threshold posed by RAN
optimizer to mitigate and keep inter-cell interference as low as possible (an example might be the
Ericsson parameter pMaxServingCell).
Considering these extra restrictions equation (3) is rewritten as follows:
, arg
UE
o t etP
0
UE
P
max,
UE
ulP
  max, , arg
min
min ,min , ( ) ( )UE UE UE T R
o ul o t et o o o oUL
R RRH
pathloss j LNA f C
P P P G G
P SE
L L L L L
 
  (4)
40 40
C-RAN Design considerations
 SINR considerations
The major problem that RAN designers might face on LTE-A C-RAN planning for IoT
sensor applications is that quite often, due to load (inter-cell interference in the area),
LTE-A CPE outdoor unit might easily be saturated on uplink transmitted power.
This means that the power control algorithm might request (under loaded conditions) CPE
outdoor unit to increase uplink transmitted power , to fulfill the RRH/RRU received
SINR or power level, however the CPE outdoor unit might fail (saturates) since:
, arg 0,
UE req
o t et uplinkP P 
- Requested CPE outdoor unit transmitted power , arg max,
UE UE
o t et ulP P ,  hence saturates
since  max, , argmin ,UE UE
ul o t etP P = max,
UE
ulP , that is restricted from configured parameter (i.e.
Ericsson parameter pMaxServingCell ).
- Requested CPE outdoor unit transmitted power , arg max,
UE UE
o t et ulP P  hence there is
enough power since  max, , argmin ,UE UE
ul o t etP P = , arg
UE
o t etP , but on the same time
, arg max,
UE UE UE
o o t et ulP P P   as a result fails (saturates) to respond to that power
request because of hardware circuitry restrictions since
  max, , argmin ,min ,UE UE UE
o ul o t etP P P =  , argmin ,UE UE
o o t etP P = UE
oP  saturation due to
power CPE outdoor specifications.
41 41
C-RAN Design considerations
 SINR considerations
The major problem that RAN designers might face on LTE-A C-RAN planning for IoT
sensor applications is that quite often, due to load (inter-cell interference in the area),
LTE-A CPE outdoor unit might easily be saturated on uplink transmitted power.
Considering both previous conditions it holds that:
Requested ( , arg
UE
o t etP  UE
oP ) ( , arg
UE
o t etP  max,
UE
ulP )
And as a consequence always:
  1R feeder
f pathlossLNA
eNodeB t BW f
LNA
N L
SE N RB N
G
 
    
 
 
42 42
C-RAN Design considerations
 SINR considerations
Planning Conclusions:
1st Conclusion: C-RAN designers, considering the necessary CPE outdoor unit uplink
connectivity, have to ensure that previous saturation conditions should never happen!!!
2nd Conclusion: Considering all design restrictions as well as the RRH/RRU sensitivity conditions:
    max, , argmin ,min , ( ) ( ) 1
UE UE UE T R R feeder
o ul o t et o o o o f pathlossLNA
eNodeB t BW f
pathloss j LNA f C LNA
P P P G G N L
SE N RB N
L L L L L G
    
      
 
 
  
 
max, , arg
1
min ,min ,
( ) ( )
R feeder
f pathlossLNA
t BW f pathloss j LNA f C
LNAUE UE UE
o ul o t et T R
o o o o
N L
N RB N L L L L L
G
P P P
G G 
 
   
 
  

 
, arg
1
( ) ( )
R feeder
f pathlossLNA
t BW f pathloss j LNA f C
LNAUE
o t et T R
o o o o
N L
N RB N L L L L L
G
P
G G 
 
   
 
 

(5)
43 43
C-RAN Design considerations
 SINR considerations
Planning Conclusions:
2nd Conclusion: Considering all design restrictions as well as the RRH/RRU sensitivity conditions:
Considering strict condition for   max, , argmin ,min ,UE UE UE
o ul o t etP P P = UE
oP , r R  :
- Initial setting of maximum power max,
UE
ulP parameter configuration on every cell
coverage area r R (i.e. Ericsson parameter pMaxServingCell) shall be such that
max,
UE UE
ul oP P   max, , argmin ,UE UE
ul o t etP P  UE
oP r R  .
Simultaneous power control parameter configuration, combined with maximum
geographical coverage R should be such that: , arg max,
UE UE UE
o t et ul oP P P  r R  
 max, , argmin ,UE UE
ul o t etP P = , arg
UE
o t etP r R     max, , argmin ,min ,UE UE UE
o ul o t etP P P = UE
oP r R  
ensuring condition , arg
UE
o t etP r R  .
44 44
C-RAN Design considerations
 SINR considerations
Planning Conclusions:
3nd Conclusion: A good C-RAN proposal is to use a design margin , so that any Noise and
Interference peaks will be over-dimensioned and absorbed on initial design.
arg 3mP dB
    max, , arg
arg
min ,min , ( ) ( ) 1
UE UE UE T R R feeder
o ul o t et o o o o f pathlossLNA
eNodeB t BW f m
pathloss j LNA f C LNA
P P P G G N L
SE N RB N P
L L L L L G
    
      
 
 
  
 
arg
max, , arg
1
min ,min ,
( ) ( )
R feeder
f pathlossLNA
t BW f m pathloss j LNA f C
LNA
UE UE UE
o ul o t et T R
o o o o
N L
N RB N P L L L L L
G
P P P
G G 
  
     
     

 
arg
, arg
1
Power Control decision
( ) ( )
R feeder
f pathlossLNA
t BW f m pathloss j LNA f C
LNA
UE
o t et T R
o o o o
N L
N RB N P L L L L L
G
P
G G 
  
     
    

(6)
45 45
C-RAN Design considerations
 Accessibility Considerations: Cell selection in idle mode (camping) is also
crucial for the C-RAN CPE outdoor unit, since wrong cell camping will lead to
RRH/RRU sensitivity condition failure!!!
The answer is to follow always the 3GPP specifications (i.e. 3GPP TS 36.304)
46 46
C-RAN Design considerations
 Accessibility Considerations:
According to 3GPP TS 36.304 cell camping is validated following the recommendation:
 min min 0rxlev rxlevmeas rxlev rxlev offset compensationS Q Q Q P    
Where rxlevmeasQ is the real CPE outdoor unit measured downlink RRH transmitted power over
the reference signals RS (RSRP signal strength measurement, minrxlevQ is a configurable cell
parameter broadcasted over BCCH channel on the downlink and minrxlev offsetQ is an offset
configuranle parameter for fine tuning purposes.
compensationP is a power configurable parameter and according to 3GPP recommendations
compensationP =  max ,0EMAX UMAXP P .
EMAXP is based on 3GPP EMAXP = max,
UE
ulP and UMAXP is according to 3GPP UMAXP = UE
oP .
(7)
47 47
C-RAN Design considerations
 Accessibility Considerations:
Substituting into (7) we could get the updated cell camping suitability condition:
   min min max,max ,0UE UE
rxlev rxlevmeas rxlev rxlev offset ul oS Q Q Q P P    
Following nominal cell planning and considering the LTE-A outdoor unit cell selection to
guarantee the equation (5) sensitivity conditions, cell planners should always select camping
parameters so that:
- In every geographical cell coverage area r R condition to be fulfilled is
 min minrxlev rxlev offsetQ Q  rxlevS r R  , so that always 0rxlevS 
- In every geographical cell coverage area r R condition to be fulfilled is max,
UE UE
ul oP P
r R  , so that always  max,max ,0UE UE
ul oP P = 0 r R   0rxlevS  , r R 
48 48
C-RAN Design considerations
 Throughput considerations.
Throughput depends on SINR, pathloss as well as LoS conditions
Follow excel file, provided by instructor, for further analysis

More Related Content

What's hot

3GPP LTE-A Standardisation in Release 12 and Beyond - Jan 2013 Eiko Seidel, C...
3GPP LTE-A Standardisation in Release 12 and Beyond - Jan 2013 Eiko Seidel, C...3GPP LTE-A Standardisation in Release 12 and Beyond - Jan 2013 Eiko Seidel, C...
3GPP LTE-A Standardisation in Release 12 and Beyond - Jan 2013 Eiko Seidel, C...Eiko Seidel
 
LTE-Advanced Pro from Qualcomm
LTE-Advanced Pro from QualcommLTE-Advanced Pro from Qualcomm
LTE-Advanced Pro from QualcommLow Hong Chuan
 
Arte 12052005 1
Arte 12052005 1Arte 12052005 1
Arte 12052005 1pkedar79
 
Towards achieving-high-performance-in-5g-mobile-packet-cores-user-plane-function
Towards achieving-high-performance-in-5g-mobile-packet-cores-user-plane-functionTowards achieving-high-performance-in-5g-mobile-packet-cores-user-plane-function
Towards achieving-high-performance-in-5g-mobile-packet-cores-user-plane-functionEiko Seidel
 
C-RAN Architecture based on SDN for 5G Mobile - Inatel
C-RAN Architecture based on SDN for 5G Mobile - Inatel  C-RAN Architecture based on SDN for 5G Mobile - Inatel
C-RAN Architecture based on SDN for 5G Mobile - Inatel Diego C. Zuñiga
 
A Flexible Network Architecture for 5G Systems
A Flexible Network Architecture for 5G SystemsA Flexible Network Architecture for 5G Systems
A Flexible Network Architecture for 5G SystemsEiko Seidel
 
LTE-A HetNets using Carrier Aggregation - Eiko Seidel, CTO, Nomor Research
LTE-A HetNets using Carrier Aggregation - Eiko Seidel, CTO, Nomor ResearchLTE-A HetNets using Carrier Aggregation - Eiko Seidel, CTO, Nomor Research
LTE-A HetNets using Carrier Aggregation - Eiko Seidel, CTO, Nomor ResearchEiko Seidel
 
CLOUD RAN- Benefits of Centralization and Virtualization
CLOUD RAN- Benefits of Centralization and VirtualizationCLOUD RAN- Benefits of Centralization and Virtualization
CLOUD RAN- Benefits of Centralization and VirtualizationAricent
 
Radio Measurements in LTE
Radio Measurements in LTERadio Measurements in LTE
Radio Measurements in LTESofian .
 
Sample-by-sample and block-adaptive robust constant modulus-based algorithms
Sample-by-sample and block-adaptive robust constant modulus-based algorithmsSample-by-sample and block-adaptive robust constant modulus-based algorithms
Sample-by-sample and block-adaptive robust constant modulus-based algorithmsDr. Ayman Elnashar, PhD
 
Evaluation of 5G Data Duplication for URLLC - Nomor Reseach GmbH
Evaluation of 5G Data Duplication for URLLC - Nomor Reseach GmbHEvaluation of 5G Data Duplication for URLLC - Nomor Reseach GmbH
Evaluation of 5G Data Duplication for URLLC - Nomor Reseach GmbHEiko Seidel
 
3.3 gpp NR USER Plane introduction
3.3 gpp NR USER Plane introduction3.3 gpp NR USER Plane introduction
3.3 gpp NR USER Plane introductionSaurabh Verma
 
Addressing 5G Sync plane issues
Addressing 5G Sync plane issuesAddressing 5G Sync plane issues
Addressing 5G Sync plane issuesDhiman Chowdhury
 
5 g network white paper
5 g network white paper 5 g network white paper
5 g network white paper Ravi Sharma
 
Backhaul Ppt
Backhaul PptBackhaul Ppt
Backhaul Pptwillyaoll
 
Final Performance Evaluation of 3GPP NR eMBB within 5G-PPP consortium
Final Performance Evaluation of 3GPP NR eMBB within 5G-PPP consortiumFinal Performance Evaluation of 3GPP NR eMBB within 5G-PPP consortium
Final Performance Evaluation of 3GPP NR eMBB within 5G-PPP consortiumEiko Seidel
 
Relay Enhanced LTE-Advanced Networks – Resource Allocation and QoS provisioni...
Relay Enhanced LTE-Advanced Networks – Resource Allocation and QoS provisioni...Relay Enhanced LTE-Advanced Networks – Resource Allocation and QoS provisioni...
Relay Enhanced LTE-Advanced Networks – Resource Allocation and QoS provisioni...Eiko Seidel
 

What's hot (20)

3GPP LTE-A Standardisation in Release 12 and Beyond - Jan 2013 Eiko Seidel, C...
3GPP LTE-A Standardisation in Release 12 and Beyond - Jan 2013 Eiko Seidel, C...3GPP LTE-A Standardisation in Release 12 and Beyond - Jan 2013 Eiko Seidel, C...
3GPP LTE-A Standardisation in Release 12 and Beyond - Jan 2013 Eiko Seidel, C...
 
LTE-Advanced Pro from Qualcomm
LTE-Advanced Pro from QualcommLTE-Advanced Pro from Qualcomm
LTE-Advanced Pro from Qualcomm
 
Arte 12052005 1
Arte 12052005 1Arte 12052005 1
Arte 12052005 1
 
EVERYTHING IN LTE
EVERYTHING IN LTEEVERYTHING IN LTE
EVERYTHING IN LTE
 
Towards achieving-high-performance-in-5g-mobile-packet-cores-user-plane-function
Towards achieving-high-performance-in-5g-mobile-packet-cores-user-plane-functionTowards achieving-high-performance-in-5g-mobile-packet-cores-user-plane-function
Towards achieving-high-performance-in-5g-mobile-packet-cores-user-plane-function
 
Epc cups overview
Epc cups overviewEpc cups overview
Epc cups overview
 
C-RAN Architecture based on SDN for 5G Mobile - Inatel
C-RAN Architecture based on SDN for 5G Mobile - Inatel  C-RAN Architecture based on SDN for 5G Mobile - Inatel
C-RAN Architecture based on SDN for 5G Mobile - Inatel
 
A Flexible Network Architecture for 5G Systems
A Flexible Network Architecture for 5G SystemsA Flexible Network Architecture for 5G Systems
A Flexible Network Architecture for 5G Systems
 
LTE-A HetNets using Carrier Aggregation - Eiko Seidel, CTO, Nomor Research
LTE-A HetNets using Carrier Aggregation - Eiko Seidel, CTO, Nomor ResearchLTE-A HetNets using Carrier Aggregation - Eiko Seidel, CTO, Nomor Research
LTE-A HetNets using Carrier Aggregation - Eiko Seidel, CTO, Nomor Research
 
CLOUD RAN- Benefits of Centralization and Virtualization
CLOUD RAN- Benefits of Centralization and VirtualizationCLOUD RAN- Benefits of Centralization and Virtualization
CLOUD RAN- Benefits of Centralization and Virtualization
 
5G Sandardization
5G Sandardization5G Sandardization
5G Sandardization
 
Radio Measurements in LTE
Radio Measurements in LTERadio Measurements in LTE
Radio Measurements in LTE
 
Sample-by-sample and block-adaptive robust constant modulus-based algorithms
Sample-by-sample and block-adaptive robust constant modulus-based algorithmsSample-by-sample and block-adaptive robust constant modulus-based algorithms
Sample-by-sample and block-adaptive robust constant modulus-based algorithms
 
Evaluation of 5G Data Duplication for URLLC - Nomor Reseach GmbH
Evaluation of 5G Data Duplication for URLLC - Nomor Reseach GmbHEvaluation of 5G Data Duplication for URLLC - Nomor Reseach GmbH
Evaluation of 5G Data Duplication for URLLC - Nomor Reseach GmbH
 
3.3 gpp NR USER Plane introduction
3.3 gpp NR USER Plane introduction3.3 gpp NR USER Plane introduction
3.3 gpp NR USER Plane introduction
 
Addressing 5G Sync plane issues
Addressing 5G Sync plane issuesAddressing 5G Sync plane issues
Addressing 5G Sync plane issues
 
5 g network white paper
5 g network white paper 5 g network white paper
5 g network white paper
 
Backhaul Ppt
Backhaul PptBackhaul Ppt
Backhaul Ppt
 
Final Performance Evaluation of 3GPP NR eMBB within 5G-PPP consortium
Final Performance Evaluation of 3GPP NR eMBB within 5G-PPP consortiumFinal Performance Evaluation of 3GPP NR eMBB within 5G-PPP consortium
Final Performance Evaluation of 3GPP NR eMBB within 5G-PPP consortium
 
Relay Enhanced LTE-Advanced Networks – Resource Allocation and QoS provisioni...
Relay Enhanced LTE-Advanced Networks – Resource Allocation and QoS provisioni...Relay Enhanced LTE-Advanced Networks – Resource Allocation and QoS provisioni...
Relay Enhanced LTE-Advanced Networks – Resource Allocation and QoS provisioni...
 

Viewers also liked

Mobile + Cloud + IoT - Case Study
Mobile + Cloud + IoT - Case StudyMobile + Cloud + IoT - Case Study
Mobile + Cloud + IoT - Case StudyAndri Yadi
 
Developing IoT devices. Creating wearables with the new LinkIt™ 2523 HDK by SAC
Developing IoT devices. Creating wearables with the new LinkIt™ 2523 HDK by SACDeveloping IoT devices. Creating wearables with the new LinkIt™ 2523 HDK by SAC
Developing IoT devices. Creating wearables with the new LinkIt™ 2523 HDK by SACMediaTek Labs
 
#Winning with Sitecore
#Winning with Sitecore#Winning with Sitecore
#Winning with SitecoreSagittarius
 
re:Invent 2016 の振り返りで学ぶawsを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略
re:Invent 2016 の振り返りで学ぶawsを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略re:Invent 2016 の振り返りで学ぶawsを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略
re:Invent 2016 の振り返りで学ぶawsを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略Takashi Kozu
 
Personalising Customer Experiences Through Analytics
Personalising Customer Experiences Through AnalyticsPersonalising Customer Experiences Through Analytics
Personalising Customer Experiences Through AnalyticsSagittarius
 
クラウドファンディングを活用したIoT事例集
クラウドファンディングを活用したIoT事例集クラウドファンディングを活用したIoT事例集
クラウドファンディングを活用したIoT事例集Ouma オーマ
 
Provoke: Case study - digital transformation for Robinsons Brewery
Provoke: Case study - digital transformation for Robinsons Brewery Provoke: Case study - digital transformation for Robinsons Brewery
Provoke: Case study - digital transformation for Robinsons Brewery Mando
 
クラウド x IoT実践事例のご紹介
クラウド x IoT実践事例のご紹介クラウド x IoT実践事例のご紹介
クラウド x IoT実践事例のご紹介masaoki_ohashi
 
IoT Reference Architecture and Case Studies
IoT Reference Architecture and Case StudiesIoT Reference Architecture and Case Studies
IoT Reference Architecture and Case StudiesSerhiy (Serge) Haziyev
 
What is digital personalisation in Travel and why should I care? Travel Techn...
What is digital personalisation in Travel and why should I care? Travel Techn...What is digital personalisation in Travel and why should I care? Travel Techn...
What is digital personalisation in Travel and why should I care? Travel Techn...Sagittarius
 
Costa Farms Case Study : Azure IoT Hub, Azure Functions
Costa Farms Case Study : Azure IoT Hub, Azure FunctionsCosta Farms Case Study : Azure IoT Hub, Azure Functions
Costa Farms Case Study : Azure IoT Hub, Azure FunctionsJoe Raio
 
Sagittarius - Knowing Your Niche
Sagittarius - Knowing Your NicheSagittarius - Knowing Your Niche
Sagittarius - Knowing Your NicheSagittarius
 
re:Inventの振り返りで学ぶAWSを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略
re:Inventの振り返りで学ぶAWSを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略re:Inventの振り返りで学ぶAWSを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略
re:Inventの振り返りで学ぶAWSを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略株式会社スカイアーチネットワークス
 
Vodafone IoT_Prompt Softech case study
Vodafone IoT_Prompt Softech case studyVodafone IoT_Prompt Softech case study
Vodafone IoT_Prompt Softech case studyAshim Goldar
 
Provoke: Agile Marcoms - Strategies & Technologies
Provoke: Agile  Marcoms - Strategies & TechnologiesProvoke: Agile  Marcoms - Strategies & Technologies
Provoke: Agile Marcoms - Strategies & TechnologiesMando
 
Constructing the Case for Cloud
Constructing the Case for CloudConstructing the Case for Cloud
Constructing the Case for CloudJustin Pirie
 
Case study: Building a business case for cloud, migration in practice and spr...
Case study: Building a business case for cloud, migration in practice and spr...Case study: Building a business case for cloud, migration in practice and spr...
Case study: Building a business case for cloud, migration in practice and spr...Eduserv
 
Close the Gap - Understand your customer and enhance your digital experience ...
Close the Gap - Understand your customer and enhance your digital experience ...Close the Gap - Understand your customer and enhance your digital experience ...
Close the Gap - Understand your customer and enhance your digital experience ...edynamic
 

Viewers also liked (20)

Mobile + Cloud + IoT - Case Study
Mobile + Cloud + IoT - Case StudyMobile + Cloud + IoT - Case Study
Mobile + Cloud + IoT - Case Study
 
Developing IoT devices. Creating wearables with the new LinkIt™ 2523 HDK by SAC
Developing IoT devices. Creating wearables with the new LinkIt™ 2523 HDK by SACDeveloping IoT devices. Creating wearables with the new LinkIt™ 2523 HDK by SAC
Developing IoT devices. Creating wearables with the new LinkIt™ 2523 HDK by SAC
 
Neyy
NeyyNeyy
Neyy
 
#Winning with Sitecore
#Winning with Sitecore#Winning with Sitecore
#Winning with Sitecore
 
re:Invent 2016 の振り返りで学ぶawsを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略
re:Invent 2016 の振り返りで学ぶawsを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略re:Invent 2016 の振り返りで学ぶawsを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略
re:Invent 2016 の振り返りで学ぶawsを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略
 
Personalising Customer Experiences Through Analytics
Personalising Customer Experiences Through AnalyticsPersonalising Customer Experiences Through Analytics
Personalising Customer Experiences Through Analytics
 
クラウドファンディングを活用したIoT事例集
クラウドファンディングを活用したIoT事例集クラウドファンディングを活用したIoT事例集
クラウドファンディングを活用したIoT事例集
 
Provoke: Case study - digital transformation for Robinsons Brewery
Provoke: Case study - digital transformation for Robinsons Brewery Provoke: Case study - digital transformation for Robinsons Brewery
Provoke: Case study - digital transformation for Robinsons Brewery
 
Orange Business Live 2013 M2M breakout
Orange Business Live 2013 M2M breakoutOrange Business Live 2013 M2M breakout
Orange Business Live 2013 M2M breakout
 
クラウド x IoT実践事例のご紹介
クラウド x IoT実践事例のご紹介クラウド x IoT実践事例のご紹介
クラウド x IoT実践事例のご紹介
 
IoT Reference Architecture and Case Studies
IoT Reference Architecture and Case StudiesIoT Reference Architecture and Case Studies
IoT Reference Architecture and Case Studies
 
What is digital personalisation in Travel and why should I care? Travel Techn...
What is digital personalisation in Travel and why should I care? Travel Techn...What is digital personalisation in Travel and why should I care? Travel Techn...
What is digital personalisation in Travel and why should I care? Travel Techn...
 
Costa Farms Case Study : Azure IoT Hub, Azure Functions
Costa Farms Case Study : Azure IoT Hub, Azure FunctionsCosta Farms Case Study : Azure IoT Hub, Azure Functions
Costa Farms Case Study : Azure IoT Hub, Azure Functions
 
Sagittarius - Knowing Your Niche
Sagittarius - Knowing Your NicheSagittarius - Knowing Your Niche
Sagittarius - Knowing Your Niche
 
re:Inventの振り返りで学ぶAWSを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略
re:Inventの振り返りで学ぶAWSを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略re:Inventの振り返りで学ぶAWSを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略
re:Inventの振り返りで学ぶAWSを利用したデータ活用戦略と、サバカン屋の新作缶づめ戦略
 
Vodafone IoT_Prompt Softech case study
Vodafone IoT_Prompt Softech case studyVodafone IoT_Prompt Softech case study
Vodafone IoT_Prompt Softech case study
 
Provoke: Agile Marcoms - Strategies & Technologies
Provoke: Agile  Marcoms - Strategies & TechnologiesProvoke: Agile  Marcoms - Strategies & Technologies
Provoke: Agile Marcoms - Strategies & Technologies
 
Constructing the Case for Cloud
Constructing the Case for CloudConstructing the Case for Cloud
Constructing the Case for Cloud
 
Case study: Building a business case for cloud, migration in practice and spr...
Case study: Building a business case for cloud, migration in practice and spr...Case study: Building a business case for cloud, migration in practice and spr...
Case study: Building a business case for cloud, migration in practice and spr...
 
Close the Gap - Understand your customer and enhance your digital experience ...
Close the Gap - Understand your customer and enhance your digital experience ...Close the Gap - Understand your customer and enhance your digital experience ...
Close the Gap - Understand your customer and enhance your digital experience ...
 

Similar to IoT M2M case study analysis

5G Enablers for new network
5G Enablers for new network5G Enablers for new network
5G Enablers for new networkErtan Öztürk
 
6 lte-a challenges and evolving lte network architecture
6 lte-a challenges and evolving lte network architecture6 lte-a challenges and evolving lte network architecture
6 lte-a challenges and evolving lte network architectureCPqD
 
Cloud RAN-Deployment-CPRI-Fronthaul-Technology
Cloud RAN-Deployment-CPRI-Fronthaul-TechnologyCloud RAN-Deployment-CPRI-Fronthaul-Technology
Cloud RAN-Deployment-CPRI-Fronthaul-TechnologyHarsha Nath Jha
 
Internet acess to rural areas using wifi altanai bisht , 1st year
Internet acess to rural areas using wifi   altanai bisht , 1st yearInternet acess to rural areas using wifi   altanai bisht , 1st year
Internet acess to rural areas using wifi altanai bisht , 1st yearALTANAI BISHT
 
Enabling 5G X-Haul with Deterministic Ethernet - A TransPacket whitepaper
Enabling 5G X-Haul with Deterministic Ethernet - A TransPacket whitepaperEnabling 5G X-Haul with Deterministic Ethernet - A TransPacket whitepaper
Enabling 5G X-Haul with Deterministic Ethernet - A TransPacket whitepaperIvar Søvold
 
5G RAN fundamentals
5G RAN fundamentals5G RAN fundamentals
5G RAN fundamentalsRavi Sharma
 
Nokia_Mission-critical_Utilities_Network_Teleprotection_Application_Note_EN
Nokia_Mission-critical_Utilities_Network_Teleprotection_Application_Note_ENNokia_Mission-critical_Utilities_Network_Teleprotection_Application_Note_EN
Nokia_Mission-critical_Utilities_Network_Teleprotection_Application_Note_ENJuan Boggiano
 
Accelerating 5G enterprise networks with edge computing and latency assurance
Accelerating 5G enterprise networks with edge computing and latency assuranceAccelerating 5G enterprise networks with edge computing and latency assurance
Accelerating 5G enterprise networks with edge computing and latency assuranceADVA
 
EBlink leading fronthaul solutions - 2016
EBlink leading fronthaul solutions - 2016EBlink leading fronthaul solutions - 2016
EBlink leading fronthaul solutions - 2016sylvain Lamblot
 
Day 1 LTE Technology Overview
Day 1 LTE Technology OverviewDay 1 LTE Technology Overview
Day 1 LTE Technology Overviewmahesh savita
 
5 g peek from cmcc 20may2013
5 g peek from cmcc 20may20135 g peek from cmcc 20may2013
5 g peek from cmcc 20may2013Muljati Muli
 
Andy sutton - Multi-RAT mobile backhaul for Het-Nets
Andy sutton - Multi-RAT mobile backhaul for Het-NetsAndy sutton - Multi-RAT mobile backhaul for Het-Nets
Andy sutton - Multi-RAT mobile backhaul for Het-Netshmatthews1
 
IEC61850: Use of IEC61850 to telecontrol MV grids (Article)
IEC61850: Use of IEC61850 to telecontrol MV grids (Article)IEC61850: Use of IEC61850 to telecontrol MV grids (Article)
IEC61850: Use of IEC61850 to telecontrol MV grids (Article)iGrid T&D
 
Lte technology-for-engineers
Lte technology-for-engineersLte technology-for-engineers
Lte technology-for-engineersa8us
 
109885868-LTE-Technology-for-Engineers.pdf
109885868-LTE-Technology-for-Engineers.pdf109885868-LTE-Technology-for-Engineers.pdf
109885868-LTE-Technology-for-Engineers.pdfMohamedShabana37
 
Radisys & Airspan - Small Cells and LTE-A Webinar Presentation
Radisys & Airspan -  Small Cells and LTE-A Webinar PresentationRadisys & Airspan -  Small Cells and LTE-A Webinar Presentation
Radisys & Airspan - Small Cells and LTE-A Webinar PresentationRadisys Corporation
 
Evolving to an open C-RAN Architecture for 5G
Evolving to an open C-RAN Architecture for 5GEvolving to an open C-RAN Architecture for 5G
Evolving to an open C-RAN Architecture for 5Gkinsleyaniston
 

Similar to IoT M2M case study analysis (20)

5G Enablers for new network
5G Enablers for new network5G Enablers for new network
5G Enablers for new network
 
6 lte-a challenges and evolving lte network architecture
6 lte-a challenges and evolving lte network architecture6 lte-a challenges and evolving lte network architecture
6 lte-a challenges and evolving lte network architecture
 
Cloud RAN-Deployment-CPRI-Fronthaul-Technology
Cloud RAN-Deployment-CPRI-Fronthaul-TechnologyCloud RAN-Deployment-CPRI-Fronthaul-Technology
Cloud RAN-Deployment-CPRI-Fronthaul-Technology
 
Internet acess to rural areas using wifi altanai bisht , 1st year
Internet acess to rural areas using wifi   altanai bisht , 1st yearInternet acess to rural areas using wifi   altanai bisht , 1st year
Internet acess to rural areas using wifi altanai bisht , 1st year
 
Enabling 5G X-Haul with Deterministic Ethernet - A TransPacket whitepaper
Enabling 5G X-Haul with Deterministic Ethernet - A TransPacket whitepaperEnabling 5G X-Haul with Deterministic Ethernet - A TransPacket whitepaper
Enabling 5G X-Haul with Deterministic Ethernet - A TransPacket whitepaper
 
5G RAN fundamentals
5G RAN fundamentals5G RAN fundamentals
5G RAN fundamentals
 
Cloud ran wp_tfs_nse_ae
Cloud ran wp_tfs_nse_aeCloud ran wp_tfs_nse_ae
Cloud ran wp_tfs_nse_ae
 
5 cc
5 cc5 cc
5 cc
 
Nokia_Mission-critical_Utilities_Network_Teleprotection_Application_Note_EN
Nokia_Mission-critical_Utilities_Network_Teleprotection_Application_Note_ENNokia_Mission-critical_Utilities_Network_Teleprotection_Application_Note_EN
Nokia_Mission-critical_Utilities_Network_Teleprotection_Application_Note_EN
 
Accelerating 5G enterprise networks with edge computing and latency assurance
Accelerating 5G enterprise networks with edge computing and latency assuranceAccelerating 5G enterprise networks with edge computing and latency assurance
Accelerating 5G enterprise networks with edge computing and latency assurance
 
EBlink leading fronthaul solutions - 2016
EBlink leading fronthaul solutions - 2016EBlink leading fronthaul solutions - 2016
EBlink leading fronthaul solutions - 2016
 
Day 1 LTE Technology Overview
Day 1 LTE Technology OverviewDay 1 LTE Technology Overview
Day 1 LTE Technology Overview
 
5G peek
5G peek5G peek
5G peek
 
5 g peek from cmcc 20may2013
5 g peek from cmcc 20may20135 g peek from cmcc 20may2013
5 g peek from cmcc 20may2013
 
Andy sutton - Multi-RAT mobile backhaul for Het-Nets
Andy sutton - Multi-RAT mobile backhaul for Het-NetsAndy sutton - Multi-RAT mobile backhaul for Het-Nets
Andy sutton - Multi-RAT mobile backhaul for Het-Nets
 
IEC61850: Use of IEC61850 to telecontrol MV grids (Article)
IEC61850: Use of IEC61850 to telecontrol MV grids (Article)IEC61850: Use of IEC61850 to telecontrol MV grids (Article)
IEC61850: Use of IEC61850 to telecontrol MV grids (Article)
 
Lte technology-for-engineers
Lte technology-for-engineersLte technology-for-engineers
Lte technology-for-engineers
 
109885868-LTE-Technology-for-Engineers.pdf
109885868-LTE-Technology-for-Engineers.pdf109885868-LTE-Technology-for-Engineers.pdf
109885868-LTE-Technology-for-Engineers.pdf
 
Radisys & Airspan - Small Cells and LTE-A Webinar Presentation
Radisys & Airspan -  Small Cells and LTE-A Webinar PresentationRadisys & Airspan -  Small Cells and LTE-A Webinar Presentation
Radisys & Airspan - Small Cells and LTE-A Webinar Presentation
 
Evolving to an open C-RAN Architecture for 5G
Evolving to an open C-RAN Architecture for 5GEvolving to an open C-RAN Architecture for 5G
Evolving to an open C-RAN Architecture for 5G
 

More from Spiros Louvros

Selected papers-2014 Topology Conference
Selected papers-2014 Topology ConferenceSelected papers-2014 Topology Conference
Selected papers-2014 Topology ConferenceSpiros Louvros
 
Analytical average throughput and delay estimations for LTE
Analytical average throughput and delay estimations for LTEAnalytical average throughput and delay estimations for LTE
Analytical average throughput and delay estimations for LTESpiros Louvros
 
IEEE CAMAD 2014_LTE Uplink Delay Constraints for Smart Grid Applications
IEEE CAMAD 2014_LTE Uplink Delay Constraints for Smart Grid ApplicationsIEEE CAMAD 2014_LTE Uplink Delay Constraints for Smart Grid Applications
IEEE CAMAD 2014_LTE Uplink Delay Constraints for Smart Grid ApplicationsSpiros Louvros
 
IEEE ομιλία_τελικό
IEEE ομιλία_τελικόIEEE ομιλία_τελικό
IEEE ομιλία_τελικόSpiros Louvros
 

More from Spiros Louvros (10)

Selected papers-2014 Topology Conference
Selected papers-2014 Topology ConferenceSelected papers-2014 Topology Conference
Selected papers-2014 Topology Conference
 
Analytical average throughput and delay estimations for LTE
Analytical average throughput and delay estimations for LTEAnalytical average throughput and delay estimations for LTE
Analytical average throughput and delay estimations for LTE
 
IEEE CAMAD 2014
IEEE CAMAD 2014IEEE CAMAD 2014
IEEE CAMAD 2014
 
IEEE CAMAD 2014_LTE Uplink Delay Constraints for Smart Grid Applications
IEEE CAMAD 2014_LTE Uplink Delay Constraints for Smart Grid ApplicationsIEEE CAMAD 2014_LTE Uplink Delay Constraints for Smart Grid Applications
IEEE CAMAD 2014_LTE Uplink Delay Constraints for Smart Grid Applications
 
LTE Air Interface
LTE Air InterfaceLTE Air Interface
LTE Air Interface
 
9783319006628-c1
9783319006628-c19783319006628-c1
9783319006628-c1
 
9783319006628-c1
9783319006628-c19783319006628-c1
9783319006628-c1
 
IEEE ομιλία_τελικό
IEEE ομιλία_τελικόIEEE ομιλία_τελικό
IEEE ομιλία_τελικό
 
Radio Link budget
Radio Link budgetRadio Link budget
Radio Link budget
 
Kaufman roberts paper
Kaufman roberts paperKaufman roberts paper
Kaufman roberts paper
 

IoT M2M case study analysis

  • 1. All material is Copyright © Informa Telecoms & Media IoT M2M Case study Real network projects
  • 2. 2 2 Case study 1 LTE TDD RURAL COVERAGE for M2M services
  • 3. 3 3 Project scenario Provide LTE coverage for M2M forest surveillance over mountainous rural areas Technical project requests: 1. Check for high temperature/gas/fire alerts 2. Check for video confirmations on alerting 3. All in one board architecture 4. Autonomous power – solar or PoE 5. Connect through LTE to a main server 6. Use C-RAN connectivity to minimize implementation
  • 4. 4 4 Project scenario Provide LTE coverage for M2M forest surveillance over mountainous rural areas Technical project requests: 1. Check for high temperature/gas/fire alerts
  • 5. 5 5 Project scenario Provide LTE coverage for M2M forest surveillance over mountainous rural areas Technical project requests: 2. check for video confirmations on alerting
  • 6. 6 6 Project scenario Provide LTE coverage for M2M forest surveillance over mountainous rural areas Technical project requests: 3. All in one board architecture The solution
  • 7. 7 7 Project scenario Provide LTE coverage for M2M forest surveillance over mountainous rural areas Technical project requests: 4. Autonomous plug and play Sensor probes can be easily attached by just screwing them into the bottom sockets
  • 8. 8 8 Project scenario Provide LTE coverage for M2M forest surveillance over mountainous rural areas Technical project requests: 4. Autonomous power – solar or PoE Sensor probes can be easily attached by just screwing them into the bottom sockets
  • 9. 9 9 Project scenario Provide LTE coverage for M2M forest surveillance over mountainous rural areas Technical project requests: 5. Connect through LTE to a main server The Sensor data gathered by the Waspmote Plug & Sense! nodes is sent to the Cloud by Meshlium it is a Gateway router specially designed to connect Waspmote sensor networks to the Internet via Ethernet, WiFi and 3G interfaces Meshlium LoRAWAN
  • 10. 10 10 Project scenario Provide LTE coverage for M2M forest surveillance over mountainous rural areas Technical project requests: 5. Connect through LTE (3.6 GHz) to a main server The Sensor data gathered by the Waspmote Plug & Sense! nodes is sent to the Cloud by Meshlium it is a Gateway router specially designed to connect Waspmote sensor networks to the Internet via Ethernet, WiFi and 3G interfaces Meshlium
  • 11. 11 11 Project scenario Technical project requests: 5. Connect through LTE (3.6 GHz) to a main server Forest shelter – local aggregator Indoor shelter VoIP, data/internet and O&M services
  • 12. 12 12 Project scenario Technical project requests: 5. Connect through LTE (3.6 GHz) to a main server Why LTE ??? Among proposed 3GPP technologies with non-dominant standardized solution so the most popular due to its cost effectiveness and simplicity on network implementation is the LTE-A.
  • 13. 13 13 Project scenario Technical project requests: 5. Connect through LTE (3.6 GHz) to a main server Why LTE 3.6 GHz ?? In Greece LTE 3,6 GHz is an unused band Project has been supported by government, through EU funding. Greek frequency authorities (EETT) has allocated the 3.6 GHz band free of charge to the Rural project since it is unused so far Two channel bandwidths have been reserved: - 3.6 GHz 30 MHz channel bandwidth - 3.8 GHz 30 MHz channel bandwidth
  • 14. 14 14 Project scenario Technical project requests: 5. Connect through LTE (3.6 GHz) to a main server Why LTE 3.6 GHz TDD??? In Greece LTE 3.6 GHz TDD is an unused band, leaving other TDD sub- bands available for other future services
  • 15. 15 15 Project scenario Technical project requests: 6. Use C-RAN connectivity to minimize implementation Why LTE C-RAN ??? Most world dominant vendors are proposing the LTE-A network architecture and functionality to support the C-RAN approach and to migrate towards 5G. C-RAN concept is proposed to be based on a centralized baseband processing pool equipment serving a number of clustered distributed radio access nodes (RRUs). Furthermore in legacy operator networks such as LTE-A and Heterogeneous Networks, where coordinated functionality and real-time processing is essential to performance interference as well as mobility and synchronization improvements, the cloud RAN approach is easily accommodated.
  • 16. 16 16 Project scenario Technical project requests: 6. Use C-RAN connectivity to minimize implementation Why LTE C-RAN ??? cell planning principles are quite similar to LTE-A with extra restrictions and demands adapting to the specific traffic and service. Ericsson & Huawei have lately (early 2016) proposed a combination of powerful software features to combine cloud RAN with LTE-A technology and deliver extreme application coverage with huge peak cell throughputs over existing 4G operator infrastructures, in an effort towards 5G networks aligned with 3GPP and 5GPPP standards and proposals.
  • 17. 17 17 The project architecture C-RAN architecture  use Huawei eA360 Customer Premise Equipment (CPE) at 3.6-3.8 GHz Meshlium
  • 18. 18 18 The project architecture C-RAN architecture  use Huawei DBS3900 eNodeB technology with RRU3232 at 3.6-3.8 GHz
  • 19. 19 19 The project architecture C-RAN architecture  use Huawei DBS3900 eNodeB technology with RRU3232 at 3.6-3.8 GHz
  • 20. 20 20 The project architecture C-RAN architecture  use Huawei DBS3900 eNodeB technology with BBU3232 at 3.6-3.8 GHz
  • 21. 21 21 The project architecture C-RAN architecture  use Huawei eA360 Customer Premise Equipment (CPE) at 3.6-3.8 GHz In such architectures a large number of remote Remote Radio Handlers/Remote Radio Units (RRH/RRU) are deployed over a large geographical area, all connected over front haul fibre links (dark fibre links), towards a centralized pool Base Band Unit (BBU) on cloud server with typical cell coverage ranges of 15-20 Km over fibre links for LTE-A solutions. It is widely accepted that using RRH/RRU distributed units over radio interface introduces advanced technologies over radio access network, moving processing load functions to the cell edge devices (Mobile Edge Computing solutions) and exploiting IP/ethernet with emphasis to MPLS over optical network technology for the RAN transmission and backhaul network topology.
  • 22. 22 22 The project architecture C-RAN architecture  use Huawei eA360 Customer Premise Equipment (CPE) at 3.6-3.8 GHz Such a design facilitates any kind of traffic over a well-planned LTE-A network including traditional IP subscriber web traffic, cloud services, sensor based traffic as well as generic IoT services of any kind.
  • 23. 23 23 The project architecture C-RAN settings  activate TTI bundling What is TTI bundling? TTI bundling is signaled by rrcConnectionReconfigution. You can see in 3GPP TS36.331 6.3.2. Key word is ttiBundling and MAC- MainConfig There are thresholds defined at the eNB, This trigger condition shall be checked with every UL transmission of the UEs and if the trigger condition is fulfilled, the eNB shall inititate the process to start TTI bundling for the UE.
  • 24. 24 24 The project architecture C-RAN settings  activate TTI bundling What is TTI bundling? This feature is activated in eNB as RRCReconfigurationRequest during the intial PDP context for default bearer established. Again device must be supported as device capabilities message. After that UL will be automatically group every 4 TTI. Re-transmittion of NACK is corrected at 9 sub-frames later. Basically when device is moved around at cell edge the errors of PUSCH is overwhelming therefore TTI bundling is reduced the overhead and resources of HARQ - MAC layer. Note: in Rel 10 it might not be allowed to enable both Semi-Persistent Scheduling and TTI bundling at the same time.
  • 25. 25 25 The project architecture C-RAN settings  activate TTI bundling What is TTI bundling? Like If the UE has gone in bad radio condition or cell edge where the Current Modulation and coding scheme has gone below or equal to the threshold defined for triggerring the TTI bundling. If TTI bundling measurements are ongoing and the percentage of NACKed transmissions is greater than Bler threshold for TTI bundling. Based on these criterion, eNB can trigger the TTI bundling for the UE. Similarly if the UE moves back again to good radio condition the eNB will ask the TTI bundlng to be turned off.
  • 26. 26 26 The project architecture C-RAN settings  activate TTI bundling Check also beside the options present above one could consider using additional triggers (at the eNB side to start RRC reconfig). For example: 1. PHR (power headroom) report in addition to measured UE power in the up-link. 2. Using known eNB tx power and maximal UE power to configure A1 and A2 measurement event (36.331 A1/A2=Serving becomes better/worst than threshold).
  • 27. 27 27 The project architecture C-RAN settings  activate TTI bundling Remarks 1. improving the data part (PUSCH) by TTI bundling is not enough, one need to look on the control channel send over PUCCH (e.g. use repetition). 2. 2. The implications on the MAC design are all by trivial, for example how the MAC scheduler works in both UL and DL (if PUCCH repetition is used) when combining UEs with bundling and few w/o.
  • 28. 28 28 The project architecture C-RAN settings  RRC connected users ??? There is RRC connected user license limit provided by vendor. By default, this is 60 (as per my knowledge and experience). As users increase in network, you need to buy license allowing more users from vendor. If you guide me which vendor you are working ,I might be able to send you the license parameter to check. Secondly, there is product capacity provided by the Again this can be identified if product version is known.
  • 29. 29 29 The project architecture C-RAN settings  RRC connected users ??? Do not confuse it with applicability while considering 1 ms TTI and 20 MHz BW. There is difference between theoretical and practical limitations. Specific equipment has its limitation in processing the load. This is the reason you are observing challenge in understanding this. RRC connected user capacity is provided at eNB level. This is the number of UEs in connected mode at an instance.
  • 30. 30 30 LoRAWAN RAN planning considerations  LoRAWAN technical specs.
  • 31. 31 31 LoRAWAN RAN planning considerations  LoRAWAN technical specs.
  • 32. 32 32 LoRAWAN RAN planning considerations  LoRAWAN technical specs. Our project scenario
  • 33. 33 33 LoRAWAN RAN planning considerations  LoRAWAN technical specs. Our surveillance scenario
  • 34. 34 34 C-RAN Design considerations  SINR considerations: The major concern is related to the uplink cell planning & optimization issues in such a way to guarantee adequate SINR for accepted service accessibility as well as integrity (throughput) performance.
  • 35. 35 35 C-RAN Design considerations  SINR considerations assure the signal-to-noise ration over the uplink receiving levels so that uplink RRH = arg uplink t et on RRH/RRU unit, otherwise several severe side effects might take place Suppose that CPE outdoor unit transmits on power level , arg UE o t etP and the receiving RRH unit receives a signal strength RRHSE = ,min UL RP , then RRH receiving unit will be able to successfully decode the received signal under a noisy and interference channel link. Receiving sensitivity RRHSE is defined as the minimum receiving signal level min UL RP , depending on the requested CPE outdoor unit transmitted power , arg UE o t etP and is given by the following formula: , arg min ( ) ( )UE T R o t et o o o oUL R RRH pathloss j LNA f C P G G P SE L L L L L     where jL are the jumper losses on RRH antenna unit, LNAL is the LNA losses if used, fL are the waveguide (feeder) losses, CL are the feeder connector losses over LNA. (1)
  • 36. 36 36 C-RAN Design considerations  SINR considerations The ideal condition for successful decoding on the receiving RRH unit is:   1R feeder f pathlossLNA RRH t BW f LNA N L SE N RB N G            Check next slide (2)
  • 37. 37 37 C-RAN Design considerations  SINR considerations
  • 38. 38 38 C-RAN Design considerations  SINR considerations Substituting (2) on (1) will contribute into the sufficient uplink sensitivity condition on RRH receiving unit  , arg 1( ) ( ) R feederUE T R f pathlosso t et o o o o LNA RRH t BW f pathloss j LNA f C LNA N LP G G SE N RB N L L L L L G                  , arg 1 ( ) ( ) R feeder f pathlossLNA t BW f pathloss j LNA f C LNAUE o t et T R o o o o N L N RB N L L L L L G P G G             (3)
  • 39. 39 39 C-RAN Design considerations  SINR considerations LTE-A for C-RAN has a superior power control algorithm to compensate for adequate power for the received level of however there should be further considerations regarding some extra restrictions since maintaining always condition on equation (3) is not always feasible. This is because CPE outdoor unit has predefined hardware restrictions on the maximum allowed transmitted power Moreover than that there is a maximum allowed uplink power threshold posed by RAN optimizer to mitigate and keep inter-cell interference as low as possible (an example might be the Ericsson parameter pMaxServingCell). Considering these extra restrictions equation (3) is rewritten as follows: , arg UE o t etP 0 UE P max, UE ulP   max, , arg min min ,min , ( ) ( )UE UE UE T R o ul o t et o o o oUL R RRH pathloss j LNA f C P P P G G P SE L L L L L     (4)
  • 40. 40 40 C-RAN Design considerations  SINR considerations The major problem that RAN designers might face on LTE-A C-RAN planning for IoT sensor applications is that quite often, due to load (inter-cell interference in the area), LTE-A CPE outdoor unit might easily be saturated on uplink transmitted power. This means that the power control algorithm might request (under loaded conditions) CPE outdoor unit to increase uplink transmitted power , to fulfill the RRH/RRU received SINR or power level, however the CPE outdoor unit might fail (saturates) since: , arg 0, UE req o t et uplinkP P  - Requested CPE outdoor unit transmitted power , arg max, UE UE o t et ulP P ,  hence saturates since  max, , argmin ,UE UE ul o t etP P = max, UE ulP , that is restricted from configured parameter (i.e. Ericsson parameter pMaxServingCell ). - Requested CPE outdoor unit transmitted power , arg max, UE UE o t et ulP P  hence there is enough power since  max, , argmin ,UE UE ul o t etP P = , arg UE o t etP , but on the same time , arg max, UE UE UE o o t et ulP P P   as a result fails (saturates) to respond to that power request because of hardware circuitry restrictions since   max, , argmin ,min ,UE UE UE o ul o t etP P P =  , argmin ,UE UE o o t etP P = UE oP  saturation due to power CPE outdoor specifications.
  • 41. 41 41 C-RAN Design considerations  SINR considerations The major problem that RAN designers might face on LTE-A C-RAN planning for IoT sensor applications is that quite often, due to load (inter-cell interference in the area), LTE-A CPE outdoor unit might easily be saturated on uplink transmitted power. Considering both previous conditions it holds that: Requested ( , arg UE o t etP  UE oP ) ( , arg UE o t etP  max, UE ulP ) And as a consequence always:   1R feeder f pathlossLNA eNodeB t BW f LNA N L SE N RB N G           
  • 42. 42 42 C-RAN Design considerations  SINR considerations Planning Conclusions: 1st Conclusion: C-RAN designers, considering the necessary CPE outdoor unit uplink connectivity, have to ensure that previous saturation conditions should never happen!!! 2nd Conclusion: Considering all design restrictions as well as the RRH/RRU sensitivity conditions:     max, , argmin ,min , ( ) ( ) 1 UE UE UE T R R feeder o ul o t et o o o o f pathlossLNA eNodeB t BW f pathloss j LNA f C LNA P P P G G N L SE N RB N L L L L L G                      max, , arg 1 min ,min , ( ) ( ) R feeder f pathlossLNA t BW f pathloss j LNA f C LNAUE UE UE o ul o t et T R o o o o N L N RB N L L L L L G P P P G G                , arg 1 ( ) ( ) R feeder f pathlossLNA t BW f pathloss j LNA f C LNAUE o t et T R o o o o N L N RB N L L L L L G P G G             (5)
  • 43. 43 43 C-RAN Design considerations  SINR considerations Planning Conclusions: 2nd Conclusion: Considering all design restrictions as well as the RRH/RRU sensitivity conditions: Considering strict condition for   max, , argmin ,min ,UE UE UE o ul o t etP P P = UE oP , r R  : - Initial setting of maximum power max, UE ulP parameter configuration on every cell coverage area r R (i.e. Ericsson parameter pMaxServingCell) shall be such that max, UE UE ul oP P   max, , argmin ,UE UE ul o t etP P  UE oP r R  . Simultaneous power control parameter configuration, combined with maximum geographical coverage R should be such that: , arg max, UE UE UE o t et ul oP P P  r R    max, , argmin ,UE UE ul o t etP P = , arg UE o t etP r R     max, , argmin ,min ,UE UE UE o ul o t etP P P = UE oP r R   ensuring condition , arg UE o t etP r R  .
  • 44. 44 44 C-RAN Design considerations  SINR considerations Planning Conclusions: 3nd Conclusion: A good C-RAN proposal is to use a design margin , so that any Noise and Interference peaks will be over-dimensioned and absorbed on initial design. arg 3mP dB     max, , arg arg min ,min , ( ) ( ) 1 UE UE UE T R R feeder o ul o t et o o o o f pathlossLNA eNodeB t BW f m pathloss j LNA f C LNA P P P G G N L SE N RB N P L L L L L G                      arg max, , arg 1 min ,min , ( ) ( ) R feeder f pathlossLNA t BW f m pathloss j LNA f C LNA UE UE UE o ul o t et T R o o o o N L N RB N P L L L L L G P P P G G                    arg , arg 1 Power Control decision ( ) ( ) R feeder f pathlossLNA t BW f m pathloss j LNA f C LNA UE o t et T R o o o o N L N RB N P L L L L L G P G G                 (6)
  • 45. 45 45 C-RAN Design considerations  Accessibility Considerations: Cell selection in idle mode (camping) is also crucial for the C-RAN CPE outdoor unit, since wrong cell camping will lead to RRH/RRU sensitivity condition failure!!! The answer is to follow always the 3GPP specifications (i.e. 3GPP TS 36.304)
  • 46. 46 46 C-RAN Design considerations  Accessibility Considerations: According to 3GPP TS 36.304 cell camping is validated following the recommendation:  min min 0rxlev rxlevmeas rxlev rxlev offset compensationS Q Q Q P     Where rxlevmeasQ is the real CPE outdoor unit measured downlink RRH transmitted power over the reference signals RS (RSRP signal strength measurement, minrxlevQ is a configurable cell parameter broadcasted over BCCH channel on the downlink and minrxlev offsetQ is an offset configuranle parameter for fine tuning purposes. compensationP is a power configurable parameter and according to 3GPP recommendations compensationP =  max ,0EMAX UMAXP P . EMAXP is based on 3GPP EMAXP = max, UE ulP and UMAXP is according to 3GPP UMAXP = UE oP . (7)
  • 47. 47 47 C-RAN Design considerations  Accessibility Considerations: Substituting into (7) we could get the updated cell camping suitability condition:    min min max,max ,0UE UE rxlev rxlevmeas rxlev rxlev offset ul oS Q Q Q P P     Following nominal cell planning and considering the LTE-A outdoor unit cell selection to guarantee the equation (5) sensitivity conditions, cell planners should always select camping parameters so that: - In every geographical cell coverage area r R condition to be fulfilled is  min minrxlev rxlev offsetQ Q  rxlevS r R  , so that always 0rxlevS  - In every geographical cell coverage area r R condition to be fulfilled is max, UE UE ul oP P r R  , so that always  max,max ,0UE UE ul oP P = 0 r R   0rxlevS  , r R 
  • 48. 48 48 C-RAN Design considerations  Throughput considerations. Throughput depends on SINR, pathloss as well as LoS conditions Follow excel file, provided by instructor, for further analysis