Professional Documents
Culture Documents
Enabling low latency services in standard
LTE networks
FMEC 2016
César Augusto García Pérez (cgarcia@lcc.uma.es)
Pedro Merino Gómez (pedro@lcc.uma.es)
www.q4health.eu
dmorris@redzinc.net
Donal Morris
Q4Health
Q4Health Project
• Optimization of the communications of real‐time video for emergency
services over LTE.
• The project is focused on the optimization of BlueEye, a wearable
video system designed to assist first responders by Redzinc Ltd.
• Innovation Action conducted over two FIRE experimental platforms:
PerformNetworks (UMA) and OpenAir5G Lab (Eurecom).
Q4Health
Q4Health Challenges
• Remote Assistance to the
patience during the golden
hour.
• Scenarios including bad
coverage and in‐building
handover
• Real Time video system from a
first responder wearable
• Support of QoS demands by third party
applications.
• Reduce latency (LTE and future networks).
• Optimization of BS schedulers based on app type.
• Mitigation of the effect of in‐building handovers.
• Differentiation of the QoS
Q4Health
Use Case
Q4Health
Objectives
• Improving mission critical communications by reducing the latency.
• Enable certain services on network nodes to work without much
interaction with the core network.
• Reduce the communication delay between peers located in the same
cell
• Implement an efficient group communication scheme.
Q4Health
Background: LTE Basic Architecture
Q4Health
LTE Background: Centralised Network
• The most common scenario is an EPC
operator having a single core
network.
• Besides the delay to the service the
delay to the EPC has also to be
added
• This is worst for mobile peers
communicating via a service in the
cloud.
Q4Health
LTE Background: Data plane
• The IP layer of the UE is
transported to the SGW via a
tunnel. The traffic coming from
the SGW uses a different tunnel.
• A GTP tunnel is defined by its
transport addresses (eNB and
SGW) and its TEID.
• An UE might have several
tunnels for uplink and downlink
to have traffic prioritization.
Q4Health
Background: LTE Time Split
Latency Split Measurement
Te2e Radio+EPC < 20 ms
T_EPC SGW+PGW < 2,5 ms
T_Radio UE < 5 ms
Scheduling Request < 5,5 ms
+ Grant
HARQ <2,5 ms
Retransmission
From “The impact of latency on application performance,”
Nokia Siemens Networks, White Paper., 2009.
Q4Health
Fog Gateway: Architecture
Q4Health
Fog Gateway Overview
• Create a user database based on
the GTP packets received. The
database index each user IP with
its TEID and transport addresses.
• For each packet received from the
eNB:
• If it is for an IP of the fog, remove
GTP header and inject it.
• If it is for a UE registered in the
database change the TEID and send
to the eNB
• Other cases: forward to the SGW.
Q4Health
Fog Gateway: latency reduction and
limitations
Impact of the system is low, handling the GTP headers do not take
much time. It could be improved with dedicated hardware equipment.
With SDN techniques group services can be supported more efficiently.
Combined with techniques like semi‐persistent scheduling can be very
effective reducing the latency.
And even more with modifications to the base stations.
‐ The downlink of the fog only works if the UE has previously received
downlink messages from the SGW.
‐ Handover with change of SGW might lead to packet duplication.
Q4Health
Methodology: PerformNetworks Testbed
Q4Health
Methodology: Experiments definition
• Tools developed to analyze RTT time split between the different
components of the testbed.
• All the components are synchronized with a stratum 1 GPS PTP server
• Two main scenarios:
• Conformance Testing Equipment connected to EPC
• Small Cells connected to EPC
• Experiments:
• Control plane time analysis
• Basic time split
• Channel impairments effects
• Emulated F‐GW
Q4Health
Results: Conformance Testing Equipment vs
Small cells
COTS Small Cells Conformance Testing
Equipment
Time Median MAD Median MAD
RTT(ms) RTT(ms) RTT(ms) RTT(ms)
T_e2e 28,775 4,887 11,830 0,253
Results: Control Plane Analisys
• Attach time, ongoing
progress with more
signaling procedures.
• Median 534,498 ms
• MAD 94,367 ms
• Results from samples
of all the history of the
testbed.
Q4Health
Results: RTT Baseline
Current Status
• Prototype of the F‐GW is under integration in our network.
• Tools to calculate one way delay under development.
• Prototype of video platform also deployed on the testbed.
• SDN effect of the network has been characterized.
• Exploring improved versions: non GTP stations connected to GTP
routers.
• Adding more statistics on signalling procedures (service request,
dedicated bearer establishment and usage, etc.)
Q4Health
Platform Evolution
www.q4health.eu Q4Health
Thank You!
Let’s talk…
cgarcia@lcc.uma.es pedro@lcc.uma.es
César Augusto García Pérez Pedro Merino