Content for TR 22.890 Word version: 19.0.0

0… 4 5… 6… 7…

7.1 Introduction 7.2 Functional aspects 7.3 Performance

7 Potential Consolidated Requirements p. 19

7.1 Introduction p. 19

The requirements below refer to a "Railway Smart Station Services", which is acting as an application a FRMCS and the outer systems.

The potential consolidated requirements are mainly focusing the 5G Network characteristics and the interfaces between FRMCS/MCX Functions and Railway Smart Station Services as the application of FRMCS and outer system of 3GPP.

Copy of original 3GPP image for 3GPP TS 22.890, Fig. 7.3-1: Scope of the Potential Consolidated Requirements

Figure 7.3-1: Scope of the Potential Consolidated Requirements
(⇒ copy of original 3GPP image)

7.2 Functional aspects p. 20

Table 7.2-1: Functional Aspects Consolidated Requirements

CPR #	Consolidated Potential Requirement	Original PR #	Comment
CPR 7.2-1	The MCX service shall support obtaining and conveying MCX UE location information describing the positions of each MCX UE with different location accuracy simultaneously.	PR 6.3.6-1	intended to be included in clauses 5.11 and 6.12 of TS 22.280
CPR 7.2-2	The FRMCS shall be able to provide a mechanism to trigger an emergency alert based on a combination of UE location (e.g. the location of the specific platform door / train door) and application-generated trigger (e.g. train door did not close properly due to a blockage)	PR-6.4.6-1	intended to be included in a new clause of TS 22.280

7.3 Performance p. 20

Table 7.3-1: KPIs for Railway Smart Station Services

Scenario (Note 5)	End-to-end latency	Reliability (Note 1)	UE speed	UE Relative Speed	User experienced data rate	Payload size (Note 2)	Area traffic density	Overall UE density	Service area dimension (Note 3)
Multiple trains' stops at the same platform (Korea, urban railway)	≤10 ms	99.9999%	≤100 km/h	≤50km/h	≤1Mb/s	Small to large	≤ 1 Mb/s/km	≤ 5 (100m)	≤ 15 km along rail tracks including bad weather conditions (Note 4)
NOTE 1: Reliability as defined in TS 22.289, clause 3.1. NOTE 2: Small: payload ≤ 256 octets, Medium: payload ≤512 octets; Large: payload 513 -1500 octets. NOTE 3: Estimates of maximum dimensions. NOTE 4: Non-Line-of-Sight (NLOS) between UEs shall be supported NOTE 5: Off-network traffic characteristics are not addressed in this table since it can be covered by TR22.990.

8 Conclusions and Recommendations p. 20

This technical report collects use cases and derives potential requirements related to RAILSS. This TR also clarifies whether the identified requirements are supported by the current 5G system or whether they are new potential requirements.

The consolidated potential requirements that are related to KPIs will be considered to be added in TS 22.289. Most of other requirements may target MCX specifications, such as TS 22.280, TS 22.281, and TS 22.282.