Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 23.700-47
Word version: 18.0.0
1…
5…
5
Key Issues
6
Solutions
7
Evaluation
8
Conclusions
A
Public Safety use cases of large number of UEs in a single cell
$
Change history
5
Key Issues
p. 13
5.1
Key Issue #1: Multicast MBS data reception in RRC Inactive state
p. 13
5.1.1
Description
p. 13
5.2
Key Issue #2: 5MBS MOCN Network Sharing
p. 13
5.2.1
Description
p. 13
5.3
Key Issue #3: On demand multicast MBS session
p. 13
5.3.1
Description
p. 13
5.4
Key Issue #4: Group message delivery
p. 14
5.4.1
Description
p. 14
5.5
Key Issue #5: Coexistence with existing power saving mechanisms for capability-limited devices
p. 14
5.5.1
Description
p. 14
5.6
Key Issue #6: Improvement for potential performance issues related to high numbers of public safety UEs
p. 15
5.6.1
Description
p. 15
6
Solutions
p. 15
6.0
Mapping of Solutions to Key Issues
p. 15
6.1
Solution #1: Procedures for RRC Inactive MBS data reception
p. 16
6.1.1
Introduction
p. 16
6.1.2
Functional description
p. 16
6.1.3
Procedures
p. 18
6.1.3.1
General
p. 18
6.1.3.2
MBS session creation, multicast session join and session establishment procedure
p. 19
6.1.3.3
Moving a UE to RRC Inactive state
p. 20
6.1.3.4
Moving a UE to RRC-CONNECTED from RRC Inactive state
p. 21
6.1.4
Impacts on services, entities and interfaces.
p. 21
6.2
Solution #2: Procedures for MOCN network sharing
p. 22
6.2.1
Introduction
p. 22
6.2.2
Functional description
p. 22
6.2.2.1
General
p. 22
6.2.2.2
Identifier of the broadcast MBS service
p. 23
6.2.2.3
Reception of the broadcast data by the UE
p. 23
6.2.3
Procedures
p. 24
6.2.3.1
General
p. 24
6.2.3.2
Broadcast Session Establishment
p. 24
6.2.3.3
Broadcast Session Release
p. 25
6.2.4
Impacts on services, entities and interfaces
p. 25
6.3
Solution #3: AF providing assistance information
p. 26
6.3.1
Introduction
p. 26
6.3.2
Functional description
p. 26
6.3.3
Procedures
p. 26
6.3.4
Impacts on services, entities and interfaces.
p. 27
6.4
Solution #4: MBS session management for RRC Inactive MBS data receiving UE
p. 27
6.4.1
Introduction
p. 27
6.4.2
Functional description
p. 27
6.4.3
Procedures
p. 28
6.4.4
Impacts on services, entities, and interfaces
p. 29
6.5
Solution #5: Mobility Procedures for UE supporting RRC Inactive MBS data reception
p. 29
6.5.1
Introduction
p. 29
6.5.2
Functional description
p. 29
6.5.3
Procedures
p. 30
6.5.3.1
RRC-inactive multicast group member moves within RNA
p. 30
6.5.3.2
RRC-inactive multicast group member UE move out of RNA and within RA
p. 30
6.5.3.3
RRC-connected multicast group member UE move to RRC-inactive MBS reception supporting NG-RAN
p. 31
6.5.4
Impacts on services, entities, and interfaces
p. 31
6.6
Solution #6: Reusing the existing assistance info and Qos for RRC Inactive MBS data reception decision
p. 32
6.6.1
Introduction
p. 32
6.6.2
Functional description
p. 32
6.6.3
Procedures
p. 33
6.6.4
Impacts on services, entities and interfaces.
p. 33
6.7
Solution #7: MOCN RAN Sharing
p. 33
6.7.1
Introduction
p. 33
6.7.2
Functional description
p. 33
6.7.3
Procedures
p. 33
6.7.3.1
General
p. 33
6.7.3.2
MBS Session Creation
p. 34
6.7.3.3
MBS Session Start for Broadcast
p. 35
6.7.3.4
MBS Session Release for Broadcast
p. 36
6.7.3.5
Broadcast MBS Session Transport Request
p. 36
6.7.4
Impacts on services, entities and interfaces
p. 37
6.8
Solution #8: Allocating and using MOCN TMGI
p. 38
6.8.1
Introduction
p. 38
6.8.2
Functional description
p. 38
6.8.3
Procedures
p. 39
6.8.3.1
Procedure for Broadcast using MOCN TMGI
p. 39
6.8.4
Impacts on services, entities and interfaces
p. 41
6.9
Solution #9: Broadcast services considering MOCN RAN
p. 41
6.9.1
Introduction
p. 41
6.9.2
Functional description
p. 41
6.9.3
Procedures
p. 41
6.9.3.1
General
p. 41
6.9.3.2
Broadcast Session Start procedure
p. 42
6.9.3.3
Broadcast Session update and release procedure
p. 43
6.9.4
Impacts on services, entities and interfaces
p. 44
6.10
Solution #10: AF triggered MBS session management
p. 44
6.10.1
Introduction
p. 44
6.10.2
Functional description
p. 44
6.10.3
Procedures
p. 45
6.10.3.1
General
p. 45
6.10.3.2
AF triggered MBS Session management procedures with PCC
p. 46
6.10.3.3
AF triggered MBS Session management procedures without PCC
p. 48
6.10.4
Impacts on services, entities and interfaces.
p. 49
6.11
Solution #11: Solution on enabling the on-demand multicast MBS session management
p. 50
6.11.1
Introduction
p. 50
6.11.2
Functional description
p. 50
6.11.2.1
Use cases
p. 50
6.11.3
Procedures
p. 51
6.11.3.1
on-demand multicast MBS session management
p. 51
6.11.4
Impacts on services, entities and interfaces.
p. 52
6.12
Solution #12: Group Message Delivery
p. 52
6.12.1
Introduction
p. 52
6.12.2
Functional description
p. 52
6.12.3
Procedures
p. 52
6.12.3.1
General
p. 52
6.12.3.2
Group Message Delivery via MBS Broadcast
p. 53
6.12.3.3
Modification of previously submitted Group message
p. 55
6.12.4
Impacts on services, entities and interfaces
p. 56
6.13
Solution #13: Group message delivery for broadcast
p. 57
6.13.1
Introduction
p. 57
6.13.2
Functional description
p. 57
6.13.3
Procedures
p. 57
6.13.3.1
General
p. 57
6.13.3.2
Broadcast Session Establishment
p. 58
6.13.3.3
Modification of previously submitted group message
p. 59
6.13.4
Impacts on services, entities and interfaces
p. 60
6.14
Solution #14: MBS coexistence with power saving mechanisms of 5GS
p. 60
6.14.1
Introduction
p. 60
6.14.2
Functional description
p. 60
6.14.3
Procedures
p. 61
6.14.4
Impacts on services, entities and interfaces.
p. 62
6.15
Solution #15: Solution for coexistence of MBS delivery and power saving mechanisms
p. 62
6.15.1
Functional description
p. 62
6.15.2
Procedures
p. 63
6.15.3
Impacts Analysis
p. 63
6.16
Solution #16: Public Safety services offered over both Broadcast and Multicast transport
p. 63
6.16.1
Description
p. 63
6.16.1.1
General
p. 63
6.16.1.2
Functional description
p. 64
6.16.2
Procedures
p. 65
6.16.2.1
GCS AS configuration of both Broadcast and Multicast Services
p. 65
6.16.2.2
UE switching from Broadcast Reception to Multicast Reception
p. 66
6.16.2.3
UE switching from Multicast Reception to Broadcast Reception (UE based)
p. 66
6.16.2.3b
UE switching from Multicast Reception to Broadcast Reception (NG-RAN based)
p. 66
6.16.3
Impacts on services, entities and interfaces.
p. 67
6.17
Solution #17: Performance Improvements for Public Safety
p. 68
6.17.1
Introduction
p. 68
6.17.2
Functional description
p. 68
6.17.3
Procedures
p. 69
6.17.3.1
General
p. 69
6.17.3.2
UE join multicast MBS session
p. 70
6.17.3.3
UE leave multicast MBS session
p. 71
6.17.3.4
Multicast session leave requested by the network or MBS session release
p. 72
6.17.3.5
MBS Session Activation
p. 73
6.17.3.6
N2 based Handover and IDLE Mobility
p. 74
6.17.4
Impacts on services, entities and interfaces.
p. 74
6.18
Solution #18: MBS session management for RRC Inactive MBS data receiving UE
p. 75
6.18.1
Introduction
p. 75
6.18.2
Functional description
p. 75
6.18.3
Procedures
p. 76
6.18.4
Impacts on services, entities, and interfaces
p. 77
6.19
Solution #19: Procedures for Transmission mode tor inactive data reception
p. 77
6.19.1
Introduction
p. 77
6.19.2
Functional description
p. 77
6.19.3
Procedures
p. 78
6.19.3.1
Moving a UE to RRC Inactive state and providing assistance information to additional RAN nodes (Option A)
p. 78
6.19.3.2
MBS service activation
p. 79
6.19.3.3
Triggering MBS service announcement by MB-SMF (Option B)
p. 80
6.19.3.4
MBS session release (Option A and B)
p. 81
6.19.4
Impacts on services, entities and interfaces.
p. 81
6.20
Solution #20: Registration procedure enhancements for multicast reception
p. 82
6.20.1
Introduction
p. 82
6.20.2
Functional description
p. 82
6.20.3
Procedures
p. 82
6.20.3.1
Registration procedures
p. 82
6.20.4
Impacts on services, entities and interfaces
p. 83
6.21
Solution #21: Mobility Procedures for UE supporting RRC Inactive MBS data reception with the MBS session container
p. 84
6.21.1
Introduction
p. 84
6.21.2
Functional description
p. 84
6.21.3
Procedures
p. 84
6.21.3.1
RRC-inactive multicast group member UE move out of RNA and within RA
p. 84
6.21.4
Impacts on services, entities, and interfaces
p. 84
6.22
Solution #22: Session management for RRC Inactive MBS data receiving UE
p. 85
6.22.1
Introduction
p. 85
6.22.2
Functional description
p. 85
6.22.3
Procedures
p. 85
6.22.3.1
Modification to the MBS session de-activation procedure
p. 85
6.22.3.2
Modification to the MBS session (re-)activation procedure
p. 86
6.22.4
Impacts on services, entities, and interfaces
p. 86
6.23
Solution #23: MBS session activation for RRC Inactive MBS data receiving UE
p. 86
6.23.1
Introduction
p. 86
6.23.2
Functional description
p. 87
6.23.3
Procedures
p. 88
6.23.4
Impacts on services, entities, and interfaces
p. 89
6.24
Solution #24: Solution based on configuration in RAN to support MOCN RAN Sharing
p. 89
6.24.1
Introduction
p. 89
6.24.2
Functional description
p. 89
6.24.3
Procedures
p. 89
6.24.3.1
General
p. 89
6.24.3.2
MBS Session Creation
p. 89
6.24.3.3
MBS Session Start for Broadcast
p. 90
6.24.3.4
MBS Session Release for Broadcast
p. 91
6.24.4
Impacts on services, entities and interfaces.
p. 91
6.25
Solution #25: Triggering capability limited devices to receive MBS data
p. 92
6.25.1
Introduction
p. 92
6.25.2
Description
p. 92
6.25.3
Procedures
p. 93
6.25.3.1
Periodic or one time transmission of MBS data to capability-limited devices
p. 93
6.25.3.2
Deferred activation for aperiodic transmission of MBS data to capability-limited devices
p. 94
6.25.4
Impacts on services, entities and interfaces.
p. 94
6.26
Solution #26: AF selects UEs to be kept in connected mode
p. 95
6.26.1
Introduction
p. 95
6.26.2
Description
p. 95
6.26.3
Procedures
p. 96
6.26.4
Impacts on services, entities and interfaces.
p. 96
6.27
Solution #27: AF providing list of prioritized UEs when creating multicast MBS Session
p. 97
6.27.1
Introduction
p. 97
6.27.2
Functional description
p. 97
6.27.3
Procedures
p. 98
6.27.4
Impacts on services, entities and interfaces.
p. 99
6.28
Solution #28: Session management and Mobility for RRC Inactive MBS data reception
p. 100
6.28.1
Introduction
p. 100
6.28.2
Functional description
p. 100
6.28.3
Procedures
p. 101
6.28.3.1
Moving the UE to RRC Inactive mode
p. 101
6.28.3.2
Mobility within/out of RNA area.
p. 101
6.28.4
Impacts on services, entities, and interfaces
p. 103
6.29
Solution #29: MOCN network sharing with a single TMGI
p. 103
6.29.1
Introduction
p. 103
6.29.2
Description
p. 104
6.29.3
Procedures
p. 104
6.29.4
Impacts on services, entities and interfaces
p. 106
6.30
Solution #30: On demand multicast MBS session set up by MB-SMF
p. 107
6.30.1
Introduction
p. 107
6.30.2
Description
p. 108
6.30.3
Procedures
p. 110
6.30.4
Impacts on services, entities and interfaces.
p. 112
6.31
Solution #31: Multicast access control for high number of public safety UEs
p. 113
6.31.1
Introduction
p. 113
6.31.2
Functional description
p. 113
6.31.3
Procedures
p. 113
6.31.4
Impacts on services, entities, and interfaces
p. 114
7
Evaluation
p. 114
7.1
Key Issue #1: MBS session reception in RRC Inactive
p. 114
7.1.1
Overview over available solutions
p. 114
7.1.2
Assistance Information
p. 117
7.1.3
Activation of MBS multicast session
p. 119
7.1.4
Mobility for RRC_Inactive UEs receiving MBS data
p. 120
7.2
Key Issue #2: 5MBS MOCN RAN Sharing
p. 121
7.3
Key Issue #3: On demand multicast MBS session
p. 125
7.4
Key Issue #4: Group message delivery
p. 126
7.5
Key Issue #5: Coexistence with existing power saving mechanisms for capability-limited devices
p. 126
7.6
Key Issue #6: Improvement for potential performance issues related to high numbers of public safety UEs
p. 128
8
Conclusions
p. 130
8.1
Key Issue #1: MBS session reception in RRC Inactive
p. 130
8.1.1
Conclusions
p. 130
8.2
Key Issue #2: MOCN network sharing
p. 131
8.3
Key Issue #3: On demand multicast MBS session
p. 132
8.4
Key Issue #4: Group message delivery
p. 132
8.5
Key Issue #5: Coexistence with existing power saving mechanisms for capability-limited devices
p. 132
8.6
Key Issue #6: Improvement for potential performance issues related to high numbers of public safety UEs
p. 132
A
Public Safety use cases of large number of UEs in a single cell
p. 134
$
Change history
p. 135