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  TR 23.792  Word version:  16.0.0

Top   Top   None   None   Next
1…   5… 
1 Scope  2 References  3 Definitions and abbreviations  3.1 Definitions  3.2 Abbreviations  4 Requirements and reference model 
...

 

1  Scope  p. 7

The present document is a technical report that identifies the MBMS API solutions on the UE for mission critical applications to access MBMS bearer service for the usage of mission critical services. The aspects of the study include identifying functional requirements, methods and message flows, client reference model, potential impacts to MC system architecture, and the review of existing and new MBMS capabilities for use by MC services.

2  References  p. 7

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.282: "Mission Critical Data services".
[3]
TS 23.280: "Common functional architecture to support mission critical services; Stage 2".
[4]
TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2".
[5]
TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2".
[6]
TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2".
[7]
TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[8]
TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[9]
TS 26.347: "Multimedia Broadcast/Multicast Service (MBMS); Application Programming Interface and URL".
[10]
TS 29.116: "Representational state transfer over xMB reference point between content provider and BM-SC".
[11]
TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 reference point; Stage 3".
[12]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[13]
RFC 3926:  "FLUTE - File Delivery over Unidirectional Transport".
[14]
RFC 6363:  "Forward Error Correction (FEC) Framework".
[15]
RFC 6681:  "Raptor FEC Schemes for FECFRAME".
Up

3  Definitions and abbreviations  p. 8

3.1  Definitions  p. 8

MC MBMS API:
An application programming interface on the UE to enable the use of MBMS bearer service for mission critical applications.
MBMS bearer availability:
Presence of the TMGI identifying an MBMS bearer within the radio control channels.
MBMS bearer quality monitoring:
Continuous evaluation of the reception quality of an MBMS bearer, with or without data being received on the MBMS bearer.

3.2  Abbreviations  p. 8

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.
API
Application Programming Interface
BM-SC
Broadcast Multicast Service Centre
ECGI
E-UTRAN Cell Global Identifier
FEC
Forward Error Correction
FLUTE
File deLivery over Unidirectional Transport
MBMS
Multimedia Broadcast and Multicast Service
MCCH
Multicast Control Channel
MCData
Mission Critical Data
MCPTT
Mission Critical Push To Talk
MCVideo
Mission Critical Video
ROHC
Robust Header Compression
SACH
Service Announcement Channel
SAI
Service Area Identity
SC-MCCH
Single Cell Multicast Control Channel
SDP
Session Description Protocol
TMGI
Temporary Mobile Group Identity
USD
User Service Description
Up

4  Requirements and reference model  p. 8

4.1  Functional requirements  p. 8

[MBMSAPI-FR-1]
The MC MBMS API shall support registration and de-registration of MC service applications, for the use of MBMS services on the UE.
[MBMSAPI-FR-2]
The MC MBMS API shall provide mechanisms to notify the MC applications the multicast location information of the MC service UE.
[MBMSAPI-FR-3]
The MC MBMS API shall provides mechanisms for the MC applications to query the multicast location information of the MC service UE.
[MBMSAPI-FR-4]
The MC MBMS API shall provide mechanisms to notify the MC applications about the MBMS bearer announcement and de-announcement that is sent over MBMS.
[MBMSAPI-FR-5]
The MC MBMS API shall support mechanisms for the MC applications to start and stop monitoring the MBMS bearer quality.
[MBMSAPI-FR-6]
The MC MBMS API shall be asynchronous for the MC applications.
[MBMSAPI-FR-7]
The MC MBMS API shall support event notification of MBMS bearer quality detection.
[MBMSAPI-FR-8]
The MC MBMS API shall support event notification of MBMS suspension and MBMS resumption.
[MBMSAPI-FR-9]
The MC MBMS API shall support mechanisms for the MC applications to receive the MBMS data from the MC MBMS user agent.
[MBMSAPI-FR-10]
The MC MBMS user agent shall support multiple MC applications to use the MC MBMS API.
[MBMSAPI-FR-11]
The MC MBMS API shall allow concurrent calls without blocking the calling application.
Up

4.2  Reference model  p. 9

4.2.1  General  p. 9

Copy of original 3GPP image for 3GPP TS 23.792, Fig. 4.2.1-1: MC MBMS API reference model
Figure 4.2.1-1: MC MBMS API reference model
(⇒ copy of original 3GPP image)
Up
In the reference model the MC application can represent an MC service client.
The MC MBMS user agent supports the MC service client functions in receiving the MBMS bearer data for the use of MBMS transmission defined in TS 23.280, TS 23.379, TS 23.281 and TS 23.282.
Up

4.2.2  MC application  p. 9

The MC application invokes the MC MBMS API to access and manage the MBMS bearers to support MC services.
The MC application supports the following functions:
  • Registration and deregistration to the MC MBMS user agent;
  • Reception of application level control signalling messages;
  • Activation and termination of MBMS bearer quality monitoring;
  • Obtaining MBMS bearer availability through the MC MBMS API;
  • Obtaining MBMS bearer suspension and resumption status through the MC MBMS API;
  • Reception of media with or without FEC encoding and media with or without ROHC compression from the MC MBMS user agent;
  • Obtaining location information for MBMS usage through the MC MBMS API; and
  • Configuration of the MC MBMS user agent.
Up

4.2.3  MC MBMS user agent  p. 10

The MC MBMS user agent may provide MBMS media with FEC and ROHC to the MC application.
One or more MC application(s) use the MC MBMS API provided by the MC MBMS user agent.
The MC MBMS user agent supports the following functions:
  • Detection of location information for MBMS usage;
  • Detection of MBMS bearer availability;
  • Report of MBMS bearer quality to the MC application;
  • Reception of MBMS data from a lower layer of the UE;
  • Detection of suspension of MBMS bearer; and
  • Delivery of media with or without FEC encoding and media with or without ROHC compression to the MC application.
Up

4.3  Deployment considerations  p. 10

No deployment issues have been identified in the present document.

Up   Top   ToC