Beam configuration method and device

Abstract

A wireless communication method applied to a wireless terminal is disclosed. The method comprises: receiving beam mapping information for handover from a source cell to a target cell from a wireless network node; and performing a handover by using a beam determined based on the beam mapping information.

Description

Technical Field

[0001] The present invention relates generally to wireless communications, and more particularly to 5G communications. Background Art

[0002] As the number of digital data applications and services continues to increase, the demands and challenges on network resources and operators will also continue to increase. Being able to provide a wide range of network performance characteristics that meet future service demands is one of the main technical challenges facing service providers today. The performance requirements placed on the network will require connectivity in terms of data rate, latency, QOS, security, availability and many other parameters, all of which will vary from service to service. Therefore, enabling the network to allocate resources in a flexible manner in order to provide customized connectivity for each different type of service will greatly enhance the network's ability to meet future demands.

[0003] To meet these needs, the fifth generation (5G) mobile wireless technology and standards are being developed. One such technology is a separated network architecture, in which the Radio Access Network (RAN) functions are separated between the Central Unit (CU) and multiple Distributed Units (DU). For example, the RAN functions can be split at the point between the Packet Data Convergence Protocol (PDCP) layer and the Radio Link Control (RLC) layer of the 5G protocol stack, where the DU will handle all processes up to and including the RLC layer functions, and the CU will handle the PDCP layer and higher layer functions before the core network. This decomposition of RAN functions will provide many advantages to mobile network operators. For example, by isolating the stack from the PDCP layer and above, the CU will be able to act as a cloud-based aggregation point between multiple heterogeneous technologies in the provided network, and will therefore be able to serve multiple heterogeneous DUs.

[0004] Another technology developed for 5G networks is the Integrated Access and Backhaul (IAB) architecture for providing high-speed wireless backhaul to cell sites (e.g., base stations (BS)). As data demand and the number of cell sites increase, it is increasingly difficult to provide traditional fiber backhaul access to each cell site, especially for small cell base stations. For example, under the IAB architecture, the same infrastructure and resources (e.g., IAB nodes) can be used to provide access and backhaul to support user equipment (UE) packet data unit (PDU) sessions. The IAB architecture of the New Radio (NR) network will provide wireless backhaul and relay links to support flexible and dense deployment of NR cells without proportionally increasing the density of the transmission network. In addition, the IAB technology will allow dense networks of self-backhauled NR cells to be more easily deployed in a more integrated and robust manner. For example, the IAB technology in the 5G NR network will support multi-hop relay systems, where the network topology also supports redundant connections.

[0005] Figure 1 A block diagram of an IAB architecture network 100 is shown, wherein a core network 102 is connected to a donor IAB node 104. As used herein, the term "connection" refers to a wired or cable connection (e.g., a fiber optic cable) between two nodes or devices. The donor IAB node 104 is wirelessly coupled to a plurality of intermediate IAB nodes 106a and 106b and two serving IAB nodes 106c and 106d. As used herein, the term "coupling" refers to direct or indirect and wired or wireless communication between two nodes or devices.

[0006] like Figure 1 As shown, serving IAB nodes 106c and 106d are directly coupled to UEs 108a and 108b, respectively, and act as serving cell site base stations or access points for UEs 108a and 108b. UEs 108a and 108b are referred to herein as "access UEs." Serving IAB nodes 106c and 106d also act as relays and may forward their respective UE signals to their respective next uplink nodes in the transmission path, and forward downlink signals to their respective UEs 108a and 108b. Figure 1As shown, the serving IAB node 106c can forward uplink UE signals to one or both of the intermediate IAB nodes 106a and 106b, and receive downlink UE signals from one or both of the intermediate IAB nodes 106a and 106b. The intermediate IAB nodes 106a and 106b can forward uplink UE signals to the donor IAB node 104, and forward downlink signals to the serving IAB node 106d. The serving IAB node 106c can forward uplink UE signals to the donor IAB node 104, and then the donor IAB node can forward all received signals to the core network 102, and can forward downlink signals from the donor IAB node 104 to the access UE 108a.

[0007] Each IAB node 106a to 106d can have two functions: a base station BS function and a mobile terminal (Mobile Terminal, MT) function. The BS function describes that the IAB node can work like a base station and provide wireless access functions for the UE. As used herein, the "BS part" of the IAB node refers to the part of the IAB node related to the execution of the BS function of the IAB node, including all hardware, firmware and / or software. The MT function describes that the IAB node can work like a mobile terminal and is controlled and scheduled by the IAB host node or the upper-level IAB node. As used herein, the "MT part" of the IAB node refers to the part of the IAB node related to the execution of the MT function of the IAB node, including all hardware, firmware and / or software.

[0008] refer to Figure 1 If the network 100 also implements a split architecture, the host IAB node 104 will be replaced by a host CU (not shown) connected to the core network 102 and a host DU (not shown) connected to the host CU. Figure 1 As shown, each of the IAB nodes 106 a - 106 d will be coupled to the host DU in a manner similar to how they are coupled to the host IAB node 104 .

[0009] In the separated architecture network, each IAB node 106a to 106d can have two functions: DU function and mobile terminal MT function. The DU function indicates that the IAB node can work like a DU and provide the UE with the predetermined DU function. As used herein, the "DU part" of the IAB node refers to the part of the IAB node related to performing the DU function of the IAB node, including all hardware, firmware and / or software. The MT function and MT part of the IAB node in the separated architecture network are the same as the MT function and MT part of the above-mentioned IAB node of the non-separated architecture network.

[0010] Based on the IAB architecture, a mobile IAB is proposed, which focuses on scenarios where a mobile IAB node installed on a vehicle provides 5G coverage / capacity enhancement for UEs on board and / or around the vehicle. Specifically, the mobile IAB can be used in an outdoor environment to improve 5G coverage or connectivity, following a known / predictable route (e.g., bus, tram, etc.) or located in a convenient location (e.g., outside a stadium, in a hot spot area, or at an emergency site). The mobile IAB node provides connectivity for users or devices inside the vehicle and uses 5G wireless backhaul towards the macro network. It is assumed that the mobile IAB node can obtain better macro coverage than nearby UEs, for example, because better radio frequency (RF) / antenna and power capabilities are utilized.

[0011] Implementing mobile IAB nodes in 5G networks presents many challenges. One such challenge is that a group of UEs in a vehicle may perform handovers as the mobile IAB node moves. How to reduce handover overhead and reduce random access conflicts is a topic that needs to be studied.

[0012] This document relates to methods, systems and devices for beam configuration, and more particularly to methods, systems and devices for beam configuration of a UE served by a mobile IAB node during a handover procedure. Summary of the invention

[0013] The present disclosure relates to a wireless communication method, which is applied to a wireless terminal. The method comprises:

[0014] receiving beam mapping information for handover from a source cell to a target cell from a radio network node; and

[0015] The switching is performed by using the beam determined based on the beam mapping information.

[0016] Various embodiments may preferably achieve the following features:

[0017] Preferably, the handover does not include a random access procedure.

[0018] Preferably, the beam mapping information includes beam information to be used in the target cell or beam mapping between source beam information of the source cell and target beam information of the target cell.

[0019] Preferably, the source beam information includes at least one of the following fields of the source cell: a serving cell identifier (Identifier, ID), a bandwidth part (Bandwidth Part, BWP) ID, a resource set ID, a transmission configuration indicator (Transmission Configuration Indicator, TCI) state ID or a group of TCI state IDs.

[0020] Preferably, the beam information or target beam information includes at least one of the following fields of the target cell: serving cell ID, BWP ID, resource set ID, TCI state ID or a group of TCI state IDs.

[0021] Preferably, the source beam information includes at least one of the following fields of the source cell: serving cell ID, BWP ID, physical uplink control channel (PUCCH) resource ID, PUCCH spatial relationship ID or a group of PUCCH spatial relationship IDs.

[0022] Preferably, the beam information or the target beam information includes at least one of the following fields of the target cell: a serving cell ID, a BWP ID, a PUCCH resource ID, a PUCCH spatial relationship ID, or a group of PUCCH spatial relationship IDs.

[0023] Preferably, performing the switching by using the beam determined based on the beam mapping information includes at least one of the following:

[0024] Synchronize to the target cell by using the beam determined based on the beam mapping information,

[0025] receiving an uplink grant from a radio network node by using a beam determined based on the beam mapping information, or

[0026] A radio resource control reconfiguration complete message is transmitted to the radio network node by using the beam determined based on the beam mapping information.

[0027] Preferably, the beam mapping information includes a validity timer of the beam mapping information.

[0028] Preferably, the wireless communication method also includes communicating with a wireless network node in a target cell using a beam determined based on beam mapping information before at least one of the following: receiving PUCCH spatial relationship signaling from a wireless network node in the target cell; receiving TCI status signaling from a wireless network node in the target cell; completing uplink beam training in the target cell; or expiration of a validity timer of the beam mapping information.

[0029] Preferably, the wireless terminal is a user equipment, and the radio network node is a mobile integrated access and backhaul IAB node, a source IAB host, a source IAB host centralized unit CU, a source IAB distributed unit DU, a target IAB host CU or a target IAB DU.

[0030] The present disclosure relates to a wireless communication method, which is applied to a wireless network node. The method comprises:

[0031] receiving context information associated with the wireless terminal in the source cell from the target network node, and

[0032] The beam mapping information of the wireless terminal in the target cell is transmitted to the target network node.

[0033] Various embodiments may preferably achieve the following features:

[0034] Preferably, the wireless terminal is handed over from the source cell to the target cell without a random access procedure.

[0035] Preferably, handover of the wireless terminal from the source is performed, and the handover does not include a random access procedure.

[0036] Preferably, the beam mapping information includes beam information to be used in the target cell or a mapping between source beam information of the source cell and target beam information of the target cell.

[0037] Preferably, the source beam information includes at least one of the following fields of the source cell: a serving cell identification ID, a bandwidth part BWP ID, a resource set ID, a transmission configuration indicator TCI state ID, or a group of TCI state IDs.

[0038] Preferably, the beam information or target beam information includes at least one of the following fields of the target cell: serving cell ID, BWP ID, resource set ID, TCI state ID or a group of TCI state IDs.

[0039] Preferably, the source beam information includes at least one of the following fields of the source cell: serving cell ID, BWP ID, physical uplink control channel PUCCH resource ID, PUCCH spatial relationship ID or a group of PUCCH spatial relationship IDs.

[0040] Preferably, the beam information or the target beam information includes at least one of the following fields of the target cell: a serving cell ID, a BWP ID, a PUCCH resource ID, a PUCCH spatial relationship ID, or a group of PUCCH spatial relationship IDs.

[0041] Preferably, the wireless communication method further comprises: transmitting an uplink grant for transmitting a radio resource control reconfiguration complete message to a wireless terminal in the target cell by using a beam determined based on the beam mapping information.

[0042] Preferably, the wireless communication method further comprises receiving a radio resource control reconfiguration completion message from the wireless terminal in the target cell to the radio network node by using the beam determined based on the beam mapping information.

[0043] Preferably, the beam mapping information includes a validity timer for the beam mapping information.

[0044] Preferably, the wireless communication method also includes communicating with a base station in a target cell using a beam determined based on a beam before at least one of the following operations: transmitting PUCCH spatial relationship signaling to a wireless terminal in the target cell; transmitting TCI status signaling to a wireless terminal in the target cell; or expiration of a validity timer of the beam mapping information.

[0045] Preferably, the context information includes at least one of the source distributed unit DUID of the wireless terminal in the source cell, the next-generation base station (Next-Generation NodeB, gNB) DU UE F1 application protocol (F1 ApplicationProtocol, F1AP) ID (gNB-DU UE F1AP ID) of the wireless terminal in the source DU, the special cell (SpecialCell, sPCell) ID of the wireless terminal in the source cell, or a shared indication.

[0046] Preferably, the sharing indication includes at least one of the following: signaling radio bearer (SRB) sharing, indicating that the SRB configuration of the wireless terminal is reused in the source cell; data radio bearer (DRB) sharing, indicating that the DRB information of the wireless terminal is reused in the source cell; full sharing, indicating that the SRB configuration and DRB information of the wireless terminal are reused in the source cell; at least one SRB ID; or at least one DRB ID.

[0047] Preferably, the wireless communication method further comprises determining beam mapping information based on the context information.

[0048] Preferably, the wireless communication method further comprises, for the wireless terminal in the target cell, utilizing at least part of the configuration information of the wireless terminal in the source cell based on the context information.

[0049] Preferably, the wireless terminal is a user equipment, the radio network node is a mobile integrated access and backhaul IAB node or a target IAB distributed unit, and / or the target network node is a target IAB host centralized unit.

[0050] The present disclosure relates to a wireless communication method, which is applied to a target network node. The method comprises:

[0051] A handover request is received from a source network node for the wireless terminal to handover from a source cell to a target cell.

[0052] Various embodiments may preferably achieve the following features:

[0053] Preferably, the handover does not include a random access procedure.

[0054] Preferably, the handover request includes context information associated with the wireless terminal in the source network node.

[0055] Preferably, the context information includes at least one of ID information or a sharing indication.

[0056] Preferably, the sharing indication includes at least one of the following: signaling radio bearer SRB sharing, indicating reuse of the SRB configuration of the wireless terminal in the source cell; data radio bearer DRB sharing, indicating reuse of the DRB information of the wireless terminal in the source cell; full sharing, indicating reuse of the SRB configuration and DRB information of the wireless terminal in the source cell; at least one SRB ID; or at least one DRB ID.

[0057] Preferably, the ID information includes at least one of a source distributed unit DU ID of the wireless terminal in the source cell, a gNB-DU UE F1AP ID of the wireless terminal in the source DU, or a special cell sPCell ID of the wireless terminal in the source cell.

[0058] Preferably, the wireless terminal is a user equipment, the target network node is a target IAB host centralized unit CU of the wireless terminal in a target cell, and the source network node is a source IAB host CU of the wireless terminal in a source cell.

[0059] The present disclosure relates to a wireless communication method, which is applied to a source network node. The method comprises:

[0060] A handover request for the wireless terminal to handover from the source cell to the target cell is transmitted to the target network node.

[0061] Various embodiments may preferably achieve the following features:

[0062] Preferably, the handover request includes identification ID information associated with the wireless terminal.

[0063] Preferably, the handover does not include a random access procedure.

[0064] Preferably, the ID information includes at least one of a source distributed unit DU ID of the wireless terminal in the source cell, a gNB-DU UE F1AP ID of the wireless terminal in the source DU, or a special cell sPCell ID of the wireless terminal in the source cell.

[0065] Preferably, the wireless terminal is a user equipment, the target network node is a target IAB host centralized unit CU of the wireless terminal in a target cell, and the source network node is a source IAB host CU of the wireless terminal in a source cell.

[0066] The present disclosure relates to a wireless terminal. The wireless terminal comprises:

[0067] a communication unit configured to receive beam mapping information for handover from a source cell to a target cell from a radio network node, and

[0068] A processor is configured to perform switching by using a beam determined based on the beam mapping information.

[0069] Various embodiments may preferably achieve the following features:

[0070] Preferably, the processor is further configured to execute any of the aforementioned wireless communication methods.

[0071] The present disclosure relates to a wireless network node. The wireless network node comprises:

[0072] A communication unit, the communication unit being configured to:

[0073] receiving context information associated with the wireless terminal in the source cell from the target network node, and

[0074] The beam mapping information of the wireless terminal in the target cell is transmitted to the target network node.

[0075] Various embodiments may preferably achieve the following features:

[0076] Preferably, the radio network node further comprises a processor configured to execute any of the aforementioned wireless communication methods.

[0077] The present disclosure relates to a target network node. The target network node includes:

[0078] A communication unit is configured to receive a handover request from a source network node for a wireless terminal to handover from a source cell to a target cell.

[0079] Various embodiments may preferably achieve the following features:

[0080] Preferably, the target network node further comprises a processor configured to execute any of the aforementioned wireless communication methods.

[0081] The present disclosure also relates to a computer program product, including a computer-readable program medium code stored thereon, and when the code is executed by a processor, the processor implements the wireless communication method described in any of the aforementioned methods.

[0082] The exemplary embodiments disclosed herein are intended to provide features that are easily understood by reference to the following detailed description when combined with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are given as examples rather than limitations, and it will be apparent to those of ordinary skill in the art who have read the present disclosure that various modifications may be made to the disclosed embodiments while still within the scope of the present disclosure.

[0083] Therefore, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be rearranged while remaining within the scope of the present disclosure. Therefore, it will be understood by those of ordinary skill in the art that the methods and / or techniques disclosed herein present various steps or actions in an example order, and the present disclosure is not limited to the specific order or hierarchy presented, unless otherwise expressly stated.

[0084] The invention is defined by the independent claims. Preferred embodiments are defined in the dependent claims. In the following description, although many features may be designated as optional, it should be recognized that all features contained in the independent claims should not be construed as optional.

[0085] The above and other aspects and implementations thereof are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0086] Figure 1 A block diagram of an IAB architecture network is shown.

[0087] Figure 2 A schematic diagram of a mobile IAB scenario according to an embodiment of the present disclosure is shown.

[0088] Figure 3 A schematic diagram of a network (architecture) according to an embodiment of the present disclosure is shown.

[0089] Figure 4 A schematic diagram showing a process according to an embodiment of the present disclosure is shown.

[0090] Figure 5 A schematic diagram showing a process according to an embodiment of the present disclosure is shown.

[0091] Figure 6 A schematic diagram showing a process according to an embodiment of the present disclosure is shown.

[0092] Figure 7 A schematic diagram showing a process according to an embodiment of the present disclosure is shown.

[0093] Figure 8 An example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure is shown.

[0094] Fig. 9 An example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0095] For the mobile IAB scenario, the mobile IAB node moves with the vehicle, which may span a large area, e.g. Figure 2 As shown. As the mobile IAB node moves, the mobile IAB can switch from one parent IAB node to another parent IAB node. At this time, a group of UEs in the vehicle served by the mobile IAB node can also perform handover (HO). When a group of vehicle-mounted UEs perform HO at the same time, a random access channel (RACH) conflict may occur. In order to avoid RACH conflicts, RACH-free HO (i.e., HO without RACH process) can be considered for vehicle-mounted UEs. Specifically, the target host CU can configure the UE to skip the RACH process during the handover process.

[0096] In handover, the UE and the target gNB perform an initial beam detection procedure via a RACH procedure / operation. There is an association between one or more Synchronization Signal / Physical Broadcasting Channel (SS / PBCH or SSB) blocks and a Physical Random Access Channel (PRACH) transmission resource opportunity. The UE can measure the detected SS / PBCH blocks and select the PRACH resource associated with the SSB whose Reference Signal Received Power (RSRP) measurement result is greater than the subsequent transmission threshold. Based on the PRACH reception, the gNB can determine the beam direction for the downlink transmission, which is similar to the SSB associated with the PRACH resource. Thereafter, before the UE receives a Media Access Control (MAC) control element (CE) activation command for a TCI state, the UE may assume that the demodulation reference signal (DMRS) antenna port associated with the physical downlink control channel (PDCCH) reception is quasi-co-located with the SSB or Channel State Information-Reference Signal (CSI-RS) resource identified by the UE during the RACH process.

[0097] When the mobile IAB scenario is involved, the mobile IAB node performs HO from the source DU to the target DU. When the mobile IAB-DU performs HO, the vehicle-mounted UE needs to perform HO together with the mobile IAB node. For the HO of a vehicle-mounted UE, the source cell and the target cell actually belong to the same mobile IAB-DU. Here, the mobile IAB-DU is regarded as the source logical DU and the target logical DU connected to the source host CU and the target host CU respectively, as shown in Figure 3As shown. The source cell and the target cell belong to the source logical DU and the target logical DU, respectively. During the HO process, the relative position between the UE and the source / target logical DU may not change. Therefore, it can be assumed that the beam direction of the UE's uplink (Uplink, UL) / downlink (Downlink, DL) transmission / reception has not changed. Note that the target logical DU can be reconfigured by the target host CU with different time / frequency resources, and the beam configuration (e.g., TCI state, Quasi Co-Location (Quasi Co-Location, QCL) and related reference signals (Reference Signal, RS)) can also change.

[0098] Implementation 1:

[0099] From the UE's perspective, the two logical DU cells can be viewed as different physical cells (i.e., separate source and target cells). The frequencies, physical cell IDs (PCIs) and even resources that can be used by the source and target cells can be configured differently. In this case, the cell-specific and UE-specific beam management-related configurations of the source cell may be very different from those of the target cell. On the other hand, because the source logical DU and the target logical DU are actually the same, it is possible for the two logical DUs to share at least part of the UE context and / or beam direction information of a given UE.

[0100] To support possible scenarios, during the HO preparation process, the source host CU may send UE ID information to the target host CU, such as Figure 4 As shown. Based on the UE ID information, the target host CU can locate the UE at the target logical DU. For example, the UE ID information may include the gNB-DU UE F1AP ID at the source logical DU. In addition, at least one of the following information can be sent from the source host CU to the target host CU: sPcell ID and / or DU ID. Here, sPCell ID represents the NR cell global identifier (NR Cell Global Identifier, NCGI) of the source cell to which the UE is connected. DU ID represents the ID of the source logical DU.

[0101] In one embodiment, the target host CU may request the target logical DU to perform UE context setup and / or modification for the vehicle UE. To support UE context sharing between the source logical DU and the target logical DU, the target host CU may send at least one of the following information to the target logical DU: gNB-DU UE F1AP ID, sPcell ID, old DU ID, UE context sharing indication, or RACH skip indication, such as Figure 5As shown. Here, gNB-DU UE F1AP ID, sPcellID, DU ID represent the gNB-DU UE F1AP ID, sPcell ID, DU ID at the source logical DU, respectively. The UE context sharing indication may include at least one of full sharing, SRB sharing, DRB sharing, or SRB / DRB ID. Here, full sharing indicates that all SRBs and DRBs can reuse the configuration at the source logical DU. SRB sharing indicates that the RLC / MAC configuration of the SRBs at the source logical DU can be reused. DRB sharing indicates that DRB information such as DRB quality of service (QoS) or QoS flow to DRB mapping or DL ​​transport network layer (TNL) information may not be changed, and / or the previous DRB configuration at the source host CU / logical DU may be reused. SRB / DRB ID indicates that for a given SRB / DRB, the previous configuration at the source logical DU / CU may be reused. It should be noted that for DRB configuration sharing, the target host CU can at least update the UL user plane (User Plane, UP) TNL information of the DRB.

[0102] For example, if the target logical DU receives a sharing indication for a given DRB, the target logical DU can retrieve the UE's context at the source logical DU and then reuse the RLC / MAC / logical channel configuration of the DRB for the target logical DU. On the other hand, with a sharing indication for a given DRB ID, the target host CU does not need to send DRB QoS information, QoS flow to DRB mapping information to the target logical DU. The target logical DU can reuse the previously received DRB QoS information and QoS flow to DRB mapping information stored at the source logical DU.

[0103] On the other hand, the target host CU can decide whether the RACH procedure can be skipped for the UE during the HO preparation phase. Figure 5 In the example, the target host CU may send a RACH skip indication to the target logical DU. Upon receiving such an indication, the target logical DU configures beam information for the UE, and the UE reuses the beam configuration at the source logical DU as much as possible.

[0104] Implementation 2:

[0105] Figure 6A schematic diagram of a process according to an embodiment of the present disclosure is shown. In this embodiment, when / if the vehicle-mounted UE performs HO, the target logical DU may decide that the vehicle-mounted UE may skip the RACH process at the target cell. If the target logical DU receives the IAB-DU cell resource configuration from the host CU, the target logical DU may attempt to configure the same SSB / CSI-RS / sounding reference signal (SRS) as the source logical DU and / or configure at least one of the TCI state, QCL type, and SRS spatial relationship information. In one embodiment, the target logical DU is capable of configuring the same RS and / or the same TCI state and / or the same spatial relationship configuration, and the target logical DU may indicate to the target host CU that the same beam configuration may be used. In this case, the same beam configuration may be transmitted from the target host CU to the source host CU. The source CU may then send the same beam indication to the UE, for example via an RRCReconfiguration with a synchronization message, to trigger a RACH-free HO on the UE side.

[0106] In one embodiment, the IAB-DU cell resource configuration from the target host CU may be different from the configuration received from the source host CU, and the target logical DU cannot be guaranteed to use exactly the same beam-related configuration. In this case, the target logical DU can be configured with a new set of SSB / CSI-RS / SRS. In addition, the numbers and indices of these reference signalings may also be different from those of the source logical DU. Because the source logical DU and the target logical DU are actually the same physical DU, the target logical DU can derive the SSB / CSI-RS / SRS configuration mapping between the reference signaling (number and index) of the source logical DU and the reference signaling (number and index) of the target logical DU. The source host CU can send beam mapping information to the UE via RRCReconfiguration with a synchronization message. The UE can use the beam mapping information to determine the beam to be used in the target cell.

[0107] In one embodiment, the target logical DU may transmit the determined configuration mapping to the target host CU, and the target host CU transmits the received configuration mapping to the source host CU.

[0108] Specifically, the target logical IAB DU may generate one or more mappings between the beam information of the source logical DU and the beam information of the target logical DU. In one embodiment, the beam information of the source logical DU may include at least one of the following: (source) serving cell ID, (source) BWP ID, ControlResourceSetId (control resource set ID), (source) TCI state ID, or a group of (source) TCI state IDs. Similarly, the beam information of the target logical DU may include at least one of the following: (target) serving cell ID, (target) BWP ID, ControlResourceSetId, (target) TCI state ID, or a group of (target) TCI state IDs.

[0109] In one embodiment, the beam information of the source logical DU may include any combination of the following fields: (source) serving cell ID, (source) BWP ID, (source) PUCCH resource ID, (source) PUCCH spatial relationship ID, or a group of (source) PUCCH spatial relationship IDs. The beam information of the target logical DU may include any combination of the following fields: target serving cell ID, target BWPID, target PUCCH resource ID, target PUCCH spatial relationship ID, or a group of target PUCCH spatial relationship IDs.

[0110] Upon / after receiving beam mapping information (e.g., included in RRCReconfiguration with synchronization information), the UE may determine the receive (Receive, Rx) beam at the target cell based on the received beam mapping information. In one embodiment, the beam at the source cell used by the UE is (source cell 1, BWP 1, and TCI state ID 5), and the received beam mapping is from (source cell 1, BWP 1, and TCI state ID 5) to (target cell 1, BWP 1, and TCI state ID 3). In this embodiment, the UE may initially utilize (target cell 1, BWP 1, and TCI state ID 3) for PDCCH monitoring. Next, the UE may synchronize with the target cell and receive an UL grant for RRCReconfigurationcomplete message transmission. The UE may continue to utilize the mapped beam until / before the UE receives a PUCCH spatial relation activation / deactivation MAC CE and / or a TCI state activation / deactivation MAC CE from the target cell.

[0111] Implementation 3:

[0112] Figure 7 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Figure 7In the embodiment, the UE receives the beam mapping information of the target cell and the pre-allocated / assigned UL grant, for example, in the RRCReconfiguration with synchronization message. In this case, the UE can be synchronized to the target cell, and the UE can transmit the RRCReconfigurationComplete message to the target cell using the same beam direction as the source cell. In one embodiment, the beam direction information of the source cell can be used until the UE ends / completes UL beam training and / or selects a suitable transmit (Transmit, Tx) beam in the target cell.

[0113] Implementation 4:

[0114] In one embodiment, during the HO preparation process, the target logical DU determines a list of activated TCI states or PUCCH spatial relations to be used by the UE in the target cell. Specifically, the target logical DU can configure the list of activated TCI states or PUCCH spatial relations and the associated validity timer for the UE. The target logical DU passes this information to the source host CU, and the source host CU passes this information to the UE via RRCReconfiguration with a synchronization message. When receiving these activated TCI states or PUCCH spatial relationship information, the UE uses this information to perform DL monitoring in the target cell and starts the validity timer. When the validity timer expires, the list of activated TCI states or PUCCH spatial relations is no longer valid.

[0115] Figure 8 A schematic diagram of a wireless terminal 80 according to an embodiment of the present disclosure is provided. The wireless terminal 80 may be a UE, a mobile phone, a laptop computer, a tablet computer, an e-book, or a portable computer system, and is not limited thereto. The wireless terminal 80 may include a processor 800, such as a microprocessor or an application specific integrated circuit (ASIC), a storage unit 810, and a communication unit 820. The storage unit 810 may be any data storage device that stores a program code 812 accessed and executed by the processor 800. Embodiments of the storage unit 810 include, but are not limited to, a subscriber identity module (SIM), a read-only memory (ROM), a flash memory, a random access memory (RAM), a hard disk, and an optical data storage device. The communication unit 820 may be a transceiver, and is used to send and receive signals (such as messages or packets) according to the processing results of the processor 800. In one embodiment, the communication unit 820 communicates with the computer via a communication device. Figure 8At least one antenna 822 is shown for transmitting and receiving signals.

[0116] In one embodiment, the storage unit 810 and the program code 812 may be omitted, and the processor 800 may include a storage unit with stored program code.

[0117] The processor 800 may implement any of the steps of the exemplary embodiments on the wireless terminal 80 , for example, by executing the program code 812 .

[0118] The communication unit 820 may be a transceiver. The communication unit 820 may alternatively or additionally combine a transmitting unit and a receiving unit, which are configured to transmit signals to and receive signals from a wireless network node (eg, a base station), respectively.

[0119] Fig. 9A schematic diagram of a radio network node 90 according to an embodiment of the present disclosure is provided. The radio network node 90 may be a satellite, a BS, a network entity, a Mobility Management Entity (MME), a Serving Gateway (S-GW), a Packet Data Network (PDN) Gateway (P-GW), a Radio Access Network (RAN) node, a Next Generation RAN (NG-RAN) node, a gNB, an eNB, a gNB Central Unit (gNB-CU), a gNB Distributed Unit (gNB-DU), a data network, a core network or a Radio Network Controller (RNC), and is not limited thereto. In addition, the radio network node 90 may include (execute) at least one network function, such as an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), a Policy Control Function (PCF), an Application Function (AF), etc. The wireless network node 90 may include a processor 900 such as a microprocessor or an application specific integrated circuit (ASIC), a storage unit 910, and a communication unit 920. The storage unit 910 may be any data storage device that stores program code 912 accessed and executed by the processor 900. Examples of the storage unit 910 include, but are not limited to, a SIM, a ROM, a flash memory, a RAM, a hard disk, and an optical data storage device. The communication unit 920 may be a transceiver and is used to send and receive signals (e.g., messages or packets) according to the processing results of the processor 900. In an example, the communication unit 920 communicates with the computer via a memory card. Fig. 9 At least one antenna 922 is shown for transmitting and receiving signals.

[0120] In one embodiment, the storage unit 910 and the program code 912 may be omitted. The processor 900 may include a storage unit with stored program code.

[0121] The processor 900 may implement any of the steps described in the exemplary embodiments on the radio network node 90 , for example by executing the program code 912 .

[0122] The communication unit 920 may be a transceiver. The communication unit 920 may alternatively or additionally combine a transmitting unit and a receiving unit, which are configured to send and receive signals to and from a wireless terminal (eg, a user equipment or another wireless network node), respectively.

[0123] Although various embodiments of the present disclosure have been described above, it should be understood that they are given only by way of example and not by way of limitation. Similarly, various figures may depict example architectures or configurations, which are provided so that those of ordinary skill in the art can understand the exemplary features and functions of the present disclosure. However, it will be understood by those of ordinary skill in the art that the present disclosure is not limited to the example architectures or configurations shown, but may be implemented using a variety of alternative architectures and configurations. In addition, as those of ordinary skill in the art understand, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-mentioned exemplary embodiments.

[0124] It should also be understood that any reference to an element herein using names such as "first," "second," etc., does not generally limit the number or order of those elements. Rather, these names may be used herein as a convenient means of distinguishing between two or more elements or examples of an element. Thus, a reference to a first and a second element does not imply that only two elements may be employed, or that the first element must precede the second element in some manner.

[0125] In addition, those skilled in the art will appreciate that any of a variety of different techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols referenced in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0126] Those of ordinary skill in the art will further understand that any of the various illustrative logical blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of both), firmware containing various forms of programs or design codes of instructions (for convenience, referred to herein as "software" or "software modules"), or any combination of these technologies.

[0127] In order to clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, modules, circuits and steps have been described above generally according to their functions. Whether this functionality is implemented as hardware, firmware or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the entire system. Those of ordinary skill in the art can implement the described functions in various ways for each specific application, but such implementation decisions will not cause deviations from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, modules, etc. can be configured to perform one or more of the functions described herein. As used herein for a specific operation or function, the term "configured to" or "configured for" refers to a processor, device, component, circuit, structure, machine, module, etc. that is physically constructed, programmed and / or arranged to perform a specified operation or function.

[0128] In addition, it will be understood by those skilled in the art that the various illustrative logic blocks, modules, devices, components and circuits described herein may be implemented in an integrated circuit (IC) or performed by an IC circuit, which may include a general-purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logic blocks, modules and circuits may further include an antenna and / or a transceiver to communicate with various components within a network or within a device. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration to perform the functions described herein. If implemented in software, the functions may be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein may be implemented as software stored on a computer-readable medium.

[0129] Computer-readable media include computer storage media and communication media, and communication media include any media that can transfer a computer program or code from one place to another. Storage media can be any available media that can be accessed by a computer. As an example and not limitation, such computer-readable media may include RAM, ROM, Electrically Erasable Programmable ROM (EEPROM), Compact Disc ROM (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, and any other media that can be used to store the required program code in the form of instructions or data structures and can be accessed by a computer.

[0130] As used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements, for performing the relevant functions described herein. In addition, for the purpose of discussion, various modules are described as discrete modules; however, it is obvious to a person of ordinary skill in the art that two or more modules can be combined to form a single module that performs the relevant functions according to the embodiments of the present disclosure.

[0131] In addition, memory or other memory and communication components may be used in the embodiments of the present disclosure. It should be understood that, for the sake of clarity, the above description has described the embodiments of the present disclosure with reference to different functional units and processors. However, it will be apparent that any appropriate functional distribution between different functional units, processing logic elements or domains may be used without departing from the present solution. For example, functions illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic elements or controllers. Therefore, references to specific functional units are only references to suitable devices that provide the described functions, rather than referring to a strict logical or physical structure or organization.

[0132] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the claims. Therefore, the present disclosure is not limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as set forth in the claims.

Claims

1. A wireless communication method, applied to a wireless terminal, the method comprising: receiving beam mapping information for handover from a source cell to a target cell from a radio network node; as well as The switching is performed by using a beam determined based on the beam mapping information.

2. The wireless communication method according to claim 1, wherein: The handover does not include a random access procedure.

3. The wireless communication method according to claim 1 or 2, wherein: The beam mapping information includes: beam information to be used in the target cell, or beam mapping between source beam information of the source cell and target beam information of the target cell.

4. The wireless communication method according to claim 3, wherein: The source beam information includes at least one of the following fields of the source cell: Serving cell ID; Bandwidth part BWP ID; Resource set ID; Transmission Configuration Indicator TCI state ID; An array of TCI status IDs.

5. The wireless communication method according to claim 3 or 4, wherein: The beam information or the target beam information includes at least one of the following fields of the target cell: Serving cell ID; BWP ID; Resource set ID; TCI status ID; An array of TCI status IDs.

6. The wireless communication method according to any one of claims 3 to 5, wherein: The source beam information includes at least one of the following fields of the source cell: Serving cell ID; BWP ID; Physical uplink control channel PUCCH resource ID; PUCCH spatial relation ID; A set of PUCCH spatial relation IDs.

7. The wireless communication method according to any one of claims 3 to 6, wherein: The beam information or the target beam information includes at least one of the following fields of the target cell: Serving cell ID; BWP ID; PUCCH resource ID; PUCCH spatial relation ID; A set of PUCCH spatial relation IDs.

8. The wireless communication method according to any one of claims 1 to 7, wherein: Performing the switching by using the beam determined based on the beam mapping information includes at least one of the following: synchronizing to the target cell by using the beam determined based on the beam mapping information; receiving an uplink grant from the radio network node by using the beam determined based on the beam mapping information; A radio resource control reconfiguration complete message is transmitted to the radio network node by using the beam determined based on the beam mapping information.

9. The wireless communication method according to any one of claims 1 to 8, wherein: The beam mapping information includes a validity timer for the beam mapping information.

10. The wireless communication method according to any one of claims 1 to 9, further comprising: Prior to at least one of the following, communicating with the radio network node in the target cell using the beam determined based on the beam mapping information: receiving PUCCH spatial relation signaling from the radio network node in the target cell; receiving TCI status signaling from the radio network node in the target cell; completing uplink beam training in the target cell; The validity timer of the beam mapping information expires.

11. The wireless communication method according to any one of claims 1 to 10, wherein: The wireless terminal is a user equipment, and the radio network node is a mobile integrated access and backhaul IAB node, a source IAB host, a source IAB host centralized unit CU, a source IAB distributed unit DU, a target IAB host CU or a target IAB DU.

12. A wireless communication method, applied to a wireless network node, the method comprising: receiving context information associated with the wireless terminal in the source cell from the target network node, and Transmit beam mapping information of the wireless terminal in the target cell to the target network node.

13. The wireless communication method according to claim 12, wherein: The wireless terminal is handed over from the source cell to the target cell without a random access procedure.

14. The wireless communication method according to claim 12 or 13, wherein: The beam mapping information includes: beam information to be used in the target cell, or mapping between source beam information of the source cell and target beam information of the target cell.

15. The wireless communication method according to claim 14, wherein: The source beam information includes at least one of the following fields of the source cell: Serving cell ID; Bandwidth part BWP ID; Control resource set ID; Transmission Configuration Indicator TCI state ID; An array of TCI status IDs.

16. The wireless communication method according to claim 14 or 15, wherein: The beam information or target beam information used in the target cell includes at least one of the following fields of the target cell: Serving cell ID; BWP ID; Resource set ID; TCI status ID; An array of TCI status IDs.

17. The wireless communication method according to any one of claims 14 to 16, wherein: The source beam information includes at least one of the following fields of the source cell: Serving cell ID; BWP ID; Physical uplink control channel PUCCH resource ID; PUCCH spatial relation ID; A set of PUCCH spatial relation IDs.

18. The wireless communication method according to any one of claims 14 to 17, wherein: The beam information or target beam information includes at least one of the following fields of the target cell: Serving cell ID; BWP ID; PUCCH resources; PUCCH spatial relation ID; A set of PUCCH spatial relation IDs.

19. The wireless communication method according to any one of claims 12 to 18, further comprising: transmitting, to the wireless terminal in the target cell, an uplink grant for transmitting a radio resource control reconfiguration complete message by using a beam determined based on the beam mapping information, or The radio resource control reconfiguration complete message is received from the wireless terminal in the target cell to the radio network node by using the beam determined based on the beam mapping information.

20. The wireless communication method according to any one of claims 12 to 19, wherein: The beam mapping information includes a validity timer for the beam mapping information.

21. The wireless communication method according to any one of claims 12 to 20, further comprising: Prior to at least one of the following, communicating with a base station in the target cell using a beam determined based on the beam: Transmitting PUCCH spatial relation signaling to the wireless terminal in the target cell; Transmitting TCI status signaling to the wireless terminal in the target cell; The validity timer of the beam mapping information expires.

22. The wireless communication method according to claim 12, wherein: The context information includes at least one of the source distributed unit DUID of the wireless terminal in the source cell, the next generation base station distributed unit user equipment F1 application protocol identifier gNB-DU UE F1AP ID of the wireless terminal in the source DU, the special cell sPCell ID of the wireless terminal in the source cell, or a sharing indication.

23. The wireless communication method according to claim 22, wherein: The sharing instruction includes at least one of the following: Signaling radio bearer SRB sharing, indicating to reuse the SRB configuration of the wireless terminal in the source cell; Data radio bearer DRB sharing, indicating reuse of DRB information of the wireless terminal in the source cell; Full sharing, indicating reuse of the SRB configuration and the DRB information of the wireless terminal in the source cell; at least one SRB ID; At least one DRB ID.

24. The wireless communication method according to any one of claims 22 to 23, further comprising: Based on the context information, determining the beam mapping information, and / or For the wireless terminal in the target cell, at least part of the configuration information of the wireless terminal in the source cell is utilized based on the context information.

25. The wireless communication method according to any one of claims 12 to 24, wherein: The wireless terminal is a user equipment, the radio network node is a mobile integrated access and backhaul IAB node or a target IAB distributed unit, and the target network node is a target IAB host centralized unit.

26. A wireless communication method, applied to a target network node, the method comprising: A handover request is received from a source network node for the wireless terminal to handover from a source cell to a target cell.

27. The wireless communication method according to claim 26, wherein: The handover does not include a random access procedure.

28. The wireless communication method according to claim 26, wherein: The handover request includes context information associated with the wireless terminal in the source network node.

29. The wireless communication method according to claim 28, wherein: The context information includes at least one of ID information or a sharing indication.

30. The wireless communication method according to claim 29, wherein: The sharing instruction includes at least one of the following: Signaling radio bearer SRB sharing, indicating reuse of the SRB configuration of the wireless terminal in the source cell; Data radio bearer DRB sharing, indicating reuse of DRB information of the wireless terminal in the source cell; Full sharing, indicating reusing the SRB configuration and the DRB information of the wireless terminal in the source cell; At least one SRB ID; At least one DRB ID.

31. The wireless communication method according to any one of claims 26 to 30, wherein: The ID information includes at least one of the source distributed unit DUID of the wireless terminal in the source cell, the next generation base station DU user equipment F1 application protocol identifier gNB-DU UE F1AP ID of the wireless terminal in the source DU, or the special cell sPCell ID of the wireless terminal in the source cell.

32. The wireless communication method according to any one of claims 26 to 31, wherein: The wireless terminal is a user equipment, the target network node is a target IAB host centralized unit CU of the wireless terminal in the target cell, and the source network node is a source IAB host CU of the wireless terminal in the source cell.

33. A wireless terminal, comprising: a communication unit configured to receive beam mapping information for handover from a source cell to a target cell from a radio network node, and A processor is configured to perform switching by using a beam determined based on the beam mapping information.

34. The wireless terminal according to claim 33, wherein: The processor is further configured to execute the wireless communication method according to any one of claims 2 to 11.

35. A wireless network node, comprising: A communication unit, wherein the communication unit is configured to: receiving context information associated with the wireless terminal in the source cell from the target network node, and The beam mapping information of the wireless terminal in the target cell is transmitted to the target network node.

36. The radio network node according to claim 35, further comprising a processor, wherein the processor is configured to perform the wireless communication method according to any one of claims 13 to 25.

37. A target network node, comprising: A communication unit is configured to receive a handover request from a source network node for a wireless terminal to handover from a source cell to a target cell.

38. The target network node according to claim 37, further comprising a processor, wherein the processor is configured to execute the wireless communication method according to any one of claims 27 to 32.

39. A computer program product, comprising computer-readable program medium codes stored thereon, which, when executed by a processor, cause the processor to implement the wireless communication method according to any one of claims 1 to 32.

Images