hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.4.2 Service flows | Service flows are similar to Railway emergency voice communication, except that this is applicable to Public train emergency alert. Please refer to corresponding section in the current document.
In addition,
• the Public train emergency voice communication is not able to pre-empt Railway emergency communication.
• the Railway emergency voice communication is able to pre-empt any other ongoing voice communication including Public train emergency communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.4.3 Potential requirements and gap analysis | Potential requirements are similar to Railway emergency communication, except the followings. Please refer to corresponding section in the current document for relevant potential requirements and gap analysis.
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.24.4-001]
The Railway emergency voice communication is able to pre-empt any other ongoing voice communication including Public train emergency voice communication
A
[Needs analysis] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.5 Use case on Service interworking and service continuation with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.5.1 Description | The description is similar to the termination of Railway emergency communication, except that this is applicable to Public train emergency communication and no interworking in the direction from GSM-R Railway emergency call to FRMCS Public train emergency communication is required.
Please refer to corresponding Railway emergency communication section in the current document for relevant description. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.5.2 Service flows | Service flows for interworking - Mobile FRMCS User attached to GSM-R
There is no GSM-R counterpart for the FRMCS Public train emergency communication. No interworking in the direction from GSM-R Railway emergency call to FRMCS Public train emergency communication is required since a GSM-R Railway emergency call already initiates a FRMCS Railway Emergency Communication.
Service flows for interworking - Mobile FRMCS User attached to FRMCS
The Service flows for interworking for a Mobile FRMCS User attached to FRMCS is similar to the Railway emergency communication, except that this is applicable to Public train emergency communication.
Please refer to corresponding Railway emergency communication section in the current document for relevant description.
Service flows for service continuation
The Service flows for service continuation is similar to the Railway emergency communication.
Please refer to corresponding Railway emergency communication section in the current document for relevant description. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.24.5.3 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.24.5-001]
The FRMCS System shall provide the necessary means to FRMCS Users to set up a Public train emergency alert and /or Public train emergency voice communication, also to users in the legacy GSM-R system. Interworking between FRMCS and GSM-R should not require any changes on GSM-R system.
A
22.179
Partially covered in 6.18.4.2. Voice is covered, Alert not, as there is no Emergency alert functionality available in GSM-R.
[R-6.24.5-002]
In case of overlapping GSM-R and FRMCS serving the same geographical area, the FRMCS System shall update GSM-R about ongoing Public train Emergency communication / Public train emergency alert occurring in the FRMCS System.
Note: No interworking in the direction from GSM-R Railway emergency call to FRMCS Public train emergency communication is required since a GSM-R REC already initiates a FRMCS Railway Emergency Communication.
A
22.179
Basic functionality covered by 6.18.4.2. However, the areas in FRMCS and GSM-R will not exactly match, due to the fact that the capabilities wrt, to granularity of location in the two systems are different.
[R-6.24.5-003]
When the Railway Emergency Call in the GSM-R system is terminated, the linked Public train emergency alert and Public train emergency voice communication in the FRMCS System shall also be terminated.
A
22.179
Covered in 6.18.4.2
[R-6.24.5-004]
When the Public train emergency voice communication in the FRMCS System is terminated and there is a linked Railway Emergency Call in the GSM-R system, the Railway Emergency Call in the GSM-R system shall also be terminated.
A
22.179
Covered in 6.18.4.2 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25 Railway staff emergency communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.1 Introduction | In this chapter the use cases related to Railway staff emergency communication are defined. The following use cases are defined:
- Initiation of the Railway staff emergency alert
- New entry to the Railway staff emergency alert
- Changing of the Railway staff emergency alert
- Merging of Railway staff emergency alerts
- Leaving of the Railway staff emergency alert
- Termination of the Railway staff emergency alert;
- Initiation of Railway staff emergency voice communication
- Termination of Railway staff emergency voice communication
- Initiation of Data communication during Railway staff emergency Alert
- Service interworking and service continuation with GSM-R
- Interface to train borne recorder |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.2 General overview | The Railway staff emergency communication is very similar to the Railway emergency communication, but both serve two different purposes.
The Railway emergency communication is meant to address staff of all Railway Undertakings in a given area, whereas the Railway staff emergency communication addresses only the users of a specific Railway Undertaking in a given area.
Subsequently, where the Railway emergency communication has the Infrastructure Manager’s Controller a pivotal person in the call, in the Railway staff emergency communication, this is a Railway Undertaking’s Operator - usually someone that has a pivotal function in railways staff safety and has connections to railway police or other Railway Undertaking staff concerning safety and security.
In addition, the priority of the Railway staff emergency communication is lower than the one of the Railway emergency communication.
Furthermore, since the Railway staff emergency communication does not exist in GSM-R, no service interworking is required.
The following sections capture only use cases that show deltas compared to Railway emergency communication. For all other use cases (listed in 6.25.1), description, service flow and requirements would be the same as the corresponding Railway emergency communication use cases, except that they are applicable to Railway staff emergency communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.3 Use case on Initiation of the railway staff emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.3.1 Description | An FRMCS User is able to initiate the Railway staff emergency alert. Based on a set of conditions the FRMCS System will determine which FRMCS Users that shall be informed about the emergency.(see 6.25.2 General overview). The targeted FRMCS User can be e.g., railway staff, train staff, a train driver, an external system, a Railway staff emergency operator or maintenance staff. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.3.2 Service flows | In any service flow, a mobile FRMCS User, e.g., a train driver, railway staff, train staff or maintenance staff of a specific organisation is not able to leave or terminate the railway emergency alert.
Operator initiated
Service flows are similar to Railway emergency communication, except that the operator is not an FRMCS Operator (i.e., independent from an administrator of the FRMCS System). Please refer to corresponding section in the current document.
External system initiated
Service flows are similar to Railway emergency communication, except that the external system is not owned and operated by an FRMCS Operator (i.e., independent from an administrator of the FRMCS System). Please refer to corresponding section in the current document.
Mobile FRMCS User initiated
Service flows are similar to Railway emergency communication, except that the Mobile FRMCS User initiator is from a specific organisation and can only communicate with staff from its own organisation. Criteria to determine the FRMCS Users to be included in the Railway staff emergency alert are similar to Railway emergency communication, limited to staff from initiator’s organisation e.g., location and full or subparts of the FRMCS Functional Identity of the FRMCS Users. An example of a full FRMCS Functional Identity of an FRMCS User is a specific driver on a specific train from a specific organisation. An example of a subpart of an FRMCS Functional Identity of an FRMCS User is all train drivers and train staff from the same organisation.
Please refer to corresponding section in the current document for relevant service flows. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.3.3 Potential requirements and gap analysis | Potential requirements are similar to Railway emergency communication, except the followings. Please refer to corresponding section in the current document for relevant potential requirements and gap analysis.
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.25.3-001]
([R-6.4.3-001] not applicable to Railway staff emergency)
Request to initiate a railway staff emergency alert may come from Operators external to FRMCS Operator, External Systems or mobile FRMCS Users.
A
22.280
Operators and mobile FRMCS Users covered by R-6.15.5.2-001.
Not covered for external systems.
[R-6.25.3-002]
([R-6.4.3-002] not applicable to Railway staff emergency)
For requests from Operators, the FRMCS System shall be able to determine which FRMCS Users shall receive the railway staff emergency alert, based on the conditions supplied with the requests (e.g., a list/train number/area/track section/station).
A
22.280
Covered by R-6.15.5.2-014 (if MCX Service Ad Hoc Group mechanism can differentiate between railway staff emergency & railway emergency during initiation).
[R-6.25.3-003]
([R-6.4.3-003] not applicable to Railway staff emergency)
For requests from mobile FRMCS Users, based on the location information of the initiator and certain other conditions such as the FRMCS Functional Identity or subparts of the FRMCS Functional Identity of the FRMCS Users, track area, accuracy of the location, maximum track speed, station, shunting yard, speed and direction, the FRMCS System shall be able to determine which FRMCS Users shall receive the railway staff emergency alert.
A
22.280
Covered by R-6.15.5.2-014 (if MCX Service Ad Hoc Group mechanism can differentiate between railway staff emergency & railway emergency during initiation).
[R-6.25.3-004]
([R-6.4.3-007] not applicable to Railway staff emergency)
The FRMCS System shall be able to provide all applicable alerts to an Operator independent of whether involved in another alert or not to allow the Operators to switch between different alerts.
A
22.280
[R-5.4.2-007a]
[R-6.25.3-005]
([R-6.4.3-010] not applicable to Railway staff emergency)
The Railway emergency alert is able to pre-empt any other ongoing alert including Railway staff emergency alert
A
22.280
<Needs analysis of R-6.8.8 (Communication types based on priorities)> |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.4 Use case on New entry to the railway staff emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.4.1 Description | Description is similar to Railway emergency communication, except that additional FRMCS Users can be e.g., railway staff, train staff, a train driver, a Railway staff emergency operator or maintenance staff. Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.4.2 Service flows | Service flows are similar to Railway emergency communication, except that the priority is lower than the Railway Emergency Alert. Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.5 Use case on Changing of the railway staff emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.5.1 Description | Description is similar to Railway emergency communication, except that the authorised FRMCS User is an operator which is not an FRMCS Operator (i.e., independent from an administrator of the FRMCS System). Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.5.2 Service flows | Service flows are similar to Railway emergency communication, except that the priority is lower than the Railway Emergency Alert. Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.6 Use case on Merging of Railway Staff Emergency Alerts | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.6.1 Description | Description is similar to Railway emergency communication, except that the authorised FRMCS User is an operator which is not an FRMCS Operator (i.e., independent from an administrator of the FRMCS System). Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.6.2 Service flows | Service flows are similar to Railway emergency communication, except that the priority is lower than the Railway Emergency Alert. Please refer to corresponding section in the current document. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.7 Use case on Initiation of railway staff emergency voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.7.1 Service flows | Service flows are similar to Railway emergency voice communication, except that this is applicable to Railway staff emergency alert. Please refer to corresponding section in the current document.
In addition,
• the Railway staff emergency voice communication is not able to pre-empt Railway emergency communication.
• the Railway emergency voice communication is able to pre-empt any other ongoing voice communication including Railway staff emergency communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.7.2 Potential requirements and gap analysis | Potential requirements are similar to Railway emergency communication, except the followings. Please refer to corresponding section in the current document for relevant potential requirements and gap analysis.
Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.25.7-001]
The Railway emergency voice communication is able to pre-empt any other ongoing voice communication including Railway staff emergency voice communication
A
[Needs analysis] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.8 Use case on Service interworking and service continuation with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.25.8.1 Description | Service interworking of Railway staff emergency communication with GSM-R is not required. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7 Performance communication applications related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1 Use cases related to transmission of real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.1 Introduction | In this clause, the use cases related to the function of transmitting video in real time are defined.
- An FRMCS User requesting another FRMCS User to transmit real time video
- An FRMCS User receiving a request to transmit real time video
- An FRMCS User accepting a request to transmit real time video
- An FRMCS User rejecting a request to transmit real time video
- An FRMCS User ignoring a request to transmit real time video |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2 Use Case: An FRMCS User requesting another FRMCS User to transmit real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.1 Description | An FRMCS User can request another FRMCS User to transmit real time video. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.2 Pre-conditions | The FRMCS User has a functional Role entitled to request other FRMCS Users to transmit real time video.
The requested FRMCS User can be addressed by the assigned functional identity(ies), FRMCS User Identity, or FRMCS Equipment Identity.
The FRMCS Equipment of the requested user is capable of providing video |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.3 Service flows | Requesting FRMCS User
From a list of FRMCS Users provided by the FRMCS System, or by entering an unlisted identity, the requesting FRMCS User selects another FRMCS User to be invited. The list may contain functional identities, FRMCS User identities, FRMCS Equipment Identities, or phone numbers. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.4 Post-conditions | The FRMCS User has been requested transmission of real time video. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-7.1.2-001]
The FRMCS System shall enable an entitled FRMCS User to request another FRMCS User to transmit video in real time.
A
22.281
5.1.2.2.2-xxx
[R-7.1.2-002]
The FRMCS System shall provide a list of identities for the requesting FRMCS User to select from. The list may contain functional identities, FRMCS User identities, FRMCS Equipment Identities or E.164 numbers.
A
22.281
5.1.3.2.2-xxx
[R-7.1.2-003]
The real time video request shall either be based on the functional identity, FRMCS User Identity, FRMCS Equipment Identity or E.164 number.
A
22.280
This requirement is covered by MCCore for rail esp. 5.9a |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.3 Use Case: An FRMCS User receiving a real time video request to transmit real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.3.1 Description | An FRMCS User will receive a real time video request originated by the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.3.2 Pre-conditions | The FRMCS User has a functional Role that is entitled to receive real time video request from other FRMCS Users.
The FRMCS User’s equipment has a capability to capture real time video.
NOTE: Examples of Role management, like functional Roles, functional identities, FRMCS Equipment Identities, etc. in the railway environment are covered by Annex A.
The FRMCS User may or may not be transmitting real time video to an FRMCS User different from the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.3.3 Service flows | Requested FRMCS User
The real time video request is indicated to the FRMCS User by audible and visual notification. If the FRMCS User is not managed by a human, the audible and visual notification is not necessary. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.3.4 Post-conditions | The FRMCS User has received the real time video request.
Ongoing real time video transmission of the requested FRMCS User continues unaffected. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-7.1.3-001]
The FRMCS System shall be able to deliver requests for real time video to a FRMCS User entitled to provide real time video independent of the FRMCS User being involved in another ongoing real time video transmission without excessively using radio resources.
A
22.281
5.1.3.2.2-xxx |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.4 Use case: An FRMCS User accepting a request to transmit real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.4.1 Description | An FRMCS User can accept the invitation sent by the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.4.2 Pre-conditions | The FRMCS User has received a request to transmit real time video. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.4.3 Service flows | Requested FRMCS User
The FRMCS User accepts the request to transmit real time video.
Requesting FRMCS User
The FRMCS User receives a notification that the requested FRMCS User accepted the request. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.4.4 Post-conditions | The requested FRMCS User captures and transmits video in real time to the requesting FRMCS User.
In case the FRMCS User receives multiple requests to stream the video, the FRMCS System will handle this in a resource efficient way i.e. by streaming the video from the FRMCS User to the FRMCS System via the radio only once and distributing it from there to the different FRMCS Users. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-7.1.4-001]
The FRMCS User shall be able to accept to accept a real time video transmission request.
A
22.281
5.1.3.2.2-xxx esp. 5.1.3.2.2-003
5.2.6.2.1-xxx
[R-7.1.4-002]
If entitled to, a FRMCS User shall be able to provide real time video captured by itself to the FRMCS User requesting the video.
A
22.281
5.1.3.2.2-xxx esp. 5.1.3.2.2-003
5.2.6.2.1-xxx
[R-7.1.4-003]
In case of multiple requests to stream the same video to several FRMCS Users the FRMCS System shall handle this in a resource efficient manner.
A
22.281
5.2.6.2.4-001 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.5 Use case: An FRMCS User rejecting a request to transmit real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.5.1 Description | An FRMCS User can reject the invitation sent by the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.5.2 Pre-conditions | The FRMCS User has received a request to transmit real time video. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.5.3 Service flows | Requested FRMCS User
The FRMCS User rejects the request to transmit real time video.
Requesting FRMCS User
The FRMCS User receives a notification that the requested FRMCS User rejected the request. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.5.4 Post-conditions | The requested FRMCS User does not transmit video to the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.5.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-7.1.5-001]
The FRMCS User shall be able to reject a real time video transmission request.
A
22.281
5.2.6.2.4-xxx
[R-7.1.5-002]
The FRMCS System shall automatically reject requests to FRMCS Users not entitled to provide video or not capable of providing video (e.g. no camera in the FRMCS Equipment).
A
22.281
5.2.6.2.4-001
5.1.3.1.2-001
[R-7.1.5-003]
The requesting FRMCS User shall be notified of the reason for rejection.
A
22.280
This is an implicit functionality of group communication setup
6.2.1-xxx |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.6 Use case: An FRMCS User ignoring a request to transmit real time video | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.6.1 Description | An FRMCS User can ignore the invitation sent by the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.6.2 Pre-conditions | The FRMCS User has received a request to transmit real time video. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.6.3 Service flows | The requested FRMCS User does not respond.
The timeout expires.
The requesting FRMCS User receives a notification that the invitation was rejected due to a timeout. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.6.4 Post-conditions | The requested FRMCS User does not transmit video to the requesting FRMCS User. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.1.6.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
FRMCS User
[R-7.1.6-001]
If the receiving FRMCS User has not reacted on the invitation within a certain period of time [t1] the FRMCS System shall notify the inviting FRMCS User accordingly and stop the invitation request.
22.280
This is an implicit functionality of group communication setup
6.2.1-xxx |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2 Transfer of CCTV archives related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.1 Introduction | In this chapter, the use cases related to CCTV and the use of FRMCS are defined.
• Transfer of CCTV archives from Train to Ground
• Massive Inter-carriage data transfer |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.2 Use Case: Bulk Transfer of CCTV archives from Train to Ground | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.2.1 Description | This use case describes the bulk transfer of CCTV archives from the on-board system to the ground system. This use case assumes the following:
• The retention time for the recordings in the on-board system is seven days.
• The minimum retention time for the CCTV recordings in the ground system is 31 days.
• Bulk transfer of CCTV archives is performed only when train approaches stations in order to stop and at the depot.
An example calculation of the CCTV storage need during 31 days period is provided in Figure.7.2.2.1-1.
Figure.7.2.2.1-1. Onboard CCTV storage sizes with different offload rates.
Next, an example estimation is provided to illustrate the offload performance with different uplink speeds, when the train is commuting from Helsinki to Kemijärvi. The parameters for the calculation are provided in Table 1, whereas the offload results for uplink speeds of 400 Mbps, 750 Mbps and 1000 Mbps are provided respectively in Figure 7.2.2.1-2, Figure 7.2.2.1-3 and in Figure 7.2.2.1-4.
Station
Arrives
Departs
Stop time
Time between stations
HELSINKI
18:52
PASILA
18:57
19:00
0:03
0:08
TIKKURILA
19:41
19:44
0:03
0:44
RIIHIMÄKI
20:19
20:22
0:03
0:38
HÄMEENLINNA
20:46
20:48
0:02
0:26
TAMPERE
21:38
22:11
0:33
1:23
PARKANO
23:03
23:06
0:03
0:55
SEINÄJOKI
0:08
0:10
0:02
1:04
KOKKOLA
1:37
1:39
0:02
1:29
YLIVIESKA
3:10
3:12
0:02
1:33
OULU
4:42
5:00
0:18
1:48
KEMI
6:08
6:12
0:04
1:12
ROVANIEMI
7:47
7:55
0:08
1:43
MISI
8:31
8:32
0:01
0:37
KEMIJÄRVI
9:00
9:05
0:05
0:33
Table 7.2.2.1-1. The parameters for the offload calculation for the train route between Helsinki and Kemijärvi.
Figure 7.2.2.1-2. The offload results with uplink speed of 450 Mbps.
Figure 7.2.2.1-3. The offload results with uplink speed of 750 Mbps.
Figure 7.2.2.1-4. The offload results with uplink speed of 1000 Mbps. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.2.2 Pre-conditions | • Bulk transfer of CCTV archives is performed only when the train stops at the stations.
• Mobile communication infrastructure between train and ground system enables transfer of CCTV archives from train to the ground system while the train stops at the stations.
• The ground system supports sufficient archiving system for the transferred recordings. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.2.3 Service flows | 1. The train approaches the station.
2. Mobile communication system in train establishes connection dedicated for the transfer of CCTV archives with the ground system at a priority level allowing critical communication to continue in parallel
3. The transfer of CCTV archives is started upon successful connection with the ground system.
4. The transfer of CCTV archives is stopped when the connection is no longer available. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.2.4 Post-conditions | • The on-board CCTV system may re-write over the seven days and older recordings that have been transferred.
• The on-board mobile communication system remains monitoring the next approach of station. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.2.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-7.2.2-001]
The FRMCS System shall be able to support that CCTV archives can be transferred into the ground system in a time and resource efficient way with a minimum of 1 Gbps in dedicated places such as stations or train depots.
A/T
TS 22.289
See: http://www.3gpp.org/technologies/keywords-acronyms/97-lte-advanced
TS 22.289
[R4.1.2-1]
[R4.1.2-2]
[R4.1.2-3]
[R4.1.2-4]
[R-7.2.2-002]
Transferring CCTV archives shall not affect mission critical communication.
NOTE: Transferring CCTV archives is not considered to be a mission critical service.
A/T
TS 22.289
TS 22.289
[R4.1.2-1]
[R4.1.2-2]
[R4.1.2-3]
[R4.1.2-4] |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.3 Use Case: Massive Inter-carriage data transfer | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.3.1 Description | This use case describes the transfer of CCTV archives inside the train from different storages and through Inter-carriage links into the FRMCS node providing the uplink connection with the ground system. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.3.2 Pre-conditions | • Mobile communication infrastructure between train and ground system enables transfer of CCTV archives from train to the ground system while the train stops at the stations.
• The ground system supports sufficient archiving system for the transferred recordings.
• The Inter-carriage links support the same throughput speed as the FRMCS node providing the uplink. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.3.3 Service flows | Mobile communication system in train establishes connection between carriages of the train dedicated for the transfer of CCTV archives to a central node in the train form which the uplink to the ground system will take place. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.3.4 Post-conditions | Recording capacity is freed up in the carriages. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-7.3-001]
The FRMCS System shall facilitate the onboard CCTV communication between carriages of a train, to collect CCTV content at one place on the train for transfer to the ground system.
A/T
22.289
CR 22.289
R4.3.1-001-003
[R-7.3-002]
The onboard CCTV communication between carriages of a train shall not impact mission critical communication
NOTE: Transferring CCTV archives is not considered to be a mission critical service.
A/T
22.289
CR 22.289
R4.3.1-001-003 |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.4 Void | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5 On-train outgoing voice communication from train staff towards a ground user related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.1 Introduction | In this chapter the use cases related to on-train outgoing voice communication from train staff towards a ground user e.g. controller are defined. The following use cases are defined:
• Initiation of on-train outgoing voice communication by the train staff
• Termination of on-train outgoing voice communication by the train staff
• Service interworking with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.2 Use case: Initiation of on-train outgoing voice communication from train staff | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.2.1 Description | FRMCS User at the train shall be able to initiate a voice communication to any FRMCS User (s) at the ground. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.2.2 Pre-conditions | The FRMCS User, member of the train staff, is authorised to initiate the voice communication.
The FRMCS System is able to retrieve location information of the FRMCS User at the train to address the appropriate FRMCS Users at the ground. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.2.3 Service flows | The FRMCS User at the train (member of the train staff) initiates the voice communication to an FRMCS User at the ground (one or multiple). This kind of voice communication requires the QoS category of NON-CRITICAL VOICE (see [QoS]) within the FRMCS system.
The FRMCS System establishes the voice communication among the FRMCS user(s) within a setup time specified as NORMAL (see [QoS]).
The activated identities to the FRMCS User(s) are presented to all FRMCS Users during the entire voice communication.
This kind of communication can become part of the communication arbitration management.
On demand this voice communication can be recorded for post processing purposes.
If two or more than two FRMCS Users are part of the voice communication, multi talker control applies. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.2.4 Post-conditions | The FRMCS User at the train is able to communicate to the FRMCS Users at the ground. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.2.5 Potential requirements and gap analysis | Reference Number
Requirement te5t
Application / Transport
SA1 spec covering
Comments
[R-7.5.2-001]
The FRMCS System shall setup a voice communication between one FRMCS User at the train and one/multiple FRMCS Users on the ground based. The NON-CRITICAL VOICE QoS class shall apply for this kind of communication.
A
22.179
22.280
TS 22.179 Floor Control clause 6.2.3.2 Req #1,
TS 22.280 clause 5.1 req # 2
[R-7.5.2-002]
The location information of the FRMCS User at the train shall be used to locate and address the responsible FRMCS Users on the ground.
A
22.280
R-5.6.2.1.2-002
R-5.6.2.4.1-004
R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)
R-6.6.4.2-002b
R-6.6.4.1-XXX User regroup
[R-7.5.2-003]
The FRMCS System shall verify if the FRMCS User at the train as well as the FRMCS Users on the ground are authorised to establish the communication.
A
22.280
5.1.x
[R-7.5.2-004]
The FRMCS System shall establish the voice communication between the FRMCS User at the train and the FRMCS Users on the ground within a setup time specified as NORMAL (see [QoS]).
A
N/A
See section 12.10 below
[R-7.5.2-005]
The FRMCS System shall provide for on-train to one/multiple ground FRMCS User:
• arbitration information to the FRMCS User
• communication recording
• Multi-Talker Control.
A
22.280
Arbitration:
[R-5.4.2-004]
[R-5.4.2-004A]
[R-5.4.2-004B]
Multiuser talker control, recording: See relevant section |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.3 Use case: Termination of on-train outgoing voice communication from train staff | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.3.1 Description | The FRMCS User that is member of train staff shall be able to terminate the voice communication towards the FRMCS Users on the ground.
The FRMCS User on the ground shall be able to put on hold, leave or terminate the on-train voice communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.3.2 Pre-conditions | The on-train outgoing voice communication is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.3.3 Service flows | Member of train staff termination
The FRMCS User that is member of the train staff terminates the voice communication.
The FRMCS system releases the voice communication.
Communication on hold
A FRMCS User on the ground put the voice communication on hold.
The communication remains active in the FRMCS system and the FRMCS User on the ground user is able to re-join the communication.
Leaving the communication
The FRMCS User at the ground user is able to leave the voice communication if more than one FRMCS User at the ground is part of the voice communication.
Communication Termination by the ground FRMCS User
Any FRMCS User on the ground is able to terminate the voice communication between train staff and the ground user.
The FRMCS system releases the voice communication. All involved FRMCS Users are informed about. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.3.4 Post-conditions | The on-train outgoing voice communication is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.3.5 Potential requirements and gap analysis | Reference Number
Requirement te5t
Application / Transport
SA1 spec covering
Comments
[R-7.5.3-001]
The FRMCS System shall allow an authorised FRMCS User at the train that is part of the On-train outgoing voice communication, to terminate the voice communication.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is sufficient to mimic the desired behavior"
[R-7.5.3-002]
Based on the On-train outgoing voice communication termination request, the FRMCS System shall release the voice communication.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is sufficient to mimic the desired behavior"
[R-7.5.3-003]
If authorised, a FRMCS User on the ground shall be able to put the train staff to ground user voice communication on hold if more than one ground FRMCS Users are part of the voice communication.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is sufficient to mimic the desired behavior"
[R-7.5.3-004]
After the FRMCS User has put the voice communication on hold, the communication shall remain active and the FRMCS User on the ground shall be able to re-join the communication.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is sufficient to mimic the desired behavior"
[R-7.5.3-005]
If more than one FRMCS Users on the ground participate to an On-train outgoing voice communication from train staff towards a ground user, the FRMCS User on the ground user shall be able to withdraw from the communication with ability to re-join. The remaining FRMCS Users shall be informed about the withdrawn FRMCS User.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is sufficient to mimic the desired behavior"
[R-7.5.3-006]
If authorised, the FRMCS User at the train or the FRMCS Users on the ground shall be able to terminate the train staff to ground user voice communication. The FRMCS system shall inform the involved FRMCS Users about the release of the communication.
A
22.280
6.4.4 002; 6.4.5 001; 5.1.5 003-008
R-6.4.4-003, R-6.4.4-004
The affiliation mechanism is sufficient to mimic the desired behavior" |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.4 Use case: Service interworking with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.4.1 Description | For coe5istence between FRMCS System and the legacy GSM-R communication system, service interworking among the systems is required.
Depending on the scenario a ground FRMCS User can be attached to the FRMCS system, to the GSM-R system or both. The FRMCS User at the train can be attached either to the GSM-R system or to the FRMCS system.
This use case only applies to an FRMCS Equipment that supports FRMCS System and GSM-R. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.4.2 Pre-conditions | The FRMCS User is either attached to the FRMCS System or to GSM-R. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.4.3 Service flows | FRMCS User (Train staff) attached to GSM-R
When the FRMCS User (member of the train staff) is attached to the GSM-R system and is initiating voice communication to FRMCS Users on the ground, the GSM-R system will route the voice communication to the FRMCS User on the ground accordingly.
If the FRMCS User on the ground is registered to the FRMCS System, the GSM-R system establishes the communication considering the appropriate addressing scheme.
FRMCS User (Train staff) attached to FRMCS System
When the FRMCS User (member of train staff) is active in the FRMCS system and is initiating voice communication to FRMCS Users on the ground, the FRMCS system will establish the communication considering the appropriate addressing schemes applicable for FRMCS System as well as to GSM-R accordingly.
FRMCS User (Train staff) relocates between GSM-R and FRMCS System/FRMCS System and GSM-R
When the FRMCS User (train staff) relocates between GSM-R - FRMCS System or vice versa the communication service requires continuation. An interruption of the applicable bearer service is acceptable. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.4.4 Post-conditions | The communication continues if the FRMCS User at the train relocates between GSM-R and FRMCS System or vice versa. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.5.4.5 Potential requirements and gap analysis | Reference Number
Requirement te5t
Application / Transport
SA1 spec covering
Comments
[R-7.5.4-001]
The FRMCS System shall provide the necessary means to allow FRMCS Users to be reachable from the legacy GSM-R system.
A
22.179
Covered in 6.18.4.2
[R-7.5.4-002]
The FRMCS System shall provide the necessary means to FRMCS Users to set up On-train outgoing voice communication including users registered to the GSM-R system.
A
22.179
Covered in 6.18.4.2
[R-7.5.4-003]
When the FRMCS User has to relocate between FRMCS System and GSM-R or vice a versa, the voice communication service shall continue. The interruption of the bearer service associated with the relocating FRMCS User is acceptable.
Note : This requirement applies to FRMCS Equipment that contains FRMCS UE and GSM-R UE capabilities.
A
N/A
Call has to be re-established by UE. This is UE function outside scope of 3GPP |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6 Real-time video communication (video conferencing) related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.1 Introduction | A real-time video communication (video conferencing) can be used to support railway operations, such as maintenance staff when investigating infrastructure or vehicles components where help is needed from other staff or during testing of infrastructure or vehicles.
Real-time video communication (video conferencing) is supported by the FRMCS System. That encompasses user-to-user as well as multiuser video communication, including audio, and is applicable to On-network only.
In this chapter the use cases related to real-time video communication (video conferencing) are described. The following use cases are identified:
- An FRMCS User initiates a video conference
- An FRMCS User leaves and re-joins a video conference
- An FRMCS User terminates a video conference
- An FRMCS User changes from a video conference to a voice-only conference
- An FRMCS User changes from a voice-only conference to a video conference
- An FRMCS User joins an ongoing video conference |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.2 Use case: Initiation of video conference | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.2.1 Description | An FRMCS User is able to set up a video conference to other FRMCS User(s). This encompasses transmission of synchronized video aud audio information under conditions. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 7.6.2.2 Pre-conditions | The initiating FRMCS User is authorised to initiate a video conference.
The receiving FRMCS User(s) is(are) authorised to use video conference. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.