WO2024103656A1 - Procédé de configuration de faisceau et appareil associé - Google Patents

Procédé de configuration de faisceau et appareil associé Download PDF

Info

Publication number
WO2024103656A1
WO2024103656A1 PCT/CN2023/094036 CN2023094036W WO2024103656A1 WO 2024103656 A1 WO2024103656 A1 WO 2024103656A1 CN 2023094036 W CN2023094036 W CN 2023094036W WO 2024103656 A1 WO2024103656 A1 WO 2024103656A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
source
cell
wireless terminal
wireless communication
Prior art date
Application number
PCT/CN2023/094036
Other languages
English (en)
Inventor
Lin Chen
Ying Huang
Youxiong Lu
Original Assignee
Zte Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zte Corporation filed Critical Zte Corporation
Priority to PCT/CN2023/094036 priority Critical patent/WO2024103656A1/fr
Publication of WO2024103656A1 publication Critical patent/WO2024103656A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/085—Reselecting an access point involving beams of access points

Definitions

  • This document is directed generally to wireless communications, and particular to 5G communications.
  • Radio Access Network RAN
  • CU Central Unit
  • DU Distributed Unit
  • RAN functions may 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, wherein DUs will handle all processes up to and including the RLC layer functions and the CU will handle PDCP layer and higher layer functions prior to the core network.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • the CU will be able to act as a Cloud-based convergence point among multiple heterogeneous technologies in the provisioned networks and hence will be able to serve multiple heterogeneous DUs.
  • IAB Integrated Access and Backhaul
  • cell sites e.g., base stations
  • IAB nodes the same infrastructure and resources (e.g., IAB nodes) can be used to provide both access and backhaul to support User Equipment (UE) Packet Data Unit (PDU) sessions, for example.
  • UE User Equipment
  • PDU Packet Data Unit
  • the IAB architecture for New Radio (NR) networks will provide wireless backhaul and relay links enabling flexible and dense deployment of NR cells without the need for densifying the transport network proportionately.
  • IAB technologies will allow for easier deployment of a dense network of self-backhauled NR cells in a more integrated and robust manner.
  • the IAB technology in the 5G NR network will support a multi-hop relay system, where the network topology also supports redundant connections.
  • FIG. 1 illustrates a block diagram of an IAB architecture network 100 wherein a core network 102 is connected to a donor IAB node 104.
  • the term “connected” refers to a wired or cabled 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.
  • the term “coupled” refers to direct or indirect and wired or wireless communications between two nodes or devices.
  • serving IAB nodes 106c and 106d are directly coupled to UEs 108a and 108b, respectively, and function as the serving cell site base stations or access points for the UEs 108a and 108b.
  • the UEs 108a and 108b are referred to herein as “access UEs. ”
  • the serving IAB nodes 106c and 106d also function as relay and can 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. As shown in FIG.
  • 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, which can then 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.
  • Each of the IAB nodes 106a-106d can have two functions: a base station (BS) function and a mobile terminal (MT) function.
  • the BS function means the IAB node can work like a base station to provide the radio access function for a UE.
  • the “BS part” of an IAB node refers to that portion of the IAB node, including all hardware, firmware and/or software related to performing the BS functions of the IAB node.
  • the MT function means the IAB node can work like a mobile terminal to be controlled and scheduled by the IAB donor node or an upper IAB node.
  • the “MT part” of an IAB node refers to that portion of the IAB node, including all hardware, firmware and/or software related to performing the MT functions of the IAB node.
  • the donor IAB node 104 would be replaced by a donor CU (not shown) connected to the core network 102 and a donor DU (not shown) connected to the donor CU.
  • Each of the IAB nodes 106a-106d would be coupled to the donor DU in similar fashion to their coupling to the donor IAB node 104, as shown in FIG. 1.
  • each of the IAB nodes 106a-106d can have two functions: a DU function and a mobile terminal (MT) function.
  • the DU function means the IAB node can work like a DU to provide the predetermined DU functions for a UE.
  • the “DU part” of an IAB node refers to that portion of the IAB node, including all hardware, firmware and/or software related to performing the DU functions of the IAB node.
  • the MT function and MT part of an IAB node in a split architecture network is the same as described above for a non-split architecture network.
  • the mobile IAB which focus on the scenario of mobile-IAB-nodes mounted on vehicles providing 5G coverage/capacity enhancement to onboard and/or surrounding UEs is proposed.
  • the mobile IAB can be used in outdoor environment to improve 5G coverage or connectivity, either following a certain known/predictable itinerary (e.g., buses, trams, etc. ) , or situated in convenient locations (e.g. outside stadiums, hot-spot areas, or emergency sites) .
  • the mobile IAB node provides connectivity for users or devices inside the vehicle itself and uses 5G wireless backhaul toward the macro network. It is assumed that the mobile IAB node may get a better macro coverage than a nearby UE, e.g., because exploiting better RF/antenna and power capabilities.
  • the implementation of the mobile IAB node in the 5G network raises many challenges.
  • One such challenge is that a group of UEs inside the vehicle may perform handovers along with the movements of the mobile IAB node. How to reduce the handover overhead and reduce random access collision needs to be investigated.
  • This document relates to methods, systems, and devices for beam configuration, and in particular to methods, systems, and devices for the beam configuration of UEs served by the mobile IAB node during a handover procedure.
  • the present disclosure relates to a wireless communication method for use in a wireless terminal.
  • the method comprises:
  • the handover comprises no random access procedure.
  • the beam mapping information comprises beam information to be used at target cell or a beam mapping between source beam information of the source cell and target beam information of the target cell.
  • the source beam information comprises at least one of following fields for the source cell: a serving cell identifier (ID) , a bandwidth part (BWP) ID, a resource set ID, a transmission configuration indicator (TCI) state ID, or a set of TCI state IDs.
  • ID serving cell identifier
  • BWP bandwidth part
  • TCI transmission configuration indicator
  • the beam information or the target beam information comprises at least one of following fields for the target cell: a serving cell ID, a BWP ID, a resource set ID, a TCI state ID, or a set of TCI state IDs.
  • the source beam information comprises at least one of following fields for the source cell: a serving cell ID, a BWP ID, a physical uplink control channel (PUCCH) resource ID, a PUCCH spatial relation ID, or a set of PUCCH spatial relation IDs.
  • a serving cell ID a serving cell ID
  • a BWP ID a physical uplink control channel (PUCCH) resource ID
  • PUCCH spatial relation ID a PUCCH spatial relation ID
  • set of PUCCH spatial relation IDs a set of PUCCH spatial relation IDs.
  • the beam information or the target beam information comprises at least one of following fields for the target cell: a serving cell ID, a BWP ID, a PUCCH resource ID, a PUCCH spatial relation ID, or a set of PUCCH spatial relation IDs.
  • performing the handover by using a beam determined based on the beam mapping information comprises at least one of:
  • the beam mapping information comprises a validity timer for the beam mapping information.
  • the wireless communication method further comprises utilizing the beam determined based on the beam mapping information to communicate with the wireless network node in the target cell before at least one of: receiving, from the wireless network node in the target cell, a PUCCH spatial relation signaling, receiving, from the wireless network node in the target cell, a TCI State signaling, completing an uplink beam training in the target cell, or validity timer for the beam mapping information expires.
  • the wireless terminal is a user equipment and/or the wireless network node is a mobile integrated access and backhaul (IAB) node, a source IAB donor, a source IAB donor centralized unit (CU) , a source IAB distributed unit (DU) , a target IAB donor CU, or a target IAB DU.
  • IAB mobile integrated access and backhaul
  • the present disclosure relates to a wireless communication method for use in a wireless network node.
  • the method comprises:
  • the wireless terminal is handed over from the source cell to the target cell without a random access procedure.
  • a handover of the wireless terminal from the source is performed and the handover comprises no random access procedure.
  • the beam mapping information comprises beam information to be used at target cell or a beam mapping between source beam information of the source cell and target beam information of the target cell.
  • the source beam information comprises at least one of following fields for the source cell: a serving cell identifier (ID) , a bandwidth part (BWP) ID, a resource set ID, a transmission configuration indicator (TCI) state ID, or a set of TCI state IDs.
  • ID serving cell identifier
  • BWP bandwidth part
  • TCI transmission configuration indicator
  • the beam information or the target beam information comprises at least one of following fields for the target cell: a serving cell ID, a BWP ID, a resource set ID, a TCI state ID, or a set of TCI state IDs.
  • the source beam information comprises at least one of following fields for the source cell: a serving cell ID, a BWP ID, a physical uplink control channel (PUCCH) resource ID, a PUCCH spatial relation ID, or a set of PUCCH spatial relation IDs.
  • a serving cell ID a serving cell ID
  • a BWP ID a physical uplink control channel (PUCCH) resource ID
  • PUCCH spatial relation ID a PUCCH spatial relation ID
  • set of PUCCH spatial relation IDs a set of PUCCH spatial relation IDs.
  • the beam information or the target beam information comprises at least one of following fields for the target cell: a serving cell ID, a BWP ID, a PUCCH resource ID, a PUCCH spatial relation ID, or a set of PUCCH spatial relation IDs.
  • the wireless communication method further comprises transmitting, to the wireless terminal in the target cell, an uplink grant for transmitting a radio resource control reconfiguration complete message by using the beam determined based on the beam mapping information.
  • the wireless communication method further comprises receiving, from the wireless terminal in the target cell, to the wireless network node, the radio resource control reconfiguration complete message by using the beam determined based on the beam mapping information.
  • the beam mapping information comprises a validity timer for the beam mapping information.
  • the wireless communication method further comprises utilizing the beam determined based on the beam to communicate with the base station in the target cell before at least one of: transmitting, to the wireless terminal in the target cell, a PUCCH spatial relation signaling, or transmitting, to the wireless terminal in the target cell, a TCI State signaling, or the validity timer for the beam mapping information expires.
  • the context information comprises at least one of a source distributed unit (DU) ID for the wireless terminal in the source cell, a gNB-DU UE F1AP ID for the wireless terminal in the source DU, a special cell (sPCell) ID for the wireless terminal in the source cell, or a sharing indication.
  • DU source distributed unit
  • gNB-DU UE F1AP ID for the wireless terminal in the source DU
  • sPCell special cell
  • the sharing indication includes at least one of: a signaling radio bearer (SRB) sharing which indicates reusing SRB configurations of the wireless terminal in the source cell, a data radio bearer (DRB) sharing which indicates reusing DRB information of the wireless terminal in the source cell, a full sharing which indicates reusing the SRB configurations and the DRB information of the wireless terminal in the source cell, at least one SRB ID, or at least one DRB ID.
  • SRB signaling radio bearer
  • DRB data radio bearer
  • the wireless communication method further comprises determining, based on the context information, the beam mapping information.
  • the wireless communication method further comprises utilizing, for the wireless terminal in the target cell, at least part of configuration information of the wireless terminal in the source cell based on the context information.
  • the wireless terminal is a user equipment and/or the wireless 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 donor centralized unit.
  • IAB mobile integrated access and backhaul
  • the present disclosure relates to a wireless communication method for use in a target network node.
  • the method comprising:
  • a source network node receiving, from a source network node, a handover request for a handover of a wireless terminal from a source cell to a target cell.
  • the handover comprises no random access procedure.
  • the handover request comprises context information associated with the wireless terminal in the source network node.
  • the context information comprises at least one of ID information or a sharing indication.
  • the sharing indication includes at least one of: a signaling radio bearer (SRB) sharing which indicates reusing SRB configurations of the wireless terminal in the source cell, a data radio bearer (DRB) sharing which indicates reusing DRB information of the wireless terminal in the source cell, a full sharing which indicates reusing the SRB configurations and the DRB information of the wireless terminal in the source cell, at least one SRB ID, or at least one DRB ID.
  • SRB signaling radio bearer
  • DRB data radio bearer
  • the ID information comprises at least one of a source distributed unit (DU) ID for the wireless terminal in the source cell, a gNB-DU UE F1AP ID for the wireless terminal in the source DU, or a special cell (sPCell) ID for the wireless terminal in the source cell.
  • DU source distributed unit
  • gNB-DU UE F1AP ID for the wireless terminal in the source DU
  • sPCell special cell
  • the wireless terminal is a user equipment
  • the target network node is a target IAB donor centralized unit (CU) for the wireless terminal in the target cell
  • the source network node is a source IAB donor CU for the wireless terminal in the source cell.
  • CU target IAB donor centralized unit
  • the present disclosure relates to a wireless communication method for use in a source network node.
  • the method comprises:
  • the handover request comprises identifier (ID) information associated with the wireless terminal.
  • ID identifier
  • the handover comprises no random access procedure.
  • the ID information comprises at least one of a source distributed unit (DU) ID for the wireless terminal in the source cell, a gNB-DU UE F1AP ID for the wireless terminal in the source DU, or a special cell (sPCell) ID for the wireless terminal in the source cell.
  • DU source distributed unit
  • gNB-DU UE F1AP ID for the wireless terminal in the source DU
  • sPCell special cell
  • the wireless terminal is a user equipment
  • the target network node is a target IAB donor centralized unit (CU) for the wireless terminal in the target cell
  • the source network node is a source IAB donor CU for the wireless terminal in the source cell.
  • CU target IAB donor centralized unit
  • the present disclosure relates to a wireless terminal.
  • the wireless terminal comprises:
  • a communication unit configured to receive, from a wireless network node, beam mapping information for a handover from a source cell to a target cell, and
  • a processor configured to perform the handover by using a beam determined based on the beam mapping information.
  • Various embodiments may preferably implement the following feature:
  • the processor is further configured to perform any of aforementioned wireless communication methods.
  • the present disclosure relates to a wireless network node.
  • the wireless network node comprises:
  • a communication unit configured to:
  • Various embodiments may preferably implement the following feature:
  • the wireless network node further comprises a processor configured to perform any of the aforementioned wireless communication methods.
  • the present disclosure relates to a target network node.
  • the target network node comprises:
  • a communication unit configured to receive, from a source network node, a handover request for a handover of a wireless terminal from a source cell to a target cell.
  • Various embodiments may preferably implement the following feature:
  • the target network node further comprises a processor configured to perform any of the aforementioned wireless communication methods.
  • the present disclosure relates to a computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement a wireless communication method recited in any one of foregoing methods.
  • the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, the specific order and/or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present disclosure. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present disclosure is not limited to the specific order or hierarchy presented unless expressly stated otherwise.
  • FIG. 1 shows a block diagram of an IAB architecture network.
  • FIG. 2 shows a schematic diagram of a mobile IAB scenario according to an embodiment of the present disclosure.
  • FIG. 3 shows a schematic diagram of a network (architecture) according to an embodiment of the present disclosure.
  • FIG. 4 shows a schematic diagram of a process according to an embodiment of the present disclosure.
  • FIG. 5 shows a schematic diagram of a process according to an embodiment of the present disclosure.
  • FIG. 6 shows a schematic diagram of a process according to an embodiment of the present disclosure.
  • FIG. 7 shows a schematic diagram of a process according to an embodiment of the present disclosure.
  • FIG. 8 shows an example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure.
  • FIG. 9 shows an example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure.
  • the mobile IAB node moves together with the vehicles, which may across a large area, as shown in FIG. 2.
  • mobile IAB may perform handover from one parent IAB node to another parent IAB node.
  • a group of UEs inside the vehicles served by the mobile IAB node may also perform HOs (handovers) .
  • RACH random access channel
  • a RACH-less HO i.e., HO without RACH procedure
  • the target donor CU may configure the UE to skip the RACH procedure during the handover procedure.
  • the UE and the target gNB performs an initial beam detection procedure via the RACH procedure/operation.
  • the UE may measure the detected SS/PBCH block and selects a PRACH resource which is associated with the SSB whose RSRP (reference signal received power) measurement result is greater than a threshold for subsequent transmission.
  • the gNB may determine the beam direction for the downlink transmission which is similar to the SSB associated with the PRACH resource.
  • the UE may assume that the DMRS (demodulation reference signal) antenna port associated with PDCCH (physical downlink control channel) receptions is quasi co-located with the SSB or the CSI-RS resource identified by the UE during the RACH procedure before the UE receives the MAC (media access control) CE (control element) activation command for one of the TCI (transmission configuration indicator) states.
  • DMRS demodulation reference signal
  • PDCCH physical downlink control channel
  • the mobile IAB node When it comes to the mobile IAB scenario, the mobile IAB node performs HO from a source DU to a target DU.
  • the onboard UEs need to perform the HOs along with the mobile IAB node.
  • the source cell and target cell actually belong to the same mobile IAB-DU.
  • the mobile IAB-DU can be regarded as a source logical DU and a target logical DU which connects to the source donor CU and target donor CU respectively as shown in FIG. 3.
  • the source cell and the target cell belong to the source logical DU and the target logical DU respectively.
  • the relative position between the UE and the source/target logical DU may not change during the HO procedure.
  • the target logical DU may be reconfigured with the different time/frequency resources by the target donor CU, the beam configuration (e.g. the TCI state, QCL and relevant RS (s) ) may be changed as well.
  • the beam configuration e.g. the TCI state, QCL and relevant RS (s)
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the two logical DU cells can be seen as different physical cells (i.e., separate source cell and target cell) .
  • the frequency, PCI (physical cell ID) and even the resources that can be used by the source and target cells may be configured differently. Under such condition, the cell-specific and UE specific beam management relevant configurations for the source cell may be largely different from those for the target cell.
  • the source logical DU and target logical DU are actually the same, it is possible for the two logical DUs to share a least part of the UE context and/or beam direction information for a given UE.
  • the source donor-CU may send UE ID information to the target donor-CU as shown in FIG. 4. Based on the UE ID information, the target donor CU can locate the UE at the target logical DU.
  • the UE ID information may include gNB-DU UE F1AP ID at the source logical-DU.
  • the at least one of the following information may be sent from the source donor-CU to the target donor-CU: sPcell (special cell) ID and/or DU ID.
  • the sPCell ID denotes the NCGI (NR Cell Global Identifier) of the source cell (s) that UE connects.
  • the DU ID denotes the ID of the source logical-DU.
  • the target donor CU may request the target logical DU to perform UE context setup and/or modification for the onboard UE.
  • the target donor CU may send at least one of the following information to target logical DU: gNB-DU UE F1AP ID, sPcell ID, old DU ID, a UE context sharing indication or a RACH skip indication as shown in FIG. 5.
  • the gNB-DU UE F1AP ID, sPcell ID, DU ID denotes the gNB-DU UE F1AP ID, the sPcell ID, the DU ID at the source logical DU respectively.
  • the UE context sharing indication may include at least one of: full sharing, SRB (signaling radio bearer) sharing, DRB (data radio bearer) sharing, or SRB/DRB ID (s) .
  • the full sharing means that all the SRBs and DRBs can reuse the configuration of the source logical DU.
  • the SRB sharing means that the RLC/MAC (radio link control/media access control) configuration of the SRB at the source logical DU can be reused.
  • the DRB sharing means that the DRB information, such as DRB QoS (quality of service) or the QoS flow to DRB mapping or the DL TNL (Transport Network Layer) information may not change and/or that the previous DRB configuration at the source donor CU/logical DU can be reused.
  • the SRB/DRB ID (s) means that, for the given SRB/DRB, the previous configuration at source logical DU/CU can be reused. It should be noted that for the DRB configuration sharing, the target donor CU may at least update the UL UP (user plane) TNL information for the DRB.
  • the target logical DU may retrieve the UE’s context at the source logical DU and then reuse the RLC/MAC/logical channel configuration of this DRB for the target logical DU.
  • the target donor CU does not need to send the DRB QoS information, QoS flow (s) to DRB mapping info to the target logical DU.
  • Target logical DU may reuse the previous received DRB QoS information and the QoS flow (s) to DRB mapping info stored at the source logical DU.
  • the target donor CU may decide whether the RACH procedure may be skipped for the UE during the HO preparation phase.
  • the target donor CU may send the RACH skip indication to the target logical DU.
  • the target logical DU configures beam information for the UE which reuses the beam configuration at the source logical DU as much as possible.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • FIG. 6 shows a schematic diagram of a process according to an embodiment of the present disclosure.
  • the target logical DU may decide that the onboard UE may skip the RACH procedure at the target cell when/if the onboard UE performs the HO. If the target logical DU received the IAB-DU Cell Resource Configuration from the donor CU, the target logical DU may try to configure the same SSB/CSI-RS/SRS and/or configure at least one of the TCI (Transmission configuration indication) state, the QCL type and the SRS spatial relation information as the source logical DU.
  • TCI Transmission configuration indication
  • the target logical DU may be able to configure the same RS and/or the same TCI state and/or the same spatial relation configuration
  • the target logical DU may indicate the target donor CU that the same beam configuration can be used.
  • the same beam configuration can be delivered from the target donor CU to the source donor CU.
  • source CU may send the same beam indication to the UE, e.g., via RRCReconfiguration with a synchronization (i.e., sync) message, to trigger the RACH-less HO at the UE side.
  • the IAB-DU Cell Resource Configuration from target donor CU may be different from the one received from source donor CU, the target logical DU cannot guarantee that the completely same beam relevant configuration can be used.
  • the target logical DU may configure a new set of SSB/CSI-RS/SRS.
  • the number and index for these reference signalings may also be different from those for the source logical DU.
  • the target logical DU may derive the SSB/CSI-RS/SRS configuration mapping between (the number and index of) the reference signaling for the source logical DU and (the number and index of) the reference signaling for the target logical DU.
  • the source donor CU may send the beam mapping information to UE via RRCReconfiguration with sync (synchronization) message.
  • the UE may use the beam mapping information to determine the beam to be used at the target cell.
  • the target logical DU may transmit the determined configuration mapping to the target donor CU and the target donor CU transmits the received configuration mapping to the source donor CU.
  • the target logical IAB DU may generate the one or more mappings between beam information of the source logical DU and the beam information of the target logical DU.
  • the beam information of the source logical DU may include at least one of: a (source) serving cell ID, a (source) BWP ID, a ControlResourceSetId, a (source) TCI state Id or a set of (source) TCI state Ids.
  • the beam information of the target logical DU may include at least one of: a (target) serving cell ID, a (target) BWP ID, a ControlResourceSetId, a (target) TCI state Id or a set of (target) TCI state Ids.
  • the beam information of the source logical DU may include any combination of the following fields: a (source) serving cell ID, a (source) BWP ID, a (source) PUCCH Resource ID, a (source) PUCCH Spatial Relation ID or a set of (source) PUCCH Spatial Relation IDs.
  • the beam information of the target logical DU may include any combination of the following fields: a target serving cell ID, a target BWP ID, a target PUCCH Resource ID, a target PUCCH Spatial Relation ID or a set of target PUCCH Spatial Relation IDs.
  • the UE may determine the Rx (reception) beam at the target cell based on the received beam mapping information.
  • 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, BWP1 and TCI state ID 3) .
  • the UE may utilize the (target cell 1, BWP1 and TCI state ID 3) for PDCCH monitoring initially.
  • the UE may synchronize with the target cell and receive the UL grant for RRCReconfigurationcomplete message transmission. The UE may continue utilizing the mapped beam until/before the UE receives the PUCCH spatial relation Activation/Deactivation MAC CE and/or TCI States Activation/Deactivation MAC CE from the target cell.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • FIG. 7 shows a schematic diagram of a process according to an embodiment of the present disclosure.
  • the UE receives the beam mapping information and pre-allocated/assigned UL grant of the target cell, e.g., in the RRCReconfiguration with sync message.
  • the UE may synchronize to the target cell and the UE may use the same beam direction of the source cell to transmit the RRCReconfigurationComplete message to target cell.
  • the beam direction information of the source cell can be used until the UE finishes/completes UL beam training at the target cell and/or selects a suitable Tx beam.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • the target logical DU determines a list of activated TCI states or PUCCH spatial relation to be used by the UE at the target cell.
  • the target logical DU may configure a list of activated TCI states or PUCCH spatial relation and an associated validity timer for the UE.
  • the target logical DU delivers this information to the source donor CU and the source donor CU delivers this information to the UE via the RRCReconfiguration with sync message.
  • the UE Upon receiving these activated TCI state or PUCCH spatial relation information, the UE utilizes this information for DL monitoring at the target cell and starts the validity timer. When the validity timer expires, the list of activated TCI states or PUCCH spatial relation is no longer valid.
  • FIG. 8 relates to a schematic diagram of a wireless terminal 80 according to an embodiment of the present disclosure.
  • the wireless terminal 80 may be a user equipment (UE) , a mobile phone, a laptop, a tablet computer, an electronic book or a portable computer system and is not limited herein.
  • the wireless terminal 80 may include a processor 800 such as a microprocessor or 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, which is accessed and executed by the processor 800.
  • Embodiments of the storage unit 810 include but are not limited to a subscriber identity module (SIM) , read-only memory (ROM) , flash memory, random-access memory (RAM) , hard-disk, and optical data storage device.
  • SIM subscriber identity module
  • ROM read-only memory
  • RAM random-access memory
  • the communication unit 820 may a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to processing results of the processor 800. In an embodiment, the communication unit 820 transmits and receives the signals via at least one antenna 822 shown in FIG. 8.
  • 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.
  • the processor 800 may implement any one of the steps in exemplified embodiments on the wireless terminal 80, e.g., by executing the program code 812.
  • the communication unit 820 may be a transceiver.
  • the communication unit 820 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals to and from a wireless network node (e.g., a base station) .
  • a wireless network node e.g., a base station
  • FIG. 9 relates to a schematic diagram of a wireless network node 90 according to an embodiment of the present disclosure.
  • the wireless network node 90 may be a satellite, a base station (BS) , a network entity, a Mobility Management Entity (MME) , Serving Gateway (S-GW) , 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 herein.
  • BS base station
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • PDN Packet Data Network Gateway
  • RAN radio access network
  • NG-RAN next generation RAN
  • gNB next generation RAN
  • gNB next generation RAN
  • the wireless network node 90 may comprise (perform) at least one network function such as an access and mobility management function (AMF) , a session management function (SMF) , a user place 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 ASIC, a storage unit 910 and a communication unit 920.
  • the storage unit 910 may be any data storage device that stores a program code 912, which is accessed and executed by the processor 900. Examples of the storage unit 910 include but are not limited to a SIM, ROM, flash memory, RAM, hard-disk, and optical data storage device.
  • the communication unit 920 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to processing results of the processor 900.
  • the communication unit 920 transmits and receives the signals via at least one antenna 922 shown in FIG. 9.
  • the storage unit 910 and the program code 912 may be omitted.
  • the processor 900 may include a storage unit with stored program code.
  • the processor 900 may implement any steps described in exemplified embodiments on the wireless network node 90, e.g., via executing the program code 912.
  • the communication unit 920 may be a transceiver.
  • the communication unit 920 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals to and from a wireless terminal (e.g., a user equipment or another wireless network node) .
  • a wireless terminal e.g., a user equipment or another wireless network node
  • any reference to an element herein using a designation such as “first, ” “second, ” and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
  • any one of the various illustrative logical blocks, units, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as “software” or a “software unit” ) , or any combination of these techniques.
  • a processor, device, component, circuit, structure, machine, unit, etc. can be configured to perform one or more of the functions described herein.
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, units, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein. If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
  • a storage media can be any available media that can be accessed by a computer.
  • such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • unit refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various units are described as discrete units; however, as would be apparent to one of ordinary skill in the art, two or more units may be combined to form a single unit that performs the associated functions according to embodiments of the present disclosure.
  • memory or other storage may be employed in embodiments of the present disclosure.
  • memory or other storage may be employed in embodiments of the present disclosure.
  • any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present disclosure.
  • functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
  • references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Est divulgué un procédé de communication sans fil destiné à être utilisé dans un terminal sans fil. Le procédé consiste à recevoir, en provenance d'un nœud de réseau sans fil, des informations de mappage de faisceau pour un transfert intercellulaire depuis une cellule source vers une cellule cible, et à effectuer le transfert intercellulaire à l'aide d'un faisceau déterminé en fonction des informations de mappage de faisceau.
PCT/CN2023/094036 2023-05-12 2023-05-12 Procédé de configuration de faisceau et appareil associé WO2024103656A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/094036 WO2024103656A1 (fr) 2023-05-12 2023-05-12 Procédé de configuration de faisceau et appareil associé

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/094036 WO2024103656A1 (fr) 2023-05-12 2023-05-12 Procédé de configuration de faisceau et appareil associé

Publications (1)

Publication Number Publication Date
WO2024103656A1 true WO2024103656A1 (fr) 2024-05-23

Family

ID=91083737

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/094036 WO2024103656A1 (fr) 2023-05-12 2023-05-12 Procédé de configuration de faisceau et appareil associé

Country Status (1)

Country Link
WO (1) WO2024103656A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220182905A1 (en) * 2019-01-29 2022-06-09 Nokia Solutions And Networks Oy Method, device and computer readable medium for centralized unit switch
US20220191755A1 (en) * 2019-03-28 2022-06-16 Telefonaktiebolaget Lm Ericsson (Publ) Optional Sending of Complete Message in Conditional Handover
CN115104373A (zh) * 2020-02-21 2022-09-23 高通股份有限公司 物理随机接入信道重复和接收波束扫描和关联的波束细化
US20230007701A1 (en) * 2021-06-30 2023-01-05 Nokia Technologies Oy Methods and apparatuses for avoiding radio link control (rlc) context fetch in small data transmission (sdt)
EP4175359A1 (fr) * 2020-06-28 2023-05-03 ZTE Corporation Procédé de gestion de ressources et dispositif de réseau

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220182905A1 (en) * 2019-01-29 2022-06-09 Nokia Solutions And Networks Oy Method, device and computer readable medium for centralized unit switch
US20220191755A1 (en) * 2019-03-28 2022-06-16 Telefonaktiebolaget Lm Ericsson (Publ) Optional Sending of Complete Message in Conditional Handover
CN115104373A (zh) * 2020-02-21 2022-09-23 高通股份有限公司 物理随机接入信道重复和接收波束扫描和关联的波束细化
EP4175359A1 (fr) * 2020-06-28 2023-05-03 ZTE Corporation Procédé de gestion de ressources et dispositif de réseau
US20230007701A1 (en) * 2021-06-30 2023-01-05 Nokia Technologies Oy Methods and apparatuses for avoiding radio link control (rlc) context fetch in small data transmission (sdt)

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "discussion on Inter-Donor IAB Node Migration", 3GPP TSG-RAN WG3 MEETING #109-E R3-205264, 7 August 2020 (2020-08-07), XP051915930 *

Similar Documents

Publication Publication Date Title
US11323942B2 (en) Handover method and apparatus
US20230097891A1 (en) System and method for mobility enhancements
USRE47613E1 (en) System and method for primary point handovers
CN109076383B (zh) 用于由终端配置双连接的方法及其装置
US11627509B2 (en) Telecommunications system, terminal device, infrastructure equipment and methods
WO2021097801A1 (fr) Procédés et appareil de routage de paquet pour un relais de liaison latérale
US9992815B2 (en) Method of performing handover procedure, making handover decision for device-to-device communications and control node thereof
US20190349819A1 (en) Method and apparatus for supporting beam in wireless communication system
US10405344B2 (en) Zone-based homing and scheduling for centralized radio access network (C-RAN) system with a cluster of baseband units
CN110463240B (zh) 电信设备和方法
WO2021213436A1 (fr) Commutation de chemin pour relais ue-à-réseau de couche 3
WO2022082601A1 (fr) Procédé et appareil de mobilité entre donneurs
EP3603144A1 (fr) Appareil et procédés de télécommunications sans fil
US20220182905A1 (en) Method, device and computer readable medium for centralized unit switch
CN115398975A (zh) 用于侧链路中继通信的信令传输的系统和方法
JP2024503709A (ja) データ伝送方法及び装置
EP4055875A1 (fr) Rapport basé sur un seuil à des fins de prise en charge de commande d'admission efficace de réseaux sans fil
CN115152277A (zh) 提供网络切片的方法和通信装置
US20240040463A1 (en) Integrated access and backhaul node
WO2024103656A1 (fr) Procédé de configuration de faisceau et appareil associé
US20210337441A1 (en) Mobility interruption reduction in multi-rat dual-connectivity (mr-dc)
CN113261340B (zh) 传输信息的方法、终端设备、基站和核心网设备
WO2024077600A1 (fr) Systèmes et procédés pour des communications de dispositif à dispositif
WO2023070511A1 (fr) Amélioration sur un réseau de liaison terrestre et d'accès intégré
WO2023108354A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau