Tech-invite   3GPPspecs   Glossaries   IETFRFCs   Groups   SIP   ABNFs   Ti+   Search in Tech-invite

Top   in Index   Prev   Next

TR 23.780 (SA6)
Study on MBMS Usage
for Mission Critical Communication Services

3GPP‑Page   full‑ToC    
use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V14.0.0 (Wzip)  2016/12  93 p.


Rapporteur:  Mr. Trank, Magnus
See also:

The objective of this technical report is to study how mission critical communication services utilize MBMS.

full Table of Contents for  TR 23.780  Word version:   14.0.0

 

Here   Top

 

1  ScopeWord-p. 9
2  References
3  Definitions and abbreviationsWord-p. 10
4  Assumptions and architectural requirementsWord-p. 11
5  Key issues
5.1  Key issue 1 - Service continuity
5.2  Key issue 2 - Service announcementWord-p. 15
5.3  Key issue 3 - MBMS bearer reception acknowledgementWord-p. 16
5.4  Key issue 4 - Handling resource shortage
5.5  Key issue 5 - Performance (KPI 3)
5.6  Key issue 6 - Usage of Forward Error Correction (FEC)Word-p. 17
5.7  Key issue 7 - MBMS bearer management involving multiple MCPTT servers
5.8  Key issue 8 - Cohesive MBMS operationWord-p. 18
5.9  Key issue 9 - Notification on MBMS bearer activation result
5.10  Key issue 10 - Header compression of MBMS data
5.11  Key issue 11 - Handling MBMS bearer suspension
5.12  Key issue 12 - MBMS media delivery while UE in idle modeWord-p. 21
5.13  Key issue 13 - Location information reporting
5.14  Key issue 14 - MBMS usage in roaming, interconnect and migration scenariosWord-p. 22
5.15  Key issue 15 - Packet drop due to IP Differentiated Services
5.16  Key issue 16 - MBMS bearer usage across different MC services
6  SolutionsWord-p. 23
6.1  Solution 1-1: Service continuity between MBSFN areas used by different MBMS bearers
6.2  Solution 1-2: Service continuity with a UE-to-Network relayWord-p. 25
6.3  Solution 1-3: Service continuity
6.4  Solution 2-1: MBMS bearer announcement over MBMS bearerWord-p. 29
6.5  Solution 3-1: MBMS bearer quality detection
6.6  Solution 5-1: Enhanced MCPTT group call setup procedure with MBMS bearer
6.7  Solution 6-1: FEC for Mission Critical ServicesWord-p. 35
6.8  Solution 6-2: Mission Critical Server-based FEC
6.9  Solution 7-1: Service area owning MC service server distributes mediaUp
6.10  Solution 7-2: MBMS bearer management by MC service server (controlling role) with multiple MC service servers involved
6.11  Solution 8-1: GCS AS to indicate the preferred MBMS mechanism to the MCEUp
6.12  Solution 8-2: MCE derives the MBMS mechanism with the interaction with the eNB and the UE
6.13  Solution 9-1: Notification of MBMS bearer activation resultUp
6.14  Solution 10-1: Header compression of MBMS data
6.15  Solution 10-2: header compression function within the BM-SC
6.16  Solution 11-1: Reporting of MBMS bearer suspension.Up
6.17  Solution 11-2: MBMS suspension notification
6.18  Solution 12-1: Media delivery for MC service clients in MBMS MC receive-only modeWord-p. 61
6.19  Solution 13-1: Location reportingWord-p. 63
6.20  Solution 14-1: MBMS when roaming
6.21  Solution 15-1: Usage of IP Differentiated Services
6.22  Solution 16-1: MBMS bearer usage across different MC services
7  Overall evaluation
8  ConclusionsWord-p. 78
A  Performance evaluation of solution 6-1 for MCPTTWord-p. 82
B  Interest of FEC for MCData file distribution capabilityWord-p. 91
C  Change historyWord-p. 93

Up   Top