Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  17.5.0

Top   Top   None   None   Next
1…   5…   7…   7.4…   7.5…   8…   9…   10…   10.1.2…   10.1.3…   10.1.5…   10.2…   10.2.3…   10.2.5…   10.3…   10.7…   10.7.3…   10.7.3.7…   10.7.3.10…   10.8…   10.8.4…   10.9…   10.9.3…   10.9.3.8…   10.10…   10.11…   10.12…   10.13…   10.13.3…   10.14…   10.15…   10.15.3…   A…   B…

 

1  Scope |R16|Word‑p. 15
This document specifies the common functional architecture, procedures and information flows needed to support mission critical services including the common services core architecture.
The corresponding service requirements are defined in TS 22.179, TS 22.280, TS 22.281 and TS 22.282.
The present document is applicable primarily to mission critical services using E-UTRAN access based on the EPC architecture defined in TS 23.401. 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.
Up

2  References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
[3]
TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1".
[4]
TS 22.281: "Mission Critical Video services".
[5]
TS 22.282: "Mission Critical Data services".
[6]
TS 23.002: "Network Architecture".
[7]
TS 23.179: "Functional architecture and information flows to support mission critical communication services; Stage 2"
[8]
TS 23.203: "Policy and charging control architecture".
[9]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[10]
TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".
[11]
TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".
[12]
TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2".
[13]
TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2".
[14]
TS 23.303: "Proximity-based services (ProSe); Stage 2".
[15]
TS 23.335: "User Data Convergence (UDC); Technical realization and information flows".
[16]
TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2".
[17]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[18]
TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[19]
TS 29.283: "Diameter Data Management Applications".
[0]
Void
[21]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[22]
RFC 5245  (April 2010): "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols".
[23]
GSMA PRD IR.92 v10.0: "IMS Profile for Voice and SMS".
[24]
GSMA PRD IR.88 v15.0: "LTE and EPC Roaming Guidelines".
[25]
TS 33.180: "Security of the mission critical service".
[26]
RFC 6733  (October 2012): "Diameter Base Protocol".
[27]
TS 29.214: "Policy and Charging Control over Rx reference point".
[28]
TS 22.011: "Service accessibility".
[29]
TS 23.271: "Functional stage 2 description of Location Services (LCS)".
[30]
TS 25.305: "Stage 2 functional specification of User Equipment (UE) positioning in UTRAN".
[31]
TS 23.032: "Universal Geographical Area Description (GAD)".
Up

3  Definitions, symbols and abbreviationsWord‑p. 16

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Accuracy:
Reflects the uncertainty of the location at the moment of location measurement, e.g. see TS 25.305 and TS 23.032.
Active MC service user profile:
The MC service user profile that is currently used by an MC service client of an MC service user while receiving MC service.
Altitude:
Third dimension for the geographical coordinates at the moment of location measurement, e.g. see TS 25.305 and TS 23.032.
Bearing:
Direction at the moment of location measurement, e.g. see TS 25.305.
ECGI:
E-UTRAN Cell Global Identifier, which is used to identify cells globally, where the ECGI is constructed from the Mobile Country Code (MCC), Mobile Network Code (MNC) and the E-UTRAN Cell Identifier (ECI).
Interconnection:
A means of communication between MC systems whereby MC service users obtaining MC service from one MC system can communicate with MC service users who are obtaining MC service from one or more other MC systems.
Interconnection group:
An MC service group that is configured to allow inclusion of MC service group members who are MC service users from partner MC system(s).
LCS network:
The 3GPP network that provides location service as defined in TS 23.271.
Location:
The current physical location of the MC service UE.
MBMS SAI:
Multimedia Broadcast Multicast Service Area Identity which is mapped to the MBMS service area.
MC gateway server:
A server providing topology hiding for MC service interconnection with a partner MC system, where that partner MC system is in a different trust domain.
MC service:
A generic name for any one of the three mission critical services: either MCPTT, or MCVideo, or MCData.
MC service affiliated group member:
An MC service user who has indicated an interest in a particular MC service group and has been accepted to participate in MC service group communication for that MC service group.
MC service client:
A generic name for the client application function of a specific MC service. MC service client could be replaced by MCPTT client, or MCVideo client, or MCData client depending on the context.
MC service group:
A defined set of MC service users with associated communication dispositions (e.g. media restrictions, default priority and commencement directions) configured for the use with one or more MC services.
MC service group affiliation:
A mechanism by which an MC service user's MC service(s) communication interest in one or more MC service groups is determined.
MC service group call:
A mechanism by which an MC service user can make a one-to-many MC service(s) transmission to other users that are members of MC service group(s).
MC service group de-affiliation:
A mechanism by which an MC service user's MC service(s) communication interest in one or more MC service groups is removed.
MC service group home system:
The MC system where the MC service group is defined.
MC service group host MC service server:
The MC service server within an MC system which provides centralised support for a particular MC service of an MC service group defined in a MC service group home system.
MC service group member:
An MC service user, whose MC service ID is listed in a particular MC service group.
MC service ID:
A generic name for the user ID of a mission critical user within a specific MC service. MC service ID could be replaced by MCPTT ID, or MCVideo ID, or MCData ID depending on the context.
MC service server:
A generic name for the server application function of a specific MC service. MC service server could be replaced by MCPTT server, MCVideo server, or MCData server depending on the context.
MC service user:
An authorized user, who can use an MC service UE to participate in one or more MC services.
MC service user profile:
The set of information associated to an MC service user that allows that user to employ one or more MC services in a given role and from a given MC service UE.
MC service UE:
A UE that can be used to participate in one or more MC services.
MC system:
The collection of applications, services, and enabling capabilities required to provide a single mission critical service or multiple mission critical services to one or more mission critical organizations.
MC user:
A user, identified by an MC ID, who, after authorization, obtains mission critical service(s).
Migration:
A means for an MC Service user to obtain MC service directly from a partner MC system.
Partner MC system:
Allied MC system that provides MC services to an MC service user based on the MC service user profiles that are defined in the primary MC system of that MC service user.
Preconfigured MC service group:
an MC service group used only for regrouping that has been configured in advance of a group or user regrouping operation to serve as the source of regroup group configuration.
Pre-selected MC service user profile:
The MC service user profile that is to be selected as the active MC service user profile through configuration, and applicable for an authenticated MC service user upon MC service authorization.
Primary MC system:
MC system where the MC service user profiles of an MC service user are defined.
Requested Priority:
A value for use in a MC service group or MC private communication that, if accepted, is used by the MCX service server to temporarily replace the priority level that is predefined in the MC service group or MC service user profile. This value is used in combination with other factors to determine the application priority for the requested communication.
Selected MC service user profile:
The MC service user profile that is to be selected as the active MC service user profile for an MC service upon request by an MC service user.
Serving MC service server:
The MC service server which is providing MC service to an MC service client.
Serving MC system:
The MC system which is providing MC service to an MC user.
Speed:
Movement at the moment of location measurement, e.g. see TS 25.305 and TS 23.032.
Time of measurement:
Date and time expressed with a certain precision to reflect the moment of the location measurement.
For the purposes of the present document, the following terms given in TS 22.280 apply
Mission Critical
Mission Critical Applications
Mission Critical Organization
Mission Critical Service
Functional alias
For the purposes of the present document, the following terms given in TS 22.179 apply
Multi-talker control
Up

3.2  SymbolsWord‑p. 18
For the purposes of the present document, the symbols given in TS 22.280 apply
Nc6

3.3  Abbreviations

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
APN
Access Point Name
BM‑SC
Broadcast Multicast Service Centre
CMS
Configuration Management Server
CSC
Common Services Core
CSCF
Call Server Control Function
DPF
Direct Provisioning Function
E-UTRAN
Evolved Universal Terrestrial Radio Access Network
EPC
Evolved Packet Core
EPS
Evolved Packet System
FEC
Forward Error Correction
GBR
Guaranteed Bit Rate
GCS AS
Group Communication Service Application Server
GCSE_LTE
Group Communication Service Enabler over LTE
GMS
Group Management Server
GRUU
Globally Routable User agent URI
HSS
Home Subscriber Server
HTTP
Hyper Text Transfer Protocol
I-CSCF
Interrogating CSCF
IARI
IMS Application Reference Identifier
ICE
Interactive Connectivity Establishment
ICSI
IMS Communication Service Identifier
IdMS
Identity Management Server
IM CN
IP Multimedia Core Network
IMPI
IP Multimedia Private Identity
IMPU
IP Multimedia PUblic identity
IMS
IP Multimedia Subsystem
KMS
Key Management Server
LCS
Location Services
LMC
Location Management Client
LMS
Location Management Server
MBMS
Multimedia Broadcast and Multicast Service
MBSFN
Multimedia Broadcast multicast service Single Frequency Network
MC
Mission Critical
MC ID
Mission Critical user identity
MCPTT AS
MCPTT Application Server
MCPTT ID
MCPTT user identity
NAT
Network Address Translation
P-CSCF
Proxy CSCF
PLMN
Public Land Mobile Network
ProSe
Proximity-based Services
PSI
Public Service Identity
QoS
Quality of Service
RAN
Radio Access Network
RF
Radio Frequency
ROHC
RObust Header Compression
S-CSCF
Serving CSCF
SIP
Session Initiated Protocol
SSL
Secure Sockets Layer
TLS
Transport Layer Security
TMGI
Temporary Mobile Group Identity
UDC
User Data Convergence
UDR
User Data Repository
USB
Universal Serial Bus
URI
Uniform Resource Identifier
WLAN
Wireless Local Area Network
For the purposes of the present document, the abbreviations given in TS 22.280 apply
MCData
MCPTT
MCVideo
Up

4  IntroductionWord‑p. 20
A common functional architecture to support MC services (i.e., MCPTT defined in TS 23.379, MCVideo defined in TS 23.281, MCData defined in TS 23.282) including common application plane and signalling plane entities is specified in this document.
Each MC service supports several types of communications amongst the users (e.g. group call, private call). There are several common functions and entities (e.g. group, configuration, identity) which are used by the MC services.
The common functional architecture to support MC services utilises aspects of the IMS architecture defined in TS 23.228, the Proximity-based Services (ProSe) architecture defined in TS 23.303, the Group Communication System Enablers for LTE (GCSE_LTE) architecture defined in TS 23.468 and the PS-PS access transfer procedures defined in TS 23.237.
The MC service UE primarily obtains access to a MC service via E-UTRAN, using the EPS architecture defined in TS 23.401. Certain MC service functions such as dispatch and administrative functions can be supported using either MC service UEs in E-UTRAN or using MC service UEs via non-3GPP access networks. External applications usage of MC services can be enabled via E-UTRAN or non-3GPP access networks.
Up

Up   Top   ToC