Question: When a User Equipment (UE) triggers a procedure to request specific System Information Blocks (SIBs), how does it indicate the requested SIB(s) in the `DedicatedSIBRequest` message?
Option 1: By including the `requestedSIB-List` in the `onDemandSIB-RequestList` for required SIB(s) and separately handling positioning SIB (posSIB) requests.
Option 2: Through a dedicated `SIB-Request` field specifically designed for each type of SIB, without using lists.
Option 3: By setting a specific bit pattern in the `DedicatedSIBRequest` message header to signify the request type (SIB or posSIB).
Option 4: The UE does not specify the requested SIB(s) in the `DedicatedSIBRequest` message; instead, it relies on network inference.
Explanation: According to standard RRC protocol procedures for efficient resource utilization and clear communication, when a UE needs to request specific SIB(s), it systematically includes the `requestedSIB-List` within the `onDemandSIB-RequestList` of the `DedicatedSIBRequest` message. This structured approach ensures the network can accurately identify and respond to the UE's information needs, distinguishing between general SIB requests and those for positioning (posSIB) when necessary.