System Message Block Forward Compatibility via Service Indication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication systems lack forward compatibility, as system message blocks are designed for specific protocol releases without considering future compatibility, limiting their ability to support new services and scenarios across different protocol releases.
Innovation Solution
A method for generating and transmitting system message blocks that include cell access related information and service indication information, allowing for the indication of service types and new functions across multiple protocol releases, ensuring compatibility by using shared or modified parameters and interpretations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If system message blocks are designed for a specific protocol release, then the system can ensure reliable operation for that release, but it loses forward compatibility with future protocol releases
Solution Approach 1:
The system message block is designed to serve multiple protocol releases simultaneously. By incorporating service indication information that can identify different service types (eMBB, URLLC, mMTC) and using a unified message structure that accommodates both legacy and new services, the message block achieves multi-functionality across different protocol versions without requiring separate message designs for each release.
Solution Approach 2:
The system message block incorporates dynamic service indication information that can adapt its content and interpretation based on the protocol release version. The message structure allows flexible interpretation where legacy UEs interpret the message according to their protocol version while new UEs can recognize and utilize additional service types, enabling the same message to dynamically serve different protocol releases appropriately.
2Adaptability or versatility
If system message blocks include service indication information for multiple service types, then forward compatibility is improved, but the message complexity increases
Solution Approach 1:
The system message block is segmented into distinct functional components: cell access related information and service indication information. This segmentation allows legacy UEs to process only the cell access information they understand while ignoring the service indication portion, whereas new UEs can process both sections. This modular segmentation reduces the effective complexity each UE must handle while maintaining overall message comprehensiveness.
Solution Approach 2:
Service indication information acts as an intermediary element that bridges legacy and new services within the same message block. Rather than creating separate message structures for different services, the service indication information serves as a mediator that guides UEs on how to interpret the message content based on their capabilities and the supported service types, simplifying the overall structure while enabling multi-service support.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
A system message block transmission method, a base station and a UE are provided. The system message block transmission method includes: generating a first system message block and transmitting the first system message block. The first system message block includes cell access related information and service indication information, the service indication information is used to indicate at least one of a service type supported by a cell and a new function of the first system message block, the service type includes a service type in a first protocol release or the service type includes a service type in the first protocol release and a service type in a second protocol release, the new function is related to the second protocol release, and the second protocol release is an evolution release of the first protocol release.