Patent Application
20230379788
This disclosure relates to cancellation of a conditional Primary Secondary-Cell (PSCell) change.
Conditional Handover (CHO)
Two new work items for mobility enhancements in LTE and NR have started in 3GPP in release 16. The main objectives of the work items are to improve the robustness at handover and to decrease the interruption time at handover.
One problem related to robustness at handover is that the HO Command (RRCConnectionReconfiguration with mobilityControlInfo and RRCReconfiguration with a reconfigurationWithSync field) is normally sent when the radio conditions for the UE are already quite bad. That may lead to that the HO Command may not reach the UE in time if the message is segmented or there are retransmissions.
In LTE and NR, different solutions to increase mobility robustness have been discussed in the past. One solution discussed in NR is called “conditional handover” or “early handover command.” In order to avoid the undesired dependence on the serving radio link upon the time (and radio conditions) where the UE should execute the handover, the possibility to provide RRC signaling for the handover to the UE earlier should be provided. To achieve this, it should be possible to associate the HO command with a condition for example based on radio conditions possibly similar to the ones associated with an A3 event, where a given neighbour becomes X db better than target. As soon as the condition is fulfilled, the UE executes the handover in accordance with the provided handover command.
Such a condition could, for example, be that the quality of the target cell or beam becomes X dB stronger than the serving cell. The threshold Y used in a preceding measurement reporting event should then be chosen lower than the one in the handover execution condition. This allows the serving cell to prepare the handover upon reception of an early measurement report and to provide the RRCConnectionReconfiguration with mobilityControlInfo at a time when the radio link between the source cell and the UE is still stable. The execution of the handover is done at a later point in time (and threshold), which is considered optimal for the handover execution.
While the UE evaluates the condition, it should continue operating per its current RRC configuration, i.e., without applying the conditional HO command. When the UE determines that the condition is fulfilled, it disconnects from the serving cell, applies the conditional HO command and connects to the target cell. These steps are equivalent to the current, instantaneous handover execution.
Conditional handover is described in stage 2, TS 38.300 in chapter 9.2.3.4., a portion of which is reproduced below:
TS 38.300 Chapter 9.2.3.4
9.2.3.4 Conditional Handover
9.2.3.4.1 General
A Conditional Handover (CHO) is defined as a handover that is executed by the UE when one or more handover execution conditions are met. The UE starts evaluating the execution condition(s) upon receiving the CHO configuration, and stops evaluating the execution condition(s) once the execution condition(s) is met.
The following principles apply to CHO:
9.2.3.4.2 C-Plane Handling
As in intra-NR RAN handover, in intra-NR RAN CHO, the preparation and execution phase of the conditional handover procedure is performed without involvement of the 5GC; i.e. preparation messages are directly exchanged between gNBs. The release of the resources at the source gNB during the conditional handover completion phase is triggered by the target gNB.
End TS 38.300 Chapter 9.2.3.4
Cancellation in Conditional Handover
In 3GPP rel-16, the possibility for a candidate target node for conditional handover to cancel one or multiple candidate target cells already prepared for a CHO has been standardized. A new Conditional Handover Cancel procedure was added to 3GPP TS 38.423, a portion of which is reproduced below:
8.2.9.1 General
The Conditional Handover Cancel procedure is used to enable a target NG-RAN node to cancel an already prepared conditional handover. The procedure uses UE-associated signalling.
The target NG-RAN node initiates the procedure by sending the CONDITIONAL HANDOVER CANCEL message to the source NG-RAN node. The target NG-RAN node shall indicate the reason for cancelling the conditional handover by means of an appropriate cause value. At the reception of the CONDITIONAL HANDOVER CANCEL message, the source NG-RAN node shall consider that the target NG-RAN node is about to remove any reference to, and release any resources previously reserved for candidate cells associated to the UE-associated signalling identified by the Source NG-RAN node UE XnAP ID IE and the Target NG-RAN node UE XnAP ID IE. If the Candidate Cells To Be Cancelled List IE is included in CONDITIONAL HANDOVER CANCEL message, the source NG-RAN node shall consider that only the resources reserved for the cells identified by the included NG-RAN CGI are about to be released.
8.2.9.3 Unsuccessful Operation
Not applicable.
8.2.9.4 Abnormal Conditions
If the CONDITIONAL HANDOVER CANCEL message refers to a context that does not exist, the source NG-RAN node shall ignore the message.
If one or more candidate cells in the Candidate Cells To Be Cancelled List IE included in the CONDITIONAL HANDOVER CANCEL message were not prepared using the same UE-associated signaling connection, the source NG-RAN node shall ignore those non-associated candidate cells.
End 3GPP TS 38.423
PSCell Change
The UE can be configured with Dual Connectivity, communicating both via an MCG (Master Cell Group) and an SCG (Secondary Cell Group). When the UE is configured with dual connectivity, the UE is configured with two MAC entities: one MAC entity for the MCG and one MAC entity for the SCG. In Multi-Radio Dual Connectivity (MR-DC) the cell groups are located in two different logical nodes, i.e. different NG-RAN nodes, possibly connected via a non-ideal backhaul, one providing NR access and the other one providing either E-UTRA or NR access. One node acts as the MN (Master Node) and the other as the SN (Secondary Node). The MN and SN are connected via a network interface and at least the MN is connected to the core network.
The operation in MR-DC involves different reconfiguration procedures, like secondary node addition, secondary node modification, secondary node release and secondary node change.
NOTE 4: The order the S-SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN/T-SN is not defined. The SgNB may send the report when the transmission of the related bearer is stopped.
Conditional PSCell Change (CPC)
A solution for Conditional PSCell Change (CPC) procedure was standardized in Rel-16. Therein a UE operating in Multi-Radio Dual Connectivity (MR-DC) receives in a conditional reconfiguration one or multiple RRC Reconfiguration(s) (e.g., an RRCReconfiguration message) containing an SCG configuration (e.g., an secondaryCellGroup of IE CellGroupConfig) with a reconfigurationWithSync that is stored and associated with an execution condition (e.g., a condition like an A3/A5 event configuration), so that one of the stored messages is only applied upon the fulfilment of the execution condition; for example associated with the serving PSCell, upon which the UE would perform PSCell change (in case it finds a neighbour cell that is better than the current SpCell of the SCG).
The following principles apply to CPC:
In Rel-16, CPC was limited to intra-node CPC i.e. for a UE configured with MR-DC, the SN determines to configure CPC and provides a CPC configuration to the UE (e.g. via the MN), but the target candidate PSCell is a cell that is also associated to the same SN i.e. both source PSCell and target candidate PSCell(s) are associated to the S-SN. Also, only an SN-initiated CPC with or without MN involvement is supported.
In this case CPC is configured at the UE by modifying the SCG configuration via SRB3, so the SN initiated modification without MN involved procedure is used, as shown above. The SN can decide whether the Random Access procedure is required. Some of the steps shown in
The UE completes the CPC execution procedure by sending an RRCReconfigurationComplete message to the new PSCell if the SRB3 is configured.
This procedure is used in case SRB3 is not configured. The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is not used; and, in this particular case, the configuration contains an NR SCG RRCReconfiguration including the IE ConditionalReconfiguration, which is part of the SCG Configuration and includes an RRCReconfiguration to be stored, per target candidate PSCell, and a condition configuration (on or two measId(s) pointing to a measurement configuration). The steps shown in
In rel-16 CPC will be supported, but in rel-17 also PSCell Addition will be included, i.e., Conditional PSCell Addition/Change (CPAC). In rel-16 only intra-SN CPC without MN involvement is standardized. Inter SN PSCell CPC and CPC with MN involvement will be included in rel-17.
As described above, in rel-16 only intra-SN case without MN involvement for CPC is supported, i.e., where S-SN and T-SN are the same node in picture 10.5.1-2 from TS 37.340. That means that the cell is changed, but both the old and the new cell are in the same node.
A problem that the disclosure addresses relates to a new scenario to be supported in Rel-17, which is when a UE is operating in Multi-Radio Dual Connectivity (MR-DC), i.e., having a connection with a Master Node (MN) and a Secondary Node (SN), and the UE is configured with an inter-SN, SN initiated Conditional PSCell Change (CPC), i.e. when at least one target candidate PSCell in CPC is associated with a target candidate SN (T-SN) that is not the same node as the source SN (S-SN) to which the UE is connected. In existing solutions, there is no possibility for the target candidate SN or the S-SN to cancel one or multiple candidate PSCells. In the existing standard, there is no signalling and associated procedures supporting inter-SN, MN initiated Conditional PSCell Change (CPC).
Accordingly, certain challenges presently exist. That is, for example, there is currently no possibility for the S-SN to cancel one or multiple candidate PSCells. Methods for an MN to cancel a previously configured Conditional PSCell Addition (CPA) have been described, but the difference with this case for CPC is that at least three nodes are involved, the S-SN, the MN, and a target candidate SN (at least one). There is currently no possibility for the S-SN to cancel CPC.
The problem when three nodes are involved is that it is the target candidate SN that reserves resources for a UE that may later perform conditional PSCell change from the S-SN towards that target candidate SN. The target candidate SN reserves resources such as C-RNTI, RACH (in case of contention free RACH is configured), transmission power, bandwidth, and make sure the services/bearers the UE is running are supported in target with a minimum QoS, etc. for the UE, but it has no knowledge about the current UE behavior as the UE still resides in the S-SN.
If the S-SN identifies that the UE is, for example, moving away from the candidate target cell or has performed CPC to a cell in a different SN, the S-SN currently has no possibility to inform the T-SN that it may release the resources for the UE.
Such a problem is specific for CPC and does not exist in conventional PSCell change. The reason is that in legacy, when PSCell is prepared, the UE is expected to access the PScell within a short time whereas in CPC, as explained above, the UE may come some time later or not come.
Accordingly, in one aspect there is provided a method performed by an MN for cancellation of a CPC. The method includes transmitting to a T-SN a request for a CPC configuration. The method also includes receiving a response to the request. The method further includes receiving a cancellation indication transmitted by a S-SN, the cancellation indication indicating that the CPC configuration is to be cancelled.
In another aspect there is provided a method performed by a S-SN for cancellation of a CPC. The method includes the S-SN transmitting a cancellation indication to a master node indicating that a CPC is to be cancelled.
In another aspect there is provided a method performed by a T-SN for cancellation of a CPC. The method includes the T-SN receiving a request transmitted by an MN to prepare a CPC configuration. The method also includes transmitting to the MN a response to the request. The method further includes receiving a cancellation indication transmitted by the MN, the cancellation indication indicating that the CPC configuration is to be cancelled.
In another aspect there is provided a computer program comprising instructions which when executed by processing circuitry of a network node causes the network node to perform any of the methods disclosed herein. In one embodiment, there is provided a carrier containing the computer program wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.
In another aspect there is provided a network node that is configured to perform the methods disclosed herein. The network node may include memory and processing circuitry coupled to the memory.
The various embodiments described herein address one or more of the issues disclosed herein. The embodiments may provide one or more of the following technical advantage(s). Certain embodiments make it possible for the S-SN to cancel a previously configured conditional PSCell Change towards an SN target candidate, e.g., if the UE has moved away from the target candidate cell, if the source wants to release a UE, or in case the UE has executed CPC to another target candidate.
The disclosure describes the cancellation of one or multiple candidate cells (sometimes called target candidate cells) belonging to (or associated with) a target candidate SN (T-SN), after a successful SN Addition preparation
The disclosure refers to a UE operating in Multi-Radio Dual Connectivity (MR-DC) according to the NR specifications e.g., TS 37.340, TS 38.331, etc. The disclosure refers to a first network node (NN) operating as a Master Node (MN), e.g., having a Master Cell Group (MCG) configured to the UE and/or an MN-terminated bearer; that MN can be a gNodeB, or a Central Unit gNodeB (CU-gNB) or an eNodeB, or a Central Unit eNodeB (CU-gNB), or any network node. The disclosure also refers to a second network node operating as a Secondary Node (SN), or Source Secondary Node (S-SN) e.g. having a Secondary Cell Group (SCG) configured to the UE and/or an SN-terminated bearer; that SN can be a gNodeB, or a Central Unit gNodeB (CU-gNB) or an eNodeB, or a Central Unit eNodeB (CU-gNB), or any network node. Notice that MN, S-SN and T-SN may be from the same or different Radio Access Technologies (and possibly be associated to different Core Network nodes).
The disclosure refers to a target candidate SN, or target SN (T-SN) candidate, as the network node (e.g. gNodeB) that is prepared during the CPC procedure and that creates an RRC Reconfiguration message with an SCG configuration to be provided to the UE and stored, with an execution condition, wherein the UE only applies the message upon the fulfilment of the execution condition. That target candidate SN is associated to one or multiple target candidate cell(s) that the UE can be configured with. The UE then can execute the condition and accesses one of these target candidate cells, associated with a target candidate SN that becomes the T-SN after execution (i.e. upon fulfilment of the execution condition).
The disclosure refers to a Conditional PSCell Change (CPC) and/or Conditional PSCell Addition (CPA) and/or Conditional PSCell Change/Addition (CPAC) configuration and procedures (like CPAC execution). Other terms may be considered as synonyms such as conditional reconfiguration, or Conditional Configuration (since the message that is stored and applied upon fulfilment of a condition is an RRCReconfiguration or RRCConnectionReconfiguration). Terminology wise, one could also interpret conditional handover (CHO) in a broader sense, also covering CPC (Conditional PSCell Change) or CPAC (Conditional PSCell Addition/Change) procedures.
The configuration of CPC can be done using the same IEs as conditional handover, which may be called at some point conditional configuration or conditional reconfiguration. The principle for the configuration is the same with configuring triggering/execution conditions and a reconfiguration message to be applied when the triggering conditions are fulfilled. The configuration IEs from TS 38.331 are shown and described below:
The ConditionalReconfiguration IE, shown in table below, is used to add, modify and release the configuration of conditional configuration.
The CondConfigId IE, which is shown in the table below, is used to identify a CHO or CPC configuration.
The CondConfigToAddModList IE, which is shown in the table below, concerns a list of conditional configurations to add or modify, with for each entry the cho-ConfigId and the associated condExecutionCond and condRRCReconfig.
Solutions for CPC configuration (SN-generated CPC and MN-generated CPC)
The current disclosure concerns S-SN-initiated CPC cancelling. However, it is assumed that there may be different ways to realize the CPC configuration between MN, S-SN and a target candidate (which is to be cancelled).
SN-Initiated CPC
In one embodiment, illustrated in
In another embodiment, illustrated in
MN-Initiated CPC
In MN-initiated CPC, the difference is that the first step is initiated by the MN. However, an SN Addition procedure is anyways required between the MN and a target candidate T-SN. Even if this is an MN-initiated CPC, in principle the CPC configuration can be created by the SN or by the MN. For a solution where the SN generates the CPC configuration, the MN needs to request the SN to generate the configuration, as in the embodiment for SN-initiated (see
For a solution where the MN generates CPC configuration, the MN does not need to request the SN to generate the configuration as in the embodiment for SN-initiated as shown in
In the different embodiment presented above for CPC configuration, regardless if SN-initiated or MN-initiated CPC, an aspect related to the disclosure is that the S-SN determines to cancel CPC. Then, the S-SN sends an indication of CPC cancelling to the MN. Upon reception the MN sends an indication of CPC cancelling to a target candidate SN configured with CPC.
The method comprises different embodiments for S-SN initiated cancel of conditional PSCell Change (CPC), in terms of inter-node signaling and inter-node procedures, for the cases inter-SN MN-initiated conditional PSCell Change and inter-SN SN-initiated conditional PSCell Change.
In one set of embodiments, a network node operating as Source Secondary Node (S-SN), decides to cancel the configuration of CPC for at least a given UE operating in MR-DC. The configuration of Conditional PSCell Change (CPC) for a UE operating in MR-DC has previously been initiated by a network node operating as Master Node (MN) and the MN has built the message towards the UE containing the CPC configuration. The determination to cancel CPC may be based on measurements reports received from the UE. Upon determining to cancel CPC, the MN may initiate a procedure according to the following.
Option A: The S-SN Cancels MN-Initiated CPC
In this option, the MN initiates the configuration of conditional PSCell Change (CPC). The final message to the UE containing the conditional reconfiguration may either be generated in the MN or in the S-SN.
If the message including CPC configuration is generated in the MN (CPC not provided as an SCG configuration to the UE) the message to be applied upon execution (i.e., when the conditions are fulfilled) contains an SCG configuration that is sent from the T-SN to the MN, so the MN adds the conditions and sends the message to the UE. This option is shown in
If the message including CPC configuration is generated in the S-SN (CPC provided as an SCG configuration to the UE), the MN forwards the SCG configuration (to be applied upon execution by the UE) from the T-SN to the S-SN which adds the conditions and replies back to the MN with the message including the CPC configuration to the UE. The MN then generates an RRC Reconfiguration message including an SCG Reconfiguration (e.g. nr-scg field) wherein that SCG Reconfiguration includes the conditional reconfiguration (IE ConditionalReconfiguration).
The steps shown in
(Step 1-6) contains the configuration of CPC with the MN generating the reconfiguration message towards the UE where CPC is configured. The configuration may be done in a different way using different messages and/or different signalling flow, but it does not make any difference for this invention.
(Step 7) The node operating as Secondary Node (SN) sends an indication to the MN that CPC is to be cancelled (e.g. for at least a target candidate cell and/or node). The indication can contain a reconfiguration to the UE (e.g. transmitted in an RRC container), so that CPC target candidate(s) are removed and, a list of candidate cell(s) to be cancelled for CPC, indicated as part of the inter-node message (e.g. XnAP message).
In one option, the S-SN indicates the reason for cancelling the conditional PSCell change by means of an appropriate cause value. There may be different options on how that indication can be transmitted and actions associated to it. In a first option that indication can be an S-NODE MODIFICATION REQUIRED message including indication of cancellation of target candidate cells to the MN. The advantage is that the S-SN is indeed indicating to the MN that the UE's configuration is to be modified (as CPC configuration for at least one target candidate is to be removed). That option especially makes sense in the case CPC is an SCG configuration e.g. if the SN is the one generating the CPC configuration that is now being modified (i.e. at least one target candidate is being removed). The message to the MN contains an SCG RRCReconfiguration* message, releasing the CPC candidates. The MN uses the RRCReconfiguration* message and may add more MN related information when building the final message sent to the UE e.g. reconfiguring measurements, bearers, etc., especially if all candidates are being removed. The message to the MN also includes information of which target candidate cells and/or target candidate SNs are to be cancelled, so that the MN can indicate the cancelling to the correct target candidate SN and/or for the correct target candidate cell(s). The information may, e.g., be a list of cells or the identifiers (ID)s of the conditional reconfiguration for CPC. In the case of a cell list an addition issue may exists e.g. in case the UE is configured with CPC to the same cell as it is configured with CHO. Then the UE cannot know if it is the CHO or the CPC configuration that is to be cancelled. In that case the cell ID may be sent together with additional information, e.g. a CPC indication, a CHO indication, the measID for the conditional reconfiguration or some other indication.
Alternatively, that indication is an S-NODE RELEASE REQUIRED message including indication of cancellation of target candidate cells to the MN. The S-SN may send an S-NODE RELEASE REQUIRED message instead, containing similar information as in S-NODE MODIFICATION REQUIRED. In one sub-alternative, the S-NODE RELEASE REQUIRED message is used to release all CPC configurations, i.e., not a subset of the configured target candidate cells associated to that target candidate SN. The content of the messages and the actions between the network nodes described in the first option can also be included in this option. Alternatively, the SN may send a new message instead, e.g., a CPC CANCEL message, including indication of cancellation of target candidate cells to the MN. In one sub-option, if all target candidate cells associated to the target candidate SN receiving the message, the empty message (i.e. without a cell list) can indicate that. The content of the messages and the actions between the network nodes described in the first option can also be included in this option. Alternatively, the SN may send a CHO CANCEL message, including indication of cancellation of target candidate cells to the MN for CPC. The content of the messages and the actions between the network nodes described in the first option can also be included in this option. In yet another alternative, the request does NOT contain an SCG RRC Reconfiguration including the cells to be removed. Instead, this message in step 7 contains just the indication to the MN so the MN can cancel CPC with the target candidate SNs. Once that step is performed by the MN, and the MN possibly receives a confirmation from the target candidate SN, the MN indicates that to the S-SN, so that the S-SN can generate the CPC configuration (i.e., the SCG RRC Reconfiguration with CPC) including the CPC target candidate cells to be removed.
(Step 8) Upon reception of the indication from the S-SN to cancel CPC (towards a target candidate SN), the MN determines which target candidate SN(s) are to be CPC cancelled. Upon that determination, the node operating as Master Node (MN) sends an indication to the determined target candidate SN that CPC is to be cancelled (for at least one of its target candidate cells). There may be different options on how the MN can indicate CPC cancel to a target candidate SN.
In one option, the MN sends an S-NODE MODIFICATION REQUEST message including indication of cancellation of cells to the T-SN (e.g. a list of cells, a list of cell identifiers, a list of other type of identifiers, etc.). Alternatively, the MN may send an S-NODE RELEASE REQUEST message instead, containing similar information as in S-NODE MODIFICATION REQUEST. Notice that the legacy S-NODE RELEASE REQUEST indicates the complete release of configurations while according to this option, the message may contain an indication indicating that this is for releasing CPC for at least one target candidate cell. In case the MN determines to release all target candidate cells for a given target candidate SN, the message can be transmitted without any additional indication so that upon reception the target candidate SN releases all CPC configurations, stored context for that UE, release resources, etc.
Alternatively, the MN may send a new message instead, e.g. a CPC CANCEL message, including indication of cancellation of target candidate cells to the target candidate SN. In one sub-option, if all target candidate cells associated to the target candidate SN receiving the message, the empty message (i.e. without a cell list) can indicate that. The content of the messages and the actions between the network nodes described in the first option can also be included in this option. Alternatively, the MN may send a new message instead, e.g. a SN ADDITION CANCEL message, including indication of cancellation of target candidate cells to the target candidate SN. In one sub-option, if all target candidate cells associated to the target candidate SN receiving the message, the empty message (i.e. without a cell list) can indicate that. The content of the messages and the actions between the network nodes described in the first option can also be included in this option.
(Step 9) The node operating as target candidate SN (optionally) acknowledges the cancellation of CPC cells in the T-SN by transmitting to the MN an S-NODE MODIFICATION REQUEST ACKNOWLEDGE or alternatively by transmitting to the MN an S-NODE RELEASE REQUEST ACKNOWLEDGE message (or any other response message, transmitted by the T-SN in response to a request or indication to cancel CPC). That may be useful in case the target candidate SN determines to cancel more cells that the ones requested by the MN, to that response message may indicate which target candidate cells have been effectively cancelled at the target candidate SN. There is also an option that the target candidate SN does not acknowledge the cancellation of CPC (a Class 2 procedure), it is taken for granted that the cancellation is successful in the target candidate SN.
In yet another alternative, in case the request from the S-SN to the MN to cancel CPC did NOT contain an SCG RRC Reconfiguration including the cells to be removed, upon acknowledging that CPC has been cancelled towards a target candidate SN (e.g., by reception of a message from the T-SN), the MN indicates that to the S-SN, so that the S-SN can generate the CPC configuration (i.e., the SCG RRC Reconfiguration with CPC) including the CPC target candidate cells to be removed. At this point the MN has a CPC configuration from the S-SN for removing CPC in the UE with an RRC Reconfiguration.
In the previous steps, it has been assumed that the SN generates the CPC configuration as an SCG configuration, even if this is an MN-initiated CPC. However, in another alternative, it is the MN that generates the CPC configuration. The difference if it is the MN generating CPC is that the configuration towards the UE to remove the CPC target candidates is also generated by the MN. Hence, all previous steps remain the same, except the inclusion of SCG reconfiguration from the SN to the MN and/or requests/indications from the MN to the SN for the SN to generate an SCG RRC Reconfiguration to remove CPC candidates in the UE. At the reception of the acknowledge message, the MN considers that the target candidate SN is about to remove any reference to, and release any resources previously reserved for candidate cells associated to the UE-associated signalling identified by the MN node UE XnAP ID IE and the target candidate SN NG-RAN node UE XnAP ID IE.
(Step 10) The node operating as Master Node (MN) sends an RRCReconfiguration message to the UE, containing the new UE configuration where the previously configured CPC cells have been removed from the configuration. Step 10 and 11 may also be done before step 8 and 9 or in parallel with step 8 and 9.
(Step 11) The UE completes the reconfiguration (i.e. remove the indicated CPC candidates) and informs the MN in an RRCReconfigurationComplete message.
An example in RRC 38.331 is shown below with the overall procedure, for the case CPC is an MN-generated configuration (i.e. the IE ConditionalReconfiguration is provided to the UE in an RRCReconfiguration message including the condReconfigToRemoveList).
The ConditionalReconfiguration IE is used to add, modify and release the configuration of conditional reconfiguration.
The UE actions are defined as follows. The UE shall: for each condReconfigId value included in the condReconfigToRemoveList that is part of the current UE conditional reconfiguration in VarConditionalReconfig: remove the entry with the matching condReconfigd from the VarConditionadReconfig.
Below is an example implementation of updated S-NODE RELEASE REQUIRED and sending of conditional reconfiguration ID. This message is sent by the S-NG-RAN node to request the release of resources for a specific UE at the S-NG-RAN node.
Direction: S-NG-RAN node NM-NG-RAN node.
9.2.3.x Conditional Reconfiguration ID
This IE is defined in TS 38.331 [10] in CondReconfigID and is used to uniquely identify a CHO, CPC or CPA configuration.
S-NG-RAN Node Initiated S-NG-RAN Node Release
This procedure, illustrated in
The S-NG-RAN node may start data forwarding and stop providing user data to the UE upon reception of the S-NODE RELEASE CONFIRM message, except if the S-NODE RELEASE REQUIRED was sent for a CPC cancelling.
If the S-NG-RAN node to M-NG-RAN node Container IE is included in the S-NODE RELEASE REQUIRED message, the M-NG-RAN node may use the contained information to apply delta configuration. In the case of CPC cancellation, it may contain the configuration to remove CPC target cell candidates.
Option B1:
In this option, the S-SN cancels SN-initiated CPC. Also in this option, illustrated in
The message can be sent directly to the UE in case SRB3 is configured, otherwise the message is transferred to the MN, which provided the message to the UE (in an SCG RRC container). For option B some different variants of when the UE reconfiguration is done is shown. These different variants exist also for option A, i.e., the UE reconfiguration may take place before or after informing T-SN about the cancellation also in option A. The new Information message in step 15 in option B2 and the new Error message in step 15 in option B3 may be sent in option A also. The reconfiguration towards the UE is in this option B1 done first, before informing T-SN about the cancellation. The steps shown in
(Step 1-8) contains the configuration of CPC with the S-SN building the reconfiguration message towards the UE where CPC is configured (RRCReconfiguration* as shown in the figure, in step 5, to be provided to the UE within an nr-scg field as a container within another RRCReconfiguration from the MN, as in step 6). The configuration may be done in a different way using different messages and/or different signalling flow, but it does not make any difference for this invention.
(Step 9) The node operating as Secondary Node (SN) sends a message including an indication of cancellation of target candidate cells (e.g. target candidate PSCells) to the MN.
The message to the MN contains an SCG RRCReconfiguration* message to be sent to the UE, releasing the CPC candidates. The message to the MN also includes information of which cells where CPC is cancelled, so that the MN can forward the release request to the correct target candidate SN. The information may e.g. be a list of cells or the ID of the conditional reconfiguration. In one option the message is an S-NODE MODIFICATION REQUIRED message including indication of cancellation of target candidate cells (e.g. target candidate PSCells) to the MN. In another option, an S-NODE RELEASE REQUIRED with a list of target candidate cells to be cancelled, or conditional reconfiguration IDs are sent from the S-SN.
(Step 10) The node operating as Master Node (MN) sends an RRCReconfiguration message to the UE (including the RRCReconfiguration* as the SCG RRC container), containing the new UE configuration where the previously configured CPC cells have been removed from the configuration within the RRCReconfiguration* in the SCG RRC container (in the case we assume that CPC is generated at the SN, as in Rel-16 CPC intra-node solution).
(Step 11) The UE completes the reconfiguration and informs the MN in an RRCReconfigurationComplete message.
(Step 12) The node operating as Master Node (MN) sends a message, possibly including an SCG complete message to the S-SN (RRCReconfigurationComplete*), indicating that the configuration has been provided to the UE i.e. indicating that the UE has removed the CPC configurations as indicated by the S-SN in previous steps. In one option the message is an SN MODIFICATION CONFIRM (which is a response to step 9)
(Step 13) The node operating as Master Node (MN) sends a message to a target candidate SN including an indication of cancellation of target candidate cells (e.g., target candidate PSCells) to at least one target candidate SN. Upon reception the target candidate SN determines which target candidate cells are to be cancelled/removed for CPC configuration.
In one option that message is an S-NODE MODIFICATION REQUEST message including indication of cancellation of cells to the T-SN, e.g., a list of cells for which CPC configuration is to be cancelled. In one option that message is an S-NODE RELEASE REQUEST message including indication of cancellation of cells to the T-SN, e.g., a list of cells for which CPC configuration is to be cancelled. In another option, a new message, e.g., CPC CANCEL is sent to the target candidate SN. In one option, the node operating as target candidate SN sends an acknowledgement of the cancellation of CPC cells in the T-SN by responding the request to cancel with a message. In other words, in this option a class 1 procedure of an inter-node control protocol (like XnAP) would be used for the cancelling of CPC from the MN to a target candidate SN.
(Step 14) The target candidate (optionally) sends an acknowledgement that the resources have been removed (a Class 1 procedure). In case of a Class 2 procedure (another option), this step does not exist.
An example implementation in TS 38.423 is shown below.
In step 9, additional information related to what cells that are cancelled, needs to be transferred to the MN outside the SCG configuration, so that the MN knows which SN to inform about the cancellation of CPC. Below the target cell IDs are added (highlighted) in the S-NODE MODIFICATION REQUIRED message. Another alternative would be that the conditional reconfiguration IDs are transferred instead.
S-Node Modification Required
This message is sent by the S-NG-RAN node to the M-NG-RAN node to request the modification of S-NG-RAN node resources for a specific UE. Direction: S-NG-RAN node→M-NG-RAN node.
In another embodiment, the cancellation information, e.g. the list of cells to be cancelled or the conditional reconfiguration ID, is contained in S-NODE RELEASE REQUIRED instead of S-NODE MODIFICATION REQUIRED and S-NODE RELEASE REQUEST instead of S-NODE MODIFICATION REQUEST.
Option 1B2:
In this option, the S-SN cancels SN-initiated CPC, and UE reconfiguration is done after T-SN is informed.
Also, in this option the S-SN initiates the configuration of conditional PSCell Change (CPC) and the final message sent to the UE with the conditional reconfiguration (for CPC) is built in S-SN (i.e. the IE ConditionalReconfiguration is provided within an SCG RRC Reconfiguration e.g. nr-scg). The message can be sent directly to the UE in case SRB3 is configured, otherwise the message is transferred to the MN, which provides the message to the UE (in an SCG RRC Reconfiguration, like the field nr-scg within an MN built message). Later, the S-SN decides/determines to cancel the configuration of CPC (and indicates that to the MN so the MN can cancel CPC towards a target candidate SN). The reconfiguration of the UE is in this option done after informing the target candidate SN about the cancellation.
(Step 1-8) contains the configuration of CPC with the S-SN building the reconfiguration message towards the UE where CPC is configured (RRCReconfiguration* as shown in the figure, in step 5, to be provided to the UE within an nr-scg field as a container within another RRCReconfiguration from the MN, as in step 6). The configuration may be done in a different way using different messages and/or different signalling flow, but it does not make any difference for this invention.
(Step 9) The node operating as Secondary Node (SN) sends a message including an indication of cancellation of target candidate cells (e.g. target candidate PSCells) to the MN.
The message to the MN contains an SCG RRCReconfiguration* message to be sent to the UE, releasing the CPC candidates. The message to the MN also includes information of which cells where CPC is cancelled, so that the MN can forward the release request to the correct target candidate SN. The information may e.g. be a list of cells or the ID of the conditional reconfiguration. In one option the message is an S-NODE MODIFICATION REQUIRED message including indication of cancellation of cells to the MN. In another option, an S-NODE RELEASE REQUIRED with a list of target candidate cells to be cancelled, or conditional reconfiguration IDs are sent from the S-SN.
(Step 10) The node operating as Master Node (MN) sends a message to a target candidate SN including an indication of cancellation of target candidate cells (e.g. target candidate PSCells) to at least one target candidate SN. Upon reception the target candidate SN determines which target candidate cells are to be cancelled/removed for CPC configuration.
In one option that message is an S-NODE MODIFICATION REQUEST message including indication of cancellation of cells to the T-SN e.g. a list of cells for which CPC configuration is to be cancelled. In one option that message is an S-NODE RELEASE REQUEST message including indication of cancellation of cells to the T-SN e.g. a list of cells for which CPC configuration is to be cancelled. In another option, a new message, e.g. CPC CANCEL is sent to the target candidate SN.
(Step 11) In one option, the node operating as T-SN acknowledges the cancellation of CPC cells in the T-SN by responding the request to cancel with a message. In other words, in this option a class 1 procedure of an inter-node control protocol (like XnAP) would be used for the cancelling of CPC from the MN to a target candidate SN.
(Step 12) The node operating as Master Node (MN) sends an RRCReconfiguration message to the UE (including the RRCReconfiguration* as the SCG RRC container), containing the new UE configuration where the previously configured CPC cells have been removed from the configuration within the RRCReconfiguration* in the SCG RRC container (in the case we assume that CPC is generated at the SN, as in Rel-16 CPC intra-node solution).
(Step 13) The UE completes the reconfiguration and informs the MN in an RRCReconfigurationComplete message.
(Step 14) The MN informs the S-SN that the UE reconfiguration is complete.
(Step 15) In this step the MN informs the T-SN in a new message that the UE reconfiguration is complete and that the T-SN may release the resources. The resources cannot be released in T-SN before the UE has been reconfigured, as the UE may otherwise try to access the T-SN in case the conditions are fulfilled before the CPC is removed in the UE. This case is new, as three different nodes are involved, with one node initiating the cancellation of the conditional reconfiguration, one node reconfiguring the UE and a third node having the resources reserved for the UE. For conditional handover, only two nodes are involved in the cancellation, the source node and the target node. This new message may also be sent in MN-initiated CPC, option A above.
Option B3:
In this option, the S-SN cancels SN-initiated CPC, and UE reconfiguration is done after T-SN is informed. Also in this option, the S-SN initiates the configuration of conditional PSCell Change (CPC) and the final message sent to the UE with the conditional reconfiguration is built in S-SN. The message can be sent directly to the UE in case SRB3 is configured, otherwise the message is transferred to the MN, which forwards the message to the UE. Later, the S-SN decides to cancel the configuration of CPC. The reconfiguration of the UE is done after informing the T-SN about the cancellation. The difference compared to option B1 is that there is no message sent to the T-SN, informing it that the reconfiguration in the UE is completed. Instead an error message is sent in case the reconfiguration fails. Option B3 is illustrated in
(Step 1-8) contains the configuration of CPC with the S-SN building the reconfiguration message towards the UE where CPC is configured (RRCReconfiguration* as shown in the figure, in step 5, to be provided to the UE within an nr-scg field as a container within another RRCReconfiguration from the MN, as in step 6). The configuration may be done in a different way using different messages and/or different signalling flow, but it does not make any difference for this invention.
(Step 9) The node operating as Secondary Node (SN) sends a message including an indication of cancellation of target candidate cells (e.g. target candidate PSCells) to the MN.
The message to the MN contains an SCG RRCReconfiguration* message to be sent to the UE, releasing the CPC candidates. The message to the MN also includes information of which cells where CPC is cancelled, so that the MN can forward the release request to the correct target candidate SN. The information may e.g. be a list of cells or the ID of the conditional reconfiguration. In one option the message is an S-NODE MODIFICATION REQUIRED message including indication of cancellation of cells to the MN. In another option, an S-NODE RELEASE REQUIRED with a list of target candidate cells to be cancelled, or conditional reconfiguration IDs are sent from the S-SN.
(Step 10) The node operating as Master Node (MN) sends a message to a target candidate SN including an indication of cancellation of target candidate cells (e.g. target candidate PSCells) to at least one target candidate SN. Upon reception the target candidate SN determines which target candidate cells are to be cancelled/removed for CPC configuration.
In one option that message is an S-NODE MODIFICATION REQUEST message including indication of cancellation of cells to the T-SN e.g. a list of cells for which CPC configuration is to be cancelled. In one option that message is an S-NODE RELEASE REQUEST message including indication of cancellation of cells to the T-SN, e.g., a list of cells for which CPC configuration is to be cancelled. In another option, a new message, e.g., CPC CANCEL is sent to the target candidate SN.
(Step 11) In one option, the node operating as T-SN acknowledges the cancellation of CPC cells in the T-SN by responding the request to cancel with a message. In other words, in this option a class 1 procedure of an inter-node control protocol (like XnAP) would be used for the cancelling of CPC from the MN to a target candidate SN.
(Step 12) The node operating as Master Node (MN) sends an RRCReconfiguration message to the UE (including the RRCReconfiguration* as the SCG RRC container), containing the new UE configuration where the previously configured CPC cells have been removed from the configuration within the RRCReconfiguration* in the SCG RRC container (in the case we assume that CPC is generated at the SN, as in Rel-16 CPC intra-node solution).
(Step 13) The UE completes the reconfiguration and informs the MN in an RRCReconfigurationComplete message.
(Step 14) The MN informs the S-SN that the UE reconfiguration is complete.
(Step 15) In this step the MN informs the T-SN in a new message that the UE reconfiguration has failed and that the T-SN may not release the resources. The T-SN has likely kept the resourced for a while, possibly with a timer in the implementation, to ensure that the resources are not released too early. This new message may also be sent in MN-initiated CPC, option A above.
In some embodiments, wherein the cancellation indication transmitted by the S-SN comprises one of: an S-NODE MODIFICATION REQUIRED message, an S-NODE RELEASE REQUIRED message, a CPC CANCEL message, or a CHO CANCEL.
In some embodiments, process 1400 also includes releasing of resources associated with the CPC configuration that has been indicated to be cancelled and/or stopping a supervision timer.
In some embodiments, process 1400 also includes transmitting to the T-SN an indication that the CPC configuration is to be cancelled. In some embodiments, the indication transmitted to the T-SN comprises one of: an S-NODE MODIFICATION REQUEST message, a CPC CANCEL message, an SN ADDITION CANCEL message, or an S-NODE RELEASE REQUEST message.
In some embodiments, process 1400 also includes reconfiguring a UE to remove a conditional PSCell change associated with the S-SN.
In some embodiments, process 1400 also includes, prior to transmitting the request to the T-SN, receiving from the S-SN a request to configure CPC. In some embodiments, receiving the request transmitted by the S-SN comprises receiving one of: an S-NODE MODIFICATION REQUIRED message, or an S-NODE RELEASE REQUIRED message. In some embodiments, the request transmitted by the S-SN comprises information indicating the T-SN.
In some embodiments, transmitting the request to the T-SN to prepare the CPC configuration comprises transmitting to the T-SN an S-NODE ADDITION REQUEST message.
In some embodiments, the cancellation indication comprises one of: an S-NODE MODIFICATION REQUEST message, an CPC CANCEL message, or an SN ADDITION CANCEL message.
In some embodiments, process 1500 also includes, prior to transmitting the cancellation indication to the MN, transmitting a request to the MN to prepare a CPC configuration; and receiving a response message transmitted by the MN. In some embodiments, the request comprises: an S-NODE MODIFICATION REQUIRED message, or an S-NODE RELEASE REQUIRED message. In some embodiments, the response transmitted by the MN is an S-NODE MODIFICATION CONFIRM message.
In some embodiments, the cancellation indication is transmitted as a result of: detecting that a UE has moved away from a candidate target cell, detecting that a Secondary Cell Group, SCG, is going to be deactivated or suspended, or detecting that a conditional hand over, CHO, needs to be configured.
In some embodiments, the cancellation indication is one of: an S-NODE MODIFICATION REQUIRED message, an S-NODE RELEASE REQUIRED message, an S-NODE MODIFICATION REQUEST message, an S-NODE RELEASE REQUEST message, or a CPC CANCEL message.
In some embodiments, the request to prepare the CPC configuration comprises: a conditional PSCell Addition, an S-NODE MODIFICATION REQUIRED message, or an S-NODE RELEASE REQUIRED message.
In some embodiments, the response to the request to configure the CPC comprises: a conditional PSCell Addition Acknowledgement or an SN MODIFICATION REQUEST ACKNOWLEDGE message.
In some embodiments, process 1600 also includes acknowledging the cancellation of CPC cells to the MN. In some embodiments, acknowledging the cancellation of CPC cells comprises transmitting to the MN one of: an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message or an S-NODE RELEASE REQUEST ACKNOWLEDGE message.
With reference to
Telecommunication network 1810 is itself connected to host computer 1830, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 1830 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 1821 and 1822 between telecommunication network 1810 and host computer 1830 may extend directly from core network 1814 to host computer 1830 or may go via an optional intermediate network 1820. Intermediate network 1820 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1820, if any, may be a backbone network or the Internet; in particular, intermediate network 1820 may comprise two or more sub-networks (not shown).
The communication system of
Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to
Communication system 1900 further includes base station 1920 provided in a telecommunication system and comprising hardware 1925 enabling it to communicate with host computer 1910 and with UE 1930. Hardware 1925 may include communication interface 1926 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1900, as well as radio interface 1927 for setting up and maintaining at least wireless connection 1970 with UE 1930 located in a coverage area (not shown in
Communication system 1900 further includes UE 1930 already referred to. Its hardware 1935 may include radio interface 1937 configured to set up and maintain wireless connection 1970 with a base station serving a coverage area in which UE 1930 is currently located. Hardware 1935 of UE 1930 further includes processing circuitry 1938, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 1930 further comprises software 1931, which is stored in or accessible by UE 1930 and executable by processing circuitry 1938. Software 1931 includes client application 1932. Client application 1932 may be operable to provide a service to a human or non-human user via UE 1930, with the support of host computer 1910. In host computer 1910, an executing host application 1912 may communicate with the executing client application 1932 via OTT connection 1950 terminating at UE 1930 and host computer 1910. In providing the service to the user, client application 1932 may receive request data from host application 1912 and provide user data in response to the request data. OTT connection 1950 may transfer both the request data and the user data. Client application 1932 may interact with the user to generate the user data that it provides.
It is noted that host computer 1910, base station 1920 and UE 1930 illustrated in
In
Wireless connection 1970 between UE 1930 and base station 1920 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 1930 using OTT connection 1950, in which wireless connection 1970 forms the last segment. More precisely, the teachings of these embodiments may improve one or more of the date rate, latency, and power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and/or extended battery lifetime.
A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 1950 between host computer 1910 and UE 1930, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 1950 may be implemented in software 1911 and hardware 1915 of host computer 1910 or in software 1931 and hardware 1935 of UE 1930, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 1950 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 1911, 1931 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 1950 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1920, and it may be unknown or imperceptible to base station 1920. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 1910's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 1911 and 1931 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1950 while it monitors propagation times, errors etc.
Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
Summary of Additional Embodiments
The method of any of the above embodiments, and further comprising sending an indication to a determined target candidate SN that CPC is to be cancelled.
Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/IB2021/059132 | 10/5/2021 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63089946 | Oct 2020 | US |
