Multicast Group Reuse in Cellular Network Transport
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cellular network technologies face inefficiencies in managing multicast traffic due to the need for multiple IP Multicast addresses and groups, which increases resource usage and complexity in nodes like eNBs and routers.
Innovation Solution
Allocating multiple multicast sessions to a single IP Multicast group with unique identifiers within the group, allowing RAN nodes to distinguish and forward data correctly, thereby reducing the number of required IP Multicast groups and addresses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a new IP Multicast address is allocated for each MBMS session, then multicast transmission can be properly managed per session, but the number of IP Multicast addresses and groups increases significantly, consuming more resources in eNBs and routers
Solution Approach 1:
The patent merges multiple MBMS sessions into a single IP Multicast group by allowing multiple sessions to share the same transport IP Multicast address. This is achieved by identifying sessions that can be multiplexed together and assigning them a common group address, thereby reducing the total number of IP Multicast addresses required in the network while maintaining proper session management through additional identification mechanisms.
Solution Approach 2:
The patent makes a single IP Multicast address universal by enabling it to serve multiple MBMS sessions simultaneously. The same transport IP Multicast address can be used for distributing data from the MBMS gateway to multiple RAN nodes for different sessions, with session differentiation achieved through other means such as session identifiers or contextual information at the receiving end.
2Adaptability or versatility
If multiple IP Multicast groups are used for different MBMS sessions, then each session can be independently managed, but the complexity of protocol activities and information handling in eNBs and routers increases
Solution Approach 1:
The patent combines multiple session management functions into a single IP Multicast group context, reducing the number of separate protocol instances that need to be maintained. By allowing one IP Multicast group to carry multiple sessions, the system reduces the overall protocol complexity in eNBs and routers while maintaining the ability to manage individual sessions through identification mechanisms.
Solution Approach 2:
The patent introduces an intermediary identification mechanism (such as session identifiers or contextual information) that mediates between the shared IP Multicast address and the individual session requirements. This intermediary allows the system to maintain session independence and proper routing decisions without requiring separate IP Multicast groups for each session, thereby reducing complexity.
3Measurement precision
If a large number of IP Multicast addresses are used, then each MBMS session can be properly identified, but the amount of information that routers and switches must maintain and communicate increases considerably
Solution Approach 1:
The patent merges multiple session identification functions into a single IP Multicast address context, reducing the amount of routing and forwarding information that routers and switches must maintain. Instead of maintaining separate entries for each session's IP Multicast address, network devices only need to maintain information for the shared group address, significantly reducing information overhead while session identification is preserved through other means.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
For transmission of multicast data in a cellular network, a gateway (200) allocates a set of multicast sessions (111, 112) to a single Internet Protocol Multicast group (110). For each of the multicast sessions (111, 112), the gateway indicates an Internet Protocol Multicast address of the Internet Protocol Multicast group to one or more radio access network nodes (100) of the cellular network. For each of the multicast sessions (111, 112), the gateway (200) indicates a different identifier to the radio access network nodes (100), e.g., in the form of a Tunnel Endpoint Identifier. The gateway (200) sends multicast data of the multicast sessions (111, 112) in one or more Internet Protocol Multicast data packets addressed to the Internet Protocol Multicast address of the Internet Protocol Multicast group. The multicast data of each of the multicast sessions (111, 112) include the respective identifier to allow identification of the multicast session (111, 112) at the radio access network node (100).