Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.282  Word version:  19.1.0

Top   Top   None   None   Next
1…   5…   6…   6.6…   7…   7.4…   7.4.2.1.10…   7.4.2.2…   7.4.2.5…   7.4.2.8…   7.4.3…   7.5…   7.5.2.1.12…   7.5.2.2…   7.5.2.4…   7.5.2.6…   7.5.2.8…   7.5.2.11…   7.5.2.14…   7.5.3…   7.6   7.7…   7.7.2.1.13…   7.7.2.2…   7.8…   7.9…   7.13…   7.13.3.1.19…   7.13.3.2…   7.13.3.8…   7.13.3.16…   7.13.4…   7.14…   7.14.2.2…   7.17…   7.17.2.13…   7.17.3…   7.17.3.1.4…   7.17.3.2…   7.17.3.2.4…   7.17.3.2.6…   7.17.4…   7.17.6…   A…   B… 
1 Scope  2 References  3 Definitions, symbols and abbreviations  3.1 Definitions  3.2 Abbreviations  4 Introduction 
...

 

1  Scope  p. 16

This document specifies the functional architecture, procedures and information flows needed to support the Mission Critical Data (MCData) services. MCData is a suite of services which utilizes the common functional architecture defined in TS 23.280 to support MC services over LTE including the common services core.
MCData services suite consists of the following sub-services:
  • short data service (SDS);
  • file distribution (FD);
  • data streaming (DS); and
  • IP connectivity.
MCData features include:
  • conversation management;
  • transmission and reception control;
  • communication release; and
  • enhanced status.
The corresponding service requirements are defined in TS 22.282 and TS 22.280.
The present document is applicable primarily to MCData service using E-UTRAN access based on the EPC architecture defined in TS 23.401. Certain application functions of the MCData service could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access.
The MCData service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.
Up

2  References  p. 16

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.280: "Mission Critical Common Requirements (MCCoRe); Stage 1".
[3]
TS 22.282: "Mission Critical Data services".
[4]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[5]
TS 23.280: "Common functional architecture and information flows to support mission critical communication services; Stage 2".
[6]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[7]
TS 23.303: "Proximity-based services (ProSe); Stage 2".
[8]
TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[9]
TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".
[10]
TS 23.002: "Network Architecture".
[11]
TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); stage 2".
[12]
TS 29.283: "Diameter data management applications".
[13]
TS 33.180: "Security of the Mission Critical Service".
[14]
TS 23.203: "Policy and charging control architecture".
[15]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[16]
TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 reference point; Stage 3".
[17]
TS 29.214: "Policy and charging control over Rx reference point".
[18]
TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems; Stage 2".
[19]
TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point".
[20]
TS 29.116: "Representational state transfer over xMB reference point between content provider and BM-SC".
[21]
TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[22]
TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
Up

3  Definitions, symbols and abbreviations  p. 17

3.1  Definitions  p. 17

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.
Auto-receive:
A mechanism where data smaller than a configured size threshold are delivered to the receiving MCData client(s) from the MCData server i.e. without waiting for the receiving user to indicate a present need for the data.
Conversation identifier:
A universally unique identifier that identifies a series of related MCData transactions.
Data stream:
A sequence of data that is agnostic to any underlying media (e.g. audio, video, telemetry data), on which processing of data (e.g. semantic, syntactic, save or filter operation) can begin before all the content is received.
FD disposition:
is one of "not downloaded" and "download completed".
Folder Identifier:
A unique identifier that identifies a folder in the MCData message store
IP Data:
Structured or unstructured payload that is transparent to the MCData transport service.
MCData client:
An instance of an MC service client that provides the client application function for the MCData service.
MCData emergency communication:
An MC service emergency group communication or MC service emergency private communication within the MCData service.
MCData group:
An MC service group configured for MCData service.
MCData group affiliation:
An MC service group affiliation for MCData.
MCData group communication:
A one-to-many communication using an MCData service.
MCData group de-affiliation:
An MC service group de-affiliation for MCData.
MCData ID:
An instance of an MC service ID within the MCData service.
MCData imminent peril communication:
An MC service imminent peril group communication within the MCData service.
MCData server:
An instance of an MC service server that provides the server application function for the MCData service.
MCData service:
A data communication service comprising at least one underlying generic capability (e.g. SDS, file distribution, data streaming) with strong security, high availability, reliability and priority handling to support applications for mission critical organizations and mission critical applications for other businesses and organizations (e.g. utilities, railways).
MCData UE:
An MC service UE that can be used to participate in MCData services.
MCData user:
An MC service user who is authorized for MCData services suite via an MCData UE.
Metadata:
data associated with a transmitted or stored SDS, file or data stream, consisting of information from messages (e.g. MCData IDs, conversation ID) and other related information (e.g. size, type).
Object:
An MCData communication information (such as a message or a file) that is stored in the MCData message store with its associated metadata.
Object identifier:
A unique identifier that identifies an object stored in the MCData message store.
Reception control:
A mechanism that allows the MCData service to regulate data reception to the receiving MCData clients.
Reply identifier:
A reference to the original MCData transaction to which the current transaction is a reply.
SDS data:
A payload with limited size and variable content type used in SDS transactions.
SDS disposition:
is one of "undelivered", "delivered" and "read".
Standalone communication:
A unidirectional one-to-one or group data communication completed after one transaction.
Transaction identifier:
A unique identifier that identifies a MCData transaction within a conversation.
Transmission control:
A mechanism that allows the MCData service to regulate data transmission requests from the sending MCData users, either prior to or after active sending from the MCData UE.
For the purposes of the present document, the following terms and definitions given in TS 22.280 apply:
Mission Critical
Mission Critical Applications
Mission Critical Service
Mission Critical Organization
For the purposes of the present document, the following terms given in TS 22.179 apply:
Group-broadcast group
User-broadcast group
For the purposes of the present document, the following terms and definitions given in TS 22.282 apply:
MCData system
For the purposes of the present document, the following terms and definitions given in TS 23.280 apply:
Ad hoc Group Communication
MC service client
MC service group
MC service group affiliation
MC service group de-affiliation
MC service ID
MC service server
For the purposes of the present document, the following terms and definitions given in TS 23.203 apply:
Dynamic PCC rule
Up

3.2  Abbreviations  p. 19

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.
DS
Data Streaming
E2EE
End to End Encryption
FD
File Distribution
ITSI
Individual TETRA Subscriber Identity
LMR
Land Mobile Radio
MC
Mission Critical
MCData ID
MCData user identity
PCC
Policy and Charging Control
PCRF
Policy and Charging Rules Function
QCI
QoS Class Identifier
RSI
Radio Set Identity
SDS
Short Data Service
UM
Unacknowledged Mode
Up

4  Introduction  p. 19

The MCData service suite provides a set of generic capabilities and specific services to enable one-to-one and group data communications between MCData users.
The MCData architecture utilises the common functional architecture to support mission critical services over LTE defined in TS 23.280 and 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 defining MBMS support via the MB2 interface, the MBMS User Service architecture defined in TS 26.348, the Security of the Mission Critical Service in TS 33.180 and the PS-PS access transfer procedures defined in TS 23.237 to enable support of the MCData service.
The MCData UE primarily obtains access to the MCData service via E-UTRAN, using the EPS architecture defined in TS 23.401. Certain application functions of MCData service can be accessed using MCData UEs via non-3GPP access networks.
The MCData system provides the function to support interworking with LMR systems defined in TS 23.283.
Up

Up   Top   ToC