Tech-invite   3GPPspecs   RFCs   Search in Tech-invite

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

TR 23.782 (SA6)
Study on Mission Critical Communication Interworking
between LTE and non‑LTE Systems

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

Rapporteur:  Mr. Monnes, Peter

The objective of this technical report is to study and identify solutions suitable for interworking between LTE mission critical systems and non-LTE mission critical systems that satisfy the MCPTT requirements in TS 22.179 and the MCData requirements in 22.282 (SDS only).
The present document refers to an IWF entity as an editorial convenience. The structure and functionality of the IWF is out of scope of the present document. The definition of IWF-1 and interactions with IWF-1 by the MCPTT system and the definition of IWF-2 and interactions with IWF-2 by the MCData (SDS only) are in scope of the present document.

full Table of Contents for  TR 23.782  Word version:   15.0.0

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

 

Here   Top

 

1  ScopeWord-p. 10
2  ReferencesWord-p. 10
3  Definitions and abbreviationsWord-p. 11
4  Interworking scenariosWord-p. 12
4.1  MC service scenariosWord-p. 12
4.1.1  GeneralWord-p. 12
4.1.2  Scenario 1: Private communicationWord-p. 12
4.1.3  Scenario 2: Group communicationWord-p. 13
4.2  MCPTT scenariosWord-p. 16
4.2.1  Scenario 3: Floor control between MCPTT and legacy systemsWord-p. 16
4.3  MCData scenariosWord-p. 16
4.3.1  GeneralUpWord-p. 16
4.3.2  Scenario 4: Private standalone MCData SDS communicationWord-p. 16
4.3.3  Scenario 5: Group standalone MCData SDS communicationWord-p. 17
5  Key issuesWord-p. 18
5.1  IdentityWord-p. 18
5.1.1  Key issue #1-1: Mapping of MCPTT, MCData and TETRA/P25 user identitiesUpWord-p. 18
5.1.2  Key issue #1-2: Mapping of MCPTT, MCData and TETRA/P25 group identitiesWord-p. 19
5.2  Homing and affiliationWord-p. 19
5.2.1  Key issue #2-1: Group affiliation managementWord-p. 19
5.2.2  Key issue #2-2: Group controlling systemWord-p. 20
5.2.3  Key issue #2-3: Late entry to group callWord-p. 20
5.3  Session setup and terminationWord-p. 20
5.3.1  Key issue #3-1: Private callWord-p. 20
5.3.2  Key issue #3-2: Call backWord-p. 21
5.3.3  Key issue #3-3: Group callWord-p. 21
5.4  Media planeWord-p. 22
5.4.1  Key issue #4-1: Vocoder reconciliationWord-p. 22
5.4.2  Key issue #4-2: Unstoppable audioWord-p. 23
5.5  EncryptionWord-p. 24
5.5.1  Key issue #5-1: End-to-end payload encryptionWord-p. 24
5.5.2  Key issue #5-2: Key agreementWord-p. 24
5.5.3  Key issue #5-3: Unencrypted transmissions within an encrypted callWord-p. 25
5.5.4  Key issue #5-4: Key managementUpWord-p. 25
5.6  Group managementWord-p. 27
5.6.1  Key issue #6-1: RegroupingWord-p. 27
5.6.2  Key issue #6-2: Group linkingWord-p. 27
5.6.3  Key issue #6-3: Separate regrouping within each systemWord-p. 28
5.7  Prioritisation and pre-emptionWord-p. 28
5.7.1  Key issue #7-1: Emergency callsWord-p. 28
5.7.2  Key issue #7-2: Emergency alertsWord-p. 29
5.8  Floor controlWord-p. 30
5.8.1  Key Issue #8-1: Simultaneous floor requestWord-p. 30
5.8.2  Key Issue #8-2: User's floor is revoked by another user in another systemWord-p. 31
5.8.3  Key issue #8-3: Floor Request timingWord-p. 32
5.9  MCData SDSWord-p. 32
5.9.1  Key Issue #9-1: Payload size handlingWord-p. 32
5.9.2  Key Issue #9-2: Payload conversionWord-p. 32
6  SolutionsWord-p. 33
6.1  General solutionsWord-p. 33
6.1.1  Solution #0-1: General interworking architecture solution between MCPTT and LMR Systems.Word-p. 33
6.1.2  Solution #0-2: General interworking architecture between MCData and LMR systemsWord-p. 34
6.2  IdentityWord-p. 35
6.2.1  Solution #1-1: Identity mappingWord-p. 35
6.3  Homing and affiliationWord-p. 35
6.3.1  Solution #2-1: Group affiliationWord-p. 35
6.3.2  Solution #2-2: Group controlling systemWord-p. 38
6.4  Session setup and terminationWord-p. 39
6.4.1  Solution #3-1: Private call with parameter negotiation solutionWord-p. 39
6.4.2  Solution #3-2: Private call initiated by LMR user to MCPTT userWord-p. 43
6.4.3  Solution #3-3: Group call on a temporary groupWord-p. 44
6.4.4  Solution #3-4: Group call on an interworking groupWord-p. 47
6.4.5  Solution #3-5: Late entry in interworking group callWord-p. 54
6.4.6  Solution #3-6: Group call over linked groupWord-p. 57
6.5  Media planeWord-p. 58
6.5.1  Solution #4-1: Codec reconciliationUpWord-p. 58
6.5.2  Solution #4-2: Codec configurationWord-p. 59
6.5.3  Solution #4-3: Codec negotiation by LMR systemWord-p. 60
6.5.4  Solution #4-4: Floor override with unstoppable audioWord-p. 61
6.6  EncryptionWord-p. 63
6.6.1  Solution #5-1: Means for supporting TETRA and P25 end-to-end encrypted speechWord-p. 63
6.7  Group managementWord-p. 64
6.7.1  Solution #6-1: Group regroupWord-p. 64
6.7.2  Solution #6-2: Group regroup between MCPTT and LMR system in MCPTT systemWord-p. 69
6.7.3  Solution #6-3: Group creation between MCPTT and LMR systemWord-p. 71
6.7.4  Solution #6-4: Local group regrouping within each systemWord-p. 73
6.8  Prioritization and pre-emptionWord-p. 73
6.8.1  Solution #7-1: Emergency callsWord-p. 73
6.8.2  Solution #7-2: Emergency alertsWord-p. 76
6.9  Floor controlWord-p. 78
6.9.1  Solution #8-1: Time-stamping of floor requests during transmissionWord-p. 78
6.9.2  Solution #8-2: Group controlling systemWord-p. 81
6.10  MCData SDSWord-p. 86
6.10.1  Solution #9-1: Procedure for standalone MCData SDS interworkingWord-p. 86
6.10.2  Solution #9-2: Payload size handling for standalone MCData SDS interworkingWord-p. 89
7  Overall evaluationUpWord-p. 90
8  ConclusionsWord-p. 97
A  Change historyWord-p. 101

Up   Top