Content for TR 23.790 Word version: 15.0.0
4 Gap Analyses
5 Solutions
6 Overall evaluation
7 Conclusions
A Gap Analyses for future features
B List of normative stage 1 requirements
$ Change History
4 Gap Analyses p. 8
4.1 Introduction p. 8
4.2 Multi-talker feature control p. 9
4.2.1 Description p. 9
4.2.2 Potential gaps p. 9
4.3 Functional alias(es) p. 9
4.3.1 Description p. 9
4.3.2 Potential gaps p. 10
4.4 Architecture enhancement(s) for railway communication p. 10
5 Solutions p. 12
5.1 Introduction p. 12
5.2 Multi-talker feature control p. 12
5.2.1 Solution MT1: Floor request and floor granted during an MCPTT session p. 12
5.2.1.1 Description p. 12
5.2.1.2 Architectural requirements p. 13
5.2.1.3 Solution evaluation p. 14
5.2.2 Solution MT2: Floor override using floor revoked during an MCPTT session p. 14
5.2.2.1 Description p. 14
5.2.2.2 Architectural requirements p. 15
5.2.2.3 Solution evaluation p. 15
5.2.3 Solution MT3: Change the maximum number of simultaneous talkers p. 15
5.2.3.1 Description p. 15
5.2.3.2 Architectural requirements p. 16
5.2.3.3 Solution evaluation p. 16
5.2.4 Solution MT4: Architectural enhancements to support multi-user talker control p. 16
5.2.4.1 Description p. 16
5.2.4.2 Architectural requirements p. 17
5.2.4.3 Solution evaluation p. 17
5.2.5 Solution MT5: Parameters to support multi-talker control p. 17
5.2.5.1 Description p. 17
5.2.5.2 Architectural requirements p. 18
5.2.5.3 Solution evaluation p. 18
5.3 Functional alias(es) p. 18
5.3.1 Solution FA1: Call processing to support functional alias(es) p. 18
5.3.1.1 Description p. 18
5.3.1.1.1 Functional alias ID used for pre-arranged group call setup p. 18
5.3.1.1.2 Functional alias ID used for chat group calls p. 19
5.3.1.2 Architectural requirements p. 21
5.3.1.3 Solution evaluation p. 21
5.3.2 Solution FA2: Configuration exchanges between the UE and the network to support functional alias(es) p. 21
5.3.2.1 Description p. 21
5.3.2.1.1 MC service user obtains a list of functional alias(es) from the network p. 21
5.3.2.1.2 Authorised MC service user retrieves active functional alias(es) for a certain MC service user from the network p. 22
5.3.2.1.3 MC service user receives updated functional alias(es) information from the network p. 22
5.3.2.1.4 MC service user activates functional alias(es) to the network p. 23
5.3.2.1.5 MC service user de-activates functional aliases to the network p. 24
5.3.2.2 Architectural requirements p. 25
5.3.2.3 Solution evaluation p. 25
5.3.3 Solution FA3: Parameters to support functional alias(es) p. 26
5.3.3.1 Description p. 26
5.3.3.2 Architectural requirements p. 26
5.3.3.3 Solution evaluation p. 27
5.3.4 Solution FA4: Architectural enhancements to support functional alias(es) p. 27
5.3.4.1 Description p. 27
5.3.4.2 Architectural requirements p. 28
5.3.4.3 Solution evaluation p. 29
5.3.5 Solution FA5: Functional alias(es) management operations p. 29
5.3.5.1 Description p. 29
5.3.5.1.1 Functional alias(es) activation p. 29
5.3.5.1.2 Functional alias(es) deactivation p. 30
5.3.5.1.3 Functional alias(es) taken over p. 30
5.3.5.1.4 Functional alias(es) subscribe to status notifications p. 31
5.3.5.1.5 Functional alias(es) unsubscribe from status notifications p. 32
5.3.5.2 Architectural requirements p. 32
5.3.5.3 Solution evaluation p. 33
6 Overall evaluation p. 33
6.1 General p. 33
6.2 Solution evaluation: Multi-talker feature control p. 33
6.3 Solution evaluation: Functional alias(es) p. 35
7 Conclusions p. 37
A Gap Analyses for future features p. 38
A.1 Introduction p. 38
A.2 Assured Voice Communication (AVC) p. 38
A.2.1 Description p. 38
A.2.2 Potential gaps p. 38
A.3 Multi-train voice communication between Drivers including Ground user(s) p. 38
A.3.1 Description p. 38
A.3.2 Potential gaps p. 39
A.4 Location management p. 39
A.4.1 Description p. 39
A.4.2 Potential gaps p. 39
A.5 FRMCS user communication handling p. 39
A.5.1 Description p. 39
A.5.2 Potential gaps p. 40
A.6 Interworking with GSM-R p. 40
A.6.1 Description p. 40
A.6.2 Potential gaps p. 40
A.7 Emergency communication p. 40
A.7.1 Description p. 40
A.7.2 Potential gaps p. 41
A.8 FRMCS system security framework p. 41
A.8.1 Description p. 41
A.8.2 Potential gaps p. 41
B List of normative stage 1 requirements p. 42
B.1 Overview p. 42
B.2 Functional alias(es) p. 42
B.2.1 Description p. 42
B.2.2 Requirements p. 42
B.3 Multi-talker control p. 44
$ Change History p. 46
