Patent Application
20240292282
The present disclosure relates to a radio communication system and, in particular, to mobility of radio terminals.
Non Patent Literatures 1 and 2 disclose a conditional handover (CHO) being discussed in the 3GPP. In some implementations for CHO, a source radio access network (RAN) node (e.g., eNodeB (eNB)) transmits a handover command including a handover execution condition (e.g., threshold) to a radio terminal (e.g., User Equipment (UE)). The radio terminal maintains the connection with the source RAN node even after receiving the handover command, and initiates access to the target RAN node as soon as the condition configured by the handover command is satisfied. That is, the conditional handover (CHO) is different from existing handovers in that the radio terminal initiates access to the target cell not in response to receiving the handover command, but in response to the satisfaction of the condition configured by the handover command.
The CHO can improve the reliability of delivery of the handover command to the UE by early event triggering (i.e., lowering a threshold which triggers a measurement report by the radio terminal). This allows the CHO to reduce a handover failure rate.
In CHO, a configuration of a plurality of candidate target cells may be sent to the radio terminal. The candidate targets cell may be referred to as potential target cells. For example, the radio terminal receives a handover command including configurations of a plurality of candidate target cells and a CHO execution threshold from the source RAN node (e.g., eNB). The radio terminal measures the configured candidate target cells and, when the measurement in any candidate target cell meets the CHO execution threshold, initiates access to this candidate cell.
The inventors have studied applying conditional mobility operations similar to the conditional handover to a cell change (PSCell change) of a primary cell (Primary SCG Cell (PSCell)) of a Secondary Cell Group (SCG) of a Dual Connectivity (DC) and found various problems.
The PSCell is, in other words, a Special Cell (SpCell) of the SCG. The UE performs a random access to the PSCell when it performs a handover procedure (or a Reconfiguration with Sync procedure). The SCG is a group of serving cells associated with a Secondary Node (SN) of the DC and includes a SpCell (i.e., PSCell) and optionally one or more Secondary Cells (SCells).
The PSCell Change is an example of a procedure which involves the Reconfiguration with sync procedure. Accordingly, the conditional PSCell change can be referred to as a conditional Reconfiguration with sync (for PSCell change).
As an example, consider a case where an SN uses the SN initiated SN Modification with MN involvement procedure for the PSCell change. In this case, RRC signaling between the SN and the UE for the conditional mobility (e.g., conditional PSCell change) is transmitted via a Signaling Radio Bearer (SRB) of a Master Cell Group (MCG). The MCG is a group of serving cells served by a Master Node (MN) of the DC. In this case, it is not clear how the SN knows a satisfaction of an execution condition of the PSCell change (or an initiation of the conditional mobility).
One of the objects to be attained by embodiments disclosed herein is to provide apparatuses, methods, and programs that contribute to allowing an SN to be aware of a satisfaction of an execution condition of a conditional PSCell change (or an initiation of the conditional PSCell change). It should be noted that this object is merely one of the objects to be attained by the embodiments disclosed herein. Other objects or problems and novel features will be made apparent from the following description and the accompanying drawings.
In a first aspect, a radio access network node includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to act as a secondary node of dual connectivity for a radio terminal. The at least one processor is configured to transmit to the radio terminal, via a master node of the dual connectivity, a first Radio Resource Control (RRC) message indicating an execution condition of a conditional primary cell change of a primary cell of a secondary cell group from a first cell to a second cell. The at least one processor is further configured to receive, via the master node, a second RRC message that is transmitted from the radio terminal in response to a satisfaction of the execution condition.
In a second aspect, the radio terminal includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to perform dual connectivity of a master cell group associated with a master node and a secondary cell group associated with a secondary node. The at least one processor is configured to receive from the secondary node, via the master node, a first radio Resource Control (RRC) message indicating an execution condition of a conditional primary cell change of a primary cell of the secondary cell group from a first cell to a second cell. The at least one processor is further configured to transmit a second RRC message form the radio terminal to the secondary node via the master node, in response to a satisfaction of the execution condition.
In a third aspect, a method for a radio access network node including:
In a fourth aspect, a method for a radio terminal including:
In a fifth aspect, a radio access network node includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to act as a secondary node of dual connectivity for a radio terminal. The at least one processor is configured to transmit to the radio terminal, via a master node of the dual connectivity, a first Radio Resource Control (RRC) message indicating an execution condition of a conditional primary cell change of a primary cell of a secondary cell group from a first cell to a second cell. The at least one processor is further configured to receive directly from the radio terminal, in the first cell or any secondary cell of the secondary cell group, an indication of an initiation or execution of the conditional primary cell change. The indication is transmitted from the radio terminal in response to a satisfaction of the execution condition.
In a sixth aspect, the radio terminal includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to perform dual connectivity of a master cell group associated with a master node and a secondary cell group associated with a secondary node. The at least one processor is configured to receive from the secondary node, via the master node, a first radio Resource Control (RRC) message indicating an execution condition of a conditional primary cell change of a primary cell of the secondary cell group from a first cell to a second cell. The at least one processor is further configured to transmit directly to the secondary node, in the first cell or any secondary cell of the secondary cell group, an indication of an initiation or execution of the conditional primary cell change, in response to a satisfaction of the execution condition.
In a seventh aspect, a method for a radio access network node including:
In an eighth aspect, a method for a radio terminal including:
In a ninth aspect, a program includes instructions (software codes) that, when loaded into a computer, cause the computer to perform the method according to the above-described third, fourth, seventh, or eighth aspect.
According to the above-deceived aspects, it is possible to provide apparatuses, methods, and programs that contribute to allowing an SN to be aware of a satisfaction of an execution condition of a conditional PSCell change (or an initiation of the conditional PSCell change).
Specific embodiments will be described hereinafter in detail with reference to the drawings. The same or corresponding elements are denoted by the same symbols throughout the drawings, and duplicated explanations are omitted as necessary for the sake of clarity.
Each of the embodiments described below may be used individually, or two or more of the embodiments may be appropriately combined with one another. These embodiments include novel features different from each other. Accordingly, these embodiments contribute to attaining objects or solving problems different from one another and also contribute to obtaining advantages different from one another.
The following descriptions on the embodiments mainly focus on the 3GPP Long Term Evolution (LTE) systems and 5G systems. However, these embodiments may be applied to other radio communication systems supporting dual connectivity. Note that, the term “LTE” used in this specification includes enhancement/evolution of LTE and LTE-Advanced to provide interworking with the 5G System, unless otherwise specified. The 5G system includes a network deployment in which an LTE eNodeB (eNB) is connected to a 5G core network (5GC). This eNB may be referred to as a Next generation (ng)-eNB. The ng-eNB may also be referred to as an eNB/5GC, which means an eNB connected to a 5GC.
Each of the MN 1 and the SN 2 may be an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (EUTRAN) node or a Next generation Radio Access Network (NG-RAN) node. The EUTRAN node may be an eNB or an en-gNB. The NG-RAN node may be a gNB or an ng-eNB. The Radio access Technology (RAT) of the MN 1 may be different from that of the SN 2.
The DC may be Multi-Radio Dual Connectivity (MR-DC). The MR-DC includes Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (E-UTRA)-NR Dual Connectivity (EN-DC), NR-E-UTRA DC (NE-DC), NG-RAN EN-DC (NGEN-DC), and NR-NR DC (NR DC).
Before the procedure in
In step 201, the SN 2 sends to the MN 1 an SN MODIFICATION REQUIRED message that contains an RRC message (e.g., RRC Reconfiguration message) of the SN RAT (e.g., NR) generated by the SN 2. The RRC message includes an initiation (or execution) condition of the conditional PSCell change (or the conditional Reconfiguration with sync for PSCell change). The initiation (or execution) condition of the conditional PSCell change includes, for example, a threshold and a corresponding time-to-trigger (TTT). Alternatively, the initiation (or execution) condition of the conditional PSCell change may be reception of an explicit execution instruction (e.g., predetermined signaling) from the network. In this case, the reception by the UE 3 of a configuration (e.g., radio parameters) used for receiving the execution instruction may implicitly indicate to the UE 3 that the initiation (or execution) condition of the conditional PSCell change is the reception of the execution instruction. In other words, if the UE 3 receives this configuration (e.g., radio parameters), the UE 3 may determine (or understand) that the initiation (or execution) condition of the conditional PSCell change associated therewith is the reception of the execution instruction (e.g., predetermined signaling).
The RRC message may also include a condition (e.g., offset) for the UE 3 to exit the conditional PSCell change, and a value of a validity timer. The value of the validity timer may indicate how long the resources of the candidate target cell (i.e., a candidate PSCell cell after the change) are valid. Alternatively, the value of the validity timer may indicate a period (or time) during which access to the candidate target cell is permitted, or a period (or time) during which the configuration for the conditional PSCell change is valid.
If one or both of data forwarding and an SN security key change need to be applied, the MN 1 may perform an MN initiated SN Modification procedure and apply a forwarding address or new SN security key information or both to the SN 2 using an SN Modification Request message. In response to it, the SN 2 may generate an RRC message (e.g., RRC Reconfiguration message) again and transmit this message to the MN 1 using an SN Modification Request Acknowledge message.
In step 202, the MN 1 performs an RRC reconfiguration procedure (e.g., LTE RRC Connection Reconfiguration procedure) of the MN RAT (e.g., LTE) via the MCG SRB, and forwards the RRC message of the SN RAT received from the SN 2 to the UE 3. The MN 1 may transmit to the UE 3, via the MCG SRB, an RRC message (e.g., LTE RRC Connection Reconfiguration message) of the MN RAT which carries the RRC message of the SN RAT received from the SN 2.
The UE 3 maintains the current PSCell configuration (i.e., the configuration before the change) and keeps using the current PSCell, even after receiving the RRC message of the SN RAT (step 202). If the execution condition of the conditional PSCell change (i.e., conditional Reconfiguration with sync) configured by the RRC message of the SN RAT (step 202) is satisfied (step 203), then the UE 3 sends to the MN 1 an RRC response message (e.g., LTE RRC Connection Reconfiguration Complete message) of the MN RAT containing an RRC response message (e.g., NR RRC Reconfiguration Complete message) of the SN RAT destined for the SN 2 (step 204). The UE 3 applies the new PSCell configuration and initiates access (i.e., a random access procedure) to the target PSCell.
In step 205, the MN 1 responds to the SN 2 with an SN MODIFICATION CONFIRM message. The SN MODIFICATION CONFIRM message contains the RRC response message (e.g., RRC Reconfiguration Complete message) of the SN RAT received from the UE 3.
In the procedure in
The SN 2 may stop downlink data transfer to the UE 3 via the PSCell of before the change, in response to receiving the RRC response message from the UE 3. Put another way, the RRC response message from the UE 3 may trigger the SN 2 to stop downlink data transfer to the UE 3 via the PSCell of before the change. This allows the SN 2 to continue data transmission (downlink, uplink, or both) for the UE 3 in the current PSCell (i.e., the PSCell before the change) (and other serving cell(s) (i.e., SCG SCell(s)) of the current SCG) until just before the initiation (or execution) of the conditional PSCell change.
In the procedure in
After step 302, the SN 2 may stop downlink data transfer to the UE 3 via the PSCell of before the change, in response to the reception of the RRC response message from the UE 3.
According to the operations of the MN 1, the SN 2, and the UE 3 described in the present embodiment, it is possible to allow the SN 2 to be aware of the satisfaction of the execution condition of the conditional PSCell change (or the initiation of the conditional PSCell change) in which RRC signaling between the SN 2 and the UE 3 is performed via the MN 1.
In the present embodiment, the UE 3 may further be operated as follows. If the condition (e.g., offset) of exiting the conditional PSCell change is satisfied or the above-described validity timer expires, the UE 3 may transmit, to the SN 2 via the MN 1, termination information indicating that due to this fact the conditional PSCell change has not been performed (non-execution) or the conditional PSCell change has failed. For example, the UE 3 may be operated as follows instead of the operation of step 204 in
The termination information may further include information (e.g., a cause) for distinguishing by which of the satisfaction of the exit condition and the expiration of the validity timer the non-execution or the failure of the conditional PSCell change is caused.
In the case where there are a plurality of candidate target cells and either or both of the exit condition and the value of the validity timer are configured on a per-cell basis, the UE 3 may transmit the SN RAT RRC message containing the termination information in response to the exit condition being satisfied (or the expiration of the validity timer) for all the candidate target cells. Alternatively, the UE 3 may transmit the SN RAT RRC message containing the termination information in response to the exit condition being satisfied (or the expiration of the validity timer) for any one of the candidate target cells. In the latter case, the UE 3 may include, in the SN RAT RRC message, information indicating the candidate target cell(s) (e.g., the first one cell, or a plurality of cells for which the exit condition has been satisfied (or the validity timer has expired) simultaneously or almost (or substantially) simultaneously.
The present embodiment provides a specific example of the conditional PSCell change described in the first embodiment. The configuration example of a radio communication network according to the present embodiment may be similar to the example illustrated in
The CU 21 may be a logical node which hosts Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB (or hosts the RRC and PDCP protocols of the gNB). The DU 22 may be a logical node which hosts Radio Link Control (RLC), Medium Access Control (MAC) and Physical (PHY) layers of the gNB. The interface 501 may be an F1 interface if the CU 21 is a gNB-CU and the DUs 22 are gNB-DUs.
The CU 21 may include a Control Plane (CP) Unit (e.g., a gNB-CU-CP) and one or more User Plane (UP) Units (e.g., gNB-CU-UPs).
Before the procedure in
In step 601, the CU 21 sends a UE CONTEXT SETUP REQUEST message to the target DU 22B in order to create a UE context and set up one or more bearers. The UE CONTEXT SETUP REQUEST message may request a configuration (e.g., CellGroupConfig) of a radio resource of the PSCell from the target DU 22B. To indicate that it is a conditional PSCell change request, a “CG-ConfigInfo” information element contained in a “CU to DU RRC Information” information element within the UE CONTEXT SETUP REQUEST message may be used. Alternatively, in order to indicate that it is a conditional mobility request, a new information element may be defined within the UE CONTEXT SETUP REQUEST message.
In step 602, the target DU 22B responds to the CU 21 with a UE CONTEXT SETUP RESPONSE message. In response to receiving the conditional PSCell Change request, the target DU 22B may determine whether the conditional PSCell Change is acceptable. The target DU 22B may include in the UE CONTEXT SETUP RESPONSE message an information element indicating whether the conditional PSCell Change is acceptable (step 602).
In step 603, the CU 21 sends to the MN 1 an SN MODIFICATION REQUIRED message containing an RRC message (e.g., RRC Reconfiguration message) generated by the CU 21. The RRC message indicates an initiation (or execution) condition (e.g., a threshold and a TTT) of the conditional PSCell change (or the conditional Reconfiguration with sync for PSCell change). The RRC message may also include a condition (e.g., offset) for the UE 3 to exit the conditional PSCell change and a value of a validity timer. The value of the validity timer may indicate how long the resources of the candidate target cell (i.e., candidate cell to be used as the PSCell after the change) are valid. Alternatively, the value of the validity timer may indicate a period (or time) during which access to the candidate target cell is permitted, or a period (or time) during which the configuration for the conditional PSCell change is valid.
More specifically, the CU 21 may determine the initiation condition of the conditional PSCell change and include it in the CG-ConfigInfo information element or a new information element contained in the UE CONTEXT SETUP REQUEST message (step 601). The target DU 22B may then generate a radio resource configuration (e.g., CellGroupConfig) containing the initiation condition of the conditional PSCell change and include it in the UE CONTEXT SETUP RESPONSE message (step 602). The CU 21 may generate an RRC message (e.g., NR RRCReconfiguration message) containing the received radio resource configuration (e.g., CellGroupConfig) and include it in the SN MODIFICATION REQUIRED message (step 603). The CU 21 may transmit one or both of the condition for the UE 3 to exit the conditional PSCell change and the value of the validity timer to the DU 22B in step 601, together with the initiation condition of the conditional PSCell change. The DU 22B may also include them in the radio resource configuration (e.g., CellGroupConfig), which contains the initiation condition of the conditional PSCell change, and transmit it to the CU 21.
Alternatively, the CU 21 may determine the initiation condition of the conditional PSCell change and include it in a new information element within the SN MODIFICATION REQUIRED message (step 603). The CU 21 may further include in this message one or both of the condition for the UE 3 to exit the conditional PSCell change and the value of the validity timer.
Further alternatively, the target DU 22B may determine the initiation condition of the conditional PSCell change. In this case, the target DU 22B may determine the initiation condition of the conditional PSCell change in response to the conditional PSCell change request (step 601) and include the determined initiation condition in the CellGroupConfig information element or a new information element within the UE CONTEXT SETUP RESPONSE message (step 602). After that, the CU 21 may generate an RRC message containing the CellGroupConfig information element or new information element, which contains the initiation condition of the conditional PSCell change, and include it in the SN MODIFICATION REQUIRED message (step 603). The DU 22 may further determine one or both of the condition for the UE 3 to exit the conditional PSCell change and the value of the validity timer and include them in the RRC message to the CU 21.
If one or both of data forwarding and an SN security key change need to be applied, the MN 1 may perform an MN initiated SN Modification procedure and apply a forwarding address or new SN security key information or both to the SN 2 (i.e., CU 21) using an SN Modification Request message.
In step 604, the CU 21 sends a UE CONTEXT MODIFICATION REQUEST message to the source DU 22A. The message includes an indication of the conditional PSCell change.
In step 605, the source DU 22A responds to the CU 21 with a UE CONTEXT MODIFICATION RESPONSE message.
In step 606, the MN 1 performs an RRC (Connection) Reconfiguration procedure via an MCG SRB and forwards the RRC message received from the CU 21 to the UE 3. The MN 1 may transmit to the UE 3 via the MCG SRB an RRC (Connection) Reconfiguration message carrying the RRC message received from the CU 21.
The UE 3 maintains the PSCell configuration before the change and keeps using the PSCell of before the change served by the source DU 22A, even after receiving the RRC message (step 606). If the execution condition of the conditional PSCell change (i.e., conditional Reconfiguration with sync) configured by the RRC message (step 606) is satisfied (step 607), then the UE 3 applies the new PSCell configuration and sends to the MN 1 an RRC (Connection) Reconfiguration Complete message which contains an RRC response message destined for the SN 2 (i.e., CU 21) (step 608). The UE 3 initiates access (i.e., random access procedure) to the target PSCell (i.e., the cell served by the target DU 22B) (step 610).
In step 609, the MN 1 responds to the SN 2 (i.e., CU 21) with an SN MODIFICATION CONFIRM message. The SN MODIFICATION CONFIRM message contains the RRC response message received from the UE 3.
In the procedure in
The SN 2 (i.e., CU 21) may stop downlink data transfer to the UE 3 via the source DU 22A, in response to receiving the RRC response message from the UE 3. Put another way, the RRC response message from the UE 3 may trigger the SN 2 (i.e., CU 21) to stop downlink data transfer to the UE 3 via the PSCell of before the change. This allows the SN 2 (i.e., CU 21) to continue data transmission (downlink, uplink, or both) for the UE 3 in the PSCell of before the change (and other serving cell(s) (i.e., SCG SCell(s)) of the current SCG) until just before the initiation (or execution) of the conditional PSCell change.
Alternatively, before the reception of the RRC response message from the UE 3, the SN 2 (i.e., CU 21) may stop downlink data transfer to the UE 3 via the source DU 22A in response to receiving from the source DU 22A a control message indicating downlink data not yet transmitted to the UE 3. This control data may be a message (or a frame, or a Protocol Data Unit (PDU)) transmitted to the CU 21 so as to indicate the downlink data not yet transmitted to the UE 3. More specifically, the control message may be a DOWNLINK DATA DELIVERY STATUS (DDDS) frame. The DDDS frame may be a GTP-U (or F1-U) PDU.
According to the operations of the MN 1, the SN 2 (the CU 21, the source DU 22A, and the target DU 22B), and the UE 3 described in the present embodiment, it is possible to allow the SN 2 to be aware of the satisfaction of the execution condition of the conditional PSCell change (or the initiation of the conditional PSCell change) in which RRC signaling between the SN 2 and the UE 3 is performed via the MN 1. Although the present embodiment is described with reference to the intra-CU inter-DU conditional PSCell Change as an example, it can also be applied to or reused for an intra-CU intra-DU conditional PSCell Change.
In the present embodiment, as described in the first embodiment, when the condition (e.g., offset) of exiting the conditional PSCell change is satisfied or the above-described validity timer expires, the UE 3 may transmit, to the SN 2 (i.e., CU 21) via the MN 1, termination information indicating that due to this fact the conditional PSCell change has not been performed (non-execution) or the conditional PSCell change has failed. For example, the UE 3 may be operated as follows instead of the operation of step 608 in
The present embodiment provides another example of the signaling for the conditional PSCell Change. The configuration example of a radio communication network according to the present embodiment may be similar to the example illustrated in
In the present embodiment, an SN 2 sends an RRC message indicating an execution condition of the conditional PSCell change to a UE 3 via an MN 1. On the other hand, the SN 2 receives an indication of execution (or initiation) of the conditional PSCell change, which is sent by the UE 3 in response to satisfaction of the execution condition of the conditional PSCell change, directly from the UE 3 in the current PSCell (i.e., the PSCell before the change) or any SCG SCell.
In the present embodiment, the UE 3 receives the RRC message indicating the execution condition of the conditional PSCell change from the SN 2 via the MN 1. On the other hand, the UE 3 transmits the indication of execution (or initiation) of the conditional PSCell change directly to the SN 2 in the current PSCell (i.e., the PSCell before the change) or any SCG SCell, in response to satisfaction of the execution condition of the conditional PSCell change.
According to the operations of the MN 1, the SN 2 and the UE 3 described in the present embodiment, it is possible to allow the SN 2 to be aware of the satisfaction of the execution condition of the conditional PSCell change (or the initiation of the conditional PSCell change) in which RRC signaling between the SN 2 and the UE 3 is performed via the MN 1.
In addition, in the present embodiment, the indication of execution (or initiation) of the conditional PSCell change is transmitted from the UE 3 directly to the SN 2 without passing through the MN 1. This makes it possible to avoid a delay due to the intervention of the MN 1, thereby reducing the delay required for transmitting the indication from the UE 3 to the SN 2.
The indication of execution (or initiation) of the conditional PSCell change may be transmitted by using signaling of a layer lower than the RRC layer. More specifically, the indication may be transmitted by using signaling of the MAC layer or the physical layer. The indication may be Uplink Control Information (UCI) transmitted through a Physical Uplink Control Channel (PUCCH). Instead, the indication may be a MAC Control Element (CE).
The transmission of the indication of execution (or initiation) of the conditional mobility using signaling of a layer (e.g., the MAC layer or the physical layer) lower than the RRC layer is effective especially in the case where an SN initiated SN Modification with MN involvement procedure is used for the conditional PSCell Change. In the SN initiated SN Modification with MN involvement, the RRC signaling for the conditional mobility (e.g., conditional PSCell change) is transmitted via the MCG SRB. Thus, the transmission of the RRC signaling from the UE 3 to the SN 2 is delayed due to the intervention of the MN 1. In contrast, signaling of the MAC layer or the physical layer from the UE 3 to the SN 2 can be transmitted directly to the SN 2 via a physical channel of a cell served by the SN 2. Thus, by using signaling of a layer (e.g., the MAC layer or the physical layer) lower than the RRC layer to transmit the indication of the conditional mobility execution, the UE 3 can reduce the delay required for transmitting this indication from the UE 3 to the SN 2.
The SN 2 may determine in advance and notify the UE 3 of a configuration of a radio resource to be used for the indication of execution (or initiation) of the conditional PSCell change. The notification may be transmitted via RRC layer signaling via the MN 1.
In the case where there is a plurality of candidate target cells, the indication of execution (or initiation) of the conditional PSCell change may include information explicitly or implicitly indicating the selected candidate target cell (i.e., the candidate target cell for which the PSCell Change has been triggered).
The signaling in the present embodiment may be performed according to, for example, but not limited to,
Processing in steps 701 and 702 in
In step 703, the UE 3 transmits to the MN 1 an RRC message (e.g., LTE RRC Connection Reconfiguration Complete message) of the MN RAT containing an RRC response message (e.g., NR RRC Reconfiguration Complete message) of the SN RAT destined for the SN 2.
In step 704, the MN 1 responds to the SN 2 with an SN MODIFICATION CONFIRM message. The SN MODIFICATION CONFIRM message contains the RRC response message (e.g., RRC Reconfiguration Complete message) of the SN RAT received from the UE 3.
The UE 3 maintains the current PSCell configuration (i.e., the configuration before the change) and keeps using the current PSCell, even after receiving the RRC message (step 702). If the execution condition of the conditional PSCell change (i.e., conditional Reconfiguration with sync) configured by the RRC message of the SN RAT (step 702) is satisfied (step 705), the UE 3 transmits an indication (or report) indicating execution or initiation of the conditional mobility (i.e., conditional PSCell Change) directly to the SN 2 in the current PSCell (or an SCG SCell). As described above, this indication (or report) may by transmitted via signaling of a layer (e.g., the MAC layer or the physical layer) lower than the RRC layer. The UE 3 applies the new PSCell configuration and initiates access (i.e., random access procedure) to the target PSCell.
The SN 2 may stop downlink data transfer to the UE 3 via the PSCell of before the change, in response to the reception of the indication (or report) (step 706). In other words, the indication (or report) from the UE 3 (step 706) may trigger the SN 2 to stop downlink data transfer to the UE 3 via the PSCell of before the change. This allows the SN 2 to continue data transmission (downlink, uplink, or both) for the UE 3 in the current PSCell (i.e., the PSCell before the change) (and SCG SCell(s)) until just before the initiation (or execution) of the conditional PSCell change.
In some implementations, the C-RAN deployment may be applied to the SN 2 (e.g., gNB), and the SN 2 (e.g., gNB) may include a CU (e.g., gNB-CU) and one or more DUs (e.g., gNB-DUs). The conditional PSCell change in the present embodiment may be applied to the PSCell change between different DUs in the SN 2 (e.g., intra-gNB-CU inter-gNB-DU PSCell change). In this case, if the execution condition of the conditional PSCell change (i.e., conditional Reconfiguration with sync) configured by the RRC message of the SN RAT is satisfied, the UE 3 may transmit the indication (or the report) indicating execution or initiation of the conditional mobility (i.e., conditional PSCell Change) directly to the source DU (e.g., gNB-DU) in the current PSCell. In response to receiving the indication (or report), the source DU (e.g., gNB-DU) may notify the CU (e.g., gNB-CU) that the conditional mobility has been executed or initiated in the UE. The source DU (e.g., gNB-DU) may send this notification by using an IE of an F1 message, or using RRC information (e.g., IE, message) contained in an DU to CU RRC container (e.g., DU To CU RRC Information).
The following provides configuration examples of the MN 1, the SN 2, and the UE 3 according to the above-described embodiments.
The network interface 803 is used to communicate with network nodes (e.g., the MN1, and control nodes and transfer nodes of a core network). The network interface 803 may include, for example, a network interface card (NIC) conforming to the IEEE 802.3 series.
The processor 804 performs digital baseband signal processing (i.e., data-plane processing) and control-plane processing for radio communication. The processor 804 may include a plurality of processors. The processor 804 may include, for example, a modem processor (e.g., a Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g., a Central Processing Unit (CPU) or a Micro Processing Unit (MPU)) that performs the control-plane processing. The processor 804 may include a digital beamformer module for beam forming. The digital beamformer module may include a Multiple Input Multiple Output (MIMO) encoder and a pre-coder.
The memory 805 is composed of a combination of a volatile memory and a non-volatile memory. The volatile memory is, for example, a Static Random Access Memory (SRAM), a Dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is, for example, a mask Read Only Memory (MROM), an Electrically Erasable Programmable ROM (EEPROM), a flash memory, a hard disc drive, or any combination thereof. The memory 805 may include a storage located apart from the processor 804. In this case, the processor 804 may access the memory 805 via the network interface 803 or an I/O interface (not shown).
The memory 805 may store one or more software modules (computer programs) 806 including instructions and data to perform processing by the SN 2 described in the above embodiments. In some implementations, the processor 804 may be configured to load the software modules 806 from the memory 805 and execute the loaded software modules, thereby performing processing of the SN 2 described in the above embodiments.
When the SN 2 is a CU (e.g., eNB-CU or gNB-CU), the SN 2 does not need to include the RF transceiver 801 (and the antenna array 802).
The baseband processor 903 performs digital baseband signal processing (i.e., data-plane processing) and control-plane processing for radio communication. The digital baseband signal processing includes, for example, (a) data compression/decompression, (b) data segmentation/concatenation, (c) composition/decomposition of a transmission format (i.e., transmission frame), (d) channel coding/decoding, (e) modulation (i.e., symbol mapping)/demodulation, and (f) generation of OFDM symbol data (i.e., baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT). Meanwhile, the control-plane processing includes communication management of layer 1 (e.g., transmission power control), layer 2 (e.g., radio resource management and hybrid automatic repeat request (HARQ) processing), and layer 3 (e.g., signaling regarding attach, mobility, and call management).
The digital baseband signal processing by the baseband processor 903 may include, for example, signal processing of a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a MAC layer, and a PHY layer. The control-plane processing performed by the baseband processor 903 may also include processing of a Non-Access Stratum (NAS) protocol, an RRC protocol, and MAC CEs.
The baseband processor 903 may perform MIMO encoding and pre-coding for beam forming.
The baseband processor 903 may include a modem processor (e.g., DSP) that performs the digital baseband signal processing and a protocol stack processor (e.g., a CPU or an MPU) that performs the control-plane processing. In this case, the protocol stack processor, which performs the control-plane processing, may be integrated with an application processor 904 described in the following.
The application processor 904 is also referred to as a CPU, an MPU, a microprocessor, or a processor core. The application processor 904 may include a plurality of processors (processor cores). The application processor 904 loads a system software program (Operating System (OS)) and various application programs (e.g., a call application, a WEB browser, a mailer, a camera operation application, and a music player application) from a memory 906 or from another memory (not shown) and executes these programs, thereby providing various functions of the UE 3.
In some implementations, as represented by a dashed line (905) in
The memory 906 is a volatile memory, a non-volatile memory, or a combination thereof. The memory 906 may include a plurality of memory devices that are physically independent from each other. The volatile memory is, for example, an SRAM, a DRAM, or a combination thereof. The non-volatile memory is, for example, an MROM, an EEPROM, a flash memory, a hard disc drive, or any combination thereof. The memory 906 may include, for example, an external memory device that can be accessed from the baseband processor 903, the application processor 904, and the SoC 905. The memory 906 may include an internal memory device that is integrated in the baseband processor 903, the application processor 904, or the SoC 905. The memory 906 may also include a memory in a Universal Integrated Circuit Card (UICC).
The memory 906 may store one or more software modules (computer programs) 907 including instructions and data to perform the processing by the UE 3 described in the above embodiments. In some implementations, the baseband processor 903 or the application processor 904 may load these software modules 907 from the memory 906 and execute the loaded software modules, thereby performing the processing of the UE 3 described in the above embodiments with reference to the drawings.
The control-plane processing and operations performed by the UE 3 described in the above embodiments can be achieved by elements other than the RF transceiver 901 and the antenna array 902, i.e., achieved by the memory 906, which stores the software module 907, and one or both of the baseband processor 903 and the application processor 904.
As described above with reference to
Each of the above-described embodiments may be used individually or two or more embodiments may be appropriately combined with one another. For example, the third embodiment may be executed independently from the first and second embodiments, contribute to solving objects or problems different from those of the first and second embodiments, and provide an effect different from that provided by the first and second embodiments.
The functions described as the conditional PSCell change in the above-described embodiments may be referred to as pre-conditioned PSCell change, pre-prepared PSCell change, delayed PSCell change, or the like.
In the embodiments described above, the UE 3 may execute the generation and transmission of an RRC message (e.g., RRCReconfigurationComplete) which is a response to an RRC message (e.g., NR RRCReconfiguration) of the SN RAT (e.g., NR) received via an RRC message (e.g., LTE RRCConnection Reconfiguration) of the MN RAT (e.g., LTE) as follows. Upon detecting that the RRC message of the MN RAT contains the RRC message of the SN RAT, the RRC layer of the MN RAT of the UE 3 passes it to the RRC layer of the SN RAT. The RRC layer of the SN RAT of the UE 3 decodes the RRC message of the SN RAT, and upon detecting that the conditional PSCell change is needed, determines whether the execution condition for the conditional PSCell change is satisfied. If the execution condition for the conditional PSCell change is satisfied, the RRC layer of the SN RAT generates a response RRC message (e.g., RRCReconfigurationComplete) of the SN RAT, and passes it to the RRC layer of the MN RAT. The RRC layer of the MN RAT generates an RRC message (e.g., RRCConnectionReconfigurationComplete) of the MN RAT containing the response RRC message received from the RRC layer of the SN RAT and transmits it to the MN 1. The MN 1 then forwards the response RRC message of the SN RAT to the SN 2.
On the other hand, if a condition of exiting the conditional PSCell change is satisfied or a validity timer expires, the RRC layer of the SN RAT of the UE 3 may generate a response RRC message (e.g., RRCReconfigurationComplete) containing information indicating that the conditional PSCell change was not successfully completed and then pass it to the RRC layer of the MN RAT. The RRC layer of the MN RAT generates an RRC message (e.g., RRCConnection ReconfigurationComplete) of the MN RAT containing the response RRC message received from the RRC layer of the SN RAT and transmits it to the MN 1. The MN 1 then forwards the response RRC message of the SN RAT to the SN 2. Note that, in the case where there is a plurality of candidate target cells (i.e., there are a plurality of candidates of the target PSCell), the RRC layer of the SN RAT may perform the above operation if the condition of exiting the conditional PSCell change is satisfied for any one of the candidate target cells or the validity timer expires for any one of the candidate target cells. Alternatively, the RRC layer of the SN RAT may execute the above operation if the condition of exiting the conditional PSCell change is satisfied for all the candidate target cells or the validity timer expires for all the candidate target cells.
In the conditional PSCell change in the embodiments described above, the UE 3 may handle a timer T30x regarding the conditional PSCell change as follows. In the normal PSCell change, the UE 3 starts a timer T304 upon receiving the RRC message (e.g., RRC Reconfiguration including reconfiguration With Sync) of the instruction of the PSCell change. Alternatively, in the conditional PSCell change, the UE 3 may not immediately start the timer T30x even when it received the RRC message (e.g., RRC Reconfiguration including reconfigurationWithSync for Conditional PSCell change) of the instruction of the conditional PSCell change. If the condition of the conditional PSCell change for a certain candidate target cell is satisfied, then the UE 3 starts the timer T30x corresponding to this candidate target cell. After that, if a random access in the candidate target cell (e.g., SpCell) is successful, the UE 3 stops the timer T30x. Note that the conventional T304 may be used as the T30x, or a new timer may be provided as the T30x.
The User Equipment (UE) in the present disclosure is an entity to be connected to a network via a wireless interface. It should be noted that the radio terminal (UE) in the present disclosure is not limited to a dedicated communication device, and it may be any device as follows having the communication functions herein explained.
The terms “User Equipment (UE)” (as the term is used by 3GPP), “mobile station”, “mobile terminal”, “mobile device”, and “radio terminal (wireless device)” are generally intended to be synonymous with one another. The UE may include standalone mobile stations, such as terminals, cell phones, smartphones, tablets, cellular IoT (internet of things) terminals, and IoT devices. It will be appreciated that the terms “UE” and “radio terminal” also encompass devices that remain stationary for a long period of time.
A UE may, for example, be an item of equipment for production or manufacture and/or an item of energy related machinery (for example equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power generators; nuclear electricity generators; batteries; nuclear systems and/or associated equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil hydraulic equipment; pneumatic equipment; metal working machinery; manipulators; robots and/or their application systems; tools; molds or dies; rolls; conveying equipment; elevating equipment; materials handling equipment; textile machinery; sewing machines; printing and/or related machinery; paper projecting machinery; chemical machinery; mining and/or construction machinery and/or related equipment; machinery and/or implements for agriculture, forestry and/or fisheries; safety and/or environment preservation equipment; tractors; power transmission equipment; and/or application systems for any of the previously mentioned equipment or machinery etc.).
A UE may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motorcycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.).
A UE may, for example, be an item of information and communication equipment (for example information and communication equipment such as: electronic computer and related equipment; communication and related equipment; electronic components etc.).
A UE may, for example, be an item of trade and/or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, a consumer electronic and electronic appliance (for example a consumer electronic appliance such as: audio equipment; a speaker; a radio; video equipment; a television etc.).
A UE may, for example, be an electrical application system or equipment (for example an electrical application system or equipment such as: an x-ray system; a particle accelerator; radio isotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment etc.).
A UE may, for example, be an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a surveying or sensing instrument (for example a surveying or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.), a watch or clock, a laboratory instrument, optical apparatus, medical equipment and/or system, a weapon, an item of cutlery, a hand tool, or the like.
A UE may, for example, be a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed for attachment to or for insertion into another electronic device (for example a personal computer, electrical measuring machine)).
A UE may be a device or a part of a system that provides applications, services, and solutions described below, as to “internet of things (IoT)”, using a variety of wired and/or wireless communication technologies. Internet of Things devices (or “things”) may be equipped with appropriate electronics, software, sensors, network connectivity, and/or the like, which enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may comprise automated equipment that follow software instructions stored in an internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices might also remain stationary and/or inactive for a long period of time. IoT devices may be implemented as a part of a (generally) stationary apparatus. IT devices may also be embedded in non-stationary apparatus (e.g. vehicles) or attached to animals or persons to be monitored/tracked. It will be appreciated that IoT technology can be implemented on any communication devices that can connect to a communications network for sending/receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory. It will be appreciated that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices, Machine-to-Machine (M2M) communication devices, or Narrow Band-IoT (NB-IoT) UE.
It will be appreciated that a UE may support one or more IoT or MTC applications.
Some examples of MTC applications are listed in 3GPP TS 22.368 V13.2.0 (2017 Jan. 13), Annex B (the contents of which are incorporated herein by reference). This list is not exhaustive and is intended to be indicative of some examples of MTC applications. In this list, the Service Area of the MTC applications includes Security, Tracking & Tracing, Payment, Health, Remote Maintenance/Control, Metering, and Consumer Devices.
Examples of the MTC applications regarding Security include Surveillance systems, Backup for landline, Control of physical access (e.g., to buildings), and Car/driver security.
Examples of the MTC applications regarding Tacking & Tracing include Fleet Management, Order Management, Telematics insurance: Pay as you drive (PAYD), Asset Tracking, Navigation, Traffic information, Road tolling, and Road traffic optimisation/steering.
Examples of the MTC applications regarding Payment include Point of sales (POS), Vending machines, and Gaming machines.
Examples of the MTC applications regarding Health include Monitoring vital signs, Supporting the aged or handicapped, Web Access Telemedicine points, and Remote diagnostics.
Examples of the MTC applications regarding Remote Maintenance/Control include Sensors, Lighting, Pumps, Valves, Elevator control, Vending machine control, and Vehicle diagnostics.
Examples of the MTC applications regarding Metering include Power, Gas, Water, Heating, Grid control, and Industrial metering.
Examples of the MTC applications regarding Consumer Devices include Digital photo frame, Digital camera, and eBook.
Applications, services, and solutions may be an Mobile Virtual Network Operator (MVNO) service/system, an emergency radio communication service/system, a Private Branch exchange (PBX) service/system, a PHS/Digital Cordless Telecommunications service/system, a Point of sale (POS) service/system, an advertise calling service/system, a Multimedia Broadcast and Multicast Service (MBMS) service/system, a Vehicle to Everything (V2X) service/system, a train radio service/system, a location related service/system, a Disaster/Emergency Wireless Communication Service/system, an Internet of Things (IoT) service/system, a community service/system, a video streaming service/system, a femto cell application service/system, a Voice over LTE (VoLTE) service/system, a radio tag service/system, a charging service/system, a radio on demand service/system, a roaming service/system, an activity monitoring service/system, a telecom carrier/communication NW selection service/system, a functional restriction service/system, a Proof of Concept (PoC) service/system, a personal information management service/system, a display video service/system, a non-communication service/system, an ad-hoc network/Delay Tolerant Networking (DTN) service/system, etc.
The above-described UE categories are merely examples of applications of the technical ideas and embodiments described in the present disclosure. The UE described in this disclosure is not limited to these examples and various modifications can be made thereto by those skilled in the art.
The above-described embodiments are merely examples of applications of the technical ideas obtained by the inventors. These technical ideas are not limited to the above-described embodiments and various modifications can be made thereto.
The whole or part of the embodiments disclosed above can be described as, but not limited to, the following supplementary notes.
A radio access network node comprising:
The radio access network node according to Supplementary Note 1, wherein the at least one processor is configured to detect an initiation of the conditional primary cell change by receiving the second RRC message.
The radio access network node according to Supplementary Note 1 or 2, wherein the at least one processor is configured to, in response to receiving the second RRC message, stop downlink data transfer to the radio terminal in a serving cell of the secondary cell group.
The radio access network node according to any one of Supplementary Notes 1 to 3, wherein
The radio access network node according to Supplementary Note 4, wherein the at least one processor is further configured to, in response to receiving, prior to the second RRC message, from the first distributed unit a control message indicating downlink data not yet transferred to the radio terminal, stop downlink data transfer via the first distributed unit to the radio terminal.
The radio access network node according to Supplementary Note 5, wherein the control message is a DOWNLINK DATA DELIVERY STATUS frame.
A radio terminal comprising:
The radio terminal according to Supplementary Note 7, wherein the second RRC message triggers the secondary node to stop downlink data transfer to the radio terminal in a serving cell of the secondary cell group.
A method for a radio access network node, the method comprising:
A method for a radio terminal, the method comprising:
A program for causing a computer to perform a method for a radio access network node, the method comprising:
A program for causing a computer to perform a method for a radio terminal, the method comprising:
A radio access network node comprising:
The radio access network node according to Supplementary Note 13, wherein the indication is transmitted by using signaling in a layer lower that an RRC layer.
The radio access network node according to Supplementary Note 14, wherein the signaling is signaling in a Medium Access Control (MAC) layer or a physical layer.
A radio terminal comprising:
The radio terminal according to Supplementary Note 16, wherein the at least one processor is configured to transmit the indication via signaling in a layer lower that an RRC layer.
The radio terminal according to Supplementary Note 17, wherein the signaling is signaling in a Medium Access Control (MAC) layer or a physical layer.
The radio terminal according to any one of Supplementary Notes 16 to 18, wherein
A method for a radio access network node, the method comprising:
A method for a radio terminal, the method comprising:
A program for causing a computer to perform a method for a radio access network node, the method comprising:
A program for causing a computer to perform a method for a radio terminal, the method comprising:
This application is based upon and claims the benefit of priority from Japanese Patent Application No. 2019-003563, filed on Jan. 11, 2019, the disclosure of which is incorporated herein in its entirety by reference.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2019-003563 | Jan 2019 | JP | national |
This application is a continuation application of U.S. 18/360,106, filed Jul. 27, 2023, which is a continuation application of U.S. 17/419,643 (now U.S. Pat. No. 11,792,696), filed Jun. 29, 2021, which is a National Stage Entry of PCT/JP2019/042921 filed on Oct. 31, 2019, which claims priority from Japanese Patent Application 2019-003563 filed on Jan. 11, 2019, the contents of all of which are incorporated herein by reference, in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 18360106 | Jul 2023 | US |
| Child | 18659073 | US | |
| Parent | 17419643 | Jun 2021 | US |
| Child | 18360106 | US |
