Communication control method
The communication control method addresses the challenge of RACH-less handovers in cellular systems by using SSB index information in handover commands, enabling efficient RRC reconfiguration completion messages during cellular handovers, even without explicit beam information, thus enhancing handover efficiency.
Patent Information
- Application Number
- PCT/JP2024/017141
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-10
- Filing Date
- 2024-05-08
- Publication Date
- 2024-11-14
AI Technical Summary
In cellular communication systems, particularly with mobile IAB nodes, RACH-less handovers face challenges in efficiently transferring the UE from a source cell to a target cell without explicit beam information, leading to potential delays and failures in transmitting the RRC reconfiguration completion message.
The communication control method involves the target donor node transmitting a handover command with index information of a synchronization signal block (SSB) to the UE via the source cell, allowing the UE to transmit the RRC reconfiguration complete message using resources linked to the SSB index, thereby ensuring proper handover without explicit beam information.
This method enables seamless RACH-less handovers by ensuring the UE can correctly transmit the RRC reconfiguration completion message to the target cell, reducing signaling delays and improving handover efficiency even when explicit beam information is not provided.
Smart Images

Figure JP2024017141_14112024_PF_FP_ABST
Abstract
Description
Communication Control Method
[0001] The present disclosure relates to a communication control method for use in a cellular communication system.
[0002] The Third Generation Partnership Project (3GPP), a standardization project for cellular communication systems, is considering the introduction of a new relay node called an Integrated Access and Backhaul (IAB) node (see, for example, Non-Patent Document 1). One or more relay nodes intervene in communication between a base station and a user device and relay this communication.
[0003] 3GPP TS 38.300 V17.4.0 (2023-03)
[0004] A communication control method according to a first aspect is a communication control method for handing over user equipment (UE) from a source cell of a mobile Integrated Access and Backhaul (IAB) node to a target cell of the mobile IAB node, the communication control method including receiving, by the user equipment, a handover command including beam information from a network, and transmitting, by the user equipment, an RRC Reconfiguration Complete message in the target cell using the beam information.
[0005] A communication control method according to a second aspect is a communication control method used in a cellular communication system. The communication control method includes a step in which a target donor node transmits a handover command including index information related to an index of a synchronization signal block (SSB) to a user equipment via a source cell. The communication control method also includes a step in which the user equipment receives the handover command. The communication control method further includes a step in which the user equipment transmits an RRC reconfiguration complete (RRCReconfigurationComplete) message to the target cell using a resource associated with the index of the synchronization signal block.
[0006] A communication control method according to a third aspect is a communication control method used in a cellular communication system. The communication control method includes a step of transmitting, from a source base station, to a user equipment, a handover command including index information related to an index of a synchronization signal block (SSB). The communication control method also includes a step of receiving, by the user equipment, the handover command. The communication control method further includes a step of transmitting, by the user equipment, an RRC reconfiguration complete (RRCReconfigurationComplete) message to a target base station using a resource associated with the index of the synchronization signal block.
[0007] A communication control method according to a fourth aspect is a communication control method for use in a cellular communication system. The communication control method includes a step in which a target donor node transmits a handover command, which does not explicitly include beam information, to a user equipment via a source cell. The communication control method also includes a step in which the user equipment receives the handover command. The communication control method further includes a step in which the user equipment transmits an RRC reconfiguration complete message to the target cell using the beam used when accessing the source cell.
[0008] A communication control method according to a fifth aspect is a communication control method for use in a cellular communication system, the communication control method including a step of a target donor node transmitting, to a user equipment via a source cell, either a first handover command that explicitly includes a timing advance value or a second handover command that does not explicitly include a timing advance value, the user equipment transmitting, when receiving the first handover command, an RRC reconfiguration complete message to the target cell using the timing advance value, and, when receiving the second handover command, transmitting an RRC reconfiguration complete message to the target cell using the timing advance value used when accessing the source cell.
[0009] FIG. 1 is a diagram showing an example of the configuration of a cellular communication system according to one embodiment. FIG. 2 is a diagram showing the relationship between an IAB node, parent nodes, and child nodes. FIG. 3 is a diagram showing an example of the configuration of a gNB (base station) according to one embodiment. FIG. 4 is a diagram showing an example of the configuration of an IAB node (relay node) according to one embodiment. FIG. 5 is a diagram showing an example of the configuration of a UE (user equipment) according to one embodiment. FIG. 6 is a diagram showing an example of a protocol stack related to IAB-MT RRC connection and NAS connection. FIG. 7 is a diagram showing an example of a protocol stack related to the F1-U protocol. FIG. 8 is a diagram showing an example of a protocol stack related to the F1-C protocol. FIG. 9 is a diagram showing an example of a scenario according to the first embodiment. FIG. 10 is a diagram showing an example of an operation according to the first embodiment. FIGS. 11(A) and 11(B) are diagrams showing example resources according to the first embodiment. FIG. 12 is a diagram showing an example of an operation according to the second embodiment. FIG. 13 is a diagram showing an example of an operation according to the third embodiment. FIG. 14 is a diagram showing an example of an operation according to the fourth embodiment. Fig. 15 is a diagram illustrating an example of operation according to the fifth embodiment. Fig. 16 is a diagram illustrating the configuration of a RACH-less handover in LTE by uplink configuration including applicable timing advance (TA) information and an uplink grant in MobilityControlInfo.
[0010] A cellular communication system according to an embodiment will be described with reference to the drawings. In the description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.
[0011] [First embodiment]
[0012] (Configuration of Cellular Communication System) An example configuration of a cellular communication system according to one embodiment will be described. The cellular communication system 1 according to one embodiment is a 3GPP 5G system. Specifically, the radio access method in the cellular communication system 1 is NR (New Radio), which is a 5G radio access method. However, LTE (Long Term Evolution) may be applied at least in part to the cellular communication system 1. Furthermore, future cellular communication systems such as 6G may also be applied to the cellular communication system 1.
[0013] FIG. 1 is a diagram showing an example of the configuration of a cellular communication system 1 according to an embodiment.
[0014] 1, the cellular communication system 1 includes a 5G core network (5GC) 10, user equipment (UE) 100, base station devices (hereinafter sometimes referred to as "base stations") 200-1 and 200-2, and IAB nodes 300-1 and 300-2. The base station 200 may be referred to as a gNB.
[0015] In the following, we will mainly describe an example in which base station 200 is an NR base station, but base station 200 may also be an LTE base station (i.e., eNB).
[0016] In the following, base stations 200-1 and 200-2 may be referred to as gNB 200 (or base station 200), and IAB nodes 300-1 and 300-2 may be referred to as IAB node 300.
[0017] The 5GC 10 has an Access and Mobility Management Function (AMF) 11 and a User Plane Function (UPF) 12. The AMF 11 is a device that performs various mobility controls for the UE 100. The AMF 11 manages information about the area in which the UE 100 is located by communicating with the UE 100 using Non-Access Stratum (NAS) signaling. The UPF 12 is a device that performs transfer control of user data, etc.
[0018] Each gNB 200 is a fixed wireless communication node and manages one or more cells. A cell is used as a term indicating the smallest unit of a wireless communication area. A cell may also be used as a term indicating a function or resource for performing wireless communication with a UE 100. One cell belongs to one carrier frequency. Hereinafter, there may be cases where a cell and a base station are used interchangeably.
[0019] Each gNB 200 is interconnected with the 5GC 10 via an interface called an NG interface. In FIG. 1, two gNBs 200-1 and 200-2 connected to the 5GC 10 are illustrated.
[0020] Each gNB 200 may be divided into a central unit (CU) and a distributed unit (DU). The CU and DU are connected to each other via an interface called an F1 interface. The F1 protocol is a communication protocol between the CU and DU, and includes the F1-C protocol, which is a control plane protocol, and the F1-U protocol, which is a user plane protocol.
[0021] The cellular communication system 1 supports IAB, which enables wireless relay of NR access using NR for backhaul. The donor gNB 200-1 (or donor node, hereinafter sometimes referred to as the "donor node") is the terminal node of the NR backhaul on the network side and is a donor base station with additional functions that support IAB. The backhaul can be multi-hopped via multiple hops (i.e., multiple IAB nodes 300).
[0022] FIG. 1 shows an example in which IAB node 300-1 wirelessly connects with donor node 200-1, IAB node 300-2 wirelessly connects with IAB node 300-1, and the F1 protocol is transmitted over two backhaul hops.
[0023] The UE 100 is a mobile wireless communication device that performs wireless communication with a cell. The UE 100 may be any device that performs wireless communication with the gNB 200 or the IAB node 300. For example, the UE 100 is a mobile phone terminal and / or a tablet terminal, a laptop PC, a sensor or a device provided in a sensor, a vehicle or a device provided in a vehicle, or an aircraft or a device provided in an aircraft. The UE 100 wirelessly connects to the IAB node 300 or the gNB 200 via an access link. FIG. 1 shows an example in which the UE 100 is wirelessly connected to the IAB node 300-2. The UE 100 indirectly communicates with the donor node 200-1 via the IAB node 300-2 and the IAB node 300-1.
[0024] FIG. 2 is a diagram showing an example of the relationship between the IAB node 300, parent nodes, and child nodes.
[0025] As shown in FIG. 2, each IAB node 300 has an IAB-DU corresponding to a base station function unit and an IAB-MT (Mobile Termination) corresponding to a user equipment function unit.
[0026] An adjacent node (i.e., an upper node) on the NR Uu radio interface of the IAB-MT is called a parent node. The parent node is the parent IAB node or the DU of the donor node 200. The radio link between the IAB-MT and the parent node is called a backhaul link (BH link). FIG. 2 shows an example in which the parent nodes of the IAB node 300 are IAB nodes 300-P1 and 300-P2. The direction toward the parent node is called upstream. From the perspective of the UE 100, the upper node of the UE 100 may correspond to the parent node.
[0027] Adjacent nodes (i.e., lower nodes) on the NR access interface of the IAB-DU are called child nodes. The IAB-DU manages the cell, similar to the gNB 200. The IAB-DU terminates the NR Uu radio interface to the UE 100 and lower IAB nodes. The IAB-DU supports the F1 protocol to the CU of the donor node 200-1. In FIG. 2, an example is shown in which the child nodes of the IAB node 300 are IAB nodes 300-C1 to 300-C3, but the child nodes of the IAB node 300 may also include the UE 100. The direction toward the child nodes is called downstream.
[0028] Furthermore, all IAB nodes 300 connected to the donor node 200 via one or more hops form a directed acyclic graph (DAG) topology (hereinafter sometimes referred to as "topology") with the donor node 200 as the root. In this topology, as shown in FIG. 2, adjacent nodes on the IAB-DU interface are child nodes, and adjacent nodes on the IAB-MT interface are parent nodes. The donor node 200 centralizes, for example, resource, topology, and route management of the IAB topology. The donor node 200 is a gNB that provides network access to the UE 100 via a network of backhaul links and access links.
[0029] (Configuration of base station) Next, the configuration of the gNB 200, which is a base station according to the embodiment, will be described. Fig. 3 is a diagram showing an example configuration of the gNB 200. As shown in Fig. 3, the gNB 200 has a wireless communication unit 210, a network communication unit 220, and a control unit 230.
[0030] The wireless communication unit 210 performs wireless communication with the UE 100 and wireless communication with the IAB node 300. The wireless communication unit 210 has a receiving unit 211 and a transmitting unit 212. The receiving unit 211 performs various receptions under the control of the control unit 230. The receiving unit 211 includes an antenna, and converts (down-converts) a wireless signal received by the antenna into a baseband signal (received signal), and outputs the signal to the control unit 230. The transmitting unit 212 performs various transmissions under the control of the control unit 230. The transmitting unit 212 includes an antenna, and converts (up-converts) a baseband signal (transmitted signal) output by the control unit 230 into a wireless signal, and transmits the signal from the antenna.
[0031] The network communication unit 220 performs wired communication (or wireless communication) with the 5GC10 and wired communication (or wireless communication) with other adjacent gNBs 200. The network communication unit 220 has a receiving unit 221 and a transmitting unit 222. The receiving unit 221 performs various receptions under the control of the control unit 230. The receiving unit 221 receives a signal from the outside and outputs the received signal to the control unit 230. The transmitting unit 222 performs various transmissions under the control of the control unit 230. The transmitting unit 222 transmits the transmission signal output by the control unit 230 to the outside.
[0032] The control unit 230 performs various controls in the gNB 200. The control unit 230 includes at least one memory and at least one processor electrically connected to the memory. The memory stores programs executed by the processor and information used in processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation, encoding / decoding, etc. of baseband signals. The CPU executes programs stored in the memory to perform various processes. The processor performs processing of each layer, which will be described later. Note that the control unit 230 may perform each process or operation in the gNB 200 in each of the embodiments shown below.
[0033] (Configuration of Relay Node) Next, a configuration of an IAB node 300, which is a relay node (or relay node device; hereinafter, may be referred to as a "relay node") according to an embodiment, will be described. FIG. 4 is a diagram showing an example configuration of the IAB node 300. As shown in FIG. 4, the IAB node 300 has a wireless communication unit 310 and a control unit 320. The IAB node 300 may have multiple wireless communication units 310.
[0034] The wireless communication unit 310 performs wireless communication (BH link) with the gNB 200 and wireless communication (access link) with the UE 100. The wireless communication unit 310 for BH link communication and the wireless communication unit 310 for access link communication may be provided separately.
[0035] The wireless communication unit 310 has a receiving unit 311 and a transmitting unit 312. The receiving unit 311 performs various types of reception under the control of the control unit 320. The receiving unit 311 includes an antenna, and converts (down-converts) a wireless signal received by the antenna into a baseband signal (received signal), and outputs the signal to the control unit 320. The transmitting unit 312 performs various types of transmission under the control of the control unit 320. The transmitting unit 312 includes an antenna, and converts (up-converts) a baseband signal (transmitted signal) output by the control unit 320 into a wireless signal, and transmits the signal from the antenna.
[0036] The control unit 320 performs various controls in the IAB node 300. The control unit 320 includes at least one memory and at least one processor electrically connected to the memory. The memory stores programs executed by the processor and information used in processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processes. The processor performs processing of each layer, which will be described later. Note that the control unit 320 may perform each process or operation in the IAB node 300 in each of the embodiments described below.
[0037] (Configuration of User Device) Next, a configuration of the UE 100, which is a user device according to the embodiment, will be described. Fig. 5 is a diagram showing an example configuration of the UE 100. As shown in Fig. 5, the UE 100 includes a radio communication unit 110 and a control unit 120.
[0038] The wireless communication unit 110 performs wireless communication in an access link, i.e., wireless communication with the gNB 200 and wireless communication with the IAB node 300. The wireless communication unit 110 may also perform wireless communication in a side link, i.e., wireless communication with other UEs 100. The wireless communication unit 110 has a receiving unit 111 and a transmitting unit 112. The receiving unit 111 performs various receptions under the control of the control unit 120. The receiving unit 111 includes an antenna, and converts (down-converts) a wireless signal received by the antenna into a baseband signal (received signal), and outputs the signal to the control unit 120. The transmitting unit 112 performs various transmissions under the control of the control unit 120. The transmitting unit 112 includes an antenna, and converts (up-converts) a baseband signal (transmitted signal) output by the control unit 120 into a wireless signal, and transmits the signal from the antenna.
[0039] The control unit 120 performs various controls in the UE 100. The control unit 120 includes at least one memory and at least one processor electrically connected to the memory. The memory stores programs executed by the processor and information used in processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation, encoding / decoding, etc. of baseband signals. The CPU executes programs stored in the memory to perform various processes. The processor performs processing of each layer, which will be described later. Note that the control unit 120 may be configured to perform each process in the UE 100 in each of the embodiments described below.
[0040] (Protocol Stack Configuration) Next, a description will be given of the configuration of a protocol stack according to the embodiment. Fig. 6 is a diagram showing an example of a protocol stack related to an IAB-MT RRC connection and a NAS connection.
[0041] As shown in FIG. 6, the IAB-MT of IAB node 300-2 has a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a non-access stratum (NAS) layer.
[0042] The PHY layer performs encoding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data and control information are transmitted between the PHY layer of the IAB-MT of IAB node 300-2 and the PHY layer of the IAB-DU of IAB node 300-1 via a physical channel.
[0043] The MAC layer performs data priority control, retransmission processing using Hybrid Automatic Repeat reQuest (HARQ), random access procedures, etc. Data and control information are transmitted via transport channels between the MAC layer of the IAB-MT of IAB node 300-2 and the MAC layer of the IAB-DU of IAB node 300-1. The MAC layer of the IAB-DU includes a scheduler. The scheduler determines the uplink and downlink transport format (transport block size, modulation and coding scheme (MCS)) and the allocated resource blocks.
[0044] The RLC layer transmits data to the RLC layer on the receiving side using the functions of the MAC layer and PHY layer. Data and control information are transmitted between the RLC layer of the IAB-MT of IAB node 300-2 and the RLC layer of the IAB-DU of IAB node 300-1 via logical channels.
[0045] The PDCP layer performs header compression / decompression, and encryption / decryption. Data and control information are transmitted between the PDCP layer of the IAB-MT of the IAB node 300-2 and the PDCP layer of the donor node 200 via a radio bearer.
[0046] The RRC layer controls logical channels, transport channels, and physical channels in response to the establishment, re-establishment, and release of radio bearers. RRC signaling for various settings is transmitted between the RRC layer of the IAB-MT of the IAB node 300-2 and the RRC layer of the donor node 200. When there is an RRC connection with the donor node 200, the IAB-MT is in an RRC connected state. When there is no RRC connection with the donor node 200, the IAB-MT is in an RRC idle state.
[0047] The NAS layer, which is positioned above the RRC layer, performs session management, mobility management, etc. NAS signaling is transmitted between the NAS layer of the IAB-MT of the IAB node 300-2 and the AMF 11.
[0048] Figure 7 shows a protocol stack for the F1-U protocol. Figure 8 shows a protocol stack for the F1-C protocol. Here, an example is shown in which the donor node 200 is divided into a CU and a DU.
[0049] As shown in Figure 7, the IAB-MT of IAB node 300-2, the IAB-DU of IAB node 300-1, the IAB-MT of IAB node 300-1, and the DU of donor node 200 each have a BAP (Backhaul Adaptation Protocol) layer above the RLC layer. The BAP layer is a layer that performs routing processing and bearer mapping / demapping processing. In the backhaul, the IP layer is transmitted via the BAP layer, enabling routing over multiple hops.
[0050] In each backhaul link, PDUs (Protocol Data Units) of the BAP layer are transmitted by a backhaul RLC channel (BH NR RLC channel). By configuring multiple backhaul RLC channels in each BH link, traffic prioritization and QoS (Quality of Service) control are possible. The association between BAP PDUs and backhaul RLC channels is performed by the BAP layer of each IAB node 300 and the BAP layer of the donor node 200.
[0051] As shown in FIG. 8, the protocol stack of the F1-C protocol has an F1AP layer and an SCTP layer instead of the GTP-U layer and UDP layer shown in FIG.
[0052] In the following, the processing or operations performed by the IAB-DU and IAB-MT of the IAB may be simply described as the processing or operations of the "IAB." For example, the transmission of a BAP layer message from the IAB-DU of IAB node 300-1 to the IAB-MT of IAB node 300-2 will be described as the IAB node 300-1 sending the message to IAB node 300-2. In addition, the processing or operations of the DU or CU of the donor node 200 may also be simply described as the processing or operations of the "donor node."
[0053] Also, the upstream direction and the uplink (UL) direction may be used interchangeably, and the downstream direction and the downlink (DL) direction may be used interchangeably.
[0054] (Mobile IAB Node) Currently, 3GPP has begun discussions toward the introduction of mobile IAB nodes. A mobile IAB node is, for example, an IAB node that is moving. A mobile IAB node may be an IAB node that is capable of moving. Alternatively, a mobile IAB node may be an IAB node that is currently stationary but is certain to move in the future (or is expected to move in the future).
[0055] The mobile IAB node enables, for example, a UE 100 under the mobile IAB node to receive services from the mobile IAB node while moving in accordance with the movement of the mobile IAB node. For example, a case is envisioned in which a user (or UE 100) on a vehicle receives services via a mobile IAB node installed on the vehicle.
[0056] On the other hand, in contrast to mobile IAB nodes, there are also IAB nodes that do not move. Such IAB nodes are sometimes referred to as intermediate IAB nodes. An intermediate IAB node is, for example, an IAB node that does not move. Alternatively, the intermediate IAB node may be a stationary IAB node. Alternatively, the intermediate IAB node may be an IAB node that remains stationary (or does not move) and remains installed at its installation location. Alternatively, the intermediate IAB node may be a stationary IAB node that does not move. The intermediate IAB node may also be a fixed IAB node.
[0057] A mobile IAB node can also be connected to an intermediate IAB node. Also, a mobile IAB node can be connected to a donor node 200. A mobile IAB node can also change its connection destination due to movement (migration or handover). The connection source may be an intermediate IAB node. The connection source may be the donor node 200. Also, the connection destination may be an intermediate IAB node. The connection destination may be the donor node 200.
[0058] In the following, the terms "migration" of a mobile IAB node and "handover" of a mobile IAB node may be used interchangeably.
[0059] In the following description, the mobile IAB node may be referred to as a "mobile IAB node." The mobile IAB node may also be referred to as a "migrating IAB node." In either case, the mobile IAB node may be referred to as a mobile IAB node.
[0060] (Communication Control Method According to First Embodiment) Next, a communication control method according to the first embodiment will be described.
[0061] (RACH-less handover) 3GPP specifies RACH-less handover (RACH-less HO) (for example, 3GPP TS 36.300 V14.13.0 (2020-12)). RACH-less handover is a handover that skips the random access procedure. In RACH-less handover, for example, the following processing is performed.
[0062] That is, the UE 100 receives an RRC connection reconfiguration (RRCConnectionReconfiguration) message including RACH-less handover configuration information (MobilityControlInfo) from the source cell, and thereby the RACH-less handover is configured. When the UE 100 receives a handover command from the source cell, the UE 100 switches the connection destination from the source cell to the target cell and synchronizes with the target cell. Thereafter, the UE 100 uses the uplink resource (UL-grant) included in the setting information (MobilityControlInfo) without transmitting a preamble signal (Msg1) in the random access procedure and receiving a response signal (Msg2) to the preamble signal, and transmits an RRC connection reconfiguration complete (RRCConnectionReconfigurationComplete) message (Msg3) to the target cell.
[0063] In the RACH-less handover, the random access procedure is skipped, and therefore, the delay in the execution time of the handover can be improved in the UE 100 compared to when the random access procedure is executed.
[0064] (Beamforming and Synchronization) On the other hand, NR uses beamforming technology. Beamforming technology is, for example, a technology for transmitting radio waves in a specific direction or receiving radio waves from a specific direction. NR makes it possible to transmit radio waves in a specific direction and receive radio waves from a specific direction by causing multiple antenna elements to operate cooperatively through phase control.
[0065] The base station 200 periodically transmits a synchronization signal called a synchronization signal block (SSB). The base station 200 transmits the SSB for each beam while sequentially switching the beam direction at different timings. The UE 100 detects each SSB and selects an SSB to select an optimal beam. The UE 100 then uses the SSB to establish synchronization with the base station 200. The SSB includes an SSB index that distinguishes the SSB from other SSBs. The UE 100 identifies the optimal beam using the SSB index and performs a random access procedure using resources linked to the selected SSB index as resources for a PRACH (Physical Random Access Channel).
[0066] (Challenges of RACH (Random Access Channel)-less handover) In the random access procedure, UE100 notifies gNB200 of which beam is the optimal beam by transmitting a preamble signal as Msg1 to gNB200 using resources linked to the selected SSB index. gNB200 can transmit a response signal (Msg2) to UE100 using the beam corresponding to the SSB index, and thereafter, communication is performed between UE100 and gNB200 using the optimal beam.
[0067] However, in RACH-less handover, Msg1 is not transmitted. Therefore, UE100 cannot notify gNB200 which beam is the optimal beam, and gNB200 cannot know which beam is the optimal beam for UE100. Therefore, UE100 may not be able to properly transmit the RRC connection reconfiguration complete message (Msg3) to the target cell. In addition, UE100 may not be able to receive a response (DL transmission signal from gNB200) corresponding to the RRC connection reconfiguration complete message (Msg3).
[0068] (Scenario According to First Embodiment) Here, a scenario regarding handover according to the first embodiment will be described.
[0069] 9 is a diagram illustrating an example of a scenario according to the first embodiment. FIG. 9 illustrates an example in which the connection destination of the mobile IAB node 300M is switched from the donor node (IAB donor #1, i.e., source donor node) 200-1 to the donor node (IAB donor #2, i.e., target donor node) 200-2. In this case, the UE 100 under the mobile IAB node 300M also moves along with the movement of the mobile IAB node 300M. For example, the mobile IAB node 300M is installed in a vehicle, and the UE 100 is a UE owned by a user aboard the vehicle.
[0070] 9, before moving, the mobile IAB node 300M is located under the cell (i.e., source cell) managed by donor DU#1 (IAB donor DU#1) (200-D1) of the source donor node 200-1. The IAB-DU#1 of the mobile IAB node 300M is connected to donor CU#1 (IAB donor CU#1) (200-C1) of the source donor node 200-1 via an F1 connection.
[0071] Then, the mobile IAB node 300M moves to a cell (i.e., a target cell) managed by donor DU #2 (IAB donor DU #2) (200-D2) of the target donor node 200-2. By moving from the source cell to the target cell, the mobile IAB node 300M manages the cell using a different cell ID. Therefore, the mobile IAB node 300M logically establishes IAB-DU #2. In this case, IAB-DU #2 connects to donor CU #2 (IAB donor CU #2) (200-C2) of the target donor node 200-2 via an F1 connection.
[0072] At this time, the UE 100 switches the connection destination from IAB-DU #1 to IAB-DU #2, which is called full migration. In the case of full migration, the connection destination of the UE 100 becomes the donor CU #2 (200-C2) of the target donor node 200-2 via IAB-DU #2. However, in the UE 100, although it is logical, the connection destination IAB-DU is switched from IAB-DU #1 (the source cell managed by) to IAB-DU #2 (the target cell managed by), so it can also be considered as a handover. In the following, there are cases where the terms "full migration" and "handover" are used interchangeably.
[0073] In this way, the UE 100 under the mobile IAB node 300M may perform a handover. In particular, it is assumed that a handover by the UE 100 under the mobile IAB node 300M does not involve physical movement. Therefore, by having the UE 100 perform a RACH-less handover, it is possible to reduce delay and signaling compared to when a random access procedure is executed.
[0074] However, even in this scenario, when UE 100 under mobile IAB node 300M performs RACH-less handover, Msg 1 is not transmitted. Therefore, UE 100 cannot notify IAB-DU #2 of mobile IAB node 300M which beam is the optimal beam, and IAB-DU #2 cannot know which beam is the optimal beam for UE 100. Therefore, even in this UE 100, there are cases where it is not possible to properly transmit an RRC connection reconfiguration complete message (Msg 3) to the target cell.
[0075] (Problem Associated with First Embodiment) In 3GPP, discussions are underway regarding RACH-less handover for UE 100 under the control of mobile IAB node 300M. In particular, in 3GPP, the following two options are being considered for RACH-less handover.
[0076] Option 1: Explicit beam information is included in the handover command (explicit approach).
[0077] Option 2: Reuse the same beam used in the source cell (implicit approach).
[0078] At present, the details of either option have not been determined, and it has not been determined what kind of beam information will be included. As shown in the above-described scenario ( FIG. 9 ), there is a situation specific to the mobile IAB node 300M in which the UE 100 physically uses the same DU before and after handover. In such a situation, it is assumed that Option 2 is effective. However, in situations other than the above-described scenario, Option 1 may be effective.
[0079] Taking into consideration the above-mentioned considerations, the first embodiment aims to enable the UE 100 to appropriately transmit the RRC reconfiguration complete message (Msg3) to the target cell in the RACH-less handover.
[0080] Therefore, in the first embodiment, first, a target donor node (e.g., target donor node 200-2) transmits a handover command including index information related to an index of a synchronization signal block (SSB) to a user equipment (e.g., UE 100) via a source cell. Second, the user equipment receives the handover command. Third, the user equipment transmits an RRC reconfiguration complete (RRCReconfigurationComplete) message to the target cell using resources linked to the index of the synchronization signal block.
[0081] As described above, in the first embodiment, since the handover command includes the SSB index, the UE 100 can grasp what kind of beam is used in the target cell. Also, in the first embodiment, since the resource used to transmit the RRC reconfiguration complete message (Msg 3) is linked to the SSB index included in the handover command, the UE 100 can also transmit the RRC reconfiguration complete message (Msg 3) to the target cell using the resource. Therefore, in the first embodiment, the UE 100 can appropriately transmit the RRC reconfiguration complete message (Msg 3) to the target cell in a RACH-less handover.
[0082] (Example of Operation According to First Embodiment) Next, an example of operation according to the first embodiment will be described. Fig. 10 is a diagram showing an example of operation according to the first embodiment.
[0083] The operation example shown in Fig. 10 mainly represents an operation example when the scenario shown in Fig. 9 is used. That is, it is assumed that UE 100 under the control of mobile IAB node 300M moves from a source cell managed by IAB-DU #1 of mobile IAB node 300M to a target cell managed by IAB-DU #2 of mobile IAB node 300M as mobile IAB node 300M moves.
[0084] In the following, there may be cases where IAB-DU#1 and the source cell are used without distinction, and there may be cases where IAB-DU#2 and the target cell are used without distinction.
[0085] As shown in FIG. 10, in step S10, the UE 100 is in an RRC connected state with the source cell.
[0086] In step S11, the UE 100 transmits a measurement report to the source cell. The measurement report includes a radio quality measurement value for each SSB index for the target cell. The radio quality measurement value may be any one of RSRP (Reference Signal Received Power), RSRP (Reference Signal Received Quality), and SINR (Signal to Interference plus Noise Ratio). That is, the measurement report includes a radio quality measurement value for each SSB of the target cell.
[0087] In step S12, in response to receiving the measurement report, the source cell transmits an F1 message including the measurement report to donor CU #1 (200-C1) of source donor node 200-1. Donor CU #1 (200-C1) receives the F1 message.
[0088] In step S13, the donor CU#1 (200-C1) decides to hand over the UE 100 based on the measurement report.
[0089] In step S14, the donor CU#1 (200-C1) transmits a handover request message, which is an Xn message, to the donor CU#2 (200-C2) of the target donor node 200-2. The handover request message may include at least one of the following information:
[0090] (A1) The measurement report
[0091] (A2) Information requesting RACH-less handover
[0092] (A3) Current Timing Advance (TA) Setting Value of UE 100 In the following description, it is assumed that the handover request message includes a measurement report.
[0093] In step S15, the donor CU#2 (200-C2) decides to accept the handover request, and transmits a handover request acknowledgement (HANDOVER REQUEST ACKNOWLEDGE) message (Xn message) to the donor CU#1 (200-C1).
[0094] The handover request acceptance message may include at least one of the following information:
[0095] (B1) Information indicating the SSB index
[0096] (B2) Information indicating UL resources In the above (B1), the SSB index may be an SSB index with the best quality among the radio measurement qualities included in the measurement report received from the UE 100. The information indicating the SSB index is an example of index information related to the SSB index. The information indicating the SSB index may be information indicating an SSB index (first index) that the UE 100 applies to the target cell. Alternatively, the information indicating the SSB index may be an example of beam information.
[0097] In the above (B2), the information indicating the UL resource is resource information used by the UE 100 to transmit an RRC reconfiguration complete message (Msg3). The UL resource itself may be a resource configured by a configured grant (CG). Alternatively, the UL resource itself may be a resource configured by a dynamic grant (DG). The UL resource may be designated as an UL resource linked to the SSB index of the above (B1). Alternatively, the UE 100 may transmit the RRC reconfiguration complete message using the UL resource linked to the selected SSB index.
[0098] B1 and B2 may be stored in a handover command (HO Command). The handover command is a message included in a handover request accept message as an RRC container (RRC Reconfiguration with sync message). In the following description, it is assumed that at least one of B1 and B2 is included in the handover command.
[0099] In addition, when the handover request message (step S14) includes a TA value, the donor CU #2 (200-C2) may determine whether or not a RACH-less handover is possible based on the TA value. For example, the donor CU #2 (200-C2) may determine that a RACH-less handover cannot be performed if the TA value is greater than or equal to a threshold compared with the TA value applied by the target cell to the UE 100, and may determine that a RACH-less handover can be performed if this is not the case. In the above-mentioned scenario (FIG. 9), if it is assumed that the distance between the UE 100 and IAB-DU #1 and IAB-DU #2 is almost the same and the TA value is also unchanged, the donor CU #2 (200-C2) can determine that a RACH-less handover is possible, and if not, it can determine that a RACH-less handover is not possible.
[0100] Alternatively, when a TA value is included in the handover request message, the donor CU #2 (200-C2) may determine whether or not it is necessary to explicitly provide the TA value based on the TA value. Similar to the determination of whether or not RACH-less handover is possible, the donor CU #2 (200-C2) may determine that it is necessary to explicitly provide the TA value (second TA value) when the TA value (first TA value) is different from the TA value (second TA value) that the target cell applies to the UE 100 by a threshold or more, and may determine that it is not necessary to explicitly provide the TA value (second TA value) when this is not the case.
[0101] In step S16, in response to receiving the handover request permission message, donor CU #1 (200-C1) of source donor node 200-1 extracts a synchronized RRC reconfiguration completion (handover command) message from the handover request permission message and transmits an F1 message including the message to the source cell.
[0102] In step S16, in response to receiving the F1 message, the source cell extracts a synchronization-included RRC reconfiguration complete (handover command) message from the F1 message, and transmits the message to the UE 100. The UE 100 receives the message.
[0103] In step S17, in order to perform a RACH-less handover, the UE 100 transmits an RRC reconfiguration complete message (Msg3) to the target cell using at least one of the above (B1) and (B2) included in the synchronization-attached RRC reconfiguration complete (handover command) message. That is, when the UE 100 uses the above (B1), it transmits an RRC reconfiguration complete message to the target cell using resources linked to the SSB index. Details will be described later. On the other hand, when the UE 100 uses the above (B2), it is sufficient to transmit an RRC reconfiguration complete message to the target cell using the UL resource indicated as information indicating the UL resource.
[0104] In step S18, the target cell transmits a reception confirmation signal (HARQ ACK) to the UE 100 in response to successfully receiving the RRC reconfiguration complete message.
[0105] In step S19, when the UE 100 receives the reception confirmation signal, the UE 100 confirms that the execution of the RACH-less handover has been completed.
[0106] (Method of linking SSB index with UL resource) Here, the method of linking SSB index with UL resource (step S17) will be described. There are two linking methods: one using configured grant (CG) and one using dynamic grant (DG).
[0107] (1) When CG is used When CG is used, resources configured by configuration information (Configured Grant Config) are used. The UE 100 receives an RRC message including the configuration information from the source cell, and thereby, resources by the CG (hereinafter, sometimes referred to as "resources by CG configuration") are configured. The resources by the CG are resources (first resources) configured using the RRC message.
[0108] Fig. 11(A) is a diagram illustrating an example of resources configured by CG according to the first embodiment. In the example of Fig. 11(A), resources from UL resource #1 to UL resource #5 are configured. As for the resources configured by CG, one resource may be configured. Alternatively, multiple resources may be configured as shown in Fig. 11(A).
[0109] First, the handover command may explicitly include information indicating an index specifying the resource (hereinafter, this information may be referred to as "configuration index information"). The configuration index information may explicitly specify each resource. For example, "configuration index information: UL resource #1, UL resource #2". This indicates that UL resource #1 and UL resource #2 are used as resources for transmitting an RRC reconfiguration complete message (Msg3).
[0110] Alternatively, the configuration index information may be explicitly specified for each group. For example, "configuration index information: CG#1, CG#2". In this case, it indicates that the UL resources included in CG#1 and CG#2 are used as resources for transmitting the RRC reconfiguration complete message (Msg3). However, which group each resource belongs to may be specified in the handover command or may be set by the configuration information included in the RRC message transmitted from the source cell.
[0111] Alternatively, the configuration index information may be specified by flag information. For example, "Configuration index information: UL resource #1, "Use for RACH-less handover Msg3" (flag present) UL resource #2, "Use for RACH-less handover Msg3" (flag present) UL resource #3, (no flag = not for RACH-less handover Msg3)..." The presence or absence of a flag may be represented by one bit. That is, "1" may indicate the presence of the flag, and "0" may indicate the absence of the flag, or vice versa. Alternatively, the configuration index information may be specified for each group as "Configuration index information: CG #1, "Use for RACH-less handover Msg3" (flag present) CG #2, "Use for RACH-less handover Msg3" (flag present) CG #3, (no flag = not for RACH-less handover Msg3)..."
[0112] In this way, the handover command may include configuration index information specifying a resource (first resource) based on CG configuration, and the configuration index information may be used to configure a transmission resource for the RRC reconfiguration complete message (Msg3). Alternatively, the CG-configured resource included in the handover command may be implicitly indicated to the UE 100 as a transmission resource for the RRC reconfiguration complete message (Msg3). When the configuration index information is included in the handover command, the UE 100 will transmit the RRC reconfiguration complete message (Msg3) using the resource specified by the configuration index information.
[0113] Secondly, based on the correspondence between the SSB index and the resource according to the CG configuration, the resource associated with the SSB index (above B1) may be used as the transmission resource for the RRC reconfiguration complete message (Msg3).
[0114] In this case, a resource count value is allocated to each resource set by the CG based on the reference timing. For example, as shown in FIG. 11A, the resource count value is allocated in ascending order of frequency and closest to the reference timing. The reference timing may be (the boundary of) radio frame #0. The resource count value may be allocated in order starting from "1" as shown in FIG. 11A. The resource count value may also be allocated in order starting from "0".
[0115] The handover command includes linking information indicating which CG-configured resource is linked to each SSB index. For example, the linking information includes information indicating that SSB index #1 is linked to UL resource #1, that SSB index #2 is linked to UL resource #2, etc. In this case, multiple UL resources may be linked to one SSB index. UE 100 may transmit an RRC reconfiguration complete message (Msg3) using the resource linked to the SSB index determined to be the best based on the linking information included in the handover command (step S17). In this case, the source cell can determine the SSB index (or beam) determined to be the best by UE 100 from the UL resource for which the RRC reconfiguration complete message (Msg3) is received. The source cell can then communicate with UE 100 using this beam. This allows UE 100 to perform optimal communication with the source cell.
[0116] Alternatively, the number of UL resources for each SSB index may be set in the handover command based on the UL resource number allocation rule. For example, when the UL resources shown in Fig. 11(A) are configured by CG configuration, if "1" is set as the number of UL resources for each SSB index in the handover command, based on the UL resource number allocation rule, SSB index #1 may be linked to UL resource #1, SSB index #2 may be linked to UL resource #2, SSB index #3 may be linked to UL resource #3, etc. When UE 100 selects SSB index #1 (as the best SSB), it can transmit Msg3 using UL resource #1. For example, if "2" is set as the number of UL resources per SSB index in the handover command, then, assuming the UL resource number allocation rule, SSB index #1 is linked to UL resource #1 and UL resource #2, and SSB index #2 is linked to UL resource #3 and UL resource #4, and so on. When UE 100 selects SSB index #2 (as the best SSB), it can transmit Msg3 using UL resource #3 or UL resource #4 (or using UL resource #3 and UL resource #4). The number of UL resources per SSB index included in the handover command may be setting index information or linking information.
[0117] (2) When DG is used When DG is used, resources set by downlink control information (DCI) are used. By receiving the DCI, the UE 100 is configured with resources by the DG (hereinafter, sometimes referred to as "resources by DG setting").
[0118] Fig. 11(B) is a diagram showing an example of resources configured by DG configuration according to the first embodiment. In the example of Fig. 11(B), each of resources DG#1 to DG#5 is configured by DCI. One resource may be configured as the resource configured by DG configuration. Alternatively, multiple resources may be configured as shown in Fig. 11(B).
[0119] The handover command includes information associating the SSB index with each resource according to the DG configuration. For example, the association information includes information indicating that SSB index #1 is associated with DG #1 and DG #2, information indicating that SSB index #2 is associated with DG #3, information indicating that SSB index #3 is associated with DG #4, etc. One SSB index may be associated with a resource according to one DG configuration, or one SSB index may be associated with resources according to multiple DG configurations.
[0120] As in the case of CG, UE100 may transmit an RRC reconfiguration complete message (Msg3) using resources by DG configuration linked to the SSB index determined to be the best based on the linking information included in the handover command (step S17). In this case, the source cell can grasp the SSB index (or beam) determined to be the best by UE100 from the UL resource on which the RRC reconfiguration complete message (Msg3) is received. Thereafter, the source cell can communicate with UE100 using the beam. Therefore, UE100 can perform optimal communication with the source cell.
[0121] The resources themselves configured by the DG may be included in the handover command. That is, information about the resources included in the DCI may be included in the handover command. The handover command may include information about the resources as well as information linking each DG with each SSB index. In this case, the UE 100 can transmit an RRC reconfiguration complete message (Msg3) based on the handover command without monitoring the DCI.
[0122] (Another operation example according to the first embodiment) In the first embodiment, an operation example has been described based on the scenario shown in Fig. 9, but is not limited to this. For example, the first embodiment can also be applied to handover between the UE 100 and the gNB 200.
[0123] In this case, in Figure 10, this can be implemented by replacing the "IAB-DU #1 (source cell)" of the mobile IAB node 300M with "DU (source cell provided by) of the source gNB" and the "donor CU #1", which is donor CU #1 (200-C1) of the source donor node 200-1, with "CU of the source gNB", and by replacing the "IAB-DU #2 (target cell)" of the mobile IAB node 300M with "DU (target cell provided by) of the target gNB" and the "donor CU #2", which is donor CU #2 (200-C2) of the target donor node 200-2, with "CU of the target gNB".
[0124] Specifically, first, a source base station (e.g., a source gNB) transmits a handover command including index information related to an index of a synchronization signal block (SSB) to a user equipment (e.g., a UE 100) (e.g., step S16 in FIG. 10). Second, the user equipment receives the handover command. Third, the user equipment transmits an RRC reconfiguration complete message to a target base station (e.g., a target gNB) using resources associated with the index of the synchronization signal block (e.g., step S17 in FIG. 10).
[0125] As a result, in other operation examples as well, similarly to the first embodiment, the UE 100 can appropriately transmit the RRC reconfiguration complete message (Msg3) in the RACH-less handover.
[0126] Second Embodiment Next, a second embodiment will be described, focusing on the differences from the first embodiment.
[0127] In the first embodiment, the index information included in the handover command is the information indicating the SSB index (option 1), which is explicitly included. In the second embodiment, the handover command is described as including information indicating that the same index as the SSB index used by the UE 100 for the source cell is also used for the target cell (option 2). That is, in the second embodiment, a handover command that supports both the above option 1 and the above option 2 is described.
[0128] Specifically, the index information included in the handover command represents either information indicating the first index of the synchronization signal block that the user equipment (e.g., UE 100) applies to the target cell, or information indicating that the second index of the synchronization signal block that the user equipment applied to the source cell is to be applied to the target cell.
[0129] In the UE 100, it is possible to determine based on the handover command whether the SSB index to be applied to the source cell is a new SSB index (first index) or whether the SSB index (second index) used in the source cell should be reused. Then, the UE 100 can communicate with the gNB 200 using the beam indicated by the SSB index. Therefore, the UE 100 can also transmit an RRC reconfiguration complete message (Msg3) using the beam.
[0130] Specifically, when the handover command includes information indicating the first index, the user equipment transmits the RRC reconfiguration complete message using the resource associated with the first index. On the other hand, when the handover command includes information indicating that the index is the same as the second index, the UE 100 transmits the RRC reconfiguration complete message using the resource used in communication with the source cell.
[0131] Therefore, also in the second embodiment, it is possible to appropriately transmit the RRC reconfiguration complete message (Msg3) to the target cell in a RACH-less handover.
[0132] (Operation example according to the second embodiment) Next, an operation example according to the second embodiment will be described. Fig. 12 is a diagram showing an operation example according to the second embodiment. Like the first embodiment, Fig. 12 also shows an operation example based on the scenario shown in Fig. 9.
[0133] Steps S10 to S14 are the same as those in the first embodiment.
[0134] In step S20, donor CU #2 (200-C2) of target donor node 200-2 decides to accept the handover request and transmits a handover request permission message to donor CU #1 (200-C1). At least one of the following pieces of information is set as index information in the handover request permission message (specifically, a handover command):
[0135] (C1) Information indicating the SSB index that the UE 100 applies to the target cell
[0136] (C2) Information indicating that the UE 100 applies the SSB index applied to the source cell to the target cell. The above (C1) is the same as (B1) in the first embodiment. The handover command may include either (C1) or (C2) using a selection (CHOICE) syntax. The donor CU #1 (200-C1) can transmit either of two types of messages using one handover command.
[0137] Steps S21 and thereafter can be carried out in the same manner as in the first embodiment.
[0138] However, when the handover command includes (C1), the UE 100 uses the resource associated with the SSB index to transmit an RRC reconfiguration complete message (Msg3) to the target cell, as in the first embodiment (step S17). On the other hand, when the handover command includes (C2), the UE 100 uses the UL resource that the UE 100 used for communication with the source cell to transmit an RRC reconfiguration complete message (Msg3) to the target cell (step S17).
[0139] (Another operation example according to the second embodiment) In the second embodiment, an operation example has been described based on the scenario shown in Fig. 9, but is not limited to this. For example, the second embodiment can also be applied to handover between the UE 100 and the gNB 200, similar to the first embodiment.
[0140] In this case, in Figure 12, this can be implemented by replacing the "IAB-DU #1 (source cell)" of the mobile IAB node 300M with "DU (source cell provided by) of the source gNB" and the "donor CU #1", which is donor CU #1 (200-C1) of the source donor node 200-1, with "CU of the source gNB", and by replacing the "IAB-DU #2 (target cell)" of the mobile IAB node 300M with "DU (target cell provided by) of the target gNB" and the "donor CU #2", which is donor CU #2 (200-C2) of the target donor node 200-2, with "CU of the target gNB".
[0141] Third Embodiment Next, a third embodiment will be described, focusing on the differences from the first embodiment.
[0142] In the third embodiment, donor CU #1 (200-C1) (or source gNB 200-1) of source donor node 200-1 decides to perform handover (i.e., RACH-less handover) when the SSB index included in the measurement report is the same as the SSB index that it applies to UE 100.
[0143] Specifically, a source donor node (e.g., donor CU #1 (200-C1) of source donor node 200-1) decides to perform a RACH-less handover if the index included in the measurement report is identical to the index of the synchronization signal block that the source donor node itself applies to a user equipment (e.g., UE 100).
[0144] As a result, for example, in the source donor node 200-1, since the identity of the SSB index is determined using the SSB index that the source donor node 200-1 applies to the UE 100, it is possible to appropriately execute option 2. Then, by transmitting a handover command including information indicating the same SSB index as the source cell, etc., to the UE 100, the UE 100 can reuse the resources used in the source cell and transmit an RRC reconfiguration complete message (Msg3) to the target cell. Therefore, even in the third embodiment, it is possible to appropriately transmit the RRC reconfiguration complete message (Msg3) to the target cell.
[0145] (Example of Operation According to Third Embodiment) Next, an example of operation according to the third embodiment will be described. Fig. 13 is a diagram showing an example of operation according to the third embodiment.
[0146] Steps S10 to S12 are the same as those in the first embodiment.
[0147] In step S30, the donor CU #1 (200-C1) of the source donor node 200-1 compares the SSB index included in the measurement report with the SSB index currently applied by the source cell to the UE 100, and determines whether they are the same. If they are the same, the donor CU #1 (200-C1) decides to perform a RACH-less handover. If there are multiple SSB indices included in the measurement report, the donor CU #1 (200-C1) may decide to perform a RACH-less handover if the SSB index that the donor CU #1 (200-C1) applies to the UE 100 is included among them. If they are not the same (or if all the SSB indices included in the measurement report do not include the SSB index that the donor CU #1 (200-C1) applies to the UE 100), the donor CU #1 (200-C1) may decide not to perform a RACH-less handover.
[0148] In addition, the SSB index currently applied to the UE 100 by the source cell may be received from the source cell using an F1 message.
[0149] In step S31, the donor CU#1 (200-C1) transmits a handover request message to the donor CU#2 (200-C2) of the target donor node 200-2. The handover request message may include at least one of the following information:
[0150] (D1) SSB index (of the source cell) currently used by UE 100
[0151] (D2) Information indicating that the SSB index (of the source cell) currently used by the UE 100 can continue to be used. The above (D1) may be the SSB index currently used by the source cell for the UE 100. Meanwhile, the above (D2) may represent a request for the above-mentioned option 2.
[0152] In step S32, donor CU#2 (200-C2) of target donor node 200-2 decides to accept the handover request and sends a handover request acceptance message including a handover command to donor CU#1 (200-C1) of source donor node 200-1. The handover command may include any of the following information:
[0153] (E1) SSB index
[0154] (E2) Information indicating continued use of currently used SSB index The above (E1) may represent the SSB index notified by (D1). That is, it may represent the SSB index that the source cell is currently applying to the UE 100. Alternatively, the above (E1) may be the index that the donor CU #2 (200-C2) considers to be the best SSB index that the UE 100 is currently applying based on the SSB index included in the measurement report.
[0155] Step S33 and subsequent steps are the same as those in the first embodiment, except that the UE 100 transmits an RRC reconfiguration complete message (Msg3) to the target cell by using the UL resource used in the communication of the source cell based on the above (E1) or (E2) included in the handover command (step S17).
[0156] (Other operation examples of the third embodiment) In the third embodiment, an operation example has also been described based on the scenario shown in Fig. 9, but is not limited to this. For example, the third embodiment can also be applied to handover between the UE 100 and the gNB 200, as in the first embodiment.
[0157] In this case, in Figure 13, this can be implemented by replacing the "IAB-DU #1 (source cell)" of the mobile IAB node 300M with "DU (source cell provided by) of the source gNB" and the "donor CU #1", which is donor CU #1 (200-C1) of the source donor node 200-1, with "CU of the source gNB", and by replacing the "IAB-DU #2 (target cell)" of the mobile IAB node 300M with "DU (target cell provided by) of the target gNB" and the "donor CU #2", which is donor CU #2 (200-C2) of the target donor node 200-2, with "CU of the target gNB".
[0158] Fourth Embodiment Next, a fourth embodiment will be described, focusing on the differences from the first embodiment.
[0159] In the first embodiment, an example in which an SSB index is explicitly specified in a handover command has been described. In the second embodiment, an example of a handover command supporting option 1 and option 2 has been described. In the fourth embodiment, an example in which beam information is not explicitly specified in a handover command will be described. In this case, the UE 100 accesses the target cell using the beam information used in the source cell.
[0160] Specifically, first, a target donor node (e.g., donor CU #2 (200-C2) of target donor node 200-2) transmits a handover command that does not explicitly include beam information to a user equipment (e.g., UE 100) via a source cell. Second, the user equipment receives the handover command. Third, the user equipment transmits an RRC reconfiguration complete message to the target cell using the beam information used in the source cell.
[0161] In this way, even if the SSB index is not explicitly included in the handover command, the UE 100 can transmit the RRC reconfiguration complete message (Msg3) to the target cell by using the beam information used in the source cell. Therefore, in the fourth embodiment, the UE 100 can also appropriately transmit the RRC reconfiguration complete message (Msg3) to the target cell in the RACH-less handover.
[0162] (Example of Operation According to Fourth Embodiment) Next, an example of operation according to the fourth embodiment will be described.
[0163] FIG. 14 is a diagram illustrating an example of operation according to the fourth embodiment.
[0164] Steps S10 to S14 may be the same operations as in the first embodiment. However, in step S12, the source cell may include the beam information used in communication with the UE 100 in an F1 message together with a measurement report and transmit it to the donor CU #1 (200-C1) of the source donor node 200-1. Then, in step S14, the donor CU #1 (200-C1) may transmit a handover request message including the beam information and the measurement report to the donor CU #2 (200-C2) of the target donor node 200-2. Alternatively, if the donor CU #1 (200-C1) manages the beam information of the source cell, the source cell may not transmit the beam information, and the donor CU #1 (200-C1) may transmit a handover request message including the beam information and the measurement report (step S14).
[0165] In step S40, donor CU#2 (200-C2) of target donor node 200-2 determines whether or not to explicitly notify beam information.
[0166] First, the donor CU # 2 (200-C2) may determine not to explicitly notify when the same resource is used in the source cell and the target cell. If the same resource is used, the UE 100 can transmit, for example, an RRC reconfiguration complete message (Msg3) to the target cell without explicitly notifying the beam information.
[0167] Secondly, the donor CU # 2 (200-C2) may determine not to explicitly notify when the same beam (SSB index) is used in the source cell and the target cell. If the same beam is used, the UE 100 can access the target cell using the beam used in the source cell without notifying the beam information, and can also transmit an RRC reconfiguration complete message (Msg3) to the target cell using the beam.
[0168] In addition, in cases other than those mentioned above, donor CU #2 (200-C2) may explicitly include beam information in the handover and transmit it.
[0169] In step S41, if donor CU #2 (200-C2) explicitly notifies beam information, it includes the beam information in the handover command and sends a handover request permission message including the handover command to donor CU #1 (200-C1) of source donor node 200-1. If donor CU #2 (200-C2) does not explicitly notify beam information, it sends a handover request permission message including a handover command that does not include beam information to donor CU #1 (200-C1). Donor CU #1 (200-C1) receives the handover request permission message.
[0170] In step S42, the donor CU#1 (200-C1) transmits an F1 message including a handover command to the source cell, which receives the F1 message.
[0171] In step S43, the source cell transmits a handover command to the UE 100. The UE 100 receives the handover command.
[0172] In step S44, if beam information is explicitly included in the handover command, UE 100 accesses the target cell using the beam indicated by the beam information. UE 100 can use the beam to transmit an RRC reconfiguration complete message (Msg3) to the target cell. On the other hand, if beam information is not explicitly included in the handover command, UE 100 accesses the target cell using the beam used to access the source cell. UE 100 can use the beam used in the source cell to transmit an RRC reconfiguration complete message (Msg3) to the target cell.
[0173] (Another operation example according to the fourth embodiment) In the fourth embodiment, an operation example has also been described based on the scenario shown in Fig. 9, but is not limited to this. For example, the fourth embodiment can also be applied to handover between the UE 100 and the gNB 200, as in the first embodiment.
[0174] In this case, in Figure 14, this can be implemented by replacing the "IAB-DU #1 (source cell)" of the mobile IAB node 300M with "DU (source cell provided by) of the source gNB" and the "donor CU #1", which is donor CU #1 (200-C1) of the source donor node 200-1, with "CU of the source gNB", and by replacing the "IAB-DU #2 (target cell)" of the mobile IAB node 300M with "DU (target cell provided by) of the target gNB" and the "donor CU #2", which is donor CU #2 (200-C2) of the target donor node 200-2, with "CU of the target gNB".
[0175] Fifth Embodiment Next, a fifth embodiment will be described, focusing on the differences from the first embodiment.
[0176] The fifth embodiment is an example in which a TA value is included in the handover command. Specifically, first, a target donor node (e.g., CU #2 (200-2) of the target donor node 200-2) transmits either a first handover command that explicitly includes a timing advance value or a second handover command that does not explicitly include a timing advance value to a user equipment (e.g., UE 100) via a source cell. Second, when the user equipment receives the first handover command, it transmits an RRC reconfiguration complete message to the target cell using the timing advance value, and when it receives the second handover command, it transmits an RRC reconfiguration complete message (Msg3) to the target cell using the timing advance value used when accessing the source cell.
[0177] As described above, in the fifth embodiment, when the TA value is explicitly indicated, the UE 100 can transmit the RRC reconfiguration complete message (Msg 3) to the target cell by using the TA value, and even when the TA value is not explicitly indicated, the UE 100 can transmit the RRC reconfiguration complete message (Msg 3) to the target cell by using the TA value used in the source cell. Therefore, also in the fifth embodiment, the UE 100 can appropriately transmit the RRC reconfiguration complete message (Msg 3) to the target cell in the RACH-less handover.
[0178] (Example of Operation According to Fifth Embodiment) Next, an example of operation according to the fifth embodiment will be described.
[0179] FIG. 15 is a diagram illustrating an example of operation according to the fourth embodiment.
[0180] Steps S10 to S14 may be the same operations as in the first embodiment. However, in step S12, the source cell may include the TA value used in communication with the UE 100 in an F1 message together with a measurement report and transmit it to the donor CU #1 (200-C1) of the source donor node 200-1. Then, in step S14, the donor CU #1 (200-C1) may transmit a handover request message including the TA value and the measurement report to the donor CU #2 (200-C2) of the target donor node 200-2. Alternatively, if the donor CU #1 (200-C1) manages the TA value of the source cell, the donor CU #1 (200-C1) may transmit a handover request message including the TA value and the measurement report without the source cell transmitting the TA value (step S14).
[0181] In step S50, the donor CU#2 (200-C2) of the target donor node 200-2 determines whether or not to explicitly notify the TA value.
[0182] First, the donor CU #2 (200-C2) may determine not to explicitly notify when the same physical DU is used in the source cell and the target cell and / or when the same physical antenna is used in the source cell and the target cell. This is because, when the same physical ID or the same physical antenna is used, the UE 100 under the control of the mobile IAB node 300M can consider the distance between the source cell and the UE 100 and the distance between the target cell and the UE 100 to be the same.
[0183] Second, donor CU#2 (200-C2) may decide not to explicitly notify if the same TA value is used in the source cell and the target cell.
[0184] In other cases than those mentioned above, donor CU#2 (200-C2) may explicitly include the TA value in the handover and transmit it.
[0185] The explicit TA value may be any of the following:
[0186] First, the explicit TA value may be 0. The TA value may be expressed as a number other than 0.
[0187] Secondly, the explicit TA value may be information specifying which TA value is currently being used (or the TA value that the source cell uses for the UE 100). The information may be represented by a TA group (TAG: Timing Advance Group). The TA group may be represented by a pTAG (primary TAG). The TA group may be represented by an sTAG (secondary TAG). The TA group may be represented by multiple TAG IDs. Alternatively, the information may be represented by information indicating a cell group. The cell group may be represented by an MCG (Master Cell Group). The cell group may be represented by an SCG (Secondary Cell Group). The cell group may be represented by a CG ID (Cell Group ID). Alternatively, the information may be represented by information indicating a cell. The cell may be represented by a PCell (Primary Cell), an SCell (Secondary Cell), a PSCell (Primary SCell), a cell ID, or a cell ID, or the information may be represented by a combination of two or more of these.
[0188] In step S51, if donor CU #2 (200-C2) explicitly notifies the TA value, it includes the TA value in the handover command and transmits a handover request permission message including the handover command to donor CU #1 (200-C1) of source donor node 200-1. If donor CU #2 (200-C2) does not explicitly notify the TA value, it transmits a handover request permission message including a handover command that does not include a TA value to donor CU #1 (200-C1). Donor CU #1 (200-C1) receives the handover request permission message.
[0189] In step S52, the donor CU#1 (200-C1) transmits an F1 message including a handover command to the source cell, which receives the F1 message.
[0190] In step S53, the source cell transmits a handover command to the UE 100. The UE 100 receives the handover command.
[0191] In step S54, if a TA value is explicitly included in the handover command, UE 100 uses the TA value to access the target cell. UE 100 can use the TA value to transmit an RRC reconfiguration complete message (Msg3) to the target cell. On the other hand, if a TA value is not explicitly included in the handover command, UE 100 uses the TA value used when accessing the source cell to access the target cell. UE 100 can use the TA value used in the source cell to transmit an RRC reconfiguration complete message (Msg3) to the target cell.
[0192] (Other operation examples of the fifth embodiment) In the fifth embodiment, an operation example has also been described based on the scenario shown in Fig. 9, but is not limited to this. For example, the fifth embodiment can also be applied to handover between the UE 100 and the gNB 200, as in the first embodiment.
[0193] In this case, in Figure 15, this can be implemented by replacing the "IAB-DU #1 (source cell)" of the mobile IAB node 300M with "DU (source cell provided by) of the source gNB" and the "donor CU #1", which is donor CU #1 (200-C1) of the source donor node 200-1, with "CU of the source gNB", and by replacing the "IAB-DU #2 (target cell)" of the mobile IAB node 300M with "DU (target cell provided by) of the target gNB" and the "donor CU #2", which is donor CU #2 (200-C2) of the target donor node 200-2, with "CU of the target gNB".
[0194] [Other Embodiments] In the first to fifth embodiments, cases where a general handover is applied have been described, but the present invention is not limited to this. The first to fifth embodiments can also be applied to a conditional handover (CHO). When a trigger condition is satisfied, a UE under the control of the mobile IAB node 300M autonomously performs a handover to a target cell corresponding to the trigger condition without transmitting a measurement report. In this case, the UE 100 can also perform the RACH-less handover described in the first to fifth embodiments to the target cell, thereby achieving the same implementation as the first to fifth embodiments.
[0195] The above-described operational flows are not limited to being implemented independently, but can also be implemented by combining two or more operational flows. For example, some steps of one operational flow may be added to another operational flow, or some steps of one operational flow may be replaced with some steps of another operational flow. In each flow, it is not necessary to execute all steps, and only some steps may be executed.
[0196] In the above-described embodiments and examples, an example in which the base station is an NR base station (gNB) has been described, but the base station may be an LTE base station (eNB) or a 6G base station. The base station may also be a relay node such as an IAB (Integrated Access and Backhaul) node. The base station may also be a DU of the IAB node. The UE 100 may also be an MT (Mobile Termination) of the IAB node.
[0197] That is, the UE 100 may be a terminal function unit (a type of communication module) for a base station to control a repeater that relays signals. Such a terminal function unit is referred to as an MT. Examples of the MT include, in addition to the IAB-MT, an NCR (Network Controlled Repeater)-MT and a RIS (Reconfigurable Intelligent Surface)-MT.
[0198] The term "network node" primarily refers to a base station, but may also refer to a core network device or a part of a base station (CU, DU, or RU). A network node may also be configured by a combination of at least a part of a core network device and at least a part of a base station.
[0199] Also, a program that causes a computer to execute each process performed by the UE 100 or the gNB 200 may be provided. The program may be recorded on a computer-readable medium. Using a computer-readable medium, it is possible to install the program on a computer. Here, the computer-readable medium on which the program is recorded may be a non-transitory recording medium. The non-transitory recording medium is not particularly limited, but may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.
[0200] Furthermore, circuits that perform each process performed by UE100 or gNB200 may be integrated, and at least a portion of UE100 or gNB200 may be configured as a semiconductor integrated circuit (chip set, SoC: System on a chip).
[0201] The functions performed by the UE 100 or the gNB 200 (network node) may be implemented in circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), CPUs (Central Processing Units), conventional circuits, and / or combinations thereof, programmed to perform the described functions. A processor includes transistors and other circuits and is considered to be circuitry or processing circuitry. A processor may also be a programmed processor that executes a program stored in memory. In this specification, circuitry, unit, or means refers to hardware that is programmed to perform the described functions or hardware that executes them. The hardware may be any hardware disclosed herein or any hardware known to be programmed or capable of performing the described functions. If the hardware is a processor, the circuitry, means, or unit is a combination of hardware and software used to configure the hardware and / or processor.
[0202] As used in this disclosure, the terms "based on" and "depending on / in response to" do not mean "based only on" or "depending only on," unless expressly stated otherwise. The term "based on" means both "based only on" and "based at least in part on." Similarly, the term "depending on" means both "depending only on" and "depending at least in part on." The terms "include," "comprise," and variations thereof do not mean including only the listed items, but may mean including only the listed items or may include additional items in addition to the listed items. Additionally, the term "or," as used in this disclosure, is not intended to mean an exclusive or. Furthermore, any reference to elements using designations such as "first," "second," etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used herein as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way. In this disclosure, where articles are added by translation, such as a, an, and the in English, these articles shall include the plural unless the context clearly indicates otherwise.
[0203] Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design changes can be made within the scope of the gist. Furthermore, the embodiments, operation examples, and processes can be appropriately combined within the scope of not being inconsistent.
[0204] This application claims priority to U.S. Provisional Application No. 63 / 465,322 (filed May 10, 2023), the entire contents of which are incorporated herein by reference.
[0205] (Supplementary Note 1) (Supplementary Note 1) A communication control method used in a cellular communication system (e.g., cellular communication system 1), comprising the steps of: a target donor node (e.g., donor CU#2 (200-C2)) transmitting a handover command including index information related to an index of a synchronization signal block (SSB) to a user equipment (e.g., UE100) via a source cell (e.g., IAB-DU#1); the user equipment receiving the handover command; and the user equipment transmitting an RRC reconfiguration complete (RRCReconfigurationComplete) message to a target cell by using a resource linked to the index of the synchronization signal block.
[0206] (Supplementary Note 2) The index information represents either information indicating a first index of the synchronization signal block that the user equipment applies to the target cell, or information indicating that the user equipment applies a second index of the synchronization signal block that the user equipment applied to the source cell to the target cell. The communication control method according to Supplementary Note 1.
[0207] (Supplementary Note 3) The communication control method according to Supplementary Note 1 or Supplementary Note 2, wherein the step of transmitting the RRC reconfiguration complete message includes a step in which, when the handover command includes information representing the first index, the user equipment transmits the RRC reconfiguration complete message using resources associated with the first index, and, when the handover command includes information representing that the index is identical to the second index, the user equipment transmits the RRC reconfiguration complete message using resources used in communication with the source cell.
[0208] (Supplementary Note 4) The communication control method according to any one of Supplementary Notes 1 to 3, further comprising: a step in which the user equipment transmits to the source cell a measurement report including a radio quality measurement value for each index of the synchronization signal block (SSB); a step in which the source cell transmits an F1 message including the measurement report to a source donor node in response to receiving the measurement report; and a step in which the source donor node determines a handover of the user equipment based on the measurement report and transmits a handover request message including the measurement report to the target donor node, wherein the step of transmitting to the user equipment includes a step in which the target donor node determines the index of the synchronization signal block based on the measurement report.
[0209] (Supplementary Note 5) The communication control method according to any one of Supplementary Note 1 to Supplementary Note 4, wherein the resource is either a first resource set by an RRC message or a second resource set by downlink control information (DCI).
[0210] (Supplementary Note 6) The communication control method according to any one of Supplementary Notes 1 to 5, wherein the handover command includes configuration index information specifying the first resource, and the step of transmitting to the target cell includes a step of the user equipment transmitting the RRC reconfiguration complete message by using the first resource specified by the configuration index information.
[0211] (Supplementary Note 7) The communication control method according to any one of Supplementary Notes 1 to 6, wherein the handover command includes information linking the index with the first resource.
[0212] (Supplementary Note 8) The communication control method according to any one of Supplementary Notes 1 to 7, wherein the handover command includes information linking the index with the second resource.
[0213] (Supplementary Note 9) The communication control method according to any one of Supplementary Notes 1 to 8, wherein the step of transmitting the handover request message to the target donor node includes a step in which the source donor node decides to perform a RACH-less handover if the index included in the measurement report is identical to an index of the synchronization signal block that the source donor node itself applies to the user equipment.
[0214] (Supplementary Note 10) The communication control method according to any one of Supplementary Notes 1 to 9, wherein the handover request message includes either the index of the synchronization signal applied to the user equipment by the source cell or information indicating that the index will be continuously used in the target cell.
[0215] (Supplementary Note 11) The communication control method according to any one of Supplementary Notes 1 to 10, wherein the handover command includes either the index of the synchronization signal that the source cell applies to the user equipment, or information indicating that the index will continue to be used in the target donor node.
[0216] (Supplementary Note 12) A communication control method used in a cellular communication system, comprising: a step in which a source network node (e.g., source gNB200-1) transmits a handover command including index information regarding an index of a synchronization signal block (SSB) to a user equipment; a step in which the user equipment receives the handover command; and a step in which the user equipment transmits an RRC reconfiguration complete (RRCReconfigurationComplete) message to a target network node (e.g., target gNB200-2) using resources linked to the index of the synchronization signal block.
[0217] (Supplementary Note 13) A communication control method used in a cellular communication system, comprising: a step in which a target donor node transmits a handover command that does not explicitly include beam information to a user equipment via a source cell; a step in which the user equipment receives the handover command; and a step in which the user equipment transmits an RRC reconfiguration complete message to a target cell using the beam that was used when accessing the source cell.
[0218] (Supplementary Note 14) The communication control method according to any one of Supplementary Notes 1 to 13, wherein the step of transmitting the handover command to the user equipment includes a step of the target donor node transmitting the handover command to the user equipment when the same resources are used in the target cell and the source cell, and when the same beam is used in the target cell and the source cell.
[0219] (Supplementary Note 15) A communication control method used in a cellular communication system, comprising: a step in which a target donor node transmits, to a user equipment via a source cell, either a first handover command that explicitly includes a timing advance value or a second handover command that does not explicitly include the timing advance value; and a step in which, when the user equipment receives the first handover command, the user equipment transmits an RRC reconfiguration complete message to a target cell using the timing advance value, and when the user equipment receives the second handover command, the user equipment transmits the RRC reconfiguration complete message to the target cell using the timing advance value used when accessing the source cell.
[0220] (Supplementary Note 16) The communication control method according to any one of Supplementary Notes 1 to 15, wherein the step of transmitting to the user equipment includes a step of the target donor node transmitting the second handover command to the user equipment in any of the following cases: the target cell and the source cell are in the same physical DU, and / or the target cell and the source cell use the same physical antenna, and the target cell and the source cell have the same TA value.
[0221] (Second Supplement) 1. Introduction The WID on Mobile IAB states the following as the objectives of enhancing mobility for full transition:
[0222] The detailed objectives of WI are as follows: ・Define migration / topology adaptation procedures to enable IAB node mobility, including inter-donor migration (full migration) of entire mobile IAB nodes [RAN3, RAN2]. ・Mobile IAB nodes can connect to stationary (intermediate) IAB nodes. Optimizations specific to the scenario where a mobile IAB node connects to a stationary (intermediate) IAB node or directly to an IAB donor DU are not prioritized. ・Mobility of dual-connected IAB nodes is deprioritized. ・Enhancements for IAB nodes to move with their UEs, including aspects related to group mobility. There are no optimizations for targeting surrounding UEs [RAN3, RAN2]. Note: Solutions should avoid touching on topics already discussed in Rel-17 and excluded from Rel-17, except for enhancements specific to IAB node mobility. - Mitigation of interference due to IAB node mobility, including avoidance of potential collisions of reference and control signals (PCI, RACH, etc.) [RAN3, RAN2]. The following principles should be respected: - Mobile IAB nodes should be able to serve legacy UEs. - Solutions providing optimization of mobile IAB may involve enhancements to Rel-18 UE functionality, but such enhancements shall be backward compatible.
[0223] This appendix discusses the details of the mobility enhancements for the mobile IAB.
[0224] 2. Discussion RACH-less handover of Rel-18 UE RAN2#119e reached the following agreement:
[0225] R2 assumes that for onboard RRC connected UEs handed over with mobile IAB nodes, a RACH-less procedure may be considered (also dependent on UL synchronization assumptions).
[0226] Furthermore, RAN2#121bis-e further discussed RACH-less handover and reached the following agreement on various further considerations.
[0227] The RACH-less mIAB scenario only covers the same TA case if finally agreed upon.
[0228] Further study is required on the feasibility of beam handling during RACH-less HO in mIAB WI (this point needs to be addressed in order to support RACH-less in mIAB).
[0229] RAN2 further discusses the following options to support beam operation of the first UL transmission / DL reception towards the target logical DU in RACH-less HO during DU migration.
[0230] Option 1: (Explicit approach) Explicit beam information is included in the HO command. See further discussion for details.
[0231] Option 2: (Implicit approach) The UE reuses the same beam status as the source cell (beam information is not explicitly included in the HO command).
[0232] RACH-less HO using the same TA with security key change is applicable to UEs served during mIAB DU migration. The UL grant and HO completion procedures in mIAB RACH-less HO require further study.
[0233] In LTE, RACH-less handover is configured in MobilityControlInfo with information on applicable Timing Advance (TA) and uplink configuration including uplink grant as follows:
[0234] 2.1.1 TA Configuration Aspects Regarding the TA value, in LTE, it was configured as either "0" or the latest TA value (i.e., targetTA) as described above, but for mobile IAB-full transition, RAN2 agreed that "only the same TA case will be covered if the RACH-less mIAB scenario is finally agreed upon." In this case, there are two options: the UE should implicitly apply the current TA to the target cell, or the UE should follow the explicit configuration provided by the handover command (i.e., TA = 0 or the latest TA value indicated).
[0235] If RACH-less handover is supported only in mobile IAB, the implicit method is efficient in terms of signaling overhead. On the other hand, if RACH-less handover is also supported in other scenarios, i.e., other Rel-18 WIs such as NTN and LTM, as pointed out by several companies in the previous discussion, an explicit method is required.
[0236] For now, only the mobile IAB scenario is considered and RAN2 should agree that the UE will apply the latest TA value to the target cell if no explicit configuration is provided by the Handover Command for RACH-less handover. Note that this also means that the UE will apply the explicit configuration to access the target cell if an explicit configuration is provided in other scenarios.
[0237] Proposal 1: RAN2 should agree that if no explicit TA configuration is provided in the Handover Command for RACH-less handover, the UE will apply the latest TA value to access the target cell. For other scenarios, explicit TA configuration is not precluded.
[0238] 2.1.2. UL Grant Aspects In LTE, pre-allocated uplink grants and dynamic grants are supported for RACH-less HO.
[0239] If RACH-less HO is configured, the UE accesses the target cell via an uplink grant pre-allocated to the UE in an RRC message. If the UE does not receive a pre-allocated uplink grant in an RRC message from the source eNB, the UE monitors the PDCCH of the target cell.
[0240] The pre-allocated uplink grant provides the number of HARQ processes (numberOfConfUL-Processes), scheduling interval (ul-SchedInterval), start subframe (ul-StartSubframe), and radio resources (ul-Grant) in LTE for the periodic uplink grant that the UE uses to send the RRC Connection Reconfiguration Complete (Msg 3). A pre-allocated uplink grant is required due to the absence of Msg 2 (which was included in the RAR MAC PDU) due to the RACH-less handover procedure.
[0241] For similar reasons, NR needs to provide pre-allocated periodic uplink grants. This is feasible because NR already supports Configured Grant (CG), but further consideration is needed as to whether to reuse (e.g., slightly simplify) the existing CG configuration (i.e., ConfiguredGrantConfig).
[0242] For dynamic grants (DG), pre-allocated uplink grants (or CGs) are not required. Instead, the UE monitors the target cell's PDCCH and follows the UL grants in the PDCCH. In general, NR RACH-less handover is possible, but resource efficiency is not considered to be significantly different from pre-allocated uplink grants (or CGs). Since pre-allocated UL grants are considered a baseline solution, it is unclear whether there is a real need to specify another option for the same purpose.
[0243] For now, RAN2 should agree that pre-allocated periodic uplink grants will be provided by Handover Command. The details of the configuration of pre-allocated UL grants and whether DG should be supported or not require further study.
[0244] Proposal 2: RAN2 should agree to provide pre-allocated periodic uplink grants in the handover command for RACH-less handover.
[0245] 2.1.3 Beam Information Aspects The concept of beam sweeping was introduced in NR, so the LTE RACH-less handover function did not need to consider this point. In the previous meeting, RAN2 agreed that the feasibility of beam handling is a prerequisite for supporting RACH-less handover.
[0246] Regarding the message structure, RAN2#121bis-e identified two options:
[0247] RAN2 further discusses the following options to support beam operation for the first UL transmission / DL reception towards the target logical DU in RACH-less HO during DU movement: Option 1: (Explicit approach) Include explicit beam information in the HO command. Further study is required for details. Option 2: (Implicit approach) The UE reuses the same beam status as the source cell (beam information is not explicitly included in the HO command).
[0248] As clarified in the email discussion, Option 1 is a more general approach and may be applicable not only to mobile IAB but also to various other scenarios. On the other hand, Option 2 is an optimization approach specific to mobile IAB scenarios and is only effective when the source and target cells operate on the same frequency, with the same resources and the same configuration. However, Option 2 is more efficient in terms of signaling overhead.
[0249] Considering that option 2 does not work in other mobile IAB scenarios (e.g., source and target cells operate on different frequencies), it is clear that option 1 should be the baseline. Furthermore, option 1 could potentially be reused for other scenarios such as NTN and LTM.
[0250] Proposal 3: RAN2 should agree that explicit beam information can be set in the handover command for RACH-less handover, i.e., the explicit approach of option 1.
[0251] On the other hand, from the perspective of option 2, it is pointed out that RACH-less handover is sufficient to work only in limited scenarios, and furthermore, it is more beneficial for mobile IABs, which need to perform group handovers of many UEs during a complete transition, as it allows optimizing the signaling overhead.
[0252] In this sense, as a harmonized approach, if no explicit beam information is provided by the handover command, it is considered that "the UE reuses the same beam status as the source cell".
[0253] Proposal 4: In addition to Proposal 3, RAN2 should further agree that if no explicit beam information is provided by the handover command, the UE will reuse the same beam state as the source cell, i.e., if Option 1 is not configured, the implicit approach of Option 2 will apply.
[0254] Regarding the beam information, it is necessary to clarify what should be included. Beam information is considered to mean the SSB index of the best beam from the target cell. In legacy handover, the UE can first select the best beam from the target cell and notify the target cell of the selected beam via PRACH (Msg1), i.e., through the PRACH resource associated with the selected beam. Since the gNB can know the selected beam upon receiving Msg1, it can apply this beam to the Random Access Response transmission (i.e., Msg2). This mechanism allows the UE to receive Msg2.
[0255] In RACH-less handover, the UE does not transmit Msg1, so the target cell cannot know which beam is best from the UE's perspective. In other words, the target cell cannot know which beam should receive Msg3 (RRC reconfiguration complete, initial message from the UE). To solve this problem, the following two approaches can be considered.
[0256] Approach 1: "Explicit beam information" is the SSB index (or TCI state) applied to the pre-allocated uplink grant for RRC reconfiguration completion, or Approach 2: "Explicit beam information" is mapping information of each pre-allocated uplink resource to each SSB.
[0257] The interpretation of the RAN2 agreement is "Option 1: (Explicit approach) Include explicit beam information in the HO command. Further study is required for details." The target gNB needs to specify the SSB index to be included in the handover command, but this is feasible because the measurement results including RSRP / RSRQ / SINR of each SB are already included in the inter-node message (HandoverPreparationInformation) for the handover request.
[0258] In addition to the SSB index, if the SSB index is used for reference signals, the TCI state may be more generic information in RACH-less handover, since it includes the SSB index. Since the TCI state can be configured by the handover command, the UE is only informed which TCI state ID should be used for the first PUSCH transmission (i.e., RRC reconfiguration complete).
[0259] On the other hand, Approach 2 is similar to the existing mapping between PRACH occasions and SSBs, in which the UE selects the best beam from the target cell and completes RRC reconfiguration within the associated UL resources.
[0260] These approaches are feasible from the perspective of RAN2, but approach 1 may be better from a resource efficiency perspective, although this may need to be discussed with RAN1 before a final decision is made.
[0261] Proposal 5: RAN2 should discuss whether the SSB index (or TCI state) associated with the pre-allocated uplink grant, or the mapping of pre-allocated uplink resources to each SB, is provided in the handover command as "explicit beam information". This may need to be discussed with RAN1.
[0262] 2.2. Conditional Handover for Legacy and Rel-18 UEs 2.2.1. Legacy CHO Aspects In RAN2#119bis-e, three options for CHO during full transition were discussed and the following assumptions were reached:
[0263] From the QC tdoc, the following options O1, O2, and O3 are possible: 1) Message deferral by logical source IAB-DU with conditional delivery, e.g., during MT migration; 2) Conditional execution by UE based on broadcast indications, e.g., SIB indication of service time or DC indication of MT migration (including CHO with new triggers); 3) Legacy CHO (with implementation-specific behavior, e.g., using source cell power down or target cell power up to trigger the actual HO). (...) RAN2 may be able to function with O1 and O3 above, but further consideration is required if O2 above (e.g., new trigger) is required.
[0264] In RAN2#120, this issue is further discussed and summarized as follows:
[0265] The hurdles to strengthening connected mobility appear to be very high. Options 1 and 3 (no changes from before Rel17) are supported by many companies.
[0266] Option 1 (i.e., deferred RRC message delivery 0) and option 3 (i.e., existing CHO trigger 0 where source cell powers down and target cell powers up) are existing mechanisms (subject to implementation) and can therefore support legacy UEs without changing the specification, whereas option 2 (i.e., new CHO trigger) is only applicable to Rel-18 UEs.
[0267] As long as the network serves legacy UEs, it will need to implement either option 1 or option 3, which is expected to work for Rel-18 UEs as well, so there is no need to introduce a new CHO trigger (option 2).
[0268] However, option 1 is worth checking, especially as it relates to the F1AP specification, to see if any (small) enhancements are required.
[0269] Observation 1: It may be worthwhile to check in RAN3 whether option 1 (i.e., deferring delivery of RRC messages) works for handover of UEs during hard transition.
[0270] 2.2.2. Applicability of CondEvent T1 RAN2#121bis-e has discussed whether to support CondEvent T1 in mobile IAB scenarios.
[0271] Further consideration: CHO with CondT1 may be supported "for free", i.e., if the impact of TS is a minor modification to the description so that it can also be applied to TN.
[0272] TS38.331 does not restrict the use of CondEvent T1 in terrestrial networks.
[0273] The field description of CondReconfigToAddMod states that in case of CHO, if the network configures condEventD1 or condEventT1 for a candidate cell, the network configures a second trigger event condEventA3, condEventA4, or condEventA5 for the same candidate cell. The network shall not configure both condEventD1 and condEventT1 for the same candidate cell. In a mobile IAB scenario, CondEvent A4 (Neighborhood becomes better than threshold) is at least available, and CondEvent D1 (based on UE location) is not required.
[0274] In other words, CondEvent T1 can be considered free to use as long as the UE implements the functionality.
[0275] Observation 2: According to the current RRC specification, CondEvent T1 can be used for mobile IAB scenarios as long as the UE implements this functionality.
[0276] 2.2.3 Rel-18 Enhancements As discussed in Section 2.1, if RACH-less handover is introduced, the combination of these features will be worth considering as an extension of CHO. CHO is effective in distributing the signaling overhead caused by a large number of handover commands, which is an advantage for the source cell. On the other hand, RACH-less handover reduces the number of PRACHs to the target cell. In other words, these features actually provide independent benefits for different cells (or different steps in the entire handover procedure). Therefore, such enhancements need to be discussed.
[0277] Proposal 6: If RACH-less handover is introduced, RAN2 should discuss whether RACH-less handover can also be configured as a conditional handover, i.e., conditional reconfiguration.
Claims
1. A communication control method for handing over a user equipment from a source cell of a mobile Integrated Access and Backhaul (IAB) node to a target cell of the mobile IAB node, the communication control method comprising: the user equipment receiving a handover command including beam information from a network; and the user equipment transmitting an RRC reconfiguration complete message in the target cell using the beam information.
2. The communication control method according to claim 1, wherein the beam information is TCI status identification information.
3. A communication control method as described in claim 1, wherein the beam information is information indicating an SSB index.
4. The communication control method according to claim 1, wherein the handover command is a handover command used in a RACH (Random Access Channel)-less handover.
5. The communication control method according to claim 1, wherein the beam information is determined based on a measurement report from the user equipment.
6. The communication control method according to claim 1, wherein the RRC reconfiguration completion message is transmitted using either a resource set by an RRC message or a resource set by DCI (Downlink Control Information).
Citation Information
Patent Citations
Handling communication
WO2021256982A1
Communication control method
WO2023282251A1
