System Information Extension Utility Function for SIB Types
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current telecommunications systems lack efficient mechanisms for introducing new system information block types in Radio Resource Control (RRC) protocol, limiting the ability to extend system information transmissions due to constraints in spare values and backward compatibility issues.
Innovation Solution
The introduction of a system information extension utility function that includes additional indicators and fields in protocol blocks to support extended system information block types, allowing user equipment units to recognize and process new types, even if they fall outside the nominal range of values, through the use of extension indicators and code sets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If new system information block types are added to extend system information transmissions, then the adaptability and versatility of the protocol is improved, but the device complexity and difficulty of detecting and measuring increase due to constraints in spare values and backward compatibility requirements
Solution Approach 1:
The patent segments the system information block type field into multiple parts: a nominal range field and an extension indicator field. This segmentation allows the protocol to maintain its original structure for backward compatibility while adding extension capabilities through separate indicator bits that trigger interpretation of additional extension fields.
Solution Approach 2:
The patent adds a new dimension to the protocol by introducing extension indicator bits and extension fields that operate alongside the existing nominal range fields. This dimensional extension allows new SIB types to be defined without modifying the core protocol structure, enabling future-proofing while maintaining compatibility with existing implementations.
2Adaptability or versatility
If extension indicators and fields are added to protocol blocks, then the adaptability for new SIB types is improved, but the overhead in ASN.1 definitions increases
Solution Approach 1:
The patent applies local quality by making extension fields optional and location-specific. Extension indicators are placed only where needed in the protocol structure (in nominal range fields and scheduling information), and extension fields are included only when the indicators are set. This localized approach minimizes overhead while maintaining adaptability where required.
Solution Approach 2:
The patent uses partial action by implementing extension capabilities only in specific protocol elements rather than throughout the entire protocol. The extension mechanism is applied selectively to system information block type fields and scheduling information, avoiding unnecessary overhead in parts of the protocol where extension is not needed.
3Reliability
If spare values are constrained to maintain backward compatibility, then the reliability of existing systems is preserved, but the ability to introduce new SIB types is limited
Solution Approach 1:
The patent introduces extension indicator bits as intermediaries between the existing nominal range fields and the new extension fields. These indicators act as mediators that allow existing systems to ignore the extension mechanism (maintaining backward compatibility) while enabling new systems to utilize the full range of SIB types by interpreting the extension fields when indicators are set.
Solution Approach 2:
The patent performs preliminary action by reserving specific bit patterns in the nominal range fields as extension indicators before they are needed. This preliminary reservation of spare values as indicators allows the protocol to maintain its original structure while preparing the ground for future extensions without requiring immediate changes to the core protocol.
Data Source
AI summary
System information is transmitted over an air interface (32) between a node of a telecommunications network and a user equipment unit (30). The system information includes system information blocks which use extended system information block types, e.g., system information block type values which are outside a range of nominal system information block type values. The use of the extended system information block types is facilitated by embodiments of system information extension utility functions at the network node, by method of operating the network nodes, and by corresponding embodiments of system information processing functions provided at the user equipment unit (30).