Tech-invite3GPP-SpecsReleasesFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TR 23.778SA6
Study on Mission Critical Services
Access aspects

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

Rapporteur:  Mr. Trank, Magnus

This technical report is a study of mission critical service access aspects. The present document identifies architecture enhancements needed to support mission critical services delivered over IOPS or with gateway UEs, based on the stage 1 requirements.

full Table of Contents for  TR 23.778  Word version:   16.0.0

this ToC is filtered in order to show the essential title levels only
Here   Top
1  ScopeWord-p. 6
2  ReferencesWord-p. 6
3  Definitions, symbols and abbreviationsWord-p. 7
4  Key issuesWord-p. 7
4.1  IOPS related key issuesWord-p. 7
4.1.1  Key issue 2-1 MC system configuration data synchronizationWord-p. 7
4.1.2  Key issue 2-2 MC service client configuration for IOPSWord-p. 8
4.1.3  Key issue 2-3 on how to handle an MC UE switching to/from an IOPS MC systemWord-p. 8
4.1.4  Key issue 2-4 IOPS architectureWord-p. 8
4.1.5  Key issue 2-5 on ongoing communication continuity when backhaul is recoveredWord-p. 9
4.1.6  Key issue 2-6 on support MBMS in IOPSWord-p. 9
4.1.7  Key issue 2-7 on determining a list of MC users connected to the IOPS MC systemWord-p. 10
5  Architectural requirementsWord-p. 10
5.1  IOPS related requirementsWord-p. 10
6  SolutionsWord-p. 11
6.1  Solution 1: UE and user data synchronizationWord-p. 11
6.2  Solution 2: Functional model for IOPS based on a switchable standalone MC systemWord-p. 13
6.3  Solution 3: Functional model for IOPS based on an always-on partner MC systemWord-p. 14
6.4  Solution 4: Functional model for IOPS MC system based on only IP connectivityWord-p. 15
6.5  Solution 5: Functional model for IOPS based on an always-on participating serverWord-p. 23
6.6  Solution 6: Procedure for switching from the primary MC system to an IOPS MC systemWord-p. 25
6.7  Solution 7: IOPS notification to MC UEsWord-p. 27
6.8  Solution 8: MC service client configuration for IOPSWord-p. 29
6.9  Solution 9: Functionality for determining the MC user registration status in IOPSWord-p. 29
7  Overall evaluationWord-p. 33
7.1  GeneralUpWord-p. 33
7.2  Architecture evaluationWord-p. 33
7.3  Key issue and solution evaluationWord-p. 34
8  ConclusionsWord-p. 35
A  Change historyWord-p. 36

Up   Top