Tech-invite   3GPPspecs   Glossaries   IETFRFCs   Groups   SIP   ABNFs   Ti+   Search in Tech-invite

Top   in Index   full‑ToC   Next

TR 23.790 (SA6)
Study on Application Architecture
for the Future Railway Mobile Communication System (FRMCS)

3GPP‑Page   full‑ToC    
use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V15.0.0 (Wzip)  2017/12  46 p.

Rapporteur:  Mr. Oettl, Martin
See also:

The railway community is considering a successor to GSM-R with first FRMCS trial implementations expected to start around 2020.

The Future Railway Mobile Communication System (FRMCS) functional working group of the International Union of Railways (UIC) have investigated and summarised their requirements for the next generation railway communication system in the Future Railway Mobile Communication User Requirement Specification (URS). The requirements have been shared with 3GPP.

The present document identifies gaps between the FRMCS requirements and stage 2 mission critical services specifications. For those gaps that cannot be fulfilled by the existing architecture, functional architecture enhancements, new procedures and information flows are documented and suggested as candidates for normative specifications.

The study takes existing 3GPP functionality and those specified for Mission Critical Communication in normative specifications TS 23.379 (MCPTT), 23.280 (Common functional architecture), 23.281 (Mission Critical Video) and TS 23.282 (Mission Critical Data) into account. Studies on migration and interconnection (TR 23.781) and interworking between LTE and non-LTE systems (TR 23.782) are considered.

full Table of Contents for  TR 23.790  Word version:   15.0.0


Here   Top


1  ScopeWord-p. 7
2  References
3  Definitions and abbreviationsWord-p. 8
4  Gap Analyses
5  Solutions
5.1  Introduction
5.2  Multi-talker feature control
5.3  Functional alias(es)
5.3.1  Solution FA1: Call processing to support functional alias(es)
5.3.2  Solution FA2: Configuration exchanges between the UE and the network to support functional alias(es)
5.3.3  Solution FA3: Parameters to support functional alias(es)Word-p. 26
5.3.4  Solution FA4: Architectural enhancements to support functional alias(es)
5.3.5  Solution FA5: Functional alias(es) management operationsUp
6  Overall evaluation
7  ConclusionsWord-p. 37
A  Gap Analyses for future featuresWord-p. 38
B  List of normative stage 1 requirementsWord-p. 42
C  Change historyWord-p. 46

Up   Top