WO2022151086A1 - 集成的接入和回传的通信方法以及装置 - Google Patents

集成的接入和回传的通信方法以及装置 Download PDF

Info

Publication number
WO2022151086A1
WO2022151086A1 PCT/CN2021/071577 CN2021071577W WO2022151086A1 WO 2022151086 A1 WO2022151086 A1 WO 2022151086A1 CN 2021071577 W CN2021071577 W CN 2021071577W WO 2022151086 A1 WO2022151086 A1 WO 2022151086A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
node
indication information
target
terminal device
Prior art date
Application number
PCT/CN2021/071577
Other languages
English (en)
French (fr)
Inventor
李国荣
贾美艺
路杨
易粟
Original Assignee
富士通株式会社
李国荣
贾美艺
路杨
易粟
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 富士通株式会社, 李国荣, 贾美艺, 路杨, 易粟 filed Critical 富士通株式会社
Priority to JP2023542006A priority Critical patent/JP2024502623A/ja
Priority to PCT/CN2021/071577 priority patent/WO2022151086A1/zh
Priority to CN202180088990.7A priority patent/CN116686335A/zh
Publication of WO2022151086A1 publication Critical patent/WO2022151086A1/zh
Priority to US18/220,345 priority patent/US20230354136A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H04W36/362—Conditional handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • H04B7/06964—Re-selection of one or more beams after beam failure

Definitions

  • the embodiments of the present application relate to the field of communication technologies.
  • IAB Integrated access and backhaul
  • RAN Radio Access Network
  • IAB-node IAB node
  • IAB host IAB-donor
  • IAB host IAB-donor
  • the backhaul may occur via a single hop or multiple hops.
  • the IAB node supports the function of gNB-DU (Distributed Unit, distributed unit), that is, IAB-DU.
  • the IAB-DU terminates the NR access interface to the terminal equipment and the next-hop IAB node, and terminates the F1 protocol of the gNB-CU (Centralized Unit, centralized unit) function on the IAB-donor.
  • IAB-node DUs may also be referred to as IAB-DUs.
  • the IAB node In addition to the gNB-DU function, the IAB node also supports a part of terminal equipment functions (UE functions), which can be called IAB-MT.
  • the IAB-MT includes, for example, Physical Layer, Layer 2 (L2), Radio Resource Control (RRC, Radio Resource Control) and Non-Access-Stratum (NAS, Non-Access-Stratum) functions to connect to another IAB node or IAB-
  • L2 Physical Layer
  • RRC Radio Resource Control
  • NAS Non-Access-Stratum
  • An IAB node is connected to an IAB-donor by one or more hops.
  • the IAB-donor is the root node, and the adjacent nodes on the IAB-DU interface of the IAB node are called the descendant node (descendant node or child node) of the IAB node, that is, the IAB child node (descendant IAB-node) , the adjacent node on the IAB-MT interface is called the parent node, that is, the IAB parent node (parent IAB-node).
  • the direction to the child node is further referred to as downstream, while the direction to the parent node is referred to as upstream.
  • the IAB-donor performs centralized resource, topology and routing management for this IAB topology.
  • inter-centralized unit inter-centralized unit
  • the IAB sub-node or terminal device migrates together with the IAB node after recovery or after handover (or referred to as post-migration).
  • the IAB child node or terminal device may not actively initiate reconstruction, so the configuration information of the CU (for example, the security key (key) will not be updated. ) or other parameters), resulting in failure to communicate properly with the target CU.
  • embodiments of the present application provide an integrated access and backhaul (IAB) communication method and apparatus.
  • IAB integrated access and backhaul
  • an integrated access and backhaul (IAB) communication method including:
  • the IAB sub-node or the terminal device receives the indication information sent by the network device; the indication information is used when the IAB sub-node or the IAB node where the terminal device is located performs cross-centralized unit (inter-CU) recovery or migration , instructing the IAB sub-node or terminal device to consider that a radio link failure (RLF) is detected or instructing the IAB sub-node or terminal device to initiate connection re-establishment; and
  • RLF radio link failure
  • the IAB sub-node or terminal device initiates a radio link failure recovery process or a connection re-establishment process.
  • an integrated access and backhaul (IAB) communication device including:
  • a receiving part which receives the indication information sent by the network device; the indication information is used to indicate that the IAB child node or the IAB node where the terminal device is located performs cross-centralized unit (inter-CU) recovery or migration.
  • the IAB sub-node or terminal device considers that a radio link failure (RLF) is detected or instructs the IAB sub-node or terminal device to initiate connection re-establishment; and
  • RLF radio link failure
  • a processing unit which initiates a radio link failure recovery process or a connection re-establishment process.
  • an integrated access and backhaul (IAB) communication method including:
  • the IAB sub-node or the terminal device receives the indication information sent by the network device; the indication information is used when the IAB sub-node or the IAB node where the terminal device is located performs cross-centralized unit (inter-CU) recovery or migration , indicating the configuration information of the target CU corresponding to the IAB sub-node or terminal device; and
  • inter-CU cross-centralized unit
  • the IAB sub-node or terminal device communicates according to the configuration information of the target CU.
  • an integrated access and backhaul (IAB) communication device including:
  • the indication information is used to indicate that the IAB child node or the IAB node where the terminal device is located performs cross-centralized unit (inter-CU) recovery or migration.
  • inter-CU cross-centralized unit
  • a processing unit which communicates according to the configuration information of the target CU.
  • the IAB sub-node or the terminal device receives the indication information sent by the network device, and initiates a wireless link failure recovery process or a connection re-establishment process according to the indication information; or, the IAB sub-node or the terminal device receives The indication information sent by the network device, where the indication information indicates the configuration information of the corresponding target CU, and the communication is performed according to the configuration information of the target CU. Therefore, in the case of supporting inter-CU recovery or handover, even if the IAB child node or terminal device does not change the serving IAB node, the IAB child node or terminal device will update the configuration information of the CU, so that it can correctly match the target CU. communication.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of the overall architecture of the IAB according to an embodiment of the present application.
  • FIG 3 is another schematic diagram of the overall architecture of the IAB according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of the relationship between a child node and a parent node in an IAB network according to an embodiment of the present application
  • Fig. 5 is a schematic diagram of the protocol stack of the F1-U interface between IAB-DU and IAB-donor-CU;
  • Fig. 6 is a schematic diagram of the protocol stack of the F1-C interface between IAB-DU and IAB-donor-CU;
  • FIG. 7 is a schematic diagram of a protocol stack of an SRB between an IAB-MT and an IAB-donor-CU according to an embodiment of the present application;
  • Fig. 8 is a schematic diagram of the CHO process of the Inter-CU of IAB-node
  • Fig. 9 is a schematic diagram of the RLF recovery process of the Inter-CU of IAB-node
  • FIG. 10 is an example diagram of an inter-CU switching or recovery scenario according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a communication method of an IAB according to an embodiment of the present application.
  • FIG. 12 is another schematic diagram of a communication method of an IAB according to an embodiment of the present application.
  • FIG. 13 is another schematic diagram of a communication method of an IAB according to an embodiment of the present application.
  • FIG. 14 is another schematic diagram of a communication method of an IAB according to an embodiment of the present application.
  • 15 is another schematic diagram of a communication method of an IAB according to an embodiment of the present application.
  • 16 is another schematic diagram of a communication method of an IAB according to an embodiment of the present application.
  • 17 is another schematic diagram of a communication method of an IAB according to an embodiment of the present application.
  • FIG. 18 is another schematic diagram of a communication method of an IAB according to an embodiment of the present application.
  • FIG. 19 is another schematic diagram of a communication method of an IAB according to an embodiment of the present application.
  • FIG. 20 is a schematic diagram of a scenario of a communication method of an IAB according to an embodiment of the present application.
  • 21 is a schematic diagram of a communication device of an IAB according to an embodiment of the present application.
  • FIG. 22 is another schematic diagram of a communication device of an IAB according to an embodiment of the present application.
  • FIG. 23 is a schematic diagram of a network device according to an embodiment of the present application.
  • FIG. 24 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements in terms of numelation, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be referred to by these terms restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed items.
  • the terms “comprising”, “including”, “having”, etc. refer to the presence of stated features, elements, elements or components, but do not preclude the presence or addition of one or more other features, elements, elements or components.
  • the term "communication network” or “wireless communication network” may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE, Long Term Evolution), Long Term Evolution Enhanced (LTE-A, LTE- Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access) and so on.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution Enhanced
  • WCDMA Wideband Code Division Multiple Access
  • High-Speed Packet Access High-Speed Packet Access
  • HSPA High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to communication protocols at any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G , New Radio (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
  • Network device refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • Network devices may include but are not limited to the following devices: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobility management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller) and so on.
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include a remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low power node (such as femeto, pico, etc.), IAB (Integrated Access and Backhaul) node or IAB-DU or IAB-donor.
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low power node such as femeto, pico, etc.
  • IAB Integrated Access and Backhaul node or IAB-DU or IAB-donor.
  • base station may include some or all of their functions, each base station may provide communication coverage for a particular geographic area.
  • the term "cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used. The terms “cell”
  • the term "User Equipment” (UE, User Equipment) or “Terminal Equipment” (TE, Terminal Equipment or Terminal Device), for example, refers to a device that accesses a communication network through a network device and receives network services.
  • Terminal equipment may be fixed or mobile, and may also be referred to as Mobile Station (MS, Mobile Station), Terminal, Subscriber Station (SS, Subscriber Station), Access Terminal (AT, Access Terminal), IAB-MT, Station (station), etc.
  • the terminal device may include but is not limited to the following devices: Cellular Phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • Cellular Phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication device
  • handheld device machine type communication device
  • laptop computer Cordless phones, smartphones, smart watches, digital cameras, and more.
  • the terminal device may also be a machine or device that performs monitoring or measurement, such as but not limited to: Machine Type Communication (MTC, Machine Type Communication) terminals, Vehicle communication terminal, device to device (D2D, Device to Device) terminal, machine to machine (M2M, Machine to Machine) terminal, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • network side refers to one side of the network, which may be a certain base station, and may also include one or more network devices as described above.
  • user side or “terminal side” or “terminal device side” refers to the side of a user or terminal, which may be a certain UE, or may include one or more terminal devices as above.
  • equipment may refer to network equipment or terminal equipment.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application, which schematically illustrates a situation in which a terminal device and a network device are used as an example.
  • a communication system 100 may include a network device 101 and a terminal device 102 .
  • FIG. 1 only takes one terminal device and one network device as an example for description, but the embodiment of the present application is not limited to this, for example, there may be multiple terminal devices.
  • Enhanced Mobile Broadband eMBB, enhanced Mobile Broadband
  • Massive Machine Type Communication mMTC, massive Machine Type Communication
  • Ultra-Reliable and Low Latency Communication URLLC, Ultra-Reliable and Low.
  • -Latency Communication etc.
  • FIG. 2 is a schematic diagram of an overall architecture of an IAB according to an embodiment of the present application; as shown in FIG. 2 , the overall architecture of the IAB uses a standalone mode.
  • FIG. 3 is another schematic diagram of the overall architecture of the IAB according to the embodiment of the present application; as shown in FIG. 3 , the overall architecture of the IAB uses a dual-connection (EN-DC) mode; in the dual-connection mode, the IAB node is connected to the One MeNB, IAB host as SgNB to terminate X2-C.
  • EN-DC dual-connection
  • FIG. 4 is a schematic diagram of the relationship between a child node and a parent node in an IAB network according to an embodiment of the present application; as shown in FIG. 4 , the direction from the IAB node to the child node is further referred to as a downstream (downstream), and the direction to the parent node called upstream.
  • FIG. 5 is a schematic diagram of the protocol stack of the F1-U interface between the IAB-DU and the IAB-donor-CU
  • FIG. 6 is a schematic diagram of the protocol stack of the F1-C interface between the IAB-DU and the IAB-donor-CU.
  • F1-U and F1-C are described by taking 2-hop backhaul as an example.
  • F1-U and F1-C use the IP transport layer between IAB-DU and IAB-donor-CU, in addition, F1-U and F1-C have security protection.
  • a Backhaul Adaptation Protocol (BAP, Backhaul Adaptation Protocol) layer is introduced.
  • the BAP sublayer contains a BAP entity located in the MT function and another co-located BAP entity located in the DU function.
  • the IP layer performs wireless backhaul through the BAP sublayer to ensure multi-hop routing; the IP layer can also be used for non-F1 services, such as Operation Administration and Maintenance (OAM) services.
  • OAM Operation Administration and Maintenance
  • BAP PDUs are transmitted by a BH Radio Link Control (RLC, Radio Link Control) channel (channel); on each BH link (BH link)
  • RLC Radio Link Control
  • BH link BH link
  • multiple BH RLC channels can be configured, which allows traffic prioritization and Quality of Service (QoS) enforcement.
  • QoS Quality of Service
  • the BAP entity on each IAB node and IAB-donor-DU performs the mapping of the BH RLC channel of the BAP PDUs.
  • FIG. 7 is a schematic diagram of a protocol stack of a signaling radio bearer (SRB, Signalling Radio Bearer) between an IAB-MT and an IAB-donor-CU according to an embodiment of the present application.
  • IAB-MT and IAB-donor-CU establish SRBs for carrying RRC and NAS.
  • RRC layer and the Packet Data Convergence Protocol (PDCP, Packet Data Convergence Protocol) layer of the IAB sub-node for example, the IAB-MT of the IAB node 2 or the terminal device at the opposite end (network side) are located on the CU.
  • PDCP Packet Data Convergence Protocol
  • the IAB network is schematically described above, and the following is a schematic description of recovery and handover.
  • the terminal device sends a measurement report (measurement report) message to the network; if the network device determines that the terminal device needs to be handed over, it will pass the relevant configuration of the target cell through the RRC reconfiguration message (carrying the reconfiguration message). with sync) to the end device.
  • the terminal device receives the RRC reconfiguration message, it starts to perform the handover process.
  • the handover may fail because the measurement report sent by the terminal device may not be correctly received by the network device, or the RRC reconfiguration message sent by the network device may not be correctly received by the terminal device.
  • conditional handover in order to improve handover reliability and reduce handover failures, conditional handover (CHO, conditional handover) is introduced.
  • the network device configures the terminal device with one or more candidate target cells (eg SpCell) in a conditional reconfiguration.
  • the terminal device evaluates the conditions corresponding to each configured candidate target cell. If a condition corresponding to a target candidate cell (ie, a measurement event) is satisfied, the terminal device initiates a conditional handover to this cell, applying the conditional reconfiguration related to this cell.
  • 3GPP has agreed to use Rel-16CHO as the baseline in the IAB.
  • FIG. 8 is a schematic diagram of the CHO process of the Inter-CU of the IAB-node.
  • the source CU decides to perform CHO configuration on the IAB node (801), and then the source CU sends a handover request message to one or more target CUs (or target donor CUs) (802).
  • the UE context establishment process (803 and 804) is performed between the target CU and the target IAB parent node to prepare the relevant configuration and/or resources in the target IAB parent node for the IAB node.
  • the target CU then sends a handover request confirmation message to the source CU (805), which carries the conditional reconfiguration of the target cell.
  • the source CU After receiving the handover request confirmation message of one or more target CUs, the source CU sends an RRC reconfiguration (RRC reconfiguration) message to the IAB node through the source IAB parent node (807), which includes the configuration of one or more target cells and corresponding conditions.
  • RRC reconfiguration RRC reconfiguration
  • the IAB node receives and stores the RRC reconfiguration message, and replies with an RRC reconfiguration complete message (809).
  • the IAB node evaluates the conditions according to the configuration of one or more target cells and the corresponding conditions included in the RRC reconfiguration message. When it is considered that the condition is met, the source CU can be detached and the stored configuration of the target cell that meets the condition can be applied, and a random access to the target cell can be initiated through a random access channel (RACH).
  • RACH random access channel
  • the IAB node may perform CHO. After the IAB node is successfully migrated to the target CU, the target CU may notify the source CU to release the context of the IAB node, as shown by 813 to 814 in FIG. 8 .
  • the IAB node can also perform Inter-CU Radio Link Failure (RLF, Radio Link Failure) recovery (recovery).
  • Fig. 9 is a schematic diagram of the RLF recovery process of the Inter-CU of the IAB-node.
  • the source IAB parent node may include initial parent IAB-node, intermediate hop IAB-node on At least one of initial path and initial IAB-donor-DU
  • the target IAB parent node may include at least one of new parent IAB-node, intermediate hop IAB-node on new path and new IAB-donor-DU.
  • the inter-CURLF recovery process of IAB-node can include:
  • IAB node detects the RLF of (BH, backhaul);
  • the IAB MT performs synchronization and RACH to the target IAB parent node (also known as the new IAB parent node) served by the target IAB-donor CU (also known as the new IAB-donor CU) .
  • the recovered IAB MT sends an RRC reconstruction request message to the target IAB-donor CU through the target IAB parent node;
  • the target IAB-donor CU obtains the UE context (context) of the IAB MT from the source IAB-donor CU (also known as the old IAB-donor CU) through the Xn interface;
  • the target IAB-donor CU initiates a UE context establishment process to the target IAB parent node to establish an F1 logical connection to the restored IAB-MT.
  • the target IAB-donor CU sends an RRC reconstruction message to the IAB-MT through the target IAB parent node;
  • the restored IAB MT sends an RRC reconstruction complete message to the target IAB-donor CU through the target IAB parent node;
  • the target IAB-donor CU sends an RRC reconfiguration message to the restored IAB-MT through the target IAB parent node, and the restored IAB-MT responds with the RRC reconfiguration complete message.
  • the IAB-donor CU configures the BH RLC channel (channels) and BAP sublayer routing (routing) entries on the new path (path) between the target IAB parent node and the target IAB-donor DU, and the pair on the target IAB-donor DU. DL mapping for the new path of the restored IAB-node.
  • the DU of the restored IAB node establishes or redirects the F1-C connection with the target CU, and establishes or updates the F1 interface context, the UE context, and the like.
  • the IAB-donor CU updates the F1-U connection to the restored IAB-node, eg, updates the UL BH information associated with each GTP tunnel.
  • the target IAB-donor CU sends a UE context release message to instruct the source IAB-donor CU to release the resources of the restored IAB-node.
  • the source IAB-donor CU sends a UE context release complete message to the source IAB parent node.
  • the source IAB parent node releases the restored IAB-MT context, and responds to the UE context release complete message.
  • the source IAB-donor CU releases the routing entries of the BH RLC channel and the BAP sublayer on the source path between the source IAB parent node and the source IAB-donor DU.
  • FIG. 10 is an example diagram of a scenario of inter-CU switching or restoration according to an embodiment of the present application.
  • the physical layer cell identity PCI, Physical Cell Identity
  • frequency of the cell provided by the DU of the IAB-node may remain unchanged. If the IAB child node or terminal device of the IAB-node is still under the coverage of the original cell, the topology relationship can remain unchanged, and the IAB child node or terminal device is migrated to the target CU along with the IAB node.
  • the target CU the target IAB-donor CU
  • the target CU the target IAB-donor CU
  • security parameters such as keys, etc.
  • the IAB child node or terminal device may not initiate the reconstruction process to obtain the configuration information of the target CU, and also cannot correctly receive the target CU using the configuration of the target CU ( For example, the configuration information sent by the security parameter and/or the security algorithm, etc.), therefore, the configuration information of the target CU will not be updated, resulting in failure to communicate with the target CU correctly.
  • FIG. 11 is a schematic diagram of an IAB communication method according to an embodiment of the present application. As shown in FIG. 11 , the method includes:
  • the IAB sub-node or the terminal device receives the indication information sent by the network device; the indication information is used to perform cross-centralized unit (inter-CU) restoration or migration at the IAB node where the IAB sub-node or the terminal device is located.
  • inter-CU cross-centralized unit
  • RLF radio link failure
  • the IAB sub-node or terminal device initiates a radio link failure recovery process or a connection re-establishment process.
  • FIG. 11 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order of the various operations can be adjusted appropriately, and other operations can be added or some of the operations can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the description of the above-mentioned FIG. 11 .
  • the IAB sub-node or the terminal device initiates the radio link failure recovery process or the connection re-establishment process, and can obtain the configuration information of the target CU.
  • the IAB sub-node or terminal device can update the configuration information of the target CU, so as to be able to communicate with the target CU correctly.
  • FIG. 8 and FIG. 9 For the specific content of the radio link failure recovery process or the connection re-establishment process, reference may be made to the embodiments described later, and also to related technologies, for example, FIG. 8 and FIG. 9 .
  • the indication information is first indication information sent by an IAB node performing radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • RLF radio link failure
  • CHO conditional handover
  • an IAB node during or after the RLF recovery or CHO process can send the first indication information to the affiliated IAB sub-node or terminal device; After receiving the first indication information, the IAB sub-node or the terminal device considers that a radio link failure (RLF) is detected or initiates a connection re-establishment process.
  • RLF radio link failure
  • the IAB node receives a RRC re-establishment sent by a target centralized unit (Target CU) (RRC reestablishment) message, or establishing an F1 interface with the target CU, or receiving backhaul (BH) configuration information, the IAB node sends the first indication information to the IAB sub-node or terminal device.
  • the target CU is the donor CU where the cell where the IAB node performs RLF recovery is located, for example, the donor CU where the cell selected by the IAB node for the RRC connection reestablishment process is located.
  • the moment when the IAB node sends the first indication information may be any time point from 907 to 915 in FIG. 9 .
  • the moment when the target CU and the restored IAB-DU establish or rebuild or update the F1 interface context such as the moment when the gNB DU configuration update process or the gNB CU configuration update process; or the target CU and the restored IAB-DU establish or rebuild or update a pair.
  • the BH configuration information which may include, for example, the target IAB parent node and the target IAB- BH RLC channels and BAP sublayer routing entries on the new path between donor DUs, or DL mapping of the new path to the restored IAB-node on the target IAB-donor DU; or update the F1-U connection (e.g. GTP tunnel information) moment, and so on.
  • the IAB node sends the first indication information to the IAB sub-node or terminal device after a radio link failure (RLF) recovery process is performed across an inter-CU.
  • the target CU is the donor CU where the cell where the IAB node performs RLF recovery is located, for example, the donor CU where the cell selected by the IAB node for the RRC connection reestablishment process is located.
  • the IAB sub-node or terminal device when the IAB sub-node or terminal device is single-connected, or the IAB sub-node or terminal device is configured with dual connections and the IAB node is the IAB sub-node or terminal device
  • the IAB sub-node or terminal device considers (determines) that a radio link failure (RLF) is detected for the MCG.
  • RLF radio link failure
  • the IAB sub-node or the terminal device initiates a radio link failure recovery process, including: when the IAB sub-node has activated access stratum security (AS security) and SRB2 has been established, or the terminal When the access layer security (AS security) has been activated and the SRB2 and at least one data radio bearer (DRB) have been established, the timer (T316) is configured and the SCG transmission is not suspended.
  • the IAB sub-node or terminal device initiates the MCG failure information (MCG failure information) process to report the failure of the MCG radio link, otherwise initiates the connection re-establishment process.
  • MCG failure information MCG failure information
  • the IAB sub-node or terminal device when configured with dual connectivity and the IAB node is a secondary cell group (SCG) of the IAB sub-node or terminal device, the IAB sub-node or The terminal device considers (determines) that a radio link failure (RLF) is detected for the SCG.
  • SCG secondary cell group
  • RLF radio link failure
  • the IAB sub-node or the terminal device initiates the radio link failure recovery process, including: in the case that the MCG transmission is not suspended, the IAB sub-node or the terminal device initiates an SCG failure information (SCG failure information) process to Report SCG radio link failure, otherwise initiate the connection re-establishment procedure.
  • SCG failure information SCG failure information
  • the IAB sub-node or terminal device may initiate a CHO procedure.
  • the IAB node in the process of conditional handover (CHO) migration across centralized units (inter-CUs), the IAB node initiates a conditional handover (CHO), or sends a radio resource control reconfiguration complete (RRC reconfiguration complete). ) message, or establishing an F1 interface with the target CU, or receiving BH configuration information, the IAB node sends the first indication information to the IAB sub-node or terminal device.
  • CHO conditional handover
  • RRC reconfiguration complete radio resource control reconfiguration complete
  • the moment when the IAB node sends the first indication information may be any time point from the HO condition evaluation to 811 in FIG. 8 .
  • the moment when the IAB-node initiates CHO for example, detach from source or starts to apply the stored conditional reconfiguration of the target cell that meets the conditions or starts to initiate RACH to the target cell
  • the moment when it sends an RRC reconfiguration complete message or when it receives an RRC
  • the time of RLC layer confirmation or HARQ confirmation of the reconfiguration complete message or the time when the DU of the IAB-node sends the F1AP setup request message to the target CU, or the time when the F1 setup response message is received from the target CU, or the time when the target CU and the IAB-node the moment when the SCTP connection between the two is established, or when the F1-C connection is switched to use the new TNL address of the IAB-node and the TNL address of the target CU,
  • the BH configuration information may include, for example, the connection between the target IAB parent node and the target IAB-donor DU BH RLC channels and BAP sublayer routing entries on the new path, or DL mapping of the new path to the IAB-node on the target IAB-donor DU; or the time to update the F1-U connection (e.g. GTP tunnel information), etc.
  • the IAB node sends the first indication information to the IAB sub-node or terminal device after performing a conditional handover (CHO) migration process across a centralized unit (inter-CU).
  • CHO conditional handover
  • the first indication information includes at least one or any combination of the following: Backhaul Adaptation Protocol (BAP) Protocol Data Unit (PDU), Radio Link Control (RLC) PDU, Medium Access Control (MAC) ) Control Cell (CE), Medium Access Control (MAC) subheader, physical layer signaling.
  • BAP Backhaul Adaptation Protocol
  • PDU Protocol Data Unit
  • RLC Radio Link Control
  • MAC Medium Access Control
  • CE Control Cell
  • MAC Medium Access Control
  • a new BAP control PDU can be defined, or a BH RLF indication can be used, such as a BAP control PDU of type 3 BH RLF indication, or a new RLC control PDU can be defined.
  • a BH RLF indication can be used, such as a BAP control PDU of type 3 BH RLF indication, or a new RLC control PDU can be defined.
  • the content of the BH RLF indication reference may also be made to the embodiments of the third aspect described later.
  • a new MAC CE may be defined, and the MAC CE corresponds to a new LCID in a subheader; or a new MAC subheader may be defined, and the MAC subheader adopts a new LCID.
  • a field in DCI may be used, group common DCI, common DCI, UE-specific DCI, or Paging-DCI, etc. may be used, and the field may be 1 bit.
  • the first indication information may also indicate whether the donor CU of the IAB node has changed, or indicate whether the IAB node has performed the same CU migration (intra-CU migration) or inter-CU migration (inter-CU migration) .
  • the first indication information includes at least one of the following: a CU change indication, an identification of the target CU, an indication of initiating a reconstruction process, and the like.
  • the indication information is that the inter-centralized unit (inter-CU) performs radio link failure (RLF) recovery or conditional handover (CHO) migration of the source centralized unit (Source CU) after recovery or migration
  • RLF radio link failure
  • CHO conditional handover
  • FIG. 13 is another schematic diagram of an IAB communication method according to an embodiment of the present application.
  • the source CU may send third indication information to the IAB sub-node or terminal device; the IAB sub-node or terminal device receives the third indication information.
  • the indication information it is considered that a radio link failure (RLF) is detected or a connection re-establishment process is initiated.
  • RLF radio link failure
  • the source centralized unit (CU) sends the third indication information to the target CU or the distributed unit (DU) of the IAB node through the Xn interface, and the target CU or the The DU sends the third indication information to the IAB sub-node or terminal device.
  • the source CU can send the RRC message carrying the third indication information to the target IAB-donor CU through the Xn interface, and the target IAB-donor CU sends the third indication information to the target IAB-donor CU through the DL RRC MESSAGE TRANSFER After the handover or the restored IAB node, the IAB node sends the third indication information to the IAB sub-node or the terminal device through the RRC message or the PDCP control PDU.
  • the IAB sub-node or terminal device may consider that a radio link failure (RLF) is detected or initiate a connection re-establishment process; in addition, the IAB sub-node or terminal device may also send a response message or a completion message to the post-handover or recovery After the IAB node (optional), the IAB node can also send information to the target IAB-donor CU through the UL RRC MESSAGE TRANSFER (optional).
  • RLF radio link failure
  • the source CU in the process of radio link failure (RLF) recovery across centralized units (inter-CUs), when the source CU receives a context retrieval request message sent by the target CU, or to the When the target CU sends a context retrieval response message or receives a context release message sent by the target CU, the source CU sends the third indication information.
  • RLF radio link failure
  • the time when the source CU sends the third indication information can be any of the following time points: for example, the time when the source CU receives the retrieve UE context request message sent by the target IAB-donor CU through the Xn interface, or The moment when the retrieve UE context response message is sent to the target IAB-donor CU through the Xn interface, or when or after the UE context release message sent by the target IAB-donor CU is received, and so on.
  • the sending time of the third indication information includes: the time when the restored IAB-MT sends the RRC re-establishment request message, or the time when the restored IAB-MT receives the RRC re-establishment message.
  • the moment when the target CU and the restored IAB-DU establish or rebuild or update the F1 interface context such as the moment when the gNB DU configuration update process or the gNB CU configuration update process; or the target CU and the restored IAB-DU establish or rebuild or update a pair.
  • the BH configuration information which may include, for example, the target IAB parent node and the target IAB- BH RLC channels and BAP sublayer routing entries on the new path between donor DUs, or DL mapping of the new path to the restored IAB-node on the target IAB-donor DU; or update the F1-U connection (e.g. GTP tunnel information) moment, and so on.
  • the source CU sends the third indication information after an inter-centralized unit (inter-CU) radio link failure (RLF) recovery procedure.
  • inter-CU inter-centralized unit
  • RLF radio link failure
  • the IAB sub-node or terminal device when the IAB sub-node or terminal device is single-connected, or the IAB sub-node or terminal device is configured with dual connections and the IAB node is the IAB sub-node or terminal device
  • the IAB child node or terminal device determines (consides) that a radio link failure (RLF) is detected for the MCG.
  • RLF radio link failure
  • the IAB sub-node or the terminal device initiates a radio link failure recovery process, including: when the IAB sub-node has activated access stratum security (AS security) and SRB2 has been established, or the terminal When the access layer security (AS security) has been activated and the SRB2 and at least one data radio bearer (DRB) have been established, the timer (T316) is configured and the SCG transmission is not suspended. And when the primary serving cell change (PSCell change) is not in progress, the IAB sub-node or terminal device initiates the MCG failure information process to report the failure of the MCG radio link, otherwise initiates the connection reestablishment process.
  • AS security access stratum security
  • DRB data radio bearer
  • the IAB sub-node or terminal device when the IAB sub-node or terminal device is configured with dual connectivity and the IAB node is a secondary cell group (SCG) of the IAB sub-node or terminal device, the IAB sub-node or The terminal device determines (thinks) that a radio link failure (RLF) is detected for the SCG.
  • SCG secondary cell group
  • RLF radio link failure
  • the IAB sub-node or the terminal device initiates the radio link failure recovery process, including: in the case that the MCG transmission is not suspended, the IAB sub-node or the terminal device initiates the SCG failure information process to report the SCG radio link fails, otherwise the connection re-establishment process is initiated.
  • the source CU in the process of conditional handover (CHO) migration across centralized units (inter-CUs), the source CU sends the third indication in the case of receiving a context release message sent by the target CU information.
  • the moment when the source CU sends the third indication information may be any of the following time points: In 813 of FIG. 8, the moment when the source CU receives the UE context release message sent by the target IAB-donor CU or after.
  • the sending time of the third indication information includes: the IAB-node initiates CHO (for example, detach from source or start to apply the stored conditional reconfiguration of the target cell that meets the conditions or start to initiate the CHO to the target cell).
  • the BH configuration information may include, for example, the connection between the target IAB parent node and the target IAB-donor DU BH RLC channels and BAP sublayer routing entries on the new path, or DL mapping of the new path to the IAB-node on the target IAB-donor DU; or the time to update the F1-U connection (e.g. GTP tunnel information), etc.
  • the source CU sends the third indication information after a conditional handover (CHO) migration process across an inter-CU.
  • CHO conditional handover
  • the third indication information includes at least one or any combination of the following: Packet Data Convergence Protocol (PDCP) protocol data unit (PDU), radio resource control (RRC) message, and F1AP message.
  • PDCP Packet Data Convergence Protocol
  • PDU protocol data unit
  • RRC radio resource control
  • F1AP F1AP message
  • the third indication information may be included in the PDCP PDU (which carries the RRC message or the PDCP control PDU), and encryption and/or integrity protection such as the old key and security algorithm are used; for another example, for the descendant IAB-node, the third The indication information can also be carried in the F1AP message and sent to the DU of the descendant IAB-node.
  • the third indication information may further indicate whether the donor CU of the IAB node has changed, or indicate whether the IAB node has performed the same CU migration (intra-CU migration) or inter-CU migration (inter-CU migration) .
  • the third indication information includes at least one of the following: a CU change indication, an identification of the target CU, an indication of initiating a reconstruction process, and the like.
  • descendant IAB-nodes or the UE may indicate its capability to the CU to indicate whether to support the communication method in the foregoing embodiment.
  • the RRC message can be, for example, an RRC re-establishment message or an RRC reconfiguration message;
  • the F1AP message can be a UE context setup request or a UE context modification request;
  • the Xn message can be an RRC transfer or a Retrieve UE context response, etc.
  • the configuration information of the CU may include at least one or any combination of the following: the configuration of the RRC layer, the configuration of the PDCP layer, the configuration of the RLC layer, the configuration of the MAC layer, the configuration of the physical layer, and the configuration of the BAP layer Configuration.
  • the IAB sub-node or terminal device receives the indication information sent by the network device, and initiates a wireless link failure recovery process or a connection re-establishment process according to the indication information. Therefore, in the case of supporting inter-CU recovery or handover, even if the IAB child node or terminal device does not change the serving IAB node, the IAB child node or terminal device will update the configuration information of the CU, so that it can correctly match the target CU. communication.
  • An embodiment of the present application provides an IAB communication method, which is described from an IAB sub-node or terminal device. The same content as the embodiment of the first aspect will not be repeated.
  • FIG. 14 is a schematic diagram of a communication method of an IAB according to an embodiment of the present application. As shown in FIG. 14 , the method includes:
  • the IAB sub-node or the terminal device receives the indication information sent by the network device; the indication information is used to perform cross-centralized unit (inter-CU) restoration or migration at the IAB node where the IAB sub-node or the terminal device is located.
  • inter-CU cross-centralized unit
  • the configuration information of the target CU corresponding to the IAB sub-node or terminal device is indicated;
  • the IAB sub-node or terminal device communicates according to the configuration information of the target CU.
  • FIG. 14 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order of the various operations can be adjusted appropriately, and other operations can be added or some of the operations can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the description of the above-mentioned FIG. 14 .
  • the IAB sub-node or terminal device receives the configuration information of the target CU sent by the network device, and the IAB sub-node or terminal device can update the configuration information of the CU, thereby being able to communicate with the target CU correctly.
  • the configuration information of the target CU may include at least one or any combination of the following: the configuration of the Radio Resource Control (RRC) layer, the configuration of the Packet Data Convergence Protocol (PDCP) layer, the RLC Layer configuration, MAC layer configuration, physical layer configuration, and BAP layer configuration, the configuration information may include security-related configurations, such as security keys, security algorithms, and security parameters of whether to apply the primary cell group or the secondary cell group.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • the configuration information may include security-related configurations, such as security keys, security algorithms, and security parameters of whether to apply the primary cell group or the secondary cell group.
  • the indication information may be the same as the configuration information of the target CU, for example, the indication information directly includes the configuration information of the target CU; the indication information may also be different from the configuration information of the target CU, for example, the indication information
  • the sequence number or index of the configuration information of the target CU may only be indicated, or the indication information may be a part of the configuration information of the target CU, and so on.
  • the indication information is second indication information sent by the target CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • RLF radio link failure
  • CHO conditional handover
  • the context of the IAB child node or terminal device of the IAB-node after recovery or CHO is sent to the target CU by the source CU (ie, the source donor CU) in advance through the Xn interface.
  • the context of the IAB-node for example, in the case of RLF recovery, it is sent by the source CU to the target CU through the Retrieve UE Context Response message, and in the case of CHO, it is sent from the source CU to the target CU through the Handover Request message .
  • the context of the descendant IAB-node or UE of the restored or migrated IAB-node is sent separately, for example, after the IAB-node is restored or CHO to the target CU, the target CU obtains it from the source CU (for example, after receiving the restoration or CHO)
  • the target CU may send the second indication information to the IAB sub-node or terminal device according to the context of the IAB sub-node or terminal device.
  • the target CU sends a radio resource control reestablishment (RRC reestablishment) message or receives a radio resource
  • RRC reestablishment radio resource control reestablishment
  • the target CU sends the second indication information to the IAB child node or terminal device .
  • the time when the target CU sends the second indication information may be any time point from 907 to 915 in FIG. 9 .
  • the restored IAB-MT sends the RRC re-establishment request message, or when the restored IAB-MT receives the RRC re-establishment message, or when the restored IAB-MT sends the RRC re-establishment complete message, or when the restored IAB-MT sends the RRC re-establishment complete message, or when the restored IAB-MT sends the RRC re-establishment complete message.
  • the moment when the target CU and the restored IAB-DU establish or rebuild or update the F1 interface context such as the moment when the gNB DU configuration update process or the gNB CU configuration update process; or the target CU and the restored IAB-DU establish or rebuild or update a pair.
  • the BH configuration information which may include, for example, the target IAB parent node and the target IAB- BH RLC channels and BAP sublayer routing entries on the new path between donor DUs, or DL mapping of the new path to the restored IAB-node on the target IAB-donor DU; or update the F1-U connection (e.g. GTP tunnel information) moment, and so on.
  • the target CU after a radio link failure (RLF) recovery process is performed across an inter-CU, the target CU sends the second indication information to the IAB sub-node or terminal device.
  • RLF radio link failure
  • the target CU receives a radio resource control reconfiguration complete message, or establishes an F1 interface with the IAB node , or in the case of sending BH configuration information, the target CU sends the second indication information to the IAB sub-node or terminal device.
  • CHO conditional handover
  • the time when the target CU sends the second indication information may be any time point from the HO condition evaluation to 811 in FIG. 8 .
  • the moment when the IAB-node initiates CHO (for example, detach from source or starts to apply the stored conditional reconfiguration of the target cell that meets the conditions or starts to initiate RACH to the target cell), or when it sends an RRC reconfiguration complete message, or when it receives an RRC
  • the BH configuration information may include, for example, the connection between the target IAB parent node and the target IAB-donor DU BH RLC channels and BAP sublayer routing entries on the new path, or DL mapping of the new path to the IAB-node on the target IAB-donor DU; or the time to update the F1-U connection (e.g. GTP tunnel information), etc.
  • the target CU sends the second indication information to the IAB sub-node or terminal device after performing a conditional handover (CHO) migration process across an inter-CU.
  • CHO conditional handover
  • the second indication information indicates configuration information of a Radio Resource Control (RRC) layer and/or a Packet Data Convergence Protocol (PDCP) layer in the target CU.
  • the second indication information includes at least one or any combination of the following information: next hop count (nextHopChainingCount), key set change indication (keySet ChangeIndicator), non-access stratum (NAS) security information (nas-Container ), encryption algorithm (ciphering Algorithm), integrity protection algorithm (integrityProtAlgorithm); but this application is not limited to this.
  • the second indication information may also indicate whether the donor CU of the IAB node has changed, or indicate whether the IAB node has performed the same CU migration (intra-CU migration) or inter-CU migration (inter-CU migration). migration).
  • the second indication information may further include a CU change indication and/or an identifier of a target CU, and the like.
  • the target CU sends the unencrypted or default encrypted second indication information to the IAB sub-node or terminal device through a radio resource control (RRC) message.
  • RRC radio resource control
  • Fig. 15 is another schematic diagram of an IAB communication method according to an embodiment of the present application.
  • the target CU sends an RRC message carrying the second indication information to the restored or switched IAB node through DL RRC MESSAGE TRANSFER
  • the IAB node sends the second indication information to the IAB sub-node or the terminal device through an RRC message.
  • the IAB sub-node or terminal device can obtain the configuration information of the target CU; in addition, the IAB sub-node or terminal device can also send a response message or a completion message to the IAB node after handover or recovery (optional) , the IAB node can also send information to the target IAB-donor CU through UL RRC MESSAGE TRANSFER (optional).
  • the following describes how the IAB sub-node or the terminal device correctly obtains the second indication information.
  • IAB child node or UE will configure lower layers to suspend integrity protection and encryption for SRB1 (configure lower layers to suspend integrity protection and ciphering for SRB1; NOTE: Ciphering is not applied for the subsequent RRCReestablishment message used to resume the connection. An integrity check is performed by lower layers, but merely upon request from RRC). In the embodiment shown in FIG. 15 , since it is not the reconstruction initiated by descendant IAB-nodes or UE, it is necessary to let them suspend the integrity protection and encryption of SRB1, that is, no encryption is performed on the RRC message.
  • the IAB sub-node or terminal device receives a notification message of the IAB node; and the IAB sub-node or terminal device suspends the integrity of the Signaling Radio Bearer (SRB) according to the notification message Protecting and encrypting operations to obtain the second indication information.
  • SRB Signaling Radio Bearer
  • the IAB-node restored by RLF or CHO migrated to notify the descendant IAB-nodes or UE, for example, by signaling at the PHY or MAC or RLC or BAP layer; after receiving the notification, the descendant IAB-nodes or UE suspends the pairing of Integrity protection and encryption for SRB1.
  • the IAB sub-node or terminal device performs decryption and decoding operations on the radio resource control (RRC) message; and in the case of unsuccessful decoding, the radio resource control (RRC) message is not Perform decryption or perform a default decryption operation, and perform a decoding operation to obtain the second indication information.
  • RRC radio resource control
  • the RRC layer of the IAB sub-node or terminal device reports decryption failure and/or integrity check failure at the lower layer (eg PDCP layer)
  • the RRC layer configures the lower layer (eg PDCP) not to apply decryption and/or integrity check to SRB1
  • This PDCP PDU is then decrypted and/or integrity checked, and if the lower layer decryption and/or integrity check is successful, the lower layer passes the message to the RRC layer.
  • the RRC layer of the IAB sub-node or terminal device configures the lower layer (such as PDCP) to perform integrity protection and encryption on SRB1, but if the lower layer decryption fails and/or the integrity check fails, the lower layer does not apply decryption and/or integrity Check, then decrypt and/or integrity check this PDCP PDU, and pass the message to the RRC layer if the lower layer decryption and/or integrity check is successful.
  • the lower layer such as PDCP
  • the above description is given by taking unencrypted as an example, but the present application is not limited to this, for example, it may also be encrypted by default.
  • the encrypted key uses the default key, or the encryption (or security) algorithm is algorithm 0, and so on.
  • the target CU sends the second indication information to the IAB sub-node or the terminal device by using the configuration information of the source CU through a radio resource control (RRC) message.
  • RRC radio resource control
  • the target CU sends the second indication information using the security algorithm and/or security parameters (eg keys) of the source CU (old CU).
  • security parameters eg keys
  • the target CU sends the second indication information to the source CU through an Xn interface, and after the source CU uses the configuration information to process the second indication information, the second indication information is processed by post-recovery or migration The latter path is sent to the IAB sub-node or terminal device.
  • FIG. 16 is another schematic diagram of an IAB communication method according to an embodiment of the present application.
  • the target CU sends an RRC message (the RRC container included in the XnAP message) carrying the second indication information to the source through the Xn interface CU, processed by the source CU using security algorithms and/or security parameters (such as keys) (for example, the PDCP layer of the source CU uses the security algorithms and/or security parameters corresponding to the IAB sub-node or terminal device to perform encryption and/or integrity protection ), send the processed second indication information to the IAB node of recovery or CHO through the F1AP message DL RRC MESSAGE TRANSFER (using a new path), and the IAB node sends the RRC message containing the processed second indication information To the IAB child node or terminal device.
  • security algorithms and/or security parameters such as keys
  • the IAB sub-node or terminal device can obtain the configuration information of the target CU by using the configuration information of the source CU (such as security algorithm and/or security parameters); in addition, the IAB sub-node or terminal device can also send a response message or The completion message is sent to the IAB node after handover or recovery (optional), such as RRC reestablishment complete message or RRC reconfiguration complete message, etc.
  • the IAB node can also send information to the target IAB-donor CU through the F1AP message UL RRC MESSAGE TRANSFER ( optional).
  • the target CU sends the second indication information to the IAB sub-node or terminal device through an F1AP message.
  • FIG. 17 is another schematic diagram of the communication method of the IAB according to the embodiment of the present application.
  • the target CU sends the F1AP message carrying the second indication information to the IAB node of recovery or CHO, and the IAB node passes the PHY,
  • the MAC, RLC or BAP signaling sends the second indication information to the IAB sub-node or terminal device.
  • the second indication information includes NextHopChainingCount
  • a 3-bit field may be included in the PHY, MAC, RLC or BAP signaling to indicate the NextHopChainingCount (representing an integer ranging from 0 to 7).
  • the PHY, MAC, RLC or BAP layer of the IAB sub-node or the terminal device can send the received second indication information to the RRC layer, and the RRC layer performs the operation of updating the configuration information (for example, updating the Keys);
  • the IAB child node or terminal device can also send a response message or completion message or HARQ confirmation or RLC confirmation to the IAB node of recovery or CHO (optional), the IAB node can also send F1AP message to the target IAB-donor CU ( optional).
  • the target CU sends the second indication information to the source CU through an Xn interface
  • the source CU sends the second indication information to the DU of the IAB node through an F1AP message , and is sent by the DU of the IAB node to the IAB sub-node or terminal device.
  • FIG. 18 is another schematic diagram of an IAB communication method according to an embodiment of the present application.
  • the target CU sends the second indication information to the source CU through the Xn interface, and the source CU sends the second indication information through the F1AP message (using a new path)
  • the second indication information is sent to the IAB node after recovery or handover, and the IAB node sends the second indication information to the IAB sub-node or the terminal device through PHY, MAC, RLC or BAP signaling.
  • the IAB sub-node or terminal device can send the second indication information to the RRC layer, and the RRC layer performs the operation of updating the configuration information (for example, updating Keys); in addition, the IAB sub-node or terminal device can also send a response message or completion message to the IAB node after handover or recovery (optional), the IAB node can also send an F1AP message to the target IAB-donor CU (optional). Alternatively, the IAB node may also send an F1AP message (optional) to the source IAB-donor CU, and the source IAB-donor CU sends an Xn message (optional) to the target IAB-donor CU.
  • the indication information is fourth indication information sent by a source CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • RLF radio link failure
  • CHO conditional handover
  • the target CU sends a radio resource control reestablishment (RRC reestablishment) message, or receives a radio resource control
  • RRC reestablishment complete radio resource control
  • the source CU sends the fourth indication information to the IAB sub-node or terminal device.
  • the sending time of the fourth indication information includes: the time when the restored IAB-MT sends the RRC re-establishment request message, or the time when the restored IAB-MT receives the RRC re-establishment message, Or the moment when the recovered IAB-MT sends the RRC re-establishment complete message, or the moment when the MT of the recovered IAB-node receives the first RRC reconfiguration (RRC reconfiguration) message after the RRC connection is reestablished, or the moment when the recovered IAB-node
  • the moment when the target CU and the restored IAB-DU establish or rebuild or update the F1 interface context such as the moment when the gNB DU configuration update process or the gNB CU configuration update process; or the target CU and the restored IAB-DU establish or rebuild or update a pair.
  • the BH configuration information which may include, for example, the target IAB parent node and the target IAB- BH RLC channels and BAP sublayer routing entries on the new path between donor DUs, or DL mapping of the new path to the restored IAB-node on the target IAB-donor DU; or update the F1-U connection (e.g. GTP tunnel information) moment, and so on.
  • the source CU sends the fourth indication information to the IAB sub-node or terminal device after performing a radio link failure (RLF) recovery process across an inter-CU.
  • RLF radio link failure
  • the target CU receives a radio resource control reconfiguration complete message, or establishes an F1 interface with the IAB node, or In the case of sending the BH configuration information, the source CU sends the fourth indication information to the IAB sub-node or terminal device.
  • CHO conditional handover
  • the sending moment of the fourth indication information includes: the IAB-node initiates CHO (for example, detach from source or start to apply the stored conditional reconfiguration of the target cell that meets the conditions or start to initiate RACH to the target cell) ), or the moment of sending the RRC reconfiguration complete message, or the moment of receiving the RLC layer confirmation or HARQ confirmation of the RRC reconfiguration complete message, or the moment when the DU of the IAB-node sends the F1AP setup request message to the target CU, or from the target CU
  • the BH configuration information may include, for example, the connection between the target IAB parent node and the target IAB-donor DU BH RLC channels and BAP sublayer routing entries on the new path, or DL mapping of the new path to the IAB-node on the target IAB-donor DU; or the time to update the F1-U connection (e.g. GTP tunnel information), etc.
  • the source CU sends the fourth indication information to the IAB sub-node or terminal device after performing a conditional handover (CHO) migration process across an inter-CU.
  • CHO conditional handover
  • the fourth indication information indicates configuration information of a Radio Resource Control (RRC) layer and/or a Packet Data Convergence Protocol (PDCP) layer in the target CU.
  • the fourth indication information includes at least one or any combination of the following information: next hop count (nextHopChainingCount), key set change indication (keySet ChangeIndicator), non-access stratum (NAS) security information (nas-Container ), encryption algorithm (ciphering Algorithm), integrity protection algorithm (integrityProtAlgorithm); but this application is not limited to this.
  • the fourth indication information may further indicate whether the donor CU of the IAB node has changed, or indicate that the IAB node has performed intra-CU migration or inter-CU migration (inter-CU migration) .
  • the fourth indication information may further include a CU change indication and/or an identifier of the target CU, and the like.
  • the source CU receives the fourth indication information sent by the target CU through a radio resource control (RRC) message, and after the source CU uses the configuration information to process the fourth indication information, passes The Xn interface is sent to the DU of the IAB node, and the DU of the IAB node is sent to the IAB sub-node or terminal device.
  • RRC radio resource control
  • FIG. 19 is another schematic diagram of a communication method of an IAB according to an embodiment of the present application.
  • the target CU sends the RRC message carrying the fourth indication information to the source CU through the Xn interface, and the source CU uses the configuration information of the source CU (the old security key encryption and/or integrity protection) for the RRC message. ) after processing, send the processed fourth instruction information to the target CU through the Xn interface, and the target CU sends the processed fourth instruction information to the restored or switched through DL RRC MESSAGE TRANSFER (using a new path).
  • the IAB node sends the processed fourth indication information to the IAB sub-node or the terminal device through an RRC message.
  • the IAB child node or terminal device can use the configuration information of the source CU (such as security algorithm and/or keys) to obtain the configuration information of the target CU; in addition, the IAB child node or terminal device can also send a response message or complete The message is sent to the IAB node after handover or recovery (optional), and the IAB node can also send information to the target IAB-donor CU through UL RRC MESSAGE TRANSFER (optional).
  • the configuration information of the source CU such as security algorithm and/or keys
  • the time delay of the cell selection and random access process in the RRC re-establishment process is saved, which is beneficial to reduce the recovery or migration of the IAB sub-node or terminal equipment to a new CU due to the IAB-node The resulting business interruption time.
  • the IAB sub-node or terminal device may indicate its capability to the CU, for example, in the UE capability information or the RRC setup complete message or the RRC resume complete or RRC reestablishment complete message, to indicate whether the above-mentioned embodiment is supported communication method.
  • the RRC message can be, for example, an RRC re-establishment message or an RRC reconfiguration message;
  • the F1AP message can be a UE context setup request or a UE context modification request;
  • the Xn message can be an RRC transfer or a Retrieve UE context response, etc.
  • the IAB sub-node or the terminal device receives the indication information sent by the network device, the indication information indicates the configuration information of the corresponding target CU, and communicates according to the configuration information of the target CU. Therefore, in the case of supporting inter-CU recovery or handover, even if the IAB child node or terminal device does not change the serving IAB node, the IAB child node or terminal device will update the configuration information of the CU, so that it can correctly match the target CU. communication.
  • This embodiment of the present application provides an IAB communication method, which is described from the IAB node, and the same content as the first and second aspects of the embodiment will not be repeated.
  • the embodiments of the third aspect may be implemented in combination with the embodiments of the first and second aspects, or may be implemented independently.
  • FIG. 20 is a schematic diagram of a scenario of an IAB communication method according to an embodiment of the present application.
  • IAB-node1 when IAB-node1 has RLF or RLF recovery failure on the backhaul link between it and the parent node (IAB-donor), it can send a message to the child node (IAB-node1) of IAB-node1 -node 3 and IAB-node 4) send an RLF indication (RLF indication or BH RLF indication) so that the IAB child nodes can know about the situation and search for other parent nodes to find a new route to communicate with the IAB-donor.
  • RLF indication RLF indication or BH RLF indication
  • Type 4 was agreed and specified, that is, the Type 4 BH RLF indication received by the child node will be considered by the child node to detect RLF.
  • BAP specification TS 38.340v16.2.0
  • the format of the BAP Control PDU indicated to the BH RLF is shown.
  • Table 1 shows the format of the BAP Control PDU indicated by the BH RLF.
  • the BAP control PDU includes:
  • D/C field length 1bit, indicating whether the corresponding BAP PDU is a BAP Data PDU or a BAP Control PDU;
  • PDU type 4 bits in length, indicating the type of control information included in the corresponding BAP Control PDU.
  • the BAP control PDU further includes R bits, which are 1 bit respectively; 3 R bits total 3 bits.
  • Rel-17 in order to provide some information to child nodes earlier, to speed up the recovery process of child nodes, thereby reducing the service interruption of child nodes, 3GPP is discussing whether RLF indication of type 1 to type 3 is required, and whether child nodes receive to the behavior of these types of RLF indications.
  • the RLF indication of the current BAP layer is only for type 4, and the RLF indication of type 1 to type 3 cannot be implemented.
  • the IAB node detects that a radio link failure (RLF) has occurred on the backhaul link between the IAB node and the parent node or is attempting RLF recovery or RLF recovery is successful or RLF recovery fails; and the IAB The node sends RLF indication information to the served IAB sub-node or terminal device; the RLF indication information indicates one of at least two types of backhaul link radio link failure (BH RLF).
  • RLF radio link failure
  • the type of the backhaul link radio link failure includes at least one of the following:
  • Type 1 of backhaul link radio link failure which means that the IAB node detects that a radio link failure (RLF) occurs in the backhaul link between the IAB node and the parent node,
  • RLF radio link failure
  • Type 2 of backhaul link radio link failure which means that the IAB node has detected a radio link failure (RLF) on the backhaul link between the IAB node and the parent node and the IAB node is attempting RLF recovery,
  • RLF radio link failure
  • Type 3 of backhaul link radio link failure which means that the IAB node detects that a radio link failure (RLF) occurs in the backhaul link between the IAB node and the parent node and the IAB node RLF recovery is successful,
  • RLF radio link failure
  • Type 4 of backhaul link radio link failure which means that the IAB node detects a radio link failure (RLF) on the backhaul link between the IAB node and the parent node and the IAB node RLF recovery fails.
  • RLF radio link failure
  • the RLF indication information is sent to the IAB sub-node or terminal device using a BAP control PDU; the PDU type field of the BAP control PDU indicates the type of the backhaul link radio link failure.
  • one value of more than one bit in the PDU Type field of the BAP Control PDU indicates type 4 of the backhaul link radio link failure; the other value indicates the return link radio link failure type 4; Type 2 or Type 3 for backhaul link radio link failure.
  • Table 4 shows that
  • one value of the plurality of bits in the PDU Type field of the BAP Control PDU indicates type 4 of the backhaul link radio link failure; the other value indicates the type of backhaul link radio link failure 1, or type 2, or one of type 1 and type 2; the other value indicates type 3 of the radio link failure of the backhaul link.
  • Table 5 where the value of PDU type is 0100 indicates BH RLF indication type 2):
  • the R field of the BAP Control PDU using the RLF indication information indicates the at least two types of backhaul link radio link failures.
  • one value of 1 bit in the R field of the BAP control PDU indicates type 4 of backhaul link radio link failure; the other value indicates type 2 or backhaul link failure of the backhaul link radio link.
  • Type 3 of wireless link failure For example, 0 means type 4 and 1 means type 2.
  • one value of a plurality of bits in the R field of the BAP control PDU indicates type 4 of the radio link failure of the backhaul link; another value indicates type 2 of the radio link failure of the backhaul link; The value indicates the type 3 of the radio link failure of the backhaul link.
  • the type 3 RLF indication may indicate whether the IAB node recovers to another IAB-donor CU, i.e. whether the IAB-donor CU recovered from a radio link failure is the same as the IAB node's source IAB-donor CU or IAB-donor CU Whether the donor CU has changed, such as using a field with a length of 1 bit.
  • the type 3 RLF indication may indicate the identity or index of the restored CU, etc., in the event that the IAB node successfully restores to another IAB-donor CU.
  • the IAB sub-node or terminal device when the IAB sub-node or terminal device receives the above-mentioned type 2 RLF indication or type 3 RLF indication or type 4 RLF indication, if the IAB sub-node or terminal device is configured with CHO, the CHO process can be initiated, Otherwise, a radio link failure recovery procedure may be initiated.
  • the IAB child node may generate an RLF indication when receiving the RLF indication, and the IAB child node sends the generated RLF indication to the child node or terminal device of the IAB child node.
  • an IAB child node when an IAB child node receives a type 1 or type 2 RLF indication, it can generate one of type 1 and type 2 RLF indication, or when an IAB child node receives a type 3 RLF indication, it can generate a type 3 RLF indication , or the IAB child node can generate a type 4 RLF indication when it receives a type 4 RLF indication.
  • an IAB child node when an IAB child node receives an RLF indication of type 1 or type 2 or type 3 or type 4, it can forward the RLF indication to a child node or terminal device of the IAB child node.
  • the IAB child node when it receives the RLF indication of type 1 or type 2 or type 3 or type 4, it may stop sending a scheduling request (Scheduling Request, SR) and/or a buffer status report (Buffer Status Report) to the IAB node. Status Report, BSR).
  • SR scheduling request
  • Buffer Status Report Buffer Status Report
  • the system information block type 1 (System Information Block Type 1, SIB1) of the cell under the IAB child node is in the The IAB-support field does not appear.
  • the behavior of the IAB child node when receiving the RLF indication is configurable, for example, the IAB-donor CU can configure the IAB child node to adopt the behavior in the above embodiment.
  • the RLF indication information indicates one of at least two types of backhaul link radio link failure (BH link RLF), which can provide some information to the child node earlier and accelerate the process of the child node recovery. , thereby reducing the service interruption of sub-nodes.
  • BH link RLF backhaul link radio link failure
  • This embodiment of the present application provides an IAB communication method, which is described from the IAB node, and the same contents as those of the embodiments in the first to third aspects will not be repeated. Furthermore, the embodiments of the fourth aspect may be implemented in combination with the embodiments of the first to third aspects, or may be implemented independently.
  • the RLF indication uses the BAP control PDU to indicate that since the IAB child node has a BAP layer but the terminal device does not have a BAP layer, the current RLF indication is not suitable for informing the terminal device to perform related operations.
  • the IAB node detects that a radio link failure (RLF) has occurred on the backhaul link between the IAB node and the parent node or is attempting RLF recovery or RLF recovery is successful or RLF recovery fails; and the The IAB node sends the RLF indication information to the served terminal equipment using physical layer signaling, MAC layer signaling, RLC layer signaling or system information.
  • RLF radio link failure
  • the IAB node sends the RLF indication information to the served IAB child node using a BAP control PDU, or the IAB node uses physical layer signaling, MAC layer signaling, RLC layer signaling, or system information to send RLF indication information to the served IAB sub-node.
  • the IAB child node sends the RLF indication information.
  • the physical layer signaling includes a downlink control information (DCI) format indicating the type of backhaul link radio link failure.
  • DCI downlink control information
  • a new DCI format can be designed for the PHY, or the BH RLF indication and/or BH RLF indication type can be explicitly indicated in the DCI.
  • the MAC layer signaling includes a MAC CE; one or more bits or fields in the MAC CE indicate the type of backhaul link radio link failure.
  • a new MAC CE may be employed, with a new LCID.
  • a MAC CE is identified by a corresponding MAC sub-header, and the MAC sub-header includes the LCID corresponding to the MAC CE.
  • the MAC CE may contain a bitmap, in which each bit represents a type; for 1 bit, for example, 1 means that it is a BH RLF indication of this type, and 0 means that it is not a BH RLF indication of this type.
  • the RLC layer signaling includes RLC control PDUs.
  • the system information includes a Main Information Block (MIB, Main Information Block) and/or a System Information Block (SIB, System Information Block); a field in the MIB and/or SIB indicates a backhaul link Type of radio link failure.
  • MIB Main Information Block
  • SIB System Information Block
  • the IAB-DU sends the MIB and/or SIB1 autonomously, eg the cellBarred field in the MIB is set to barred or the IAB-support field in the SIB1 does not appear, or the MIB and/or SIB1 use a new
  • the field indicates the BH RLF indication and/or the BH RLF indication type.
  • the IAB node sends the RLF indication information to the terminal equipment to which it belongs by using physical layer signaling, MAC layer signaling, RLC layer signaling or system information.
  • the IAB node can indicate to the terminal equipment that BH RLF occurs in its serving IAB node, which helps to reduce the service interruption delay caused by RLF recovery.
  • An embodiment of the present application provides an IAB communication device.
  • the apparatus may be, for example, an IAB sub-node or terminal device, or one or some components or components configured in the IAB sub-node or terminal device, and the same contents as those in the first and second aspects will not be repeated.
  • FIG. 21 is a schematic diagram of an IAB communication apparatus according to an embodiment of the present application.
  • the IAB communication apparatus 2100 includes a receiving unit 2101 and a processing unit 2102 .
  • the receiving unit 2101 receives indication information sent by a network device; the indication information is used to perform inter-centralized unit (inter-CU) restoration or migration at the IAB sub-node or the IAB node where the terminal device is located In the case of instructing the IAB sub-node or terminal device to consider that a radio link failure (RLF) is detected or instructing the IAB sub-node or terminal device to initiate connection re-establishment; and the processing unit 2102 initiates a radio link failure recovery process or connection rebuild process.
  • inter-CU inter-centralized unit
  • the indication information is first indication information sent by an IAB node performing radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • RLF radio link failure
  • CHO conditional handover
  • the IAB node receives a RRC re-establishment sent by a target centralized unit (Target CU) (RRC reestablishment) message, or establishing an F1 interface with the target CU, or receiving backhaul (BH) configuration information, the IAB node sends the first indication information to the IAB sub-node or terminal device.
  • RLF radio link failure
  • Target CU target centralized unit
  • BH backhaul
  • the IAB node sends the first indication information to the IAB sub-node or terminal device after a radio link failure (RLF) recovery process is performed across an inter-CU.
  • RLF radio link failure
  • the processing unit 2102 is further configured to: in the case that the IAB sub-node or terminal device is single-connected, or the IAB sub-node or terminal device is configured with dual-connection and the IAB node is In the case of the master cell group (MCG) of the IAB child node or the terminal equipment, it is determined that a radio link failure (RLF) is detected for the MCG.
  • MCG master cell group
  • RLF radio link failure
  • the processing unit 2102 is configured to initiate an MCG failure information procedure when the timer (T316) is configured and the SCG transmission is not suspended and the PSCell change is not in progress to report the failure of the MCG radio link, otherwise the connection re-establishment procedure is initiated.
  • the processing unit 2102 is further configured to: configure dual connectivity in the IAB sub-node or terminal device and the IAB node is a secondary cell group (SCG) of the IAB sub-node or terminal device In this case, it is determined that a radio link failure (RLF) is detected for the SCG.
  • SCG secondary cell group
  • RLF radio link failure
  • the processing unit 2102 is configured to initiate an SCG failure information procedure to report the failure of the SCG radio link when the MCG transmission is not suspended, otherwise initiate the connection re-establishment procedure.
  • the IAB node in the process of conditional handover (CHO) migration across centralized units (inter-CUs), the IAB node initiates a conditional handover (CHO), or sends a radio resource control reconfiguration complete (RRC reconfiguration complete). ) message, or establishing an F1 interface with the target CU, or receiving BH configuration information, the IAB node sends the first indication information to the IAB sub-node or terminal device.
  • CHO conditional handover
  • RRC reconfiguration complete radio resource control reconfiguration complete
  • the IAB node sends the first indication information to the IAB sub-node or terminal device after performing a conditional handover (CHO) migration process across a centralized unit (inter-CU).
  • CHO conditional handover
  • the first indication information includes at least one or any combination of the following: Backhaul Adaptation Protocol (BAP) Protocol Data Unit (PDU), Radio Link Control (RLC) PDU, Medium Access Control (MAC) ) Control Cell (CE), Medium Access Control (MAC) subheader, physical layer signaling.
  • BAP Backhaul Adaptation Protocol
  • PDU Protocol Data Unit
  • RLC Radio Link Control
  • MAC Medium Access Control
  • CE Control Cell
  • MAC Medium Access Control
  • the indication information is that a source centralized unit (Source CU) that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CU) passes recovery or migration
  • RLF radio link failure
  • CHO conditional handover
  • the source centralized unit (CU) sends the third indication information to the target CU or the distributed unit (DU) of the IAB node through the Xn interface, and the target CU or the The DU sends the third indication information to the IAB sub-node or terminal device.
  • the source CU in the process of radio link failure (RLF) recovery across centralized units (inter-CUs), when the source CU receives a context retrieval request message sent by the target CU, or to the When the target CU sends a context retrieval response message or receives a context release message sent by the target CU, the source CU sends the third indication information.
  • RLF radio link failure
  • the source CU sends the third indication information after an inter-centralized unit (inter-CU) radio link failure (RLF) recovery procedure.
  • inter-CU inter-centralized unit
  • RLF radio link failure
  • the source CU in the process of conditional handover (CHO) migration across centralized units (inter-CUs), the source CU sends the third indication in the case of receiving a context release message sent by the target CU information.
  • the source CU sends the third indication information after a conditional handover (CHO) migration process across an inter-CU.
  • CHO conditional handover
  • the third indication information includes at least one or any combination of the following: Packet Data Convergence Protocol (PDCP) protocol data unit (PDU), radio resource control (RRC) message, and F1AP message.
  • PDCP Packet Data Convergence Protocol
  • PDU protocol data unit
  • RRC radio resource control
  • F1AP F1AP message
  • the receiving unit 2101 receives indication information sent by a network device; the indication information is used to perform inter-centralized unit (inter-CU) restoration or migration at the IAB sub-node or the IAB node where the terminal device is located In the case of , the configuration information of the target CU corresponding to the IAB sub-node or the terminal device is indicated; and the processing unit 2102 communicates according to the configuration information of the target CU.
  • inter-CU inter-centralized unit
  • the indication information is second indication information sent by the target CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • RLF radio link failure
  • CHO conditional handover
  • the target CU sends a radio resource control reestablishment (RRC reestablishment) message or receives a radio resource
  • RRC reestablishment radio resource control reestablishment
  • the target CU sends the second indication information to the IAB child node or terminal device .
  • the target CU after a radio link failure (RLF) recovery process is performed across an inter-CU, the target CU sends the second indication information to the IAB sub-node or terminal device.
  • RLF radio link failure
  • the target CU receives a radio resource control reconfiguration complete message, or establishes an F1 interface with the IAB node , or in the case of sending BH configuration information, the target CU sends the second indication information to the IAB sub-node or terminal device.
  • CHO conditional handover
  • the target CU sends the second indication information to the IAB sub-node or terminal device after performing a conditional handover (CHO) migration process across an inter-CU.
  • CHO conditional handover
  • the second indication information indicates configuration information of a Radio Resource Control (RRC) layer and/or a Packet Data Convergence Protocol (PDCP) layer in the target CU;
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • the second indication information includes at least one or any combination of the following information: next hop count (nextHopChainingCount), key set change indication (keySetChangeIndicator), non-access stratum (NAS) security information ( nas-Container), encryption algorithm (ciphering Algorithm), integrity protection algorithm (integrityProtAlgorithm).
  • the target CU sends the unencrypted or default encrypted second indication information to the IAB sub-node or terminal device through a radio resource control (RRC) message.
  • RRC radio resource control
  • the processing unit 2102 is further configured to: receive a notification message of the IAB node; and suspend the integrity protection and encryption operations on the signaling radio bearer (SRB) according to the notification message, so as to obtain the second indication information.
  • SRB signaling radio bearer
  • the processing unit 2102 is further configured to: perform decryption and decoding operations on the radio resource control (RRC) message; and in the case of failure to successfully decode the radio resource control (RRC) message Decryption is not performed or a default decryption operation is performed, and a decoding operation is performed to obtain the second indication information.
  • RRC radio resource control
  • the target CU sends the second indication information to the IAB sub-node or the terminal device by using the configuration information of the source CU through a radio resource control (RRC) message.
  • RRC radio resource control
  • the target CU sends the second indication information to the source CU through an Xn interface, and after the source CU uses the configuration information to process the second indication information, the second indication information is processed by post-recovery or migration The latter path is sent to the IAB sub-node or terminal device.
  • the target CU sends the second indication information to the IAB sub-node or terminal device through an F1AP message.
  • the target CU sends the second indication information to the source CU through an Xn interface
  • the source CU sends the second indication information to the DU of the IAB node through an F1AP message , and is sent by the DU of the IAB node to the IAB sub-node or terminal device.
  • the indication information is fourth indication information sent by a source CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • RLF radio link failure
  • CHO conditional handover
  • the target CU sends a radio resource control reestablishment (RRC reestablishment) message, or receives a radio resource control
  • RRC reestablishment complete radio resource control
  • the source CU sends the fourth indication information to the IAB sub-node or terminal device.
  • the source CU sends the fourth indication information to the IAB sub-node or terminal device after performing a radio link failure (RLF) recovery process across an inter-CU.
  • RLF radio link failure
  • the target CU receives a radio resource control reconfiguration complete message, or establishes an F1 interface with the IAB node, or In the case of sending the BH configuration information, the source CU sends the fourth indication information to the IAB sub-node or terminal device.
  • CHO conditional handover
  • the source CU sends the fourth indication information to the IAB sub-node or terminal device after performing a conditional handover (CHO) migration process across an inter-CU.
  • CHO conditional handover
  • the fourth indication information indicates configuration information of a Radio Resource Control (RRC) layer and/or a Packet Data Convergence Protocol (PDCP) layer in the target CU;
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • the fourth indication information includes at least one or any combination of the following information: next hop count (nextHopChainingCount), key set change indication (keySet ChangeIndicator), non-access stratum (NAS) security information (nas-Container), encryption algorithm (ciphering Algorithm), integrity protection algorithm (integrityProtAlgorithm).
  • the source CU receives the fourth indication information sent by the target CU through a radio resource control (RRC) message, and after the source CU uses the configuration information to process the fourth indication information, passes The Xn interface is sent to the DU of the IAB node, and the DU of the IAB node is sent to the IAB sub-node or terminal device.
  • RRC radio resource control
  • the communication apparatus 2100 of the IAB may further include other components or modules, and for the specific content of these components or modules, reference may be made to the related art.
  • FIG. 21 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc. The implementation of this application does not limit this.
  • the IAB sub-node or terminal device receives the indication information sent by the network device, and initiates a wireless link failure recovery process or a connection re-establishment process according to the indication information; or, the IAB sub-node or terminal device receives the indication sent by the network device.
  • the indication information indicates the configuration information of the corresponding target CU, and the communication is performed according to the configuration information of the target CU. Therefore, in the case of supporting inter-CU recovery or handover, even if the IAB child node or terminal device does not change the serving IAB node, the IAB child node or terminal device will update the configuration information of the CU, so that it can correctly match the target CU. communication.
  • An embodiment of the present application provides an IAB communication device.
  • the apparatus may be, for example, an IAB node, or may be one or some components or components configured in the IAB node.
  • the IAB communication device in the embodiment of the sixth aspect corresponds to the IAB communication device of the fifth aspect, and the same content as the embodiment of the first and second aspects will not be repeated.
  • Fig. 22 is a schematic diagram of the communication device of the IAB according to the embodiment of the present application.
  • the communication device 2200 of the IAB includes: a generating part 2201 and a sending part 2202.
  • the generating unit 2201 generates indication information; the indication information is used to indicate that the IAB sub-node or the IAB node where the terminal device is located performs cross-centralized unit (inter-CU) restoration or migration.
  • the IAB sub-node or terminal device considers that a radio link failure (RLF) is detected or instructs the IAB sub-node or terminal device to initiate connection re-establishment; and the sending unit 2202 sends the indication information to the IAB sub-node or terminal device.
  • RLF radio link failure
  • the communication device 2200 of the IAB is an IAB node performing radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • the indication information is the first indication information sent by an IAB node that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • the IAB node receives a RRC re-establishment sent by a target centralized unit (Target CU) (RRC reestablishment) message, or establishing an F1 interface with the target CU, or receiving backhaul (BH) configuration information, the IAB node sends the first indication information to the IAB sub-node or terminal device.
  • RLF radio link failure
  • Target CU target centralized unit
  • BH backhaul
  • the IAB node sends the first indication information to the IAB sub-node or terminal device after a radio link failure (RLF) recovery process is performed across an inter-CU.
  • RLF radio link failure
  • the IAB node in the process of conditional handover (CHO) migration across centralized units (inter-CUs), the IAB node initiates a conditional handover (CHO), or sends a radio resource control reconfiguration complete (RRC reconfiguration complete). ) message, or establishing an F1 interface with the target CU, or receiving BH configuration information, the IAB node sends the first indication information to the IAB sub-node or terminal device.
  • CHO conditional handover
  • RRC reconfiguration complete radio resource control reconfiguration complete
  • the IAB node sends the first indication information to the IAB sub-node or terminal device after performing a conditional handover (CHO) migration process across a centralized unit (inter-CU).
  • CHO conditional handover
  • the first indication information includes at least one or any combination of the following: Backhaul Adaptation Protocol (BAP) Protocol Data Unit (PDU), Radio Link Control (RLC) PDU, Medium Access Control (MAC) ) Control Cell (CE), Medium Access Control (MAC) subheader, physical layer signaling.
  • BAP Backhaul Adaptation Protocol
  • PDU Protocol Data Unit
  • RLC Radio Link Control
  • MAC Medium Access Control
  • CE Control Cell
  • MAC Medium Access Control
  • the communication device 2200 of the IAB is a source CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • the indication information is the first message sent by the source centralized unit (Source CU) that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across the centralized unit (inter-CU) through the path after recovery or migration.
  • Source CU source centralized unit
  • RLF radio link failure
  • CHO conditional handover
  • the source centralized unit (CU) sends the third indication information to the target CU or the distributed unit (DU) of the IAB node through the Xn interface, and the target CU or the The DU sends the third indication information to the IAB sub-node or terminal device.
  • the source CU in the process of radio link failure (RLF) recovery across centralized units (inter-CUs), when the source CU receives a context retrieval request message sent by the target CU, or to the When the target CU sends a context retrieval response message or receives a context release message sent by the target CU, the source CU sends the third indication information.
  • RLF radio link failure
  • the source CU sends the third indication information after an inter-centralized unit (inter-CU) radio link failure (RLF) recovery procedure.
  • inter-CU inter-centralized unit
  • RLF radio link failure
  • the source CU in the process of conditional handover (CHO) migration across centralized units (inter-CUs), the source CU sends the third indication in the case of receiving a context release message sent by the target CU information.
  • the source CU sends the third indication information after a conditional handover (CHO) migration process across an inter-CU.
  • CHO conditional handover
  • the third indication information includes at least one or any combination of the following: Packet Data Convergence Protocol (PDCP) protocol data unit (PDU), radio resource control (RRC) message, and F1AP message.
  • PDCP Packet Data Convergence Protocol
  • PDU protocol data unit
  • RRC radio resource control
  • F1AP F1AP message
  • the generating unit 2201 generates indication information; the indication information is used in the case that the IAB child node or the IAB node where the terminal device is located performs cross-centralized unit (inter-CU) restoration or migration, Indicate the configuration information of the target CU corresponding to the IAB child node or the terminal device; and the sending unit 2202 sends the configuration information of the target CU to the IAB child node or the terminal device.
  • inter-CU cross-centralized unit
  • the IAB communication device 2200 is a target CU for inter-centralized unit (inter-CU) radio link failure (RLF) recovery or conditional handover (CHO) migration.
  • the indication information is second indication information sent by the target CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • the target CU sends a radio resource control reestablishment (RRC reestablishment) message or receives a radio resource
  • RRC reestablishment radio resource control reestablishment
  • the target CU sends the second indication information to the IAB child node or terminal device .
  • the target CU after a radio link failure (RLF) recovery process is performed across an inter-CU, the target CU sends the second indication information to the IAB sub-node or terminal device.
  • RLF radio link failure
  • the target CU receives a radio resource control reconfiguration complete message, or establishes an F1 interface with the IAB node , or in the case of sending BH configuration information, the target CU sends the second indication information to the IAB sub-node or terminal device.
  • CHO conditional handover
  • the target CU sends the second indication information to the IAB sub-node or terminal device after performing a conditional handover (CHO) migration process across an inter-CU.
  • CHO conditional handover
  • the second indication information indicates configuration information of a Radio Resource Control (RRC) layer and/or a Packet Data Convergence Protocol (PDCP) layer in the target CU; for example, the second indication information includes the following At least one or any combination of information: next hop count (nextHopChainingCount), key set change indication (keySetChangeIndicator), non-access stratum (NAS) security information (nas-Container), encryption algorithm (ciphering Algorithm), integrity Protection algorithm (integrityProtAlgorithm).
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • the target CU sends the unencrypted or default encrypted second indication information to the IAB sub-node or terminal device through a radio resource control (RRC) message.
  • RRC radio resource control
  • the target CU sends the second indication information to the IAB sub-node or the terminal device by using the configuration information of the source CU through a radio resource control (RRC) message.
  • RRC radio resource control
  • the target CU sends the second indication information to the source CU through an Xn interface, and after the source CU uses the configuration information to process the second indication information, the second indication information is processed by post-recovery or migration The latter path is sent to the IAB sub-node or terminal device.
  • the target CU sends the second indication information to the IAB sub-node or terminal device through an F1AP message.
  • the target CU sends the second indication information to the source CU through an Xn interface
  • the source CU sends the second indication information to the DU of the IAB node through an F1AP message , and is sent by the DU of the IAB node to the IAB sub-node or terminal device.
  • the communication device 2200 of the IAB is a source CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • the indication information is fourth indication information sent by a source CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • the target CU sends a radio resource control reestablishment (RRC reestablishment) message, or receives a radio resource control
  • RRC reestablishment complete radio resource control
  • the source CU sends the fourth indication information to the IAB sub-node or terminal device.
  • the source CU sends the fourth indication information to the IAB sub-node or terminal device after performing a radio link failure (RLF) recovery process across an inter-CU.
  • RLF radio link failure
  • the target CU receives a radio resource control reconfiguration complete message, or establishes an F1 interface with the IAB node, or In the case of sending the BH configuration information, the source CU sends the fourth indication information to the IAB sub-node or terminal device.
  • CHO conditional handover
  • the source CU sends the fourth indication information to the IAB sub-node or terminal device after performing a conditional handover (CHO) migration process across an inter-CU.
  • CHO conditional handover
  • the fourth indication information indicates configuration information of a Radio Resource Control (RRC) layer and/or a Packet Data Convergence Protocol (PDCP) layer in the target CU; for example, the fourth indication information includes the following At least one or any combination of information: next hop count (nextHopChainingCount), key set change indication (keySet ChangeIndicator), non-access stratum (NAS) security information (nas-Container), encryption algorithm (ciphering Algorithm), complete Sexual Protection Algorithm (integrityProtAlgorithm).
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • the source CU receives the fourth indication information sent by the target CU through a radio resource control (RRC) message, and after the source CU uses the configuration information to process the fourth indication information, passes The Xn interface is sent to the DU of the IAB node, and the DU of the IAB node is sent to the IAB sub-node or terminal device.
  • RRC radio resource control
  • the communication apparatus 2200 of the IAB may further include other components or modules, and for the specific content of these components or modules, reference may be made to the related art.
  • FIG. 22 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc. The implementation of this application does not limit this.
  • the node of the IAB sends indication information to the IAB sub-node or terminal device, and the IAB sub-node or terminal device initiates a radio link failure recovery process or a connection re-establishment process according to the indication information, or, the IAB sub-node or terminal device.
  • An embodiment of the present application further provides a communication system, and reference may be made to FIG. 1 , and the same contents as those of the embodiments of the first aspect to the sixth aspect will not be repeated.
  • the communication system may include: the communication apparatus 2100 of the IAB according to the embodiment of the fifth aspect and the communication apparatus 2200 of the IAB according to the embodiment of the sixth aspect, which perform the first and second aspects.
  • the communication system may include: an IAB node, which executes the communication method of the IAB described in the third and fourth aspects.
  • the embodiment of the present application also provides a network device, which may be, for example, a base station or an IAB node, but the present application is not limited to this, and may also be other network devices.
  • a network device which may be, for example, a base station or an IAB node, but the present application is not limited to this, and may also be other network devices.
  • FIG. 23 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • the network device 2300 may include: a processor 2310 (eg, a central processing unit CPU) and a memory 2320 ; the memory 2320 is coupled to the processor 2310 .
  • the memory 2320 can store various data; in addition, a program 2330 for information processing is also stored, and the program 2330 is executed under the control of the processor 2310 .
  • the processor 2310 may be configured to execute a program to implement the communication method of the IAB as described in the embodiment of the first aspect.
  • the processor 2310 may be configured to perform the following control: generate indication information; the indication information is used in the case of performing inter-centralized unit (inter-CU) restoration or migration at the IAB sub-node or the IAB node where the terminal device is located Next, instruct the IAB sub-node or terminal device to consider that a radio link failure (RLF) is detected or instruct the IAB sub-node or terminal device to initiate connection re-establishment; and send the indication information to the IAB sub-node or terminal device .
  • inter-CU inter-centralized unit
  • RLF radio link failure
  • the processor 2310 may be configured to execute a program to implement the communication method of the IAB as described in the embodiment of the second aspect.
  • the processor 2310 may be configured to perform the following control: generate indication information; the indication information is used to perform inter-centralized unit (inter-CU) restoration or migration at the IAB sub-node or the IAB node where the terminal device is located In the case of , indicating the configuration information of the target CU corresponding to the IAB sub-node or terminal device; and sending the configuration information of the target CU to the IAB sub-node or terminal device.
  • inter-CU inter-centralized unit
  • the processor 2310 may be configured to execute a program to implement the communication method of the IAB according to the embodiment of the third aspect.
  • the processor 2310 may be configured to perform the following control: it is detected that a radio link failure (RLF) occurs in the backhaul link between the IAB node and the parent node, or RLF recovery is being attempted or RLF recovery is successful or RLF recovery fails and send RLF indication information to the affiliated IAB child node or terminal device; the RLF indication information indicates at least one of two types of backhaul link radio link failure (BH link RLF).
  • RLF radio link failure
  • the processor 2310 may be configured to execute a program to implement the communication method of the IAB according to the embodiment of the fourth aspect.
  • the processor 2310 may be configured to control the following: detecting that a radio link failure (RLF) occurs on the backhaul link between the IAB node and the parent node or is attempting RLF recovery or RLF recovery is successful or RLF recovery failure; use BAP control PDU to send RLF indication information to the affiliated IAB sub-node; and use physical layer signaling, MAC layer signaling, RLC layer signaling or system information to send the RLF indication information to the affiliated terminal equipment.
  • RLF radio link failure
  • the network device 2300 may further include: a transceiver 2340, an antenna 2350, and the like; wherein, the functions of the above components are similar to those in the prior art, and will not be repeated here. It is worth noting that the network device 2300 does not necessarily include all the components shown in FIG. 23 ; in addition, the network device 2300 may also include components not shown in FIG. 23 , and reference may be made to the prior art.
  • the embodiments of the present application also provide an IAB sub-node or terminal device, but the present application is not limited to this, and may also be other devices.
  • the following description takes a terminal device as an example; for the IAB child node, the structure shown in FIG. 24 may or may be omitted, or some components (eg, the display 2450 ) and the like may be omitted.
  • FIG. 24 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 2400 may include a processor 2410 and a memory 2420 ; the memory 2420 stores data and programs, and is coupled to the processor 2410 .
  • this figure is exemplary; other types of structures may be used in addition to or in place of this structure to implement telecommunication functions or other functions.
  • the processor 2410 may be configured to execute a program to implement the communication method of the IAB as described in the embodiment of the first aspect.
  • the processor 2410 may be configured to perform the following control: receive indication information sent by a network device; the indication information is used to perform inter-centralized unit (inter-CU) execution at the IAB sub-node or the IAB node where the terminal device is located. ) in the case of recovery or migration, instructing the IAB sub-node or terminal device to consider that a radio link failure (RLF) is detected or instructing the IAB sub-node or terminal device to initiate connection re-establishment; and initiating a radio link failure recovery process or Connection re-establishment process.
  • RLF radio link failure
  • the processor 2410 may be configured to execute a program to implement the communication method of the IAB according to the embodiment of the second aspect.
  • the processor 2410 may be configured to perform the following control: receive indication information sent by a network device; the indication information is used to perform inter-centralized unit (inter-CU) execution at the IAB sub-node or the IAB node where the terminal device is located. ) in the case of restoration or migration, indicating the configuration information of the target CU corresponding to the IAB sub-node or the terminal device; and performing communication according to the configuration information of the target CU.
  • inter-CU inter-centralized unit
  • the terminal device 2400 may further include: a communication module 2430 , an input unit 2440 , a display 2450 , and a power supply 2460 .
  • the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the terminal device 2400 does not necessarily include all the components shown in FIG. 24 , and the above components are not required; in addition, the terminal device 2400 may also include components not shown in FIG. 24 . There is technology.
  • An embodiment of the present application further provides a computer program, wherein when the program is executed in an IAB sub-node or terminal device, the program causes the IAB sub-node or terminal device to execute the embodiments of the first and second aspects The IAB communication method.
  • the embodiments of the present application further provide a storage medium storing a computer program, wherein the computer program enables an IAB sub-node or terminal device to execute the IAB communication method described in the first and second aspects.
  • the embodiment of the present application further provides a computer program, wherein when the program is executed in an IAB node, the program causes the IAB node to execute the IAB communication method according to the first to fourth aspects of the embodiment.
  • the embodiments of the present application further provide a storage medium storing a computer program, wherein the computer program enables an IAB node to execute the IAB communication method described in the first to fourth aspects.
  • the apparatuses and methods above in the present application may be implemented by hardware, or may be implemented by hardware combined with software.
  • the present application relates to a computer-readable program that, when executed by logic components, enables the logic components to implement the above-described apparatus or constituent components, or causes the logic components to implement the above-described various methods or steps.
  • the present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, and the like.
  • the method/apparatus described in conjunction with the embodiments of this application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams shown in the figures and/or one or more combinations of the functional block diagrams may correspond to either software modules or hardware modules of the computer program flow.
  • These software modules may respectively correspond to the various steps shown in the figure.
  • These hardware modules can be implemented by, for example, solidifying these software modules using a Field Programmable Gate Array (FPGA).
  • FPGA Field Programmable Gate Array
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
  • a storage medium can be coupled to the processor, such that the processor can read information from, and write information to, the storage medium; or the storage medium can be an integral part of the processor.
  • the processor and storage medium may reside in an ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
  • the functional blocks and/or one or more combinations of the functional blocks described in the figures can be implemented as a general-purpose processor, a digital signal processor (DSP) for performing the functions described in this application ), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof.
  • DSP digital signal processor
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described with respect to the figures can also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, multiple microprocessors processor, one or more microprocessors in communication with the DSP, or any other such configuration.
  • IAB integrated access and backhaul
  • the IAB sub-node or the terminal device receives the indication information sent by the network device; the indication information is used when the IAB sub-node or the IAB node where the terminal device is located performs cross-centralized unit (inter-CU) recovery or migration , instructing the IAB sub-node or terminal device to consider that a radio link failure (RLF) is detected or instructing the IAB sub-node or terminal device to initiate connection re-establishment; and
  • RLF radio link failure
  • the IAB sub-node or terminal device initiates a radio link failure recovery process or a connection re-establishment process.
  • Supplement 2 The method according to Supplement 1, wherein the indication information is sent by an IAB node that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • RLF radio link failure
  • CHO conditional handover
  • Supplement 3 The method according to Supplement 2, wherein the target centralized unit is received at the IAB node during or after radio link failure (RLF) recovery across centralized units (inter-CUs) (Target CU) sends a radio resource control reestablishment (RRC reestablishment) message, or establishes an F1 interface with the target CU, or receives backhaul (BH) configuration information, the IAB node sends the IAB child node or The terminal device sends the first indication information.
  • RLF radio link failure
  • RRC reestablishment radio resource control reestablishment
  • BH backhaul
  • Supplementary Note 4 The method according to Supplementary Note 2, wherein during or after a conditional handover (CHO) migration process across centralized units (inter-CUs), a conditional handover (CHO) is initiated at the IAB node, or In the case of sending a radio resource control reconfiguration complete (RRC reconfiguration complete) message, or establishing an F1 interface with the target CU, or receiving BH configuration information, the IAB node sends the first IAB node to the IAB sub-node or terminal device.
  • RRC reconfiguration complete radio resource control reconfiguration complete
  • the IAB sub-node or terminal device is single-connected, or the IAB sub-node or terminal device is configured with dual-connection and the IAB node is the master cell group (MCG) of the IAB sub-node or terminal device
  • MCG master cell group
  • the IAB sub-node or terminal device considers (determines) that a radio link failure (RLF) is detected for the MCG.
  • RLF radio link failure
  • Supplement 6 The method according to Supplement 5, wherein the IAB sub-node or terminal device initiates a radio link failure recovery process, including:
  • the IAB sub-node or terminal device initiates the MCG failure information procedure to report the MCG radio link fails, otherwise the connection re-establishment process is initiated.
  • Supplement 7 The method according to Supplement 3 or 4, wherein the method further comprises:
  • the IAB sub-node or the terminal device determines to detect the SCG to Radio Link Failure (RLF).
  • SCG secondary cell group
  • RLF Radio Link Failure
  • Supplement 8 The method according to Supplement 7, wherein the IAB sub-node or terminal device initiates a radio link failure recovery process, including:
  • the IAB sub-node or the terminal device initiates the SCG failure information procedure to report the failure of the SCG radio link, otherwise initiates the connection reestablishment procedure.
  • Supplement 9 The method according to any one of Supplementary Notes 2 to 8, wherein the first indication information includes at least one or any combination of the following: Backhaul Adaptation Protocol (BAP) Protocol Data Units (PDUs), Radio Link Control (RLC) PDU, Medium Access Control (MAC) Control Cell (CE), Medium Access Control (MAC) subheader, physical layer signaling.
  • BAP Backhaul Adaptation Protocol
  • PDUs Protocol Data Units
  • RLC Radio Link Control
  • MAC Medium Access Control
  • CE Medium Access Control
  • MAC Medium Access Control subheader
  • Supplement 10 The method according to Supplement 1, wherein the indication information is a source centralized unit that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • RLF radio link failure
  • CHO conditional handover
  • Supplement 11 The method according to Supplement 10, wherein the source centralized unit (CU) sends the third indication information to the target CU or the distributed unit (DU) of the IAB node through an Xn interface , and the target CU or the DU sends the third indication information to the IAB sub-node or terminal device.
  • the source centralized unit (CU) sends the third indication information to the target CU or the distributed unit (DU) of the IAB node through an Xn interface
  • the target CU or the DU sends the third indication information to the IAB sub-node or terminal device.
  • Supplement 12 The method according to Supplement 10 or 11, wherein the target CU is received at the source CU during or after the inter-centralized unit (inter-CU) radio link failure (RLF) recovery process
  • inter-CU inter-centralized unit
  • RLF radio link failure
  • Supplementary Note 13 The method according to Supplementary Note 10 or 11, wherein, during or after the conditional handover (CHO) migration process across centralized units (inter-CUs), the source CU receives the information sent by the target CU. In the case of a context release message, the third indication information is sent.
  • Supplement 14 The method according to Supplement 12 or 13, wherein the method further comprises:
  • the IAB sub-node or terminal device is single-connected, or the IAB sub-node or terminal device is configured with dual-connection and the IAB node is the master cell group (MCG) of the IAB sub-node or terminal device
  • MCG master cell group
  • the IAB sub-node or the terminal device determines that a radio link failure (RLF) is detected for the MCG.
  • RLF radio link failure
  • Supplementary note 15 The method according to supplementary note 14, wherein the IAB sub-node or terminal device initiates a radio link failure recovery process, comprising:
  • the IAB sub-node or terminal device initiates the MCG failure information procedure to report the MCG radio link fails, otherwise the connection re-establishment process is initiated.
  • Supplement 16 The method according to Supplement 12 or 13, wherein the method further comprises:
  • the IAB sub-node or the terminal device determines to detect the SCG to Radio Link Failure (RLF).
  • SCG secondary cell group
  • RLF Radio Link Failure
  • Supplement 17 The method according to Supplement 16, wherein the IAB sub-node or terminal device initiates a radio link failure recovery process, comprising:
  • the IAB sub-node or the terminal device initiates the SCG failure information procedure to report the failure of the SCG radio link, otherwise initiates the connection reestablishment procedure.
  • Supplement 18 The method according to any one of Supplements 10 to 17, wherein the third indication information includes at least one or any combination of the following: Packet Data Convergence Protocol (PDCP) protocol data unit (PDU), wireless Resource Control (RRC) messages, F1AP messages.
  • PDCP Packet Data Convergence Protocol
  • PDU protocol data unit
  • RRC wireless Resource Control
  • F1AP F1AP messages.
  • An integrated access and backhaul (IAB) communication method comprising:
  • the IAB sub-node or the terminal device receives the indication information sent by the network device; the indication information is used when the IAB sub-node or the IAB node where the terminal device is located performs cross-centralized unit (inter-CU) recovery or migration , indicating the configuration information of the target CU corresponding to the IAB sub-node or terminal device; and
  • inter-CU cross-centralized unit
  • the IAB sub-node or terminal device communicates according to the configuration information of the target CU.
  • Supplement 20 The method according to Supplement 19, wherein the indication information is the target CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • RLF radio link failure
  • CHO conditional handover
  • Supplement 21 The method according to Supplement 20, wherein during or after the inter-centralized unit (inter-CU) radio link failure (RLF) recovery process, the target CU sends RRC re-establishment (RRC reestablishment) message, or a radio resource control reestablishment complete (RRC reestablishment complete) message is received, or an F1 interface is established with the IAB node, or BH configuration information is sent, the target CU sends the IAB subordinate The node or terminal device sends the second indication information.
  • RLF radio link failure
  • Supplement 22 The method according to Supplement 20, wherein during or after the conditional handover (CHO) migration process across centralized units (inter-CUs), the target CU receives that the RRC reconfiguration completes message, or establishes an F1 interface with the IAB node, or sends BH configuration information, the target CU sends the second indication information to the IAB sub-node or terminal device.
  • the target CU receives that the RRC reconfiguration completes message, or establishes an F1 interface with the IAB node, or sends BH configuration information
  • the target CU sends the second indication information to the IAB sub-node or terminal device.
  • Supplement 23 The method according to any one of Supplementary Notes 20 to 22, wherein the second indication information indicates a Radio Resource Control (RRC) layer and/or a Packet Data Convergence Protocol (PDCP) layer in the target CU configuration information.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • Supplement 24 The method according to any one of Supplements 20 to 23, wherein the second indication information includes at least one or any combination of the following information: next hop count (nextHopChainingCount), key set change indication (keySetChangeIndicator), non-access stratum (NAS) security information (nas-Container), encryption algorithm (ciphering Algorithm), integrity protection algorithm (integrityProtAlgorithm).
  • next hop count (nextHopChainingCount)
  • key set change indication keySetChangeIndicator
  • NAS non-access stratum
  • security information nas-Container
  • encryption algorithm ciphering Algorithm
  • integrity protection algorithm IntegrityProtAlgorithm
  • Supplement 25 The method according to any one of Supplementary Notes 20 to 24, wherein the target CU sends the unencrypted or default encrypted second indication information to the IAB through a Radio Resource Control (RRC) message Child node or terminal device.
  • RRC Radio Resource Control
  • Supplement 26 The method according to Supplement 25, wherein the method further comprises:
  • the IAB sub-node or terminal device receives the notification message of the IAB node.
  • the IAB sub-node or the terminal device suspends the integrity protection and encryption operations on the signaling radio bearer (SRB) according to the notification message, so as to obtain the second indication information.
  • SRB signaling radio bearer
  • Supplement 27 The method according to Supplement 25, wherein the method further comprises:
  • RRC radio resource control
  • the radio resource control (RRC) message is not decrypted or a default decryption operation is performed, and a decoding operation is performed to obtain the second indication information.
  • RRC radio resource control
  • Supplement 28 The method according to any one of Supplementary Notes 20 to 24, wherein the target CU sends the second indication information to a radio resource control (RRC) message using the configuration information of the source CU. the IAB sub-node or terminal device.
  • RRC radio resource control
  • Supplement 29 The method according to any one of Supplementary Notes 20 to 24, wherein the target CU sends the second indication information to the source CU through an Xn interface, and the source CU uses the configuration information After the second indication information is processed, it is sent to the IAB sub-node or terminal device through the restored or migrated path.
  • Supplementary note 30 The method according to any one of supplementary notes 20 to 24, wherein the target CU sends the second indication information to the IAB sub-node or terminal device through an F1AP message.
  • Supplement 31 The method according to any one of Supplementary Notes 20 to 24, wherein the target CU sends the second indication information to the source CU through an Xn interface, and the source CU sends the information to the source CU through an F1AP message.
  • the second indication information is sent to the DU of the IAB node, and is sent to the IAB sub-node or terminal device by the DU of the IAB node.
  • Supplement 32 The method according to Supplement 19, wherein the indication information is sent by a source CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • RLF radio link failure
  • CHO conditional handover
  • Supplement 33 The method according to Supplement 32, wherein during or after the inter-centralized unit (inter-CU) radio link failure (RLF) recovery process, the target CU sends a radio resource control re-establishment (RRC) reestablishment) message, or, receiving a radio resource control reestablishment complete (RRC reestablishment complete) message, or establishing an F1 interface with the IAB node, or sending BH configuration information, the source CU sends the IAB child node. Or the terminal device sends the fourth indication information.
  • RRC radio resource control re-establishment
  • RRC reestablishment complete radio resource control reestablishment complete
  • Supplementary note 34 The method according to supplementary note 32, wherein during or after the conditional handover (CHO) migration process across centralized units (inter-CUs), the target CU receives a radio resource control reconfiguration complete message, Or in the case of establishing an F1 interface with the IAB node or sending BH configuration information, the source CU sends the fourth indication information to the IAB sub-node or terminal device.
  • CHO conditional handover
  • Supplement 35 The method according to any one of Supplements 32 to 34, wherein the fourth indication information indicates a Radio Resource Control (RRC) layer and/or a Packet Data Convergence Protocol (PDCP) layer in the target CU configuration information.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • Supplement 36 The method according to any one of Supplements 32 to 35, wherein the fourth indication information includes at least one or any combination of the following information: next hop count (nextHopChainingCount), key set change indication (keySet ChangeIndicator), non-access stratum (NAS) security information (nas-Container), encryption algorithm (ciphering Algorithm), integrity protection algorithm (integrityProtAlgorithm).
  • Supplement 37 The method according to any one of Supplements 32 to 36, wherein the source CU receives the fourth indication information sent by the target CU through a radio resource control (RRC) message, and the source CU receives the fourth indication information sent by the target CU through a radio resource control (RRC) message, After the CU uses the configuration information to process the fourth indication information, it sends the DU to the IAB node through the Xn interface, and the DU of the IAB node sends the DU to the IAB sub-node or terminal device.
  • RRC radio resource control
  • RRC radio resource control
  • IAB integrated access and backhaul
  • the network device generates indication information; the indication information is used to instruct the IAB sub-node or the terminal device when the IAB sub-node or the IAB node where the terminal device is located performs cross-centralized unit (inter-CU) recovery or migration consider that a radio link failure (RLF) is detected or that the IAB sub-node or terminal device is instructed to initiate connection re-establishment; and
  • inter-CU cross-centralized unit
  • Supplementary note 39 The method according to supplementary note 38, wherein the network device is an IAB node that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs);
  • the indication information is the first indication information sent by an IAB node that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • Supplement 40 The method of Supplement 39, wherein the target centralized unit is received at the IAB node during or after radio link failure (RLF) recovery across centralized units (inter-CUs) (Target CU) sends a radio resource control reestablishment (RRC reestablishment) message, or establishes an F1 interface with the target CU, or receives backhaul (BH) configuration information, the IAB node sends the IAB child node or The terminal device sends the first indication information.
  • RLF radio link failure
  • RRC reestablishment radio resource control reestablishment
  • BH backhaul
  • Supplement 41 The method according to Supplement 39, wherein during or after a conditional handover (CHO) migration process across centralized units (inter-CUs), a conditional handover (CHO) is initiated at the IAB node, or In the case of sending a radio resource control reconfiguration complete (RRC reconfiguration complete) message, or establishing an F1 interface with the target CU, or receiving BH configuration information, the IAB node sends the first IAB node to the IAB sub-node or terminal device.
  • RRC reconfiguration complete radio resource control reconfiguration complete
  • Supplement 42 The method according to any one of Supplements 39 to 42, wherein the first indication information includes at least one or any combination of the following: Backhaul Adaptation Protocol (BAP) Protocol Data Units (PDUs), Radio Link Control (RLC) PDU, Medium Access Control (MAC) Control Cell (CE), Medium Access Control (MAC) subheader, physical layer signaling.
  • BAP Backhaul Adaptation Protocol
  • PDUs Protocol Data Units
  • RLC Radio Link Control
  • MAC Medium Access Control
  • CE Medium Access Control
  • MAC Medium Access Control subheader
  • Supplement 43 The method according to Supplement 38, wherein the network device is a source CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs);
  • the indication information is the third message sent by the source centralized unit (Source CU) that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across the centralized unit (inter-CU) through the path after recovery or migration.
  • Supplement 44 The method according to Supplement 43, wherein the source centralized unit (CU) sends the third indication information to the target CU or the distributed unit (DU) of the IAB node through an Xn interface , and the target CU or the DU sends the third indication information to the IAB sub-node or terminal device.
  • the source centralized unit (CU) sends the third indication information to the target CU or the distributed unit (DU) of the IAB node through an Xn interface
  • the target CU or the DU sends the third indication information to the IAB sub-node or terminal device.
  • Supplement 45 The method according to Supplement 43 or 44, wherein the target CU is received at the source CU during or after the inter-centralized unit (inter-CU) radio link failure (RLF) recovery process
  • inter-CU inter-centralized unit
  • RLF radio link failure
  • Supplementary Note 46 The method according to Supplementary Note 43 or 44, wherein, during or after the conditional handover (CHO) migration process across centralized units (inter-CUs), the source CU receives the information sent by the target CU. In the case of a context release message, the third indication information is sent.
  • CHO conditional handover
  • Supplement 47 The method according to any one of Supplements 43 to 46, wherein the third indication information includes at least one or any combination of the following: Packet Data Convergence Protocol (PDCP) Protocol Data Units (PDUs), wireless Resource Control (RRC) messages, F1AP messages.
  • PDCP Packet Data Convergence Protocol
  • PDUs Protocol Data Units
  • RRC wireless Resource Control
  • F1AP messages F1AP messages.
  • IAB integrated access and backhaul
  • the network device generates indication information; the indication information is used to instruct the IAB sub-node or the IAB node where the terminal device is located to perform cross-centralized unit (inter-CU) recovery or migration. configuration information of the target CU corresponding to the terminal device; and sending the configuration information of the target CU to the IAB sub-node or the terminal device.
  • inter-CU cross-centralized unit
  • Supplement 49 The method according to Supplement 48, wherein the network device is a target CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs);
  • the indication information is the second indication information sent by the target CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • Supplement 50 The method according to Supplement 49, wherein during or after the inter-centralized unit (inter-CU) radio link failure (RLF) recovery process, the target CU sends RRC re-establishment (RRC reestablishment) message, or a radio resource control reestablishment complete (RRC reestablishment complete) message is received, or an F1 interface is established with the IAB node, or BH configuration information is sent, the target CU sends the IAB sub- The node or terminal device sends the second indication information.
  • RLF radio link failure
  • Supplement 51 The method according to Supplement 49, wherein during or after the conditional handover (CHO) migration process across centralized units (inter-CUs), the target CU receives that the RRC reconfiguration completes message, or establishes an F1 interface with the IAB node, or sends BH configuration information, the target CU sends the second indication information to the IAB sub-node or terminal device.
  • the target CU receives that the RRC reconfiguration completes message, or establishes an F1 interface with the IAB node, or sends BH configuration information
  • the target CU sends the second indication information to the IAB sub-node or terminal device.
  • Supplement 52 The method according to any one of Supplements 49 to 51, wherein,
  • the second indication information indicates configuration information of a Radio Resource Control (RRC) layer and/or a Packet Data Convergence Protocol (PDCP) layer in the target CU.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • Supplement 53 The method according to any one of Supplements 49 to 52, wherein the second indication information includes at least one or any combination of the following information: next hop count (nextHopChainingCount), key set change indication (keySetChangeIndicator), non-access stratum (NAS) security information (nas-Container), encryption algorithm (ciphering Algorithm), integrity protection algorithm (integrityProtAlgorithm).
  • next hop count (nextHopChainingCount)
  • key set change indication keySetChangeIndicator
  • NAS non-access stratum
  • security information nas-Container
  • encryption algorithm ciphering Algorithm
  • integrity protection algorithm IntegrityProtAlgorithm
  • Supplement 54 The method according to any one of Supplements 49 to 53, wherein the target CU sends the unencrypted or default encrypted second indication information to the IAB through a Radio Resource Control (RRC) message Child node or terminal device.
  • RRC Radio Resource Control
  • Supplement 55 The method according to any one of Supplementary Notes 49 to 53, wherein the target CU sends the second indication information to a radio resource control (RRC) message using the configuration information of the source CU. the IAB sub-node or terminal device.
  • RRC radio resource control
  • Supplement 56 The method according to any one of Supplements 49 to 53, wherein the target CU sends the second indication information to the source CU through an Xn interface, and the source CU uses the configuration information After the second indication information is processed, it is sent to the IAB sub-node or terminal device through the restored or migrated path.
  • Supplementary note 57 The method according to any one of supplementary notes 49 to 53, wherein the target CU sends the second indication information to the IAB sub-node or terminal device through an F1AP message.
  • Supplement 58 The method according to any one of Supplements 49 to 53, wherein the target CU sends the second indication information to the source CU through an Xn interface, and the source CU sends the information to the source CU through an F1AP message.
  • the second indication information is sent to the DU of the IAB node, and is sent to the IAB sub-node or terminal device by the DU of the IAB node.
  • Supplement 59 The method according to Supplement 48, wherein the network device is a source CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs);
  • the indication information is the fourth indication information sent by the source CU that performs radio link failure (RLF) recovery or conditional handover (CHO) migration across centralized units (inter-CUs).
  • Supplement 60 The method according to Supplement 59, wherein during or after a radio link failure (RLF) recovery process across centralized units (inter-CUs), the target CU sends a radio resource control re-establishment (RRC) reestablishment) message, or, receiving a radio resource control reestablishment complete (RRC reestablishment complete) message, or establishing an F1 interface with the IAB node, or sending BH configuration information, the source CU sends the IAB child node. Or the terminal device sends the fourth indication information.
  • RLF radio link failure
  • RRC radio resource control re-establishment
  • RRC reestablishment complete radio resource control reestablishment complete
  • Supplement 61 The method according to Supplement 59, wherein during or after the conditional handover (CHO) migration process across centralized units (inter-CUs), the target CU receives a radio resource control reconfiguration complete message, Or in the case of establishing an F1 interface with the IAB node or sending BH configuration information, the source CU sends the fourth indication information to the IAB sub-node or terminal device.
  • CHO conditional handover
  • Supplement 62 The method according to any one of Supplements 59 to 61, wherein the fourth indication information indicates a Radio Resource Control (RRC) layer and/or a Packet Data Convergence Protocol (PDCP) layer in the target CU configuration information.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • Supplement 63 The method according to any one of Supplements 59 to 62, wherein the fourth indication information includes at least one or any combination of the following information: next hop count (nextHopChainingCount), key set change indication (keySet ChangeIndicator), non-access stratum (NAS) security information (nas-Container), encryption algorithm (ciphering Algorithm), integrity protection algorithm (integrityProtAlgorithm).
  • Supplement 64 The method according to any one of Supplements 59 to 63, wherein the source CU receives the fourth indication information sent by the target CU through a radio resource control (RRC) message, and the source CU receives the fourth indication information sent by the target CU through a radio resource control (RRC) message, After the CU uses the configuration information to process the fourth indication information, it sends the DU to the IAB node through the Xn interface, and the DU of the IAB node sends the DU to the IAB sub-node or terminal device.
  • RRC radio resource control
  • RRC radio resource control
  • An integrated access and backhaul (IAB) communication method comprising:
  • the IAB node detects that a radio link failure (RLF) has occurred on the backhaul link between the IAB node and the parent node or is attempting RLF recovery or RLF recovery is successful or RLF recovery fails; and
  • RLF radio link failure
  • the IAB node sends RLF indication information to the IAB sub-node or terminal equipment to which it belongs; the RLF indication information indicates one of at least two types of backhaul link radio link failure (BH RLF).
  • BH RLF backhaul link radio link failure
  • Supplement 66 The method according to Supplement 65, wherein the type of the backhaul link radio link failure includes at least one of the following:
  • Type 1 of backhaul link radio link failure which means that the IAB node detects that a radio link failure (RLF) occurs in the backhaul link between the IAB node and the parent node,
  • RLF radio link failure
  • Type 2 of backhaul link radio link failure which means that the IAB node has detected a radio link failure (RLF) on the backhaul link between the IAB node and the parent node and the IAB node is attempting RLF recovery,
  • RLF radio link failure
  • Type 3 of backhaul link radio link failure which means that the IAB node detects that a radio link failure (RLF) occurs in the backhaul link between the IAB node and the parent node and the IAB node RLF recovery is successful,
  • RLF radio link failure
  • Type 4 of backhaul link radio link failure which means that the IAB node detects a radio link failure (RLF) on the backhaul link between the IAB node and the parent node and the IAB node RLF recovery fails.
  • RLF radio link failure
  • Supplement 67 The method according to Supplement 66, wherein the RLF indication information is sent to the IAB sub-node or terminal device by using a BAP control PDU; the PDU type field of the BAP control PDU indicates the backhaul chain Type of radio link failure.
  • Supplement 68 The method according to Supplement 67, wherein one value of more than one bit in the PDU type field of the BAP control PDU indicates type 4 of the backhaul link radio link failure; the other value indicates Type 2 of backhaul link radio link failure or Type 3 of backhaul link radio link failure.
  • Supplement 69 The method according to Supplement 67, wherein one value of the plurality of bits in the PDU type field of the BAP control PDU indicates type 4 of the backhaul link radio link failure; the other value indicates the return Type 2 of the radio link failure of the backhaul link; another value indicating type 3 of the radio link failure of the backhaul link.
  • Supplement 70 The method according to Supplement 66, wherein the R field of the BAP control PDU using the RLF indication information indicates the at least two types of backhaul link radio link failures.
  • Supplement 71 The method according to Supplement 70, wherein one value of 1 bit in the R field of the BAP control PDU indicates type 4 of the radio link failure of the backhaul link; the other value indicates the backhaul Link radio link failure type 2 or backhaul link radio link failure type 3.
  • Supplement 72 The method according to Supplement 70, wherein one value of the plurality of bits in the R field of the BAP control PDU indicates type 4 of the radio link failure of the backhaul link; the other value indicates the backhaul Type 2 for link radio link failure; another value indicates type 3 for backhaul link radio link failure.
  • IAB integrated access and backhaul
  • the IAB node detects that a radio link failure (RLF) has occurred on the backhaul link between the IAB node and the parent node or is attempting RLF recovery or RLF recovery is successful or RLF recovery fails; and
  • RLF radio link failure
  • the IAB node sends the RLF indication information to the served terminal equipment by using physical layer signaling, MAC layer signaling, RLC layer signaling or system information.
  • Supplement 74 The method of Supplement 73, wherein the physical layer signaling includes a downlink control information (DCI) format, the downlink control information (DCI) indicating a type of backhaul link radio link failure.
  • DCI downlink control information
  • Supplementary note 75 The method according to supplementary note 73, wherein the MAC layer signaling includes MAC CE;
  • One or more bits or a field in the MAC CE indicates the type of backhaul link radio link failure.
  • Supplement 76 The method according to Supplement 73, wherein the RLC layer signaling includes an RLC control PDU.
  • Supplement 77 The method according to Supplement 73, wherein the system information includes a master information block (MIB) and/or a system information block (SIB); a field in the MIB and/or the SIB indicates a backhaul chain Type of radio link failure.
  • MIB master information block
  • SIB system information block
  • Supplement 78 The method according to Supplement 77, wherein a cell barred field (cellBarred) in the MIB is set to barred or an IAB support field (IAB-support) in the SIB is not present.
  • cellBarred cell barred field
  • IAB-support IAB support field
  • An IAB sub-node or terminal device comprising a memory and a processor, the memory stores a computer program, and the processor is configured to execute the computer program to achieve any one of Supplements 1 to 37 The communication method of the IAB.
  • Supplement 80 A network device comprising a memory and a processor, wherein the memory stores a computer program, the processor is configured to execute the computer program to implement the IAB according to any one of Supplements 38 to 78 communication method.
  • a communication system comprising:
  • IAB child node or terminal device which executes the communication method of IAB as described in any one of Supplementary Notes 1 to 37;
  • a network device which executes the communication method of the IAB as described in any one of Supplementary Notes 38 to 64.
  • a communication system comprising:
  • the IAB node which executes the communication method of the IAB as described in any one of Supplementary Notes 65 to 78.

Landscapes

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

Abstract

本申请实施例提供一种集成的接入和回传(IAB)的通信方法以及装置。所述方法包括：IAB子节点或者终端设备接收网络设备发送的指示信息，根据该指示信息发起无线链路失败恢复过程或者连接重建过程；或者，IAB子节点或者终端设备接收网络设备发送的指示信息，所述指示信息指示对应的目标CU的配置信息，根据所述目标CU的配置信息进行通信。

Description

集成的接入和回传的通信方法以及装置 技术领域
本申请实施例涉及通信技术领域。
背景技术
集成的接入和回传(IAB，Integrated access and backhaul)使5G无线接入网(RAN，Radio Access Network)支持无线中继。中继节点被称为IAB-node(IAB节点)，支持通过NR的接入和回传。NR回传在网络侧的终止点被称为IAB-donor(IAB宿主，也可认为是一种IAB节点)，它表示一个具有支持IAB功能的gNB。可能通过单跳或多跳发生回传。
IAB节点支持gNB-DU(Distributed Unit，分布式单元)的功能，即IAB-DU。IAB-DU终止到终端设备和下一跳IAB节点的NR接入接口，并终止到IAB-donor上的gNB-CU(Centralized Unit，集中式单元)功能的F1协议。IAB-node DU也可被称为IAB-DU。
除了gNB-DU功能，IAB节点还支持一部分终端设备功能(UE功能)，可称为IAB-MT。IAB-MT例如包括物理层、层2(L2)、无线资源控制(RRC，Radio Resource Control)和非接入层(NAS，Non-Access-Stratum)功能，来连接到另一个IAB节点或IAB-donor的gNB-DU、连接到IAB-donor上gNB-CU和连接到核心网。
IAB节点通过一跳或多跳连接到一个IAB-donor。在拓扑中，该IAB-donor为根节点，IAB节点的IAB-DU接口上的邻节点被称为该IAB节点的子节点(descendant node或child node)，即IAB子节点(descendant IAB-node)，在IAB-MT接口上的邻节点被称为父节点(parent node)，即IAB父节点(parent IAB-node)。到子节点的方向被进一步称为下行流(downstream)，而到父节点的方向被称为上行流(upstream)。IAB-donor为该IAB拓扑执行集中式的资源、拓扑和路由管理。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
但是，发明人发现：在支持跨集中式单元(inter-CU)恢复或切换的情况下，假设 IAB子节点或终端设备随着恢复后或切换后(或称为迁移后)的IAB节点一起迁移到目标IAB-donor CU，由于IAB子节点或终端设备没有改变服务的IAB节点，IAB子节点或终端设备可能不会主动发起重建，因此不会更新CU的配置信息(例如，安全密钥(key)或其他参数)，从而导致无法与目标CU正确地通信。
针对上述问题的至少之一，本申请实施例提供一种集成的接入和回传(IAB)的通信方法以及装置。
根据本申请实施例的一个方面，提供一种集成的接入和回传(IAB)的通信方法，包括：
IAB子节点或者终端设备接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备认为检测到无线链路失败(RLF)或指示所述IAB子节点或者终端设备发起连接重建；以及
所述IAB子节点或终端设备发起无线链路失败恢复过程或者连接重建过程。
根据本申请实施例的另一个方面，提供一种集成的接入和回传(IAB)的通信装置，包括：
接收部，其接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备认为检测到无线链路失败(RLF)或指示所述IAB子节点或者终端设备发起连接重建；以及
处理部，其发起无线链路失败恢复过程或者连接重建过程。
根据本申请实施例的另一个方面，提供一种集成的接入和回传(IAB)的通信方法，包括：
IAB子节点或者终端设备接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备所对应的目标CU的配置信息；以及
所述IAB子节点或终端设备根据所述目标CU的配置信息进行通信。
根据本申请实施例的另一个方面，提供一种集成的接入和回传(IAB)的通信装置，包括：
接收部，其接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指 示所述IAB子节点或者终端设备所对应的目标CU的配置信息；以及
处理部，其根据所述目标CU的配置信息进行通信。
本申请实施例的有益效果之一在于：IAB子节点或者终端设备接收网络设备发送的指示信息，根据该指示信息发起无线链路失败恢复过程或者连接重建过程；或者，IAB子节点或者终端设备接收网络设备发送的指示信息，所述指示信息指示对应的目标CU的配置信息，根据所述目标CU的配置信息进行通信。由此，在支持inter-CU恢复或切换的情况下，即使IAB子节点或终端设备没有改变服务的IAB节点，IAB子节点或终端设备也会更新CU的配置信息，从而能够与目标CU正确地通信。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
图1是本申请实施例的通信系统的示意图；
图2是本申请实施例的IAB整体架构的一示意图；
图3是本申请实施例的IAB整体架构的另一示意图；
图4是本申请实施例的IAB网络中子节点和父节点关系的一示意图；
图5是IAB-DU和IAB-donor-CU间F1-U接口的协议栈的一示意图；
图6是IAB-DU和IAB-donor-CU间F1-C接口的协议栈的一示意图；
图7是本申请实施例的IAB-MT与IAB-donor-CU间SRB的协议栈的一示意图；
图8是IAB-node的Inter-CU的CHO过程的一示意图；
图9是IAB-node的Inter-CU的RLF恢复过程的一示意图；
图10是本申请实施例的inter-CU切换或恢复的场景示例图；
图11是本申请实施例的IAB的通信方法的一示意图；
图12是本申请实施例的IAB的通信方法的另一示意图；
图13是本申请实施例的IAB的通信方法的另一示意图；
图14是本申请实施例的IAB的通信方法的另一示意图；
图15是本申请实施例的IAB的通信方法的另一示意图；
图16是本申请实施例的IAB的通信方法的另一示意图；
图17是本申请实施例的IAB的通信方法的另一示意图；
图18是本申请实施例的IAB的通信方法的另一示意图；
图19是本申请实施例的IAB的通信方法的另一示意图；
图20是本申请实施例的IAB的通信方法的一场景示意图；
图21是本申请实施例的IAB的通信装置的一示意图；
图22是本申请实施例的IAB的通信装置的另一示意图；
图23是本申请实施例的网络设备的示意图；
图24是本申请实施例的终端设备的示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标 准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femeto、pico等等)、IAB(Integrated Access and Backhaul)节点或IAB-DU或IAB-donor。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。在不引起混淆的情况下，术语“小区”和“基站”可以互换。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment或Terminal Device)例如是指通过网络设备接入通信网络并接收网络服务的设备。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、IAB-MT、站(station)，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、 机器到机器(M2M，Machine to Machine)终端，等等。
此外，术语“网络侧”或“网络设备侧”是指网络的一侧，可以是某一基站，也可以包括如上的一个或多个网络设备。术语“用户侧”或“终端侧”或“终端设备侧”是指用户或终端的一侧，可以是某一UE，也可以包括如上的一个或多个终端设备。本文在没有特别指出的情况下，“设备”可以指网络设备，也可以指终端设备。
以下通过示例对本申请实施例的场景进行说明，但本申请不限于此。
图1是本申请实施例的通信系统的示意图，示意性说明了以终端设备和网络设备为例的情况，如图1所示，通信系统100可以包括网络设备101和终端设备102。为简单起见，图1仅以一个终端设备和一个网络设备为例进行说明，但本申请实施例不限于此，例如可以有多个终端设备。
在本申请实施例中，网络设备101和终端设备102之间可以进行现有的业务或者未来可实施的业务发送。例如，这些业务可以包括但不限于：增强的移动宽带(eMBB，enhanced Mobile Broadband)、大规模机器类型通信(mMTC，massive Machine Type Communication)和高可靠低时延通信(URLLC，Ultra-Reliable and Low-Latency Communication)，等等。
以下通过示例对本申请实施例的场景进行说明，但本发明不限于此。
图2是本申请实施例的IAB整体架构的一示意图；如图2所示，该IAB整体架构使用standalone模式。图3是本申请实施例的IAB整体架构的另一示意图；如图3所示，该IAB整体架构使用双连接(EN-DC)模式；在双连接模式中，IAB节点通过E-UTRA连接到一个MeNB，IAB宿主作为SgNB终止X2-C。
图4是本申请实施例的IAB网络中子节点和父节点关系的一示意图；如图4所示，IAB节点到子节点的方向被进一步称为下行流(downstream)，而到父节点的方向被称为上行流(upstream)。
图5是IAB-DU和IAB-donor-CU间F1-U接口的协议栈的一示意图；图6是IAB-DU和IAB-donor-CU间F1-C接口的协议栈的一示意图。在图5和图6中，F1-U和F1-C以2跳回传为例进行说明。F1-U和F1-C使用IAB-DU和IAB-donor-CU间的IP传输层，另外，F1-U和F1-C有安全保护。
在本申请实施例中，为了支持IAB网络中数据的传输和路由，回传适配协议(BAP，Backhaul Adaptation Protocol)层被引入。在IAB-node中，BAP子层包含一个位于MT功能的BAP实体和位于DU功能的另一个共位置的BAP实体。IP层通过BAP子层进行无线回传，以确保多跳路由；IP层也可以用于非F1业务，例如操作维护管理(OAM， Operation Administration and Maintenance)业务。
在本申请实施例中，在每个回传链路(link)上，BAP PDUs由BH无线链路控制(RLC，Radio Link Control)信道(channel)传输；在每个BH链路(BH link)上，可以配置多个BH RLC信道，这样允许通信优先化(traffic prioritization)和服务质量(QoS，Quality of Service)实施(enforcement)。每个IAB节点和IAB-donor-DU上的BAP实体执行BAP PDUs的BH RLC信道的映射。
图7是本申请实施例的IAB-MT与IAB-donor-CU间信令无线承载(SRB，Signalling Radio Bearer)的协议栈的一示意图。IAB-MT与IAB-donor-CU建立用于承载RRC和NAS的SRBs。如图7所示，IAB子节点(例如IAB节点2的IAB-MT)或终端设备在对端(网络侧)的RRC层和分组数据会聚协议(PDCP，Packet Data Convergence Protocol)层位于CU上。
以上示意性说明了IAB网络，以下再对恢复和切换进行示意性说明。
在常规切换(HO，Handover)过程中，终端设备向网络发送测量报告(measurement report)消息；如果网络设备判断该终端设备需要切换，则会将目标小区的相关配置通过RRC重配置消息(携带reconfiguration with sync)发送给终端设备。终端设备收到该RRC重配置消息时，就开始执行切换过程。由于终端设备发送的测量报告可能无法被网络设备正确地接收、或者网络设备发送的RRC重配置消息可能无法被终端设备正确地收到，因此切换可能发生失败。
在Rel-16中，为提升切换可靠性，减少切换失败，引入了条件切换(CHO，conditional handover)。在CHO中，网络设备在条件重配置中为终端设备配置一个或更多候选目标小区(例如SpCell)。终端设备评估每个配置的候选目标小区对应的条件。如果一个目标候选小区对应的条件(即测量事件)被满足，那么终端设备发起到该小区的条件切换，应用与该小区相关的条件重配置。3GPP已经同意在IAB中以Rel-16CHO作为基线。
图8是IAB-node的Inter-CU的CHO过程的一示意图。如图8中的801至810所示，源CU(或源donor CU)决定对IAB节点进行CHO配置(801)，之后源CU向一个或更多目标CU(或目标donor CU)发送切换请求消息(802)。
如果目标CU决定接受IAB节点的迁移，则目标CU与目标IAB父节点之间进行UE上下文建立过程(803和804)，为该IAB节点在目标IAB父节点中准备相关的配置和/或资源。然后目标CU向源CU发送切换请求确认消息(805)，其中携带目标小区的条件重配置。
源CU在收到一个或更多目标CU的切换请求确认消息后，通过源IAB父节点向该IAB节点发送RRC重配置(RRC reconfiguration)消息(807)，其中包括一个或更多目标小区的配置和对应的条件。IAB节点接收并存储该RRC重配置消息，回复RRC重配置完成消息(809)。
IAB节点根据RRC重配置消息中包括的一个或更多目标小区的配置和对应的条件，进行条件的评估。当认为满足条件时，可以从源CU去附着(detach)并应用存储的满足条件的目标小区的配置，通过随机接入信道(RACH)发起到该目标小区的随机接入。
如图8中的811至812所示，IAB节点可以执行CHO。在IAB节点成功迁移到目标CU后，目标CU可以通知源CU释放该IAB节点的上下文，如图8中的813至814所示。
在Rel-16中，IAB节点还可以执行Inter-CU的无线链路失败(RLF，Radio Link Failure)恢复(recovery)。图9是IAB-node的Inter-CU的RLF恢复过程的一示意图，在图9中，为简单起见省略了部分实体，例如源IAB父节点可以包括initial parent IAB-node、intermediate hop IAB-node on initial path和initial IAB-donor-DU中的至少一个，目标IAB父节点可以包括new parent IAB-node、intermediate hop IAB-node on new path和new IAB-donor-DU中的至少一个。
如图9所示，IAB-node的inter-CU RLF恢复过程可以包括：
901：IAB node(IAB-MT)检测到(BH，backhaul)的RLF；
902：IAB MT执行到目标IAB父节点(也可称为新的IAB父节点)的同步和RACH，该目标IAB父节点由目标IAB-donor CU(也可称为新的IAB-donor CU)服务。
903-904：恢复的IAB MT通过目标IAB父节点发送RRC重建请求消息到目标IAB-donor CU；
905-906：目标IAB-donor CU通过Xn接口，从源IAB-donor CU(也可称为旧的IAB-donor CU)获取该IAB MT的UE上下文(context)；
907：目标IAB-donor CU向目标IAB父节点发起UE上下文建立过程，以对恢复的IAB-MT建立F1逻辑连接。
908：目标IAB-donor CU通过目标IAB父节点发送RRC重建消息给IAB-MT；
909：恢复的IAB MT通过目标IAB父节点发送RRC重建完成消息到目标IAB-donor CU；
910-911：目标IAB-donor CU通过目标IAB父节点发送RRC重配置消息给恢复的 IAB-MT，恢复的IAB-MT响应RRC重配置完成消息。
912：IAB-donor CU配置目标IAB父节点和目标IAB-donor DU之间新路径(path)上的BH RLC信道(channels)和BAP子层路由(routing)条目、以及目标IAB-donor DU上对恢复的IAB-node的新路径的DL映射。
913：恢复的IAB节点的DU与目标CU建立或重定向F1-C连接、以及建立或更新F1接口上下文、UE上下文等。
914：IAB-donor CU更新与到恢复的IAB-node的F1-U连接，例如更新每个GTP tunnel关联的UL BH信息。
915：目标IAB-donor CU发送UE上下文释放消息来指示源IAB-donor CU释放恢复的IAB-node的资源。
916：源IAB-donor CU发送UE上下文释放完成消息到源IAB父节点。
917：源IAB父节点释放恢复的IAB-MT上下文，并响应UE上下文释放完成消息。
918：源IAB-donor CU释放源IAB父节点和源IAB-donor DU之间的源路径上的BH RLC信道和BAP子层的路由条目。
以上对于IAB节点执行Inter-CU的CHO和RLF恢复进行了示意性说明，本申请不限于此，关于切换或恢复的内容还可以参考相关技术。
在Rel-16中，只支持intra-CU RLF恢复或者到intra-CU的CHO，其中IAB-node在RLF恢复或执行CHO后，仍然连接到迁移前的IAB donor CU(以下简称CU)。这种情况下，IAB子节点或终端设备可以随着该IAB-node在恢复或CHO后的路径与CU通信。由于CU未改变，也就是IAB子节点或终端设备在对端(网络侧)的RRC层和PDCP层未改变，不会有CU的配置信息改变而IAB子节点或终端设备无法获得该配置信息的问题，例如更新的安全密钥key或其它安全参数等可以由CU通过恢复或CHO的IAB节点发送给IAB子节点或终端设备。
在Rel-17中，支持inter-CU RLF恢复或inter-CU的CHO。
图10是本申请实施例的inter-CU切换或恢复的场景示例图。如图10所示，IAB-node恢复或CHO到目标IAB-donor CU时，该IAB-node的DU提供的小区的物理层小区标识(PCI，Physical Cell Identity)和频率可能保持不改变。如果该IAB-node的IAB子节点或终端设备仍然在原小区的覆盖下，那么拓扑关系可以保持不变，IAB子节点或终端设备随着该IAB节点一起迁移到目标CU下。
假设IAB子节点或终端设备随着恢复或CHO的IAB-node一起迁移到目标 IAB-donor CU(以下简称目标CU)下，由于对应的RRC和PDCP层位于目标CU，而目标CU由于是与源CU不同的gNB设备，因而会采用与源CU不同的配置信息，例如安全参数(例如key等)和/或安全算法等，因此子节点或终端设备需要更新目标CU的配置信息。
但是，由于IAB子节点或终端设备没有改变服务的IAB-node，IAB子节点或终端设备可能不会发起重建过程来获得目标CU的配置信息，另外也无法正确接收目标CU使用目标CU的配置(例如安全参数和/或安全算法等)发送的配置信息，因此不会更新目标CU的配置信息，从而导致无法与目标CU正确地通信。
针对上述问题，以下对本申请实施例进行进一步说明。在本申请实施例中，“当……时”、“在……情况下”、“对于……的情况”以及“如果……”表示基于某个或某些条件或状态等，另外，这些表述方式可以互相替换。此外，“指示”可以是显式地包含某些信息以进行通知，也可以是隐式地通过某些特征进行通知等。
第一方面的实施例
本申请实施例提供一种IAB的通信方法，从IAB子节点或终端设备进行说明。图11是本申请实施例的IAB的通信方法的一示意图，如图11所示，该方法包括：
1101，IAB子节点或者终端设备接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备认为检测到无线链路失败(RLF)或指示所述IAB子节点或者终端设备发起连接重建；以及
1102，所述IAB子节点或终端设备发起无线链路失败恢复过程或者连接重建过程。
值得注意的是，以上附图11仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图11的记载。
由此，IAB子节点或终端设备发起无线链路失败恢复过程或者连接重建过程，能够获得目标CU的配置信息。IAB子节点或终端设备能够更新目标CU的配置信息，从而能够与目标CU正确地通信。关于无线链路失败恢复过程或者连接重建过程的具体内容，可以参考后述的实施例，还可以参考相关技术，例如可以参考图8和9等。
在一些实施例中，所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF) 恢复或条件切换(CHO)迁移的IAB节点发送的第一指示信息。
图12是本申请实施例的IAB的通信方法的一示意图，如图12所示，RLF恢复或CHO过程进行中或之后的IAB节点可以向所属的IAB子节点或终端设备发送第一指示信息；IAB子节点或者终端设备接收到该第一指示信息后，认为检测到无线链路失败(RLF)或者发起连接重建过程。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中，在所述IAB节点接收到目标集中式单元(Target CU)发送的无线资源控制重建立(RRC reestablishment)消息、或者与目标CU建立F1接口、或者接收到回传(BH)配置信息的情况下，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。本实施例中目标CU是IAB节点进行RLF恢复的小区所在的donor CU，例如是IAB节点进行RRC连接重建过程所选择的小区所在的donor CU。
例如，IAB节点发送该第一指示信息的时刻可以是图9中的907至915的任意时间点。例如恢复的IAB-MT发送RRC re-establishment request消息的时刻，或者恢复的IAB-MT收到RRC re-establishment消息的时刻，或者恢复的IAB-MT发送RRC re-establishment complete消息的时刻，或者恢复的IAB-node的MT收到RRC连接重建后第一条RRC重配置(RRC reconfiguration)消息的时刻，或者恢复的IAB-node的MT发送RRC重配置完成(RRC reconfiguration complete)消息的时刻，或者恢复的IAB-node的DU向目标CU发送F1AP setup request消息的时刻，或者从目标CU接收到F1 setup response消息的时刻，或者目标CU和恢复的IAB-node之间的SCTP连接被建立的时刻，或者F1-C连接被切换来使用恢复的IAB-node的新的TNL地址和新的IAB-donor CU的TNL地址的时刻，
或者目标CU与恢复的IAB-DU建立或重建或更新F1接口上下文的时刻，例如gNB DU配置更新过程或者gNB CU配置更新过程的时刻；或者目标CU与恢复的IAB-DU建立或重建或更新对恢复的IAB-node的子IAB-node或UE的F1AP UE context的时刻；或者恢复的IAB-node的DU收到BH配置信息的时刻，该BH配置信息可以包括例如目标IAB父节点和目标IAB-donor DU之间新路径上的BH RLC channels和BAP子层routing条目、或目标IAB-donor DU上对恢复的IAB-node的新路径的DL映射；或者更新F1-U连接(例如GTP隧道信息)的时刻，等等。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程之后，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。本实 施例中目标CU是IAB节点进行RLF恢复的小区所在的donor CU，例如是IAB节点进行RRC连接重建过程所选择的小区所在的donor CU。
在一些实施例中，在所述IAB子节点或终端设备为单连接的情况下，或者所述IAB子节点或终端设备被配置双连接且所述IAB节点为所述IAB子节点或终端设备的主小区组(MCG)的情况下，所述IAB子节点或终端设备认为(确定)对MCG检测到无线链路失败(RLF)。
例如，所述IAB子节点或终端设备发起无线链路失败恢复过程，包括：所述IAB子节点在接入层安全(AS security)已经被激活且SRB2已经被建立的情况下，或者所述终端设备在接入层安全(AS security)已经被激活且SRB2和至少一个数据无线承载(Data Radio Bearer，DRB)已经被建立的情况下，在定时器(T316)被配置、且SCG发送没有被挂起、且主服务小区改变(PSCell change)没有在进行的情况下，所述IAB子节点或终端设备发起MCG失败信息(MCG failure information)过程来报告MCG无线链路失败，否则发起连接重建过程。
在一些实施例中，在所述IAB子节点或终端设备被配置双连接且所述IAB节点为所述IAB子节点或终端设备的辅小区组(SCG)的情况下，所述IAB子节点或终端设备认为(确定)对SCG检测到无线链路失败(RLF)。
例如，所述IAB子节点或终端设备发起无线链路失败恢复过程，包括：在MCG发送没有被挂起的情况下，所述IAB子节点或终端设备发起SCG失败信息(SCG failure information)过程来报告SCG无线链路失败，否则发起所述连接重建过程。
在一些实施例中，在所述IAB子节点或终端设备被配置CHO的情况下，所述IAB子节点或终端设备可以发起CHO过程。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中，在所述IAB节点发起条件切换(CHO)、或者发送无线资源控制重配置完成(RRC reconfiguration complete)消息、或者与目标CU建立F1接口、或者接收到BH配置信息的情况下，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
例如，IAB节点发送该第一指示信息的时刻可以是图8中的HO条件评估至811的任意时间点。例如IAB-node发起CHO(例如，detach from source或开始应用存储的满足条件的目标小区的条件重配置或开始向目标小区发起RACH)的时刻，或发送RRC reconfiguration complete消息的时刻，或收到RRC reconfiguration complete消息的RLC层确认或HARQ确认的时刻，或者IAB-node的DU向目标CU发送F1AP setup request 消息的时刻，或者从目标CU接收到F1 setup response消息的时刻，或者目标CU和IAB-node之间的SCTP连接被建立的时刻，或者F1-C连接被切换来使用IAB-node的新的TNL地址和目标CU的TNL地址的时刻，
或者目标CU与IAB-DU建立或重建或更新F1接口上下文的时刻，例如gNB DU配置更新过程或者gNB CU配置更新过程的时刻；或者目标CU与IAB-node的DU建立或重建或更新对恢复的IAB-node的子IAB-node或UE的F1AP UE context的时刻；或者IAB-node的DU收到BH配置信息的时刻，该BH配置信息可以包括例如目标IAB父节点和目标IAB-donor DU之间新路径上的BH RLC channels和BAP子层routing条目、或目标IAB-donor DU上对IAB-node的新路径的DL映射；或者更新F1-U连接(例如GTP隧道信息)的时刻，等等。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程之后，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
在一些实施例中，所述第一指示信息包括如下至少之一或任意组合：回传适配协议(BAP)协议数据单元(PDU)、无线链路控制(RLC)PDU、介质访问控制(MAC)控制信元(CE)、介质访问控制(MAC)子头、物理层信令。
例如，可以定义新的BAP control PDU，或者采用BH RLF indication，例如type 3 BH RLF indication的BAP control PDU，或者定义新的RLC control PDU等。关于BH RLF indication的内容还可以参考后述的第三方面的实施例。
再例如，可以定义新的MAC CE，该MAC CE对应子头(subheader)中一个新的LCID；或者定义新的MAC子头，该MAC子头采用新的LCID。
再例如，可以使用DCI中的一个域，可以采用group common DCI、common DCI或UE-specific DCI、或Paging-DCI等，该域可以是1bit。
在一些实施例中，第一指示信息还可以指示IAB节点的donor CU是否发生了改变，或者指示IAB节点进行了相同CU的迁移(intra-CU migration)还是跨CU的迁移(inter-CU migration)。
在一些实施例中，第一指示信息包含下面至少一个：CU改变指示，目标CU的标识和发起重建过程的指示等。
以上以IAB节点发送第一指示信息为例进行了说明，以下再对源CU发送第三指示信息进行说明。
在一些实施例中，所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF) 恢复或条件切换(CHO)迁移的源集中式单元(Source CU)通过恢复后或迁移后的路径发送的第三指示信息。
图13是本申请实施例的IAB的通信方法的另一示意图，如图13所示，源CU可以向IAB子节点或终端设备发送第三指示信息；IAB子节点或者终端设备接收到该第三指示信息后，认为检测到无线链路失败(RLF)或者发起连接重建过程。
在一些实施例中，所述源集中式单元(CU)通过Xn接口将所述第三指示信息发送给目标CU或者所述IAB节点的分布式单元(DU)，并且由所述目标CU或所述DU将所述第三指示信息发送给所述IAB子节点或者终端设备。
例如，如图13所示，源CU可以通过Xn接口将承载了第三指示信息的RRC消息发送给目标IAB-donor CU，该目标IAB-donor CU通过DL RRC MESSAGE TRANSFER将第三指示信息发送给切换后或恢复后的IAB节点，由该IAB节点通过RRC消息或者PDCP控制PDU将该第三指示信息发送给IAB子节点或者终端设备。
如图13所示，IAB子节点或者终端设备可以认为检测到无线链路失败(RLF)或者发起连接重建过程；此外，IAB子节点或者终端设备还可以发送响应消息或完成消息给切换后或恢复后的IAB节点(可选的)，该IAB节点还可以通过UL RRC MESSAGE TRANSFER向目标IAB-donor CU发送信息(可选的)。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中，在所述源CU接收到目标CU发送的取回上下文请求消息的情况下，或者向所述目标CU发送取回上下文响应消息的情况下，或者接收到目标CU发送的上下文释放消息的情况下，所述源CU发送所述第三指示信息。
例如，对于inter-CU RLF恢复，源CU发送该第三指示信息的时刻可以是如下任意时间点：例如源CU通过Xn接口收到目标IAB-donor CU发送的Retrieve UE context request消息的时刻，或者通过Xn接口向目标IAB-donor CU发送Retrieve UE context response消息的时刻，或者收到目标IAB-donor CU发送的UE context release消息的时刻或之后，等等。
再例如，对于inter-CU RLF恢复场景，第三指示信息的发送时刻包括：恢复的IAB-MT发送RRC re-establishment request消息的时刻，或者恢复的IAB-MT收到RRC re-establishment消息的时刻，或者恢复的IAB-MT发送RRC re-establishment complete消息的时刻，或者恢复的IAB-node的MT收到RRC连接重建后第一条RRC重配置(RRC reconfiguration)消息的时刻，或者恢复的IAB-node的MT发送RRC重配置完成(RRC  reconfiguration complete)消息的时刻，或者恢复的IAB-node的DU向目标CU发送F1AP setup request消息的时刻，或者从目标CU接收到F1 setup response消息的时刻，或者目标CU和恢复的IAB-node之间的SCTP连接被建立的时刻，或者F1-C连接被切换来使用恢复的IAB-node的新的TNL地址和新的IAB-donor CU的TNL地址的时刻，
或者目标CU与恢复的IAB-DU建立或重建或更新F1接口上下文的时刻，例如gNB DU配置更新过程或者gNB CU配置更新过程的时刻；或者目标CU与恢复的IAB-DU建立或重建或更新对恢复的IAB-node的子IAB-node或UE的F1AP UE context的时刻；或者恢复的IAB-node的DU收到BH配置信息的时刻，该BH配置信息可以包括例如目标IAB父节点和目标IAB-donor DU之间新路径上的BH RLC channels和BAP子层routing条目、或目标IAB-donor DU上对恢复的IAB-node的新路径的DL映射；或者更新F1-U连接(例如GTP隧道信息)的时刻，等等。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程之后，所述源CU发送所述第三指示信息。
在一些实施例中，在所述IAB子节点或终端设备为单连接的情况下，或者所述IAB子节点或终端设备被配置双连接且所述IAB节点为所述IAB子节点或终端设备的主小区组(MCG)的情况下，所述IAB子节点或终端设备确定(认为)对MCG检测到无线链路失败(RLF)。
例如，所述IAB子节点或终端设备发起无线链路失败恢复过程，包括：所述IAB子节点在接入层安全(AS security)已经被激活且SRB2已经被建立的情况下，或者所述终端设备在接入层安全(AS security)已经被激活且SRB2和至少一个数据无线承载(Data Radio Bearer，DRB)已经被建立的情况下，在定时器(T316)被配置且SCG发送没有被挂起且主服务小区改变(PSCell change)没有在进行的情况下，所述IAB子节点或终端设备发起MCG失败信息过程来报告MCG无线链路失败，否则发起所述连接重建过程。
在一些实施例中，在所述IAB子节点或终端设备被配置双连接且所述IAB节点为所述IAB子节点或终端设备的辅小区组(SCG)的情况下，所述IAB子节点或终端设备确定(认为)对SCG检测到无线链路失败(RLF)。
例如，所述IAB子节点或终端设备发起无线链路失败恢复过程，包括：在MCG发送没有被挂起的情况下，所述IAB子节点或终端设备发起SCG失败信息过程来报告SCG无线链路失败，否则发起所述连接重建过程。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中，所述源CU在接收到目标CU发送的上下文释放消息的情况下，发送所述第三指示信息。
例如，对于inter-CU CHO，源CU发送该第三指示信息的时刻可以是如下任意时间点：在图8的813中，源CU接收到目标IAB-donor CU发送的UE context release消息的时刻或之后。
再例如，对于inter-CU CHO场景，第三指示信息的发送时刻包括：IAB-node发起CHO(例如，detach from source或开始应用存储的满足条件的目标小区的条件重配置或开始向目标小区发起RACH)的时刻，或发送RRC reconfiguration complete消息的时刻，或收到RRC reconfiguration complete消息的RLC层确认或HARQ确认的时刻，或者IAB-node的DU向目标CU发送F1AP setup request消息的时刻，或者从目标CU接收到F1 setup response消息的时刻，或者目标CU和IAB-node之间的SCTP连接被建立的时刻，或者F1-C连接被切换来使用IAB-node的新的TNL地址和目标CU的TNL地址的时刻，
或者目标CU与IAB-DU建立或重建或更新F1接口上下文的时刻，例如gNB DU配置更新过程或者gNB CU配置更新过程的时刻；或者目标CU与IAB-node的DU建立或重建或更新对恢复的IAB-node的子IAB-node或UE的F1AP UE context的时刻；或者IAB-node的DU收到BH配置信息的时刻，该BH配置信息可以包括例如目标IAB父节点和目标IAB-donor DU之间新路径上的BH RLC channels和BAP子层routing条目、或目标IAB-donor DU上对IAB-node的新路径的DL映射；或者更新F1-U连接(例如GTP隧道信息)的时刻，等等。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程之后，所述源CU发送所述第三指示信息。
在一些实施例中，所述第三指示信息包括如下至少之一或任意组合：分组数据会聚协议(PDCP)协议数据单元(PDU)、无线资源控制(RRC)消息、F1AP消息。
例如，第三指示信息可以包括在PDCP PDU(其中承载RRC消息或是PDCP control PDU)，采用旧的key和安全算法等加密和/或完整性保护；再例如，对于descendant IAB-node，第三指示信息还可以承载在F1AP消息中，发送给该descendant IAB-node的DU。
在一些实施例中，第三指示信息还可以指示IAB节点的donor CU是否发生了改变，或者指示IAB节点进行了相同CU的迁移(intra-CU migration)还是跨CU的迁移 (inter-CU migration)。
在一些实施例中，第三指示信息包含下面至少一个：CU改变指示，目标CU的标识和发起重建过程的指示等。
在本申请实施例中，descendant IAB-nodes或UE可以向CU指示其能力，以表明是否支持上述实施例中的通信方法。此外，RRC消息例如可以是RRC re-establishment消息或RRC reconfiguration消息；F1AP消息可以是UE context setup request或UE context modification request；Xn消息可以是RRC transfer或Retrieve UE context response等。
在一些实施例中，所述CU的配置信息可以包括下面的至少一种或任意组合：RRC层的配置、PDCP层的配置、RLC层的配置、MAC层的配置、物理层的配置和BAP层的配置。
值得注意的是，以上附图11至13可以与附图8或9结合起来，但本申请不限于此，还可以与其他inter-CU的恢复或切换过程结合起来，本申请实施例不限制这些过程中的具体步骤或执行顺序。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，IAB子节点或者终端设备接收网络设备发送的指示信息，根据该指示信息发起无线链路失败恢复过程或者连接重建过程。由此，在支持inter-CU恢复或切换的情况下，即使IAB子节点或终端设备没有改变服务的IAB节点，IAB子节点或终端设备也会更新CU的配置信息，从而能够与目标CU正确地通信。
第二方面的实施例
本申请实施例提供一种IAB的通信方法，从IAB子节点或者终端设备进行说明。与第一方面的实施例相同的内容不再赘述。
图14是本申请实施例的IAB的通信方法的一示意图，如图14所示，该方法包括：
1401，IAB子节点或者终端设备接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备所对应的目标CU的配置信息；以及
1402，所述IAB子节点或终端设备根据所述目标CU的配置信息进行通信。
值得注意的是，以上附图14仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图14的记载。
由此，IAB子节点或终端设备接收网络设备发送的目标CU的配置信息，IAB子节点或终端设备能够更新CU的配置信息，从而能够与目标CU正确地通信。
在一些实施例中，目标CU(即目标donor CU)的配置信息可以包括下面的至少一种或任意组合：无线资源控制(RRC)层的配置、分组数据会聚协议(PDCP)层的配置、RLC层的配置、MAC层的配置、物理层的配置和BAP层的配置，该配置信息可以包括安全相关的配置，例如安全key、安全算法、应用主小区组还是辅小区组的安全参数等。
在一些实施例中，该指示信息可以与该目标CU的配置信息相同，例如该指示信息直接包括该目标CU的配置信息；该指示信息也可以不同于该目标CU的配置信息，例如该指示信息可以仅指示该目标CU的配置信息的序号或索引，或者该指示信息是该目标CU的配置信息的一部分，等等。
在一些实施例中，所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的所述目标CU发送的第二指示信息。例如，恢复后或CHO后的IAB-node的IAB子节点或终端设备的上下文被提前由源CU(即源donor CU)通过Xn接口发送到目标CU。例如，与IAB-node的上下文一起被发送，例如在RLF恢复的情况下，通过Retrieve UE Context Response消息由源CU发送到目标CU，在CHO情况下，通过Handover Request消息由源CU发送到目标CU。或者恢复后或迁移后的IAB-node的descendant IAB-node或UE的上下文被单独发送，例如在IAB-node恢复或CHO到目标CU后，由目标CU向源CU获取(例如收到恢复或CHO的IAB-node发送的RRC Reconfiguration complete消息或与恢复或CHO的IAB-node建立F1接口后)，或者由源CU发送给目标CU(例如收到释放恢复或CHO的IAB-node的UE context release消息后)。目标CU可以根据IAB子节点或终端设备的上下文，向IAB子节点或终端设备发送该第二指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中，在所述目标CU发送无线资源控制重建立(RRC reestablishment)消息、或者接收到无线资源控制重建立完成(RRC reestablishment complete)消息、或者与所述IAB 节点建立F1接口、或者发送BH配置信息的情况下，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
例如，对于inter-CU RLF恢复场景，目标CU发送该第二指示信息的时刻可以是图9中的907至915的任意时间点。例如恢复的IAB-MT发送RRC re-establishment request消息的时刻，或者恢复的IAB-MT收到RRC re-establishment消息的时刻，或者恢复的IAB-MT发送RRC re-establishment complete消息的时刻，或者恢复的IAB-node的MT收到RRC连接重建后第一条RRC重配置(RRC reconfiguration)消息的时刻，或者恢复的IAB-node的MT发送RRC重配置完成(RRC reconfiguration complete)消息的时刻，或者恢复的IAB-node的DU向目标CU发送F1AP setup request消息的时刻，或者从目标CU接收到F1 setup response消息的时刻，或者目标CU和恢复的IAB-node之间的SCTP连接被建立的时刻，或者F1-C连接被切换来使用恢复的IAB-node的新的TNL地址和新的IAB-donor CU的TNL地址的时刻，
或者目标CU与恢复的IAB-DU建立或重建或更新F1接口上下文的时刻，例如gNB DU配置更新过程或者gNB CU配置更新过程的时刻；或者目标CU与恢复的IAB-DU建立或重建或更新对恢复的IAB-node的子IAB-node或UE的F1AP UE context的时刻；或者恢复的IAB-node的DU收到BH配置信息的时刻，该BH配置信息可以包括例如目标IAB父节点和目标IAB-donor DU之间新路径上的BH RLC channels和BAP子层routing条目、或目标IAB-donor DU上对恢复的IAB-node的新路径的DL映射；或者更新F1-U连接(例如GTP隧道信息)的时刻，等等。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程之后，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中，在所述目标CU接收到无线资源控制重配置完成消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
例如，对于inter-CU CHO场景，目标CU发送该第二指示信息的时刻可以是图8中的HO条件评估至811的任意时间点。例如IAB-node发起CHO(例如，detach from source或开始应用存储的满足条件的目标小区的条件重配置或开始向目标小区发起RACH)的时刻，或发送RRC reconfiguration complete消息的时刻，或收到RRC reconfiguration complete消息的RLC层确认或HARQ确认的时刻，或者IAB-node的DU 向目标CU发送F1AP setup request消息的时刻，或者从目标CU接收到F1 setup response消息的时刻，或者目标CU和IAB-node之间的SCTP连接被建立的时刻，或者F1-C连接被切换来使用IAB-node的新的TNL地址和目标CU的TNL地址的时刻，
或者目标CU与IAB-DU建立或重建或更新F1接口上下文的时刻，例如gNB DU配置更新过程或者gNB CU配置更新过程的时刻；或者目标CU与IAB-node的DU建立或重建或更新对恢复的IAB-node的子IAB-node或UE的F1AP UE context的时刻；或者IAB-node的DU收到BH配置信息的时刻，该BH配置信息可以包括例如目标IAB父节点和目标IAB-donor DU之间新路径上的BH RLC channels和BAP子层routing条目、或目标IAB-donor DU上对IAB-node的新路径的DL映射；或者更新F1-U连接(例如GTP隧道信息)的时刻，等等。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程之后，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
在一些实施例中，所述第二指示信息指示所述目标CU中无线资源控制(RRC)层和/或分组数据会聚协议(PDCP)层的配置信息。例如，所述第二指示信息包括如下信息的至少之一或任意组合：下一跳计数(nextHopChainingCount)、密钥集改变指示(keySet ChangeIndicator)、非接入层(NAS)安全信息(nas-Container)、加密算法(ciphering Algorithm)、完整性保护算法(integrityProtAlgorithm)；但本申请不限于此。
在一些实施例中，所述第二指示信息还可以指示IAB节点的donor CU是否发生了改变，或者指示IAB节点进行了相同CU的迁移(intra-CU migration)还是跨CU的迁移(inter-CU migration)。
在一些实施例中，第二指示信息还可以包含CU改变指示和/或目标CU的标识等。
在一些实施例中，所述目标CU通过无线资源控制(RRC)消息，将未加密或者被默认加密的第二指示信息发送给所述IAB子节点或者终端设备。
图15是本申请实施例的IAB的通信方法的另一示意图，如图15所示，目标CU通过DL RRC MESSAGE TRANSFER将承载了第二指示信息的RRC消息发送给恢复后或切换后的IAB节点，由该IAB节点通过RRC消息将该第二指示信息发送给IAB子节点或者终端设备。
如图15所示，IAB子节点或者终端设备可以获得目标CU的配置信息；此外，IAB子节点或者终端设备还可以发送响应消息或完成消息给切换后或恢复后的IAB节点(可选的)，该IAB节点还可以通过UL RRC MESSAGE TRANSFER向目标IAB-donor CU 发送信息(可选的)。
以下对于IAB子节点或者终端设备如何正确地得到该第二指示信息进行说明。
IAB子节点或UE在发送RRC re-establishment request过程中，会配置低层挂起对SRB1的完整性保护和加密(configure lower layers to suspend integrity protection and ciphering for SRB1；NOTE:Ciphering is not applied for the subsequent RRCReestablishment message used to resume the connection.An integrity check is performed by lower layers,but merely upon request from RRC)。在图15所示的实施例中，由于不是descendant IAB-nodes或UE发起的重建，需要让它们挂起对SRB1的完整性保护和加密，也就是对该RRC消息不执行加密。
在一些实施例中，所述IAB子节点或者终端设备接收所述IAB节点的通知消息；以及所述IAB子节点或者终端设备根据所述通知消息挂起对信令无线承载(SRB)的完整性保护和加密操作，以获得所述第二指示信息。
例如，由RLF恢复或CHO迁移的IAB-node通知descendant IAB-nodes或UE，例如通过PHY或MAC或RLC或BAP层的信令发送；descendant IAB-nodes或UE收到该通知后，挂起对SRB1的完整性保护和加密。
在一些实施例中，所述IAB子节点或者终端设备对所述无线资源控制(RRC)消息进行解密和解码操作；以及在不能成功解码的情况下，对所述无线资源控制(RRC)消息不进行解密或进行默认解密操作，并且进行解码操作以获得所述第二指示信息。
例如，IAB子节点或终端设备的RRC层在低层(例如PDCP层)上报解密失败和/或完整性检查失败时，RRC层配置低层(例如PDCP)对SRB1不应用解密和/或完整性检查，再对这个PDCP PDU进行解密和/或完整性检查，如果低层解密和/或完整性检查成功，则低层将该消息传递到RRC层。
再例如，IAB子节点或终端设备的RRC层配置低层(例如PDCP)对SRB1执行完整性保护和加密，但如果低层解密失败和/或完整性检查失败，则低层不应用解密和/或完整性检查，再对这个PDCP PDU进行解密和/或完整性检查，如果低层解密和/或完整性检查成功，则将该消息传递到RRC层。
以上以未加密为例进行了说明，但本申请不限于此，例如还可以是默认加密。例如，加密的key采用默认的key，或者加密(或安全)算法是采用算法0，等等。
在一些实施例中，所述目标CU通过无线资源控制(RRC)消息，使用所述源CU的配置信息将所述第二指示信息发送给所述IAB子节点或者终端设备。
例如，目标CU使用源CU(旧CU)的安全算法和/或安全参数(例如keys)发送该第二指示信息。
在一些实施例中，所述目标CU通过Xn接口将所述第二指示信息发送给所述源CU，并且由所述源CU使用配置信息处理所述第二指示信息后，通过恢复后或迁移后的路径发送给所述IAB子节点或者终端设备。
图16是本申请实施例的IAB的通信方法的另一示意图，如图16所示，目标CU通过Xn接口将承载第二指示信息的RRC消息(包含在XnAP消息中的RRC container)发送给源CU，由源CU使用安全算法和/或安全参数(例如keys)进行处理(例如源CU的PDCP层使用IAB子节点或终端设备对应的安全算法和/或安全参数进行加密和/或完整性保护)后，通过F1AP消息DL RRC MESSAGE TRANSFER(使用新的路径)将处理后的第二指示信息发送给恢复或CHO的IAB节点，该IAB节点将包含该处理后的第二指示信息的RRC消息发送给IAB子节点或者终端设备。
如图16所示，IAB子节点或者终端设备可以使用源CU的配置信息(例如安全算法和/或安全参数)获得目标CU的配置信息；此外，IAB子节点或者终端设备还可以发送响应消息或完成消息给切换后或恢复后的IAB节点(可选的)，例如RRC reestablishment complete消息或RRC reconfiguration complete消息等，该IAB节点还可以通过F1AP消息UL RRC MESSAGE TRANSFER向目标IAB-donor CU发送信息(可选的)。
在一些实施例中，所述目标CU通过F1AP消息将所述第二指示信息发送给所述IAB子节点或者终端设备。
图17是本申请实施例的IAB的通信方法的另一示意图，如图17所示，目标CU将承载第二指示信息的F1AP消息发送给恢复或CHO的IAB节点，由该IAB节点通过PHY、MAC、RLC或BAP信令将该第二指示信息发送给IAB子节点或者终端设备。
例如，当第二指示信息包含NextHopChainingCount时，PHY、MAC、RLC或BAP信令中可以包含3bit的域，来指示该NextHopChainingCount(表示取值0～7的整数)。
如图17所示，IAB子节点或者终端设备的PHY、MAC、RLC或BAP层可以将收到的第二指示信息发送给RRC层，由RRC层执行更新配置信息(例如更新Keys)的操作；此外，IAB子节点或者终端设备还可以发送响应消息或完成消息或HARQ确认或RLC确认给恢复或CHO的IAB节点(可选的)，该IAB节点还可以向目标IAB-donor CU发送F1AP消息(可选的)。
在一些实施例中，所述目标CU通过Xn接口将所述第二指示信息发送给所述源CU，由所述源CU通过F1AP消息将所述第二指示信息发送给所述IAB节点的DU，并且由所述IAB节点的DU发送给所述IAB子节点或者终端设备。
图18是本申请实施例的IAB的通信方法的另一示意图，如图18所示，目标CU通过Xn接口将第二指示信息发送给源CU，由源CU通过F1AP消息(使用新的路径)将第二指示信息发送给恢复后或切换后的IAB节点，由该IAB节点通过PHY、MAC、RLC或BAP信令将该第二指示信息发送给IAB子节点或者终端设备。
如图18所示，IAB子节点或者终端设备可以将第二指示信息发送给RRC层，由RRC层执行更新配置信息(例如更新Keys)的操作；此外，IAB子节点或者终端设备还可以发送响应消息或完成消息给切换后或恢复后的IAB节点(可选的)，该IAB节点还可以向目标IAB-donor CU发送F1AP消息(可选的)。或者，该IAB节点还可以向源IAB-donor CU发送F1AP消息(可选的)，该源IAB-donor CU向目标IAB-donor CU发送Xn消息(可选的)。
以上以目标CU发送第二指示信息为例进行了说明，以下再对源CU发送第四指示信息进行说明。
在一些实施例中，所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的源CU发送的第四指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中，在目标CU发送无线资源控制重建立(RRC reestablishment)消息、或者、接收到无线资源控制重建立完成(RRC reestablishment complete)消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
例如，对于inter-CU RLF恢复场景，第四指示信息的发送时刻包括：恢复的IAB-MT发送RRC re-establishment request消息的时刻，或者恢复的IAB-MT收到RRC re-establishment消息的时刻，或者恢复的IAB-MT发送RRC re-establishment complete消息的时刻，或者恢复的IAB-node的MT收到RRC连接重建后第一条RRC重配置(RRC reconfiguration)消息的时刻，或者恢复的IAB-node的MT发送RRC重配置完成(RRC reconfiguration complete)消息的时刻，或者恢复的IAB-node的DU向目标CU发送F1AP setup request消息的时刻，或者从目标CU接收到F1 setup response消息的时刻，或者目标CU和恢复的IAB-node之间的SCTP连接被建立的时刻，或者F1-C连接被切换来使 用恢复的IAB-node的新的TNL地址和新的IAB-donor CU的TNL地址的时刻，
或者目标CU与恢复的IAB-DU建立或重建或更新F1接口上下文的时刻，例如gNB DU配置更新过程或者gNB CU配置更新过程的时刻；或者目标CU与恢复的IAB-DU建立或重建或更新对恢复的IAB-node的子IAB-node或UE的F1AP UE context的时刻；或者恢复的IAB-node的DU收到BH配置信息的时刻，该BH配置信息可以包括例如目标IAB父节点和目标IAB-donor DU之间新路径上的BH RLC channels和BAP子层routing条目、或目标IAB-donor DU上对恢复的IAB-node的新路径的DL映射；或者更新F1-U连接(例如GTP隧道信息)的时刻，等等。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程之后，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中，在目标CU接收到无线资源控制重配置完成消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
例如，对于inter-CU CHO场景，第四指示信息的发送时刻包括：IAB-node发起CHO(例如，detach from source或开始应用存储的满足条件的目标小区的条件重配置或开始向目标小区发起RACH)的时刻，或发送RRC reconfiguration complete消息的时刻，或收到RRC reconfiguration complete消息的RLC层确认或HARQ确认的时刻，或者IAB-node的DU向目标CU发送F1AP setup request消息的时刻，或者从目标CU接收到F1 setup response消息的时刻，或者目标CU和IAB-node之间的SCTP连接被建立的时刻，或者F1-C连接被切换来使用IAB-node的新的TNL地址和目标CU的TNL地址的时刻，
或者目标CU与IAB-DU建立或重建或更新F1接口上下文的时刻，例如gNB DU配置更新过程或者gNB CU配置更新过程的时刻；或者目标CU与IAB-node的DU建立或重建或更新对恢复的IAB-node的子IAB-node或UE的F1AP UE context的时刻；或者IAB-node的DU收到BH配置信息的时刻，该BH配置信息可以包括例如目标IAB父节点和目标IAB-donor DU之间新路径上的BH RLC channels和BAP子层routing条目、或目标IAB-donor DU上对IAB-node的新路径的DL映射；或者更新F1-U连接(例如GTP隧道信息)的时刻，等等。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程之 后，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
在一些实施例中，所述第四指示信息指示所述目标CU中无线资源控制(RRC)层和/或分组数据会聚协议(PDCP)层的配置信息。例如，所述第四指示信息包括如下信息的至少之一或任意组合：下一跳计数(nextHopChainingCount)、密钥集改变指示(keySet ChangeIndicator)、非接入层(NAS)安全信息(nas-Container)、加密算法(ciphering Algorithm)、完整性保护算法(integrityProtAlgorithm)；但本申请不限于此。
在一些实施例中，第四指示信息还可以指示IAB节点的donor CU是否发生了改变，或者指示IAB节点进行了相同CU的迁移(intra-CU migration)还是跨CU的迁移(inter-CU migration)。
在一些实施例中，第四指示信息还可以包含CU改变指示和/或目标CU的标识等。
在一些实施例中，所述源CU接收所述目标CU通过无线资源控制(RRC)消息发送的所述第四指示信息，由所述源CU使用配置信息处理所述第四指示信息后，通过Xn接口发送给所述IAB节点的DU，并且由所述IAB节点的DU发送给所述IAB子节点或者终端设备。
图19是本申请实施例的IAB的通信方法的另一示意图。如图19所示，目标CU通过Xn接口将承载第四指示信息的RRC消息发送给源CU，由源CU对该RRC消息采用源CU的配置信息(旧的安全Key加密和/或完整性保护)进行处理后，通过Xn接口将处理后的第四指示信息发送给目标CU，目标CU通过DL RRC MESSAGE TRANSFER(使用新的路径)将处理后的第四指示信息发送给恢复后或切换后的IAB节点，由该IAB节点通过RRC消息将该处理后的第四指示信息发送给IAB子节点或者终端设备。
如图19所示，IAB子节点或者终端设备可以使用源CU的配置信息(例如安全算法和/或keys)获得目标CU的配置信息；此外，IAB子节点或者终端设备还可以发送响应消息或完成消息给切换后或恢复后的IAB节点(可选的)，该IAB节点还可以通过UL RRC MESSAGE TRANSFER向目标IAB-donor CU发送信息(可选的)。
由此，通过直接发送安全相关的配置信息，节省了RRC重建过程中的小区选择和随机接入过程的时延，有利于减少IAB子节点或终端设备由于IAB-node恢复或迁移到新的CU产生的业务中断时间。
在本申请实施例中，IAB子节点或终端设备可以向CU指示其能力，例如在UE能力信息或RRC setup complete消息或RRC resume complete或RRC reestablishment complete消息中指示，以表明是否支持上述实施例中的通信方法。
此外，RRC消息例如可以是RRC re-establishment消息或RRC reconfiguration消息；F1AP消息可以是UE context setup request或UE context modification request；Xn消息可以是RRC transfer或Retrieve UE context response等。
值得注意的是，以上附图14至19可以与附图8或9结合起来，但本申请不限于此，还可以与其他inter-CU的恢复或切换过程结合起来，本申请实施例不限制这些过程中的具体步骤或执行顺序。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，IAB子节点或者终端设备接收网络设备发送的指示信息，所述指示信息指示对应的目标CU的配置信息，根据所述目标CU的配置信息进行通信。由此，在支持inter-CU恢复或切换的情况下，即使IAB子节点或终端设备没有改变服务的IAB节点，IAB子节点或终端设备也会更新CU的配置信息，从而能够与目标CU正确地通信。
第三方面的实施例
本申请实施例提供一种IAB的通信方法，从IAB节点进行说明，与第一、二方面的实施例相同的内容不再赘述。此外，第三方面的实施例可以与第一、二方面的实施例结合起来实施，也可以单独地实施。
图20是本申请实施例的IAB的通信方法的一场景示意图。如图20所示，IAB-node1在它与父节点(IAB-donor)之间的回传链路(backhaul)发生RLF或RLF恢复失败等情况下，可以向IAB-node 1的子节点(IAB-node 3和IAB-node 4)发送RLF指示(RLF indication或BH RLF indication)，以便IAB子节点可以知晓该情况并搜索其他父节点，找到新的路由与IAB-donor进行通信。
在3GPP Rel-16会议中，讨论了4种类型的BH RLF indication；同意并规定了Type 4，即子节点收到的Type 4 BH RLF indication将被子节点认为检测到RLF。在BAP规范(TS 38.340v16.2.0)中，显示了对BH RLF指示的BAP控制PDU的格式。
表1示出了BH RLF指示的BAP控制PDU的格式。
表1
D/C PDU类型(PDU type) R R R
如表1所示，BAP控制PDU包括：
D/C域：长度1bit，指示对应的BAP PDU是BAP Data PDU还是BAP Control PDU；
表2
比特(Bit) 描述(Description)
0 BAP控制PDU(BAP Control PDU)
1 BAP数据PDU(BAP Data PDU)
PDU type：长度4bits，指示对应的BAP Control PDU中包括的控制信息的类型。
表3
Figure PCTCN2021071577-appb-000001
如表1所示，BAP控制PDU还包括R比特，分别为1bit；3个R比特共3bits。
在Rel-17中，为了更早地提供一些信息给子节点，加速子节点恢复的过程，从而减少子节点的业务中断，3GPP正在讨论是否需要type 1～type 3的RLF indication，以及子节点收到这些类型的RLF indication的行为。但是，当前BAP层的RLF指示只是针对type 4，无法实现type 1～type 3的RLF indication。
在一些实施例中，IAB节点检测到所述IAB节点与父节点之间的回传链路发生无线链路失败(RLF)或者正在尝试RLF恢复或者RLF恢复成功或者RLF恢复失败；以及所述IAB节点向所服务的IAB子节点或者终端设备发送RLF指示信息；所述RLF指示信息指示至少两种回传链路无线链路失败(BH RLF)的类型中的一种。
例如，所述回传链路无线链路失败的类型包括下面的至少一种：
回传链路无线链路失败的类型1，其表示IAB节点检测到所述IAB节点与父节点之间的回传链路发生无线链路失败(RLF)，
回传链路无线链路失败的类型2，其表示IAB节点检测到所述IAB节点与父节点之 间的回传链路发生无线链路失败(RLF)且所述IAB节点正在尝试RLF恢复，
回传链路无线链路失败的类型3，其表示IAB节点检测到所述IAB节点与父节点之间的回传链路发生无线链路失败(RLF)且所述IAB节点RLF恢复成功，
回传链路无线链路失败的类型4，其表示IAB节点检测到所述IAB节点与父节点之间的回传链路发生无线链路失败(RLF)且所述IAB节点RLF恢复失败。
在一些实施例中，使用BAP控制PDU向所述IAB子节点或者终端设备发送所述RLF指示信息；所述BAP控制PDU的PDU类型域指示所述回传链路无线链路失败的类型。
在一些实施例中，BAP控制PDU的PDU类型域中的多于一个比特的一个取值指示回传链路无线链路失败的类型4；另一个取值指示回传链路无线链路失败的类型2或者回传链路无线链路失败的类型3。例如，如表4所示：
表4
Figure PCTCN2021071577-appb-000002
在一些实施例中，BAP控制PDU的PDU类型域中的多个比特的一个取值指示回传链路无线链路失败的类型4；另一个取值指示回传链路无线链路失败的类型1、或类型2、或类型1和类型2中的一种类型；另一个取值指示回传链路无线链路失败的类型3。例如，如表5所示(其中PDU type的取值0100指示BH RLF indication type 2)：
表5
Figure PCTCN2021071577-appb-000003
Figure PCTCN2021071577-appb-000004
在一些实施例中，使用所述RLF指示信息的BAP控制PDU的R域指示所述至少两种回传链路无线链路失败的类型。
例如，BAP控制PDU的R域中的1个比特的一个取值指示回传链路无线链路失败的类型4；另一个取值指示回传链路无线链路失败的类型2或回传链路无线链路失败的类型3。例如，0表示type 4，1表示type 2。
表6
Figure PCTCN2021071577-appb-000005
再例如，BAP控制PDU的R域中的多个比特的一个取值指示回传链路无线链路失败的类型4；另一个取值指示回传链路无线链路失败的类型2；另一个取值指示回传链路无线链路失败的类型3。
表7
D/C PDU类型(PDU type) RLF类型 R
在一些实施例中，type 3 RLF indication可以指示IAB节点是否恢复到另一个IAB-donor CU，即无线链路失败恢复的IAB-donor CU与该IAB节点的源IAB-donor CU是否相同或者IAB-donor CU是否改变，例如采用长度为1bit的域。
在一些实施例中，在IAB节点成功恢复到另一个IAB-donor CU的情况下，type 3 RLF indication可以指示恢复的CU的标识或索引等。
在一些实施例中，IAB子节点或者终端设备收到上述type 2 RLF indication或type 3 RLF indication或type 4 RLF indication时，如果该IAB子节点或者终端设备被配置了CHO，则可以发起CHO过程，否则，可以发起无线链路失败恢复过程。
在一些实施例中，IAB子节点在收到RLF indication时，可以生成一个RLF indication，IAB子节点将生成的RLF indication发送给该IAB子节点的子节点或者终端设备。
例如，IAB子节点在收到type 1或type 2 RLF indication时，可以生成type 1和type 2 RLF indication中的一种，或者IAB子节点在收到type 3 RLF indication时，可以生成type 3 RLF indication，或者IAB子节点在收到type 4 RLF indication时，可以生成type 4 RLF indication。
在一些实施例中，IAB子节点在收到type 1或type 2或type 3或type 4的RLF indication时，可以转发该RLF indication给该IAB子节点的子节点或者终端设备。
在一些实施例中，IAB子节点在收到type 1或type 2或type 3或type 4的RLF indication时，可以停止向IAB节点发送调度请求(Scheduling Request，SR)和/或缓存状态报告(Buffer Status Report，BSR)。
在一些实施例中，IAB子节点在收到type 1或type 2或type 3或type 4的RLF indication时，IAB子节点下的小区的系统信息块类型1(System Information Block Type 1，SIB1)中IAB-support域不出现。
在一些实施例中，IAB子节点在收到RLF indication时的行为是可配置的，例如IAB-donor CU可以配置IAB子节点采用上述实施例中的行为。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，RLF指示信息指示至少两种回传链路无线链路失败(BH link RLF)的类型中的一种，能够更早地提供一些信息给子节点，加速子节点恢复的过程，从而减少子节点的业务中断。
第四方面的实施例
本申请实施例提供一种IAB的通信方法，从IAB节点进行说明，与第一至三方面的实施例相同的内容不再赘述。此外，第四方面的实施例可以与第一至三方面的实施例结合起来实施，也可以单独地实施。
如上所述，RLF indication采用BAP control PDU来指示，由于IAB子节点有BAP层但是终端设备没有BAP层，因此当前的RLF indication不适用于通知终端设备进行相关操作。
在一些实施例中，IAB节点检测到所述IAB节点与父节点之间的回传链路上发生无线链路失败(RLF)或者正在尝试RLF恢复或者RLF恢复成功或者RLF恢复失败；以及所述IAB节点使用物理层信令、MAC层信令、RLC层信令或者系统信息向所服务的终端设备发送所述RLF指示信息。
在一些实施例中，所述IAB节点使用BAP控制PDU向所服务的IAB子节点发送RLF指示信息，或者IAB节点使用物理层信令、MAC层信令、RLC层信令或者系统信息向所服务的IAB子节点发送所述RLF指示信息。
在一些实施例中，所述物理层信令包括下行控制信息(DCI)格式，所述下行控制信息(DCI)指示回传链路无线链路失败的类型。例如，可以为PHY设计新的DCI format，或者在DCI中显式地指示BH RLF indication和/或BH RLF indication type。
在一些实施例中，所述MAC层信令包括MAC CE；所述MAC CE中的一个或多于一个比特或者一个域指示回传链路无线链路失败的类型。例如，可以采用新的MAC CE，具有新的LCID。
例如，MAC CE由对应的MAC sub-header标识，该MAC sub-header中包括该MAC CE对应的LCID。再例如，MAC CE可以包含位图(bitmap)，其中每个bit表示一种类型；对于1个bit，例如1表示是该类型的BH RLF indication，0表示不是该类型的BH RLF indication。再例如，MAC CE中可以有一个域显式地指示是哪种类型。
在一些实施例中，所述RLC层信令包括RLC控制PDU。
在一些实施例中，所述系统信息包括主信息块(MIB，Main Information Block)和/或系统信息块(SIB，System Information Block)；所述MIB和/或SIB中一个域指示回传链路无线链路失败的类型。
例如，IAB-DU自主地发送MIB和/或SIB1，例如MIB中小区禁止域(cellBarred)被设置为禁止(barred)或者SIB1中的IAB-support域不出现，或者MIB和/或SIB1使用新的域指示BH RLF indication和/或BH RLF indication type。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，IAB节点使用物理层信令、MAC层信令、RLC层信令或者系统信息向所属的终端设备发送所述RLF指示信息。IAB节点可以向终端设备指示其服务IAB节点发生BH RLF，有助于减少RLF恢复产生的业务中断时延。
第五方面的实施例
本申请实施例提供一种IAB的通信装置。该装置例如可以是IAB子节点或终端设备，也可以是配置于IAB子节点或终端设备的某个或某些部件或者组件，与第一、二方面的实施例相同的内容不再赘述。
图21是本申请实施例的IAB的通信装置的一示意图，如图21所示，IAB的通信装置2100包括：接收部2101和处理部2102。
在一些实施例中，接收部2101接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备认为检测到无线链路失败(RLF)或指示所述IAB子节点或者终端设备发起连接重建；以及处理部2102发起无线链路失败恢复过程或者连接重建过程。
在一些实施例中，所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的IAB节点发送的第一指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中，在所述IAB节点接收到目标集中式单元(Target CU)发送的无线资源控制重建立(RRC reestablishment)消息、或者与目标CU建立F1接口、或者接收到回传(BH)配置信息的情况下，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程之后，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
在一些实施例中，所述处理部2102还用于：在所述IAB子节点或终端设备为单连接的情况下，或者所述IAB子节点或终端设备被配置双连接且所述IAB节点为所述IAB子节点或终端设备的主小区组(MCG)的情况下，确定对MCG检测到无线链路失败(RLF)。
在一些实施例中，所述处理部2102用于：在定时器(T316)被配置且SCG发送没有被挂起且主服务小区改变(PSCell change)没有在进行的情况下，发起MCG失败信息过程来报告MCG无线链路失败，否则发起所述连接重建过程。
在一些实施例中，所述处理部2102还用于：在所述IAB子节点或终端设备被配置双连接且所述IAB节点为所述IAB子节点或终端设备的辅小区组(SCG)的情况下， 确定对SCG检测到无线链路失败(RLF)。
在一些实施例中，所述处理部2102用于：在MCG发送没有被挂起的情况下，发起SCG失败信息过程来报告SCG无线链路失败，否则发起所述连接重建过程。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中，在所述IAB节点发起条件切换(CHO)、或者发送无线资源控制重配置完成(RRC reconfiguration complete)消息、或者与目标CU建立F1接口、或者接收到BH配置信息的情况下，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程之后，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
在一些实施例中，所述第一指示信息包括如下至少之一或任意组合：回传适配协议(BAP)协议数据单元(PDU)、无线链路控制(RLC)PDU、介质访问控制(MAC)控制信元(CE)、介质访问控制(MAC)子头、物理层信令。
在一些实施例中，所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的源集中式单元(Source CU)通过恢复后或迁移后的路径发送的第三指示信息。
在一些实施例中，所述源集中式单元(CU)通过Xn接口将所述第三指示信息发送给目标CU或者所述IAB节点的分布式单元(DU)，并且由所述目标CU或所述DU将所述第三指示信息发送给所述IAB子节点或者终端设备。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中，在所述源CU接收到目标CU发送的取回上下文请求消息的情况下，或者向所述目标CU发送取回上下文响应消息的情况下，或者接收到目标CU发送的上下文释放消息的情况下，所述源CU发送所述第三指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程之后，所述源CU发送所述第三指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中，所述源CU在接收到目标CU发送的上下文释放消息的情况下，发送所述第三指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程之后，所述源CU发送所述第三指示信息。
在一些实施例中，所述第三指示信息包括如下至少之一或任意组合：分组数据会聚协议(PDCP)协议数据单元(PDU)、无线资源控制(RRC)消息、F1AP消息。
在一些实施例中，接收部2101接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备所对应的目标CU的配置信息；以及处理部2102根据所述目标CU的配置信息进行通信。
在一些实施例中，所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的所述目标CU发送的第二指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中，在所述目标CU发送无线资源控制重建立(RRC reestablishment)消息、或者接收到无线资源控制重建立完成(RRC reestablishment complete)消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程之后，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中，在所述目标CU接收到无线资源控制重配置完成消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程之后，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
在一些实施例中，所述第二指示信息指示所述目标CU中无线资源控制(RRC)层和/或分组数据会聚协议(PDCP)层的配置信息；
在一些实施例中，所述第二指示信息包括如下信息的至少之一或任意组合：下一跳计数(nextHopChainingCount)、密钥集改变指示(keySetChangeIndicator)、非接入层(NAS)安全信息(nas-Container)、加密算法(ciphering Algorithm)、完整性保护算法(integrityProtAlgorithm)。
在一些实施例中，所述目标CU通过无线资源控制(RRC)消息，将未加密或者被默认加密的第二指示信息发送给所述IAB子节点或者终端设备。
在一些实施例中，所述处理部2102还用于：接收所述IAB节点的通知消息；以及根据所述通知消息挂起对信令无线承载(SRB)的完整性保护和加密操作，以获得所述第二指示信息。
在一些实施例中，所述处理部2102还用于：对所述无线资源控制(RRC)消息进行解密和解码操作；以及在不能成功解码的情况下，对所述无线资源控制(RRC)消息不进行解密或进行默认解密操作，并且进行解码操作以获得所述第二指示信息。
在一些实施例中，所述目标CU通过无线资源控制(RRC)消息，使用所述源CU的配置信息将所述第二指示信息发送给所述IAB子节点或者终端设备。
在一些实施例中，所述目标CU通过Xn接口将所述第二指示信息发送给所述源CU，并且由所述源CU使用配置信息处理所述第二指示信息后，通过恢复后或迁移后的路径发送给所述IAB子节点或者终端设备。
在一些实施例中，所述目标CU通过F1AP消息将所述第二指示信息发送给所述IAB子节点或者终端设备。
在一些实施例中，所述目标CU通过Xn接口将所述第二指示信息发送给所述源CU，由所述源CU通过F1AP消息将所述第二指示信息发送给所述IAB节点的DU，并且由所述IAB节点的DU发送给所述IAB子节点或者终端设备。
在一些实施例中，所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的源CU发送的第四指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中，在目标CU发送无线资源控制重建立(RRC reestablishment)消息、或者、接收到无线资源控制重建立完成(RRC reestablishment complete)消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程之后，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中，在目标CU接收到无线资源控制重配置完成消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程之后，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
在一些实施例中，所述第四指示信息指示所述目标CU中无线资源控制(RRC)层和/或分组数据会聚协议(PDCP)层的配置信息；
在一些实施例中，所述第四指示信息包括如下信息的至少之一或任意组合：下一跳计数(nextHopChainingCount)、密钥集改变指示(keySet ChangeIndicator)、非接入层(NAS)安全信息(nas-Container)、加密算法(ciphering Algorithm)、完整性保护算法(integrityProtAlgorithm)。
在一些实施例中，所述源CU接收所述目标CU通过无线资源控制(RRC)消息发送的所述第四指示信息，由所述源CU使用配置信息处理所述第四指示信息后，通过Xn接口发送给所述IAB节点的DU，并且由所述IAB节点的DU发送给所述IAB子节点或者终端设备。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。IAB的通信装置2100还可以包括其他部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图21中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，IAB子节点或者终端设备接收网络设备发送的指示信息，根据该指示信息发起无线链路失败恢复过程或者连接重建过程；或者，IAB子节点或者终端设备接收网络设备发送的指示信息，所述指示信息指示对应的目标CU的配置信息，根据所述目标CU的配置信息进行通信。由此，在支持inter-CU恢复或切换的情况下，即使IAB子节点或终端设备没有改变服务的IAB节点，IAB子节点或终端设备也会更新CU的配置信息，从而能够与目标CU正确地通信。
第六方面的实施例
本申请实施例提供一种IAB的通信装置。该装置例如可以是IAB节点，也可以是配置于IAB节点的某个或某些部件或者组件。第六方面的实施例中的IAB通信装置与第五方面的IAB的通信装置相对应，与第一、二方面的实施例相同的内容不再赘述。
图22是本申请实施例的IAB的通信装置的一示意图，如图22所示，IAB的通信装 置2200包括：生成部2201和发送部2202。
在一些实施例中，生成部2201生成指示信息；所述指示信息被用于在IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备认为检测到无线链路失败(RLF)或指示所述IAB子节点或者终端设备发起连接重建；以及发送部2202向所述IAB子节点或终端设备发送所述指示信息。
在一些实施例中，所述IAB的通信装置2200为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的IAB节点。所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的IAB节点发送的第一指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中，在所述IAB节点接收到目标集中式单元(Target CU)发送的无线资源控制重建立(RRC reestablishment)消息、或者与目标CU建立F1接口、或者接收到回传(BH)配置信息的情况下，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程之后，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中，在所述IAB节点发起条件切换(CHO)、或者发送无线资源控制重配置完成(RRC reconfiguration complete)消息、或者与目标CU建立F1接口、或者接收到BH配置信息的情况下，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程之后，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
在一些实施例中，所述第一指示信息包括如下至少之一或任意组合：回传适配协议(BAP)协议数据单元(PDU)、无线链路控制(RLC)PDU、介质访问控制(MAC)控制信元(CE)、介质访问控制(MAC)子头、物理层信令。
在一些实施例中，所述IAB的通信装置2200为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的源CU。所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的源集中式单元(Source CU)通过恢复后或迁移后的路径发送的第三指示信息。
在一些实施例中，所述源集中式单元(CU)通过Xn接口将所述第三指示信息发送给目标CU或者所述IAB节点的分布式单元(DU)，并且由所述目标CU或所述DU将所述第三指示信息发送给所述IAB子节点或者终端设备。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中，在所述源CU接收到目标CU发送的取回上下文请求消息的情况下，或者向所述目标CU发送取回上下文响应消息的情况下，或者接收到目标CU发送的上下文释放消息的情况下，所述源CU发送所述第三指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程之后，所述源CU发送所述第三指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中，所述源CU在接收到目标CU发送的上下文释放消息的情况下，发送所述第三指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程之后，所述源CU发送所述第三指示信息。
在一些实施例中，所述第三指示信息包括如下至少之一或任意组合：分组数据会聚协议(PDCP)协议数据单元(PDU)、无线资源控制(RRC)消息、F1AP消息。
在一些实施例中，生成部2201生成指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备所对应的目标CU的配置信息；以及发送部2202向所述IAB子节点或终端设备发送所述目标CU的配置信息。
在一些实施例中，所述IAB通信装置2200为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的目标CU。所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的所述目标CU发送的第二指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中，在所述目标CU发送无线资源控制重建立(RRC reestablishment)消息、或者接收到无线资源控制重建立完成(RRC reestablishment complete)消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程之后，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中，在所述目标CU接收到无线资源控制重配置完成消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程之后，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
在一些实施例中，所述第二指示信息指示所述目标CU中无线资源控制(RRC)层和/或分组数据会聚协议(PDCP)层的配置信息；例如，所述第二指示信息包括如下信息的至少之一或任意组合：下一跳计数(nextHopChainingCount)、密钥集改变指示(keySetChangeIndicator)、非接入层(NAS)安全信息(nas-Container)、加密算法(ciphering Algorithm)、完整性保护算法(integrityProtAlgorithm)。
在一些实施例中，所述目标CU通过无线资源控制(RRC)消息，将未加密或者被默认加密的第二指示信息发送给所述IAB子节点或者终端设备。
在一些实施例中，所述目标CU通过无线资源控制(RRC)消息，使用所述源CU的配置信息将所述第二指示信息发送给所述IAB子节点或者终端设备。
在一些实施例中，所述目标CU通过Xn接口将所述第二指示信息发送给所述源CU，并且由所述源CU使用配置信息处理所述第二指示信息后，通过恢复后或迁移后的路径发送给所述IAB子节点或者终端设备。
在一些实施例中，所述目标CU通过F1AP消息将所述第二指示信息发送给所述IAB子节点或者终端设备。
在一些实施例中，所述目标CU通过Xn接口将所述第二指示信息发送给所述源CU，由所述源CU通过F1AP消息将所述第二指示信息发送给所述IAB节点的DU，并且由所述IAB节点的DU发送给所述IAB子节点或者终端设备。
在一些实施例中，所述IAB的通信装置2200为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的源CU。所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的源CU发送的第四指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中，在目标CU发送无线资源控制重建立(RRC reestablishment)消息、或者、接收到无线资源控制重建立完成(RRC reestablishment complete)消息、或者与所述IAB节 点建立F1接口、或者发送BH配置信息的情况下，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程之后，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中，在目标CU接收到无线资源控制重配置完成消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
在一些实施例中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程之后，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
在一些实施例中，所述第四指示信息指示所述目标CU中无线资源控制(RRC)层和/或分组数据会聚协议(PDCP)层的配置信息；例如，所述第四指示信息包括如下信息的至少之一或任意组合：下一跳计数(nextHopChainingCount)、密钥集改变指示(keySet ChangeIndicator)、非接入层(NAS)安全信息(nas-Container)、加密算法(ciphering Algorithm)、完整性保护算法(integrityProtAlgorithm)。
在一些实施例中，所述源CU接收所述目标CU通过无线资源控制(RRC)消息发送的所述第四指示信息，由所述源CU使用配置信息处理所述第四指示信息后，通过Xn接口发送给所述IAB节点的DU，并且由所述IAB节点的DU发送给所述IAB子节点或者终端设备。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。IAB的通信装置2200还可以包括其他部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图22中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，IAB的节点向IAB子节点或者终端设备发送指示信息，IAB子 节点或者终端设备根据该指示信息发起无线链路失败恢复过程或者连接重建过程，或者，IAB子节点或者终端设备根据目标CU的配置信息进行通信。由此，在支持inter-CU恢复或切换的情况下，即使IAB子节点或终端设备没有改变服务的IAB节点，IAB子节点或终端设备也会更新CU的配置信息，从而能够与目标CU正确地通信。
第七方面的实施例
本申请实施例还提供一种通信系统，可以参考图1，与第一方面至第六方面的实施例相同的内容不再赘述。
在一些实施例中，该通信系统可以包括：第五方面的实施例所述的IAB的通信装置2100和第六方面的实施例所述的IAB的通信装置2200，其执行第一、二方面的实施例所述的IAB的通信方法；
在一些实施例中，该通信系统可以包括：IAB节点，其执行第三、四方面的实施例所述的IAB的通信方法。
本申请实施例还提供一种网络设备，例如可以是基站或IAB节点，但本申请不限于此，还可以是其他的网络设备。
图23是本申请实施例的网络设备的构成示意图。如图23所示，网络设备2300可以包括：处理器2310(例如中央处理器CPU)和存储器2320；存储器2320耦合到处理器2310。其中该存储器2320可存储各种数据；此外还存储信息处理的程序2330，并且在处理器2310的控制下执行该程序2330。
例如，处理器2310可以被配置为执行程序而实现如第一方面的实施例所述的IAB的通信方法。例如处理器2310可以被配置为进行如下的控制：生成指示信息；所述指示信息被用于在IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备认为检测到无线链路失败(RLF)或指示所述IAB子节点或者终端设备发起连接重建；以及向所述IAB子节点或终端设备发送所述指示信息。
例如，处理器2310可以被配置为执行程序而实现如第二方面的实施例所述的IAB的通信方法。例如处理器2310可以被配置为进行如下的控制：生成指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备所对应的目标CU的配置信息；以及向所述IAB子节点或终端设备发送所述目标CU的配置信息。
例如，处理器2310可以被配置为执行程序而实现如第三方面的实施例所述的IAB的通信方法。例如处理器2310可以被配置为进行如下的控制：检测到所述IAB节点与父节点之间的回传链路发生无线链路失败(RLF)或者正在尝试RLF恢复或者RLF恢复成功或者RLF恢复失败；以及向所属的IAB子节点或者终端设备发送RLF指示信息；所述RLF指示信息指示至少两种回传链路无线链路失败(BH link RLF)的类型中的一种。
再例如，处理器2310可以被配置为执行程序而实现如第四方面的实施例所述的IAB的通信方法。例如处理器2310可以被配置为进行如下的控制：检测到所述IAB节点与父节点之间的回传链路上发生无线链路失败(RLF)或者正在尝试RLF恢复或者RLF恢复成功或者RLF恢复失败；使用BAP控制PDU向所属的IAB子节点发送RLF指示信息；以及使用物理层信令、MAC层信令、RLC层信令或者系统信息向所属的终端设备发送所述RLF指示信息。
此外，如图23所示，网络设备2300还可以包括：收发机2340和天线2350等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备2300也并不是必须要包括图23中所示的所有部件；此外，网络设备2300还可以包括图23中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种IAB子节点或终端设备，但本申请不限于此，还可以是其他的设备。以下以终端设备为例进行说明；对于IAB子节点，可以也可以具有图24的结构，或者也可以省略部分部件(例如显示器2450)等。
图24是本申请实施例的终端设备的示意图。如图24所示，该终端设备2400可以包括处理器2410和存储器2420；存储器2420存储有数据和程序，并耦合到处理器2410。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或代替该结构，以实现电信功能或其他功能。
例如，处理器2410可以被配置为执行程序而实现如第一方面的实施例所述的IAB的通信方法。例如处理器2410可以被配置为进行如下的控制：接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备认为检测到无线链路失败(RLF)或指示所述IAB子节点或者终端设备发起连接重建；以及发起无线链路失败恢复过程或者连接重建过程。
再例如，处理器2410可以被配置为执行程序而实现如第二方面的实施例所述的IAB 的通信方法。例如处理器2410可以被配置为进行如下的控制：接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备所对应的目标CU的配置信息；以及根据所述目的CU的配置信息进行通信。
如图24所示，该终端设备2400还可以包括：通信模块2430、输入单元2440、显示器2450、电源2460。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备2400也并不是必须要包括图24中所示的所有部件，上述部件并不是必需的；此外，终端设备2400还可以包括图24中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机程序，其中当在IAB子节点或终端设备中执行所述程序时，所述程序使得所述IAB子节点或终端设备执行第一、二方面的实施例所述的IAB的通信方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得IAB子节点或终端设备执行第一、二方面的实施例所述的IAB的通信方法。
本申请实施例还提供一种计算机程序，其中当在IAB节点中执行所述程序时，所述程序使得所述IAB节点执行第一至四方面的实施例所述的IAB的通信方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得IAB节点执行第一至四方面的实施例所述的IAB的通信方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介 质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于包括以上实施例的实施方式，还公开下述的附记：
附记1.一种集成的接入和回传(IAB)的通信方法，包括：
IAB子节点或者终端设备接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备认为检测到无线链路失败(RLF)或指示所述IAB子节点或者终端设备发起连接重建；以及
所述IAB子节点或终端设备发起无线链路失败恢复过程或者连接重建过程。
附记2.根据附记1所述的方法，其中，所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的IAB节点发送的第一指示信息。
附记3.根据附记2所述的方法，其中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中或之后，在所述IAB节点接收到目标集中式单元(Target CU)发送的无线资源控制重建立(RRC reestablishment)消息、或者与目标CU建立F1接口、或者接收到回传(BH)配置信息的情况下，所述IAB节点向所述IAB子节点或者终端 设备发送所述第一指示信息。
附记4.根据附记2所述的方法，其中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中或之后，在所述IAB节点发起条件切换(CHO)、或者发送无线资源控制重配置完成(RRC reconfiguration complete)消息、或者与目标CU建立F1接口、或者接收到BH配置信息的情况下，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
附记5.根据附记3或4所述的方法，其中，所述方法还包括：
在所述IAB子节点或终端设备为单连接的情况下，或者所述IAB子节点或终端设备被配置双连接且所述IAB节点为所述IAB子节点或终端设备的主小区组(MCG)的情况下，所述IAB子节点或终端设备认为(确定)对MCG检测到无线链路失败(RLF)。
附记6.根据附记5所述的方法，其中，所述IAB子节点或终端设备发起无线链路失败恢复过程，包括：
在定时器(T316)被配置且SCG发送没有被挂起且主服务小区改变(PSCell change)没有在进行的情况下，所述IAB子节点或终端设备发起MCG失败信息过程来报告MCG无线链路失败，否则发起所述连接重建过程。
附记7.根据附记3或4所述的方法，其中，所述方法还包括：
在所述IAB子节点或终端设备被配置双连接且所述IAB节点为所述IAB子节点或终端设备的辅小区组(SCG)的情况下，所述IAB子节点或终端设备确定对SCG检测到无线链路失败(RLF)。
附记8.根据附记7所述的方法，其中，所述IAB子节点或终端设备发起无线链路失败恢复过程，包括：
在MCG发送没有被挂起的情况下，所述IAB子节点或终端设备发起SCG失败信息过程来报告SCG无线链路失败，否则发起所述连接重建过程。
附记9.根据附记2至8任一项所述的方法，其中，所述第一指示信息包括如下至少之一或任意组合：回传适配协议(BAP)协议数据单元(PDU)、无线链路控制(RLC)PDU、介质访问控制(MAC)控制信元(CE)、介质访问控制(MAC)子头、物理层信令。
附记10.根据附记1所述的方法，其中，所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的源集中式单元(Source CU)通过恢复后或迁移后的路径发送的第三指示信息。
附记11.根据附记10所述的方法，其中，所述源集中式单元(CU)通过Xn接口将所述第三指示信息发送给目标CU或者所述IAB节点的分布式单元(DU)，并且由所述目标CU或所述DU将所述第三指示信息发送给所述IAB子节点或者终端设备。
附记12.根据附记10或11所述的方法，其中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中或之后，在所述源CU接收到目标CU发送的取回上下文请求消息的情况下，或者向所述目标CU发送取回上下文响应消息的情况下，或者接收到目标CU发送的上下文释放消息的情况下，所述源CU发送所述第三指示信息。
附记13.根据附记10或11所述的方法，其中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中或之后，所述源CU在接收到目标CU发送的上下文释放消息的情况下，发送所述第三指示信息。
附记14.根据附记12或13所述的方法，其中，所述方法还包括：
在所述IAB子节点或终端设备为单连接的情况下，或者所述IAB子节点或终端设备被配置双连接且所述IAB节点为所述IAB子节点或终端设备的主小区组(MCG)的情况下，所述IAB子节点或终端设备确定对MCG检测到无线链路失败(RLF)。
附记15.根据附记14所述的方法，其中，所述IAB子节点或终端设备发起无线链路失败恢复过程，包括：
在定时器(T316)被配置且SCG发送没有被挂起且主服务小区改变(PSCell change)没有在进行的情况下，所述IAB子节点或终端设备发起MCG失败信息过程来报告MCG无线链路失败，否则发起所述连接重建过程。
附记16.根据附记12或13所述的方法，其中，所述方法还包括：
在所述IAB子节点或终端设备被配置双连接且所述IAB节点为所述IAB子节点或终端设备的辅小区组(SCG)的情况下，所述IAB子节点或终端设备确定对SCG检测到无线链路失败(RLF)。
附记17.根据附记16所述的方法，其中，所述IAB子节点或终端设备发起无线链路失败恢复过程，包括：
在MCG发送没有被挂起的情况下，所述IAB子节点或终端设备发起SCG失败信息过程来报告SCG无线链路失败，否则发起所述连接重建过程。
附记18.根据附记10至17任一项所述的方法，其中，所述第三指示信息包括如下至少之一或任意组合：分组数据会聚协议(PDCP)协议数据单元(PDU)、无线资源控制(RRC)消息、F1AP消息。
附记19.一种集成的接入和回传(IAB)的通信方法，包括：
IAB子节点或者终端设备接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备所对应的目标CU的配置信息；以及
所述IAB子节点或终端设备根据所述目标CU的配置信息进行通信。
附记20.根据附记19所述的方法，其中，所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的所述目标CU发送的第二指示信息。
附记21.根据附记20所述的方法，其中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中或之后，在所述目标CU发送无线资源控制重建立(RRC reestablishment)消息、或者接收到无线资源控制重建立完成(RRC reestablishment complete)消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
附记22.根据附记20所述的方法，其中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中或之后，在所述目标CU接收到无线资源控制重配置完成消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
附记23.根据附记20至22任一项所述的方法，其中，所述第二指示信息指示所述目标CU中无线资源控制(RRC)层和/或分组数据会聚协议(PDCP)层的配置信息。
附记24.根据附记20至23任一项所述的方法，其中，所述第二指示信息包括如下信息的至少之一或任意组合：下一跳计数(nextHopChainingCount)、密钥集改变指示(keySetChangeIndicator)、非接入层(NAS)安全信息(nas-Container)、加密算法(ciphering Algorithm)、完整性保护算法(integrityProtAlgorithm)。
附记25.根据附记20至24任一项所述的方法，其中，所述目标CU通过无线资源控制(RRC)消息，将未加密或者被默认加密的第二指示信息发送给所述IAB子节点或者终端设备。
附记26.根据附记25所述的方法，其中，所述方法还包括：
所述IAB子节点或者终端设备接收所述IAB节点的通知消息；以及
所述IAB子节点或者终端设备根据所述通知消息挂起对信令无线承载(SRB)的完整性保护和加密操作，以获得所述第二指示信息。
附记27.根据附记25所述的方法，其中，所述方法还包括：
所述IAB子节点或者终端设备对所述无线资源控制(RRC)消息进行解密和解码操作；以及
在不能成功解码的情况下，对所述无线资源控制(RRC)消息不进行解密或进行默认解密操作，并且进行解码操作以获得所述第二指示信息。
附记28.根据附记20至24任一项所述的方法，其中，所述目标CU通过无线资源控制(RRC)消息，使用所述源CU的配置信息将所述第二指示信息发送给所述IAB子节点或者终端设备。
附记29.根据附记20至24任一项所述的方法，其中，所述目标CU通过Xn接口将所述第二指示信息发送给所述源CU，并且由所述源CU使用配置信息处理所述第二指示信息后，通过恢复后或迁移后的路径发送给所述IAB子节点或者终端设备。
附记30.根据附记20至24任一项所述的方法，其中，所述目标CU通过F1AP消息将所述第二指示信息发送给所述IAB子节点或者终端设备。
附记31.根据附记20至24任一项所述的方法，其中，所述目标CU通过Xn接口将所述第二指示信息发送给所述源CU，由所述源CU通过F1AP消息将所述第二指示信息发送给所述IAB节点的DU，并且由所述IAB节点的DU发送给所述IAB子节点或者终端设备。
附记32.根据附记19所述的方法，其中，所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的源CU发送的第四指示信息。
附记33.根据附记32所述的方法，其中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中或之后，在目标CU发送无线资源控制重建立(RRC reestablishment)消息、或者、接收到无线资源控制重建立完成(RRC reestablishment complete)消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
附记34.根据附记32所述的方法，其中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中或之后，在目标CU接收到无线资源控制重配置完成消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
附记35.根据附记32至34任一项所述的方法，其中，所述第四指示信息指示所述目标CU中无线资源控制(RRC)层和/或分组数据会聚协议(PDCP)层的配置信息。
附记36.根据附记32至35任一项所述的方法，其中，所述第四指示信息包括如下信息的至少之一或任意组合：下一跳计数(nextHopChainingCount)、密钥集改变指示(keySet ChangeIndicator)、非接入层(NAS)安全信息(nas-Container)、加密算法(ciphering Algorithm)、完整性保护算法(integrityProtAlgorithm)。
附记37.根据附记32至36任一项所述的方法，其中，所述源CU接收所述目标CU通过无线资源控制(RRC)消息发送的所述第四指示信息，由所述源CU使用配置信息处理所述第四指示信息后，通过Xn接口发送给所述IAB节点的DU，并且由所述IAB节点的DU发送给所述IAB子节点或者终端设备。
附记38.一种集成的接入和回传(IAB)的通信方法，包括：
网络设备生成指示信息；所述指示信息被用于在IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备认为检测到无线链路失败(RLF)或指示所述IAB子节点或者终端设备发起连接重建；以及
向所述IAB子节点或终端设备发送所述指示信息。
附记39.根据附记38所述的方法，其中，所述网络设备为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的IAB节点；所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的IAB节点发送的第一指示信息。
附记40.根据附记39所述的方法，其中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中或之后，在所述IAB节点接收到目标集中式单元(Target CU)发送的无线资源控制重建立(RRC reestablishment)消息、或者与目标CU建立F1接口、或者接收到回传(BH)配置信息的情况下，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
附记41.根据附记39所述的方法，其中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中或之后，在所述IAB节点发起条件切换(CHO)、或者发送无线资源控制重配置完成(RRC reconfiguration complete)消息、或者与目标CU建立F1接口、或者接收到BH配置信息的情况下，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
附记42.根据附记39至42任一项所述的方法，其中，所述第一指示信息包括如下至少之一或任意组合：回传适配协议(BAP)协议数据单元(PDU)、无线链路控制(RLC) PDU、介质访问控制(MAC)控制信元(CE)、介质访问控制(MAC)子头、物理层信令。
附记43.根据附记38所述的方法，其中，所述网络设备为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的源CU；所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的源集中式单元(Source CU)通过恢复后或迁移后的路径发送的第三指示信息。
附记44.根据附记43所述的方法，其中，所述源集中式单元(CU)通过Xn接口将所述第三指示信息发送给目标CU或者所述IAB节点的分布式单元(DU)，并且由所述目标CU或所述DU将所述第三指示信息发送给所述IAB子节点或者终端设备。
附记45.根据附记43或44所述的方法，其中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中或之后，在所述源CU接收到目标CU发送的取回上下文请求消息的情况下，或者向所述目标CU发送取回上下文响应消息的情况下，或者接收到目标CU发送的上下文释放消息的情况下，所述源CU发送所述第三指示信息。
附记46.根据附记43或44所述的方法，其中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中或之后，所述源CU在接收到目标CU发送的上下文释放消息的情况下，发送所述第三指示信息。
附记47.根据附记43至46任一项所述的方法，其中，所述第三指示信息包括如下至少之一或任意组合：分组数据会聚协议(PDCP)协议数据单元(PDU)、无线资源控制(RRC)消息、F1AP消息。
附记48.一种集成的接入和回传(IAB)的通信方法，包括：
网络设备生成指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元(inter-CU)恢复或迁移的情况下，指示所述IAB子节点或者终端设备所对应的目标CU的配置信息；以及向所述IAB子节点或终端设备发送所述目标CU的配置信息。
附记49.根据附记48所述的方法，其中，所述网络设备为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的目标CU；所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的所述目标CU发送的第二指示信息。
附记50.根据附记49所述的方法，其中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中或之后，在所述目标CU发送无线资源控制重建立(RRC  reestablishment)消息、或者接收到无线资源控制重建立完成(RRC reestablishment complete)消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
附记51.根据附记49所述的方法，其中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中或之后，在所述目标CU接收到无线资源控制重配置完成消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述目标CU向所述IAB子节点或者终端设备发送所述第二指示信息。
附记52.根据附记49至51任一项所述的方法，其中，
所述第二指示信息指示所述目标CU中无线资源控制(RRC)层和/或分组数据会聚协议(PDCP)层的配置信息。
附记53.根据附记49至52任一项所述的方法，其中，所述第二指示信息包括如下信息的至少之一或任意组合：下一跳计数(nextHopChainingCount)、密钥集改变指示(keySetChangeIndicator)、非接入层(NAS)安全信息(nas-Container)、加密算法(ciphering Algorithm)、完整性保护算法(integrityProtAlgorithm)。
附记54.根据附记49至53任一项所述的方法，其中，所述目标CU通过无线资源控制(RRC)消息，将未加密或者被默认加密的第二指示信息发送给所述IAB子节点或者终端设备。
附记55.根据附记49至53任一项所述的方法，其中，所述目标CU通过无线资源控制(RRC)消息，使用所述源CU的配置信息将所述第二指示信息发送给所述IAB子节点或者终端设备。
附记56.根据附记49至53任一项所述的方法，其中，所述目标CU通过Xn接口将所述第二指示信息发送给所述源CU，并且由所述源CU使用配置信息处理所述第二指示信息后，通过恢复后或迁移后的路径发送给所述IAB子节点或者终端设备。
附记57.根据附记49至53任一项所述的方法，其中，所述目标CU通过F1AP消息将所述第二指示信息发送给所述IAB子节点或者终端设备。
附记58.根据附记49至53任一项所述的方法，其中，所述目标CU通过Xn接口将所述第二指示信息发送给所述源CU，由所述源CU通过F1AP消息将所述第二指示信息发送给所述IAB节点的DU，并且由所述IAB节点的DU发送给所述IAB子节点或者终端设备。
附记59.根据附记48所述的方法，其中，所述网络设备为跨集中式单元(inter-CU) 进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的源CU；所述指示信息为跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复或条件切换(CHO)迁移的源CU发送的第四指示信息。
附记60.根据附记59所述的方法，其中，在跨集中式单元(inter-CU)进行无线链路失败(RLF)恢复过程中或之后，在目标CU发送无线资源控制重建立(RRC reestablishment)消息、或者、接收到无线资源控制重建立完成(RRC reestablishment complete)消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
附记61.根据附记59所述的方法，其中，在跨集中式单元(inter-CU)进行条件切换(CHO)迁移过程中或之后，在目标CU接收到无线资源控制重配置完成消息、或者与所述IAB节点建立F1接口、或者发送BH配置信息的情况下，所述源CU向所述IAB子节点或者终端设备发送所述第四指示信息。
附记62.根据附记59至61任一项所述的方法，其中，所述第四指示信息指示所述目标CU中无线资源控制(RRC)层和/或分组数据会聚协议(PDCP)层的配置信息。
附记63.根据附记59至62任一项所述的方法，其中，所述第四指示信息包括如下信息的至少之一或任意组合：下一跳计数(nextHopChainingCount)、密钥集改变指示(keySet ChangeIndicator)、非接入层(NAS)安全信息(nas-Container)、加密算法(ciphering Algorithm)、完整性保护算法(integrityProtAlgorithm)。
附记64.根据附记59至63任一项所述的方法，其中，所述源CU接收所述目标CU通过无线资源控制(RRC)消息发送的所述第四指示信息，由所述源CU使用配置信息处理所述第四指示信息后，通过Xn接口发送给所述IAB节点的DU，并且由所述IAB节点的DU发送给所述IAB子节点或者终端设备。
附记65.一种集成的接入和回传(IAB)的通信方法，包括：
IAB节点检测到所述IAB节点与父节点之间的回传链路发生无线链路失败(RLF)或者正在尝试RLF恢复或者RLF恢复成功或者RLF恢复失败；以及
所述IAB节点向所属的IAB子节点或者终端设备发送RLF指示信息；所述RLF指示信息指示至少两种回传链路无线链路失败(BH RLF)的类型中的一种。
附记66.根据附记65所述的方法，其中，所述回传链路无线链路失败的类型包括下面的至少一种：
回传链路无线链路失败的类型1，其表示IAB节点检测到所述IAB节点与父节点之 间的回传链路发生无线链路失败(RLF)，
回传链路无线链路失败的类型2，其表示IAB节点检测到所述IAB节点与父节点之间的回传链路发生无线链路失败(RLF)且所述IAB节点正在尝试RLF恢复，
回传链路无线链路失败的类型3，其表示IAB节点检测到所述IAB节点与父节点之间的回传链路发生无线链路失败(RLF)且所述IAB节点RLF恢复成功，
回传链路无线链路失败的类型4，其表示IAB节点检测到所述IAB节点与父节点之间的回传链路发生无线链路失败(RLF)且所述IAB节点RLF恢复失败。
附记67.根据附记66所述的方法，其中，使用BAP控制PDU向所述IAB子节点或者终端设备发送所述RLF指示信息；所述BAP控制PDU的PDU类型域指示所述回传链路无线链路失败的类型。
附记68.根据附记67所述的方法，其中，BAP控制PDU的PDU类型域中的多于一个比特的一个取值指示回传链路无线链路失败的类型4；另一个取值指示回传链路无线链路失败的类型2或者回传链路无线链路失败的类型3。
附记69.根据附记67所述的方法，其中，BAP控制PDU的PDU类型域中的多个比特的一个取值指示回传链路无线链路失败的类型4；另一个取值指示回传链路无线链路失败的类型2；另一个取值指示回传链路无线链路失败的类型3。
附记70.根据附记66所述的方法，其中，使用所述RLF指示信息的BAP控制PDU的R域指示所述至少两种回传链路无线链路失败的类型。
附记71.根据附记70所述的方法，其中，BAP控制PDU的R域中的1个比特的一个取值指示回传链路无线链路失败的类型4；另一个取值指示回传链路无线链路失败的类型2或回传链路无线链路失败的类型3。
附记72.根据附记70所述的方法，其中，BAP控制PDU的R域中的多个比特的一个取值指示回传链路无线链路失败的类型4；另一个取值指示回传链路无线链路失败的类型2；另一个取值指示回传链路无线链路失败的类型3。
附记73.一种集成的接入和回传(IAB)的通信方法，包括：
IAB节点检测到所述IAB节点与父节点之间的回传链路上发生无线链路失败(RLF)或者正在尝试RLF恢复或者RLF恢复成功或者RLF恢复失败；以及
所述IAB节点使用物理层信令、MAC层信令、RLC层信令或者系统信息向所服务的终端设备发送所述RLF指示信息。
附记74.根据附记73所述的方法，其中，所述物理层信令包括下行控制信息(DCI) 格式，所述下行控制信息(DCI)指示回传链路无线链路失败的类型。
附记75.根据附记73所述的方法，其中，所述MAC层信令包括MAC CE；
所述MAC CE中的一个或多于一个比特或者一个域指示回传链路无线链路失败的类型。
附记76.根据附记73所述的方法，其中，所述RLC层信令包括RLC控制PDU。
附记77.根据附记73所述的方法，其中，所述系统信息包括主信息块(MIB)和/或系统信息块(SIB)；所述MIB和/或SIB中一个域指示回传链路无线链路失败的类型。
附记78.根据附记77所述的方法，其中，所述MIB中的小区禁止域(cellBarred)被设置为禁止或者所述SIB中的IAB支持域(IAB-support)不出现。
附记79.一种IAB子节点或终端设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记1至37任一项所述的IAB的通信方法。
附记80.一种网络设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记38至78任一项所述的IAB的通信方法。
附记81.一种通信系统，包括：
IAB子节点或终端设备，其执行如附记1至37任一项所述的IAB的通信方法；
网络设备，其执行如附记38至64任一项所述的IAB的通信方法。
附记82.一种通信系统，包括：
IAB节点，其执行如附记65至78任一项所述的IAB的通信方法。

Claims (20)

  1. 一种集成的接入和回传(IAB)的通信装置，包括：
    接收部，其接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元恢复或迁移的情况下，指示所述IAB子节点或者终端设备认为检测到无线链路失败或指示所述IAB子节点或者终端设备发起连接重建；以及
    处理部，其发起无线链路失败恢复过程或者连接重建过程。
  2. 根据权利要求1所述的装置，其中，所述指示信息为跨集中式单元进行无线链路失败恢复或条件切换迁移的IAB节点发送的第一指示信息。
  3. 根据权利要求2所述的装置，其中，在跨集中式单元进行无线链路失败恢复过程中或之后，在所述IAB节点接收到目标集中式单元发送的无线资源控制重建立消息、或者与目标集中式单元建立F1接口、或者接收到回传配置信息的情况下，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息；
    或者，
    在跨集中式单元进行条件切换迁移过程中或之后，在所述IAB节点发起条件切换、或者发送无线资源控制重配置完成消息、或者与目标集中式单元建立F1接口、或者接收到回传配置信息的情况下，所述IAB节点向所述IAB子节点或者终端设备发送所述第一指示信息。
  4. 根据权利要求3所述的装置，其中，所述处理部还用于：
    在所述IAB子节点或终端设备为单连接的情况下，或者所述IAB子节点或终端设备被配置双连接且所述IAB节点为所述IAB子节点或终端设备的主小区组的情况下，确定对主小区组检测到无线链路失败；
    其中，在定时器被配置且辅小区组发送没有被挂起且主服务小区改变没有在进行的情况下，发起主小区组失败信息过程来报告主小区组无线链路失败，否则发起所述连接重建过程。
  5. 根据权利要求3所述的装置，其中，所述处理部还用于：
    在所述IAB子节点或终端设备被配置双连接且所述IAB节点为所述IAB子节点或终端设备的辅小区组的情况下，确定对辅小区组检测到无线链路失败；
    其中，在主小区组发送没有被挂起的情况下，发起辅小区组失败信息过程来报告辅小区组无线链路失败，否则发起所述连接重建过程。
  6. 根据权利要求2所述的装置，其中，所述第一指示信息包括如下至少之一或任意组合：回传适配协议协议数据单元、无线链路控制协议数据单元、介质访问控制控制信元、介质访问控制子头、物理层信令。
  7. 根据权利要求1所述的装置，其中，所述指示信息为跨集中式单元进行无线链路失败恢复或条件切换迁移的源集中式单元通过恢复后或迁移后的路径发送的第三指示信息。
  8. 根据权利要求7所述的装置，其中，所述源集中式单元通过Xn接口将所述第三指示信息发送给目标集中式单元或者所述IAB节点的分布式单元，并且由所述目标集中式单元或所述分布式单元将所述第三指示信息发送给所述IAB子节点或者终端设备。
  9. 根据权利要求7所述的装置，其中，在跨集中式单元进行无线链路失败恢复过程中或之后，在所述源集中式单元接收到目标集中式单元发送的取回上下文请求消息的情况下，或者向所述目标集中式单元发送取回上下文响应消息的情况下，或者接收到目标集中式单元发送的上下文释放消息的情况下，所述源集中式单元发送所述第三指示信息。
  10. 根据权利要求7所述的装置，其中，在跨集中式单元进行条件切换迁移过程中或之后，所述源集中式单元在接收到目标集中式单元发送的上下文释放消息的情况下，发送所述第三指示信息。
  11. 根据权利要求7所述的装置，其中，所述第三指示信息包括如下至少之一或任意组合：分组数据会聚协议协议数据单元、无线资源控制消息、F1AP消息。
  12. 一种集成的接入和回传(IAB)的通信装置，包括：
    接收部，其接收网络设备发送的指示信息；所述指示信息被用于在所述IAB子节点或者终端设备所在的IAB节点进行跨集中式单元恢复或迁移的情况下，指示所述IAB子节点或者终端设备所对应的目标集中式单元的配置信息；以及
    处理部，其根据所述目标集中式单元的配置信息进行通信。
  13. 根据权利要求12所述的装置，其中，所述指示信息为跨集中式单元进行无线链路失败恢复或条件切换迁移的所述目标集中式单元发送的第二指示信息。
  14. 根据权利要求13所述的装置，其中，在跨集中式单元进行无线链路失败恢复过程中或之后，在所述目标集中式单元发送无线资源控制重建立消息、或者接收到无线资源控制重建立完成消息、或者与所述IAB节点建立F1接口、或者发送回传配置信息的情况下，所述目标集中式单元向所述IAB子节点或者终端设备发送所述第二指示信息。
  15. 根据权利要求13所述的装置，其中，在跨集中式单元进行条件切换迁移过程中或之后，在所述目标集中式单元接收到无线资源控制重配置完成消息、或者与所述IAB节点建立F1接口、或者发送回传配置信息的情况下，所述目标集中式单元向所述IAB子节点或者终端设备发送所述第二指示信息。
  16. 根据权利要求13所述的装置，其中，所述第二指示信息指示所述目标集中式单元中无线资源控制层和/或分组数据会聚协议层的配置信息；
    其中，所述第二指示信息包括如下信息的至少之一或任意组合：下一跳计数、密钥集改变指示、非接入层安全信息、加密算法、完整性保护算法。
  17. 根据权利要求13所述的装置，其中，所述目标集中式单元通过无线资源控制消息，将未加密或者被默认加密的第二指示信息发送给所述IAB子节点或者终端设备；
    或者，所述目标集中式单元通过无线资源控制消息，使用所述源集中式单元的配置信息将所述第二指示信息发送给所述IAB子节点或者终端设备；
    或者，所述目标集中式单元通过Xn接口将所述第二指示信息发送给所述源集中式单元，并且由所述源集中式单元使用配置信息处理所述第二指示信息后，通过恢复后或迁移后的路径发送给所述IAB子节点或者终端设备；
    或者，所述目标集中式单元通过F1AP消息将所述第二指示信息发送给所述IAB子节点或者终端设备；
    或者，所述目标集中式单元通过Xn接口将所述第二指示信息发送给所述源集中式单元，由所述源集中式单元通过F1AP消息将所述第二指示信息发送给所述IAB节点的分布式单元，并且由所述IAB节点的分布式单元发送给所述IAB子节点或者终端设备。
  18. 根据权利要求12所述的装置，其中，所述指示信息为跨集中式单元进行无线链路失败恢复或条件切换迁移的源集中式单元发送的第四指示信息。
  19. 根据权利要求18所述的装置，其中，所述源集中式单元接收所述目标集中式单元通过无线资源控制消息发送的所述第四指示信息，由所述源集中式单元使用配置信息处理所述第四指示信息后，通过Xn接口发送给所述IAB节点的分布式单元，并且由所述IAB节点的分布式单元发送给所述IAB子节点或者终端设备。
  20. 根据权利要求18所述的装置，其中，在跨集中式单元进行无线链路失败恢复过程中或之后，在目标集中式单元发送无线资源控制重建立消息、或者、接收到无线资源控制重建立完成消息、或者与所述IAB节点建立F1接口、或者发送回传配置信息的情况下，所述源集中式单元向所述IAB子节点或者终端设备发送所述第四指示信息；
    或者，
    在跨集中式单元进行条件切换迁移过程中或之后，在目标集中式单元接收到无线资源控制重配置完成消息、或者与所述IAB节点建立F1接口、或者发送回传配置信息的情况下，所述源集中式单元向所述IAB子节点或者终端设备发送所述第四指示信息。
PCT/CN2021/071577 2021-01-13 2021-01-13 集成的接入和回传的通信方法以及装置 WO2022151086A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2023542006A JP2024502623A (ja) 2021-01-13 2021-01-13 Ｉａｂの通信方法及び装置
PCT/CN2021/071577 WO2022151086A1 (zh) 2021-01-13 2021-01-13 集成的接入和回传的通信方法以及装置
CN202180088990.7A CN116686335A (zh) 2021-01-13 2021-01-13 集成的接入和回传的通信方法以及装置
US18/220,345 US20230354136A1 (en) 2021-01-13 2023-07-11 Integrated access and backhaul communication method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/071577 WO2022151086A1 (zh) 2021-01-13 2021-01-13 集成的接入和回传的通信方法以及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/220,345 Continuation US20230354136A1 (en) 2021-01-13 2023-07-11 Integrated access and backhaul communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2022151086A1 true WO2022151086A1 (zh) 2022-07-21

Family

ID=82446622

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/071577 WO2022151086A1 (zh) 2021-01-13 2021-01-13 集成的接入和回传的通信方法以及装置

Country Status (4)

Country Link
US (1) US20230354136A1 (zh)
JP (1) JP2024502623A (zh)
CN (1) CN116686335A (zh)
WO (1) WO2022151086A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024031289A1 (zh) * 2022-08-08 2024-02-15 富士通株式会社 网络节点的通信方法、移动节点的通信方法、移动节点和宿主设备

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111757398A (zh) * 2019-03-28 2020-10-09 华为技术有限公司 一种通信方法与装置

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111757398A (zh) * 2019-03-28 2020-10-09 华为技术有限公司 一种通信方法与装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Consideration of topology adaptation enhancement for R17-IAB", 3GPP DRAFT; R2-2009652, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20201102 - 20201113, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051942568 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024031289A1 (zh) * 2022-08-08 2024-02-15 富士通株式会社 网络节点的通信方法、移动节点的通信方法、移动节点和宿主设备

Also Published As

Publication number Publication date
US20230354136A1 (en) 2023-11-02
CN116686335A (zh) 2023-09-01
JP2024502623A (ja) 2024-01-22

Similar Documents

Publication Publication Date Title
JP5920801B2 (ja) データ転送方法、装置、および通信システム
US20230147304A1 (en) Communication Method and Communications Apparatus
US10863569B2 (en) RRC connection re-establishment method for data transmission
US20180049091A1 (en) Method, apparatus, and system for transmitting data during handover procedure
US20120142361A1 (en) Method, Device and System for Reconfiguring Aggregation Cell
WO2016061785A1 (zh) 无线资源控制rrc连接方法、重连接方法和装置
US20220232431A1 (en) Sequence number transfer for radio bearers
JP6885427B2 (ja) 基地局、無線通信システムおよび通信方法
WO2017219355A1 (zh) 多连接通信方法和设备
WO2020088305A1 (zh) 一种通信方法、通信装置及系统
WO2015161575A1 (zh) 用户终端位置上报方法、基站、移动管理实体及系统
WO2018014154A1 (zh) 一种rrc连接重建方法和装置
WO2022082518A1 (zh) 信号的接收和发送方法、装置和通信系统
US20230254729A1 (en) Migration method and apparatus for iab-node
US20230354136A1 (en) Integrated access and backhaul communication method and apparatus
CN112673675B (zh) 基于rlc的分组转发中的序列号(sn)同步机制
WO2022082690A1 (zh) 群组切换的方法、装置和系统
WO2023010298A1 (zh) 信息发送方法，信息处理方法以及装置
WO2022205252A1 (zh) 发送和接收信号的方法、装置和通信系统
WO2022082544A1 (zh) Iab节点的移植方法及装置
WO2022082691A1 (zh) Iab网络的rlf恢复方法、装置以及相关设备
WO2017166291A1 (zh) 一种通信方法、终端、基站和移动性管理设备
WO2016101617A1 (zh) 一种切换流程中安全信息的处理方法、接入网关及基站
WO2024207316A1 (zh) 多路径的通信方法以及装置
WO2022233008A1 (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: 21918301

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180088990.7

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2023542006

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21918301

Country of ref document: EP

Kind code of ref document: A1