Content for TS 37.340 Word version: 18.2.0

1… 4… 4.2… 4.3… 5… 7… 8… 9 10… 10.2… 10.2.2… 10.3… 10.3.2 10.4… 10.5… 10.5.2 10.6 10.7… 10.8… 10.9… 10.10… 10.11… 10.12… 10.12.2 10.13… 10.14… 10.15 10.16… 10.17… 10.18… 10.19… 10.20 11… A B…

10.10 RRC Transfer 10.10.1 EN-DC 10.10.2 MR-DC with 5GC
...

The RRC Transfer procedure is used to deliver an RRC message, encapsulated in a PDCP PDU between the MN and the SN (and vice versa) so that it may be forwarded to/from the UE using split SRB. The RRC transfer procedure is also used for:

providing an NR measurement report, NR failure information, NR UE assistance information or intra-SN CPC execution completion from the UE to the SN via the MN. If UE is IAB-MT, providing NR IAB other information from the IAB-MT to the SN via the MN;
providing MCG failure information from the UE to the MN via the SN and an RRC reconfiguration, or release, or an inter-RAT handover command from the MN to the UE via the SN.

Additional details of the RRC transfer procedure are defined in TS 36.423.

Split SRB:

Figure 10.10.1-1: RRC Transfer procedure for the split SRB (DL operation)

Figure 10.10.1-1 shows an example signaling flow for the DL RRC Transfer in case of the split SRB:

Step 1.

The MN, when it decides to use the split SRBs, starts the procedure by initiating the RRC Transfer procedure. The MN encapsulates the RRC message in a PDCP-C PDU and ciphers with own keys.

Step 2.

The SN forwards the RRC message to the UE.

Step 3.

The SN may send PDCP delivery acknowledgement of the RRC message forwarded in step 2.

Reproduction of 3GPP TS 37.340, Fig. 10.10.1-2: RRC Transfer procedure for the split SRB (UL operation)

Figure 10.10.1-2: RRC Transfer procedure for the split SRB (UL operation)

Figure 10.10.1-2 shows an example signaling flow for the UL RRC Transfer in case of the split SRB:

Step 1.

When the UE provides response to the RRC message, it sends it to the SN.

Step 2.

The SN initiates the RRC Transfer procedure, in which it transfers the received PDCP-C PDU with encapsulated RRC message.

NR measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion:

Reproduction of 3GPP TS 37.340, Fig. 10.10.1-3: RRC Transfer procedure for NR measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion

Figure 10.10.1-3: RRC Transfer procedure for NR measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion

Figure 10.10.1-3 shows an example signaling flow for RRC Transfer in case of the forwarding of the NR measurement report, NR failure information, NR IAB other information from the UE, NR UE assistance information or intra-SN CPC execution completion:

Step 1.

When the UE sends a measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion, it sends it to the MN in a container within ULInformationTransferMRDC message as specified in TS 36.331.

Step 2.

The MN initiates the RRC Transfer procedure, in which it transfers the received NR measurement report, NR failure information, NR UE assistance information, NR IAB other information or intra-SN CPC execution completion as an octet string.

MCG failure information and RRC Reconfiguration / RRC Release / inter-RAT handover command over SRB3:

Reproduction of 3GPP TS 37.340, Fig. 10.10.1-4: RRC Transfer procedure for MCG failure information

Figure 10.10.1-4: RRC Transfer procedure for MCG failure information

Figure 10.10.1-4 shows an example signaling flow for RRC Transfer in case of the forwarding of the MCG failure information from the UE:

Step 1.

When the UE sends EUTRA MCGFailureInformation message over SRB3, it sends it to the SN in a container within ULInformationTransferMRDC message as specified in TS 38.331.

Step 2.

The SN initiates the RRC Transfer procedure, in which it transfers the received EUTRA MCGFailureInformation message as an octet string.

Step 3.

The MN initiates the RRC Transfer procedure, in which it transfers the EUTRA RRCConnectionReconfiguration message, or EUTRA RRCConnectionRelease message, or MobilityFromEUTRACommand message as an octet string.

Step 4.

The SN sends the received EUTRA RRC message to the UE over SRB3 in a container within DLInformationTransferMRDC, message as specified in TS 38.331.

10.10.2 MR-DC with 5GC p. 87

providing a SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion or intra-SN subsequent CPAC without MN involvement execution completion from the UE to the SN. If UE is IAB-MT, providing NR IAB other information from the IAB-MT to the SN when the IAB-donor is the SN;
providing MCG failure information from the UE to the MN via the SN and an RRC reconfiguration, or release, or an inter-RAT handover command from the MN to the UE via the SN;
providing F1-C traffic from an IAB-node to the MN via the SN, or F1-C traffic from the MN to an IAB-node via the SN.

Additional details of the RRC transfer procedure are defined in TS 38.423.

Split SRB:

Figure 10.10.2-1: RRC Transfer procedure for split SRB (DL operation)

Figure 10.10.2-1 shows an example signaling flow for DL RRC Transfer in case of the split SRB:

Step 1.

The MN, when it decides to use the split SRBs, starts the procedure by initiating the RRC Transfer procedure. The MN encapsulates the RRC message in a PDCP PDU and ciphers with own keys.

Step 2.

The SN forwards the RRC message to the UE.

Step 3.

The SN may send PDCP delivery acknowledgement of the RRC message forwarded in step 2.

Reproduction of 3GPP TS 37.340, Fig. 10.10.2-2: RRC Transfer procedure for split SRB (UL operation)

Figure 10.10.2-2: RRC Transfer procedure for split SRB (UL operation)

Figure 10.10.2-2 shows an example signaling flow for UL RRC Transfer in case of the split SRB:

Step 1.

When the UE provides response to the RRC message, it sends it to the SN.

Step 2.

The SN initiates the RRC Transfer procedure, in which it transfers the received PDCP PDU with encapsulated RRC message.

SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion, intra-SN subsequent CPAC without MN involvement execution completion or IAB other information:

Reproduction of 3GPP TS 37.340, Fig. 10.10.2-3: RRC Transfer procedure for SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion, intra-SN subsequent CPAC without MN involvement execution completion or IAB other information

Figure 10.10.2-3: RRC Transfer procedure for SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion, intra-SN subsequent CPAC without MN involvement execution completion or IAB other information

Figure 10.10.2-3 shows an example signaling flow for RRC Transfer in case of the forwarding of the SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion, intra-SN subsequent CPAC without MN involvement execution completion or IAB other information from the UE:

Step 1.

When the UE sends an SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion, intra-SN subsequent CPAC without MN involvement execution completion or IAB other information it sends it to the MN in a container called ULInformationTransferMRDC message as specified in TS 38.331.

Step 2.

The MN initiates the RRC Transfer procedure, in which it transfers the received SN measurement report, failure information, SN UE assistance information, intra-SN CPC execution completion, intra-SN subsequent CPAC without MN involvement execution completion or IAB other information as an octet string.

MCG failure information and RRC Reconfiguration / RRC Release / inter-RAT handover command over SRB3:

Reproduction of 3GPP TS 37.340, Fig. 10.10.2-4: RRC Transfer procedure for MCG failure information

Figure 10.10.2-4: RRC Transfer procedure for MCG failure information

Figure 10.10.2-4 shows an example signaling flow for RRC Transfer in case of the forwarding of the MCG failure information from the UE:

Step 1.

When the UE sends MCGFailureInformation message over SRB3, it sends it to the SN in a container called ULInformationTransferMRDC message as specified in TS 38.331.

Step 2.

The SN initiates the RRC Transfer procedure, in which it transfers the received MCGFailureInformation message as an octet string.

Step 3.

The MN initiates the RRC Transfer procedure, in which it transfers the RRCConnectionReconfiguration message, or RRCReconfiguration message, or RRCConnectionRelease message, or RRCRelease message, or MobilityFromNRCommand message, or MobilityFromEUTRACommand message as an octet string.

Step 4.

The SN sends the received RRC message to the UE in a container called DLInformationTransferMRDC message, as specified in TS 38.331.

F1-C traffic transfer:

Figure 10.10.2-5: Scenario 2: F1-C Traffic Transfer procedure between IAB-MT and MN (F1-terminating node) in NR-DC

Step 1.

The IAB-MT sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet to the SN (non-F1-terminating IAB-donor) via split SRB2 in a container within ULInformationTransfer message encapsulated in a PDCP PDU as specified in TS 38.331.

Step 2.

The SN initiates the RRC Transfer procedure, in which it transfers the received PDCP PDU (ULInformationTransfer message) including F1-AP message.

Step 3.

When the MN (F1-terminating IAB-donor) sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet, it starts the procedure by initiating the RRC Transfer procedure, if split SRB2 is determined to be used and usage of SCG path is determined. The MN sends the F1-AP message to the SN in a container within DLInformationTransfer message encapsulated in a PDCP PDU specified in TS 38.331.

Step 4.

The SN forwards the encapsulated DLInformationTransfer message in a PDCP PDU as specified in TS 38.331 to IAB-MT.

Content for TS 37.340 Word version: 18.2.0

10.10 RRC Transfer p. 85

10.10.1 EN-DC p. 85

10.10.2 MR-DC with 5GC p. 87