RAN Entity Multicast Mapping for Private 3GPP Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Implementing multicast and broadcast communication in LTE-based mobile networks, particularly in local private 3GPP networks like Citizens Broadband Radio Service (CBRS), is challenging due to the need for additional network elements and lack of widespread support in LTE-configured User Equipments (UEs, and the complexity of LTE cores in enterprise environments.
Innovation Solution
The solution involves configuring a radio access network (RAN) entity, such as an eNodeB or gNodeB, to facilitate multicast communication by selecting and transmitting user data packets to UEs through stored mappings of multicast group identifiers and tunnel endpoint identifiers, reducing the need for new core network elements and UE support, and employing packet replication to alleviate backhaul loading.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If eMBMS is used for multicast communication in LTE networks, then multicast service capability is improved, but device complexity and network infrastructure requirements worsen due to need for eMBMS gateway and MCE
Solution Approach 1:
The patent extracts the multicast service capability from the complex eMBMS framework and implements it directly at the eNodeB level. The eNodeB performs packet replication and distribution functions that would otherwise require separate gateway and coordination entities, thereby eliminating the need for eMBMS gateway and MCE while maintaining multicast service capability.
Solution Approach 2:
The patent merges multiple functions (packet replication, tunnel management, and multicast distribution) into the eNodeB itself. By combining these previously separate functions into a single network element, the patent reduces overall network infrastructure complexity while preserving multicast service capability.
2Adaptability or versatility
If eMBMS is deployed for multicast communication, then multicast functionality is improved, but ease of operation worsens due to lack of widespread UE support and high LTE core complexity
Solution Approach 1:
The patent enables the eNodeB to self-manage multicast operations by maintaining local mappings between downlink tunnel endpoint identifiers and multicast group identifiers. This self-service approach eliminates dependence on complex core network elements and special UE support, thereby improving ease of operation while maintaining multicast functionality.
Solution Approach 2:
Instead of requiring UEs to support complex eMBMS protocols and the core network to provide multicast services, the patent inverts the approach by having the eNodeB provide multicast services directly using standard IP multicast mechanisms. This inversion simplifies UE requirements while maintaining multicast functionality.
3Adaptability or versatility
If traditional multicast methods are used in private LTE networks, then multicast service is provided, but productivity decreases due to backhaul loading issues
Solution Approach 1:
The patent segments the multicast traffic handling by creating separate downlink tunnels for different multicast groups and maintaining specific mappings between tunnel endpoint identifiers and multicast group identifiers. This segmentation allows efficient packet replication at the eNodeB level without overwhelming the backhaul, thereby improving network efficiency while providing multicast service.
Data Source
AI summary
A radio access network (RAN) entity (e.g. an eNodeB) may be configured to facilitate multicast communication in a local private Third Generation Partnership Project (3GPP) network. The RAN entity may receive a user data packet tunneled in an IP message via one of a plurality of downlink tunnels. The RAN entity may select, from a plurality of stored mappings, one of a plurality of multicast group identifiers that is mapped to an identified one of a plurality of downlink tunnel endpoint identifiers that matches a downlink tunnel endpoint identifier from a tunnel header of the IP message, as well as one of a plurality of sets of UE identifiers that is mapped to the selected multicast group identifier. The RAN may send, for each one of the UE identifiers in the selected set of UE identifiers, the user data packet for transmission to a UE associated with the UE identifier.