TR 23.783
Study on Mission Critical (MC) services support over the 5G System (5GS)
V18.0.0 (Wzip)
2022/06 194 p.
- Rapporteur:
- Mr. Verweij, Kees
The Police of the Netherlands
full Table of Contents for TR 23.783 Word version: 18.0.0
1 Scope p. 14
The present document analyses how to ensure that the set of Mission Critical services is supported over the 5GS. Key issues are derived and solutions are developed for the impacts on existing or new Stage 2 Mission Critical specifications.
2 References p. 14
3 Definitions and abbreviations p. 15
3.1 Definitions p. 15
3.2 Abbreviations p. 15
4 Subclauses in Mission Critical Specifications containing E-UTRAN/EPS specific terminology p. 15
4.1 Introduction p. 15
4.2 TS 23.280 p. 15
4.2.1 Proposed change to 1 Scope p. 15
4.2.2 Proposed change to 2 References p. 16
4.2.3 Proposed change to 3.2 Abbreviations p. 16
4.2.4 Proposed change to 4 Introduction p. 16
4.2.5 Proposed change to 9.2.1.1 On-network architectural model diagram p. 16
4.2.6 Proposed change to 9.2.1.4 EPSE-UTRAN or 5G System p. 17
4.2.7 Proposed change to 10.12.1 General p. 17
4.3 TS 23.281 p. 18
4.3.1 Proposed change to 1 Scope p. 18
4.3.2 Proposed change to 2 References p. 18
4.3.3 Proposed change to 6.2.2.2 Common services core p. 18
4.4 TS 23.282 p. 18
4.4.1 Proposed change to 1 Scope p. 18
4.4.2 Proposed change to 2 References p. 19
4.4.3 Proposed change to 4 Introduction p. 19
4.5 TS 23.283 p. 19
4.6 TS 23.379 p. 19
4.6.1 Proposed change to 1 Scope p. 19
4.6.2 Proposed change to 2 References p. 20
4.6.3 Proposed change to 3.1 Definitions p. 20
4.6.4 Proposed change to 4 Introduction p. 21
4.7 TS 23.479 p. 22
5 Key issues to ensure support of Mission Critical services over 5GS p. 22
5.1 Key issue 1: Service continuity between on-network MC services and UE-to-network relay MC service p. 22
5.1.1 Description p. 22
5.1.2 Architectural requirements p. 22
5.2 Key issue 2: 5GC level roaming p. 22
5.2.1 Description p. 22
5.2.2 Architectural requirements p. 23
5.3 Key issue 3: Use of multicast p. 23
5.3.1 Description p. 23
5.3.2 Architectural requirements p. 23
5.4 Key issue 4: ProSe p. 23
5.4.1 Description p. 23
5.4.2 Architectural requirements p. 24
5.5 Key issue 5: APN p. 24
5.5.1 Description p. 24
5.5.2 Architectural requirements p. 24
5.6 Key issue 6: resource control p. 24
5.6.1 Description p. 24
5.6.2 Architectural requirements p. 25
5.7 Key issue 7: Deployment scenarios p. 25
5.7.1 Description p. 25
5.7.2 Architectural requirements p. 25
5.8 Key issue 8: Determine impacts of 5GS network slicing to MC services p. 25
5.8.1 Description p. 25
5.8.2 Architectural requirements p. 27
5.9 Key issue 9: IP-based wireline access to MC System located on 5GS p. 27
5.9.1 Description p. 27
5.9.2 Architectural requirements p. 28
5.10 Key issue 10: Low latency and user/media plane capabilities p. 28
5.11 Key issue 11: MC system supporting MC service UEs accessing through both 5GC and EPC p. 28
5.11.1 General p. 28
5.11.2 Potential gaps p. 29
5.12 Key issue 12: Service continuity of MC UE mobility between MC system over 5GS and EPC p. 29
5.12.1 General p. 29
5.12.2 Potential gaps p. 29
5.13 Key issue 13: MC service over 5G MBS p. 29
5.13.1 Description p. 29
5.13.2 Architectural requirements p. 32
5.14.1 Description p. 32
5.14.2 Architectural requirements p. 33
5.15 Key issue 15: Use of 5QI's p. 33
5.15.1 Description p. 33
5.15.2 Architectural requirements p. 34
6 Solutions to ensure support of Mission Critical services over 5GS p. 34
6.1 Solution 1: APN - Access to the Data Network p. 34
6.1.1 Description p. 34
6.1.1.1 General p. 34
6.1.1.2 5GS Data Network (DN) access p. 35
6.1.1.3 EPS versus 5GS QoS model p. 35
6.1.1.4 Changes to the functional architecture p. 36
6.1.1.5 Data Network (DN) AAA Server authentication/authorization p. 36
6.1.1.6 Observation and conclusions p. 37
6.1.1.6.1 Observation p. 37
6.1.1.6.2 Conclusion(s) p. 37
6.1.1.7 Proposed changes to TS 23.280 p. 37
6.1.1.7.1 Proposed changes to 5.2.7 EPS Bearerresource management p. 37
6.1.1.7.2 Proposed new 5.2.7a 5GS resource management p. 37
6.1.1.7.3 Proposed new 5.2.7a.0 General p. 37
6.1.1.7.4 Proposed new 5.2.7a.1 MBMS bearer management p. 38
6.1.1.7.5 Proposed changes to 5.2.7.2 Transport resource considerations p. 38
6.1.1.7.6 Proposed new 5.2.7.2.3 Considerations for the 5GS PDU session to the MC services DN p. 38
6.1.1.7.7 Proposed new 5.2.7.2.4 Considerations for the 5GS PDU session to the MC common core services DN and MC identity management service DN p. 38
6.1.1.7.8 Proposed changes to 7.3.1 On-network functional model p. 38
6.1.1.7.9 Proposed changes to 10.1.1.1 MC service configuration on primary MC system p. 44
6.1.1.7.10 Proposed changes to A.6 Initial MC service UE configuration data p. 45
6.1.1.8 Proposed changes to TS 23.281 5.5.1 General p. 47
6.1.1.9 Proposed changes to TS 23.282 5.8.1 General p. 48
6.1.1.9a Proposed change to TS 23.282 7.13.6.2 Migration p. 48
6.1.1.10 Proposed changes to TS 23.379 5.7.1 General p. 48
6.1.2 Solution evaluation p. 48
6.2 Solution 2: Roaming aspects over 5GS p. 48
6.2.1 Description p. 48
6.2.1.1 General p. 48
6.2.1.2 Proposed changes to TS 23.280 5.2.2 Roaming requirements p. 48
6.2.1.3 Proposed changes to TS 23.280 5.2.9 Migration p. 49
6.2.1.4 Proposed changes to TS 23.280 9.4 Architecture model for roaming p. 49
6.2.2 Impacts on existing nodes and functionality p. 49
6.2.3 Solution evaluation p. 50
6.3 Solution 3: 5GS resource control aspects p. 50
6.3.1 Description p. 50
6.3.1.1 General p. 50
6.3.1.2 Proposed changes to 3GPP TS 23.280 p. 50
6.3.1.2.1 Proposed new subclause 5.2.7.2.3 Considerations for the 5GS PDU session to the MC services DN 5.2.7.2.3.1 General p. 50
6.3.1.2.2 Proposed changes to clause 7.2 Description of the planes p. 51
6.3.1.2.3 Proposed change to 10.11.2 Request for unicast resources at session establishment using EPS p. 51
6.3.1.2.4 Proposed new subclause 10.11.2a Request for unicast resources at session establishment using 5GS p. 52
6.3.1.2.5 Proposed new subclause 10.11.3a Request for modification of unicast resources using 5GS p. 53
6.3.1.2.7 Proposed change to 10.11.5.1 General p. 54
6.3.1.2.8 Proposed new subclause 10.11.5.3 5GS related procedure p. 55
6.3.1.2.9 Proposed change to 10.11.6.1 General p. 56
6.3.1.2.10 Proposed changes to 10.11.6.2 EPS related Pprocedure p. 56
6.3.1.2.11 Proposed new subclause 10.11.6.3 5GS related procedure p. 57
6.3.1.3 Proposed changes to 3GPP TS 23.281 p. 58
6.3.1.3.1 Proposed change to 5.5 ESP resourceBearer management p. 59
6.3.1.3.2 Proposed new subclause 5.6 5GS resource management p. 59
6.3.1.3.3 Proposed new subclause 5.6.1 General p. 59
6.3.1.3.4 Proposed new subclause 5.6.2 5GS considerations p. 59
6.3.1.3.5 Proposed new subclause 5.6.3 5GS unicast considerations for MCVideo p. 59
6.3.1.3.6 Proposed changes to 6.1.1 On-network functional model using EPS p. 59
6.3.1.3.7 Proposed new subclause 6.1a.1 On-network functional model using 5GS p. 60
6.3.1.3.8 Proposed change to 6.2.2 MCVideo service application plane using EPS p. 61
6.3.1.3.9 Proposed changes to 6.2.2.2 Common services core p. 61
6.3.1.3.10 Proposed new subclause 6.2.3 MCVideo service application plane using 5GS p. 61
6.3.1.3.11 Proposed new subclause 6.2.3.1 General p. 61
6.3.1.3.12 Proposed new subclause 6.2.3.2 Common services core p. 61
6.3.1.3.13 Proposed new subclause 6.2.3.3 MCVideo application service p. 61
6.3.1.3.14 Proposed new subclause 6.2.3.3.1 MCVideo client p. 61
6.3.1.3.15 Proposed new subclause 6.2.3.3.2 MCVideo server p. 62
6.3.1.3.16 Proposed new subclause 6.2.3.3.3 Media distribution function p. 62
6.3.1.3.17 Proposed new subclause 6.2.3.3.4 Media mixer p. 62
6.3.1.3.18 Proposed new subclause 6.2.3.3.5 MCVideo user database p. 62
6.3.1.3.19 Proposed new subclause 6.2.3.3.6 Transmission control server p. 63
6.3.1.3.20 Proposed new subclause 6.2.3.3.7 Transmission control participant p. 63
6.3.1.3.21 Proposed new subclause 6.2.3.3.8 MC gateway server p. 63
6.3.1.3.22 Proposed change to 6.3 Reference points using EPS p. 63
6.3.1.3.23 Proposed new subclause 6.4 Reference points using 5GS p. 63
6.3.1.3.24 Proposed new subclause 6.4.1 Reference point MCVideo-1 (between the MCVideo client and the MCVideo server) p. 63
6.3.1.3.25 Proposed new subclause 6.4.2 Reference point MCVideo-2 (between the MCVideo server and the MCVideo user database) p. 63
6.3.1.3.26 Proposed new subclause 6.4.3 Reference point MCVideo-3 (between the MCVideo server and the MCVideo server and between the MCVideo server and the MC gateway server) p. 63
6.3.1.3.27 Proposed new subclause 6.4.4 Reference point MCVideo-4 (between the transmission control participant and the transmission control server) p. 63
6.3.1.3.28 Proposed new subclause 6.4.4A Reference point MCVideo-5 (unicast between the media distribution function and 5GS) p. 64
6.3.1.3.29 Proposed new subclause 6.4.5 Reference point MCVideo-7 (between the media distribution function and the media mixer) p. 64
6.3.1.3.30 Proposed new subclause 6.4.8 Reference point MCVideo-10 (between the MC gateway server and the MC gateway server in a different MCVideo system) p. 64
6.3.1.3.31 Proposed change to 7.10 Use of MBMS transmission (on-network) using EPS p. 64
6.3.1.4 Proposed changes to 3GPP TS 23.282 p. 64
6.3.1.4.1 Proposed changes to 4 Introduction p. 64
6.3.1.4.2 Proposed change for 5.4 File distribution capability p. 64
6.3.1.4.3 Proposed change to 5.8.4 EPS MBMS bearer management p. 66
6.3.1.4.4 Proposed new subclause 5.8.5 5GS considerations p. 66
6.3.1.4.5 Proposed new subclause 5.8.6 5GS unicast considerations for MCData p. 66
6.3.1.4.6 Proposed changes to 6.4.1 On-network functional model p. 66
6.3.1.4.7 Proposed changes to 6.4.4.1 Application plane using EPS p. 68
6.3.1.4.8 Proposed new subclause 6.4.4.2 Application plane using 5GS p. 68
6.3.1.4.9 Proposed new subclause 6.4.4.2.1 General p. 68
6.3.1.4.10 Proposed new subclause 6.4.4.2.2 Reference point MCData-2 (between the MCData server and the MCData user database) p. 68
6.3.1.4.11 Proposed new subclause 6.4.4.2.3 Reference point MCData-3 (between the MCData server and the MCData server) p. 68
6.3.1.4.12 Proposed new subclause 6.4.4.2.3A Reference point MCData-5 (between the MCData capability function and 5GS) p. 68
6.3.1.4.13 Proposed new subclause 6.4.4.2.4 Reference point MCData-6 (between the MCData server and 5GS) p. 68
6.3.1.4.14 Proposed new subclause 6.4.4.2.5 Reference point IWF-2 (between the interworking function to LMR system and the MCData server) p. 68
6.3.1.4.15 Proposed new subclause 6.4.4.2.6 Reference point MCData-7 (between the Message store client and MCData message store) p. 68
6.3.1.4.16 Proposed new subclause 6.4.4.2.7 Reference point MCData-8 (between the MCData message store and MCData server) p. 69
6.3.1.4.17 Proposed new subclause 6.4.4.2.8 Reference point MCData-9 (between the MC gateway server and the MC gateway server in a different MCData system) p. 69
6.3.1.4.17a Proposed new subclause 6.4.4.2.9 Reference point MCData-10 (between the Message notification client and MCData notification server) p. 69
6.3.1.4.17b Proposed new subclause 6.4.4.2.10 Reference point MCData-11 (between the MCData message store and the MCData notification server) p. 69
6.3.1.4.18 Proposed changes to 6.5.1 On-network functional model using EPS p. 69
6.3.1.4.19 Proposed new subclause 6.5.1a On-network functional model using 5GS p. 70
6.3.1.4.20 Proposed changes to 6.5.4.1.3 Reference point MCData-SDS-3 (multicast between the SDS distribution function and the SDS function) p. 71
6.3.1.4.21 Proposed changes to 6.6.1 On-network functional model using EPS p. 71
6.3.1.4.22 Proposed new subclause 6.6.1b On-network functional model using 5GS p. 72
6.3.1.4.23 Proposed change to 6.6.4.1.3 Reference point MCData-FD-3 (multicast between the FD functions of the MCData client and the MCData server) p. 73
6.3.1.4.24 Proposed change to 6.7.1 On-network functional model using EPS p. 73
6.3.1.4.25 Proposed new subclause 6.7.1a On-network functional model using 5GS p. 73
6.3.1.4.26 Proposed change to 6.7.4.1.3 Reference point MCData-DS-3 (multicast between the data streaming and distribution function and the DS function) p. 74
6.3.1.5 Proposed changes to 3GPP TS 23.379 p. 74
6.3.1.5.1 Proposed change to 4 Introduction p. 74
6.3.1.5.2 Proposed new subclause 5.7.2a 5GS considerations p. 75
6.3.1.5.3 Proposed new subclause 5.7.3a 5GS unicast considerations for MCPTT p. 75
6.3.1.5.4 Proposed changes to 7.3.1 On-network functional model using EPS p. 75
6.3.1.5.5 Proposed new subclause 7.3.1a On-network functional model using 5GS p. 77
6.3.1.5.6 Proposed changes to 7.4.2.3.5 Media distribution function p. 78
6.3.1.5.7 Proposed change to 7.5.2.2 Reference point MCPTT-1 (between the MCPTT client and the MCPTT server) using EPS p. 79
6.3.1.5.8 Proposed new subclause 7.5.2.2a Reference point MCPTT-1 (between the MCPTT client and the MCPTT server) using 5GS p. 79
6.3.1.5.9 Proposed new subclause 7.5.2.6a Reference point MCPTT-5 (between the MCPTT server and the 5GS) p. 79
6.3.1.5.10 Proposed change to 7.5.2.8 Reference point MCPTT-7 (unicast between the media distribution function and the media mixer) using EPS p. 80
6.3.1.5.11 Proposed new subclause 7.5.2.8a Reference point MCPTT-7 (unicast between the media distribution function and the media mixer) using 5GS p. 80
6.3.1.5.12 Proposed change to 7.5.2.9 Reference point MCPTT-8 (multicast between the media distribution function and the media mixer) using EPS p. 80
6.3.1.5.13 Proposed change to 7.5.2.10 Reference point MCPTT-9 (multicast between the floor control server and the floor participant) using EPS p. 80
6.3.1.6 Request for unicast resources at session establishment using AF session with required QoS via NEF p. 80
6.3.1.7 Request for unicast resource update in ongoing session using AF session with required QoS update via NEF p. 81
6.3.2 Solution evaluation p. 82
6.4 Solution 4: Determine impacts of 5GS network slicing to MC services p. 83
6.4.1 Description p. 83
6.4.1.1 General p. 83
6.4.1.2 Network slicing constituents p. 83
6.4.1.3 Network slicing subscription and authorisation p. 83
6.4.1.4 Network slicing allocation and resource control p. 83
6.4.1.5 Session binding p. 84
6.4.1.6 Assessment key issue 8 - gaps p. 84
6.4.2 Solution evaluation p. 85
6.5 Solution 5: Flexible media distribution for low latency applications p. 85
6.5.1 Description p. 85
6.5.1.1 General p. 85
6.5.1.2 Potential approaches p. 85
6.5.1.3 Use of EPS p. 87
6.5.1.4 Use of 5GS p. 87
6.5.1.5 EPS versus 5GS assessment p. 88
6.5.2 Solution unbundling MC service server and the media distribution function p. 89
6.5.3 Solution evaluation p. 89
6.6 Solution 6: Deployment scenarios p. 89
6.6.1 Description p. 89
6.6.1.1 Proposed changes to 3GPP TS 23.280 subclause 9.2.2.1 Administration of MC service, SIP core and EPS5GS p. 90
6.6.1.1.1 Proposed changes to 9.2.2.1.1 General p. 90
6.6.1.1.2 Proposed changes to 9.2.2.1.2 Common administration of all planes p. 90
6.6.1.1.3 Proposed changes to 9.2.2.1.3 MC service provider separate from SIP core and EPS5GS p. 90
6.6.1.1.4 Proposed changes to 9.2.2.1.4 MC service provider administers SIP core, separate from EPS5GS p. 91
6.6.1.1.5 Proposed changes to 9.2.2.1.5 SIP core partially administered by both PLMN operator and MC service provider p. 92
6.6.1.1.6 Proposed changes to 9.2.2.1.6 PLMN operator administers SIP core with SIP identities administered by MC service provider p. 92
6.6.1.2 Proposed new subclause 3GPP TS 23.280 9.2.2.2a Deployment scenarios of MC service user database, SIP database and UDM p. 93
6.6.1.3 Proposed changes to 3GPP TS 23.280 subclause 9.2.2.3 Control of bearers5G QoS flows by SIP core and MC service server p. 96
6.6.2 Impacts on existing nodes and functionality p. 97
6.6.3 Solution evaluation p. 97
6.7 Solution 7: MC service integration p. 98
6.7.1 General p. 98
6.7.2 Common functional model impact p. 98
6.7.3 MC service's functional model impact p. 99
6.7.4 Solution evaluation p. 100
6.8 Solution 8: 5G MBS impacts on MC Service functional models p. 100
6.8.0 General p. 100
6.8.1 Description p. 101
6.8.2 Impacts on existing nodes and functionality p. 104
6.8.3 Solution evaluation p. 104
6.9 Solution 9: General use of 5G MBS services for MC service group communications p. 104
6.9.1 Description p. 104
6.9.2 Impacts on existing nodes and functionality p. 106
6.9.3 Solution evaluation p. 106
6.10 Solution 10: MBS session configuration and service announcement aspects p. 106
6.10.1 Description p. 106
6.10.1.1 MBS session configuration aspects p. 106
6.10.1.2 MBS service announcement aspects p. 108
6.10.1.3 Procedure p. 111
6.10.2 Impacts on existing nodes and functionality p. 112
6.10.3 Solution evaluation p. 113
6.11 Solution 11: MC service group data transmissions over 5G MBS sessions p. 113
6.11.1 Description p. 113
6.11.1.1 Procedure p. 114
6.11.2 Impacts on existing nodes and functionality p. 116
6.11.3 Solution evaluation p. 116
6.12 Solution 12: Dynamic multicast MBS session and service announcement p. 116
6.12.1 Description p. 116
6.12.1.1 Procedure p. 116
6.12.1.2 Information flows p. 118
6.12.2 Impacts on existing nodes and functionality p. 120
6.12.3 Solution evaluation p. 120
6.13 Solution 13: Pre-established multicast MBS session and service announcement p. 120
6.13.1 Description p. 120
6.13.1.1 Procedure p. 120
6.13.1.2 Information flows p. 122
6.13.2 Impacts on existing nodes and functionality p. 122
6.13.3 Solution evaluation p. 122
6.14 Solution 14: Dynamic broadcast MBS session and service announcement p. 122
6.14.1 Description p. 122
6.14.1.1 Procedure p. 122
6.14.1.2 Information flows p. 124
6.14.2 Impacts on existing nodes and functionality p. 127
6.14.3 Solution evaluation p. 127
6.15 Solution 15: Pre-established broadcast MBS session and service announcement p. 127
6.15.1 Description p. 127
6.15.1.1 Procedure p. 127
6.15.1.2 Information flows p. 129
6.15.2 Impacts on existing nodes and functionality p. 129
6.15.3 Solution evaluation p. 129
6.16 Solution 16: Data delivery over multicast MBS session p. 129
6.16.1 Description p. 129
6.16.1.1 Procedures p. 129
6.16.1.2 Information flows p. 131
6.16.2 Impacts on existing nodes and functionality p. 132
6.16.3 Solution evaluation p. 132
6.17 Solution 17: Data delivery over broadcast MBS session p. 132
6.17.1 Description p. 132
6.17.1.1 Procedures p. 133
6.17.1.2 Information flows p. 134
6.17.2 Impacts on existing nodes and functionality p. 134
6.17.3 Solution evaluation p. 135
6.18 Solution 18: Service continuity for multicast MBS session p. 135
6.18.1 Description p. 135
6.18.2 Impacts on existing nodes and functionality p. 135
6.18.3 Solution evaluation p. 135
6.19 Solution 19: Service continuity for broadcast MBS session p. 135
6.19.1 Description p. 135
6.19.1.1 Procedures p. 136
6.19.1.2 Information flows p. 139
6.19.2 Impacts on existing nodes and functionality p. 139
6.19.3 Solution evaluation p. 139
6.20 Solution 20: Selection of multicast and broadcast service for a group communication p. 139
6.20.1 Description p. 139
6.20.2 Impacts on existing nodes and functionality p. 140
6.20.3 Solution evaluation p. 140
6.21 Solution 21: Use of MBS transmission in MCPTT p. 140
6.21.1 Description p. 140
6.21.2 Call connect and disconnect over MBS session procedures p. 140
6.22 Solution 22: Use of MBS transmission in MCVideo p. 143
6.22.1 Description p. 143
6.22.2 Call connect and disconnect over MBS session procedures p. 143
6.23 Solution 23: UE multicast MBS session leave aspects p. 147
6.23.1 Description p. 147
6.23.1.1 Procedure p. 147
6.23.2 Impacts on existing nodes and functionality p. 148
6.23.3 Solution evaluation p. 148
6.24 Solution 24: 5G MBS session release aspects p. 148
6.24.1 Description p. 148
6.24.1.1 Procedure p. 148
6.24.2 Impacts on existing nodes and functionality p. 149
6.24.3 Solution evaluation p. 149
6.25 Solution 25: 5G MBS session update for group communication p. 150
6.25.1 Description p. 150
6.25.1.1 Procedure p. 150
6.25.2 Impacts on existing nodes and functionality p. 152
6.25.3 Solution evaluation p. 152
6.26 Solution 26: MC service support over 5G ProSe p. 152
6.26.1 Description p. 152
6.26.2 Impacts on existing nodes and functionality p. 155
6.26.3 Solution evaluation p. 155
6.27 Solution 27: Use of predefined 5QIs p. 155
6.27.1 Description p. 155
6.27.2 Solution to extend MCData 5QI use71 p. 155
6.27.3 Solution evaluation p. 155
6.28 Solution 28: MBS service de-announcement p. 156
6.28.1 Description p. 156
6.28.1.1 Procedure p. 156
6.28.2 Impacts on existing nodes and functionality p. 157
6.28.3 Solution evaluation p. 157
6.29 Solution 29: Use of broadcast and multicast MBS sessions in MCPTT p. 157
6.29.1 Description p. 157
6.29.2 Call connect over MBS session p. 157
6.29.3 Call disconnect over MBS session p. 159
6.29.4 Impacts on existing nodes and functionality p. 160
6.29.5 Solution evaluation p. 160
6.30 Solution 30: Use of broadcast and multicast MBS sessions in MCVideo p. 160
6.30.1 Description p. 160
6.30.2 Video call connect over MBS session p. 161
6.30.3 Video call disconnect over MBS session p. 163
6.30.4 Impacts on existing nodes and functionality p. 164
6.30.5 Solution evaluation p. 164
6.31 Solution 31: Multicast MBS session activation and deactivation aspects for group communications p. 164
6.31.1 Description p. 164
6.31.1.1 Multicast MBS session activation procedure p. 164
6.31.1.2 Multicast MBS session deactivation procedure p. 165
6.31.2 Impacts on existing nodes and functionality p. 166
6.31.3 Solution evaluation p. 167
6.32 Solution 32: Inter-system mobility between LTE and 5G p. 167
6.32.1 Description p. 167
6.32.1.1 Inter-system mobility from 5G MBS session to LTE eMBMS bearer p. 167
6.32.1.2 Inter-system mobility from 5G MBS session to LTE unicast bearer p. 169
6.32.1.3 Inter-system mobility from LTE eMBMS to 5G MBS session p. 171
6.32.1.4 Inter-system mobility from LTE eMBMS to 5G unicast PDU session p. 172
6.32.2 Impacts on existing nodes and functionality p. 173
6.32.3 Solution evaluation p. 174
6.33 Solution 33: Service continuity for broadcast and multicast MBS sessions p. 174
6.33.1 Description p. 174
6.33.1.1 Service continuity from broadcast and multicast MBS sessions to unicast PDU session p. 174
6.33.1.2 Service continuity from unicast PDU session to broadcast and multicast MBS session p. 175
6.33.2 Impacts on existing nodes and functionality p. 177
6.33.3 Solution evaluation p. 177
6.34 Solution 34: Providing stored files in the MCData content server for distribution over 5G MBS p. 177
6.34.1 Description p. 177
6.34.1.1 Use of pre-created MBS user services p. 177
6.34.1.1.1 General p. 177
6.34.1.1.2 Procedure p. 177
6.34.1.2 Use of dynamic MBS user service establishment p. 179
6.34.1.3 Providing stored files in the MCData content server for distribution over MBS p. 180
6.34.2 Impacts on existing nodes and functionality p. 183
6.34.3 Solution evaluation p. 183
6.x.1 Description p. 183
6.x.2 Impacts on existing nodes and functionality p. 183
6.x.3 Solution evaluation p. 183
7 Overall evaluation p. 183
8 Conclusions p. 187
8.1 Key issues #2, 5, 6 and 8: Unicast communication p. 187
8.2 Key issue #13: MC services over 5G MBS p. 188
8.2.1 General p. 188
8.2.2 Comprehensive conclusion p. 188
8.2.3 Conclusions based on sub-key issues p. 189
8.3 Key issue#14: MC service over 5G ProSe p. 190
A Copy of TS 23.280 with highlighted E-UTRAN/EPS specific terminology and references p. 191
B Copy of TS 23.379 with highlighted E-UTRAN/EPS specific terminology and references p. 191
C Copy of TS 23.281 with highlighted E-UTRAN/EPS specific terminology and references p. 191
D Copy of TS 23.282 with highlighted E-UTRAN/EPS specific terminology and references p. 192
E Copy of TS 23.283 with highlighted E-UTRAN/EPS specific terminology and references p. 192
$ Change history p. 193
