Communication control method and user device
By assigning unique execution times or resources for PRACH transmissions, the method addresses uplink signaling overload in IAB systems, ensuring efficient and distributed conditional handover execution among UEs.
Patent Information
- Application Number
- JP2024554555
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2022-11-02
- Filing Date
- 2023-11-01
- Publication Date
- 2026-11-19
- Estimated Expiration
- 2043-11-01
AI Technical Summary
In cellular communication systems with integrated access and backhaul (IAB) nodes, particularly with mobile IAB nodes, the simultaneous execution of conditional handovers by multiple user equipment (UEs) leads to uplink signaling overload due to synchronized PRACH transmissions, which can overwhelm the network.
Implementing a communication control method where each UE is assigned a unique predetermined time or resource for PRACH transmission during conditional handovers, ensuring staggered execution times or resource allocation to distribute the signaling load.
The method effectively distributes the uplink signaling load, preventing collisions and reducing the risk of network overload during conditional handovers in IAB systems.
Smart Images

Figure 0007954215000001 
Figure 0007954215000002 
Figure 0007954215000003
Abstract
Description
TECHNICAL FIELD
[0001] The present disclosure relates to a communication control method for use in a cellular communication system. BACKGROUND ART
[0002] In 3GPP (Third Generation Partnership Project), which is a standardization project for cellular communication systems, the introduction of a new relay node called an IAB (Integrated Access and Backhaul) node is under consideration (see, for example, Non-Patent Document 1). One or more relay nodes intervene in communication between a base station and a user apparatus to perform relay for this communication. PRIOR ART DOCUMENTS NON-PATENT DOCUMENTS
[0003] NON-PATENT DOCUMENT 1 3GPP TS 38.300 V17.2.0 (2022-09) SUMMARY OF THE INVENTION
[0004] A communication control method according to a first aspect is a communication control method for use in a cellular communication system. The communication control method includes a step of transmitting, by a network node, a conditional reconfiguration to a user apparatus. The communication control method also includes a step of executing, by the user apparatus, a conditional handover after a predetermined time elapses from when a predetermined condition is detected. Here, the detection of the predetermined condition is either satisfaction of a trigger condition included in the conditional reconfiguration, or reception of a conditional handover execution instruction from the network node. Further, the predetermined time is a different time for each of the user apparatuses.
[0005] The second aspect of the communication control method is a communication control method used in a cellular communication system. The communication control method includes the step of a network node setting a PRACH (Physical Random Access Channel) resource on a user device. The communication control method also includes the step of a user device transmitting a PRACH using the PRACH resource set on the user device when performing a conditional handover. Here, the PRACH resource is a different resource for each user device.
[0006] The third aspect of the communication control method is a communication control method used in a cellular communication system. The communication control method includes a step in which a network node transmits a conditional reset to the user device, which includes beam information representing the beam used by the user device. The communication control method also includes a step in which the user device transmits a PRACH using resources associated with the beam when performing a conditional handover. Here, the beam is different for each user device.
[0007] The fourth aspect of the communication control method is a communication control method used in a cellular communication system. The communication control method includes a step in which a user device sends PRACH (Msg1) to the target cell when performing a conditional handover. The communication control method also includes a step in which the target cell sends a random access response (Msg2) to the user device at a different timing for each user device. Furthermore, the communication control method includes a step in which the user device sends an RRC reconfiguration complete message (Msg3) to the target cell at a different timing for each user device. [Brief explanation of the drawing]
[0008] [Figure 1] Figure 1 shows an example configuration of a cellular communication system according to one embodiment. [Figure 2]Figure 2 shows the relationship between IAB nodes, parent nodes, and child nodes. [Figure 3] Figure 3 shows an example configuration of a gNB (base station) according to one embodiment. [Figure 4] Figure 4 shows an example configuration of an IAB node (relay node) according to one embodiment. [Figure 5] Figure 5 shows an example configuration of a UE (User Equipment) according to one embodiment. [Figure 6] Figure 6 shows an example of a protocol stack for IAB-MT RRC and NAS connections. [Figure 7] Figure 7 shows an example of a protocol stack for the F1-U protocol. [Figure 8] Figure 8 shows an example of a protocol stack for the F1-C protocol. [Figure 9] Figures 9(A) and 9(B) are diagrams illustrating an example of a complete movement according to the first embodiment. [Figure 10] Figures 10(A) and 10(B) are diagrams illustrating an example of a complete movement according to the first embodiment. [Figure 11] Figure 11 is a diagram illustrating an example of operation according to the first embodiment. [Figure 12] Figure 12 is a diagram illustrating an example of operation according to the second embodiment. [Figure 13] Figure 13 is a diagram illustrating an example of operation according to the third embodiment. [Figure 14] Figure 14 is a diagram illustrating an example of operation according to the fourth embodiment. [Figure 15] Figure 15 is a diagram illustrating an example of operation according to the fifth embodiment. [Figure 16] Figure 16 shows the scenarios and subcases of cell reselection in UE. [Figure 17] Figure 17 shows the configuration of RACH-less handover in LTE, using applicable timing advance (TA) and uplink grant information within MobilityControlInfo. [Description of Embodiments]
[0009] 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.
[0010] [First Embodiment]
[0011] (Configuration of Cellular Communication System) A configuration example of the cellular communication system according to an embodiment will be described. A cellular communication system 1 according to an embodiment is a 3GPP 5G system. Specifically, the radio access scheme in the cellular communication system 1 is NR (New Radio), which is the 5G radio access scheme. However, LTE (Long Term Evolution) may be at least partially applied to the cellular communication system 1. Further, future cellular communication systems such as 6G may also be applied to the cellular communication system 1.
[0012] Figure 1 is a diagram illustrating a configuration example of the cellular communication system 1 according to an embodiment.
[0013] As shown in Figure 1, the cellular communication system 1 includes a 5G core network (5GC) 10, a user apparatus (UE: User Equipment) 100, base station apparatuses (hereinafter may be referred to as "base stations") 200-1 and 200-2, and IAB nodes 300-1 and 300-2. The base station 200 may sometimes be referred to as a gNB.
[0014] In the following, an example in which the base station 200 is an NR base station will be mainly described, but the base station 200 may be an LTE base station (that is, an eNB).
[0015] In the following, the base stations 200-1 and 200-2 may be referred to as the gNB 200 (or the base station 200), and the IAB nodes 300-1 and 300-2 may be referred to as the IAB node 300, respectively.
[0016] The 5GC 10 includes an AMF (Access and Mobility Management Function) 11 and a UPF (User Plane Function) 12. The AMF 11 is a device that performs various mobility controls and the like for the UE 100. The AMF 11 manages information on the area where the UE 100 is located by communicating with the UE 100 using NAS (Non-Access Stratum) signaling. The UPF 12 is a device that performs transfer control of user data and the like.
[0017] Each gNB 200 is a fixed wireless communication node, and manages one or a plurality of cells. A cell is used as a term indicating the minimum unit of a wireless communication area. A cell may be used as a term indicating a function or resource for performing wireless communication with the UE 100. One cell belongs to one carrier frequency. Hereinafter, the cell and the base station may be used without distinction.
[0018] Each gNB 200 is interconnected with the 5GC 10 via an interface called an NG interface. In FIG. 1, two gNBs 200-1 and gNB 200-2 connected to the 5GC 10 are illustrated.
[0019] Each gNB 200 may be divided into a Central Unit (CU) and a Distributed Unit (DU). The CU and the DU are interconnected via an interface called an F1 interface. The F1 protocol is a communication protocol between the CU and the DU, and includes an F1-C protocol which is a control plane protocol and an F1-U protocol which is a user plane protocol.
[0020] Cellular communication system 1 supports IAB, which enables wireless relay of NR access using NR for backhaul. Donor gNB200-1 (or donor node; hereinafter sometimes referred to as "donor node") is the network-side NR backhaul termination node and is a donor base station with additional functions to support IAB. Backhaul can be multi-hop, via multiple hops (i.e., multiple IAB nodes 300).
[0021] Figure 1 shows an example where IAB node 300-1 is wirelessly connected to donor node 200-1, and IAB node 300-2 is wirelessly connected to IAB node 300-1, with the F1 protocol being transmitted over two backhaul hops.
[0022] The UE100 is a mobile wireless communication device that communicates wirelessly with a cell. The UE100 can be any device that communicates wirelessly with the gNB200 or IAB node 300. For example, the UE100 may be a mobile phone terminal and / or a tablet terminal, a notebook PC, a sensor or a device installed on a sensor, a vehicle or a device installed on a vehicle, an aircraft or a device installed on an aircraft. The UE100 connects wirelessly to the IAB node 300 or gNB200 via an access link. Figure 1 shows an example of the UE100 connecting wirelessly to IAB node 300-2. The UE100 communicates indirectly with donor node 200-1 via IAB node 300-2 and IAB node 300-1.
[0023] Figure 2 shows an example of the relationship between IAB node 300, parent nodes, and child nodes.
[0024] As shown in Figure 2, each IAB node 300 has an IAB-DU, which corresponds to the base station function unit, and an IAB-MT (Mobile Termination), which corresponds to the user equipment function unit.
[0025] On the IAB-MT's NR Uu radio interface, adjacent nodes (i.e., higher-level nodes) are called parent nodes. A parent node is the DU of the parent IAB node or donor node 200. The radio link between the IAB-MT and the parent node is called a backhaul link (BH link). Figure 2 shows an example where the parent nodes of IAB node 300 are IAB nodes 300-P1 and 300-P2. The direction toward the parent node is called upstream. From the perspective of UE100, the higher-level node of UE100 may be a parent node.
[0026] Adjacent nodes (i.e., lower-level nodes) on the NR access interface of an IAB-DU are called child nodes. The IAB-DU manages cells, similar to the gNB200. The IAB-DU terminates the NR Uu radio interface to the UE100 and lower-level IAB nodes. The IAB-DU supports the F1 protocol to the CU of donor node 200-1. Figure 2 shows an example where the child nodes of IAB node 300 are IAB nodes 300-C1 to 300-C3, but the child nodes of IAB node 300 may also include the UE100. The direction toward child nodes is called downstream.
[0027] 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 Figure 2, adjacent nodes on the IAB-DU interface become child nodes, and adjacent nodes on the IAB-MT interface become parent nodes. The donor node 200 centrally manages, for example, the resources, topology, and route management of the IAB topology. The donor node 200 is a gNB that provides network access to the UE100 via the backhaul link and access link network.
[0028] (Base station configuration) Next, the configuration of the gNB200, which is a base station according to the embodiment, will be described. Figure 3 is a diagram showing an example of the configuration of the gNB200. As shown in Figure 3, the gNB200 has a wireless communication unit 210, a network communication unit 220, and a control unit 230.
[0029] The wireless communication unit 210 performs wireless communication with the UE 100 and with the IAB node 300. The wireless communication unit 210 includes a receiving unit 211 and a transmitting unit 212. The receiving unit 211 performs various types of reception under the control of the control unit 230. The receiving unit 211 includes an antenna and converts the wireless signal received by the antenna into a baseband signal (received signal) (downconvert) and outputs it to the control unit 230. The transmitting unit 212 performs various types of transmission under the control of the control unit 230. The transmitting unit 212 includes an antenna and converts the baseband signal (transmitted signal) output by the control unit 230 into a wireless signal (upconvert) and transmits it from the antenna.
[0030] The network communication unit 220 performs wired (or wireless) communication with 5GC10 and with other adjacent gNB200s. The network communication unit 220 has a receiving unit 221 and a transmitting unit 222. The receiving unit 221 performs various types of reception under the control of the control unit 230. The receiving unit 221 receives signals from the outside and outputs the received signals to the control unit 230. The transmitting unit 222 performs various types of transmission under the control of the control unit 230. The transmitting unit 222 transmits the transmission signals output by the control unit 230 to the outside.
[0031] The control unit 230 performs various controls in the gNB200. 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 for processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation, demodulation, encoding, decoding, etc., of the baseband signal. The CPU executes programs stored in the memory and performs various processing. The processor performs processing for each layer described later. In each of the embodiments shown below, the control unit 230 may perform each processing or operation in the gNB200.
[0032] (Configuration of relay nodes) Next, the configuration of the IAB node 300, which is a relay node (or relay node device; hereinafter sometimes referred to as "relay node") according to the embodiment, will be described. Figure 4 is a diagram showing an example of the configuration of the IAB node 300. As shown in Figure 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.
[0033] The wireless communication unit 310 performs wireless communication with the gNB200 (BH link) and wireless communication with the UE100 (access link). The wireless communication unit 310 for BH link communication and the wireless communication unit 310 for access link communication may be provided separately.
[0034] The wireless communication unit 310 includes 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 the wireless signal received by the antenna into a baseband signal (received signal) (downconvert) and outputs it 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 the baseband signal (transmitted signal) output by the control unit 320 into a wireless signal (upconvert) and transmits it from the antenna.
[0035] 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 for processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation, demodulation, encoding, and decoding of baseband signals. The CPU executes programs stored in the memory and performs various processes. The processor performs processing for each layer described later. In each of the embodiments shown below, the control unit 320 may perform each process or operation in the IAB node 300.
[0036] (User device configuration) Next, the configuration of the user device UE100 according to the embodiment will be described. Figure 5 is a diagram showing an example of the configuration of UE100. As shown in Figure 5, UE100 has a wireless communication unit 110 and a control unit 120.
[0037] The wireless communication unit 110 performs wireless communication on the access link, i.e., wireless communication with the gNB200 and wireless communication with the IAB node 300. The wireless communication unit 110 may also perform wireless communication on the side link, i.e., wireless communication with other UE100s. The wireless communication unit 110 has a receiving unit 111 and a transmitting unit 112. The receiving unit 111 performs various types of reception under the control of the control unit 120. The receiving unit 111 includes an antenna and converts the wireless signal received by the antenna into a baseband signal (received signal) (downconvert) and outputs it to the control unit 120. The transmitting unit 112 performs various types of transmission under the control of the control unit 120. The transmitting unit 112 includes an antenna and converts the baseband signal (transmitted signal) output by the control unit 120 into a wireless signal (upconvert) and transmits it from the antenna.
[0038] 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 for processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation, demodulation, encoding, and decoding of baseband signals. The CPU executes programs stored in the memory and performs various processes. The processor performs processing for each layer described later. The control unit 120 may perform each process in the UE 100 in each of the embodiments shown below.
[0039] (Protocol stack configuration) Next, the configuration of the protocol stack according to the embodiment will be described. Figure 6 shows an example of a protocol stack for IAB-MT RRC connection and NAS connection.
[0040] As shown in Figure 6, the IAB-MT of IAB node 300-2 has a physical (PHY) layer, a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, a PDCP (Packet Data Convergence Protocol) layer, an RRC (Radio Resource Control) layer, and a NAS (Non-Access Stratum) layer.
[0041] The PHY layer performs encoding and decoding, modulation and demodulation, antenna mapping and demapping, and resource mapping and demapping. Data and control information are transmitted between the PHY layer of IAB-MT at IAB node 300-2 and the PHY layer of IAB-DU at IAB node 300-1 via a physical channel.
[0042] The MAC layer performs data priority control, retransmission processing using Hybrid Automatic Repeat request (HARQ), and random access procedures. Data and control information are transmitted between the MAC layer of IAB-MT on IAB node 300-2 and the MAC layer of IAB-DU on IAB node 300-1 via a transport channel. The MAC layer of IAB-DU includes a scheduler. The scheduler determines the transport format (transport block size, modulation and coding scheme (MCS)) and allocated resource blocks for the up and down links.
[0043] The RLC layer uses the functions of the MAC layer and PHY layer to transmit data to the receiving RLC layer. Data and control information are transmitted between the RLC layer of IAB-MT on IAB node 300-2 and the RLC layer of IAB-DU on IAB node 300-1 via a logical channel.
[0044] The PDCP layer performs header compression / decompression, and encryption / decryption. Data and control information are transmitted between the PDCP layer of IAB-MT on IAB node 300-2 and the PDCP layer on donor node 200 via a wireless bearer.
[0045] The RRC layer controls the logical channel, transport channel, and physical channel in response to the establishment, re-establishment, and release of the radio bearer. RRC signaling for various settings is transmitted between the RRC layer of the IAB-MT on IAB node 300-2 and the RRC layer of donor node 200. If there is an RRC connection with donor node 200, the IAB-MT is in the RRC connected state. If there is no RRC connection with donor node 200, the IAB-MT is in the RRC idle state.
[0046] The NAS layer, located above the RRC layer, handles session management and mobility management, among other things. NAS signaling is transmitted between the NAS layer of IAB-MT on IAB node 300-2 and AMF11.
[0047] Figure 7 shows the protocol stack for the F1-U protocol. Figure 8 shows the protocol stack for the F1-C protocol. Here, an example is shown where donor node 200 is divided into CU and DU.
[0048] As shown in Figure 7, each of the IAB-MT on IAB node 300-2, the IAB-DU on IAB node 300-1, the IAB-MT on IAB node 300-1, and the DU on donor node 200 has a BAP (Backhaul Adaptation Protocol) layer as a layer above the RLC layer. The BAP layer is the layer that performs routing and bearer mapping / demapping. In backhaul, routing across multiple hops is possible because the IP layer is transmitted through the BAP layer.
[0049] In each backhaul link, the BAP layer's PDUs (Protocol Data Units) are transmitted via backhaul RLC channels (BH NR RLC channels). By configuring multiple backhaul RLC channels in each BH link, traffic prioritization and QoS (Quality of Service) control are possible. The mapping 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.
[0050] As shown in Figure 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 Figure 7.
[0051] In the following, the processes or operations performed by the IAB-DU and IAB-MT of the IAB may be described simply as "IAB processes or operations." 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 IAB node 300-1 transmitting the message to IAB node 300-2. Similarly, the processes or operations of the DU or CU of donor node 200 may be described simply as "donor node processes or operations."
[0052] Furthermore, the upstream direction and the uplink (UL) direction may not be distinguished. Additionally, the downstream direction and the downlink (DL) direction may not be distinguished.
[0053] (Mobile IAB node) Currently, 3GPP is considering the introduction of mobile IAB nodes. A mobile IAB node is, for example, an IAB node that is in motion. A mobile IAB node may be a mobile IAB node, or an IAB node that has the capability to move, or an IAB node that is currently stationary but is certain to move in the future (or is expected to move in the future).
[0054] A mobile IAB node allows, for example, a UE100 under the mobile IAB node to move along with the mobile IAB node while receiving services from it. For example, a user (or UE100) riding in a vehicle could receive services via a mobile IAB node installed in the vehicle.
[0055] On the other hand, in contrast to mobile IAB nodes, there are also IAB nodes that do not move. Such IAB nodes are sometimes called intermediate IAB nodes. An intermediate IAB node is, for example, an IAB node that does not move. Alternatively, an intermediate IAB node may be a stationary IAB node. Alternatively, an intermediate IAB node may be an IAB node that remains stationary (or does not move) in its installation location. Alternatively, an intermediate IAB node may be an IAB node that remains stationary without moving. An intermediate IAB node may be a fixed IAB node.
[0056] A mobile IAB node can also connect to an intermediate IAB node. Furthermore, a mobile IAB node can connect to donor node 200. A mobile IAB node can also change its connection destination through migration or handover. The source of the connection may be an intermediate IAB node. The source of the connection may also be donor node 200. Furthermore, the destination may be an intermediate IAB node. The destination of the connection may also be donor node 200.
[0057] In the following, the terms "migration" and "handover" of a moving IAB node may not be used interchangeably.
[0058] Furthermore, in the following, a moving IAB node may be referred to as a "mobile IAB node" or a "migrating IAB node." In either case, it may be referred to as a moving IAB node.
[0059] (Full migration of a moving IAB node) A mobile IAB node may move between 200 donor nodes (IAB-donors).
[0060] Figures 9(A) to 10(B) illustrate an example of the procedure when a mobile IAB node 300M moves from a source donor node 200-S to a target donor node 200-T. Note that the mobile IAB node 300M has a UE100 under its control. In the example in Figure 9(A), the UE100 is located within the cell range formed by IAB-DU#1 of the mobile IAB node 300M. The UE100 can move together with the mobile IAB node 300M.
[0061] Figure 9(A) shows an example of the initial condition. IAB-DU#1 of mobile IAB node 300M has established an F1 connection to CU of source-donor node 200-S. In addition, IAB-MT of mobile IAB node 300M has established an RRC connection to CU of source-donor node 200-S.
[0062] Figure 9(B) illustrates an example where the moving IAB node 300M enters a partial migration state with respect to the target donor node 200-T due to its migration to the target donor node 200-T. As shown in Figure 9(B), in a partial migration, the IAB-DU#1 (and UE100) of the moving IAB node 300M is terminated at the CU of the source donor node 200-S, while the IAB-MT of the moving IAB node 300M moves to the CU of the target donor node 200-T. The IAB-MT of the moving IAB node 300M establishes an RRC connection with the CU of the target donor node 200-T. In addition, the IAB-DU of the moving IAB node 300M establishes an F1 connection with the source donor node 200-S. Partial migration refers to a situation where, for example, the connection of UE100 under migrating IAB node 300M remains with source donor node 200-S via IAB-DU#1 of migrating IAB node 300M.
[0063] Figure 10(A) shows an example where the migrating IAB node 300M subsequently reaches Phase 1 of Full migration to the target donor node 200-T. In Phase 1 of Full Migration, UE100 retains a connection with the source donor node 200-S via IAB-DU#1, while a new IAB-DU#2 has established an F1 connection with the CU of the target donor node 200-T. Here, IAB-DU#1 and IAB-DU#2 may be logical IAB-DUs. A single physical IAB-DU may contain two logical IAB-DUs (IAB-DU#1 and IAB-DU#2).
[0064] Figure 10(B) shows an example where the relocating IAB node 300M subsequently reaches Phase 2 of complete relocation to the target donor node 200-T. In Phase 2 of complete relocation, the connection of the relocating IAB node 300M (and UE100) has moved from the CU of the source donor node 200-S to the CU of the target donor node 200-T. Complete relocation refers to a state where, for example, the connection of UE100 has moved to the target donor node 200-T via IAB-DU#2 of the relocating IAB node 300M.
[0065] Furthermore, the movement between CUs using two DUs (IAB-DU#1 and IAB-DU#2) via the mobile IAB node 300M is sometimes referred to as the "dual DU approach." For example, the dual DU approach is performed when UE100 moves from one CU and DU to the other CU and DU.
[0066] (Communication control method according to the first embodiment) As shown in Figures 10(A) and 10(B), when the mobile IAB node 300M is performing a complete move, the UE100 under the mobile IAB node 300M performs a handover from IAB-DU#1 to IAB-DU#2.
[0067] 3GPP is discussing the possibility of performing this handover as a conditional handover (CHO). Specifically, they are discussing two scenarios: one where the mobile IAB node 300M broadcasts an instruction to perform a conditional handover, and another where the conventional conditional handover method is used.
[0068] In the former case, the instruction to execute a conditional handover is broadcast from the mobile IAB node 300M to the subordinate UE100s. Therefore, in the former case, the processing load on downlink signaling can be reduced compared to when the instruction is performed by individual signaling (e.g., RRC message). On the other hand, in the former case, because the instruction is broadcast, the UE100s under mobile IAB node 300M may all execute a conditional handover simultaneously. In such cases, multiple UE100s may simultaneously send PRACH(Msg1). Therefore, in the former case, the uplink signaling may be overloaded.
[0069] On the other hand, in the latter case as well, if the UE100s under the mobile IAB node 300M simultaneously meet the predetermined trigger conditions (event A3, event A4, or event A5), multiple UE100s may send PRACH signals at the same time. Therefore, in the latter case as well, signaling in the uplink direction may be overloaded.
[0070] Therefore, the objective of the first embodiment is to distribute the signaling load in the uplink direction.
[0071] Therefore, in the first embodiment, firstly, the base station (e.g., gNB200) transmits a conditional reset to the user device (e.g., UE100). Secondly, the user device performs a conditional handover after a predetermined time has elapsed since detecting a predetermined condition. Here, detection of the predetermined condition is either fulfilling a trigger condition included in the conditional reset, or receiving an instruction from the base station to perform a conditional handover. The predetermined time is different for each user device.
[0072] Thus, in the first embodiment, the UE100 performs a conditional handover after a predetermined time has elapsed, which differs for each UE100, from the time it detects a predetermined condition. Therefore, in the first embodiment, the execution of the conditional handover, i.e., PRACH transmission, can be started at different timings for each UE100. Thus, in the first embodiment, the signaling load in the uplink direction can be distributed.
[0073] In the following, the mobile IAB node 300M, the parent node of the mobile IAB node 300M, and the donor node 200 (or gNB200) may be referred to as "gNB200". That is, gNB200 may be the mobile IAB node 300M. Alternatively, gNB200 may be the parent node of the mobile IAB node 300M. Alternatively, gNB200 may be the donor node 200.
[0074] (Example of operation according to the first embodiment) Next, an example of operation according to the first embodiment will be described.
[0075] Figure 11 is a diagram illustrating an example of operation according to the first embodiment.
[0076] As shown in Figure 11, in step S10, gNB200 (source cell) sets a conditional handover to UE100. gNB200 then performs a conditional reconfiguration, which includes the conditional handover setting information. tionThe setting may also be performed by sending the following to UE100. The gNB200 may send the conditional reconfiguration to UE100 using the RRCReconfiguration message. The UE100 will receive the conditional handover setting from the gNB200 through the conditional reconfiguration.
[0077] Firstly, a conditional reset includes trigger conditions for UE100 to perform a conditional handover. Multiple such trigger conditions may be included.
[0078] Secondly, conditional resetting may include instruction information that instructs the system to ensure a predetermined time (or waiting time) from the time a predetermined condition is detected until the conditional handover is executed. Alternatively, conditional resetting may include instruction information that instructs the system to execute the conditional handover after the predetermined time has elapsed. The predetermined condition includes satisfying a trigger condition included in conditional resetting. In this case, when the trigger condition is satisfied, the UE100 executes the conditional handover after the predetermined time has elapsed. The predetermined condition also includes receiving an instruction to execute a conditional handover from the gNB200. In this case, when the UE100 receives the instruction, it executes the conditional handover after the predetermined time has elapsed.
[0079] Thirdly, if the conditional reset includes instruction information that instructs the system to allocate a predetermined time, the conditional reset may also include setting information regarding the method for calculating the predetermined time.
[0080] Random numbers may be used as the calculation method. Random numbers can be used to make the predetermined time different for each UE100. The configuration information may include information indicating that a conditional handover is triggered when the generated random number is above a predetermined threshold. The random number may be generated at regular intervals. The regular interval may be included in the configuration information. The configuration information may include an upper limit on the number of random number generation cycles. The upper limit may be an upper limit on the number of consecutive random number generation cycles. The upper limit may be an upper limit on the total number of random number generation cycles. Alternatively, the upper limit may be an upper limit on the number of times the generated random number was below a predetermined threshold (i.e., the number of times transmission was withheld). When the number of random number generation cycles reaches the upper limit (or exceeds the upper limit), UE100 may perform a conditional handover without making a decision on whether to perform a conditional handover based on the random number generation. This is to allow UE100 to perform a conditional handover even if the number of times the random number falls below the predetermined threshold reaches the upper limit.
[0081] Alternatively, the UE-ID may be used as the calculation method. That is, a conditional handover is performed at UE100 at the timing associated with the UE-ID. This allows the conditional handover to be performed after a different waiting time (predetermined time) has elapsed for each UE100. The UE-ID may also be the International Mobile Subscriber Identity (IMSI). The UE-ID may also be the 5G System Temporary Subscriber Identity (5G-S-TMSI). The association between the UE-ID and the subframe may be performed by executing a conditional handover in the subframe where the formula (subframe number = (UE-ID) mod 10) is satisfied. The target to be associated with the UE-ID does not have to be a subframe. For example, the target may be a wireless frame, a combination of a wireless frame and a subframe, or at another timing (for example, a number for each subframe in which a PRACH resource exists).
[0082] Fourth, the conditional reset may include a predetermined time. A different predetermined time is set for each UE100 at the time the conditional reset is configured. In UE100, the conditional handover is executed after the predetermined time has elapsed from the time the predetermined condition is detected.
[0083] In step S11, UE100 may receive a conditional handover execution instruction broadcast from gNB200.
[0084] In step S12, the UE100 detects a predetermined condition. This predetermined condition is either the fulfillment of a trigger condition included in the conditional reset (step S10), or the receipt of an instruction to execute a conditional handover.
[0085] Firstly, UE100 may decide to execute a conditional handover after a predetermined time has elapsed only if it receives an instruction to execute a conditional handover. In other words, in the existing conditional handover settings, UE100 starts executing a conditional handover when the trigger condition is met (i.e., existing operation), and performs a new operation in which it executes a conditional handover after a predetermined time has elapsed only if it receives such an instruction.
[0086] Secondly, UE100 may decide to execute a conditional handover after a predetermined time has elapsed if the trigger conditions for a conditional handover are met and the predetermined time has been set by a conditional reset.
[0087] In step S13, UE100 detects a predetermined condition and, after a predetermined time has elapsed since detecting that condition, performs a conditional handover. That is, UE100 begins accessing the target cell and begins sending PRACH. Since the predetermined time is different for each UE100, UE100 will send PRACH at different times for each UE.
[0088] (Other operational examples of the first embodiment) In the first embodiment, an example was described in which the UE100 starts executing a conditional handover after a predetermined time has elapsed from the detection of a predetermined condition, but the embodiment is not limited to this. For example, the UE100 may start transmitting PRACH after a predetermined time has elapsed from the start of the execution of the conditional handover. That is, the UE100 starts executing a conditional handover when it detects a predetermined condition, and transmits PRACH after a predetermined time has elapsed from the start of the execution. Since PRACH is transmitted at different timings for each UE, signaling in the uplink direction can be distributed, similar to the first embodiment.
[0089] [Second Embodiment] Next, a second embodiment will be described. The second embodiment will be described focusing on the differences from the first embodiment.
[0090] The second embodiment is also an embodiment for preventing PRACH transmission collisions. Specifically, firstly, the base station (e.g., gNB200) sets a PRACH resource on the user device (e.g., UE100). Secondly, when the user device performs a conditional handover, it transmits a PRACH using the PRACH resource set on the user device. Here, the PRACH resource is different for each user device.
[0091] Thus, in the second embodiment, PRACH transmission is possible using different PRACH resources for each UE100. Therefore, in the second embodiment, PRACH transmission collisions can be avoided and signaling in the uplink direction can be distributed.
[0092] (Example of operation according to the second embodiment) Figure 12 is a diagram illustrating an example of operation according to the second embodiment. Before the operation shown in Figure 12 begins, the UE100 receives a conditional handover setting from the gNB200 (step S10 in Figure 11).
[0093] As shown in Figure 12, in step S20, the gNB200 (source cell) sets up a PRACH partition to be used for PRACH transmission when a conditional handover is performed. For example, the gNB200 may announce the PRACH partition using broadcast signaling (e.g., a System Information Block (SIB)). The gNB200 may also send it to the UE100 using individual signaling (e.g., an RRC message). The setting of the PRACH partition may also be performed in the setting of the conditional handover (step S10 in Figure 11).
[0094] The PRACH partition, for example, divides all resources used for PRACH transmission into predetermined ranges. The PRACH partition may be assigned to each group of UE100. The PRACH partition may include settings for PRACH resources available to UE100. The PRACH partition may include a partition ID (partition identification information) assigned to each partition. In this case, the PRACH resources themselves may be broadcast from the target cell of the conditional handover using SIB. Note that the conditional reset (step S10 in Figure 11) may include instruction information indicating whether or not to use the PRACH partition.
[0095] In step S21, the UE100 detects a predetermined condition. The detection of the predetermined condition may be the fulfillment of a trigger condition included in the conditional reset, as in the first embodiment. The detection of the predetermined condition may also be the receipt of an execution instruction for a conditional handover broadcast from the gNB200. The execution instruction may include instruction information indicating whether or not to use the PRACH partition.
[0096] In step S22, UE100 detects a predetermined condition and starts executing a conditional handover. When executing a conditional handover, UE100 sends a PRACH using the PRACH resource configured in UE100.
[0097] Thus, since the resources configured by the PRACH partition are different for each group of UE100 (or for each UE100), it is possible to suppress PRACH transmission collisions and distribute signaling in the uplink direction.
[0098] [Third Embodiment] Next, a third embodiment will be described. The third embodiment will also be described focusing on the differences from the first embodiment.
[0099] The third embodiment is an embodiment in which PRACH transmission is distributed in the spatial direction. Specifically, firstly, a base station (e.g., gNB200) transmits a conditional reset to the user equipment (e.g., UE100) which includes beam information representing the beam used by the user equipment. Secondly, when the user equipment performs a conditional handover, it transmits PRACH using the resources associated with the beam. Here, the beam is different for each user equipment.
[0100] Thus, in the third embodiment, the gNB200 assigns a different beam to each UE100, and the UE100 transmits PRACH using the resources associated with that beam. Therefore, since PRACH is transmitted using different resources for each UE, it becomes possible to distribute signaling in the uplink direction.
[0101] (Example of operation according to the third embodiment) Next, an example of operation according to the third embodiment will be described.
[0102] Figure 13 is a diagram illustrating an example of operation according to the third embodiment.
[0103] As shown in Figure 13, in step S30, the gNB200 (source cell) sets a conditional handover for the UE100. The gNB200 sets this by sending a conditional reset to the UE100, similar to the first embodiment. This conditional reset may include beam information. This beam information represents the beam of the target cell that the UE100 should (or is permitted to) use for PRACH transmission. The gNB200 transmits beams in different directions at different timings by beam sweeping, and the UE100 uses the optimal beam to perform PRACH transmission. This beam information represents, for example, information on the beam that the UE100 should use from among multiple beams. This beam information may represent different beams for each UE100. This beam information may represent different beams for each group of UE100s. This beam information may be represented by a beam index. Alternatively, this beam information may be represented by a Synchronization Signal Block (SSB) index.
[0104] In step S31, the UE100 detects a predetermined condition. The detection of the predetermined condition may be the fulfillment of a trigger condition included in the conditional reset, as in the first embodiment. The detection of the predetermined condition may also be the receipt of an instruction to execute a conditional handover broadcast from the gNB200. The instruction to execute may include beam information.
[0105] In step S32, UE100 detects a predetermined condition and initiates a conditional handover, transmitting a PRACH using the beam represented by the beam information and the resource associated with that beam.
[0106] Furthermore, in UE100, while a conditional handover is being performed after PRACH transmission, gNB200 may refrain from beam sweeping and direct all beams in the same direction. This is to avoid a situation where UE100 is unable to receive the beam set in the beam information while the conditional handover is being performed.
[0107] [Fourth Embodiment] Next, the fourth embodiment will be described. The fourth embodiment will also be described focusing on the differences from the first embodiment.
[0108] In the third embodiment, an example was described in which information about the beam used by UE100 is explicitly stated as beam information. In the fourth embodiment, an example is described in which the beam used for accessing the target cell is identified, rather than explicitly stated by beam information.
[0109] Specifically, firstly, the base station (e.g., mobile IAB node 300M) controls the beam directions of the target cell and source cell so that the beams of the target cell and source cell are in the same direction at the same time. Secondly, the user device (e.g., UE100) transmits PRACH to the target cell using the same beam resource associated with the beam used in the source cell.
[0110] For example, in the complete move shown in Figure 10(A), UE100 performs a handover from IAB-DU#1 to IAB-DU#2 of the moving IAB node 300M. Even though UE100 under the moving IAB node 300M does not actually move to the moving IAB node 300M, this handover may still occur. In such cases, the moving IAB node 300M controls the beams so that the source cell formed by IAB-DU#1 and the target cell formed by IAB-DU#2 are oriented in the same direction at the same time (or so that the beam index and beam direction (weight) are the same). Then, UE100 initiates a conditional handover and sends a PRACH to the target cell using the same beam used by the source cell and the resources associated with that beam.
[0111] (Example of operation according to the fourth embodiment) Next, an example of operation according to the fourth embodiment will be described. In the following description, gNB200 is assumed to be the mobile IAB node 300M, and UE100 is assumed to be a UE under the mobile IAB node 300M.
[0112] Figure 14 is a diagram illustrating an example of operation according to the fourth embodiment.
[0113] As shown in Figure 14, in step S40, the mobile IAB node (mIAB) 300M provides the source cell and the target cell. In UE100, a conditional handover from the source cell to the target cell takes place. Here, the mobile IAB node 300M controls the beams of the source cell and the target cell to coordinate. That is, the mobile IAB node 300M matches the weight (beam direction or directivity direction) for each beam index (or each SSB) between the source cell and the target cell. For example, beam index #1 points in the same direction in both the source cell and the target cell. As a result, for example, beams that point in the same direction (or provide the same coverage) are formed in both the source cell and the target cell at the same timing.
[0114] In step S41, the source cell sends a conditional reset to UE100. The conditional reset may include instruction information that instructs UE100 to access the target cell using the beam index currently in use.
[0115] In step S42, UE100 detects a predetermined condition. The detection of the predetermined condition is, as in the first embodiment, either fulfilling a trigger condition included in the conditional reset, or receiving an instruction to perform a conditional handover from the moving IAB node 300M. The instruction may include instruction information that instructs accessing the target cell using the beam index currently in use.
[0116] In step S43, UE100 detects a predetermined condition and sends PRACH to the target cell. Specifically, UE100 sends PRACH to the target cell using a beam with the same beam index as the beam used in the source cell, and using the resources associated with that beam.
[0117] [Fifth Embodiment] Next, the fifth embodiment will be described. The fifth embodiment will also be described focusing on the differences from the first embodiment.
[0118] The first to fourth embodiments primarily described how to avoid PRACH transmission collisions when performing a conditional handover.
[0119] In other words, the first to fourth embodiments described how to avoid PRACH(Msg1) transmission collisions that occur when conditional handover execution instructions are received simultaneously or when the trigger conditions for conditional handover are met simultaneously by multiple UE100s.
[0120] However, even if a collision in sending PRACH (Msg1) can be avoided, a collision may still occur in sending the RRC Reconfiguration Complete message (Msg3).
[0121] Therefore, in the fifth embodiment, an example will be described in which the gNB200 adjusts the transmission timing of the Random Access Response (Msg2) for each UE100.
[0122] Specifically, firstly, the user device (e.g., UE100) sends PRACH (Msg1) to the target cell when performing a conditional handover. Secondly, the target cell sends a random access response (Msg2) to the user device at a different timing for each user device. Thirdly, the user device sends an RRC reset completion message (Msg3) to the target cell at a different timing for each user device.
[0123] Thus, for example, in UE100, the timing of receiving the random access response (Msg2) differs for each UE100, allowing the RRC reconfiguration completion message (Msg3) to be sent at different times for each UE100. Therefore, collisions in sending the RRC reconfiguration completion message can be suppressed, and signaling in the uplink direction can be distributed.
[0124] (Example of operation according to the fifth embodiment) Next, an example of operation according to the fifth embodiment will be described.
[0125] Figure 15 is a diagram illustrating an example of operation according to the fifth embodiment. The source cell and the target cell may belong to the same gNB200 or to different gNB200s.
[0126] As shown in Figure 15, in step S50, the source cell sends a conditional reset to the UE100. The conditional reset may include the setting value of the extended handover monitoring timer (or extended monitoring timer) instead of the T304 timer. Due to the difference in the transmission timing of the random access response (Msg2) for each UE100, the transmission timing of the RRC reset completion message (Msg3) may be delayed compared to before. This delay may cause the count value of the T304 timer to exceed a predetermined value (i.e., the T304 timer expires), preventing the UE100 from sending the RRC reset completion message (Msg3). Therefore, the extended handover monitoring timer is used to enable the UE100 to send the RRC reset completion message (Msg3) even if the reception of the random access response (Msg) is delayed compared to before. Alternatively, the source cell may send a handover command (for example, an RRCReconfiguration with sync message) to the UE100 instead of sending a conditional reconfiguration.
[0127] In step S51, if a conditional reset has been performed, the UE100 detects a predetermined condition. The predetermined condition is either that the trigger condition included in the conditional reset is met, or that an instruction to perform a conditional handover is received from the gNB200, similar to the first embodiment. The instruction to perform the handover may include the timer value (or expiration value) of the extended handover monitoring timer, or an instruction to use the timer.
[0128] Next, UE100 begins accessing the target cell. That is, in step S52, UE100 starts counting on the extended handover monitoring timer. UE100 may also start counting on the timer from the moment it begins accessing the target cell.
[0129] In step S53, UE100 sends PRACH(Msg1) to the target cell.
[0130] In step S54, the target cell receives PRACH from multiple UE100s.
[0131] In step S55, the target cell sends a random access response (Msg2) to each UE100 at different times for each UE100 (or each group of UE100s).
[0132] In step S56, UE100 sends an RRC reset completion message (Msg3) to the target cell in response to receiving a random access response (Msg2). Since the timing of receiving the random access response differs for each UE100, the RRC reset completion message (Msg3) will be sent at different times for each UE.
[0133] Furthermore, in UE100, if the RRC reset completion message (Msg3) cannot be sent even when the extended handover monitoring timer count reaches the timer value (or expiration value) (i.e., when the timer expires), it is determined that the conditional handover has failed. In this case, UE100 may transition to the RRC idle state.
[0134] [Other embodiments] The above-described operation flows can be performed not only independently, but also in combination of two or more operation flows. For example, some steps of one operation flow may be added to another operation flow, or some steps of one operation flow may be replaced with some steps of another operation flow. It is not necessary to execute all steps in each flow; only some steps may be executed.
[0135] In the embodiments and examples described above, an example in which the base station is an NR base station (gNB) was described, but the base station may also be an LTE base station (eNB) or a 6G base station. Furthermore, 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 an IAB node. Furthermore, UE100 may be an MT (Mobile Termination) of an IAB node.
[0136] Furthermore, 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). Additionally, a network node may consist of a combination of at least a part of the core network device and at least a part of a base station.
[0137] A program may be provided that causes a computer to perform each of the processes performed by the UE100 or gNB200. 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-transient recording medium. The non-transient recording medium is not particularly limited, but may be a recording medium such as a CD-ROM or DVD-ROM.
[0138] Alternatively, the circuits that perform each process carried out by the UE100 or gNB200 may be integrated, and at least a portion of the UE100 or gNB200 may be configured as a semiconductor integrated circuit (chipset, SoC: System on a chip).
[0139] The phrases “based on” and “depending on / in response to” used in this disclosure do not mean “based solely on” or “depending solely on” unless otherwise specified. “Based on” means both “based solely on” and “at least partially on.” Similarly, “depending on” means both “at least partially on” and “at least partially on.” The terms “include,” “comprise,” and variations thereof do not mean that only the listed items are included; they mean that only the listed items may be included, or that additional items may be included in addition to the listed items. Furthermore, the term “or” used in this disclosure is not intended to mean exclusive OR. Additionally, any reference to elements using designations such as “first,” “second,” etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used herein as a convenient way to distinguish between two or more elements. Therefore, references to the first and second elements do not imply that only two elements may be adopted therein, or that the first element must precede the second element in any way. In this disclosure, where articles are added by translation, such as a, an, and the in English, these articles shall be plural unless it is clearly indicated by the context that they are not.
[0140] Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to that described above, and various design changes can be made without departing from the gist of the invention. Furthermore, each embodiment, each operation example, or each process can be combined as appropriate, within the bounds of consistency.
[0141] This application claims priority to U.S. Provisional Application No. 63 / 421715 (filed November 2, 2022), the entirety of which is incorporated into the specification of this application.
[0142] (First Appendix) (Note 1) A communication control method used in a cellular communication system, The network node sends a conditional reconfiguration to the user device. The user device has the step of performing a conditional handover after a predetermined time has elapsed since it detected a predetermined condition, The detection of the predetermined conditions is either fulfilling the trigger conditions included in the conditional reset, or receiving an instruction to execute the conditional handover from the network node. The predetermined time is different for each user device. Communication control method.
[0143] (Note 2) The conditional reset includes instruction information that instructs ensuring the predetermined time from the time the predetermined condition is detected until the conditional handover is performed. The communication control method described in Appendix 1.
[0144] (Note 3) The conditional reset includes the predetermined time. The communication control method described in Appendix 1 or Appendix 2.
[0145] (Note 4) A communication control method used in a cellular communication system, The network node sets the PRACH resource on the user device, The user device, when performing a conditional handover, includes the step of sending a PRACH using the PRACH resource configured on the user device, The PRACH resource is a different resource for each user device. Communication control method.
[0146] (Note 5) The transmission step includes the step of performing the conditional handover when the user device detects a predetermined condition, The detection of the predetermined conditions is either fulfilling a trigger condition included in a conditional reset received from the network node, or receiving an instruction to execute the conditional handover from the network node. A communication control method as described in any of Appendix 1 to Appendix 4.
[0147] (Note 6) The execution instruction includes instruction information indicating whether or not to use the PRACH resource. A communication control method as described in any of Appendix 1 to Appendix 5.
[0148] (Note 7) A communication control method used in a cellular communication system, The network node sends a conditional reconfiguration to the user device, which includes beam information representing the beam used by the user device. When the user device performs a conditional handover, it uses the resources associated with the beam. teP The step of sending RACH, The beam is different for each user device. Communication control method.
[0149] (Note 8) The network node further includes the step of controlling the beam directions of the target cell and the source cell so that the beams of the target cell and the source cell are aligned in the same direction at the same time, The steps performed by the user device include the user device transmitting the PRACH to the target cell using the resource associated with the same beam used in the source cell. A communication control method as described in any of Appendix 1 to Appendix 7.
[0150] (Note 9) A communication control method used in a cellular communication system, The user device sends PRACH(Msg1) to the target cell when performing a conditional handover, The target cell sends a random access response (Msg2) to the user device at a different timing for each user device. The user device has the step of sending an RRC Reconfiguration Complete message (Msg3) to the target cell at a different timing for each user device. Communication control method.
[0151] (Note 10) The source cell further includes the step of sending a conditional reset including an extended monitoring timer to the user device, The step of transmitting PRACH(Msg1) includes the step of starting the extended monitoring timer count from the time the user device starts accessing the target cell, The step of sending the RRC reset completion message (Msg3) includes the step of determining that the conditional handover has failed if the user device is unable to send the RRC reset completion message (Msg3) even when the count value of the extended monitoring timer reaches the expiration value. A communication control method as specified in one of the appendices 1 through 9.
[0152] (Second Addendum) introduction The WID for mobile IAB was revised in RAN#97e, with the following objectives: The detailed objectives of WI are as follows: Define the movement / topological adaptation procedures to achieve IAB node mobility, including the movement of entire IAB nodes between donors (complete movement). - Mobile IAB nodes can connect to stationary (intermediate) IAB nodes. Optimizations specific to scenarios where a mobile IAB node connects to a stationary (intermediate) IAB node, or connects directly to an IAB-donor-DU, are not prioritized. - Mobility of dual-connected IAB nodes will have a lower priority. • Enhance the mobility of IAB nodes and the UEs that serve them, including aspects related to group mobility. There is no optimization regarding targeting of surrounding UEs. Note: The solution should avoid touching on topics already discussed in Rel-17 or topics excluded from Rel-17, except for feature enhancements specifically for IAB node mobility. • Mitigation of interference through IAB node mobility, including avoidance of potential reference signal and control signal collisions (PCI, RACH, etc.). The following principles should be respected. - Mobile IAB nodes should be able to serve legacy UEs. - Solutions that provide optimization for mobile IAB may involve enhancements to the Rel-18 UE.
[0153] One of the main challenges in Rel-18 is how to efficiently perform handovers of multiple descendant UEs during movement between mobile IAB nodes. This note details the enhancements to the mobility of mobile IABs.
[0154] Discussion Strengthening UE Mobility UE handover procedure RAN2#119bis-e reached the following agreement regarding the UE handover procedure: RAN2 focuses on scenarios where, during full transit, the UE perceives two logical DU cells as different physical cells (e.g., having different PCIs if on the same carrier) and the two logical DU cells use separate physical resources (i.e., different carriers, or orthogonal time and frequency resources on the same carrier, as supported in legacy L1). The following options O1, O2, and O3 are considered from the QC tdoc. 1) Message retention by logical source IAB-DU 2) Conditional execution by UEs based on broadcast notifications (indications) such as service time SIB notifications (indications) or MT movement DCI notifications (indications) (including CHOs triggered by new triggers). 3) Legacy CHO (which has implementation-specific behavior, such as using source cell power down or target cell power up to trigger actual HOs) RAN2 assumes that O1 and O3 above are working, and further consideration is needed if O2 (a new trigger, etc.) is required.
[0155] O1, whose delivery has been put on hold, will operate on the Rel-15 UE and is therefore considered the baseline. O3, with its current conditional handover (CHO), will operate on the Rel-16 UE. Therefore, further consideration is needed regarding whether to strengthen the CHO for Rel-18, such as basing it on O3.
[0156] Given that feasible solutions already exist, such as O1 and O3, it is questionable whether enhancements are truly necessary. On the other hand, it is likely that at some point in the future, Rel-18 UEs will make up the majority of the network. In this case, if there are any disadvantages to existing solutions, it would be useful to make some kind of enhancement for Rel-18 and later UEs. If new solutions are discussed, one of the key points is to ensure that UE handovers do not generate signaling storms, as pointed out in RAN2#119bis-e.
[0157] Proposal 1: RAN2 should discuss whether there are any problems with existing solutions for UE handover, namely held delivery (O1) and CHO (O3).
[0158] In the case of O1, RRC resynchronization is performed. settingThe RRC reconfiguration message is held by the moving IAB node and delivered to the UE when the moving IAB-MT completes its move to the target donor. The timing of sending the RRC reconfiguration message is controlled by the moving IAB node, so the timing of receiving the RRC reconfiguration completion message is controllable. This depends on how long the two cells (i.e., provided by the dual DU) are maintained, during which some DL load may occur on the source cell and some UL load on the target cell.
[0159] In the case of O3, conditional re- setting RRC Recycle setting This is pre-transmitted by the IAB donor via the mobile IAB node. This allows for advance preparation of the UE handover command and enables the DL load to be distributed within the source cell in a timely manner. On the other hand, CHO is executed when existing events (i.e., A3 / A5) are met. O3 depends on the radio state of the source / target cell (i.e., control of transmit power), especially when the source and target cells are provided from an antenna that is physically quasi-common, and when there is a storm of UL signaling in the target cell, i.e., PRACH and RRC re-signaling. setting This could lead to the completion of the process.
[0160] From the observations above, O1 may require holding the source and target cells for extended periods to reduce DL / UL load. O3 may cause a storm of UL signaling in the target cell. In other words, a signaling storm can be avoided by holding the two cells (provided by dual DU) for a minimum period of time.
[0161] Proposal 2: If CHO is strengthened for UE in Rel-18, RAN2 should agree on a solution to avoid signaling storms at DL (source cell) and UL (target cell), even if source and target cells are held for a minimum period during the migration of the moving IAB node.
[0162] Enhanced cell reselection functionality in UE RAN2#119bis-e agreed on the following confirmations, observations, and assumptions. RAN2 has confirmed that the mobile IAB needs to work with the legacy UE. RAN2 has confirmed that if a UE camps on / connects to a mobile IAB cell for an extended period, it may consider the UE to be onboard to the mobile IAB cell (i.e., the UE needs to know that this cell is such a cell). Further investigation is needed regarding the timeframe. RAN2 makes the following assumptions about UEs operating in a moving IAB cell: Assumption 1: From a network perspective, the principles for setting legacy parameters (including cell (re)selection, cell reservation, and access restrictions) remain unchanged compared to legacy IAB cells. Assumption 2: There is no specification impact on the operation of legacy UE. Assumption 3: Information about newly broadcast mobile IAB cells in R18 (if agreed upon) does not prohibit / control access from legacy UEs. Assumption 4: Non-enhancement UEs (including legacy UEs and non-enhancement R18 UEs) simply ignore information about newly broadcast mobile IAB cells from R18 (if agreed upon). RAN2 assumption: Moving IAB cell broadcast information To assist with mobility in the idle / inactive mode of the Rel-18UE, a 1-bit mobile IAB cell type indication will be introduced (further consideration is needed regarding when it is necessary to know that the UE is onboard). Further consideration is needed regarding how this will be used (it may vary depending on the implementation). RAN2 has not identified any fixes to prevent surrounding UEs from accessing the mobile IAB node from the perspective of mobile IAB WI, but believes that SA2 may be working on an applicable Rel-18 solution.
[0163] Two main scenarios, along with several sub-cases involving expected UE behavior, can be considered as follows: Scenario A: The moving IAB node is moving along with the camped UE. -Subcase A1:UE (e.g., inside a train) should remain on the mobile IAB node. -Subcase A2: Surrounding UEs (such as outside the train) must not camp on the moving IAB node. Scenario B: The moving IAB node is parked together with the camp UE. -Subcase B1: UE (e.g., still on the train) should remain at the mobile IAB node. - Subcase B2: UE (e.g., getting off a train) re-selects a stationary cell (e.g., a macrocell). -Subcase B3: Surrounding UEs (e.g., boarding a train) need to re-select the moving IAB node. -Subcase B4: Surrounding UEs (e.g., still in the station) should remain in their fixed cells.
[0164] In subcase A1, the UE moves with the mobile IAB node. Therefore, RSRP and RSRQ from the mobile IAB node are always stable and sufficiently good. This does not trigger the cell reselection procedure. More precisely, if the frequency priority of the mobile IAB node is higher than that of the external cell, the UE may not perform either intra-frequency or inter-frequency measurements. For example, the mobile IAB node broadcasts its frequency priority as "7" or broadcasts its cell as an HSDN cell.
[0165] Furthermore, a train may have multiple carriages, and mobile IAB nodes could be located in each carriage. Even when the UE moves between carriages, from the perspective of the UE within the train, one of the mobile IAB node cells is always more stable than an external macrocell. Also, in a typical case, we assume that the mobile IAB node cells are operating at the same frequency. In this case, existing in-frequency cell reselection, i.e., the R criterion, works appropriately.
[0166] Finding 1: A typical configuration would be for a moving IAB cell to broadcast a serving frequency priority of "7" or broadcast an HSDN cell indication to prevent UEs moving with the moving IAB cell from undergoing cell reselection.
[0167] In subcases B1 and B2, the AS has no way of knowing whether the user stays on the train or gets off. In this case, even if the mobile IAB node broadcasts some information, the UE cannot ultimately decide which cell (mobile IAB node or fixed macrocell) to re-select. Therefore, the UE's re-selection of a cell ultimately depends on radio conditions and frequency priority. Consequently, the mobile IAB node needs to revert to the serving frequency priority set as observation 1. That is, the mobile IAB node either broadcasts serving frequency priority, for example, in the same way as a fixed macrocell layer, or stops broadcasting HSDN cell indications.
[0168] Finding 2: If both the UE and the mobile IAB node fail, the UE cannot determine whether to re-select the mobile IAB node unless it understands the user's intentions. In other words, it depends on the wireless conditions.
[0169] Finding 3: It is typical for a stationary mobile IAB cell to revert to the frequency priority or HSDN cell indication it was using during movement (i.e., similar to Finding 1).
[0170] However, based on the observations above, the drawback of the current mechanism is that the SIB of a moving IAB node needs to be changed according to its movement state. However, this may not be a critical issue that needs to be resolved.
[0171] Finding 4: A drawback of the current mechanism is that the moving IAB cell needs to change its SIB depending on its movement state. In other words, it falls somewhere between Finding 1 and Finding 3.
[0172] For subcase A2, the same logic as in Finding 1 allows the UE to remain in a stationary macrocell. That is, if there is sufficient RSRP / RSRQ from the macrocell, the UE will not perform in-frequency measurements, and if the priority of the macrocell frequency is higher than the priority of the mobile IAB node, or if the mobile IAB node broadcasts an HSDN cell indication (i.e., the UE is not in a high-mobility state), it will not perform inter-frequency measurements either.
[0173] For subcases B3 and B4, for the same reasons as in Finding 2, cell reselection should depend on wireless conditions, and a typical configuration of a stationary mobile IAB node, as in Finding 3, is also applicable.
[0174] However, subcases A2, B3, and B4 are desirable behaviors for the surrounding UEs. WID explicitly states that it does not perform optimizations to target surrounding UEs. In the case of subcase B3, after the UE boards the train, it becomes subcase B1 or B2, but the initial state of the UE remains that of the surrounding UEs. Therefore, these subcases are outside the scope of Rel-18.
[0175] • Enhanced the mobility of IAB nodes and their UEs, including aspects related to group mobility. There are no optimizations for targeting surrounding UEs.
[0176] Finding 5: Optimizing the targeting of surrounding UEs is outside the scope of WI, but the same configuration as Findings 1 and 3 may be applicable.
[0177] In summary, the existing cell reselection mechanism, namely the one based on radio conditions and frequency priority, still functions well. Therefore, no enhancements are needed for the UE to perform cell reselection.
[0178] HSDN is valid for subcase A1.
[0179] Proposal 3: RAN2 should agree that no enhancements are needed for UEs to perform cell reselection with and from moving IAB nodes; in other words, revert to the assumption made at the last meeting regarding "1-bit moving IAB cell type indication".
[0180] Rel-18 UE RACH-less handover RAN2#119e reached the following agreement: R2 assumes that for onboard RRC connected UEs handed over with the mobile IAB node, a RACH-less procedure may be considered (depending on the UL synchronization assumption).
[0181] In LTE, RACH-less handover is configured within MobilityControlInfo using applicable timing advance (TA) and uplink grant information, as shown in Figure 17.
[0182] Regarding the TA value in RACH-less handover of a UE during IAB node migration, since the source and target cells are provided by the same "physical" DU (although provided via two "logical" DUs), it is assumed that the UE applies the latest TA value to access the target cell. In other words, the "physical" distance from the UE should be the same. Therefore, there is no need to explicitly set a TA value for the UE. On the other hand, if RACH-less handover is used in other scenarios, such as handover in a moving IAB-MT, a general approach like LTE configuration will be required.
[0183] Proposal 4: RAN2 should discuss whether, in the case of UE RACH-less handover, the UE implicitly applies the latest TA value or explicitly sets the applicable TA value.
[0184] Since the UE needs to send RRC Reconfiguration Complete within the UL resources provided by the target cell, the UL grant information needs to be configured in the UE.
[0185] Proposal 5: RAN2 should agree on UE RACH-less handover, where UL grant information is set by the target IAB donor CU.
[0186] Given the RRC IE structure of NR, it can be assumed that RACH-less handovers are indicated by the target IAB-donor CU during the handover procedure, and therefore the RACH-less configuration is included in reconfigurationWithSync within CellGroupConfig.
[0187] Proposal 6: RAN2 should agree that RACH-less handover is configured with a handover command (reconfiguration with synchronization).
[0188] One question is whether RACH-less handover can also be applied to conditional handover. RAN2#119e agreed that it would be useful to support conditional RACH-less handover because "R2 assumes that CHO or delayed RRC settings can serve as the baseline for group mobility."
[0189] Proposal 7: RAN2 should be discussed as a way to configure RACH-less handovers even with conditional handovers (conditional reconfiguration).
[0190] Enhancement of IAB-MT Mobility Notification (indication) of a mobile IAB node to an IAB donor CU. In RAN3#117e, the following agreement was reached: Donor CUs should be aware that IAB nodes are "mobile".
[0191] RAN2#119bis-e agreed on the following baseline. UE capability signalling is a baseline for informing the CU that the MT is of the "mobile IAB" type. Further consideration is needed regarding early mobile IAB notification (indication) in Msg5, etc. Regarding mobility state / mode indication, R2 sees the possibility of reusing legacy mobility state reports (such as mobilityState-r16) and current location reports from UEs. Further consideration is needed to determine whether either of these needs to be enhanced or supplemented for potential purposes such as predictive mobility.
[0192] In Rel-16 IAB, the IAB Node Indication is sent via Msg5, which is intended for the provider to use to select an AMF that supports the IAB. Therefore, one point is whether the provider needs to select an AMF that supports the mobile IAB, and whether they send the mobile IAB node indication via Msg5 is up to RAN3.
[0193] During discussions via email, several companies pointed out that donor CUs can obtain real-time mobility status through existing measurement reports such as Immediate MDT. Such mobility status information is considered useful for predictive mobility control. The reporter clarified that mobile IAB node indication is necessary for providers to set up appropriate measurement settings on mobile IAB nodes. However, since it is not a major issue if the donor CU sets up the mobile IAB node after receiving UE capability signaling, providing early indication is not justified.
[0194] Therefore, whether or not early movement IAB notification (indication) is required depends on RAN3.
[0195] Finding 6: For example, whether an early migration IAB notification (indication) in Msg5 is necessary depends on RAN3, depending on whether the donor CU needs to select an AMF that supports the migration IAB.
[0196] Access restrictions for mobile IAB nodes In WID, mobile IAB nodes are supposed to only provide services to UEs. - A mobile IAB node does not have descendant IAB nodes and provides services only to UEs.
[0197] To ensure the requirements are met, RAN2#119e agreed as follows: Not broadcasting the "iab-Support" notification is sufficient to prevent other IAB nodes from accessing the mobile IAB (there are no further specification implications).
[0198] However, the agreement was reached without sufficient discussion. In particular, the phrase "(without any further impact on specifications)" raises questions about whether it is acceptable to leave it up to the implementation. Since WID clearly requires that mobile IAB nodes cannot access other mobile IAB nodes, it is thought that the specification needs to clarify this assumption to avoid confusion in the implementation of mobile IABs. Therefore, it would be desirable for the Stage-2 specification to either incorporate the above agreement or to clearly state that "mobile IAB nodes cannot access other mobile IAB nodes in this release."
[0199] Proposal 8: RAN2 should agree to include in the Stage-2 specification that when an IAB node operates as a mobile IAB node in this release, the SIB should not be configured with IAB-Support IE.
[0200] Another restriction was discussed in RAN2#119bis-e and left to consideration as follows: Further consideration is needed regarding the introduction of a system where a fixed network broadcasts an indication that it "supports mobile IAB" (intended for mobile IAB MT).
[0201] Several companies have pointed out that "whether notification from the network to the moving IAB node is necessary may depend on whether the moving IAB node can camp on / connect to a normal IAB-enabled cell." Assuming there are legacy IAB donors in the network, there are three releases of IAB, each supporting a different migration mechanism: Rel-16 supports intra-CU topology adaptation, Rel-17 supports inter-CU topology adaptation with partial migration, and Rel-18 supports inter-CU migration with full migration.
[0202] In other words, technically, a mobile IAB node can connect to a Rel-16 donor if it moves to a nearby location (i.e., within a cell belonging to the same donor CU). On the other hand, if the mobile IAB node moves far away, it needs to connect to a Rel-17 or Rel-18 donor (i.e., between cells belonging to different donor CUs). In other words, a former mobile IAB node can be considered a stationary IAB node from a functional standpoint.
[0203] Finding 7: A mobile IAB node can connect to a Rel-16 donor if it is only moving nearby, but if it is moving far away, it needs to connect to a Rel-17 or Rel-18 donor.
[0204] In this sense, some kind of "supported mobile IAB" information broadcast from the parent node is necessary, but it is questionable whether a mobile IAB node can determine connectable cells based on such a 1-bit indication alone. For example, this indication is associated with the area the mobile IAB node can move to. However, it may also mean that the mobile IAB node needs to know the area it is moving to (or whether it is considered a stationary IAB node, e.g., depending on the OAM configuration). In addition, it is worth considering whether there are other cases in which a mobile IAB node is allowed to connect to a parent node that does not broadcast an indication. For example, if the mobile IAB node cannot find a parent node that broadcasts an indication. Therefore, RAN2 should discuss in detail what this indication means.
[0205] Proposal 9: RAN2 should agree to introduce some kind of "support for mobile IAB" indication. Further consideration is needed as to whether this should be a simple 1-bit indication, or whether there should be conditions under which a mobile IAB node is allowed access to a parent node that does not broadcast that indication.
Claims
1. A communication control method used in a cellular communication system, The user device receives a conditional reconfiguration from a network node, which includes configuration information that sets up the user device with PRACH (Physical Random Access Channel) resources individually assigned to the user device for conditional handover, and beam information that indicates a different beam for each user device that the user device should use for PRACH transmission. The user device, when performing the conditional handover, transmits a PRACH using the PRACH resource set up in the user device and associated with the beam specified in the beam information. Communication control method.
2. The aforementioned transmission includes the user device performing the conditional handover when it detects predetermined conditions, The detection of the predetermined conditions is either fulfilling the trigger conditions included in the conditional reset received from the network node, or receiving an instruction to execute the conditional handover from the network node. The communication control method according to claim 1.
3. A user device used in a cellular communication system, A receiving unit that receives a conditional reconfiguration from a network node, which includes configuration information for setting PRACH (Physical Random Access Channel) resources individually assigned to the user device for conditional handover, and beam information indicating a different beam for each user device that the user device should use for PRACH transmission. The system includes a transmission unit that, when performing the conditional handover, transmits a PRACH using the PRACH resource set up on the user device and associated with the beam specified in the beam information. User device.
4. In user equipment used in cellular communication systems, The process of receiving a conditional reconfiguration from a network node, which includes configuration information to set a PRACH (Physical Random Access Channel) resource individually assigned to the user device for conditional handover, and beam information indicating a different beam for each user device that the user device should use for PRACH transmission, When the user device performs the conditional handover, it performs the process of transmitting a PRACH using the PRACH resource set up in the user device and associated with the beam specified in the beam information. program.
5. A chipset for user equipment used in a cellular communication system, The process of receiving a conditional reconfiguration from a network node, which includes configuration information to set a PRACH (Physical Random Access Channel) resource individually assigned to the user device for conditional handover, and beam information indicating a different beam for each user device that the user device should use for PRACH transmission, When the user device performs the conditional handover, it performs the process of transmitting a PRACH using the PRACH resource set up in the user device and associated with the beam specified in the beam information. Chipset.
6. User equipment and Network nodes, including The User device is The network node receives a conditional reconfiguration that includes configuration information to set up the user device with a PRACH (Physical Random Access Channel) resource individually assigned to the user device for conditional handover, and beam information indicating a different beam for each user device that the user device should use for PRACH transmission. When performing the conditional handover, PRAC is transmitted using the PRACH resource set on the user device and associated with the beam specified in the beam information. Cellular communication system.
Citation Information
Patent Citations
Beam selection for initiating random access during conditional handover
JP2022538565A
Random access procedures for new radio (NR) networks
US20210251012A1
Mobility Procedure
US20210410039A1
Identifying a beam for accessing a target cell of a wireless handover
WO2018083649A1
Paging using beam parameters for beam-based operation
WO2021002863A1
