11 Railways and Maritime

21.9163GPPRelease 16Release descriptionTS

11.1 Mobile Communication System for Railways 2

760054

Mobile Communication System for Railways 2

MONASTERY2

 

SP-170451

Merkel, Juergen, Nokia

760005

Study on MONASTERY2

FS_FRMCS2

S1

SP-170588

Merkel, Juergen, Nokia

790023

Study on application architecture for the Future Railway Mobile Communication System (FRMCS) Phase 2

FS_FRMCS2_SA6

S6

SP-181133

Oettl, Martin, Nokia

760004

Stage 1 of MONASTERY2

MONASTERY2

S1

SP-170451

Merkel, Juergen, Nokia

830007

Application Architecture for MONASTERY2

MONASTERY2

S6

SP-190064

Oettl, Martin, Nokia

840009

CT aspects of MONASTERY2

MONASTERY2

ct

CP-191152

Gkatzikis, Lazaros (Nokia)

840072

CT1 aspects of MONASTERY2

MONASTERY2

C1

CP-191152

Gkatzikis, Lazaros (Nokia)

840073

CT3 aspects of MONASTERY2

MONASTERY2

C3

CP-191152

Gkatzikis, Lazaros (Nokia)

Summary based on the input provided by Nokia in SP-200941.

This Feature introduces a set of additional requirements on top of Rel-15 to support the specific communication needs of railways. It also corrects inconsistencies and clarifies ambiguities.

Amongst others functionality was added to the multi-talker functionality e.g. to allow a MCX User to manually override multi talker requests was introduced and the support of supplementary services for railway communication (private calls). A lot of focus was put on interworking between FRMCS and GSM-R and a lot of refinement effort was spent on the handling and the integration of functional alias into the 3GPP system.

All three stages were affected by this work and work was covered by CRs to TS 22.179, 22.280, 22.281, 22.282, 23.280, 23.281, 23.282, 23.282, 23.379, 24.379, 24.481, 24.483 and 23.484 under the MONASTERY2 Work Item.

References

List of related CRs: select "TSG Status = Approved" in https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=760054,760005,790023,760004,830007,840009,840072,840073

11.2 Further performance enhancement for LTE in high speed scenario

Unique_ID

Name

Acronym

WG

WID

WI Rapporteur

800079

Further performance enhancement for LTE in high speed scenario

LTE_high_speed_enh2

R4

RP-181482

NTT DOCOMO

Summary based on the input provided by NTT DOCOMO, INC. in RP-192721.

In Rel-13 and 14, the mobility and throughput performance were enhanced to cover high speeds (up to 350 km/h) by specifying the requirements for UE RRM, UE demodulation and base station demodulation, considering the two types of operator’s practical deployments shown in Figures 1 and 2. Figure 1 shows the case where no specific installation is deployed to handle high-speed trains, i.e. UEs in the train use the "standard" LTE eNBs. Alternatively, figure 2 shows the case where Single Frequency Network (SFN) are deployed. SFNs use so-called "Remote Radio Heads" (RRH), which are dedicated antennas deployed along the train track. In this case, the baseband unit (BBU) is connected to the RRH, e.g. using fiber.

Figure 1. Non-Single Frequency Network (SFN) high speed scenario

Figure 2. SFN high speed scenario

These Rel-13 and 14 enhancements were conducted both for non-SFN and for SFN, but only for LTE single carrier, i.e. not covering Carrier Aggregation (CA).

This Rel-16 work item further improves the mobility and throughput performance, now considering CA and speeds up to 500 km/h. To this aim, it enhances RRM, UE demodulation and base station demodulation: it specifies enhanced RRM core requirements and corresponding RRC signals in respectively TS 36.133 [2] and TS 36.331 [3].

Part 1: RRM requirements enhancements:

In Release 14 cases (limited to 350 km/h and single carrier), the latency requirements under DRX configuration up to 1.28s DRX cycle were enhanced by reducing the cell identification delay in connected mode and cell reselection delay in idle mode [1].

In Rel-16, considering Carrier Aggregation and speeds up to 500km/h, the following enhanced requirements were introduced to achieve good mobility performance and less paging outage:

  1. Enhanced RRM requirements for active SCells (for 350km/h velocity):

The same requirements specified in Rel-14 high speed WI are applied to active SCells.

  1. Enhanced RRM requirements for deactivated SCells (for 350km/h velocity):

The cell identification delay and measurement period are reduced.

  1. Enhanced RRM requirements in DRX in connected mode (for 500km/h velocity):

The cell identification delay and measurement period on 1.28s DRX cycle are further reduced from those in Rel-14 high speed WI.

  1. Enhanced RRM requirements in idle mode (for 500km/h velocity):

The cell detection delay is further reduced from those in Rel-14 high speed WI.

  1. Enhanced UL timing adjustment requirements in connected mode (for 500km/h velocity):

The larger maximum autonomous time adjustment step is applied when the downlink bandwidth is wider than 10MHz.

Part 2: Demodulation enhancements

  1. For UE and base station demodulation enhancements

In Release 14, UE and base station demodulation requirements were enhanced [1], for both cases of operator’s practical deployments shown in figures 1 and 2.

In Release 16, regarding the CA case in SFN (figure 2), the requirements specified in Rel-14 are expanded to Dual Connectivity’s Secondary Cells (SCells) as defined in TS 36.331 [3]. Regarding further high speed up to 500 km/h, additional requirements are introduced to ensure the PDSCH/PUSCH/PRACH demodulation performance with larger Doppler shift.

The impacts on RRC signals to meet the new requirements above are also specified.

References

List of related CRs: select "TSG Status = Approved" in:
https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=800079

[1] RP-160172, Rel-14 WID on "Performance enhancements for high speed scenario in LTE"

[2] TS 36.133, “Requirements for support of radio resource management.”

[3] TS 36.331, “Radio Resource Control.”

11.3 NR support for high speed train scenario

840092

NR support for high speed train scenario

NR_HST

R4

RP-191512

CMCC

840192

Core part: NR support for high speed train scenario

NR_HST-Core

R4

RP-191512

CMCC

840292

Perf. part: NR support for high speed train scenario

NR_HST-Perf

R4

RP-191512

CMCC

Summary based on the input provided by CMCC in RP-200776.

This WI targets to specify the UE RRM requirements, UE/BS demodulation requirements for high speed train scenario. The supported velocity is up to 500km/h and the carrier frequency is up to 3.6GHz covering both TDD and FDD.

In Rel-16 WI on NR support of high speed train scenarios, the enhanced RRM requirements and demodulation requirements were specified to support the speed of up to 500km/h and carrier frequency is up to 3.6GHz.

For RRM, to guarantee the mobility performance for the scenario with velocity up to 500km/h,both enhanced requirements for NR intra-RAT measurement and enhanced requirements for inter-RAT measurement between NR and EUTRA are specified. The enhanced requirements for NR intra-RAT include NR cell re-selection requirements, NR cell identification requirements, beam management requirements. The enhanced requirements for inter-RAT measurement between NR and EUTRA include EUTRA inter-RAT measurement requirements and NR inter-RAT measurement requirements, both idle mode and connected mode are considered.

For UE demodulation, HST-SFN (multiple RRHs are connected to one BBU with fiber), HST single tap and multi-path fading channel are considered. For HST-SFN, the maximum doppler shift is 1667Hz (500km/h + 3.6GHz) and 870Hz for 30KHz SCS and 15KHz SCS respectively. For HST single tap, the maximum doppler shift is 1667Hz and 972Hz for 30KHz SCS and 15KHz SCS respectively. For multi-path fading channel, the maximum doppler shift is 1200Hz and 600Hz for 30KHz SCS and 15KHz SCS respectively. For BS demodulation, at least HST single tap is considered. And the maximum doppler shift is 3334Hz and 1740Hz for 30KHz SCS and 15KHz SCS respectively.

References

List of related CRs: select "TSG Status = Approved" in: https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=840192,840292

11.4 Maritime Communication Services over 3GPP System

800011

Maritime Communication Services over 3GPP System

MARCOM

S1

SP-180594

Hyounhee Koo, SyncTechno Inc

730007

Study on Maritime Communication Services over 3GPP system

FS_MARCOM

S1

SP-170453

SyncTechno Inc., Hyounhee Koo

800051

Stage 1 of MARCOM

MARCOM

S1

SP-180594

Hyounhee Koo, SyncTechno Inc

Summary based on the input provided by SyncTechno Inc. in SP-200344.

The MARCOM feature introduces service requirements to enable maritime communication services to be supported over 3GPP system in TS 22.119 [1]. With the MARCOM feature, the work on maritime communication services is officially included in the scope of 3GPP standardization so 3GPP enabling technologies can be applicable to for maritime usage from 3GPP Release 16 onwards.

The first 3GPP Technical Specification (TS) 22.119 [1] covering service requirements (Stage 1) is specified for the support of maritime communication (MARCOM) over 3GPP systems.

The maritime domain, one of the 5G vertical domains in 3GPP, is moving forward with the digitalisation and mobilisation of commercial as well as safety fields. Legacy 3GPP-based technologies and solutions can be beneficial to the digitalisation and mobilisation of the maritime domain though some of the legacy 3GPP enabling technologies and solutions may not be able to fully support the performances required by the maritime domain. The maritime radio environment was not originally considered by 3GPP when the technical specifications and solutions were standardised for LTE and 5G.

However, most of the legacy mobile services and IoT services based on capabilities of EPS and 5GS specified in 3GPP specifications are applicable to maritime usage for the support of mobile broadband services, and for the support of IoT services or machine-type communication services in a vessel at sea.

In addition, there are service scenarios and requirements specified in 3GPP specifications based on requirements of other related vertical domains (e.g. public safety domain, automotive domain, factory automation domain, and satellite industrial domain). Some requirements derived by service scenarios from these related vertical domains are applicable to the maritime domain. Thus, it is beneficial to use 3GPP enabling technologies developed to satisfy those requirements for the maritime domain in terms of the economy of scale.

For example, satellite access is one of the 3GPP radio access networks supported over the 5G system, so it is possible to provide seamless maritime mobile services by integrating multiple access technologies including satellite access depending on the service scenarios. In addition, Vertical LAN that can replace Ethernet-based access are applicable to indoor maritime mobile services inside a vessel.

MC Services specified in 3GPP specifications are applicable to commercial and maritime safety fields. Some similarities exist between the public safety domain and the maritime domain in terms of service scenarios that are essentially the same. For example, in some situations, mobile communication services are supported in spite of disconnected networks, i.e. off-network mode, or under isolated conditions.

However, the maritime domain also has specific situations that do not happen in other vertical domains or in the legacy ICT industrial domain. New 3GPP enabling technologies dedicated to the maritime domain can be used to address such specific situations based on requirements derived from maritime use cases. Other vertical domains may benefit from such new 3GPP enabling technologies that consider maritime domain scenarios and may need more robust technologies or solutions than those that currently exist for those vertical domains.

The stage 1 requirements in TS 22.119 [1] are specific to maritime usage over 3GPP system for commercial as well as safety purposes. The stage 1 requirements derived from specific maritime usage but also related to MCX Services are specified in 3GPP technical specifications dedicated to MCX Services [2] [3] [4] [5].

References

List of related CRs: select "TSG Status = Approved" in:
https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=800011,730007,800051

[1] TS 22.119, Maritime communication services over 3GPP system

[2] TS 22.179, Mission Critical Push to Talk (MCPTT); Stage 1

[3] TS 22.280, Mission Critical (MC) services common requirements

[4] TS 22.281, Mission Critical (MC) video

[5] TS 22.282, Mission Critical (MC) data