Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TR 21.917  Word version:  17.0.1

Top   Top   Up   Prev   Next
0…   5…   5.2   6…   6.3…   6.3.2…   6.3.3…   6.3.4…   7…   7.4…   8…   9…   10…   11…   11.9…   12…   13…   14…   15…   15.6…   16…   17…   18…   18.10…   19… 
6.3 Specific verticals support  6.3.1 Railways  6.3.1.1 Enhancements to Application Architecture for the Mobile Communication System for Railways Phase 2  6.3.1.2 Enhanced NR support for high speed train scenario (NR_HST)  6.3.1.2.1 NR_HST for FR1  6.3.1.2.2 NR_HST for FR2  6.3.1.3 NR Frequency bands for Railways  6.3.1.3.1 Introduction of 900MHz NR band for Europe for Rail Mobile Radio (RMR)  6.3.1.3.2 Introduction of 1900MHz NR TDD band for Europe for Rail Mobile Radio (RMR) 
...

 

6.3  Specific verticals support  p. 30

6.3.1  Railways  p. 30

6.3.1.1  Enhancements to Application Architecture for the Mobile Communication System for Railways Phase 2  p. 30

UID Name Acronym WG WID WI rapporteur name/company
840042Complete Gap Analysis for Railways Mobile Communication SystemMONASTERYENDS1SP-190312Gach, Guillaume, UIC
890035Enhancements to Application Architecture for the Mobile Communication System for Railways Phase 2eMONASTERY2SP-191104Oettl, Martin, Nokia
840037Stage 2 of eMONASTERY2eMONASTERY2S6SP-191104Oettl, Martin, Nokia
890063Stage 3 of eMONASTERY2eMONASTERY2C1CP-202256Gkatzikis, Lazaros, Nokia(Nokia)
840043Study on Future Railway Mobile Communication System3FS_FRMCS3S1SP-200578Gach, Guillaume, UIC,
Summary based on the input provided by Nokia in SP-220485.
The railway community is considering a successor to GSM-R, with 2G-based GSM-R technology envisaged to be completely replaced around 2030.
Initial specification work has been done in Release 15 on developing support for railway requirements for MCPTT group calls (on-network) to support the multi-talker feature and to allow the use of functional aliases. Additional specification work has been done in Release 16 on supporting railway requirements for MCPTT group and private calls and on enabling the use of functional aliases in MCPTT private calls, MCVideo and MCData service.
Additional Stage 1 requirements were identified in Release 17 (MONASTERYEND) and Stage 2 architectural solutions were developed in Release 17 (eMONASTERY2 / MONASTERY2_ARCH) which were specified in Stage 3 (eMONASTERY2).
The Mission Critical Communication framework specified by 3GPP is used as bases for railway communication and is continuously extended with railway specific functionality.
For Release 17 the Mission Critical Communication were enhanced with new functionality required by the railway community to support call forwarding and call transfer for private MCPTT calls. The MCData IP connectivity service was extended to support functional aliases and an MC service user can select an appropriate functional alias when be called by another MC service user. The relationship between MC service groups and the use of functional aliases is clarified, including those functions preventing de-affiliation when using a specific functional alias(es) or providing a list of functional aliases used by affiliated group members. For MCVideo services the use of functional aliases was added and is now available as for MCPTT. A functional alias as target address for MCPTT private emergency calls was specified and can be used as alternative to MCPTT IDs. An MC service user can now request an application layer priority, which allow arbitration of multiple service requests by MC service servers.
References
Related CRs:
set "TSG Status = Approved" in: https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=840042,890035,840037,890063,840043
[6.3.1.1-1]
TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1"
[6.3.1.1-2]
TS 22.281: "Mission Critical (MC) video"
[6.3.1.1-3]
TS 22.282: "Mission Critical (MC) data"
[6.3.1.1-4]
TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1"
[6.3.1.1-5]
TS 22.289: "Mobile communication system for railways"
[6.3.1.1-6]
TS 23.280: " Common functional architecture to support mission critical services; Stage 2"
[6.3.1.1-7]
TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2"
[6.3.1.1-8]
TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2"
[6.3.1.1-9]
TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems"
[6.3.1.1-10]
TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2"
[6.3.1.1-11]
TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; Protocol specification"
[6.3.1.1-12]
TS 24.282: "Mission Critical Data (MCData) signalling control; Protocol specification"
[6.3.1.1-13]
TS 24.481: "Mission Critical Services (MCS) group management; Protocol specification"
[6.3.1.1-14]
TS 24.483: "Mission Critical Services (MCS) Management Object (MO)"
[6.3.1.1-15]
TS 24.484: "Mission Critical Services (MCS) configuration management; Protocol specification"
[6.3.1.1-16]
TS 24.582: "Mission Critical Data (MCData) media plane control; Protocol specification"
Up

6.3.1.2  Enhanced NR support for high speed train scenario (NR_HST)  p. 31

6.3.1.2.1  NR_HST for FR1  p. 31
UID Name Acronym WG WID WI rapporteur name/company
890058Enhanced NR support for high speed train scenario for frequency range 1 (FR1)NR_HST_FR1_enhRP-210833CMCC
890158Core part: Enhanced NR support for high speed train scenario for FR1NR_HST_FR1_enh-CoreR4RP-210833CMCC
890258Perf. part: Enhanced NR support for high speed train scenario for FR1NR_HST_FR1_enh-PerfR4RP-210833CMCC
Summary based on the input provided by CMCC in RP-220631.
This WI specifies the UE RRM requirements for carrier aggregation (CA) and UE demodulation requirements for CA for FR1 high speed train scenario (HST). The supported velocity is up to 500km/h and the carrier frequency is up to 3.6GHz covering both TDD and FDD. This WI is the enhancement of Rel-16 WI NR-HST (WID: RP-191512), which targets for single carrier scenario.
In Rel-17 WI on enhanced NR support for high speed train scenario for frequency range 1 (FR1), the enhanced RRM requirements and demodulation requirements for CA were specified to support the speed of up to 500km/h and carrier frequency of up to 3.6GHz.
For RRM, to guarantee the mobility performance for FR1 HST with velocity up to 500km/h, both enhanced requirements for NR inter-frequency measurement and enhanced requirements for CA scenario are specified in TS 38.133. The enhanced requirements for NR inter-frequency measurement include NR cell re-selection requirements, time period for PSS/SSS detection, time period for time index detection and measurement period requirements. The enhanced requirements for CA include both measurement on activated SCells and measurement on deactivated SCells.
For UE demodulation requirements for CA, both HST-SFN (High Speed Train Single Frequency Network) joint transmission scheme and DPS (Dynamic Point Selection) transmission scheme are considered, and the requirements are specified in TS 38.101-4. With speed of up to 500km/h and carrier frequency of up to 3.6GHz, the maximum doppler shift is 1667Hz and 870Hz for 30KHz SCS and 15KHz SCS respectively. For 15KHz SCS, specify PDSCH requirements on single carrier of BW of {5, 10, 15, 20, 25, 30,35, 40, 45, 50} MHz. For 30KHz SCS, specify PDSCH requirements on single carrier of BW of {5, 10, 15, 20, 25, 30, 40, 50, 60, 80, 90, 100} MHz.
References
Related CRs:
set "TSG Status = Approved" in: https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=890058,890158,890258
Up
6.3.1.2.2  NR_HST for FR2  p. 31
UID Name Acronym WG WID WI rapporteur name/company
890060NR support for high speed train scenario in frequency range 2 (FR2)NR_HST_FR2RP-210800Samsung
890160Core part: NR support for high speed train scenario in FR2NR_HST_FR2-CoreR4RP-210800Samsung
890260Perf. Part: NR support for high speed train scenario in FR2NR_HST_FR2-PerfR4RP-210800Samsung
Summary based on the input provided by Ericsson in RP-220191.
This WI is targeted to specify NR UE RF requirements, RRM requirements and BS/UE performance requirements for train roof-mounted high-power devices in HST scenario with speed up to 350km/h and applicable frequency is up to 30GHz. The considered FR2 HST scenario is different from existing 3GPP WIs (for either LTE or NR) with operating bands up to 3.5GHz, and the NR FR2 RRM and demodulation requirements for non-HST scenarios are also not applicable and need to be specified.
In this WI, the FR2 HST deployment scenarios are studied, based upon which FR2 HST channel models are provided accordingly. From radio resource management (RRM) and demodulation perspectives, FR2 HST scenario is focused and evaluated, with the feasibility of FR2 HST scenario being technically confirmed.
For UE RF requirement, FR2 power class 6 for band n257, n258 and n261 is newly introduced, which is corresponding to the UE type of high speed train roof-mounted UE. Relevant UE TX and RX RF requirements for power class 6 are specified, in which the TX and EIS spherical coverage requirements are defined over the newly introduced spherical coverage evaluation areas. For UE beam correspondence requirement, the applicability rule and requirement side conditions are specified.
The RRM requirements for FR2 HST scenarios are introduced and enhanced over existing FR2 RRM requirements. Specifically, the enhancements for FR2 HST are introduced on cell re-selection, RRC connection mobility control, gradual timing adjustment, SSB based radio link monitoring and beam failure detection, intra-frequency measurement and L1-RSRP/SINR measurement. The new requirements of one shot large UL timing adjustment and TCI state switch delay are specified for FR2 HST scenarios.
The BS/UE performance requirements are discussed for FR2 HST scenarios, which will be further completed in the performance phase of this WI.
References
Related CRs:
set "TSG Status = Approved" in: https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=890060,890160,890260
[6.3.1.2.2-1]
TR 38.854: v0.4.0, R4-2206594, NR support for high-speed train scenario in frequency range 2 (FR2), Nokia, Nokia Shanghai Bell, and Samsung.
[6.3.1.2.2-2]
RP-220317: Status report for WI NR support for high-speed train scenario in frequency range 2 (FR2), Samsung.
Up

6.3.1.3  NR Frequency bands for Railways  p. 32

6.3.1.3.1  Introduction of 900MHz NR band for Europe for Rail Mobile Radio (RMR)  p. 32
UID Name Acronym WG WID WI rapporteur name/company
911016Introduction of 900MHz NR band for Europe for Rail Mobile Radio (RMR)NR_RAIL_EU_900MHzRP-211495UIC
911116Core part: NR_RAIL_EU_900MHzNR_RAIL_EU_900MHz-CoreR4RP-211495UIC
911216Perf. part: NR_RAIL_EU_900MHzNR_RAIL_EU_900MHz-PerfR4RP-211495UIC
This work item adds the support of Railways communications for bands n100 in CEPT countries.
It deals with the use of the Rail Mobile Radio spectrum in the 900MHz frequency band, which was assigned by the ECC Decision (20)02 [2] for the use by the railways in Europe.
It addresses all the necessary precautions to make the paired spectrum of 874.6-800/919.4-925MHz usable for 5G NR.
References
Related CRs:
set "TSG Status = Approved" in: https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=911016,911116,911216
[6.3.1.3.1-1]
TR 38.853: Introduction of 900MHz NR band for Europe for Rail Mobile Radio (RMR)
[6.3.1.3.1-2]
ECC Decision (20)02: "Harmonised use of the paired frequency bands 874.4-880.0 MHz and 919.4-925.0 MHz and of the unpaired frequency band 1900-1910 MHz for Railway Mobile Radio (RMR) ".
Up
6.3.1.3.2  Introduction of 1900MHz NR TDD band for Europe for Rail Mobile Radio (RMR)  p. 32
UID Name Acronym WG WID WI rapporteur name/company
911017Introduction of 1900MHz NR TDD band for Europe for Rail Mobile Radio (RMR)NR_RAIL_EU_1900MHz_TDDRP-211542UIC
911117Core part: NR_RAIL_EU_1900MHz_TDDNR_RAIL_EU_1900MHz_TDD-CoreR4RP-211542UIC
911217Perf. part: NR_RAIL_EU_1900MHz_TDDNR_RAIL_EU_1900MHz_TDD-PerfR4RP-211542UIC
This work item deals with the use of the Rail Mobile Radio spectrum in the 1900MHz frequency band, which was assigned by the ECC Decision (20)02 [2] for the use by the railways in Europe, in CEPT countries.
It addresses all the necessary precautions to make the unpaired spectrum of 1900-1910MHz usable for 5G NR.
References
Related CRs:
set "TSG Status = Approved" in: https://portal.3gpp.org/ChangeRequests.aspx?q=1&workitem=911017,911117,911217
[6.3.1.3.2-1]
TR 38.852: Introduction of 1900MHz NR band for Europe for Rail Mobile Radio (RMR)
[6.3.1.3.2-2]
ECC Decision (20)02: "Harmonised use of the paired frequency bands 874.4-880.0 MHz and 919.4-925.0 MHz and of the unpaired frequency band 1900-1910 MHz for Railway Mobile Radio (RMR)".
Up

Up   Top   ToC