Content for TR 23.782 Word version: 15.0.0
4 Interworking scenarios
5 Key issues
6 Solutions
7 Overall evaluation
8 Conclusions
$ Change History
4 Interworking scenarios p. 12
4.1 MC service scenarios p. 12
4.1.1 General p. 12
4.1.2 Scenario 1: Private communication p. 12
4.1.2.1 General p. 12
4.1.2.2 MC service UE A initiates private communication to LMR MS B p. 12
4.1.2.3 LMR MS B initiates a private communication to MC service UE A p. 13
4.1.3 Scenario 2: Group communication p. 13
4.2 MCPTT scenarios p. 16
4.3 MCData scenarios p. 16
4.3.1 General p. 16
4.3.2 Scenario 4: Private standalone MCData SDS communication p. 16
4.3.2.1 General p. 16
4.3.2.2 MCData UE initiates private standalone SDS communication to an LMR MS p. 16
4.3.2.3 LMR MS initiates a private standalone SDS communication to a MCData UE p. 16
4.3.3 Scenario 5: Group standalone MCData SDS communication p. 17
5 Key issues p. 18
5.1 Identity p. 18
5.1.1 Key issue #1-1: Mapping of MCPTT, MCData and TETRA/P25 user identities p. 18
5.1.1.1 Description p. 18
5.1.2 Key issue #1-2: Mapping of MCPTT, MCData and TETRA/P25 group identities p. 19
5.1.2.1 Description p. 19
5.2 Homing and affiliation p. 19
5.2.1 Key issue #2-1: Group affiliation management p. 19
5.2.1.1 Description p. 19
5.2.2 Key issue #2-2: Group controlling system p. 20
5.2.2.1 Description p. 20
5.2.3 Key issue #2-3: Late entry to group call p. 20
5.2.3.1 Description p. 20
5.3 Session setup and termination p. 20
5.3.1 Key issue #3-1: Private call p. 20
5.3.1.1 Description p. 20
5.3.2 Key issue #3-2: Call back p. 21
5.3.2.1 Description p. 21
5.3.3 Key issue #3-3: Group call p. 21
5.3.3.1 Description p. 21
5.4 Media plane p. 22
5.4.1 Key issue #4-1: Vocoder reconciliation p. 22
5.4.1.1 Description p. 22
5.4.2 Key issue #4-2: Unstoppable audio p. 23
5.4.2.1 Description p. 23
5.5 Encryption p. 24
5.5.1 Key issue #5-1: End-to-end payload encryption p. 24
5.5.1.1 Description p. 24
5.5.2 Key issue #5-2: Key agreement p. 24
5.5.2.1 Description p. 24
5.5.3 Key issue #5-3: Unencrypted transmissions within an encrypted call p. 25
5.5.3.1 Description p. 25
5.5.4 Key issue #5-4: Key management p. 25
5.5.4.1 Description p. 25
5.6 Group management p. 27
5.6.1 Key issue #6-1: Regrouping p. 27
5.6.1.1 Description p. 27
5.6.2 Key issue #6-2: Group linking p. 27
5.6.2.1 Description p. 27
5.6.3 Key issue #6-3: Separate regrouping within each system p. 28
5.7 Prioritisation and pre-emption p. 28
5.7.1 Key issue #7-1: Emergency calls p. 28
5.7.1.1 Description p. 28
5.7.2 Key issue #7-2: Emergency alerts p. 29
5.7.2.1 Description p. 29
5.8 Floor control p. 30
5.8.1 Key Issue #8-1: Simultaneous floor request p. 30
5.8.1.1 Description p. 30
5.8.2 Key Issue #8-2: User's floor is revoked by another user in another system p. 31
5.8.2.1 Description p. 31
5.8.3 Key issue #8-3: Floor Request timing p. 32
5.8.3.1 Description p. 32
5.9 MCData SDS p. 32
6 Solutions p. 33
6.1 General solutions p. 33
6.1.1 Solution #0-1: General interworking architecture solution between MCPTT and LMR Systems. p. 33
6.1.1.1 General p. 33
6.1.1.2 Impacts on existing nodes and functionality p. 33
6.1.1.3 Solution evaluation p. 34
6.1.2 Solution #0-2: General interworking architecture between MCData and LMR systems p. 34
6.2 Identity p. 35
6.3 Homing and affiliation p. 35
6.3.1 Solution #2-1: Group affiliation p. 35
6.3.1.1 Description p. 35
6.3.1.1.1 Affiliation cases p. 35
6.3.1.1.2 Group affiliation to group defined in MCPTT system p. 35
6.3.1.1.3 Group de-affiliation to group defined in MCPTT system p. 37
6.3.1.2 Impacts on existing nodes and functionality p. 37
6.3.1.3 Solution evaluation p. 38
6.3.2 Solution #2-2: Group controlling system p. 38
6.4 Session setup and termination p. 39
6.4.1 Solution #3-1: Private call with parameter negotiation solution p. 39
6.4.1.1 Description p. 39
6.4.1.1.1 General p. 39
6.4.1.1.1.1 Gap 1 - Multiple MCPTT client instances p. 39
6.4.1.1.1.2 Gap 2 - Commencement mode compatibility p. 39
6.4.1.1.1.3 Gap 3 - Full duplex calls p. 39
6.4.1.1.2 Private call setup in automatic commencement mode - users in multiple systems p. 40
6.4.1.1.3 Private call setup in manual commencement mode - users in multiple systems p. 41
6.4.1.2 Impacts on existing nodes and functionality p. 42
6.4.1.3 Solution Evaluation p. 42
6.4.2 Solution #3-2: Private call initiated by LMR user to MCPTT user p. 43
6.4.2.1 Description p. 43
6.4.2.2 Impacts on existing nodes and functionality p. 44
6.4.2.3 Solution evaluation p. 44
6.4.3 Solution #3-3: Group call on a temporary group p. 44
6.4.3.1 General p. 44
6.4.3.2 Description p. 44
6.4.3.2.1 Group call initiated by MCPTT user over interworking temporary group defined in MCPTT system p. 44
6.4.3.2.2 Group call initiated by LMR user over temporary interworking group defined in MCPTT system. p. 46
6.4.3.3 Impacts on existing nodes and functionality p. 47
6.4.3.4 Solution evaluation p. 47
6.4.4 Solution #3-4: Group call on an interworking group p. 47
6.4.4.1 General p. 47
6.4.4.2 Description p. 47
6.4.4.2.1 Group call initiated by MCPTT user over interworking group defined in MCPTT system p. 47
6.4.4.2.2 Group call initiated by MCPTT user over interworking group defined in LMR system p. 49
6.4.4.2.3 Group call initiated by LMR user over interworking group defined in MCPTT system. p. 51
6.4.4.2.4 Group call initiated by LMR user over interworking group defined in LMR system. p. 53
6.4.4.3 Impacts on existing nodes and functionality p. 54
6.4.4.4 Solution evaluation p. 54
6.4.5 Solution #3-5: Late entry in interworking group call p. 54
6.4.5.1 Description p. 54
6.4.5.1.1 Late entry overview p. 54
6.4.5.1.2 Late entry following affiliation, MCPTT controlling system p. 54
6.4.5.1.3 Late entry following affiliation, LMR controlling system p. 55
6.4.5.2 Impacts on existing nodes and functionality p. 56
6.4.5.3 Solution evaluation p. 57
6.4.6 Solution #3-6: Group call over linked group p. 57
6.5 Media plane p. 58
6.5.1 Solution #4-1: Codec reconciliation p. 58
6.5.1.1 Description p. 58
6.5.1.2 Impacts on existing nodes and functionality p. 59
6.5.1.3 Solution evaluation p. 59
6.5.2 Solution #4-2: Codec configuration p. 59
6.5.2.1 Description p. 59
6.5.2.2 Impacts on existing nodes and functionality p. 59
6.5.2.3 Solution evaluation p. 59
6.5.3 Solution #4-3: Codec negotiation by LMR system p. 60
6.5.3.1 Description p. 60
6.5.3.2 Impacts on existing nodes and functionality p. 61
6.5.3.3 Solution evaluation p. 61
6.5.4 Solution #4-4: Floor override with unstoppable audio p. 61
6.6 Encryption p. 63
6.6.1 Solution #5-1: Means for supporting TETRA and P25 end-to-end encrypted speech p. 63
6.6.1.1 Description p. 63
6.6.1.1.1 General p. 63
6.6.1.1.2 Gap 1 - means for transmitting the P25 or TETRA encryption synchronization vector, including the Key ID and the Algorithm ID within the MCPTT system p. 63
6.6.1.1.3 Gap 2 - Means for ensuring the time synchronization between the sync vector and the stream of encrypted speech packets in a P25 or TETRA to MCPTT interworked system. p. 63
6.6.1.1.4 Gap 3 - support for the TETRA vocoder in MCPTT to allow end-to-end security p. 63
6.6.1.1.5 Gap 4 - Support for the P25 vocoders in MCPTT to allow end-to-end security. p. 64
6.6.1.2 Impacts on existing nodes and functionality p. 64
6.6.1.3 Solution Evaluation p. 64
6.7 Group management p. 64
6.7.1 Solution #6-1: Group regroup p. 64
6.7.1.1 Description p. 64
6.7.1.1.1 General p. 64
6.7.1.1.2 Gap 1 - interworking LMR group regrouping with MC service p. 64
6.7.1.1.2.1 MC service initiates the group regroup p. 64
6.7.1.1.2.2 IWF initiates the group regroup p. 66
6.7.1.1.3 Gap 2 - ownership of the group regroup p. 67
6.7.1.1.4 Gap 3 - simultaneous group regroup requests from each side of the IWF-1 interface p. 67
6.7.1.1.5 Gap 4 - Group regroup with MC service clients and LMR clients p. 68
6.7.1.1.5.1 General p. 68
6.7.1.1.5.2 Announcement group part of group regroup p. 68
6.7.1.1.5.3 Emergency on constituent group p. 68
6.7.1.1.5.4 Activity on constituent group p. 68
6.7.1.1.6 Gap 5 - Resolution of vocoder and encryption mode for the group regroup p. 69
6.7.1.2 Impacts on existing nodes and functionality p. 69
6.7.1.3 Solution Evaluation p. 69
6.7.2 Solution #6-2: Group regroup between MCPTT and LMR system in MCPTT system p. 69
6.7.2.1 Description p. 69
6.7.2.2 Impacts on existing nodes and functionality p. 71
6.7.2.3 Solution evaluation p. 71
6.7.3 Solution #6-3: Group creation between MCPTT and LMR system p. 71
6.7.3.1 Description p. 71
6.7.3.2 Impacts on existing nodes and functionality p. 73
6.7.3.3 Solution evaluation p. 73
6.7.4 Solution #6-4: Local group regrouping within each system p. 73
6.8 Prioritization and pre-emption p. 73
6.8.1 Solution #7-1: Emergency calls p. 73
6.8.1.1 General p. 73
6.8.1.2 Description p. 74
6.8.1.2.1 Emergency call procedure p. 74
6.8.1.2.2 Emergency cancel p. 75
6.8.1.2.3 Imminent peril calls p. 75
6.8.1.2.4 Losing audio p. 76
6.8.1.2.5 Default emergency group p. 76
6.8.1.2.6 Emergency private call p. 76
6.8.1.2.7 LMR systems that do not track group emergencies p. 76
6.8.1.3 Impacts on existing nodes and functionality p. 76
6.8.1.4 Solution evaluation p. 76
6.8.2 Solution #7-2: Emergency alerts p. 76
6.9 Floor control p. 78
6.9.1 Solution #8-1: Time-stamping of floor requests during transmission p. 78
6.9.1.1 Description p. 78
6.9.1.1.1 General p. 78
6.9.1.1.2 Behaviour at the MC service client p. 78
6.9.1.1.3 Behaviour at the IWF p. 78
6.9.1.1.4 Behaviour at the floor control server p. 78
6.9.1.1.5 Floor request and floor grant procedure with time-stamping p. 79
6.9.1.2 Impacts on existing nodes and functionality p. 81
6.9.1.3 Solution evaluation p. 81
6.9.2 Solution #8-2: Group controlling system p. 81
6.9.2.1 Description p. 81
6.9.2.1.1 Floor request arbitration in the MCPTT system as the control system p. 81
6.9.2.1.2 Floor request arbitration in the LMR system as the control system p. 82
6.9.2.1.3 Floor revocation in the MCPTT system as the control system p. 83
6.9.2.1.4 Floor revocation in the LMR system as the control system p. 84
6.9.2.2 Impacts on existing nodes and functionality p. 85
6.9.2.3 Solution evaluation p. 85
6.10 MCData SDS p. 86
6.10.1 Solution #9-1: Procedure for standalone MCData SDS interworking p. 86
6.10.1.1 Description p. 86
6.10.1.1.1 General p. 86
6.10.1.1.2 Behaviour at the MCData Client p. 86
6.10.1.1.3 Behaviour at the IWF p. 86
6.10.1.1.4 Behaviour at the MCData Server p. 86
6.10.1.1.5 MCData user to LMR user SDS request p. 86
6.10.1.1.6 LMR user to MCData user SDS request p. 87
6.10.1.2 Impacts on existing nodes and functionality p. 89
6.10.1.3 Solution evaluation p. 89
6.10.2 Solution #9-2: Payload size handling for standalone MCData SDS interworking p. 89
7 Overall evaluation p. 90
8 Conclusions p. 97
8.1 General p. 97
8.2 Conclusions on key issues p. 97
8.2.1 Solution with no key issue p. 97
8.2.2 Key issue #1-1: Mapping of MCPTT, MCData and TETRA/P25 user identities p. 98
8.2.3 Key issue #1-2: Mapping of MCPTT and TETRA/P25 group identities p. 98
8.2.4 Key issue #2-1: Group affiliation p. 98
8.2.5 Key issue #2-2: Group controlling system p. 98
8.2.6 Key issue #2-3: Late entry to group call p. 98
8.2.7 Key issue #3-1: Private call p. 98
8.2.8 Key issue #3-2: Call Back p. 98
8.2.9 Key issue #3-3: Group call p. 98
8.2.10 Key issue #4-1: Vocoder reconciliation p. 98
8.2.11 Key issue #4-2: Unstoppable audio p. 99
8.2.12 Key issue #5-1: End to end payload encryption p. 99
8.2.13 Key issue #5-2: Key agreement p. 99
8.2.14 Key issue #5-3: Unencrypted transmissions within an encrypted call p. 99
8.2.15 Key issue #5-4: Key management p. 99
8.2.16 Key issue #6-1: Regrouping p. 99
8.2.17 Key issue #6-2: Group Linking p. 100
8.2.18 Key issue #6-3: Separate regrouping within each system p. 100
8.2.19 Key issue #7-1: Emergency calls p. 100
8.2.20 Key issue #7-2: Emergency alerts p. 100
8.2.21 Key issue#8-1: Simultaneous floor request p. 100
8.2.22 Key issue #8-2: User's floor is revoked by another user in another system p. 100
8.2.23 Key issue #8-3: Floor Request timing p. 100
8.2.24 Key issue #9-1: Procedure for standalone MCData SDS interworking p. 100
8.2.25 Key issue #9-2: Payload size handling p. 100
$ Change History p. 101
