MBMS RAN Requirements

The following RAN requirements have been identified [7]:

  1. MBMS data transfer shall be downlink only.
  2. QoS attributes shall be the same for MBMS Multicast and Broadcast modes.
  3. During MBMS data transmission it shall be possible to receive paging messages, which also should contain some additional information, such as CLI.
  4. Simultaneous reception of MBMS and non-MBMS services shall depend upon UE capabilities.
  5. Simultaneous reception of more than one MBMS services shall depend upon UE capabilities.
  6. A notification procedure shall be used to indicate the start of MBMS data transmission. This procedure shall contain MBMS RB information.
  7. A mechanism to enable the Network to move MBMS subscribers between cells is required.
  8. MBMS UE multicast activation (Joining) shall be transparent to UTRAN.
  9. A mechanism is required that enables the non-transmission of MBMS multicast mode in a cell which does not contain any MBMS UEs joined to the multicast group.
  10. Reception of MBMS shall not be guaranteed at RAN level. MBMS does not support individual retransmissions at the radio link layer, nor does it support retransmissions based on feedback from individual subscribers at the radio level. This does not preclude the periodic repetitions of the MBMS content based on operator or content provider scheduling or retransmissions based on feedback at the application level.
  11. MBMS shall not prevent the capability for SRNS/SBSS relocation.
  12. A mechanism to provide UTRAN the received QoS per UE is not required as part of MBMS.
  13. UE controlled "service based" cell selection/reselection shall not be permitted.
  14. Handover and SGSN relocation shall not be affected by an active MBMS session.
  15. In the case of UTRAN only, guaranteed 'QoS' linked to a certain initial downlink power setting is not required; however, the purpose and possibility of some reporting mechanism could be identified to measure the delivered QoS.
  16. MBMS Multicast mode transmissions should use dedicated resources (p-t-p) or common resources (p-t-m). The selection of the connection type (p-t-p or p-t-m) is operator dependent, typically based on downlink radio resource environment such as radio resource efficiency. A "threshold" related to the number of users may be utilised, resulting in the need for a mechanism to identify the number of subscribers in a given "area".
  17. MBMS solutions to be adopted should minimise the impact on the RAN physical layer and maximise reuse of existing physical layer and other RAN functionality.
  18. MBMS charging should be transparent to the RAN.
  19. MBMS should allow for low UE power consumption.
  20. Header compression should be used.
  21. MBMS should not prevent support for SGSN in pool.
  22. Data loss during cell change should be minimal.

The following MBMS Notification Requirements have been identified:

  1. MBMS notification shall be transmitted within the MBMS service area.
  2. MBMS notification shall be sent so it could be received by all UEs with an activated MBMS service, regardless of their RRC state or the lack of an RRC connection.
  3. MBMS notification should maximise the reuse of existing channels.
  4. MBMS notification should allow terminals to minimise their power consumption, meaning that UEs with an activated MBMS service should not listen permanently, but at regular intervals to MBMS notification.
  5. Reception of MBMS notification cannot be guaranteed.
  6. UEs may receive MBMS notification and simultaneously monitor other occasions, e.g. UE dedicated paging and CBS messages. The avoidance of collisions cannot be guaranteed. If collisions occur, the UE dedicated Paging has higher priority (UE requirement).




Back


HOME



About Us Careers Contribute Advertise






Copyright 2004-2019 3G4G.CO.UK. All rights reserved.
Contact zahidtg(at)yahoo(dot)com for further information