Content for TR 23.780 Word version: 14.0.0
4 Assumptions and architectural requirements
5 Key issues
6 Solutions
7 Overall evaluation
8 Conclusions
A Performance evaluation of solution 6-1 for MCPTT
B Interest of FEC for MCData file distribution capability
$ Change History
4 Assumptions and architectural requirements p. 11
4.1 General p. 11
4.2 Assumptions p. 11
4.3 High level reference diagram p. 11
4.4 Architectural requirements p. 14
5 Key issues p. 14
5.1 Key issue 1 - Service continuity p. 14
5.1.1 Description p. 14
5.2 Key issue 2 - Service announcement p. 15
5.2.1 Description p. 15
5.3 Key issue 3 - MBMS bearer reception acknowledgement p. 16
5.3.1 Description p. 16
5.4 Key issue 4 - Handling resource shortage p. 16
5.4.1 Description p. 16
5.4.2 Architectural requirements p. 16
5.5 Key issue 5 - Performance (KPI 3) p. 16
5.5.1 Description p. 16
5.6 Key issue 6 - Usage of Forward Error Correction (FEC) p. 17
5.6.1 Description p. 17
5.7 Key issue 7 - MBMS bearer management involving multiple MCPTT servers p. 17
5.7.1 Description p. 17
5.8 Key issue 8 - Cohesive MBMS operation p. 18
5.8.1 Description p. 18
5.8.2 Architectural requirements p. 19
5.9 Key issue 9 - Notification on MBMS bearer activation result p. 19
5.9.1 Description p. 19
5.9.2 Architectural requirements p. 20
5.10 Key issue 10 - Header compression of MBMS data p. 20
5.10.1 Description p. 20
5.11 Key issue 11 - Handling MBMS bearer suspension p. 20
5.11.1 Description p. 20
5.12 Key issue 12 - MBMS media delivery while UE in idle mode p. 21
5.12.1 Description p. 21
5.13 Key issue 13 - Location information reporting p. 21
5.13.1 Description p. 21
5.14 Key issue 14 - MBMS usage in roaming, interconnect and migration scenarios p. 22
5.14.1 Description p. 22
5.15 Key issue 15 - Packet drop due to IP Differentiated Services p. 22
5.15.1 Description p. 22
5.16 Key issue 16 - MBMS bearer usage across different MC services p. 22
5.16.1 Description p. 22
6 Solutions p. 23
6.1 Solution 1-1: Service continuity between MBSFN areas used by different MBMS bearers p. 23
6.1.1 Solution description p. 23
6.1.2 Impact on the existing nodes and functionality p. 24
6.1.3 Solution evaluation p. 24
6.2 Solution 1-2: Service continuity with a UE-to-Network relay p. 25
6.2.1 Description p. 25
6.2.2 Procedure p. 26
6.2.3 Impact on the existing nodes and functionality p. 27
6.2.4 Solution evaluation p. 27
6.3 Solution 1-3: Service continuity p. 27
6.3.1 Description p. 27
6.3.2 Procedure enhancements p. 28
6.3.3 Impact on the existing nodes and functionality p. 28
6.3.4 Solution evaluation p. 28
6.4 Solution 2-1: MBMS bearer announcement over MBMS bearer p. 29
6.4.1 Description p. 29
6.4.2 Procedure p. 29
6.4.3 Impacts on existing nodes and functionality p. 31
6.4.4 Solution evaluation p. 31
6.5 Solution 3-1: MBMS bearer quality detection p. 31
6.5.1 Description p. 31
6.5.2 Procedure p. 31
6.5.3 Impact on the existing nodes and functionality p. 32
6.5.4 Solution evaluation p. 32
6.6 Solution 5-1: Enhanced MCPTT group call setup procedure with MBMS bearer p. 32
6.6.1 Description p. 32
6.6.2 Procedure p. 33
6.6.3 Impacts on existing nodes and functionality p. 34
6.6.4 Solution evaluation p. 34
6.7 Solution 6-1: FEC for Mission Critical Services p. 35
6.7.1 Introduction p. 35
6.7.2 Use Cases p. 35
6.7.3 QoS requirements p. 35
6.7.3.1 QCI and target packet error loss rates p. 35
6.7.3.2 Latency requirements for mission critical services p. 36
6.7.4 Group call - Call flow p. 36
6.7.5 FEC Transport requirements p. 37
6.7.6 Radio scheduling aspects and FEC for MCPTT p. 38
6.7.7 Impacts on existing nodes and functionality p. 39
6.7.8 Solution evaluation p. 39
6.8 Solution 6-2: Mission Critical Server-based FEC p. 39
6.8.1 Description p. 39
6.8.2 Procedure p. 39
6.8.3 Impacts on existing nodes and functionality p. 40
6.8.4 Solution evaluation p. 41
6.9 Solution 7-1: Service area owning MC service server distributes media p. 41
6.9.1 Description p. 41
6.9.2 Procedure p. 42
6.9.3 Impacts on existing nodes and functionality p. 43
6.9.4 Solution evaluation p. 43
6.10 Solution 7-2: MBMS bearer management by MC service server (controlling role) with multiple MC service servers involved p. 43
6.10.1 Description p. 43
6.10.2 Procedure p. 44
6.10.3 Impacts on existing nodes and functionality p. 44
6.10.4 Solution evaluation p. 45
6.11 Solution 8-1: GCS AS to indicate the preferred MBMS mechanism to the MCE p. 45
6.11.1 Description p. 45
6.11.2 Procedure p. 45
6.11.3 Impacts on existing nodes and functionality p. 47
6.11.4 Solution evaluation p. 47
6.12 Solution 8-2: MCE derives the MBMS mechanism with the interaction with the eNB and the UE p. 47
6.12.1 Description p. 47
6.12.2 Procedure p. 48
6.12.3 Impacts on existing nodes and functionality p. 50
6.12.4 Solution evaluation p. 50
6.13 Solution 9-1: Notification of MBMS bearer activation result p. 50
6.13.1 Description p. 50
6.13.2 Procedure p. 50
6.13.3 Impacts on existing nodes and functionality p. 52
6.13.4 Solution evaluation p. 52
6.14 Solution 10-1: Header compression of MBMS data p. 52
6.14.1 Introduction p. 52
6.14.2 Capacity improvements with ROHC p. 52
6.14.3 Impact on performances p. 53
6.14.4 Architecture with ROHC p. 54
6.14.5 Impact on existing nodes and functionality p. 54
6.14.6 Solution evaluation p. 55
6.15 Solution 10-2: header compression function within the BM-SC p. 55
6.15.1 Introduction p. 55
6.15.2 Gain on late entry KPI p. 55
6.15.2.1 Packet scheduling p. 55
6.15.2.2 Alignment of the full header packets with the MCH Scheduling Period p. 55
6.15.3 Architecture and call flow p. 57
6.15.4 Impacts on existing nodes and functionality p. 58
6.15.5 Solution evaluation p. 58
6.16 Solution 11-1: Reporting of MBMS bearer suspension. p. 58
6.16.1 Description p. 58
6.16.2 Procedure p. 58
6.16.3 Impacts on existing nodes and functionality p. 58
6.16.4 Solution evaluation p. 59
6.17 Solution 11-2: MBMS suspension notification p. 59
6.17.1 Description p. 59
6.17.2 Procedure p. 59
6.17.3 Impact on the existing nodes and functionality p. 60
6.17.4 Solution evaluation p. 60
6.18 Solution 12-1: Media delivery for MC service clients in MBMS MC receive-only mode p. 61
6.18.1 Description p. 61
6.18.2 Procedure p. 61
6.18.3 Change of cell in MBMS MC receive-only mode p. 62
6.18.4 Impacts on existing nodes and functionality p. 62
6.18.5 Solution evaluation p. 62
6.19 Solution 13-1: Location reporting p. 63
6.19.1 Solution description p. 63
6.19.1.1 General p. 63
6.19.1.2 Scenario 1 - Mobility within an MBMS SAI p. 63
6.19.1.3 Scenario 2 - Mobility within one MBMS bearer p. 64
6.19.1.4 Scenario 3 - Mobility between MBMS bearers (with Flow ID or Session ID) p. 64
6.19.1.5 Scenario 4 - Mobility and using a separate MBMS bearer for control messages p. 65
6.19.2 Procedures p. 66
6.19.3 Impact on the existing nodes and functionality p. 67
6.19.4 Solution evaluation p. 67
6.20 Solution 14-1: MBMS when roaming p. 67
6.20.1 Description p. 67
6.20.2 Impacts on existing nodes and functionality p. 68
6.20.3 Solution evaluation p. 68
6.21 Solution 15-1: Usage of IP Differentiated Services p. 68
6.21.1 Description p. 68
6.21.2 Impacts on existing nodes and functionality p. 68
6.21.3 Solution evaluation p. 68
6.22 Solution 16-1: MBMS bearer usage across different MC services p. 68
6.22.1 Description p. 68
6.22.2 Procedure p. 70
6.22.2.1 Location information acquiring for MBMS p. 70
6.22.2.2 Use of pre-established MBMS bearer p. 70
6.22.2.2.1 General p. 70
6.22.2.2.2 Procedures p. 71
6.22.2.3 Use of dynamic MBMS bearer establishment p. 72
6.22.2.3.1 General p. 72
6.22.2.3.2 Procedures p. 73
6.22.3 Impacts on existing nodes and functionality p. 74
6.22.4 Solution evaluation p. 74
7 Overall evaluation p. 74
8 Conclusions p. 78
8.1 General p. 78
8.2 Conclusions on key issues p. 78
8.2.1 Key issue 1 - Service continuity p. 78
8.2.2 Key issue 2 - Service announcement p. 78
8.2.3 Key issue 3 - MBMS bearer reception acknowledgement p. 78
8.2.4 Key issue 4 - Handling resource shortage p. 78
8.2.5 Key issue 5 - Performance (KPI 3) p. 79
8.2.6 Key issue 6 - Usage of Forward Error Correction (FEC) p. 79
8.2.7 Key issue 7 - MBMS bearer management involving multiple MCPTT servers p. 79
8.2.8 Key issue 8 - Cohesive MBMS operation p. 79
8.2.9 Key issue 9 - Notification on MBMS bearer activation result p. 79
8.2.10 Key issue 10 - Header compression of MBMS data p. 80
8.2.11 Key issue 11 - Handling MBMS bearer suspension p. 80
8.2.12 Key issue 12 - MBMS media delivery while UE in idle mode p. 80
8.2.13 Key issue 13 - Location information reporting p. 80
8.2.14 Key issue 14 - MBMS usage in roaming, interconnect and migration scenarios p. 80
8.2.15 Key issue 15 - Packet drop due to IP Differentiated Services p. 80
8.2.16 Key issue 16 - MBMS bearer usage across different MC services p. 80
8.3 Normative Rel-14 work p. 80
A Performance evaluation of solution 6-1 for MCPTT p. 82
A.1 MBMS Bearer Simulation Model p. 82
A.2 Application layer FEC used for evaluation p. 87
A.2.1 General p. 87
A.2.2 RS (2, 4, l) configurations p. 87
A.2.3 RS (4, 8, l) configurations p. 88
A.2.4 RS (4, 6, l) configurations p. 88
A.3 Simulation Results p. 89
B Interest of FEC for MCData file distribution capability p. 91
$ Change History p. 93
