During Handover from Source Cell to Target cell, if both the Source and target cell use same Configurations for certain Physical and control channels, the target cell can re-use the same configuration and modify the parameters which are different at target cell and send reconfiguration for only those parameters. This configuration change is known as delta signaling and it significantly decreases the size of the RRC reconfiguration message during handover.
NR also uses delta configuration when UE moves from RRC_INACTIVE state to RRC_CONNCTED state. Network only sends the delta signaling that needs to be modified in which only changed parameters are signaled – to restore the configuration of a UE in the inactive state. This option is not possible for UEs in the idle state.
The reduction in RRC signaling significantly lowers the access latency experienced by UEs, which leads to more responsive end-user service and the ability to support new use cases
How network Determines to use Delta Signaling
When handover is triggered , before that
- UE triggers Measurement Report, Measurement report can contain Multiple Cells and also include Beam Measurements of Target cells
- gNB receives the Measurement reports and determines to perform Handover to target cell based on the measurementReport and RRM Information.
- The source gNB sends Handover request message to Target cell, the information can include
- Target Cell ID
- C-RNTI of the UE in the source Gnb
- Current RRC Reconfiguration provided to UE by Source Cell.
- RRM-configuration including UE inactive time
- Basic AS-configuration including antenna Info and DL Carrier Frequency
- The current QoS flow to DRB mapping rules applied to the UE .
- The SIB1 from source Gnb
- The UE capabilities for different RATs,
- PDU session related information, and can include the
- UE reported measurement information including beam-related information if available.
- The PDU session related information includes the slice information and QoS flow level QoS profile(s)
Now the Target gnb receives all this information from the source gNB, it can decide based on the information received to perform Multiple checks and determine what action is required
- The Target cell performs an Admission control check.
- If Network slicing was configured to the UE, the target gNB performs Slice-aware admission control.
- If there are any PDU sessions associated with non-supported slices then the target gNB rejects such PDU Sessions.
- The Target cell can determine if there are other cells that can be configured as Scells from the MeasurementReport to increase the data rates to UE.
- If the MeasurementReport contains beam measurements i.e SSB index, then the Target cell can configure Contention Free RACH to the UE, If there are Multiple beam indexes, the target cell can configure CFRA resources to Multiple SSB beams.
- If the Target cell determines that the Source Cell and Target cell uses Same configuration for data and control PHY Channels and RRM Configuration, then the target cell and indicate ‘Delta Signaling’ which configures only the parameters that needs to be modified.
The target gNB prepares the handover with L1/L2 and sends the HANDOVER REQUEST ACKNOWLEDGE to the source gNB, which includes a transparent container to be sent to the UE as an RRC message to perform the handover. The target gNB also indicates if a DAPS Handover is accepted.
For Inter-RAT Handover, the delta config is only applicable to SDAP/PDCP configuration, if the EUTRA is connected to 5GC.
How Does the UE knows if Delta Signaling is configured in the Handover message
In the RRC Recofiguration message network indicates whether delta signaling is being used or it is sending a new configuration for the target cell. The FullConfig IE indicates to UE if Full configuration is applicable or if delta signaling is being used.
- The IE FullConfig is applicable for the RRCReconfiguration message for intra-system intra-RAT HO.
- For inter-RAT HO from E-UTRA to NR-SA, fullConfig indicates whether or not delta signalling of SDAP/PDCP from source RAT is applicable.
- FullConfig is not sent if any DAPS bearer is configured or when the RRCReconfiguration message is transmitted on SRB3.
- In the case of NSA FullConfig is not sent if the RRCReconfiguration message for SCG is contained in another RRCConnectionReconfiguration message that is transmitted on SRB1.
- The field is mandatory present in case of inter-system handover from E-UTRA/EPC to NR.
- It is optionally present, Need N, during reconfiguration with sync and also in first reconfiguration after reestablishment; or
- It is optionally present for intra-system handover from E-UTRA/5GC to NR.
- This Field is absent for other RRCReconfiguration messages apart from mentioned above.
- FullConfig IE is also optionally present in RRCResume message.