Presentation is loading. Please wait.

Presentation is loading. Please wait.

FRMCS Traffic Analysis Summary

Similar presentations


Presentation on theme: "FRMCS Traffic Analysis Summary"— Presentation transcript:

1 FRMCS Traffic Analysis Summary
UIC FRMCS FW-AT 2503 v1.0.1 (draft), 28 September 2017 FM56(17)026 Jos Nooijen

2 Objectives FRMCS traffic analysis
Determination of the size of the required frequency band for FRMCS operation  traffic analysis is an essential input The size of the frequency band most notably depends on: Supported functionality (traffic profile/volume and characteristics) and users The traffic density (the aggregated traffic in (dense) railway areas and lines at the busy hour) System characteristics (supported radio access technology(ies)) and the location of the frequency band in the spectrum This document presents traffic analysis results for railway operation in Europe (based on input from The Netherlands, Switzerland, Sweden and France) All traffic results in this analysis are preliminary and subject to final approval by UIC

3 Starting points and prerequisites
Mobile communication functionality (i.e. voice, video, data, messaging) is implemented using IP bearer services of mobile networks Traffic profiles (i.e. voice, video, data, messaging) are expressed in bits per second Traffic volumes/flows are calculated by considering typical (representative) areas and lines of railway operation during the busy hour

4 Traffic modelling method (1)
The foundation of the method follows the procedures as outlined in ITU document M (it follows a simplified and abbreviated form) Functional requirements as outlined in the FRMCS User Requirements Specification v2.0 and FU are used as a reference All train types are taken into account except metro trains, light rail trains and trams Railway operation of a large station (shunting yard including station area) and railway lines (high speed, low density, high density) are modelled for the busy hour(s) Traffic flow density is expressed in bps/ km2 (station area, shunting area or level crossings) or bps/km (rail segment) Traffic is scaled for future growth, degraded operation and resource management overhead The model does not prescribe how to handle the traffic (e.g. number of cells per area, redundancy scheme, single or dual layer coverage, use of repeater systems)

5 Traffic modelling method (2)
Traffic constituents: A reference railway station (including a nearby shunting area, depot/workshop, platforms) A reference train (including on-train staff and on-board systems) Reference rail segments are: low density rail segment high density rail segment (including several parallel or intersected lines, typically in urban area) high speed rail segment

6 Traffic modelling method (3)
Reference traffic constituent characteristics: Communication services: Voice (bi-directional, uni-directional, user-user, multi-user) Data (bi-directional, uni-directional, user-user, multi-user) Status of mobility (speed in km per hour, stationary) Environmental conditions: In-train, indoor (e.g. depot), inside a tunnel or outdoor

7 Traffic Categories Applications are designated to one of the following categories: Critical (e.g. railway emergency, Automatic Train Control) Performance (e.g. telemetry, video surveillance) Business (internet in trains for passengers, internet for railway staff) Critical: applications that are essential for train movement and safety or a legal obligation, such as emergency communications, shunting, presence, trackside maintenance, ATC, etc. Performance: applications that help to improve the performance of the railway operation, such as train departure, telemetry, etc. Business: applications that support the railway business operation in general, such as wireless internet, etc.

8 Traffic Scenarios Traffic Scenario Critical
This scenario comprises Critical Communication Applications and Critical Support Applications (e.g. ETCS/ATO (GoA1 and -2), driver to controller voice, emergency call, telemetry) Traffic Scenario Performance This scenario comprises Critical Communication Applications, Critical Support Applications, Performance Communication Applications and Performance Support Applications (e.g. (real time) video (camera surveillance) and monitoring) Traffic Scenario Business This scenario comprises Critical Communication Applications, Critical Support Applications, Performance Communication Applications, Performance Support Applications and Business Communication Applications (e.g. internet for passengers)

9 Utrecht station and shunting area (example)

10 Reference Railway Station
The reference railway station is representative for the main European Railway stations. It includes tracks and platforms, a nearby shunting area and a depot/workshop A typical size of a main railway station is: Length: 2 km Width: 0.2 km Area: 0.4 km2

11 Reference Railway Station Traffic

12 Reference Train Traffic

13 Reference Rail Segment Traffic (per km)
The traffic on reference rail segments is the product of the number of trains per km (2nd column of the table below) and the reference train traffic

14 Traffic during migration (1)

15 Traffic during migration (2)
Traffic during migration is based on a subset of the Applications of Scenario Critical Compared to Scenario Critical traffic is reduced significantly

16 Questions?


Download ppt "FRMCS Traffic Analysis Summary"

Similar presentations


Ads by Google