A method, device and computer program product for wireless communication

Abstract

The present disclosure describes methods, systems, and devices for updating configuration information of a migration access backhaul integrated node (IAB-node) during an inter-anchor migration from a source IAB-anchor to a target IAB-anchor. A method includes providing configuration information of a migration IAB-node distributed unit (DU) in a dedicated radio resource control (RRC) message by a target IAB-anchor centralized unit (CU) during handover preparation. The method also includes sending an XnAP message by the target IAB-anchor CU to the source IAB-anchor CU, the XnAP message including configuration information as an RRC transparent transmission container, and then the source IAB-anchor CU sends a dedicated RRC message to the migration IAB-node mobile terminal (MT), the dedicated RRC message including the configuration information.

Description

Technical Field

[0001] The present disclosure is generally directed to wireless communications. In particular, the present disclosure relates to methods and apparatus for updating Integrated Access Backhaul (IAB) node configuration information during inter-anchor migration. Background Art

[0002] Wireless communication technology is driving the world towards an increasingly connected and networked society. Compared with Long Term Evolution (LTE), the fifth generation (5G) New Radio (NR) technology has a wider spectrum, for example, including millimeter wave (mmWave) bands. With the development of massive multiple input multiple output (MIMO) and / or multi-beam systems, 5G NR can provide faster speeds and shorter latency.

[0003] 5G NR may include an integrated access backhaul (IAB) implementation. An IAB implementation may include one or more IAB-anchors and multiple connected IAB-nodes. Currently, there are challenges and / or problems associated with configuring IAB-nodes, particularly when an IAB-node is migrated from one IAB-anchor to another IAB-anchor.

[0004] The present disclosure may address at least some of the challenges / problems associated with existing systems to improve the performance of wireless communications. Summary of the invention

[0005] The present application relates to methods, systems, and devices for wireless communications, and more particularly, to methods, systems, and devices for updating Integrated Access Backhaul (IAB) node configuration information during inter-anchor migration.

[0006] In one embodiment, the present disclosure describes a method for wireless communication. The method includes: during an inter-anchor migration from a source IAB-anchor to a target IAB-anchor, updating configuration information for a migrating access backhaul integrated node (IAB-node) by the following steps: during handover preparation, the target IAB-anchor centralized unit (CU) provides configuration information of a migrating IAB-node distributed unit (DU) in a dedicated radio resource control (RRC) message (i.e., RRCReconfiguration message); and the target IAB-anchor CU sends an XnAP message to the source IAB-anchor CU, the XnAP message including configuration information as an RRC transparent transmission container, and then the source IAB-anchor CU sends a dedicated RRC message to the migrating IAB-node mobile terminal (MT), the dedicated RRC message including configuration information.

[0007] In another embodiment, the present disclosure describes a method for wireless communication. The method includes: during an inter-anchor migration from a source IAB-anchor to a target IAB-anchor, updating configuration information of a migration access backhaul integrated node (IAB-node) by sending an F1-AP message from a target IAB-anchor centralized unit (CU) to a migration IAB-node distributed unit (DU), the F1-AP message including new configuration information, the new configuration information including a new radio (NR) physical cell identifier (PCI) and / or an NR cell global identifier (CGI).

[0008] In another embodiment, the present disclosure describes a method for wireless communication. The method includes: during an inter-anchor migration from a source IAB-anchor to a target IAB-anchor, updating configuration information for a migrating access backhaul integrated node (IAB-node) by allocating configuration information to the migrating IAB-node by a target IAB-anchor centralized unit (CU) and setting a cause value in an F1 setup failure; and sending an F1 setup failure message by the target IAB-anchor CU to the migrating IAB-node DU, the F1 setup failure message including the configuration information allocated to the migrating IAB-node.

[0009] In some other embodiments, the apparatus for wireless communication may include a memory storing instructions and a processing circuit in communication with the memory. When the processing circuit executes the instructions, the processing circuit is configured to perform the above method.

[0010] In some other embodiments, the device for wireless communication may include a memory storing instructions and a processing circuit in communication with the memory. When the processing circuit executes the instructions, the processing circuit is configured to perform the above method.

[0011] In some other embodiments, a computer readable medium includes instructions that, when executed by a computer, cause the computer to perform the above method.

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

[0013] Figure 1A An example of a wireless communication system including an Integrated Access Backhaul (IAB) system is shown.

[0014] Figure 1B Another example of the architecture of an IAB system is shown.

[0015] Figure 2 Examples of IAB-anchors or IAB-nodes are shown.

[0016] Figure 3An example of a user device is shown.

[0017] Figure 4 A schematic diagram showing a migrating IAB-node in inter-anchor migration.

[0018] Figure 5 A flow chart of a method for wireless communication is shown.

[0019] Fig. 6A Shown for Figure 5 An exemplary logic flow of a method of wireless communication in the present invention.

[0020] Figure 6B Shown for Figure 5 Another exemplary logic flow of a method of wireless communication in the present invention.

[0021] Figure 6C Shown for Figure 5 Another exemplary logic flow of a method of wireless communication in the present invention.

[0022] Fig.6D Shown for Figure 5 Another exemplary logic flow of a method of wireless communication in the present invention.

[0023] Figure 7 A flow chart of another method for wireless communication is shown.

[0024] Figure 8 A flow chart of another method for wireless communication is shown. DETAILED DESCRIPTION

[0025] The present disclosure will now be described in detail below with reference to the accompanying drawings, which form a part of the present disclosure and show by way of illustration specific examples of embodiments. However, it is noted that the present disclosure may be embodied in a variety of different forms, and therefore, the subject matter covered or claimed is intended to be construed as not limited to any embodiment set forth below.

[0026] Throughout the specification and claims, terms may have nuanced meanings suggested or implied by the context, not just the explicitly stated meanings. Likewise, the phrases "in one embodiment" or "in some embodiments" as used herein do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" as used herein do not necessarily refer to different embodiments. The phrases "in one implementation" or "in some implementations" as used herein do not necessarily refer to the same implementation, and the phrases "in another implementation" or "in other implementations" as used herein do not necessarily refer to different implementations. For example, the claimed subject matter is intended to include, in whole or in part, exemplary embodiments or combinations of implementations.

[0027] In general, terms can be understood at least in part from usage in context. For example, terms such as "and", "or" or "and / or" used in this article can include multiple meanings, which can depend at least in part on the context in which these terms are used. Generally, if "or" is used to associate a list such as A, B or C, it is intended to represent A, B and C used in an inclusive sense here, and A, B or C used in an exclusive sense here. In addition, the terms "one or more" or "at least one" used in this article, at least in part depending on the context, can be used to describe any feature, structure or characteristic in a singular sense, or can be used to describe a combination of features, structures or characteristics in a plural sense. Similarly, terms such as "a", "an" or "the" can also be understood to express singular usage or plural usage, which depends at least in part on the context. In addition, the term "based on" or "determined by..." can be understood as not necessarily intended to express a set of exclusive factors, and on the contrary, the presence of additional factors that are not necessarily explicitly described can be allowed, which also depends at least in part on the context.

[0028] The present disclosure describes methods and apparatus for updating Integrated Access Backhaul (IAB) node configuration information during inter-anchor migration.

[0029] Next generation (NG) or fifth generation (5G) wireless communications can provide a range of capabilities from fast downloads to supporting real-time low-latency communications. Compared to long term evolution (LTE), 5G new air interface (NR) technology has a wider spectrum, for example, including millimeter wave (mmWave) bands. With the development of large-scale multiple input multiple output (MIMO) and / or multi-beam systems, 5G NR can provide faster speeds and shorter delays. 5G NR may include the development of integrated access backhaul (IAB) implementation methods. The IAB implementation method may include one or more IAB-anchor points and multiple connected IAB-nodes. The IAB implementation method may communicate between one or more IAB-anchor points and one or more IAB-nodes via wireless backhaul and relay links. The IAB implementation method may provide flexible NR cell configurations and increase cell density without increasing the density of IAB-anchor points.

[0030] The IAB system may include one or more IAB-anchors and one or more IAB-nodes, which together provide wireless connection services to one or more user equipment (UE) (e.g., smartphones). The IAB-anchor and IAB-node may be wireless network base stations including NG radio access network (NG-RAN) base stations, which may include nodeB (NB, e.g., gNB) in a mobile telecommunications environment. The IAB-anchor may provide access backhaul to one or more connected sub-IAB-nodes, and may be connected to the core network via wired communication. In one embodiment, the core network may include a 5G core network (5GC). In another embodiment, the wired communication may include optical fiber transmission communication. The IAB-node may include a wireless access link and a wireless backhaul link. The wireless access link may be used for communication between the UE and the IAB-node. The wireless backhaul link may be used for communication between the IAB-node and the IAB-anchor, and / or communication between one IAB-node and another IAB-node. Therefore, the IAB-node does not require a wired communication network for data backhaul. In some embodiments, the IAB-node does not include a wired communication network for data backhaul, making the IAB-node more flexible and easier to implement, reducing the burden of implementing a wired communication network. The access link and the backhaul link can use the same frequency transmission band (known as in-band relay), or use different frequency transmission bands (known as out-of-band relay).

[0031] refer to Figure 1A and Figure 1B , the IAB-anchor 130 may provide access backhaul 140 to one or more connected child IAB-nodes (152 and 154). The IAB-anchor 130 may be connected to the core network 110 via wired communication 120. In one embodiment, the core network 110 may include a 5G core network (5GC). In another embodiment, the wired communication 120 may include optical fiber transmission communication.

[0032] The IAB-anchor point may provide a wireless connection to one or more user equipments (UEs). A UE may be a mobile device, such as a smart phone or a mobile communication module provided in a vehicle. For example, the IAB-anchor point 130 may provide a wireless connection 160 to a UE 172.

[0033] Similarly, but not limited to, a child IAB-node may provide a wireless connection to one or more UEs. For example, IAB-node 152 may provide a wireless connection 160 to UE 174.

[0034] Similarly, but not limited to, a child IAB-node may provide access backhaul to one or more connected grandchild IAB-nodes. For example, IAB-node 154 may provide access backhaul 140 to IAB-node 156. Similarly, but not limited to, a grandchild IAB-node may also provide access backhaul to one or more connected great-grandchild IAB-nodes and / or provide wireless connectivity to one or more UEs.

[0035] refer to Figure 1B , the IAB system 100 may include more than one IAB-anchor point (130 and 135). Each of the IAB-anchor points may be connected to a core network (e.g., 5GC) 110 via wired communication 120. In one embodiment, the IAB-anchor point 135 may provide access backhaul 140 to one or more connected child IAB-nodes 158; and the IAB-node 158 may provide wireless connectivity 160 to one or more UEs 176.

[0036] An IAB-node 156 currently connected to the IAB-anchor 130 via the IAB-node 154 may be migrated to the IAB-anchor 135. This may be referred to as an inter-anchor migration, and the IAB-node 156 may be referred to as a migrated IAB-node. Currently, during an inter-anchor migration, there are challenges and / or problems associated with configuring a migrated IAB-node.

[0037] The present disclosure describes embodiments of methods and apparatus for updating configuration information of a migrating IAB-node during inter-anchor migration that address at least some of the challenges discussed above.

[0038] Figure 2 An exemplary wireless communication base station 200 is shown. The wireless communication base station 200 may be Figure 1A and Figure 1B 130 and 135) and IAB-nodes (152, 154, 156, and 158) in the exemplary embodiment. The base station 200 may include wireless transmission / reception (Tx / Rx) circuitry 208 to send / receive communications with one or more UEs and / or one or more other base stations. The base station may also include network interface circuitry 209 to enable the base station to communicate with other base stations and / or a core network (e.g., optical fiber or wired interconnection, Ethernet, and / or other data transmission media / protocols). The base station 200 may optionally include an input / output (I / O) interface 206 to communicate with an operator or the like.

[0039] The base station may also include system circuitry 204. System circuitry 204 may include a processor 221 and / or a memory 222. Memory 222 may include an operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for one or more processors 124 to perform the functions of the base station. Parameters 228 may include parameters that support the execution of instructions 226. For example, the parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocations, and / or other parameters.

[0040] Figure 3 An exemplary user equipment (UE) 300 is shown. UE 300 may be a mobile device, such as a smart phone or a mobile communication module provided in a vehicle. UE 300 may be Figure 1A and Figure 1B UE 300 may include a communication interface 302, a system circuit 304, an input / output interface (I / O) 306, a display circuit 308, and a memory 309. The display circuit may include a user interface 310. The system circuit 304 may include any combination of hardware, software, firmware, or other logic / circuitry. The system circuit 304 may be implemented, for example, using one or more system on chip (SoC), application specific integrated circuit (ASIC), discrete analog and digital circuits, and other circuits. The system circuit 304 may be part of an implementation of any desired functionality in the UE 300. In this regard, the system circuit 304 may include, for example, logic to facilitate the following operations: decoding and playing music and video logic (e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback); running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections (as an example, for Internet connections); establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 310. The user interface 310 and the input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, tactile feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Other examples of the I / O interface 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0041] refer to Figure 3, the communication interface 302 may include a radio frequency (RF) transmission (Tx) and reception (Rx) circuit 316 that processes the transmission and reception of signals through one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver that includes a modulation / demodulation circuit, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), a filter, a waveform shaper, a filter, a preamplifier, a power amplifier, and / or other logic for transmitting and receiving through one or more antennas or (for some devices) through a physical (such as a wired) medium. The signals sent and received may follow any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, the communication interface 302 may include a transceiver that supports transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA) +, 4G / Long Term Evolution (LTE), and 5G standards. However, the techniques described below are applicable to other wireless communication technologies, whether from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0042] refer to Figure 3 , the system circuit 304 may include one or more processors 321 and a memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute instructions 326 for performing the desired functions of the UE 300. The parameters 328 may provide and specify configuration and operating options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, or other data that the UE 300 will send or has received through the communication interface 302. In various embodiments, the system power of the UE 300 may be provided by a power storage device such as a battery or a transformer.

[0043] The present disclosure describes several embodiments of methods and apparatus for updating access backhaul integration (IAB) node configuration information during inter-anchor migration, which may be partially or fully implemented in the above Figure 2 and Figure 3 The invention is implemented on a wireless network base station and / or a user equipment described in the invention.

[0044] refer to Figure 4, the IAB system 400 may include two IAB-anchors (410 and 420). The IAB-node 450 currently connected to the IAB-anchor 410 via the IAB-node 430 may be migrated to the IAB-anchor 420 via the IAB-node 440. This may be referred to as inter-anchor migration. The IAB-node 450 may be a migration IAB-node; the IAB-anchor 410 may be a source IAB-anchor; the IAB-node 430 may be a source parent IAB-node; the IAB-anchor 420 may be a target IAB-anchor; the IAB-node 440 may be a target parent IAB-node.

[0045] The source IAB-anchor 410 may include a centralized unit (CU) 412 and a distributed unit (DU) 414, and the source IAB-anchor CU 412 may communicate with the source IAB-anchor DU 414. A source parent IAB-node 430 in communication with the source IAB-anchor 410 may include a mobile terminal (MT) 432 and a distributed unit (DU) 434. A target IAB-anchor 420 may include a CU 422 and a DU 424, and the target IAB-anchor CU 422 may communicate with the target IAB-anchor DU 424. A target IAB-node 440 in communication with the target IAB-anchor 420 may include a MT 442 and a DU 444.

[0046] Prior to inter-anchor migration, the migration IAB-node 450 may communicate with the source parent IAB-node 430. The migration IAB-node 450 may include a MT 452 and a DU 454. In one embodiment, the migration IAB-node 450 may communicate with a UE 470. In another embodiment, the migration IAB-node 450 may communicate with a child IAB-node 460. The child IAB-node 460 may include a MT 462 and a DU 464.

[0047] refer to Figure 4 , the migration IAB-node 450 may change its attachment point from the source parent IAB-node 430 connected to the source IAB-anchor 410 to the target IAB-node 440 connected to the target IAB-anchor 420. In one embodiment, a handover (HO) process may occur during the inter-anchor migration, and this may be an inter-CU HO scenario. The migration IAB-node DU 454 may communicate with the target IAB-anchor CU 422 via an F1-AP message 482.

[0048] refer to Figure 5, the present disclosure describes various embodiments of a method 500 for updating configuration information for migrating an IAB-node using a dedicated RRC message (e.g., but not limited to, an RRCReconfiguration message). The method can address the difficulty / problem of time delay associated with F1-AP process updates, and using a dedicated RRC message to update configuration information at handover preparation can reduce inter-anchor migration time delays and improve the performance of the IAB system. The configuration information may include at least one of a gNB DU identity (ID), a new radio (NR) physical cell identifier (PCI), an NR cell global identifier (CGI), or a public land mobile network (PLMN) identity.

[0049] Method 500 may include some or all of the following steps: step 510: the target IAB-anchor point centralized unit (CU) provides configuration information for migrating the IAB-node distributed unit (DU) in a dedicated RRC message (for example, but not limited to, an RRCReconfiguration message); step 520: the target IAB-anchor point CU sends an XnAP message including the generated RRCReconfiguration message to the source IAB-anchor point, and the RRCReconfiguration message includes the provided configuration information; step 530: the source IAB-anchor point CU sends an RRCReconfiguration message to the migrating IAB-node mobile terminal (MT), and the RRCReconfiguration message includes the provided configuration information; and step 540: after receiving the RRCReconfiguration message, the migrating IAB-node MT forwards the provided configuration information to the migrating IAB-node DU.

[0050] Fig. 6A A logical flow of a method 600 for updating the gNB-DU ID of a migrating IAB-node 450 using a dedicated RRC message during inter-anchor migration is shown. Currently, the gNB-DU ID for a migrating IAB-node can be configured by operations, administration, and maintenance (OAM). The gNB-DU ID can be a unique identifier of a migrating IAB-node connected to an IAB-anchor. During migration, OAM can ensure the uniqueness of the gNB-DU ID of the migrating IAB-node, whose main function is to identify from which IAB-node the F1-AP communication is sent by the IAB-anchor. The method 600 of updating the gNB-DU ID of a migrating IAB-node using an RRCReconfiguration message during handover preparation can reduce inter-anchor migration time delays and improve the performance of the IAB system.

[0051] refer to Fig. 6AIn step 610 of FIG. 4 , the migration IAB-node MT 452 may send a measurement report to the source parent IAB-node DU 434 .

[0052] refer to Fig. 6A In step 620 of the method 600, the source parent IAB-node DU 434 may include sending an uplink radio resource control (RRC) transfer message to the source IAB-anchor CU 412 to convey the measurement report. The uplink RRC transfer message may include the measurement report; and the source IAB-anchor CU 412 receives the uplink RRC transfer message from the serving IAB-node 430.

[0053] refer to Fig. 6A In step 630 of , after receiving the uplink RRC transfer message, the source IAB-anchor CU 412 may send an Xn handover request message to the target IAB-anchor CU 422 in order to initiate handover preparation.

[0054] refer to Fig. 6A In step 635, the target IAB-anchor CU 422 may allocate a gNB-DUID for the migrated IAB-node and provide the allocated gNB-DU ID in a dedicated RRC message. In one embodiment, for example but not limited to, the dedicated RRC message may be an RRCReconfiguration message.

[0055] refer to Fig. 6A In step 640, the target IAB-anchor CU 422 may send an Xn handover request confirmation (ACK) message to the source IAB-anchor CU 412. The Xn handover request confirmation message may include an RRCReconfiguration message including the allocated gNB-DU ID.

[0056] refer to Fig. 6A In step 650, the source IAB-anchor CU 412 may send a UE context modification request message including the generated RRCReconfiguration message to the source parent IAB-node DU 434. The generated downlink RRCReconfiguration message may include the allocated gNB-DU ID.

[0057] refer to Fig. 6AIn step 660, after receiving the UE Context Modification Request message as an F1-AP message with an RRCReconfiguration message from the source IAB-anchor CU 412, the source parent IAB-node DU 434 may send an RRCReconfiguration message to the migration IAB-node MT 452, where the RRC reconfiguration message includes the allocated gNB-DU ID.

[0058] refer to Fig. 6A In step 670, after receiving the RRCReconfiguration message, the migration IAB-node MT452 can forward the allocated gNB-DU ID to the migration IAB-node DU.

[0059] refer to Figure 6B , the present disclosure describes another embodiment of a method 600b for updating the NR PCI of a migrating IAB-node 450 using a dedicated RRC message during handover preparation. The served cell information for the migrating IAB-node can be configured by the OAM in the F1 pre-operational state, and / or can be sent to the IAB-anchor CU via an F1 establishment request. The served cell information may include NR CGI, NR PCI, 5GS Tracking Area Code (TAC) and / or Public Land Mobile Network (PLMN) ID. The method 600b for updating the NR PCI of the migrating IAB-node using an RRCReconfiguration message can reduce the inter-anchor migration time delay and improve the performance of the IAB system.

[0060] Method 600b may be used with Fig. 6A Step 635b and step 670b are respectively different from Fig. 6A 635 and 670 in step 600b. Instead of allocating a gNB-DU ID in a dedicated RRC message in step 635, the target IAB-anchor CU 422 may allocate an NR PCI in a dedicated RRC message in step 635b; and, instead of forwarding the allocated gNB-DU ID to the migration IAB-node DU 454 in step 670, the migration IAB-node MT 452 may forward the allocated NR PCI to the migration IAB-node DU 454 in step 670b. The method 600b may also include that the migration IAB-node DU 454 may activate the cell indicated by the NR CGI and reconfigure the cell indicated by the NR PCI.

[0061] refer to Figure 6C, the present disclosure describes another embodiment of a method 600c for updating the NR CGI of a migrating IAB-node 450 using an RRCReconfiguration message during inter-anchor migration. The NR CGI for migrating the IAB-node may be configured by OAM. The NR CGI may include a PLMN ID and an NR cell ID. The NR cell ID may also include a gNB ID and a cell ID within the gNB. The method 600c for updating the NR CGI of a migrating IAB-node using a dedicated RRC message may reduce inter-anchor migration time delays and improve the performance of the IAB system.

[0062] Method 600c may be used with Fig. 6A Step 635c and step 670c are respectively different from Fig. 6A 635 and 670 in step 600c. Instead of allocating a gNB-DU ID in a dedicated RRC message in step 635, the target IAB-anchor CU 422 may allocate an NR CGI in a dedicated RRC message in step 635c; and, instead of forwarding the allocated gNB-DU ID to the migration IAB-node DU 454 in step 670, the migration IAB-node MT 452 may forward the allocated NR CGI to the migration IAB-node DU 454 in step 670c. The method 600c may also include that the migration IAB-node DU 454 may activate the cell indicated by the NR CGI and reconfigure the cell indicated by the NR PCI.

[0063] refer to Fig.6D , the present disclosure describes another embodiment of a method 600d for updating the PLMN ID of a migrating IAB-node 450 using a dedicated RRC message during inter-anchor migration. The PLMN ID for the migrating IAB-node may be configured by OAM. The method 600d for updating the PLMN ID of a migrating IAB-node using a dedicated RRC message may reduce inter-anchor migration time delay and improve the performance of the IAB system.

[0064] Method 600d may be related to Fig. 6A The method 600 in FIG. 6 is slightly different. Step 635d and step 670d are respectively different from Fig. 6A635 and 670 in step 600d. Instead of allocating a gNB-DU ID in a dedicated RRC message in step 635, the target IAB-anchor CU 422 may allocate a PLMN ID in a dedicated RRC message in step 635d; and, instead of forwarding the allocated gNB-DU ID to the migration IAB-node DU 454 in step 670, the migration IAB-node MT 452 may forward the allocated PLMN ID to the migration IAB-node DU 454 in step 670d. The method 600d may also include that the migration IAB-node DU 454 may be configured based on the allocated PLMN ID.

[0065] refer to Figure 7 , the present disclosure describes various embodiments of a method 700 for updating configuration information of a migrating IAB-node using an F1 setup failure message during inter-anchor migration. The method may resolve difficulties / problems associated with the presence of a conflict, where the previous configuration information of the migrating IAB-node is the same for some other IAB-node that is already connected to the target IAB-anchor. The present disclosure may resolve the above-mentioned conflict by allocating new configuration information via an F1 setup failure message by the target IAB-anchor, thereby improving the performance of the IAB system. The configuration information may include at least one of a gNB-DU identity (ID), a new radio (NR) physical cell identifier (PCI), or an NR cell global identifier (CGI).

[0066] The method 700 may include some or all of the following steps: step 710: after migrating from a source IAB-anchor point to a target IAB-anchor point, the migrating IAB-node DU sends an F1 establishment request message to the target IAB-anchor point CU, the F1 establishment request message including the previous configuration information of the migrating IAB-node before the migration; step 720: the target IAB-anchor point CU determines whether a conflict of configuration information exists; step 730: the target IAB-anchor point CU provides configuration information for the migrating IAB-node in response to the conflict and sets a reason value; and step 740: the target IAB-anchor point CU sends an F1 establishment failure message to the migrating IAB-node DU, the F1 establishment failure message including the newly allocated configuration information for the migrating IAB-node; and step 750: the migrating IAB-node DU configures the migrating IAB-node based on the newly allocated configuration information.

[0067] In one embodiment, the configuration information may include a gNB-DU ID. When the migrating IAB-node DU sends an F1 setup request message including a previous gNB-DU ID to the target IAB-anchor CU, the target IAB-anchor CU may determine a conflict when the previous gNB-DU ID from the migrating IAB-node is the same as one of the other connected IAB-nodes. In response to the conflict, the target IAB-anchor CU sets the cause value to unknown or gNB-DU ID conflict. After receiving the F1 setup failure message including the assigned gNB-DU ID, the migrating IAB-node DU may configure the migrating IAB-node based on the assigned gNB-DU ID.

[0068] In another embodiment, the configuration information may include NR PCI. The number of NR PCIs may be limited, and the wireless network may need to reuse a limited number of NR PCIs in reality, resulting in PCI confusion. When the migrating IAB-node DU sends an F1 establishment request message including a previous NR PCI to the target IAB-anchor CU, the target IAB-anchor CU may determine a conflict when the previous NR PCI from the migrating IAB-node is the same as one of the other connected IAB-nodes. In response to the conflict, the target IAB-anchor CU sets the cause value to unknown or PCI conflict. After receiving the F1 establishment failure message including the allocated NR PCI, the migrating IAB-node DU may activate the cell indicated by the NR CGI and reconfigure the cell indicated by the NR PCI.

[0069] In another embodiment, the configuration information may include an NR CGI. The NR CGI may include a PLMN ID and an NR cell ID. The NR cell ID may also include a gNB ID and a cell ID within the gNB. The migrating IAB-node DU sends an F1 setup request message including a previous NR CGI to the target IAB-anchor CU. The previous NR CGI may include a newly constructed NR cell ID, which includes the target IAB-anchor ID and the previous cell ID within the source IAB-anchor. When the previous cell ID within the source IAB-anchor is the same as the cell ID of any other IAB-node within the target IAB-anchor, the target IAB-node may determine a conflict. In response to the conflict, the target IAB-anchor CU sets the cause value to unknown or CGI conflict. After receiving the F1 setup failure message including the allocated NR CGI, the migrating IAB-node DU may activate the cell indicated by the NR CGI and reconfigure the cell indicated by the NR PCI.

[0070] refer to Figure 8The present disclosure describes various embodiments of a method 800 for updating the NR PCI and NR CGI of a migrating IAB-node during inter-anchor migration using an F1 Setup Response message including a list of cells to be modified. The method may address challenges / problems associated with the presence of conflicts in both NR PCI and / or NR CGI.

[0071] Method 800 may include some or all of the following steps: Step 810: After migrating from a source IAB-anchor point to a target IAB-anchor point, the migrating IAB-node DU sends an F1 establishment request message to the target IAB-anchor point CU, the F1 establishment request message including the previous NR PCI and NR CGI of the migrating IAB-node before the migration; Step 820: The target IAB-anchor point CU sends an F1 establishment response message to the migrating IAB-node DU in response to a conflict with the NR PCI and NR CGI, the F1 establishment response message including a list of cells to be modified, the list including the previous PCI and / or the previous CGI, as well as the NR PCI and / or the NR CGI; Step 830: The migrating IAB-node may regard the allocated old PCI and / or NR PCI and NR CGI as a physical cell ID and a gNB-DU identifier; Step 840: The migrating IAB-node may activate the cell indicated by the allocated NR CGI and reconfigure the cell indicated by the allocated NR PCI. In the list of cells to be modified, the NR PCI corresponds to the previous PCI; and the NR CGI corresponds to the previous CGI.

[0072] In one embodiment, in response to a CGI conflict only, the cell list to be modified may include the previous CGI, NRPCI, and NR CGI. In another embodiment, in response to a PCI conflict only, the cell list to be modified may include the previous PCI, NR PCI, and NR CGI. In another embodiment, in response to a PCI conflict and a CGI conflict, the cell list to be modified may include the previous PCI, the previous CGI, NR PCI, and NR CGI.

[0073] The present disclosure describes methods, apparatus, and computer-readable media for wireless communications. The present disclosure addresses the problem of updating access backhaul integrated (IAB) node configuration information during inter-anchor migration. The methods, devices, and computer-readable media described in the present disclosure can facilitate the performance of wireless communications by sending new configuration information to a migrating IAB-node using a dedicated RRC message, or using an F1-AP message, or using an F1 setup failure message during inter-anchor migration, thereby improving migration efficiency and overall wireless network performance. The methods, devices, and computer-readable media described in the present disclosure can improve the overall efficiency of a wireless communication system.

[0074] References throughout this specification to features, advantages, or similar language do not imply that all features and advantages that may be achieved with the present solution should or are included in any single embodiment thereof. Rather, language referring to features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussion of features and advantages and similar language throughout this specification may, but does not necessarily, refer to the same embodiment.

[0075] In addition, the features, advantages, and characteristics of the present solution may be combined in any suitable manner in one or more embodiments. One of ordinary skill in the relevant art will recognize that, based on the description herein, the present solution may be practiced without one or more specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present solution.

Claims

1. A method for wireless communication, comprising: During inter-anchor migration from a source IAB-anchor to a target IAB-anchor, the configuration information of the migration access backhaul integrated node (IAB-Node) is updated by the following steps: The target IAB-anchor point centralized unit CU sends an F1-AP message to the migration IAB-node distributed unit DU, wherein the F1-AP message includes new configuration information, and the new configuration information includes an NR cell global identifier CGI, The F1-AP message also includes previous configuration information, and the previous configuration information includes a previous CGI.

2. The method according to claim 1, wherein: The new configuration information includes a new generation wireless access network node DU (gNB-DU) identification ID.

3. A device for wireless communication, comprising: a memory for storing instructions; and a processor in communication with the memory, wherein: When the processor executes the instructions, the processor is configured to cause the device to perform: During the inter-anchor migration from the source IAB-anchor to the device, the configuration information of the migration integrated access backhaul node (IAB-node) is updated by the following steps: The centralized unit CU of the device sends an F1-AP message to the migration IAB-node distributed unit DU, wherein the F1-AP message includes new configuration information, and the new configuration information includes an NR cell global identifier CGI, The F1-AP message also includes previous configuration information, and the previous configuration information includes a previous CGI.

4. The device according to claim 3, wherein: The new configuration information includes a new generation wireless access network node DU (gNB-DU) identification ID.

5. A computer program product comprising a computer readable program medium storing instructions, wherein: When executed by a processor, the instructions are configured to cause the processor to perform the following steps: During inter-anchor migration from a source IAB-anchor to a target IAB-anchor, the configuration information of the migration access backhaul integrated node (IAB-Node) is updated by the following steps: The target IAB-anchor point centralized unit CU sends an F1-AP message to the migration IAB-node distributed unit DU, wherein the F1-AP message includes new configuration information, and the new configuration information includes an NR cell global identifier CGI, The F1-AP message also includes previous configuration information, and the previous configuration information includes a previous CGI.

6. The computer program product of claim 5, wherein: The new configuration information new generation wireless access network node DU (gNB-DU) identification ID.

Images