Positioning assistance data can be included in positioning System Information Blocks (posSIBs) as described in
TS 36.331,
TS 38.331 and
TS 36.355. The posSIBs are carried in RRC System Information (SI) messages. The mapping of posSIBs (assistance data) to SI messages is flexibly configurable and provided to the UE in SIB1 for NG-RAN node
TS 36.331,
TS 38.331.
The UE may request posSI by means of on-demand SI request in RRC_IDLE/RRC_INACTIVE and also request posSIBs by means of on-demand SI request in RRC_CONNECTED as described in
TS 38.331. U2N Remote UE may also request posSIB via a U2N Relay UE as described in
TS 38.331. The U2N relay UE forwards the posSIB transparently to the U2N Remote UE.
For each assistance data element, a separate posSIB-type is defined in
TS 36.355. Each posSIB may be ciphered by the LMF using the 128-bit Advanced Encryption Standard (AES) algorithm (with counter mode) as described in
TS 36.355, either with the same or different ciphering key. The posSIBs which exceed the maximum size limit defined in
TS 36.331,
TS 38.331 shall be segmented by the LMF.
The general procedures for broadcast of positioning assistance data and delivery of ciphering keys to UEs is described in
TS 23.273. This clause defines the overall sequences of operations that occur in the LMF, NG-RAN node and UE.
Step 1.
The LMF sends an NRPPa Assistance Information Control message to the NG-RAN node with an indication to start broadcasting assistance information. The message includes one or more System Information groups, where each group contains the broadcast periodicity and one or more posSIB types together with meta data to be scheduled in the same SI message. Each posSIB type may be ciphered and/or segmented at the LMF. The meta data may include an indication whether the posSIB type in the System Information group is ciphered or not, as well as an indication of an applicable GNSS type.
Step 2.
The NG-RAN node includes the received System Information groups in RRC System Information Messages and corresponding scheduling information in SIB1 as described in
TS 36.331,
TS 38.331. The UE applies the system information acquisition procedure according to
TS 36.331,
TS 38.331 for acquiring the assistance data information that is broadcasted.
Step 3.
If the posSIB types were ciphered by the LMF, the LMF invokes the
Nlmf_Broadcast_CipheringKeyData Notify service operation towards the AMF carrying one or more ciphering keys. For each ciphering key, the LMF includes a ciphering key value, a ciphering key identifier, a validity period, a set of applicable tracking areas, and a set of applicable posSIB types. The AMF may then distribute successfully stored ciphering keys and their validity times and validity areas to suitably subscribed UEs using a mobility management message as described in
TS 23.273. The LMF repeats this procedure whenever a ciphering key changes.
Step 4.
At any time after Step 1, the NG-RAN node may send a NRPPa Assistance Information Feedback message to the LMF providing feedback on assistance information broadcasting. The message may include an assistance information failure list indicating that certain posSIB types could not be configured for broadcasting by the NG-RAN node.
Step 5.
If the assistance information in a System Information group changes, the LMF provides updated information in a NRPPa Assistance Information Control message.
Step 6.
The NG-RAN node replaces the previously stored System Information groups with the new information received at Step 5 and includes the new System Information groups in RRC System Information Messages.
Step 7.
If the LMF wants to abort the broadcast of a System Information Group, it sends a NRPPa Assistance Information Control message to the NG-RAN node including an indication to stop broadcasting the assistance information.