Tech-invite   3GPPspecs   RFCs   SIP   Search in Tech-invite

Top   in Index   Prev   Next

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

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

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

this ToC is filtered in order to show the essential title levels only


Here   Top


1  ScopeWord-p. 7
2  ReferencesWord-p. 7
3  Definitions and abbreviationsWord-p. 8
4  Gap AnalysesWord-p. 8
4.1  IntroductionWord-p. 8
4.2  Multi-talker feature controlWord-p. 9
4.3  Functional alias(es)UpWord-p. 9
4.4  Architecture enhancement(s) for railway communicationWord-p. 10
4.4.1  IntroductionWord-p. 10
4.4.2  Multi-talker controlWord-p. 10
4.4.3  Functional Alias(es)Word-p. 11
5  SolutionsWord-p. 12
5.1  IntroductionWord-p. 12
5.2  Multi-talker feature controlWord-p. 12
5.2.1  Solution MT1: Floor request and floor granted during an MCPTT sessionWord-p. 12
5.2.2  Solution MT2: Floor override using floor revoked during an MCPTT sessionUpWord-p. 14
5.2.3  Solution MT3: Change the maximum number of simultaneous talkersWord-p. 15
5.2.4  Solution MT4: Architectural enhancements to support multi-user talker controlWord-p. 16
5.2.5  Solution MT5: Parameters to support multi-talker controlWord-p. 17
5.3  Functional alias(es)Word-p. 18
5.3.1  Solution FA1: Call processing to support functional alias(es)Word-p. 18
5.3.2  Solution FA2: Configuration exchanges between the UE and the network to support functional alias(es)Word-p. 21
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)Word-p. 27
5.3.5  Solution FA5: Functional alias(es) management operationsUpWord-p. 29
6  Overall evaluationWord-p. 33
6.1  GeneralUpWord-p. 33
6.2  Solution evaluation: Multi-talker feature controlWord-p. 33
6.3  Solution evaluation: Functional alias(es)Word-p. 35
7  ConclusionsWord-p. 37
A  Gap Analyses for future featuresWord-p. 38
A.1  IntroductionWord-p. 38
A.2  Assured Voice Communication (AVC)Word-p. 38
A.3  Multi-train voice communication between Drivers including Ground user(s)Word-p. 38
A.4  Location managementWord-p. 39
A.5  FRMCS user communication handlingWord-p. 39
A.6  Interworking with GSM-RWord-p. 40
A.7  Emergency communicationWord-p. 40
A.8  FRMCS system security frameworkWord-p. 41
B  List of normative stage 1 requirementsWord-p. 42
B.1  OverviewWord-p. 42
B.2  Functional alias(es)Word-p. 42
B.3  Multi-talker controlWord-p. 44
C  Change historyWord-p. 46

Up   Top