Tech-invite   3GPPspecs   RFCs   Search in Tech-invite

Gen21222324252627282931323334353637384‑5x
FsNEsRPsSBIsIDs Ti+
Top   in Index   Prev   Next

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

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V16.0.0 (Wzip)  2019/03  152 p.

Rapporteur:  Mr. Oettl, Martin

The present document captures architectural requirements to develop solutions for the Future Railway Mobile Communication System (FRMCS) to meet Rel-16 normative Stage 1 requirements.

short Table of Contents for  TR 23.796  Word version:   16.0.0

each title links to the equivalent title in the full ToC

 

Here   Top

 

1  ScopeWord-p. 11
2  ReferencesWord-p. 11
3  Definitions and abbreviationsWord-p. 12
4  ScenariosWord-p. 12
5  Key issuesWord-p. 13
6  Architectural requirementsWord-p. 29
7  SolutionsWord-p. 29
7.1  Solution 1 - Restricting incoming private communicationsWord-p. 29
7.2  Solution 2 - Implicit activation and deactivation of functional alias(es)Word-p. 32
7.3  Solution 3 - Client performs automatic group affiliation/de-affiliationWord-p. 35
7.4  Solution 4 - Support of functional aliases in private calls and private emergency callsWord-p. 37
7.5  Solution 5 - Support of functional aliases in emergency and imminent peril groups callsWord-p. 41
7.6  Solution 6 - Support of functional aliases in temporary voice group callsWord-p. 44
7.7  Solution 7 - Architecture to support GSM-R interworkingUpWord-p. 45
7.8  Solution 8 - Solution to support functional alias via broadcast group callsWord-p. 49
7.9  Solution 9 - Solution to support multiple functional alias use in private callsWord-p. 52
7.10  Solution 10 - Location information for a specific functional aliasWord-p. 54
7.12  Solution 12 - List of functional aliases used by affiliated group membersWord-p. 59
7.13  Solution 13 - List of MCPTT group members who did not acknowledge the group call requestWord-p. 60
7.14  Solution 14 - MC service server limits the number of simultaneous successful service authorisationsWord-p. 62
7.15  Solution 15 - Support functional aliases for SDSWord-p. 63
7.16  Solution 16 - Support functional aliases for File distribution (FD)UpWord-p. 67
7.17  Solution 17 - Support functional aliases within MCData control proceduresWord-p. 70
7.18  Solution 18 - Support of functional aliases for video emergency group callsWord-p. 73
7.19  Solution 19 - Support of functional aliases in private calls and private emergency callsWord-p. 77
7.20  Solution 20 - Support of functional aliases for video group callsWord-p. 80
7.21  Solution 21 - Support of functional aliases for private and emergency video callsWord-p. 84
7.22  Solution 22 - Support functional alias controlling for MCData servicesWord-p. 87
7.23  Solution 23 - Support functional alias controlling for MCVideo serviceUpWord-p. 88
7.24  Solution 24 - Additional commencement modes for MCPTT Group callsWord-p. 88
7.25  Solution 25 - Triggering an emergency group communication after an emergency alert automaticallyWord-p. 90
7.26  Solution 26 - User requests application layer prioritiesWord-p. 91
7.27  Solution 27 - MC gateway UEWord-p. 93
7.28  Solution 28 - IP connectivityWord-p. 97
7.29  Solution 29 - Call forwarding and call transfer for private callsWord-p. 104
7.30  Solution 30 - Arbitration of incoming communicationsWord-p. 118
7.31  Solution 31 - Client performs automatic activation and deactivation of functional aliases based on locationWord-p. 118
7.32  Solution 32 - Functional alias and alternative addressing scheme for interworking with LMR systemsWord-p. 120
7.33  Solution 33 - Communication priority for functional aliasesWord-p. 128
8  Overall evaluationWord-p. 129
9  ConclusionsWord-p. 133
A  List of normative stage 1 requirementsWord-p. 134
B  Voice communication in GSM-RWord-p. 149
C  Change historyWord-p. 152

Up   Top