MBS IP Address Type Field Decoding for 5G Session Joining
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication systems, particularly in 5G NR, face challenges in efficiently decoding and encoding IP address type information for Multicast Broadcast Service (MBS) sessions, which affects the accurate identification and joining of admitted MBS sessions by user equipment (UE) in wireless communication networks.
Innovation Solution
The method involves a UE sending a request to join MBS sessions and receiving a response message from the core network that includes an IP address type (IPAT) field, allowing the UE to decode the IP addresses corresponding to admitted sessions based on the indicated type, and the core network encoding this information for transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If IP address information for MBS sessions is transmitted without explicit type indication, then the message format remains simple and compact, but the receiving UE cannot accurately decode whether the IP addresses are IPv4 or IPv6 types
Solution Approach 1:
The received MBS information is segmented into multiple fields including TMGI, session ID, source IP address, destination IP address, and an IP address type field. Each field is independently structured and identified, allowing the UE to accurately parse and decode the IP address type (IPv4 or IPv6) without ambiguity, while maintaining a systematic and organized message format.
Solution Approach 2:
An IP address type indication field is introduced as an intermediary element between the IP address data and the decoding logic. This field explicitly carries the type information (IPv4 or IPv6) and serves as a mediator that enables the UE to correctly interpret the associated IP addresses without requiring complex inference or additional signaling mechanisms.
2Adaptability or versatility
If the system supports both IPv4 and IPv6 for MBS sessions, then the service compatibility and versatility are improved, but the complexity of managing and differentiating between different IP address types increases
Solution Approach 1:
The message structure is designed to be universal and support both IPv4 and IPv6 protocols within the same framework. The IP address type field provides a unified mechanism to indicate the protocol type, allowing the system to handle multiple IP versions without requiring separate message formats or complex version-specific processing logic.
Solution Approach 2:
The system uses parameter changes in the IP address type field to dynamically indicate whether IPv4 or IPv6 is being used. By changing the value or state of this parameter, the system can adapt to different IP protocols without altering the overall message structure or requiring separate handling procedures, thereby reducing management complexity.
3Loss of information
If detailed IP address information is included in the MBS response message, then the completeness of session information is improved, but the message size and processing overhead increase
Solution Approach 1:
Only the essential IP address information elements are extracted and included in the received MBS information message, specifically the source IP address, destination IP address, and IP address type field. Unnecessary or redundant information is excluded, ensuring that the message contains complete and accurate session information while maintaining compact size and minimizing processing overhead.
Data Source
AI summary
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a UE. The UE sends a request message to a core network. The request message requests joining one or more requested multicast broadcast service (MBS) sessions. The UE receives a response message from the core network. The response message contains received MBS information indicating one or more admitted MBS sessions. The received MBS information includes a respective IP address type (IPAT) field. The IPAT field indicates a type of an IP address corresponding to each of the one or more admitted MBS sessions. The UE decodes the IP address corresponding to each of the one or more admitted MBS sessions according to the type indicated by the respective IPAT field.