Broadcast and Multicast Traffic
Downlink broadcast and multicast traffic are supported.
Broadcast Traffic
Broadcast packets received at the EPC are forwarded to all eNodeBs (served by the EPC) and UEs in the subnet only if the destination address is the broadcast IP address of that EPC subnet.
Multicast Traffic
The Multimedia Broadcast Multicast Service (MBMS) model is supported to provide delivery of multicast traffic to the UEs.
The following components of MBMS are supported:
-
MBSFN Area Profiles – (Multi-Media Broadcast over a Single Frequency Network) An MBMS area includes the definition of the frame resources reserved for MBMS services and the list of MBMS bearers that will use those resources. MBSFN Area profiles are defined in the LTE Configuration Utility attribute “MBSFN Area Profiles” and can be associated with any eNodeB by setting this attribute on the eNodeB: LTE > MBMS > MBSFN Area.
The common allocation period defines the frame and subframe patterns of the reserved resources. The common allocation period is configured in the LTE Configuration Utility attributes MBSFN Area Profiles > Common Subframe Allocation and MBSFN Area Profiles > Common Subframe Allocation Pattern.
-
MBMS Bearers – The MBMS bearers belonging to a given profile are defined in the attribute MBSFN Area Profiles > MBMS Bearer List. For each MBMS bearer, you must specify an IP multicast address. This IP multicast address must match the address associated with the multicast application deployed to the UEs. IP multicast addresses should not be repeated across different MBSFN area profiles.
Note that allocation of the MBMS bearers into the common allocation period is done by the simulation, based on the bearer's attributes (downlink maximum bit rate, allocation delay, and modulation and coding scheme index). The allocation of each MBMS bearer is distributed across multiple frames occupying a maximum of one subframe per frame. This allows the simulation to evenly distribute the delay of the radio subframes occupied by each MBMS bearer, although a single MBMS bearer may be prevented from occupying the full capacity that an MBSFN area may offer. Given that a maximum of six subframes per frame can be used by MBMS services (if configured accordingly in the common subframe allocation pattern), then the full capacity of an MBSFN area can be achieved by configuring six MBMS bearers in that area (assuming all six subframes are in use).
-
MBMS Single Frequency Network (MBSFN) – MBSFN enforces synchronization of all MBMS transmissions across all eNodeBs that are configured under the same MBSFN area profile. Transmissions are synchronized in both time and frequency, creating a macro-diversity effect on which MBMS packets sent from different eNodeBs—within the same MBSFN area—do not interfere with each other. Instead, the eNodeBs reinforce each other due to a combining gain.
The model supports a time synchronization mechanism that aligns the multicast data packets so they are sent at the same subframe time by all the eNodeBs using the same MBSFN area profile. To accomplish this, each MBSFN area profile has an attribute called “Synchronization Delay”. The data packets will be considered for transmission by the eNodeBs on the next MBMS subframe after the delay indicated by this attribute. If the delay of an MBMS packet between the EPC and an eNodeB is greater than the synchronization delay, then that data packet will be dropped.
-
IGMP Snooping – eNodeB and EPC nodes use IGMP join messages sent by the UEs to “activate” the corresponding MBMS bearers and the pre-allocated resources for each MBMS bearer. IGMP leave messages are used to “deactivate” the MBMS bearers and their resources. The unused subframes can then be used by DSCH to transport non-GBR unicast traffic.
-
MBMS Gateway – The MBMS gateway functionality is located at the EPC node. The EPC node forwards multicast traffic in a given MBMS area only to the eNodeBs that are currently serving UEs that have joined a particular MBMS bearer. This forwarding stops when all clients of the MBMS bearer leave the multicast service in that eNodeB. When no more multicast clients are in any eNodeBs, the EPC node stops forwarding to that MBMS bearer.
-
Mobility and MBMS – As the UEs with active multicast applications move across the network and change their serving eNodeBs, the MBMS system updates the number of active users of the given MBMS bearers at the eNodeBs and EPC. As a result of the updates, the EPC/MBMS gateway may stop forwarding MBMS traffic to eNodeBs where all subscribers of a given MBMS bearer (or bearers) have left, or start forwarding the MBMS traffic to the eNodeBs where the active subscribers are now attached. eNodeB failure will cause the interruption of MBMS services on that eNodeB.
-
Multi-sector eNodeBs support MBMS services, although all sectors in the eNodeB must be subscribed to the same MBSFN area. Then multi-sector eNodeBs' MBMS configuration can be found independently from the LTE sectors' attributes, under LTE > MBMS.
-
Multicast packets that are received at the EPC (when MBMS is not configured) are forwarded to all eNodeBs and UEs in the subnet. When a UE is not a member of the given multicast group, it simply ignores the transmission. If the EPC receives packets for a multicast address not associated with any of the MBMS bearers in the MBMS area, the multicast traffic is broadcast to all eNodeBs and UEs in the subnet without using MBMS resources.
Note: You must configure IP multicast in your network before you can run LTE multicast operations in the network model. See “IP Multicast” for more information.