Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 37.340  Word version:  18.1.0

Top   Top   Up   Prev   Next
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.20  Subsequent Conditional PSCell Addition or Change |R18|p. 116

A Subsequent Conditional PSCell Addition or Change (subsequent CPAC) is defined as a conditional PSCell addition or change procedure that is executed after a PSCell addition, a PSCell change, a PCell change or an SCG release based on pre-configured subsequent CPAC configuration of candidate PSCell(s) without reconfiguration and re-initiation of CPC/CPA. The UE keeps the configured subsequent CPAC configuration (unless the network indicates to release it) and evaluates the execution conditions of candidate PSCells (if provided for the following execution of subsequent CPAC) after completion of a PSCell addition, a PSCell change, a PCell change or an SCG release. Intra-SN subsequent CPAC initiated by the SN, inter-SN subsequent CPAC initiated by either MN or SN are supported.
The following principles apply to subsequent CPAC:
  • For MN initiated subsequent CPAC, the MN initially triggers the candidate cell preparation of subsequent CPAC procedure and generates the execution conditions for the initial execution of subsequent CPAC (e.g. CPA or CPC).
  • For SN initiated subsequent CPAC, the source SN initially triggers the candidate cell preparation of subsequent CPAC procedure and generates the execution conditions for the initial execution of subsequent CPAC.
  • For both MN and SN initiated inter-SN subsequent CPAC, the candidate SN generates the execution conditions for the following execution of subsequent CPAC when the candidate SN prepares the candidate SCG configuration(s) for candidate PSCell(s). For SN initiated intra-SN subsequent CPAC, the source SN generates the execution conditions for the following execution of subsequent CPAC when the source SN prepares the candidate SCG configuration(s) for candidate PSCell(s).
  • The subsequent CPAC configuration contains candidate SCG configuration(s) of candidate PSCell(s), execution conditions, and may contain the MCG configuration (to be applied when subsequent CPAC execution is triggered), the reference configuration and the security update configuration.
  • The subsequent CPAC configuration for CPA or inter-SN CPC candidate PSCell(s) is provided in MN format. The subsequent CPAC configuration for intra-SN CPC candidate PSCell(s) can be provided in MN format or SN format.
  • For one UE, the subsequent CPAC configuration for all candidate PSCells (including inter-SN and/or intra-SN) is provided in the same format, i.e., either MN format, or SN format. If the configured candidate PSCell(s) includes at least one inter-SN CPC candidate PSCell, the subsequent CPAC configuration can only be provided in MN format. If only intra-SN CPC candidate PSCell(s) is configured, the subsequent CPAC configuration can be provided in either MN format or SN format. It is up to OAM configuration to ensure MN format or SN format to be used.
  • Each candidate PSCell configuration is provided as a delta configuration on top of a reference configuration or a complete configuration. Only one reference configuration is supported.
  • The MN generates the MCG part of the reference configuration (if any), while the SN generates the SCG part of the reference configuration. The MN can request an SCG reference configuration from any one of the involved SNs.
  • The network explicitly configures a subsequent CPAC configuration for the current serving PSCell if the network wants to use that PSCell as a candidate PSCell for subsequent CPAC.
  • The network always explicitly releases the subsequent CPAC configuration for candidate PSCells after an inter-MN PCell change.
  • Upon the release of SCG, the UE autonomously releases the stored subsequent CPAC configuration in SN format. Upon the release of SCG, the UE releases or maintains the stored subsequent CPAC configuration in MN format according to the network indication.
  • The same candidate PSCell configuration can be used for CPA execution and CPC execution, but with different execution conditions of the candidate PSCell.
  • The subsequent CPAC configuration with CPA execution condition(s) maintained after SCG release can be used for the subsequent CPA execution.
  • Upon inter-SN subsequent CPAC execution, the UE uses the first unused sk-Counter value for S-KgNB generation, based on the per-SN pre-configured sk-Counter value list.
  • Upon PCell change, PSCell change or SCG release, if the subsequent CPAC configuration is maintained, the UE also maintains the unused sk-Counter values.
  • The UE autonomously releases the subsequent CPAC configuration upon RRC re-establishment and upon RRC release.
  • While executing subsequent CPAC, the UE is not required to continue evaluating the execution condition of other candidate PSCell(s) or PCell(s).
  • The UE is not required to continue evaluating the execution conditions of other subsequent CPAC candidate PSCell(s) when PSCell change/addition or PCell change is triggered.
MN initiated subsequent CPAC
The subsequent CPAC procedure is initiated by the MN for inter-SN subsequent CPAC configuration and inter-SN subsequent CPAC execution.
Copy of original 3GPP image for 3GPP TS 37.340, Fig. 10.20-1: Inter-SN subsequent CPAC - MN initiated
Up
Figure 10.20-1 shows an example signalling flow for the inter-SN subsequent CPAC initiated by the MN:
Step 1/2/3/4.
The MN initiates the inter-SN subsequent CPAC by requesting the candidate SN(s) to allocate resources for the UE by means of the SN Addition procedure, indicating that the request is for subsequent CPAC. The MN also provides the candidate cells recommended by MN via the latest measurement results for the candidate SN(s) to choose and configure the SCG cell(s), provides the upper limit for the number of PSCells that can be prepared by each candidate SN, and provides a list of KSN and associated sk-Counter values for each candidate SN. In the SN Addition procedure, the MN also includes information of other candidate SN(s), and for each candidate SN, a list of cells recommended by the MN via the latest measurement results for the candidate SN to select the PSCell(s) for the following execution of subsequent CPAC. Within the list of cells as indicated within the measurement results indicated by the MN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR RRCReconfiguration** message contained in the SN Addition Request Acknowledge message with the prepared PSCell ID(s). For each prepared PSCell, the candidate SN also decides the list of PSCell(s) and associated execution conditions proposed for the following execution of subsequent CPAC. If data forwarding is needed, the candidate SN provides data forwarding addresses to the MN. The candidate SN may also propose data forwarding to the MN or other candidate SN(s) for subsequent CPAC. The candidate SN includes the indication of the complete or delta RRC configuration with respect to the SCG reference configuration. For the prepared PSCell(s) and the proposed PSCell(s) for the following execution of subsequent CPAC, the candidate SN can either accept or reject each of the candidate cells listed within the measurement results indicated by the MN, i.e. it cannot configure any alternative candidates.
The MN may select one of the candidate SN(s) and requests providing the SCG reference configuration as part of the SN Addition procedure. Once obtained, the MN provides the SCG reference configuration to other candidate SN(s).
Step 5.
For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message to the candidate SN(s).
Step 6/7.
For each candidate SN, the MN may initiate the SN Modification procedure towards the candidate SN to inform the prepared PSCells in other candidate SN(s), e.g., when not all proposed PSCells by this candidate SN for the following execution of subsequent CPAC were prepared by the candidate SN(s). If requested, the candidate SN sends an SN Modification Request Acknowledge message and if needed, provides the updated candidate SCG configuration(s) and/or the execution conditions for the following execution of subsequent CPAC to the MN.
Step 8.
The MN sends to the UE an RRCReconfiguration message including the subsequent CPAC configuration, i.e. a list of RRCReconfiguration* messages and associated execution conditions for the subsequent CPAC, in which each RRCReconfiguration* message contains the SCG configuration in the RRCReconfiguration** message received from one of the candidate SN(s) in steps 2 and 4, and possibly an MCG configuration. Besides, the RRCReconfiguration message can also include an updated source MCG configuration, e.g., to configure the required conditional measurements. The RRCReconfiguration message also includes a security update configuration and may also include a reference configuration.
Step 9.
The UE applies the RRCReconfiguration message received in step 8, stores the subsequent CPAC configuration and replies to the MN with an RRCReconfigurationComplete message. In case the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message, it performs the reconfiguration failure procedure.
Step 10.
In case of SN terminated bearers, early data forwarding may take place. For the early data forwarding of SN terminated bearers, the MN forwards the PDCP SDU to the candidate SN(s). For the early transmission of MN terminated split/SCG bearers, the MN forwards the PDCP PDU to the candidate SN(s).
Step 11.
The UE starts evaluating the execution conditions for the initial execution of subsequent CPAC. If the execution condition of one candidate PSCell is satisfied, the UE applies RRCReconfiguration* message corresponding to the selected candidate PSCell, and sends an MN RRCReconfigurationComplete* message, including an RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. The RRCReconfigurationComplete* message may also include the sk-Counter value associated with the selected candidate PSCell if a new sk-Counter value is selected.
Step 12.
The MN informs the SN of the selected candidate PSCell (i.e. the selected candidate SN) that the UE has completed the reconfiguration procedure successfully via SN Reconfiguration Complete message, including the RRCReconfigurationComplete** message. If the sk-Counter value is received by the RRCReconfigurationComplete* message, the MN also indicates the received sk-Counter value to the SN.
Step 13.
The UE performs synchronisation towards the PSCell indicated in the RRCReconfiguration* message applied in step 11. The order the UE sends the MN RRCReconfigurationComplete* message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Reconfiguration procedure.
Step 14.
If PDCP termination point is changed to the SN for bearers using RLC AM, the MN sends the SN Status Transfer message.
Step 15.
For SN terminated bearers or QoS flows moved from the MN, dependent on the characteristics of the respective bearer or QoS flow, the MN may take actions to minimise service interruption due to activation of MR-DC (Data forwarding).
Step 16-19.
If applicable, a PDU Session path update procedure is triggered by the MN.
Step 20-21.
If data forwarding is needed, the MN may send the Xn-U Address Indication message to the selected candidate SN. The SN may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an Early Status Transfer message to the MN.
Step 22.
The UE starts evaluating the execution conditions for the following execution of subsequent CPAC. If the execution condition of one candidate PSCell is satisfied, the UE applies RRCReconfiguration* message corresponding to the selected candidate PSCell, and sends an MN RRCReconfigurationComplete* message, including an RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. The RRCReconfigurationComplete* message may also include a sk-Counter value associated with the selected candidate PSCell if a new sk-Counter value is selected.
Step 23.
The MN informs the SN of the selected candidate PSCell that the UE has completed the reconfiguration procedure successfully via SN Reconfiguration Complete message, including the RRCReconfigurationComplete** message. If the sk-Counter value is received by the RRCReconfigurationComplete* message, the MN also indicates the received sk-Counter value to the SN.
Step 24.
The UE performs synchronisation towards the PSCell indicated in the RRCReconfiguration* message applied in step 22. The order the UE sends the MN RRCReconfigurationComplete* message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Reconfiguration procedure.
Step 25/26/27.
The MN triggers the MN initiated SN Modification procedure to inform the last serving SN to stop providing user data to the UE, to switch to the prepared state, and if applicable, to allow provisioning of new data forwarding addresses based on the data forwarding proposals of the MN and the selected candidate SN. If applicable, the MN triggers the Xn-U Address Indication procedure to inform the last serving SN the address of the SN of the selected candidate PSCell, to start late data forwarding.
Step 28/29.
If PDCP termination point is changed for bearers using RLC AM, the SN sends the SN Status Transfer message to MN, which the MN sends then to the SN of the selected candidate PSCell, if needed.
Step 30.
If applicable, data forwarding from the last serving SN takes place. It may be initiated as early as the the last serving SN receives the early data forwarding address in step 21.
Step 31.
The source SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2.
Step 32-36.
If applicable, a PDU Session path update procedure is triggered by the MN.
Step 37-38.
If data forwarding is needed, the MN may send the Xn-U Address Indication message to the selected candidate SN. The SN may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an Early Status Transfer message to the MN.
SN initiated inter-SN subsequent CPAC
The subsequent CPAC procedure is initiated by the SN for inter-SN subsequent CPAC configuration and inter-SN subsequent CPAC execution.
Copy of original 3GPP image for 3GPP TS 37.340, Fig. 10.20-2: Inter-SN subsequent CPAC - SN initiated
Up
Figure 10.20-2 shows an example signalling flow for the inter-SN subsequent CPAC initiated by the source SN:
Step 1.
The source SN (i.e. SN-1) initiates the inter-SN subsequent CPAC procedure by sending the SN Change Required message, which contains a subsequent CPAC initiation indication. The message also contains candidate node ID(s) and may include an SCG reference configuration (to support delta configuration), and contains the measurements results which may include cells that are not subsequent CPAC candidates. The message also includes a list of proposed PSCell candidates recommended by the source SN, including execution conditions for the initial evaluation, the upper limit for the number of PSCells that can be prepared by each candidate SN, and may also include the SCG measurement configurations for subsequent CPAC (e.g. measurement ID(s) to be used for subsequent CPAC). The source SN may also propose data forwarding to the MN or other candidate SN(s) for subsequent CPAC.
Step 2/3.
The MN requests each candidate SN(s) to allocate resources for the UE by means of the SN Addition procedure(s), indicating the request is for subsequent CPAC, and the measurements results which may include cells that are not subsequent CPAC candidates received from the source SN to the candidate SN, and indicating a list of proposed PSCell candidates to the candidate SN(s) received from the source SN, but not including execution conditions. The MN also includes information of other candidate SN(s), and for each candidate SN, a list of proposed PSCell candidates recommended by the source SN for the candidate SN to select the PSCell(s) for the following execution of subsequent CPAC. The MN also provides the upper limit for the number of PSCells that can be prepared by each candidate SN and provides a list of KSN and associated sk-Counter values for each candidate SN. Within the list of PSCells suggested by the source SN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR RRCReconfiguration** message contained in the SN Addition Request Acknowledge message with the prepared PSCell ID(s). For each prepared PSCell, the candidate SN also decides the list of PSCell(s) and associated execution conditions proposed for the following execution of subsequent CPAC. If data forwarding is needed, the candidate SN provides data forwarding addresses to the MN. The candidate SN may also propose data forwarding to the MN or other candidate SN(s) for subsequent CPAC. The candidate SN includes the indication of the complete or delta RRC configuration with respect to the SCG reference configuration. For the prepared PSCell(s) and the proposed PSCell(s) for the following execution of subsequent CPAC, the candidate SN can either accept or reject each of the candidate cells suggested by the source SN, i.e. it cannot configure any alternative candidates.
The MN may select one of the candidate SN(s) and requests providing the reference SCG configuration as part of the SN Addition procedure. Once obtained, the MN provides the reference configuration to other candidate SN(s).
Step 4.
For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message to the candidate SN(s).
Step 5/6.
The MN may indicate the candidate PSCells accepted by each candidate SN to the source SN via SN Modification Request message before it configures the UE, e.g., when not all candidate PSCells were accepted by the candidate SN(s). If requested, the source SN sends an SN Modification Request Acknowledge message and if needed, provides an updated measurement configuration and/or the execution conditions for the initial execution of subsequent CPAC to the MN.
For each candidate SN, the MN may initiate the SN Modification procedures towards the candidate SN to inform the prepared PSCells in other candidate SN(s), e.g., when not all proposed PSCells by this candidate SN for the following execution of subsequent CPAC were prepared by the candidate SN(s). If requested, the candidate SN sends an SN Modification Request Acknowledge message and if needed, provides the updated candidate SCG configuration(s) and/or the list of PSCell(s) and the associated execution conditions for the following execution of subsequent CPAC to the MN.
Step 7.
The MN sends to the UE an RRCReconfiguration message including the subsequent CPAC configuration, i.e. a list of RRCReconfiguration* messages and associated execution conditions for the subsequent CPAC, in which each RRCReconfiguration* message contains the SCG configuration in the RRCReconfiguration** message received from one of the candidate SN(s) in steps 2 and 3, and possibly an MCG configuration. Besides, the RRCReconfiguration message can also include an updated MCG configuration, as well as the NR RRCReconfiguration*** message generated by the source SN, e.g., to configure the required conditional measurements. The RRCReconfiguration message also includes a security update configuration and may also include a reference configuration.
Step 8.
The UE applies the RRCReconfiguration message received in step 7, stores the subsequent CPAC configuration and replies to the MN with an RRCReconfigurationComplete message, which can include an NR RRCReconfigurationComplete*** message. In case the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message, it performs the reconfiguration failure procedure.
Step 9/10.
If an SN RRC response message is included, the MN informs the source SN with the SN RRCReconfigurationComplete*** message via SN Change Confirm message. If step 5 and 6 towards the source SN are skipped, the MN will indicate the candidate PSCells accepted by each candidate SN to the source SN in the SN Change Confirm message.
The MN sends the SN Change Confirm message towards the source SN to indicate that subsequent CPAC is prepared, and in such case the source SN continues providing user data to the UE. If early data forwarding is applied, the MN informs the source SN the data forwarding addresses as received from the candidate SN(s), the source SN, if applicable, together with the Early Status Transfer procedure, starts early data forwarding. The PDCP SDU forwarding may take place during early data forwarding. In case multiple candidate SNs are prepared, the MN includes a list of Target SN ID and list of data forwarding addresses to the source SN.
Step 11.
The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies RRCReconfiguration* message corresponding to the selected candidate PSCell, and sends an MN RRCReconfigurationComplete* message, including an RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. The RRCReconfigurationComplete* message may also include the sk-Counter value associated with the selected candidate PSCell if a new sk-Counter value is selected.
Step 12.
The MN informs the SN of the selected candidate PSCell (i.e. the selected candidate SN) that the UE has completed the reconfiguration procedure successfully via SN Reconfiguration Complete message, including the RRCReconfigurationComplete** message. If the sk-Counter value is received by the RRCReconfigurationComplete* message, the MN also indicates the received sk-Counter value to the SN.
Step 13.
The UE performs synchronisation towards the PSCell indicated in the RRCReconfiguration* message applied in step 11. The order the UE sends the MN RRCReconfigurationComplete* message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Reconfiguration procedure.
Step 14/15/16.
If the source SN is configured as a candidate SN, the MN triggers the MN initiated SN Modification procedure to inform the source SN to stop providing user data to the UE, to switch to the prepared state, and if applicable, to allow provisioning of new data forwarding addresses based on the data forwarding proposals of the MN and the selected candidate SN. If applicable, the MN triggers the Xn-U Address Indication procedure to inform the source SN the address of the SN of the selected candidate PSCell, to start late data forwarding. If the source SN is not configured as a candidate SN, the MN triggers the MN initiated SN Release procedure to inform the source SN to stop providing user data to the UE, and triggers the Xn-U Address Indication procedure to inform the source SN the address of the SN of the selected candidate PSCell and if applicable, starts late data forwarding.
Step 17/18.
If PDCP termination point is changed for bearers using RLC AM, the SN sends the SN Status Transfer message to MN, which the MN sends then to the SN of the selected candidate PSCell, if needed.
Step 19.
If applicable, data forwarding from the source SN takes place. It may be initiated as early as the the source SN receives the early data forwarding address in step 10.
Step 20.
The source SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2.
Step 21-25.
If applicable, a PDU Session path update procedure is triggered by the MN.
Step 26-27.
If data forwarding is needed, the MN may send the Xn-U Address Indication message to the selected candidate SN. The SN may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an Early Status Transfer message to the MN.
SN initiated intra-SN subsequent CPAC with MN involvement
This procedure is initiated by the SN for intra-SN subsequent CPAC with MN involvement.
Copy of original 3GPP image for 3GPP TS 37.340, Fig. 10.20-3: Intra-SN subsequent CPAC - SN initiated with MN involvement
Up
Figure 10.20-3 shows an example signalling flow for intra-SN subsequent CPAC initiated by the SN with MN involvement:
Step 1.
The SN initiates the conditional SN modification procedure by sending the SN Modification Required message, which contains an intra-SN subsequent CPAC initiation indication. The message includes a list of PSCell(s) prepared and associated execution conditions proposed for the following execution of subsequent CPAC, and for each prepared PSCell, the SN decides SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR RRCReconfiguration** message contained in the SN Modification Required message. The SN may include an indication of that the SCG radio resource configuration is a complete or delta RRC configuration with respect to the reference SCG configuration.
Step 2/3.
The MN initiated SN Modification procedure may be triggered by SN Modification Required message, e.g. when an SN security key change needs to be applied.
Step 4.
The MN sends to the UE an RRCReconfiguration message including the subsequent CPAC configuration, i.e. a list of RRCReconfiguration* messages and associated execution conditions, in which each RRCReconfiguration* message contains the SCG configuration in the RRCReconfiguration** message received from the SN in step 1 and possibly an MCG configuration. Besides, the RRCReconfiguration message can also include an updated MCG configuration, as well as the NR RRCReconfiguration*** message generated by the SN, e.g., to configure the required conditional measurements. The RRCReconfiguration message also includes execution conditions for the following execution of the subsequent CPAC, and may also include a reference configuration and a security update configuration.
Step 5.
The UE applies the RRCReconfiguration message received in step 4, stores the subsequent CPAC configuration and replies to the MN with an RRCReconfigurationComplete message, which can include an NR RRCReconfigurationComplete*** message. In case the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message, it performs the reconfiguration failure procedure.
Step 6.
If an SN RRC response message is included, the MN informs the SN with the SN RRCReconfigurationComplete*** message via SN Modification Confirm message. The MN sends the SN Modification Confirm message towards the SN to indicate that subsequent CPAC is prepared.
Step 7.
The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies RRCReconfiguration* message corresponding to the selected candidate PSCell, and sends an RRCReconfigurationComplete* message, including an RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the selected candidate PSCell. The UE keeps the configured subsequent CPAC configuration and evaluates the execution conditions of other candidate PSCells after completion of the subsequent CPAC execution.
Step 8.
If the RRC connection reconfiguration procedure was successful, the MN informs the SN of the selected candidate PSCell via SN Reconfiguration Complete message, including the SN RRCReconfigurationComplete** message.
Step 9.
The UE synchronizes to the PSCell indicated in the RRCReconfiguration* message applied in step 7.
Step 10.
If PDCP termination point is changed for bearers using RLC AM, and when RRC full configuration is not used, the SN Status Transfer takes place between the MN and the SN (Figure 10.20-3 depicts the case where a bearer context is transferred from the SN to the MN).
Step 11.
If applicable, data forwarding between MN and the SN takes place (Figure 10.20-3 depicts the case where a user plane resource configuration related context is transferred from the SN to the MN).
Step 12.
The SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2.
Step 13.
If applicable, a PDU Session path update procedure is performed.
SN initiated intra-SN subsequent CPAC without MN involvement (SRB3 is not used)
The procedure follows the steps described in Figure 10.3.2-5.
SN initiated intra-SN subsequent CPAC without MN involvement (SRB3 is used)
The procedure follows the steps described in Figure 10.3.2-3a.
Up

Up   Top   ToC