B.2 Data transfer when an uplink feedback channel is established
3GPP43.246Multimedia Broadcast/Multicast Service (MBMS) in the GERANRelease 17Stage 2TS
B.2.1 PBCCH not deployed, transmission with frequency hopping
Figure B.4
In this configuration, it is assumed that the BCCH and the CCCH are located on timeslot 0 (with no additional timeslots assigned to CCCH). As shown in Figure B.4, the mobile station is able to transmit also when the BCCH or the CCCH need to be read, if one or more MBMS sessions are received on up to 3 timeslots.
NOTE 1: If in a frame the MS needs to read the BCCH or CCCH and transmit on the uplink, the MS will need to perform three switchings within that frame.
NOTE 2: After receving a (pre-)notification for a new session while listening to an ongoing session, the mobile station enters non-DRX mode and listens to all the paging blocks on the CCCH to receive a(n) (notification)assignment. As the time elapsing until the assignment received on the mobile station side (see subclauses 6.1.1.2, 6.1.1.3, 6.1.1.4) could last for a considerable length of time (up to the value of T3214, which is equal to 60 seconds, see 3GPP TS 44.018 and 3GPP TS 44.060), the worst case is in those frames where the mobile station is required to: read 1 timeslot for BCCH or CCCH, use 1 timeslot for switching from the reception of BCCH/CCCH to the reception of MBMS, read 3 timeslots for MBMS and transmit on 1 timeslot to send feedback. In this scenario the sum of RX and TX is equal to 6; this leaves only 2 timeslots for switching. As the mobile station needs to be able to perform neighbour cell measurements during these periods, it follows that Ttb = 1 and Tra = 1.
B.2.2 PBCCH not deployed, transmission without frequency hopping
Figure B.5
In this scenario, the maximum number of timeslots that one or more MBMS sessions can be received upon is 4. This assumes that both the BCCH and the CCCH are located on timeslot 0.
NOTE: After receving a (pre-)notification for a new session while listening to an ongoing session, the mobile station enters non-DRX mode and listens to all the paging blocks on the CCCH to receive a(n) (notification)assignment. As the time elapsing until the assignment received on the mobile station side (see subclauses 6.1.1.2, 6.1.1.3, 6.1.1.4) could last for a considerable length of time (up to the value of T3214, which is equal to 60 seconds, see 3GPP TS 44.018 and 3GPP TS 44.060), the worst case is in those frames where the mobile station is required to: read 1 timeslot for BCCH or CCCH, read 4 timeslots for MBMS and transmit on 1 timeslot to send feedback. In this scenario the sum of RX and TX is equal to 6; this leaves only 2 timeslots for switching. As the mobile station needs to be able to perform neighbour cell measurements during these periods, it follows that Ttb = 1 and Tra = 1.
B.2.3 PBCCH deployed, transmission with frequency hopping
Figure B.6
Figure B.6 shows that in this scenario the maximum number of timeslots that one or more MBMS sessions can be received upon is 4.
It is assumed that the PBCCH and the PCCCH are located on a single timeslot. If the PCCCH is transmitted on more than one timeslot, then the number of timeslots that one or more MBMS sessions can be received upon is reduced accordingly.
NOTE 1: As paging coordination is mandatory in the network for MBMS, the mobile station does not need to read the BCCH and the CCCH.
NOTE 2: After receving a (pre-)notification for a new session while listening to an ongoing session, the mobile station enters non-DRX mode and listens to all the paging blocks on the PCCCH to receive a(n) (notification)assignment. As the time elapsing until the assignment received on the mobile station side (see subclauses 6.1.1.2, 6.1.1.3, 6.1.1.4) could last for a considerable length of time (up to the value of T3214, which is equal to 60 seconds, see 3GPP TS 44.060), the worst case is in those frames where the mobile station is required to: read 1 timeslot for PBCCH or PCCCH, read 4 timeslots for MBMS and transmit on 1 timeslot to send feedback. In this scenario the sum of RX and TX is equal to 6; this leaves only 2 timeslots for switching. As the mobile station needs to be able to perform neighbour cell measurements during these periods, it follows that Ttb = 1 and Tra = 1.
It is also assumed that both the PBCCH and the MBMS traffic channels use frequency hopping, that the hopping pattern is the same and that, in every frame, the PBCCH and the MBMS traffic channels are transmitted on the same frequency. If the hopping pattern is not the same, the maximum number of timeslots that multiple MBMS sessions can be received upon is reduced to 3.
NOTE 3: If the hopping pattern is not the same and in a frame the MS needs to read the PBCCH or PCCCH and transmit on the uplink, the MS will need to perform three switchings within that frame.
Annex C (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
2004-08 |
GP-21 |
GP-042241 |
Approved for Release 6 |
6.0.0 |
|||
|
2004-11 |
GP-22 |
GP-042782 |
001 |
1 |
MBMS cell reselection |
6.0.0 |
6.1.0 |
|
2004-11 |
GP-22 |
GP-042800 |
002 |
1 |
Definition of MPRACH |
6.0.0 |
6.1.0 |
|
2004-11 |
GP-22 |
GP-042778 |
003 |
1 |
Clarification on RLC protocol behaviour |
6.0.0 |
6.1.0 |
|
2004-11 |
GP-22 |
GP-042801 |
004 |
2 |
Editorial corrections |
6.0.0 |
6.1.0 |
|
2004-11 |
GP-22 |
GP-042908 |
007 |
3 |
Suspension & Resumption of the reception of an MBMS session |
6.0.0 |
6.1.0 |
|
2004-11 |
GP-22 |
GP-042566 |
008 |
Addition of flexible reconfiguration for MBMS_BEARER_ID and MS_ID |
6.0.0 |
6.1.0 |
|
|
2004-11 |
GP-22 |
GP-042678 |
009 |
1 |
Addition of reception of multiple sessions |
6.0.0 |
6.1.0 |
|
2004-11 |
GP-22 |
GP-042679 |
010 |
1 |
Addition of the cause indication whereby an MBMS p-t-m bearer is not established in a cell inside the MBMS ASSIGNMENT message |
6.0.0 |
6.1.0 |
|
2004-11 |
GP-22 |
GP-042805 |
011 |
1 |
Prioritzing MBMS Neighbouring Cell Information |
6.0.0 |
6.1.0 |
|
2004-11 |
GP-22 |
GP-042807 |
012 |
1 |
Introduction of prenotification |
6.0.0 |
6.1.0 |
|
2004-11 |
GP-22 |
GP-042681 |
013 |
1 |
Modifications to description of MBMS Channels |
6.0.0 |
6.1.0 |
|
2004-11 |
GP-22 |
GP-042898 |
014 |
3 |
Use of the MBMS NEIGHBOURING CELL INFORMATION message |
6.0.0 |
6.1.0 |
|
2004-11 |
GP-22 |
GP-042896 |
015 |
2 |
MBMS notification for MS in packet transfer mode |
6.0.0 |
6.1.0 |
|
2004-11 |
GP-22 |
GP-042897 |
016 |
2 |
MBMS notification for MS in dedicated mode |
6.0.0 |
6.1.0 |
|
2005-01 |
GP-23 |
GP-050309 |
019 |
Repeated notifications of an ongoing session |
6.1.0 |
6.2.0 |
|
|
2005-01 |
GP-23 |
GP-050310 |
020 |
Definition of when MBMS ASSIGNMENT is a distribution or non-distribution message |
6.1.0 |
6.2.0 |
|
|
2005-01 |
GP-23 |
GP-050438 |
021 |
1 |
Update of sub-clause 6.1.1.3 |
6.1.0 |
6.2.0 |
|
2005-01 |
GP-23 |
GP-050439 |
022 |
1 |
Access limitation definitions |
6.1.0 |
6.2.0 |
|
2005-01 |
GP-23 |
GP-050369 |
023 |
Deletion of MS ID |
6.1.0 |
6.2.0 |
|
|
2005-01 |
GP-23 |
GP-050598 |
024 |
2 |
Clean-up to the MBMS stage 2 |
6.1.0 |
6.2.0 |
|
2005-01 |
GP-23 |
GP-050564 |
025 |
Corrections related to cell reselection |
6.1.0 |
6.2.0 |
|
|
2005-04 |
GP-24 |
GP-050985 |
026 |
1 |
Clarification of usage of ARQ and block repetition |
6.2.0 |
6.3.0 |
|
2005-04 |
GP-24 |
GP-050634 |
027 |
Removal of multiple MBMS radio bearers per MBMS service per cell |
6.2.0 |
6.3.0 |
|
|
2005-04 |
GP-24 |
GP-050988 |
028 |
1 |
Align Resource Management Procedure with Stage 3 |
6.2.0 |
6.3.0 |
|
2005-04 |
GP-24 |
GP-050891 |
029 |
Clarification of PACKET POLLING REQUEST message in MBMS broadcast/multicast mode |
6.2.0 |
6.3.0 |
|
|
2005-04 |
GP-24 |
GP-051128 |
030 |
2 |
MBMS notification for MSs in dedicated mode |
6.2.0 |
6.3.0 |
|
2005-06 |
GP-25 |
GP-051359 |
031 |
Clarification to counting requirement for higher priority MBMS sessions during multiple sessions |
6.3.0 |
6.4.0 |
|
|
2005-06 |
GP-25 |
GP-051677 |
032 |
1 |
Clarification of the session duration timer |
6.3.0 |
6.4.0 |
|
2005-06 |
GP-25 |
GP-051493 |
033 |
Corrections to Annex B |
6.3.0 |
6.4.0 |
|
|
2005-09 |
GP-26 |
GP-052235 |
0034 |
2 |
Introduction of MBMS DOWNLINK ACK/NACK message |
6.4.0 |
6.5.0 |
|
2005-09 |
GP-26 |
GP-052232 |
0035 |
1 |
Introduction of ARP for MBMS |
6.4.0 |
6.5.0 |
|
2005-11 |
GP-27 |
GP-052461 |
0036 |
Correction to MBMS notification for mobile stations in DTM or MAC-DTM state |
6.5.0 |
6.6.0 |
|
|
2005-11 |
GP-27 |
GP-052462 |
0037 |
Correction to passive mode |
6.5.0 |
6.6.0 |
|
|
2005-11 |
GP-27 |
GP-052878 |
0038 |
3 |
MBMS Transfer Mode |
6.5.0 |
6.6.0 |
|
2006-04 |
GP-29 |
GP-060710 |
0040 |
Correction to reconfiguration for an MBMS radio bearer |
6.6.0 |
6.7.0 |
|
|
2006-04 |
GP-29 |
GP-060858 |
0043 |
1 |
Clarification for T3195 |
6.6.0 |
6.7.0 |
|
2006-04 |
GP-29 |
GP-060777 |
0039 |
2 |
MBMS cell reselection enhancement |
6.7.0 |
7.0.0 |
|
2006-06 |
GP-30 |
GP-061337 |
0045 |
1 |
Correction to MS_ID release procedure |
7.0.0 |
7.1.0 |
|
2006-09 |
GP-31 |
GP-061864 |
0047 |
2 |
Differentiation of the MBMS multislot capability requirements |
7.1.0 |
7.2.0 |
|
2006-09 |
GP-31 |
GP-061762 |
0049 |
1 |
Correction to the MBMS assignment on the CCCH |
7.1.0 |
7.2.0 |
|
2006-11 |
GP-32 |
GP-062099 |
0050 |
Introduction of the MBMS Session Update procedure |
7.2.0 |
7.3.0 |
|
|
2006-11 |
GP-32 |
GP-062412 |
0052 |
2 |
Introduction of NPM Transfer Time |
7.2.0 |
7.3.0 |
|
2008-12 |
GP-40 |
Version for Release 8 |
7.3.0 |
8.0.0 |
|||
|
2009-12 |
GP-44 |
Version for Release 9 |
8.0.0 |
9.0.0 |
|||
|
2011-03 |
GP-49 |
Version for Release 10 |
9.0.0 |
10.0.0 |
|||
|
2012-09 |
GP-55 |
Version for Release 11 |
10.0.0 |
11.0.0 |
|||
|
2014-09 |
GP-63 |
Version for Release 12 (frozen at SP-65) |
11.0.0 |
12.0.0 |
|||
|
2015-12 |
GP-68 |
Version for Release 13 (frozen at SP-70) |
12.0.0 |
13.0.0 |
|||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
RP-75 |
Release 14 version (frozen at TSG-75) |
14.0.0 |
||||
|
2018-06 |
RP-80 |
Release 15 version (frozen at TSG-80) |
15.0.0 |
||||
|
2020-07 |
RP-88e |
– |
– |
– |
– |
Upgrade to Rel-16 version without technical change |
16.0.0 |
|
2022-03 |
RP-95e |
– |
– |
– |
– |
Upgrade to Rel-17 version without technical change |
17.0.0 |