Content for TR 23.792 Word version: 16.0.0
5 Key issues and gaps
6 Use cases
7 Solutions
8 Evaluations
9 Conclusions
A Analysis of capabilities provided by the MBMS user service architecture
$ Change History
5 Key issues and gaps p. 10
5.1 Announcement handling p. 10
5.2 ROHC and FEC handling p. 10
5.3 Feedback on MBMS reception p. 10
5.4 API for file distribution over MBMS p. 11
5.5 Registration p. 11
5.6 MBMS bearer quality monitoring p. 11
5.7 Location information p. 11
6 Use cases p. 11
6.0 General p. 11
6.1 MBMS bearer quality monitoring and data reception p. 12
6.1.1 General description p. 12
6.1.2 Typical flows p. 12
6.2 Location information p. 13
6.2.1 General description p. 13
6.2.2 Typical flows p. 13
6.3 Switching from MBMS delivery to unicast delivery p. 13
6.3.1 General description p. 13
6.3.2 Typical flows p. 14
6.4 MBMS bearer suspension and resumption p. 14
6.4.1 General description p. 14
6.4.2 Typical flows p. 14
6.5 Using the MBMS user services for MCData file distribution p. 15
7 Solutions p. 18
7.1 Registration and deregistration API p. 18
7.1.1 General p. 18
7.1.2 Procedures p. 18
7.1.3 Information flows p. 19
7.1.3.1 Application registration request p. 19
7.1.3.2 Application registration response p. 19
7.1.3.3 Application deregistration request p. 20
7.1.4 Evaluation p. 20
7.2 MBMS bearer registration and notification API p. 20
7.2.1 General p. 20
7.2.2 Procedures p. 20
7.2.2.1 MC MBMS bearer registration p. 20
7.2.2.2 MC MBMS bearer deregistration p. 21
7.2.2.3 MC MBMS bearer availability p. 22
7.2.2.4 MC MBMS bearer unavailability p. 23
7.2.2.5 MC MBMS bearer quality evaluation p. 23
7.2.3 Information flows p. 24
7.2.3.1 MC MBMS bearer registration request p. 24
7.2.3.2 MC MBMS bearer registration response p. 24
7.2.3.3 MC MBMS bearer deregistration request p. 25
7.2.3.4 MC MBMS bearer deregistration response p. 25
7.2.3.5 MC MBMS bearer event notification p. 25
7.2.4 Evaluation p. 25
7.3 API for media reception p. 25
7.3.1 General p. 25
7.3.2 Procedures p. 26
7.3.2.1 Open media p. 26
7.3.2.2 Close media p. 27
7.3.3 Information flows p. 27
7.3.3.1 Open media request p. 27
7.3.3.2 Open media response p. 28
7.3.3.3 Close media request p. 28
7.3.3.4 Close media response p. 28
7.3.4 Evaluation p. 28
7.4 Location information API p. 29
7.4.1 General p. 29
7.4.2 Procedures p. 29
7.4.2.1 Get SAI p. 29
7.4.2.2 SAI update notification p. 29
7.4.2.3 Get cell ID p. 30
7.4.2.4 Cell ID update notification p. 30
7.4.3 Information flows p. 31
7.4.3.1 Get SAI response p. 31
7.4.3.2 SAI update notification p. 31
7.4.3.3 Get cell ID response p. 31
7.4.3.4 Cell ID update notification p. 32
7.4.4 Evaluation p. 32
7.5 MBMS API for MCData file distribution p. 32
7.5.1 General p. 32
7.5.2 Application registration and deregistration p. 32
7.5.3 File reception p. 33
7.5.4 Evaluation p. 33
8 Evaluations p. 33
9 Conclusions p. 34
A Analysis of capabilities provided by the MBMS user service architecture p. 34
A.1 General p. 34
A.2 Announcement / User service discovery p. 35
A.3 MBMS delivery methods p. 35
A.3.1 MBMS streaming delivery method p. 35
A.3.2 MBMS download delivery method p. 36
A.3.3 Transparent mode (transport only) p. 36
A.4 xMB API p. 37
A.5 MBMS API p. 37
A.6 GCSE architecture p. 38
A.7 Gap analysis p. 38
A.7.1 xMB p. 38
A.7.1.1 Usage of pre-established bearer p. 38
A.7.1.2 Geographical area p. 38
A.7.1.3 QoS p. 38
A.7.1.4 Header compression p. 38
A.7.1.5 FEC p. 38
A.7.1.6 MCData file distribution p. 38
A.7.2 MBMS API p. 39
A.7.2.1 Service identity p. 39
A.7.2.2 MBMS quality detection p. 39
A.7.2.3 Header decompression p. 39
A.7.2.4 FEC p. 39
A.7.2.5 Announcement p. 39
A.7.2.6 Location reporting p. 39
$ Change History p. 40
