Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 23.700-47  Word version:  18.0.0

Top   Top   Up   Prev   None
1…   5…

 

5  Key Issuesp. 13

6  Solutionsp. 15

6.0  Mapping of Solutions to Key Issuesp. 15

6.1  Solution #1: Procedures for RRC Inactive MBS data receptionp. 16

6.2  Solution #2: Procedures for MOCN network sharingp. 22

6.3  Solution #3: AF providing assistance informationp. 26

6.4  Solution #4: MBS session management for RRC Inactive MBS data receiving UEp. 27

6.5  Solution #5: Mobility Procedures for UE supporting RRC Inactive MBS data receptionp. 29

6.6  Solution #6: Reusing the existing assistance info and Qos for RRC Inactive MBS data reception decisionp. 32

6.7  Solution #7: MOCN RAN Sharingp. 33

6.8  Solution #8: Allocating and using MOCN TMGIp. 38

6.9  Solution #9: Broadcast services considering MOCN RANp. 41

6.10  Solution #10: AF triggered MBS session managementp. 44

6.11  Solution #11: Solution on enabling the on-demand multicast MBS session managementp. 50

6.12  Solution #12: Group Message Deliveryp. 52

6.13  Solution #13: Group message delivery for broadcastp. 57

6.14  Solution #14: MBS coexistence with power saving mechanisms of 5GSp. 60

6.15  Solution #15: Solution for coexistence of MBS delivery and power saving mechanismsp. 62

6.16  Solution #16: Public Safety services offered over both Broadcast and Multicast transportp. 63

6.17  Solution #17: Performance Improvements for Public Safetyp. 68

6.18  Solution #18: MBS session management for RRC Inactive MBS data receiving UEp. 75

6.19  Solution #19: Procedures for Transmission mode tor inactive data receptionp. 77

6.20  Solution #20: Registration procedure enhancements for multicast receptionp. 82

6.21  Solution #21: Mobility Procedures for UE supporting RRC Inactive MBS data reception with the MBS session containerp. 84

6.22  Solution #22: Session management for RRC Inactive MBS data receiving UEp. 85

6.23  Solution #23: MBS session activation for RRC Inactive MBS data receiving UEp. 86

6.24  Solution #24: Solution based on configuration in RAN to support MOCN RAN Sharingp. 89

6.25  Solution #25: Triggering capability limited devices to receive MBS datap. 92

6.26  Solution #26: AF selects UEs to be kept in connected modep. 95

6.27  Solution #27: AF providing list of prioritized UEs when creating multicast MBS Sessionp. 97

6.28  Solution #28: Session management and Mobility for RRC Inactive MBS data receptionp. 100

6.29  Solution #29: MOCN network sharing with a single TMGIp. 103

6.30  Solution #30: On demand multicast MBS session set up by MB-SMFp. 107

6.31  Solution #31: Multicast access control for high number of public safety UEsp. 113

7  Evaluationp. 114

8  Conclusionsp. 130

A  Public Safety use cases of large number of UEs in a single cellp. 134

$  Change historyp. 135


Up   Top