Dedicated SIB20 for IoT Broadcast in LTE and 5G Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication technologies for connected vehicles, such as eMBMS and SC-PTM, face challenges in efficiently broadcasting data to IoT devices beyond 300 meters, requiring significant network upgrades and causing power consumption issues due to shared SIB usage with WEA services, which do not meet latency and priority requirements for V2V/V2X services.
Innovation Solution
A dedicated SystemInformationBlock (SIB) in LTE and 5G networks is introduced to specifically target IoT devices for V2V and V2X services, allowing for dynamic prioritization and customized message delivery, reducing power consumption and network complexity by separating IoT and WEA broadcasts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Length of stationary object
If eMBMS or SC-PTM technologies are used for broadcasting data to IoT devices beyond 300 meters, then coverage range is extended, but network complexity and upgrade requirements increase significantly
Solution Approach 1:
The patent segments the broadcast service into two distinct parts: a dedicated SIB20 for IoT device information (broadcasting control information, service configuration) and existing SIB structures for other services. This segmentation allows IoT-specific broadcast functionality to be added without complicating the overall network architecture or requiring extensive upgrades to existing broadcast mechanisms.
2Productivity
If shared SIB is used for both WEA and IoT broadcasts, then network resource utilization is improved, but power consumption increases due to frequent wake-ups in mobile devices
Solution Approach 1:
The patent creates a dedicated SIB20 specifically for IoT device broadcasts, separating it from the shared SIB structure used for WEA (Wireless Emergency Alerts) and other services. This allows IoT devices to monitor only the specific SIB20 for their relevant broadcast information, while mobile devices can efficiently manage their wake-up cycles based on their own service requirements, thereby reducing unnecessary power consumption while maintaining effective network resource utilization.
3Reliability
If dedicated SIB is introduced for IoT services, then service prioritization and latency requirements are met, but message structure complexity increases
Solution Approach 1:
The patent introduces SIB20 as a dedicated information structure that segments IoT-specific broadcast data into a standardized, self-contained format. This segmentation provides clear service prioritization and meets latency requirements by giving IoT broadcasts dedicated resources, while the standardized structure actually simplifies processing compared to ad-hoc message formats, as devices know exactly what to expect in the dedicated SIB.
Solution Approach 2:
The patent changes the parameter of SIB allocation by introducing a dedicated SIB20 with specific parameters tailored for IoT services, including service identification fields, device type filtering, and prioritization indicators. These parameter changes enable reliable service differentiation without significantly increasing overall message structure complexity, as the dedicated structure follows consistent patterns.
4Adaptability or versatility
If existing broadcast mechanisms are used for V2V/V2X services, then network compatibility is maintained, but latency and priority requirements are not met
Solution Approach 1:
The patent segments the broadcast functionality by introducing SIB20 as a dedicated structure for V2V/V2X IoT services, while maintaining the existing SIB structures for other services. This segmentation allows the network to maintain full compatibility with existing devices and protocols, while simultaneously providing low-latency, high-priority broadcast channels for time-critical V2V/V2X applications through the dedicated SIB20 resource allocation.
Data Source
AI summary
A system information block (SIB) in a radio interface is dedicated to broadcast data intended for Internet of things (IoT) devices. The data can be associated with most any IoT service, such as but not limited to, a vehicle-to-vehicle (V2V) and/or vehicle-to-everything (V2X) service. In one aspect, data, associated with an event, that has been aggregated from one or more IoT devices located within a region can be analyzed to determine a geographical area where a message regarding the event (e.g., accident) is to be broadcast. Further, the message can be dynamically prioritized and/or customized to target a particular class of IoT devices (e.g., connected cars) by employing different message identifiers.