WO2024031244A1 - Transfert de groupe et prévention de collision de pci dans un scénario iab mobile - Google Patents

Transfert de groupe et prévention de collision de pci dans un scénario iab mobile Download PDF

Info

Publication number
WO2024031244A1
WO2024031244A1 PCT/CN2022/110881 CN2022110881W WO2024031244A1 WO 2024031244 A1 WO2024031244 A1 WO 2024031244A1 CN 2022110881 W CN2022110881 W CN 2022110881W WO 2024031244 A1 WO2024031244 A1 WO 2024031244A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
donor
group
pci
iab donor
Prior art date
Application number
PCT/CN2022/110881
Other languages
English (en)
Inventor
Peng Cheng
Fangli Xu
Ralf ROSSBACH
Naveen Kumar R. PALLE VENKATA
Alexander Sirotkin
Yuqin Chen
Haijing Hu
Original Assignee
Apple Inc.
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 Apple Inc. filed Critical Apple Inc.
Priority to PCT/CN2022/110881 priority Critical patent/WO2024031244A1/fr
Publication of WO2024031244A1 publication Critical patent/WO2024031244A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0009—Control or signalling for completing the hand-off for a plurality of users or terminals, e.g. group communication or moving wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/32—Hierarchical cell structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/0085—Hand-off measurements

Definitions

  • This application relates generally to wireless communication systems, including devices, systems and methods for group handover and Physical Cell Identifier (PCI) collision prevention in a mobile Integrated Access and Backhaul (IAB) scenario.
  • PCI Physical Cell Identifier
  • Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless communication device.
  • Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., 4G) , 3GPP new radio (NR) (e.g., 5G) , and IEEE 802.11 standard for wireless local area networks (WLAN) (commonly known to industry groups as ) .
  • 3GPP 3rd Generation Partnership Project
  • LTE long term evolution
  • NR 3GPP new radio
  • WLAN wireless local area networks
  • 3GPP radio access networks
  • RANs can include, for example, global system for mobile communications (GSM) , enhanced data rates for GSM evolution (EDGE) RAN (GERAN) , Universal Terrestrial Radio Access Network (UTRAN) , Evolved Universal Terrestrial Radio Access Network (E-UTRAN) , and/or Next-Generation Radio Access Network (NG-RAN) .
  • GSM global system for mobile communications
  • EDGE enhanced data rates for GSM evolution
  • GERAN GERAN
  • UTRAN Universal Terrestrial Radio Access Network
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • NG-RAN Next-Generation Radio Access Network
  • Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE.
  • RATs radio access technologies
  • the GERAN implements GSM and/or EDGE RAT
  • the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT
  • the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE)
  • NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR)
  • the E-UTRAN may also implement NR RAT.
  • NG-RAN may also implement LTE RAT.
  • a base station used by a RAN may correspond to that RAN.
  • E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) .
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • eNodeB enhanced Node B
  • NG-RAN base station is a next generation Node B (also sometimes referred to as a or g Node B or gNB) .
  • a RAN provides its communication services with external entities through its connection to a core network (CN) .
  • CN core network
  • E-UTRAN may utilize an Evolved Packet Core (EPC)
  • EPC Evolved Packet Core
  • NG-RAN may utilize a 5G Core Network (5GC) .
  • EPC Evolved Packet Core
  • 5GC 5G Core Network
  • Frequency bands for 5G NR may be separated into two or more different frequency ranges.
  • Frequency Range 1 may include frequency bands operating in sub-6 GHz frequencies, some of which are bands that may be used by previous standards, and may potentially be extended to cover new spectrum offerings from 410 MHz to 7125 MHz.
  • Frequency Range 2 may include frequency bands from 24.25 GHz to 52.6 GHz. Bands in the millimeter wave (mmWave) range of FR2 may have smaller coverage but potentially higher available bandwidth than bands in the FR1. Skilled persons will recognize these frequency ranges, which are provided by way of example, may change from time to time or from region to region.
  • mmWave millimeter wave
  • Embodiments are presented herein of devices, systems, and methods for several critical issues in a scenario including a mobile Integrated Access and Backhaul (IAB) node.
  • the present disclosure is mainly directed to user equipment (UE) group handover and PCI collision prevention in such a scenario.
  • UE user equipment
  • a UE may be configured to receive, from a source IAB donor, a reconfiguration message associated with group handover.
  • This reconfiguration message may indicate an identifier of a UE group including one or more UEs served by a migration IAB node and multiple security key change rules, wherein said UE belongs to the UE group, and wherein the migration IAB node performs an inter-donor switch from the source IAB donor to a target IAB donor and serves said UE.
  • the UE may be further configured to receive, from the migration IAB node, a triggering message for group handover.
  • This triggering message indicating said identifier of the UE group and a determined security key change rule corresponding to the UE group, wherein the determined security key change rule is included in the multiple security key change rules.
  • the UE may be configured to perform a group handover from the source IAB donor to the target IAB donor, based on the determined security key change rule corresponding to the UE group.
  • a UE may be configured to receive, from a source IAB donor, a reconfiguration message associated with PCI collision prevention.
  • This reconfiguration message associated with PCI collision prevention may indicate one of (i) and (ii) : (i) a measurement of PCIs of one or more neighbor cells for the UE and a timer to indicate how long the UE performs the measurement for the PCIs of the one or more neighbor cells; and (ii) a detection of PCI collision between a serving cell for the UE and one or more neighbor cells for the UE.
  • each cell may include an IAB node, and the reconfiguration message associated with PCI collision prevention may be used for avoiding PCI collisions when the UE performs a handover from the source IAB donor to a target IAB donor.
  • the techniques described herein may be implemented in and/or used with a number of different types of devices, including but not limited to cellular phones, tablet computers, wearable computing devices, portable media players, and any of various other computing devices.
  • FIG. 1 illustrates an example architecture of a wireless communication system, according to embodiments disclosed herein.
  • FIG. 2 illustrates a system for performing signaling between a wireless device and a network device, according to embodiments disclosed herein.
  • FIG. 3 illustrates an example IAB network, according to embodiments disclosed herein.
  • FIG. 4 illustrates an example IAB network and its components, according to embodiments disclosed herein.
  • FIG. 5A and FIG. 5B are flowchart diagrams illustrating an example method for supporting group handover in mobile IAB node scenario, according to embodiments disclosed herein.
  • FIG. 6A and FIG. 6B are flowchart diagrams illustrating an example method for supporting PCI collision prevention in mobile IAB node scenario, according to embodiments disclosed herein.
  • FIG. 7 illustrates an example signaling diagram between a UE and network-side devices, according to embodiments disclosed herein.
  • a UE Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and/or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.
  • FIG. 1 illustrates an example architecture of a wireless communication system 100, according to embodiments disclosed herein.
  • the following description is provided for an example wireless communication system 100 that operates in conjunction with the LTE system standards and/or 5G or NR system standards as provided by 3GPP technical specifications.
  • the wireless communication system 100 includes UE 102 and UE 104 (although any number of UEs may be used) .
  • the UE 102 and the UE 104 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) , but may also comprise any mobile or non-mobile computing device configured for wireless communication.
  • the UE 102 and UE 104 may be configured to communicatively couple with a RAN 106.
  • the RAN 106 may be NG-RAN, E-UTRAN, etc.
  • the UE 102 and UE 104 utilize connections (or channels) (shown as connection 108 and connection 110, respectively) with the RAN 106, each of which comprises a physical communications interface.
  • the RAN 106 can include one or more base stations, such as base station 112 and base station 114, that enable the connection 108 and connection 110.
  • connection 108 and connection 110 are air interfaces to enable such communicative coupling, and may be consistent with RAT (s) used by the RAN 106, such as, for example, an LTE and/or NR.
  • the UE 102 and UE 104 may also directly exchange communication data via a sidelink interface 116.
  • the UE 104 is shown to be configured to access an access point (shown as AP 118) via connection 120.
  • the connection 120 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 118 may comprise a router.
  • the AP 118 may be connected to another network (for example, the Internet) without going through a CN 124.
  • the UE 102 and UE 104 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 112 and/or the base station 114 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications) , although the scope of the embodiments is not limited in this respect.
  • OFDM signals can comprise a plurality of orthogonal subcarriers.
  • the base station 112 or base station 114 may be implemented as one or more software entities running on server computers as part of a virtual network.
  • the base station 112 or base station 114 may be configured to communicate with one another via interface 122.
  • the interface 122 may be an X2 interface.
  • the X2 interface may be defined between two or more base stations (e.g., two or more eNBs and the like) that connect to an EPC, and/or between two eNBs connecting to the EPC.
  • the interface 122 may be an Xn interface.
  • the Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station 112 (e.g., a gNB) connecting to 5GC and an eNB, and/or between two eNBs connecting to 5GC (e.g., CN 124) .
  • the RAN 106 is shown to be communicatively coupled to the CN 124.
  • the CN 124 may comprise one or more network elements 126, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UE 102 and UE 104) who are connected to the CN 124 via the RAN 106.
  • the components of the CN 124 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) .
  • the CN 124 may be an EPC, and the RAN 106 may be connected with the CN 124 via an S1 interface 128.
  • the S1 interface 128 may be split into two parts, an S1 user plane (S1-U) interface, which carries traffic data between the base station 112 or base station 114 and a serving gateway (S-GW) , and the S1-MME interface, which is a signaling interface between the base station 112 or base station 114 and mobility management entities (MMEs) .
  • S1-U S1 user plane
  • S-GW serving gateway
  • MMEs mobility management entities
  • the CN 124 may be a 5GC, and the RAN 106 may be connected with the CN 124 via an NG interface 128.
  • the NG interface 128 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 112 or base station 114 and a user plane function (UPF) , and the S1 control plane (NG-C) interface, which is a signaling interface between the base station 112 or base station 114 and access and mobility management functions (AMFs) .
  • NG-U NG user plane
  • UPF user plane function
  • S1 control plane S1 control plane
  • AMFs access and mobility management functions
  • an application server 130 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 124 (e.g., packet switched data services) .
  • IP internet protocol
  • the application server 130 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc. ) for the UE 102 and UE 104 via the CN 124.
  • the application server 130 may communicate with the CN 124 through an IP communications interface 132.
  • FIG. 2 illustrates a system 200 for performing signaling 234 between a wireless device 202 and a network device 218, according to embodiments disclosed herein.
  • the system 200 may be a portion of a wireless communications system as herein described.
  • the wireless device 202 may be, for example, a UE of a wireless communication system.
  • the network device 218 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.
  • the wireless device 202 may include one or more processor (s) 204.
  • the processor (s) 204 may execute instructions such that various operations of the wireless device 202 are performed, as described herein.
  • the processor (s) 204 may include one or more baseband processors implemented using, for example, a central processing unit (CPU) , a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the wireless device 202 may include a memory 206.
  • the memory 206 may be a non-transitory computer-readable storage medium that stores instructions 208 (which may include, for example, the instructions being executed by the processor (s) 204) .
  • the instructions 208 may also be referred to as program code or a computer program.
  • the memory 206 may also store data used by, and results computed by, the processor (s) 204.
  • the wireless device 202 may include one or more transceiver (s) 210 that may include radio frequency (RF) transmitter and/or receiver circuitry that use the antenna (s) 212 of the wireless device 202 to facilitate signaling (e.g., the signaling 234) to and/or from the wireless device 202 with other devices (e.g., the network device 218) according to corresponding RATs.
  • RF radio frequency
  • the wireless device 202 may include one or more antenna (s) 212 (e.g., one, two, four, or more) .
  • the wireless device 202 may leverage the spatial diversity of such multiple antenna (s) 212 to send and/or receive multiple different data streams on the same time and frequency resources.
  • This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect) .
  • MIMO multiple input multiple output
  • MIMO transmissions by the wireless device 202 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 202 that multiplexes the data streams across the antenna (s) 212 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream) .
  • Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and/or multi user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain) .
  • SU-MIMO single user MIMO
  • MU-MIMO multi user MIMO
  • the wireless device 202 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna (s) 212 are relatively adjusted such that the (joint) transmission of the antenna (s) 212 can be directed (this is sometimes referred to as beam steering) .
  • the wireless device 202 may include one or more interface (s) 214.
  • the interface (s) 214 may be used to provide input to or output from the wireless device 202.
  • a wireless device 202 that is a UE may include interface (s) 214 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and/or output to the UE by a user of the UE.
  • Other interfaces of such a UE may be made up of made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 210/antenna (s) 212 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., and the like) .
  • the network device 218 may include one or more processor (s) 220.
  • the processor (s) 220 may execute instructions such that various operations of the network device 218 are performed, as described herein.
  • the processor (s) 204 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
  • the network device 218 may include a memory 222.
  • the memory 222 may be a non-transitory computer-readable storage medium that stores instructions 224 (which may include, for example, the instructions being executed by the processor (s) 220) .
  • the instructions 224 may also be referred to as program code or a computer program.
  • the memory 222 may also store data used by, and results computed by, the processor (s) 220.
  • the network device 218 may include one or more transceiver (s) 226 that may include RF transmitter and/or receiver circuitry that use the antenna (s) 228 of the network device 218 to facilitate signaling (e.g., the signaling 234) to and/or from the network device 218 with other devices (e.g., the wireless device 202) according to corresponding RATs.
  • transceiver s
  • RF transmitter and/or receiver circuitry that use the antenna (s) 228 of the network device 218 to facilitate signaling (e.g., the signaling 234) to and/or from the network device 218 with other devices (e.g., the wireless device 202) according to corresponding RATs.
  • the network device 218 may include one or more antenna (s) 228 (e.g., one, two, four, or more) .
  • the network device 218 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.
  • the network device 218 may include one or more interface (s) 230.
  • the interface (s) 230 may be used to provide input to or output from the network device 218.
  • a network device 218 that is a base station may include interface (s) 230 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 226/antenna (s) 228 already described) that enables the base station to communicate with other equipment in a core network, and/or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.
  • circuitry e.g., other than the transceiver (s) 226/antenna (s) 228 already described
  • ⁇ BS Base Station
  • ⁇ CU Central Unit
  • ⁇ DU Distributed Unit
  • ⁇ MAC Medium Access Control
  • NCGI NR Cell Global Identifier
  • ⁇ RF Radio Frequency
  • ⁇ RNTI Radio Network Temporary Identity
  • ⁇ UE User Equipment
  • NR cell is likely to use a higher frequency than a legacy cell (such as an LTE cell) . It becomes difficult to deploy a large number of network devices (such as gNBs) to provide a good and wide coverage with small cell radius. In such case, an IAB network naturally becomes a good solution.
  • gNBs network devices
  • FIG. 3 illustrates an example IAB network, according to embodiments disclosed herein.
  • an IAB network may include one or more IAB donors (such as IAB donor 1 and IAB donor 2) and one or more IAB nodes (such as IAB node 1, IAB node 2 and IAB node 3) .
  • IAB donor and the IAB node may be collectively referred to as “IAB device” throughout the present disclosure, which belongs to network devices 218.
  • the IAB donor may perform functions to manage and control the IAB nodes.
  • the IAB node may comprise L2 relay node, etc.
  • multiple IAB donors may be connected via wired links, and they may be configured to communicate with a network (e.g., a cellular service provider’s core network, a telecommunications network such as a public switched telephone network (PSTN) , and/or Internet, etc. ) via a wired medium (e.g., cable, fiber, etc. ) .
  • An IAB node may connect to its parent IAB node (also called upstream IAB node, which is closer to the IAB donor) or its child IAB node (also called downstream IAB node, which is farther to the IAB donor) or an IAB donor via wireless backhaul links.
  • Each IAB donor or IAB node may serve and connect to one or more wireless devices (such as UE) via wireless access links, thus facilitating communications between multiple wireless devices and/or communications between wireless devices and the network.
  • an IAB device may operate in accordance with one or more wireless communication technologies to provide continuous or nearly continuous Radio signal coverage.
  • the coverage area of an IAB device is generally referred to as a cell.
  • Cells of different IAB devices may have different sizes.
  • an IAB donor may be in a macro cell, while an IAB node may be in a small cell.
  • the IAB network in FIG. 3 is merely exemplary and not intended to be limiting.
  • the IAB network may include more or less devices in practice.
  • the IAB network according to the present disclosure may be applicable to FR1 and FR2, and the IAB node may support in-band and out-of-band backhauling.
  • IAB node In an existing IAB network, an IAB node is normally assumed to be static. However, new scenarios for IAB network including mobile IAB node (s) are attracting more and more attentions from both of industry and academic field. According to aspects of the present disclosure, all or part of IAB nodes may be movable. For example, IAB node 3 and all or part of its served UEs may be located on a vehicle (e.g., a car, a bus, an airplane, a ship, a train, a high-speed rail, etc. ) , thus they are movable. In order to enable IAB node mobility, a migration procedure for the entire mobile IAB node (also referred to as “migration IAB node” herein) is required to be considered. Related issues will be introduced and discussed in connection with FIG. 4 hereinafter.
  • migration IAB node also referred to as “migration IAB node” herein
  • FIG. 4 illustrates an example IAB network and its components associated with a migration IAB node.
  • an IAB donor may include a Central Unit (CU) and a Distributed Units (DU) (sometimes the IAB donor may include multiple DUs) .
  • the CU of the IAB donor may provide control for the IAB network, and it may perform higher layer (such as Radio Resource Control (RRC) layer) functions.
  • the DU of the IAB donor may perform scheduling for communication resources for downstream IAB nodes or served UEs for that IAB donor, and it may perform lower layer (such as Radio Link Control (RLC) layer or Medium Access Control (MAC) layer) functions.
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • the CUs of different IAB donors are different. That is, the CU of IAB donor 1 (CU1) is different from the CU of IAB donor 2 (CU2) , and they could be connected via a wired link.
  • An IAB node may include a Mobile Terminal (MT) and a Distributed Unit (DU) .
  • the MT and the DU of one IAB node may be logically separated.
  • the MT of the IAB node may operate as a scheduled node by a parent IAB node of that IAB node or an IAB donor, which functions similar to a UE.
  • the DU of the IAB node may schedule a child IAB node and served UEs of that IAB node.
  • a migration procedure of a portion of an IAB node may happen when there is a heavy load on the IAB donor that controls that IAB node.
  • This migration procedure is referred to as “Partial Migration” (or more specifically, “Inter-Donor Partial Migration” ) herein.
  • Inter-Donor Partial Migration is only supported for Standalone (SA) -mode.
  • the MT of an IAB node may migrate to a different parent node underneath another IAB donor CU, while the collocated DU of the same IAB node and its downstream IAB nodes may still retain F1 connectivity to initial IAB donor CU.
  • IAB donor 1 is the source IAB donor
  • IAB donor 2 is the target IAB donor
  • MT3 performs an inter-donor switch from the CU of IAB donor (CU1) to the CU of IAB donor 2 (CU2) (as mentioned above, CU1 is different from CU2) , while DU3 and its served UEs (e.g., UE1 and UE2) do not change.
  • the F1 traffic of DU3 (and its served UEs) is routed via Backhaul Adaptation Protocol (BAP) layer to which the MT3 has migrated, but finally the F1 traffic will be routed to CU1.
  • BAP Backhaul Adaptation Protocol
  • the DU of IAB node 3 (DU3) and its served one or more UEs are still controlled by the CU of source IAB donor (CU1) after Inter-Donor Partial Migration, thus there are no handover operations for DU3 and its served one or more UEs in such case.
  • an IAB network involving IAB mobility is considered, where one or more IAB nodes and their connected UEs may be movable.
  • a mobile IAB node does not have child IAB nodes and only serves UEs, and it could be referred to as a boundary IAB node in the present disclosure.
  • the migration procedure of the mobile IAB node may involve the migration of the entire IAB node, including the migration of both of its MT and DU. This migration procedure is referred to as “Full Migration” (or more specifically, “Inter-Donor Full Migration” ) herein.
  • the MT of an IAB node and the DU of the same IAB node may perform inter-donor switch from the source IAB donor to the target IAB donor.
  • IAB donor 1 is the source IAB donor
  • IAB donor 2 is the target IAB donor
  • both of MT3 and DU3 perform an inter-donor switch from the CU of IAB donor (CU1) to the CU of IAB donor 2 (CU2) (as mentioned above, CU1 is different from CU2) .
  • DU3 is controlled by CU2.
  • the DU of IAB node 3 may serve a group of UEs (e.g., UE1 and UE2) , this group of UEs are required to perform handover from IAB donor 1 to IAB donor 2 after Inter-Donor Full Migration. In such case, two critical issues should be considered and discussed:
  • the CU of the source IAB donor needs to send multiple UE dedicated handover commands to all UEs in a UE group served by the migration IAB node, which is likely to cause huge signaling overhead.
  • RACH Random Access Channel
  • the PCI of the cell associated with this IAB node (and more particularly, the DU of this IAB node) , is likely to collide with any of PCIs of one or more neighbor cells, since static PCI mapping via Operation, Administration and Maintenance (OAM) /CU may not work in such case.
  • OAM Operation, Administration and Maintenance
  • the method may be implemented between a UE and a network system which includes at least a source IAB donor, a target IAB donor and a migration IAB node.
  • a reconfiguration message associated with group handover may be used to configure change rules of security keys for the group of UEs.
  • a triggering message for group handover may be used to trigger this group of UEs to execute group handover from the source IAB donor to the target IAB donor, after the migration IAB node performs Inter-Donor Full-Migration.
  • FIG. 5A illustrates a flowchart diagram for an example method at UE side for supporting group handover in mobile IAB node scenario.
  • a wireless device such as a UE 102 or 104 illustrated in various of the Figures herein, and/or more generally in conjunction with any of the computer circuitry, systems, devices, elements, or components shown in the above Figures, among others, as desired.
  • a processor (and/or other hardware) of such a device may be configured to cause the device to perform any combination of the illustrated method elements and/or other method elements.
  • the method of FIG. 5A may operate as follows.
  • a UE may receive from a source IAB donor, a reconfiguration message associated with group handover.
  • the reconfiguration message may indicate an identifier of a UE group including one or more UEs served by a migration IAB node and multiple security key change rules, wherein the UE belongs to the UE group, and wherein the migration IAB node performs an inter-donor switch from the source IAB donor to a target IAB donor and serves the UE.
  • the UE may receive, from the migration IAB node, a triggering message for group handover.
  • the triggering message may indicate the above-mentioned identifier of the UE group and a determined security key change rule corresponding to the UE group, wherein the determined security key change rule may be included in the multiple security key change rules.
  • the UE may perform a group handover from the source IAB donor to the target IAB donor, based on the determined security key change rule corresponding to the UE group.
  • FIG. 5B illustrates a flowchart diagram for an example method at network side for supporting group handover in mobile IAB node scenario.
  • IAB devices e.g., a source IAB donor, a target IAB donor, and a migration IAB node which performs inter-donor switch from the source IAB donor to the target IAB donor
  • processor (s) (and/or other hardware (s) ) of such devices may be configured to cause the devices to perform any combination of the illustrated method elements and/or other method elements.
  • the method of FIG. 5B may operate as follows.
  • the source IAB donor may send, to a UE served by the migration IAB node, a reconfiguration message associated with group handover.
  • the reconfiguration message may indicate an identifier of a UE group including one or more UEs served by a migration IAB node and multiple security key change rules, wherein the UE belongs to the UE group.
  • the migration IAB node may send, to the UE, a triggering message for group handover.
  • the triggering message may indicate the identifier of the UE group and a determined security key change rule corresponding to the UE group, wherein the determined security key change rule may be included in the multiple security key change rules.
  • the triggering message may cause the UE to perform a group handover from the source IAB donor to the target IAB donor, based on the determined security key change rule corresponding to the UE group.
  • the reconfiguration message associated with group handover may be transmitted and received via RRC layer, and its specific format depends on the signaling transmission layer of the triggering message for group handover.
  • this triggering message may be transmitted and received via Downlink Control Information (DCI) in Layer 1 (L1) , or via Media Access Control (MAC) Control Element (CE) in Layer 2 (L2) .
  • DCI Downlink Control Information
  • MAC Media Access Control
  • CE Control Element
  • Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method for group handover according to the present disclosure.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 202 that is a UE, as described herein) or a network system (e.g., including multiple network devices 218 such as IAB devices, as described herein) .
  • Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method for group handover according to the present disclosure.
  • This non-transitory computer-readable media may be, for example, a memory of a UE (such as a wireless device 202 that is a UE, as described herein) or a network system (e.g., including multiple network devices 218 such as IAB devices, as described herein) .
  • Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method for group handover according to the present disclosure.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 202 that is a UE, as described herein) or a network system (e.g., including multiple network devices 218 such as IAB devices, as described herein) .
  • Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method for group handover according to the present disclosure.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 202 that is a UE, as described herein) or a network system (e.g., including multiple network devices 218 such as IAB node, as described herein) .
  • Embodiments contemplated herein include a signal as described in or related to one or more elements of the method for group handover according to the present disclosure.
  • Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method for group handover according to the present disclosure.
  • the processor may be a processor of a UE (such as processor (s) 204 of a wireless device 202 that is a UE, as described herein) or a processor in a network system (such as processor (s) 220 of a network device 218 such as an IAB device, as described herein) .
  • These instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory 206 of a wireless device 202 that is a UE, as described herein) or a memory in a network system (such as a memory 222 of a network device 218 such as an IAB device, as described herein) .
  • a memory of the UE such as a memory 206 of a wireless device 202 that is a UE, as described herein
  • a memory in a network system such as a memory 222 of a network device 218 such as an IAB device, as described herein
  • the PCI of the serving cell for the UE might collide with any of PCIs of one or more neighbor cells for the UE after handover.
  • the UE may be configured to report the observed PCI usage of neighbor cells in a measurement report to the source cell.
  • Another solution happens after the handover, in which the UE may be configured by the initial cell to detect a PCI collision between the serving cell and neighbor cells and report the collision status to the target cell.
  • FIG. 6A illustrates a flowchart diagram for an example method at UE side for supporting PCI collision prevention in mobile IAB node scenario.
  • a wireless device such as a UE 102 or 104 illustrated in various of the Figures herein, and/or more generally in conjunction with any of the computer circuitry, systems, devices, elements, or components shown in the above Figures, among others, as desired.
  • a processor (and/or other hardware) of such a device may be configured to cause the device to perform any combination of the illustrated method elements and/or other method elements.
  • the method of FIG. 6A may operate as follows.
  • the UE may receive, from a source IAB donor, a reconfiguration message associated with PCI collision prevention.
  • the reconfiguration message may indicate one of (i) and (ii) : (i) a measurement of PCIs of one or more neighbor cells for the UE a timer to indicate how long the UE performs the measurement for the PCIs of the one or more neighbor cells; and (ii) a detection of PCI collision between a serving cell for the UE and one or more neighbor cells for the UE.
  • each cell may include an IAB device (e.g., an IAB node) , and the reconfiguration message associated with PCI collision prevention may be used for avoiding PCI collisions when the UE performs a handover from the source IAB donor to a target IAB donor.
  • an IAB device e.g., an IAB node
  • FIG. 6B illustrates a flowchart diagram for an example method at network side for supporting PCI collision prevention in mobile IAB node scenario.
  • a network device such as an IAB device (e.g., a source IAB donor) in various of the Figures herein, and/or more generally in conjunction with any of the computer circuitry, systems, devices, elements, or components shown in the above Figures, among others, as desired.
  • a processor (and/or other hardware) of such a device may be configured to cause the device to perform any combination of the illustrated method elements and/or other method elements.
  • the method of FIG. 6B may operate as follows.
  • the source IAB donor may send, to a UE, a reconfiguration message associated with PCI collision prevention.
  • the reconfiguration message may indicate one of (i) and (ii) : (i) a measurement of PCIs of one or more neighbor cells for the UE a timer to indicate how long the UE performs the measurement for the PCIs of the one or more neighbor cells; and (ii) a detection of PCI collision between a serving cell for the UE and one or more neighbor cells for the UE.
  • each cell may include an IAB device (e.g., an IAB node) , and the reconfiguration message associated with PCI collision prevention may be used for avoiding PCI collisions when the UE performs a handover from the source IAB donor to a target IAB donor.
  • an IAB device e.g., an IAB node
  • the method for supporting PCI collision prevention is applicable for situations regarding UE group handover, it is also application for a single UE handover from a source cell to a target cell.
  • the network device in this method is not necessarily limited to an IAB device, it may be other types of base stations (e.g., eNBs or gNBs) in cells, each of which is associated with a PCI.
  • reconfiguration message associated with PCI collision prevention may be transmitted and received via RRC layer.
  • Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method for PCI collision prevention according to the present disclosure.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 202 that is a UE, as described herein) or a network device (such as a network device 218 like an IAB device, as described herein) .
  • Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method for PCI collision prevention according to the present disclosure.
  • This non-transitory computer-readable media may be, for example, a memory of a UE (such as a wireless device 202 that is a UE, as described herein) or a network device (such as a network device 218 like an IAB device, as described herein) .
  • Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method for PCI collision prevention according to the present disclosure.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 202 that is a UE, as described herein) or a network device (such as a network device 218 like an IAB device, as described herein) .
  • Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method for PCI collision prevention according to the present disclosure.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 202 that is a UE, as described herein) or a network device (such as a network device 218 like an IAB device, as described herein) .
  • Embodiments contemplated herein include a signal as described in or related to one or more elements of the method for PCI collision prevention according to the present disclosure.
  • Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method for PCI collision prevention according to the present disclosure.
  • the processor may be a processor of a UE (such as processor (s) 204 of a wireless device 202 that is a UE, as described herein) or a processor in a network device (such as a processor 220 of a network device 218 such as an IAB device, as described herein) .
  • These instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory 206 of a wireless device 202 that is a UE, as described herein) or a memory in a network device (such as a memory 222 of a network device 218 such as an IAB device, as described herein) .
  • a memory of the UE such as a memory 206 of a wireless device 202 that is a UE, as described herein
  • a memory in a network device such as a memory 222 of a network device 218 such as an IAB device, as described herein
  • FIG. 7 illustrates an example signaling diagram between the UE and network-side devices, according to a combination of two methods.
  • the signaling diagram is not intended to limit the exemplary embodiments in any way. Instead, the signaling diagram provides an example signaling exchange that may be used for supporting UE group handover and PCI collision prevention in mobile IAB scenario.
  • the communication signaling may mainly happen between the UE, the migration IAB node, the source IAB donor and the target IAB donor.
  • the UE may receive a reconfiguration message associated with PCI collision prevention from the source IAB donor.
  • This reconfiguration message may be transmitted and received via RRC layer, e.g., in the format of RRCReconfiguration message.
  • the reconfiguration message associated with PCI collision prevention may indicate one of the following two configurations: (i) a measurement of PCIs of one or more neighbor cells for the UE (e.g., shown as reportNeighborPCI in FIG. 7) ; and (ii) a detection of PCI collision between a serving cell for the UE and one or more neighbor cells for the UE (e.g., shown as reportPCICollision in FIG. 7) .
  • a timer which may indicate how long the UE should perform the measurement for PCIs of the neighbor cells may be also indicated in the reconfiguration message associated with PCI collision prevention.
  • Step 2 is directed to the configuration for reportNeighborPCI in Step 1.
  • the UE may perform a measurement of PCIs of its available one or more neighbor cells. For example, the UE may start the timer and perform the measurement. Upon expiry of the timer, the UE may stop the measurement and send a measurement report to the source IAB donor.
  • This measurement report may include a list of PCIs, and respective cell identifiers (IDs) and frequencies of the one or more neighbor cells.
  • IDs cell identifiers
  • the source IAB donor may send a handover request to the target IAB donor.
  • This handover request may include an identifier of (the DU of) the migration IAB node, and a list of UE contexts of all UEs served by the migration IAB node.
  • the UE contexts may indicate the status, supported transmission way, and antenna information of UEs, and so on.
  • This step may avoid sending multiple dedicated handover request messages for each UE served by the migration IAB node.
  • a new Xn message may be introduced to send the above non-UE-associated signaling to include huge payload.
  • the handover request sent from the source IAB donor to the target IAB donor may further include the list of PCIs and respective cell IDs of the one or more neighbor cells for the UE obtained from Step 2, as well as the PCI and respective cell ID of the serving cell for the UE. If the PCI of the serving cell does not overlap with any of the list of PCIs of the one or more neighbor cells, the target IAB donor may not change the PCI of the serving cell for the UE, which may avoid an interruption of migration, and save time and overhead.
  • the target IAB donor may need to change the PCI of the serving cell for the UE to a new PCI which does not overlap with any of the list of PCIs of the one or more neighbor cells, after the migration.
  • the target IAB donor may send an acknowledgement (ACK) for the handover request to the source IAB donor.
  • ACK acknowledgement
  • the UE may receive a reconfiguration message associated with group handover from the source IAB donor.
  • This reconfiguration message may be transmitted and received via RRC layer, e.g., in the format of RRCReconfiguration message.
  • RRC layer e.g., in the format of RRCReconfiguration message.
  • all UEs served by the migration IAB node may be divided into one or more groups, where any two UE groups do not overlap.
  • the source IAB donor may configure multiple UE groups for group handover via dedicated RRCReconfiguration messages.
  • the specific format of the reconfiguration message associated with group handover may depend on the particular transmission layer of signaling of the triggering message for group handover, which may be Layer 1 (L1) signaling or Layer 2 (L2) signaling.
  • L1 Layer 1
  • L2 Layer 2
  • the reconfiguration message associated with group handover may at least indicate an identifier of a UE group which the receiving UE served by the migration IAB node in Step 5 belongs to, and multiple security key change rules.
  • the identifier of the UE group may be defined as a function of identifiers (e.g., Cell-Radio Network Temporary Identities (C-RNTIs) ) of existing UEs in that UE group.
  • C-RNTIs Cell-Radio Network Temporary Identities
  • the security key change rules may include following four options (sometimes may only include two options in the middle) :
  • the reconfiguration message may also indicate a Next Chain Count (NCC) , which may be used when the security key change rule is determined as vertical security key change during the group handover (thus at this step, the UE may just store this NCC but does not apply it upon receiving NCC) .
  • NCC Next Chain Count
  • the reconfiguration message associated with group handover may at least indicate an identifier of a UE group which the receiving UE served by the migration IAB node in Step 5 belongs to, and multiple security key change rules.
  • the reconfiguration message may also indicate an NCC.
  • the reconfiguration message may include a UE group common RNTI, which may be used for information scrambling.
  • the handover for the migration IAB node and its served UEs may be performed after the reconfiguration associated with group handover is completed.
  • the reconfiguration message associated with group handover may be transmitted via Group common G-RNTI scheduling to all UEs in a UE group.
  • the G-RNTI for the transmission of the reconfiguration message may be preconfigured to all UEs in the UE group via a UE-dedicated signaling or derived based on C-RNTIs associated with those UEs.
  • the MT of the migration IAB node may perform inter-donor switch from (the CU of) the source IAB donor to the (the CU of) target IAB donor.
  • the DU of the migration IAB node may perform inter-donor switch from (the CU of) the source IAB donor to (the CU of) the target IAB donor.
  • the UE may receive a triggering message for group handover.
  • This triggering message may indicate the above-mentioned identifier of the UE group which the receiving UE served by the migration IAB node belongs to, and a determined security key change rule corresponding to this UE group.
  • the triggering message for group handover may be transmitted and received via DCI in L1 signaling, or via MAC CE in L2 signaling.
  • the UE may adopt parameters in the reconfiguration message associated with group handover regarding L1 signaling.
  • the signaling format may be illustrated as TABLE 1 (assuming there are M UE groups) .
  • Group 0 (2 bits)
  • Group 1 (2 bits)
  • Group M (2 bits)
  • the determined security key change rule for each UE group could be represented by 2 bits, where “00” refers to the above-described option 0 –no change; “01” refers to the option 1 –horizontal key change; “10” refers to the option 2 –vertical key change; and “11” refers to the option 3 –release.
  • the determined security key change rule for each UE group could be represented by 1 bit, where “0” refers to the option 1 –horizontal key change; and “1” refers to the option 2 –vertical key change.
  • the UE may adopt parameters in the reconfiguration message associated with group handover regarding L2 signaling.
  • the signaling format may be illustrated as TABLE 2 (assuming there are M groups) .
  • the triggering message may only indicate the identifier and corresponding security key change rule for the UE group including the receiving UE, or the triggering message may indicate information for multiple UE groups including said UE group.
  • the UE performs a group handover from the source IAB donor to the target IAB donor based on the determined security key change rule, which may occur together with other UE (s) in the same UE group. For example, if the security key change rule filed indicates 1 ( “01” ) , the UE may apply horizontal key change. If the security key change rule filed indicates 2 ( “10” ) , the UE may adopt configured NCC in the reconfiguration message associated with group handover and apply vertical key change. If the security key change rule filed indicates 3 ( “11” ) , the UE may release from the serving cell and may enter IDLE state and perform cell selection.
  • the migration IAB node may notify the target IAB donor that the group handover is completed after UE (s) in a UE group complete handover.
  • a new Information Element (IE) indicating of group handover completed may be added in a GNB-DU CONFIGURATION UPDATE message sent from the migration IAB node to the target IAB donor.
  • the migration IAB node may send the indication message with a time gap, after sending L1/L2 signaling to trigger group handover.
  • This indication message may be transmitted via an Xn message.
  • this indication message may also use BAP control Protocol Data Unit (PDU) .
  • PDU BAP control Protocol Data Unit
  • Step 10 is directed to the configuration for reportPCICollision in Step 1.
  • the UE may detect whether there is a PCI collision between the serving cell for the UE and the one or more neighbor cells for the UE. If the UE has detected there is a PCI collision between the serving cell for the UE and one or more neighbor cells for the UE, the UE may report a collided PCI and respective cell identifiers associated with the collided PCI (e.g., IDs of cells that are using the same PCI in close range) to the target IAB donor. It should be appreciated that this procedure happens after the UE performs handover.
  • the UE may read system information block 1 (SIB1) of its neighbor cells to determine their NR Cell Global Identifiers (NCGIs) to determine whether there is a PCI collision between the neighbor cells and the serving cell.
  • SIB1 system information block 1
  • NCGIs NR Cell Global Identifiers
  • one or more source parent IAB nodes and one or more target parent IAB nodes may involve the above communications as relay IAB nodes. Alternatively, there may exist no parent IAB nodes.
  • the steps regarding the migration IAB node may mainly be conducted by the DU of the migration IAB node except for Step 6 in FIG. 7.
  • the steps performed by the source IAB donor and the target IAB donor may mainly be conducted by the CU of the source IAB donor and the CU of the target IAB donor, respectively, in FIG. 7.
  • Step 5 is not required to be performed right before Step 8, and it may be performed in advance, e.g., before Step 1 as part of an earlier reconfiguration.
  • Step 2 and Step 10 are not required to be both performed, and the performance of one of them may lead to the effect of PCI collision prevention.
  • Steps 3-4, 5, 6-8, and 9 in FIG. 7 are mainly related to the method for UE group handover, and Steps 1, 2, 3-4, and 10 in FIG. 7 are mainly related to the method for PCI collision prevention. Therefore, the details in these steps may also apply to the corresponding method when performed independently (e.g., in FIG. 5 or FIG. 6) .
  • a user equipment comprising:
  • processors coupled to the at least one radio
  • the one or more processors are configured to cause the UE to:
  • a source Integrated Access and Backhaul (IAB) donor receives, from a source Integrated Access and Backhaul (IAB) donor, a reconfiguration message associated with group handover, the reconfiguration message indicating an identifier of a UE group including one or more UEs served by a migration IAB node and multiple security key change rules, wherein said UE belongs to the UE group, and wherein the migration IAB node performs an inter-donor switch from the source IAB donor to a target IAB donor and serves said UE;
  • IAB Integrated Access and Backhaul
  • the migration IAB node receives, from the migration IAB node, a triggering message for group handover, the triggering message indicating said identifier of the UE group and a determined security key change rule corresponding to the UE group, wherein the determined security key change rule is included in the multiple security key change rules;
  • a handover request sent from the source IAB donor to the target IAB donor includes at least an identifier of the migration IAB node and UE contexts of all UEs served by the migration IAB node.
  • RRC Radio Resource Control
  • the triggering message for group handover is received via Downlink Control Information (DCI) in Layer 1 (L1) .
  • DCI Downlink Control Information
  • the reconfiguration message associated with group handover is received via Radio Resource Control (RRC) layer, the reconfiguration message further indicating a UE group common Radio Network Temporary Identity (RNTI) ; and
  • RRC Radio Resource Control
  • RNTI Radio Network Temporary Identity
  • the triggering message for group handover is received via Media Access Control (MAC) Control Element (CE) in Layer 2 (L2) .
  • MAC Media Access Control
  • CE Control Element
  • the reconfiguration message associated with group handover is transmitted via Group common Radio Network Temporary Identity (G-RNTI) scheduling to the one or more UEs in the UE group.
  • G-RNTI Group common Radio Network Temporary Identity
  • the G-RNTI for the transmission of the reconfiguration message is preconfigured to the one or more UEs in the UE group via a UE-dedicated signaling or derived based on Cell Radio Network Temporary Identity (C-RNTI) associated with the one or more UEs.
  • C-RNTI Cell Radio Network Temporary Identity
  • the reconfiguration message associated with group handover further indicates a Next Chain Count (NCC) , which is used when the security key change rule is vertical security key change after group handover.
  • NCC Next Chain Count
  • the migration IAB node after the UE performs the group handover, notifies the target IAB donor that the group handover is completed via an Xn message or a Backhaul Adaptation Protocol (BAP) control Protocol Data Unit (PDU) .
  • BAP Backhaul Adaptation Protocol
  • PDU Protocol Data Unit
  • the source IAB donor includes at least a central unit (CU)
  • the target IAB donor includes at least a central unit (CU) ;
  • the CU of the source IAB donor is different from the CU of the target IAB donor.
  • the migration IAB node includes a mobile terminal (MT) and a distributed unit (DU) ; and
  • the migration IAB node performing an inter-donor switch from the source IAB donor to the target IAB donor includes: the MT of the migration IAB node performing an inter-donor switch from the CU of the source IAB donor to the CU of the target IAB donor, and the DU of the migration IAB node performing an inter-donor switch from the CU of the source IAB donor to the CU of the target IAB donor.
  • PCI Physical Cell Identifier
  • each cell includes an IAB node.
  • a handover request sent from the source IAB donor to the target IAB donor includes at least the list of PCIs and respective cell identifiers of the one or more neighbor cells for the UE and the PCI and respective cell identifier of the serving cell for the UE;
  • the target IAB donor in response to the PCI of the serving cell not overlapping with any of the list of PCIs of the one or more neighbor cells, the target IAB donor does not change the PCI of the serving cell for the UE; or in response to the PCI of the serving cell overlapping with any of the list of PCIs of the one or more neighbor cells, the target IAB donor changes the PCI of the serving cell for the UE to a new PCI which does not overlap with any of the list of PCIs of the one or more neighbor cells.
  • a user equipment comprising:
  • processors coupled to the at least one radio
  • the one or more processors are configured to cause the UE to:
  • IAB Integrated Access and Backhaul
  • PCI Physical Cell Identifier
  • reconfiguration message indicates one of (i) and (ii) :
  • each cell includes an IAB node
  • the reconfiguration message associated with PCI collision prevention is used for avoiding PCI collisions when the UE performs a handover from the source IAB donor to a target IAB donor.
  • a handover request sent from the source IAB donor to the target IAB donor includes at least the list of PCIs and respective cell identifiers of the one or more neighbor cells for the UE and the PCI and respective cell identifier of the serving cell for the UE;
  • the target IAB donor in response to the PCI of the serving cell not overlapping with any of the list of PCIs of the one or more neighbor cells, the target IAB donor does not change the PCI of the serving cell for the UE; or in response to the PCI of the serving cell overlapping with any of the list of PCIs of the one or more neighbor cells, the target IAB donor changes the PCI of the serving cell for the UE to a new PCI which does not overlap with any of the list of PCIs of the one or more neighbor cells.
  • a network system including a source Integrated Access and Backhaul (IAB) donor, a target IAB donor, and a migration IAB node which performs an inter-donor switch from the source IAB donor to the target IAB donor, the network system being configured to:
  • UE user equipment
  • the migration IAB node sends, from the migration IAB node to the UE, a triggering message for group handover, the triggering message indicating said identifier of the UE group and a determined security key change rule corresponding to the UE group, wherein the determined security key change rule is included in the multiple security key change rules;
  • the triggering message causes the UE to perform a group handover from the source IAB donor to the target IAB donor, based on the determined security key change rule corresponding to the UE group.
  • processors coupled to the at least one radio
  • processors are configured to cause the source IAB donor to:
  • PCI Physical Cell Identifier
  • reconfiguration message indicates one of (i) and (ii) :
  • each cell includes an IAB node
  • the reconfiguration message associated with PCI collision prevention is used for avoiding PCI collisions when the UE performs a handover from the source IAB donor to a target IAB donor.
  • a method for a user equipment (UE) comprising:
  • a source Integrated Access and Backhaul (IAB) donor receiving, from a source Integrated Access and Backhaul (IAB) donor, a reconfiguration message associated with group handover, the reconfiguration message indicating an identifier of a UE group including one or more UEs served by a migration IAB node and multiple security key change rules, wherein said UE belongs to the UE group, and wherein the migration IAB node performs an inter-donor switch from the source IAB donor to a target IAB donor and serves said UE;
  • IAB Integrated Access and Backhaul
  • the migration IAB node receiving, from the migration IAB node, a triggering message for group handover, the triggering message indicating said identifier of the UE group and a determined security key change rule corresponding to the UE group, wherein the determined security key change rule is included in the multiple security key change rules;
  • a method for a user equipment (UE) comprising:
  • IAB Integrated Access and Backhaul
  • PCI Physical Cell Identifier
  • reconfiguration message indicates one of (i) and (ii) :
  • each cell includes an IAB node
  • the reconfiguration message associated with PCI collision prevention is used for avoiding PCI collisions when the UE performs a handover from the source IAB donor to a target IAB donor.
  • a method for a network system including a source Integrated Access and Backhaul (IAB) donor, a target IAB donor, and a migration IAB node which performs an inter-donor switch from the source IAB donor to the target IAB donor, the method comprising:
  • the triggering message causes the UE to perform a group handover from the source IAB donor to the target IAB donor, based on the determined security key change rule corresponding to the UE group.
  • a method for a network device including a source Integrated Access and Backhaul (IAB) donor comprising:
  • UE user equipment
  • PCI Physical Cell Identifier
  • reconfiguration message indicates one of (i) and (ii) :
  • each cell includes an IAB node
  • the reconfiguration message associated with PCI collision prevention is used for avoiding PCI collisions when the UE performs a handover from the source IAB donor to a target IAB donor.
  • An apparatus for operating a user equipment (UE) comprising:
  • a processor configured to cause the UE to:
  • a source Integrated Access and Backhaul (IAB) donor receives, from a source Integrated Access and Backhaul (IAB) donor, a reconfiguration message associated with group handover, the reconfiguration message indicating an identifier of a UE group including one or more UEs served by a migration IAB node and multiple security key change rules, wherein said UE belongs to the UE group, and wherein the migration IAB node performs an inter-donor switch from the source IAB donor to a target IAB donor and serves said UE;
  • IAB Integrated Access and Backhaul
  • the migration IAB node receives, from the migration IAB node, a triggering message for group handover, the triggering message indicating said identifier of the UE group and a determined security key change rule corresponding to the UE group, wherein the determined security key change rule is included in the multiple security key change rules;
  • An apparatus for operating a user equipment (UE) comprising:
  • a processor configured to cause the UE to:
  • IAB Integrated Access and Backhaul
  • PCI Physical Cell Identifier
  • reconfiguration message indicates one of (i) and (ii) :
  • each cell includes an IAB node
  • the reconfiguration message associated with PCI collision prevention is used for avoiding PCI collisions when the UE performs a handover from the source IAB donor to a target IAB donor.
  • a non-transitory computer-readable storage medium storing instructions, where the instructions, when executed by a computer system, cause the computer system to perform the method of (24) or (25) .
  • (31) A non-transitory computer-readable storage medium storing instructions, where the instructions, when executed by a computer system, cause the computer system to perform the method of (26) or (27) .
  • a computer program product comprising program instructions which, when executed by a computer system, cause the computer system to perform the method of (24) or (25) .
  • a computer program product comprising program instructions which, when executed by a computer system, cause the computer system to perform the method of (26) or (27) .
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth herein.
  • a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.
  • Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system.
  • a computer system may include one or more general-purpose or special-purpose computers (or other electronic devices) .
  • the computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.
  • personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
  • personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Landscapes

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

Abstract

La présente divulgation concerne des procédés et des dispositifs de prévention de collision de transfert de groupe et d'identifiant de cellule physique (PCI) dans un scénario d'accès intégré mobile et de liaison terrestre (IAB). Selon la présente divulgation, un équipement utilisateur (UE) peut recevoir, en provenance d'un donneur IAB source, un message de reconfiguration associé à un transfert de groupe. Ce message de reconfiguration peut indiquer un identifiant d'un groupe d'UE comprenant un ou plusieurs UE desservis par un nœud IAB de migration et de multiples règles de changement de clé de sécurité, ledit UE appartenant au groupe d'UE, et le nœud IAB de migration effectuant une commutation inter-donneur du donneur IAB source à un donneur IAB cible. L'UE peut en outre recevoir, en provenance du nœud IAB de migration, un message de déclenchement de transfert de groupe. Ce message de déclenchement indiquant ledit identifiant du groupe d'UE et une règle de changement de clé de sécurité déterminée correspondant au groupe d'UE, la règle de changement de clé de sécurité déterminée étant incluse dans les multiples règles de changement de clé de sécurité. En réponse à la réception du message de déclenchement, l'UE peut effectuer un transfert de groupe à partir du donneur IAB source vers le donneur IAB cible, sur la base de la règle de changement de clé de sécurité déterminée correspondant au groupe d'UE. En outre ou en variante, un UE peut recevoir, en provenance d'un donneur IAB source, un message de reconfiguration associé à la prévention de collision de PCI. Ce message de reconfiguration associé à la prévention de collision de PCI peut indiquer l'un de (i) et de (ii) : (i) une mesure de PCI d'une ou de plusieurs cellules voisines pour l'UE et un temporisateur pour indiquer la durée pendant laquelle l'UE effectue la mesure pour le PCI de la ou des cellules voisines; et (ii) une détection de collision de PCI entre une cellule de desserte pour l'UE et une ou plusieurs cellules voisines pour l'UE. Chaque cellule peut comprendre un nœud IAB, et le message de reconfiguration associé à la prévention de collision de PCI peut être utilisé pour éviter des collisions de PCI lorsque l'UE effectue un transfert du donneur IAB source à un donneur IAB cible.
PCT/CN2022/110881 2022-08-08 2022-08-08 Transfert de groupe et prévention de collision de pci dans un scénario iab mobile WO2024031244A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/110881 WO2024031244A1 (fr) 2022-08-08 2022-08-08 Transfert de groupe et prévention de collision de pci dans un scénario iab mobile

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/110881 WO2024031244A1 (fr) 2022-08-08 2022-08-08 Transfert de groupe et prévention de collision de pci dans un scénario iab mobile

Publications (1)

Publication Number Publication Date
WO2024031244A1 true WO2024031244A1 (fr) 2024-02-15

Family

ID=89850248

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/110881 WO2024031244A1 (fr) 2022-08-08 2022-08-08 Transfert de groupe et prévention de collision de pci dans un scénario iab mobile

Country Status (1)

Country Link
WO (1) WO2024031244A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210044370A1 (en) * 2019-08-09 2021-02-11 Qualcomm Incorporated Physical cell identifier (pci) selection based on primary synchronization signal (pss) waveform
CN112840728A (zh) * 2018-10-12 2021-05-25 特许通讯运营公司 用于无线网络中的小区标识的设备及方法
WO2022087492A1 (fr) * 2020-10-22 2022-04-28 Google Llc Gestion d'accès intégré et mobilité de liaison terrestre
US20220132381A1 (en) * 2020-10-23 2022-04-28 At&T Intellectual Property I, L.P. User plane adaptation for mobile integrated access and backhaul

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112840728A (zh) * 2018-10-12 2021-05-25 特许通讯运营公司 用于无线网络中的小区标识的设备及方法
US20210044370A1 (en) * 2019-08-09 2021-02-11 Qualcomm Incorporated Physical cell identifier (pci) selection based on primary synchronization signal (pss) waveform
WO2022087492A1 (fr) * 2020-10-22 2022-04-28 Google Llc Gestion d'accès intégré et mobilité de liaison terrestre
US20220132381A1 (en) * 2020-10-23 2022-04-28 At&T Intellectual Property I, L.P. User plane adaptation for mobile integrated access and backhaul

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CATT: "Inter IAB donor-CU topology adaptation", 3GPP DRAFT; R3-206294, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-meeting; 20201102 - 20201113, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051945781 *
NOKIA (MODERATOR): "Summary of Offline Discussion on Reduction of Service", 3GPP DRAFT; R3-206856, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20201102 - 20201112, 17 November 2020 (2020-11-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052255804 *

Similar Documents

Publication Publication Date Title
US11706793B2 (en) User equipment and methods of bearer operation for carrier aggregation
US9930652B2 (en) Evolved node-B, user equipment and methods for transition between unlicensed and licensed frequency bands
US9345055B2 (en) Method and apparatus for establishing device-to-device connection in wireless communication system
US20170188273A1 (en) User equipment and methods for handover initiation
KR102038500B1 (ko) 업링크 데이터 처리 방법 및 그 장치
US9655155B2 (en) Method and apparatus for establishing device-to-device connection in wireless communication system
EP3138325A1 (fr) Équipement utilisateur et procédé pour un transfert intercellulaire à l'aide d'un rapport de mesure basé sur de multiples événements
US9560686B2 (en) Method and apparatus for reconfiguring device-to-device connection information in wireless communication system
US11659369B2 (en) Distributed sidelink (SL) architecture and protocol stack
US20150036659A1 (en) Local Networks
WO2024031244A1 (fr) Transfert de groupe et prévention de collision de pci dans un scénario iab mobile
WO2024031230A1 (fr) Rétablissement de commande de ressources radio (rrc) de groupe dans des noeuds de réseau de liaison terrestre et d'accès intégré (iab) mobiles
US11968563B2 (en) Inter-system and event-triggered mobility load balancing
KR102230149B1 (ko) 주파수 대역 결정 방법 및 그 장치
WO2023211069A1 (fr) Procédé et dispositif de traitement d'un trafic multimodal xr dans un système de communication sans fil
US20240014957A1 (en) Operation modes for high speed train enhancements
WO2024060210A1 (fr) Configuration pour un intervalle pour un ue à capacité musim
US20240007943A1 (en) Network Controlled Repeater
WO2024060189A1 (fr) Nouvelle conception de srb pour transmission de message rrc de groupe
WO2024092691A1 (fr) Procédé et dispositif d'adressage de collisions entre des fenêtres temporelles pour des opérations associées à différents réseaux
WO2023087265A1 (fr) Super-connexion de contrôle de ressources radio (rrc) ue
WO2024020917A1 (fr) Procédés et systèmes de rapport de mesure de couche d'application par un équipement utilisateur fonctionnant dans un mode à double connectivité
CN110121855A (zh) 信息配置装置、监测装置、方法及通信系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22954224

Country of ref document: EP

Kind code of ref document: A1