Tech-invite3GPP-SpecsReleasesFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TS 23.280SA6
Common functional architecture
to support Mission Critical services

use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
V17.1.0 (Wzip)2019/12  251 p.
V16.5.0 (Wzip)2019/12  227 p.
V15.7.0 (PDF)  2019/06  207 p.
V14.6.0  2018/06  146 p.

3GPP 23.280 - Functional model for application plane for an MC system
Here are some links in support of this figure:
Clause 7.5CSC‑1

Rapporteur:  Mr. Amogh, Niranth

This document specifies the common functional architecture, procedures and information flows needed to support mission critical services including the common services core architecture.
The present document is applicable primarily to mission critical services using E-UTRAN access based on the EPC architecture. Certain MC service functions such as dispatch and administrative functions could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access.
The common functional architecture to support mission critical services can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.

short Table of Contents for  TS 23.280  Word version:   17.1.0

each title links to the equivalent title in the full ToC
Here   Top
1  Scope [R16]Word-p. 14
2  ReferencesWord-p. 14
3  Definitions, symbols and abbreviationsWord-p. 15
4  IntroductionWord-p. 18
5  Assumptions and architectural requirementsWord-p. 19
6  Involved business relationshipsWord-p. 26
7  Functional modelWord-p. 29
7.1  GeneralWord-p. 29
7.2  Description of the planesWord-p. 29
7.3  Functional model descriptionWord-p. 29
7.4  Functional entities descriptionWord-p. 33
7.5  Reference pointsWord-p. 40
8  IdentitiesWord-p. 46
8.1  Application planeWord-p. 46
8.2  SIP signalling control planeWord-p. 48
8.3  Relationship between identities in different planesWord-p. 49
9  Application of functional model to deploymentsWord-p. 50
9.1  GeneralUpWord-p. 50
9.2  Architecture model and deployment scenarios for on-network operationsWord-p. 50
9.3  Architecture model for off-network operationsWord-p. 60
9.4  Architecture model for roamingUpWord-p. 61
10  Procedures and information flowsWord-p. 61
10.1  MC service configurationWord-p. 61
10.2  Group management (on-network)Word-p. 91
10.3  Pre-established session (on-network)Word-p. 115
10.4  Simultaneous session (on-network)Word-p. 119
10.5  Use of UE-to-network relayWord-p. 119
10.6  General user authentication and authorization for MC servicesWord-p. 119
10.7  Use of MBMS transmissionWord-p. 123
10.8  Affiliation and de-affiliation to/from MC service group(s)Word-p. 153
10.9  Location management (on-network)Word-p. 171
10.10  Emergency AlertWord-p. 182
10.11  MC service resource management (on-network) [R15]Word-p. 190
10.12  Priority Management [R15]Word-p. 196
10.13  Functional alias management (on-network) [R15]Word-p. 198
10.14  Generic procedures for interconnection [R15]Word-p. 213
10.15  Preconfigured regrouping [R17]Word-p. 218
A (Normative)  Configuration data for MC servicesWord-p. 236
B  Service continuity for MC serviceWord-p. 243
C  Application Priority [R17]Word-p. 246
D  Change historyWord-p. 248

Up   Top