WO2022233008A1 - 消息发送方法、装置和系统 - Google Patents

消息发送方法、装置和系统 Download PDF

Info

Publication number
WO2022233008A1
WO2022233008A1 PCT/CN2021/091967 CN2021091967W WO2022233008A1 WO 2022233008 A1 WO2022233008 A1 WO 2022233008A1 CN 2021091967 W CN2021091967 W CN 2021091967W WO 2022233008 A1 WO2022233008 A1 WO 2022233008A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
iab
message
rrc reconfiguration
reconfiguration message
Prior art date
Application number
PCT/CN2021/091967
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 JP2023566914A priority Critical patent/JP2024516007A/ja
Priority to CN202180097601.7A priority patent/CN117337598A/zh
Priority to EP21939656.1A priority patent/EP4336906A1/en
Priority to PCT/CN2021/091967 priority patent/WO2022233008A1/zh
Publication of WO2022233008A1 publication Critical patent/WO2022233008A1/zh
Priority to US18/384,944 priority patent/US20240057205A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0009—Control or signalling for completing the hand-off for a plurality of users or terminals, e.g. group communication or moving wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/0867—Load balancing or load distribution among entities in the downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This application relates to the field of communications.
  • Ultra-dense network is one of the goals of 5G. Deploying a new radio (NR) network that does not require wired backhaul is essential to achieve ultra-dense 5G. Networking is very important. As 5G millimeter wave reduces the cell coverage, the wireless self-backhaul system also needs to be multi-hop to meet the deployment requirements. 5G's high bandwidth, massive multiple-input multiple-output MIMO and beam systems make it easier than LTE to develop wireless self-backhaul systems for ultra-dense NR cells. R16 started the research and standardization of the IAB (Integrated access and backhaul, integrated access and backhaul) project.
  • IAB Integrated access and backhaul, integrated access and backhaul
  • Figure 1 is a schematic diagram of the IAB system.
  • the relay node supports both access and backhaul functions, and the wireless transmission link of the relay node is in the time domain,
  • the access link and the backhaul link are multiplexed in the frequency domain or the space domain, and the access link and the backhaul link can use the same or different frequency bands.
  • the relay node refers to an IAB-node (IAB node), which supports both access and backhaul functions.
  • IAB node The last hop access node on the network side is called IAB-donnor (IAB host), which supports the gNB function and supports IAB-node access. All UE data can be sent back to IAB-Donor through one or more hops via IAB-node.
  • IAB-node The function of IAB-node is divided into two parts, one part is gNB-DU function, called IAB-DU (distribution unit), and the other part is UE function, called IAB-MT (mobile terminal).
  • the IAB-DU implements the network side device function, connects to the downstream child IAB-node (child IAB node), provides NR air interface access to the UE and the downstream child IAB-node, and establishes an F1 connection with the IAB Donor-CU.
  • IAB-MT implements some terminal equipment functions and connects to the upstream parent IAB-node (parent IAB node) or IAB-Donor DU.
  • IAB-MT includes physical layer, layer 2, RRC (Radio Resource Control, Radio Resource Control) and NAS (Non-Access Stratum, non-access layer) layer function, also indirectly connected to IAB Donor-CU and core network (Core Network, CN).
  • the IAB-node can access the network in an independent networking (SA, Standalone) mode or a non-independent networking (EN-DC, E-UTRA-NRDual Connectivity) mode.
  • SA independent networking
  • EN-DC non-independent networking
  • FIG. 2 is a schematic diagram of an IAB architecture in SA mode.
  • Figure 3 is a schematic diagram of an IAB architecture in EN-DC mode.
  • FIG. 4 is a schematic diagram of an IAB node (IAB-node), a parent node (parent IAB-node) and a child node (child IAB-node).
  • IAB-node IAB node
  • parent IAB-node parent node
  • child IAB-node child node
  • the IAB-DU of the IAB node is connected to the IAB-MT of the child node as the network side
  • the IAB-MT of the IAB node is connected to the IAB-DU of the parent node as the terminal side.
  • Figure 5 is a schematic diagram of the F1 user plane (F1-U) protocol stack between the IAB-DU and the IAB-Donor CU.
  • Figure 6 is a schematic diagram of the F1 Control Plane (F1-C) protocol stack between the IAB-DU and the IAB-Donor CU.
  • F1-U and F1-C are built on the transport (IP) layer between IAB-DU and IAB-Donor-CU. and one-hop wired backhaul.
  • IP transport
  • BAP backhaul adaptation protocol
  • BAP PDUs Protocol Data Units
  • RLC Radio Link Control
  • multiple RLC channels of the backhaul link can be configured by IAB-Donor to carry different priorities and QoS (Quality of Service) ) service
  • the BAP entity maps BAP PDUs to different return RLC channels.
  • the IAB system has already supported the adaptive change of topology and routing caused by IAB-node moving between different DUs under the same Donor-CU.
  • the IAB-node moves under the same Donor-CU (at this time, the IAB-node is called Migrating IAB-node), it also maintains the topology relationship with the downstream child IAB-node and the UE.
  • the change of the transmission path that is, the change of the network topology, for example, the change of the network topology caused when the IAB-node switches to a new parent node or establishes a dual connection with the new parent node.
  • Fig. 7 is a schematic diagram of the network topology change caused by the movement of the IAB-node.
  • IAB-node5 switches from the cell under IAB-node3 to the cell under IAB-node 4
  • the transmission path from IAB-node5 and its downstream child nodes IAB-node 6 to Donor-CU is node1 and IAB-node 2 become through IAB-node2 and IAB-node 4, that is, the network topology has changed.
  • the Donor-CU can configure the related configuration of the network topology update for the IAB-node through the RRC reconfiguration message information, wherein the default route identifier includes the BAP address and path ID of the destination Donor-DU.
  • the IAB-node After the IAB-node switches to the new parent node, the IAB-node starts to apply the above configuration information.
  • the configuration related to the network topology update is also performed in the same way.
  • the network topology update of the child node is performed after the IAB-node completes the access to the new parent node.
  • the child node performs the network topology update after the IAB-node, because the Donor-DU (parent node) changes after the topology update.
  • the uplink data generated by the child node according to the original path configuration carries the address of the original Donor-DU, which is different from the address of the new Donor-DU.
  • uplink data will be discarded by the new Donor-DU, resulting in the child node according to the original Donor-DU address.
  • the uplink data generated by the path configuration cannot be sent to the CU, and the discarded uplink data will be retransmitted by the UE, thus resulting in long data transmission delay and service interruption time.
  • the Donor-CU needs to send a configuration message related to the network topology update to the IAB-node and each of its downstream sub-nodes.
  • the configuration message for each node needs to be sent separately, resulting in a large amount of signaling message overhead and a long service interruption time at the same time.
  • embodiments of the present application provide a message sending method, apparatus, and system.
  • an apparatus for sending a message is provided, which is applied to a first integrated access and backhaul node (IAB-node), and the apparatus includes:
  • a first receiving unit which receives a second Radio Resource Control (RRC) reconfiguration message for path migration of the second IAB-node from the Donor-CU; wherein the second IAB-node is the Describe the downstream child node of the first IAB-node;
  • RRC Radio Resource Control
  • a second receiving unit which receives the first RRC reconfiguration message for the first IAB-node path migration from the Donor-CU;
  • a first sending unit which forwards the second RRC reconfiguration message to the second IAB-node when the random access of the first IAB-node succeeds.
  • an apparatus for sending a message which is applied to a second integrated access and backhaul node (IAB-node), and the apparatus includes:
  • a fourth receiving unit which receives the third RRC reconfiguration message for the third IAB-node path migration from the Donor-CU;
  • the third sending unit when receiving the second RRC reconfiguration message sent by the Donor-CU and forwarded by the first IAB-node, forwards the third RRC reconfiguration message to the third IAB-node, so The second RRC reconfiguration message is used for the second IAB-node path migration;
  • the third IAB-node is a downstream child node of the second IAB-node, and the second IAB-node is a downstream child node of the first IAB-node.
  • an apparatus for sending a message which is applied to a second integrated access and backhaul node (IAB-node), and the apparatus includes:
  • a sixth receiving unit which receives the third RRC reconfiguration message for the third IAB-node path migration from the Donor-CU;
  • a seventh receiving unit which receives the path migration failure indication information sent when the first IAB-node fails to randomly access
  • a second processing unit which triggers the RRC re-establishment process or rolls back to the original path configuration
  • the third IAB-node is a downstream child node of the second IAB-node, and the second IAB-node is a downstream child node of the first IAB-node.
  • One of the beneficial effects of the embodiments of the present application is that: before the IAB-node switches to the new parent node, the information related to the network topology update configured for its child nodes is sent by the Donor-CU to the IAB-node and cached in the IAB-node , when the random access of the IAB-node switches to the new parent node is successful, the IAB-node forwards the information related to the network topology update configured by the Donor-CU for its child nodes to its child nodes, so that the IAB-node and the Its sub-nodes update the network topology almost at the same time, reducing the service interruption time caused by node migration.
  • Fig. 1 is a schematic diagram of the IAB system
  • Fig. 2 is the schematic diagram of the IAB architecture of SA mode
  • Fig. 3 is the schematic diagram of the IAB framework of EN-DC mode
  • Figure 4 is a schematic diagram of a parent node (parent IAB-node) and a child node (child IAB-node);
  • Fig. 5 is the schematic diagram of the F1-U protocol stack of the IAB system
  • Fig. 6 is the schematic diagram of the F1-C protocol stack of the IAB system
  • FIG. 7 is a schematic diagram of a method for moving an IAB node between different DUs under the same Donor
  • FIG. 8 is a schematic diagram of a message sending method according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a message sending method according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a message sending method according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a message sending method according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a message sending method according to an embodiment of the present application.
  • FIG. 13-15 are schematic diagrams of a scenario of a message sending method according to an embodiment of the present application.
  • 16-17 are schematic diagrams of still another scenario of the message sending method according to the embodiment of the present application.
  • 19A is a schematic diagram of a downlink message structure according to an embodiment of the present application.
  • 19B is a schematic diagram of an uplink message structure according to an embodiment of the present application.
  • 20A is a schematic diagram of a downlink message structure according to an embodiment of the present application.
  • 20B is a schematic diagram of an uplink message structure according to an embodiment of the present application.
  • 21 is a schematic diagram of a message sending apparatus according to an embodiment of the present application.
  • 22 is another schematic diagram of a message sending apparatus according to an embodiment of the present application.
  • FIG. 23 is another schematic diagram of a message sending apparatus according to an embodiment of the present application.
  • FIG. 24 is another schematic diagram of a message sending apparatus according to an embodiment of the present application.
  • 25 is a schematic diagram of a communication system according to an embodiment of the present application.
  • 26 is a schematic diagram of an IAB node in an embodiment of the present application.
  • FIG. 27 is a schematic diagram of a Donor 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 New Radio (NR, New Radio), Long Term Evolution (LTE, Long Term Evolution), enhanced Long Term Evolution (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.
  • NR New Radio
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • High-Speed Packet Access 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 future 5G, 6G, etc., and/or other communication protocols currently known or to be developed in the future.
  • 1G generation
  • 2G 2.5G, 2.75G
  • 3G 3G
  • 4G 4.5G
  • future 5G, 6G, 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 (eg femto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low power node eg femto, pico, etc.
  • 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 term "User Equipment” refers to a device that accesses a communication network through a network device and receives network services, and may also be called “Terminal Equipment” (TE, Terminal Equipment).
  • a terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS, Mobile Station), a terminal, a user, a subscriber station (SS, Subscriber Station), an access terminal (AT, Access Terminal), a station, etc. Wait.
  • 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, In-vehicle communication terminals, device-to-device (D2D, Device to Device) terminals, machine-to-machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • IAB-node3 is the parent node of IAB-node4, and IAB-node4 is the parent node of IAB-node5.
  • the network topology changes, that is, IAB -Transmission path change between node3, IAB-node4 and IAB-node5 and Donor-CU.
  • Donor CU sends configuration messages related to network topology update to IAB-node3, IAB-node4 and IAB-node5, so that the F1 transmission path is switched from the original path to the new path.
  • the network topology update to IAB-node4 and IAB-node5 is performed after IAB-node3 completes the access to the new parent node, that is, IAB-node4 and IAB-node5 perform network topology update after IAB-node3.
  • IAB-node4 and IAB-node5 perform network topology update after IAB-node3.
  • the uplink data sent by IAB-node4 and IAB-node5 according to the original configuration is discarded by Donor-DU2, causing long transmission delay and service interruption time.
  • Donor-Cu must send a downlink F1AP message (F1 Application Protocol, F1 Application Protocol) carrying network topology update related configuration information for IAB-node3 and each of its sub-nodes, namely DL F1AP MESSAGE To IAB-node3 and its respective parent node of each child node (see messages A, B, C in Figure 7).
  • F1AP message F1 Application Protocol, F1 Application Protocol
  • message C it can only be sent after the IAB-node4 path is successfully migrated. Long service interruption time.
  • the information related to the network topology update configured for its child nodes is sent by the Donor-CU to the IAB-node and cached in the IAB-node.
  • the IAB-node forwards the information related to the network topology update configured by the Donor-CU for its child nodes to its child nodes, so that the IAB-node and its child nodes can be executed almost simultaneously.
  • the network topology is updated to reduce service interruption time caused by node migration.
  • the first IAB-node as a migration node (for example, IAB-node3 in FIG. 7 ) is an IAB node under the control of Donor-CU, and the first IAB-node changes from the first parent node (for example, in FIG. 7 ).
  • IAB-node1 migrates (switches) to the second parent node (for example, IAB-node2 in Figure 7), the second IAB-node (for example, IAB-node4 in Figure 7) is the downstream child node of the first IAB-node, and the third IAB -node (eg IAB-node5 in Figure 7) is the downstream child node of the second IAB-node.
  • the number of the second IAB-node or the third IAB-node may be one or at least two, and the third IAB-node may also have other child nodes, which are not limited in the embodiments of the present application.
  • IAB-node4 is used as the second IAB-node
  • IAB-node5 is used as the third IAB-node
  • IAB-node5 has no other child nodes as an example for description.
  • This embodiment of the present application provides a method for sending a message, which is described from the side of the first IAB-node.
  • FIG. 8 is a schematic diagram of a method for sending a message in this embodiment. As shown in FIG. 8 , the method includes:
  • the first IAB-node receives a second radio resource control (RRC) reconfiguration message from the Donor-CU for path migration of the second IAB-node;
  • RRC radio resource control
  • the first IAB-node receives a first RRC reconfiguration message from the Donor-CU for path migration of the first IAB-node;
  • the first IAB-node forwards the second RRC reconfiguration message to the second IAB-node.
  • both the first RRC reconfiguration message and the second RRC reconfiguration message are generated by the Donor-CU configuration in 801 and 802, and the first or second RRC reconfiguration message from the Donor-CU may be What is directly sent by the Donor-CU to the first IAB-node may also be sent by the Donor-CU to the first parent node, and forwarded by the first parent node to the first IAB-node.
  • This embodiment of the present application does not Do not use this as a limitation.
  • the first IAB-node forwards the second RRC reconfiguration to the second IAB-node only when the first IAB-node determines that the first RRC reconfiguration message is used for path migration of the first IAB-node information.
  • the first RRC reconfiguration message includes the first parameter for changing the transmission path configuration for the first IAB-node
  • the first IAB-node may determine that the first RRC reconfiguration message is for path migration of the first IAB-node.
  • the first parameter includes a default Backhaul Radio Link Control (BH RLC) channel configured for the first IAB-node, a default Backhaul Adaptation Protocol (BAP) route or an Internet Protocol IP address.
  • BH RLC Backhaul Radio Link Control
  • BAP Backhaul Adaptation Protocol
  • the default BH RLC channel can be the BH RLC channel used by upstream F1-C and non-F1 data
  • the default BAP route can be the route used by upstream F1-C and non-F1 data, including the path identifier and destination BAP address
  • the The IP address indicates the IP address that can be routed to the new Donor-DU (for example, Donor-DU2 in FIG. 7 ) after switching to the second parent node.
  • the first IAB-node receives the first RRC reconfiguration message containing the above-mentioned first RRC reconfiguration message. parameter, it is determined that the first RRC reconfiguration message is a configuration message for path migration.
  • the first IAB-node determines that the first RRC reconfiguration message is a configuration message for path relocation by using the first RRC reconfiguration message including the first path relocation indication information.
  • the RRC message may not be used for path relocation, so it is necessary to display to the first IAB-node to instruct the RRC reconfiguration related to the path relocation, wherein,
  • the first path relocation indication information is used to indicate that the first RRC reconfiguration message is a reconfiguration message for the first IAB-node to perform path relocation.
  • this method is applied to the case where the first IAB-node performs path migration in different Donor-DUs (the Donor-DU changes after switching to the new parent node), then the first RRC reconfiguration message is used It is based on the path migration of the first IAB-node between Donor-DUs.
  • the first path relocation indication information is used to indicate that the first IAB-node is performing path relocation between Donor-DUs, that is, when the first RRC message contains the first path relocation indication information, it indicates that the first RRC reconfiguration message is for A reconfiguration message for path migration between different Donor-DUs at the first IAB-node.
  • the first RRC reconfiguration message and the second RRC reconfiguration message may be carried by one downlink message, that is, the first IAB-node simultaneously receives the first RRC reconfiguration message and the second RRC reconfiguration message, or are carried by two downlink messages respectively, that is, the first IAB-node receives the second RRC reconfiguration message and the first RRC reconfiguration message successively, which will be described in detail in the following cases. .
  • the first IAB-node switches to the second parent node and performs path migration, wherein the first IAB-node needs to perform random access to switch to the second parent node, the first IAB-node
  • the RRC reconfiguration message includes relevant information about the first IAB-node switching to the second parent node.
  • For the random access process reference may be made to the random access of the IAB node in the prior art, which will not be repeated here. Only when the random access succeeds, the forwarding of the cached second RRC reconfiguration message is triggered. When the random access fails, the first IAB-node triggers RRC re-establishment.
  • the RRC re-establishment process For the RRC re-establishment process, reference may be made to the RRC re-establishment of the IAB-node in the prior art, which will not be repeated here.
  • the first IAB-node also needs to send path migration failure indication information to its child nodes.
  • the second RRC reconfiguration message may also be forwarded to its child nodes or the second RRC reconfiguration message may be cleared. , the behavior of its child nodes when the random access fails will be specifically described in the embodiments of the second aspect described later.
  • the method may further include: the first IAB-node sending a first RRC reconfiguration complete message to the Donor-CU; in addition, the first IAB-node
  • the node may also receive a second RRC reconfiguration complete message sent by the second IAB-node, and optionally, may also forward the second RRC reconfiguration complete message to the Donor-CU, where the first RRC reconfiguration completes
  • the configuration complete message and the second RRC reconfiguration complete message may be carried by one uplink message, or may be carried by two uplink messages respectively, and the above-mentioned sending to the Donor-CU may be directly sent to the Donor-CU, or may be sent via the second parent node. It will be forwarded to the Donor-CU, and will be explained in detail later.
  • the information related to the network topology update configured for its child nodes is sent by the Donor-CU to the IAB-node and cached in the IAB-node, and the IAB-node switches to the new node.
  • the IAB-node forwards the information related to the network topology update configured by Donor-CU for its child nodes to its child nodes, so that the IAB-node and its child nodes can perform the network topology almost simultaneously. Update to reduce service interruption time due to node migration.
  • An embodiment of the present application provides a method for sending a message, which is described from the second IAB-node side.
  • the behavior of the third IAB-node side is similar to the behavior of the second IAB-node side, which is not exemplified here.
  • the second IAB-node receives the third RRC reconfiguration message for the third IAB-node path migration from the Donor-CU.
  • the third RRC reconfiguration message is generated by the Donor-CU configuration, and the third RRC reconfiguration message from the Donor-CU may be directly sent by the Donor-CU to the second IAB-node, or It can be sent by the Donor-CU to the first IAB-node and forwarded by the first IAB-node to the second IAB-node, or it can be sent by the Donor-CU to the first parent node and sent by the first parent
  • the node forwarded to the first IAB-node, and then forwarded by the first IAB-node to the second IAB-node, is not limited in this embodiment of the present application.
  • the second IAB-node when the random access of the first IAB-node is successful (random access is completed), the second IAB-node receives the second RRC reconfiguration message forwarded by the first IAB-node, and after receiving the second RRC reconfiguration message When there is a second RRC reconfiguration message, the third RRC reconfiguration message is forwarded to the third IAB-node; when the first IAB-node random access fails (it can also be regarded as the random access is not completed or cannot be completed or cannot be completed correctly ), the second IAB-node receives the path migration failure indication information sent by the first IAB-node, and triggers the RRC re-establishment process or falls back to the original path configuration, which are described below.
  • FIG. 9 is a schematic diagram of a method for sending a message on the second IAB-node side when the first IAB-node succeeds in random access. As shown in FIG. 9 , the method includes:
  • the second IAB-node receives a third RRC reconfiguration message for path migration of the third IAB-node from the Donor-CU;
  • the second IAB-node forwards the third RRC reconfiguration message to the third IAB-node, and the second RRC reconfiguration message is forwarded to the third IAB-node.
  • Two RRC reconfiguration messages are used for the second IAB-node path migration.
  • the method may further include (not shown): the second IAB-node receives the second RRC reconfiguration message sent by the Donor-CU and forwarded by the first IAB-node,
  • the implementation manner of the second RRC reconfiguration message is as described above, and will not be repeated here.
  • the second RRC reconfiguration message and the third RRC reconfiguration message may be carried by one downlink message, or by two downlink messages respectively. Bearing, which will be described in detail in the following sections.
  • the second IAB-node upon receiving the second RRC reconfiguration message, performs path migration, and at the same time triggers the second IAB-node to forward the cached third IAB-node to the third IAB-node RRC reconfiguration message. Since the second IAB-node does not change the parent node (the parent node is still the first IAB-node), the second RRC reconfiguration message does not contain handover information, and the second IAB-node does not need to perform a random access procedure.
  • the second IAB-node determines that the second RRC reconfiguration message is a configuration message for path migration of the second IAB-node, forwards the second IAB-node to the third IAB-node The third RRC reconfiguration message. It can be determined that the second RRC reconfiguration message is used for the path migration of the second IAB-node in the following two ways.
  • the second RRC reconfiguration message includes a second message for changing the transmission path configuration for the second IAB-node.
  • the parameter or, contains the second path migration indication information.
  • the implementations of the second parameter and the second path relocation indication information are the same as those of the foregoing first parameter and the first path relocation indication information, and will not be repeated here.
  • the method may further include: (not shown) the second IAB-node sending a second RRC reconfiguration complete message to the first IAB-node; and the first IAB-node The second IAB-node receives the third RRC reconfiguration complete message sent by the third IAB-node.
  • the third RRC reconfiguration complete message may also be forwarded to the Donor-CU, where the second RRC reconfiguration complete message and the third RRC reconfiguration complete message may be carried by one uplink message, or by two. Each uplink message is carried separately.
  • the above-mentioned sending to the Donor-CU can be directly sent to the Donor-CU, or forwarded to the Donor-CU via the first IAB node and/or the second parent node.
  • the following will be carried out on a case-by-case basis. Detailed description.
  • the information related to the network topology update configured for its child nodes is sent by the Donor-CU to the IAB-node and cached in the IAB-node, and the IAB-node switches to the new node.
  • the IAB-node forwards the information related to the network topology update configured by Donor-CU for its child node to its child node. Forwards information related to the network topology update configured by Donor-CU for its child nodes, so that IAB-node and its child nodes can update the network topology at almost the same time, reducing service interruption time caused by node migration.
  • Figure 10 is a schematic diagram of a method for sending a message on the second IAB-node side when the random access of the first IAB-node fails. As shown in Figure 10, the method includes:
  • the second IAB-node receives a third RRC reconfiguration message for path migration of the third IAB-node from the Donor-CU;
  • the second IAB-node receives the path migration failure indication information sent when the first IAB-node fails to randomly access;
  • the second IAB-node triggers an RRC re-establishment process.
  • the implementation of the 1001 is as described above, which is not repeated here.
  • the first IAB-node sends path migration failure indication information to the second IAB-node, so that the second IAB-node performs the RRC re-establishment process, and the first IAB-node can also forward the second RRC reconfiguration message to the second IAB-node. Or clear the second RRC reconfiguration message.
  • the method may further include: the second IAB-node receives the Donor-CU and sends it to the first IAB-node, and the first IAB-node sends it to the first IAB-node. - the second RRC reconfiguration message forwarded by the node for the path migration of the second IAB-node.
  • the method may further include: (not shown) the second IAB-node forwarding the path migration failure indication information received in 1002 to the third IAB-node to trigger the third IAB-node to execute RRC is re-established.
  • the method may further include: (not shown) forwarding the third RRC reconfiguration message by the second IAB-node to the third IAB-node, or clearing the third RRC reconfiguration message, which For a specific implementation manner, reference may be made to the first IAB-node side, which will not be repeated here.
  • the second IAB-node triggers an RRC re-establishment process.
  • RRC re-establishment process reference may be made to the RRC re-establishment of the IAB-node in the prior art, which will not be repeated here.
  • the IAB-node when the random access of the IAB-node switches to the new parent node fails, it triggers RRC re-establishment and indicates to its child nodes that the path migration fails, and its child nodes also trigger RRC re-establishment.
  • the IAB-node and its sub-nodes can re-establish RRC almost at the same time, reducing the service interruption time caused by the path migration failure.
  • FIG. 11 is a schematic diagram of another message sending method on the second IAB-node side when the random access of the first IAB-node fails. As shown in FIG. 11 , the method includes:
  • the second IAB-node receives a third RRC reconfiguration message for path migration of the third IAB-node from the Donor-CU;
  • the second IAB-node receives the second RRC reconfiguration message for the path migration of the second IAB-node that is sent by the Donor-CU to the first IAB-node and forwarded by the first IAB-node;
  • the second IAB-node receives the path migration failure indication information sent when the first IAB-node fails to randomly access;
  • the second IAB-node rolls back to the original path configuration.
  • the implementations of the 1101 and 1103 are as described above, which will not be repeated here.
  • the first IAB-node sends the path migration failure indication information and a second RRC reconfiguration message to the second IAB-node, so that the second IAB-node falls back to the original path configuration; and The difference in the aforementioned FIG.
  • the second IAB-node does not perform RRC re-establishment, that is, although it receives the second RRC reconfiguration message, it does not perform the reconfiguration, but only performs the fallback to the original path configuration, Therefore, the first IAB-node does not optionally forward the second RRC reconfiguration message to the second IAB-node, but must forward the second RRC reconfiguration message, that is, 1102 is a mandatory step, otherwise, the packet data of the second IAB-node
  • the convergence protocol PDCP may be abnormal because the second RRC reconfiguration message is not received.
  • the method may further include: (not shown) forwarding the third RRC reconfiguration message from the second IAB-node to the third IAB-node, and the second IAB-node to the third IAB-node
  • the node forwards the path migration failure indication information received in 1103, so that the third IAB-node falls back to the original path configuration.
  • the specific implementation can refer to the side of the first IAB-node, which will not be repeated here.
  • the random access of the IAB-node switches to the new parent node fails, it triggers RRC re-establishment, forwards the RRC reconfiguration of its child node to the child node and indicates the path migration failure to its child node, so that the child node The node rolls back to the original path configuration.
  • the IAB-node migration fails, the IAB-node and its child nodes can fall back to the original path configuration at the same time. Otherwise, if the child node performs path migration and generates uplink data according to the new path configuration, the uplink data will be discarded and retransmitted by the UE, which will increase the uplink data transmission delay. This method can avoid the extension of data transmission time due to path migration failure.
  • This embodiment of the present application provides a method for sending a message, which is described from the Donor-CU side.
  • Figure 12 is a schematic diagram of the message sending method. As shown in Figure 12, the method includes:
  • the Donor-CU sends a second Radio Resource Control (RRC) reconfiguration message for the path migration of the second IAB-node to the first IAB-node, so that the first IAB-node will use the reconfiguration message when the random access succeeds.
  • RRC Radio Resource Control
  • the Donor-CU sends a first Radio Resource Control (RRC) reconfiguration message to the first IAB-node for path migration of the first IAB-node.
  • RRC Radio Resource Control
  • the method may further include:
  • the Donor-CU sends a third RRC reconfiguration message for the path migration of the third IAB-node to the second IAB-node.
  • the Donor-CU generates the first RRC reconfiguration message, the second RRC reconfiguration message, the third RRC reconfiguration message, the first RRC reconfiguration message, and the second RRC reconfiguration message , the content and structure included in the third RRC reconfiguration message and the implementation of the bearer may refer to the embodiments of the first aspect and the second aspect.
  • the first RRC reconfiguration message, the second RRC reconfiguration message Reconfiguration message, the third RRC reconfiguration message can be carried by a downlink message, that is, the Donor-CU simultaneously sends the first RRC reconfiguration message, the second RRC reconfiguration message, the third RRC reconfiguration message, or by The three downlink messages are respectively carried, that is, the Donor-CU sends the third RRC reconfiguration message, the second RRC reconfiguration message and the first RRC reconfiguration message successively, which will be described in detail in the following cases.
  • the behavior of the Donor-CU sending to the first IAB-node may be to send directly to the first IAB-node without passing through other relay nodes, or may be forwarded to the first IAB-node through the first parent node
  • the behavior of Donor-CU sending to the second IAB-node may be to send directly to the second IAB-node without going through other relay nodes, or it may be forwarded to the second IAB-node through the first parent node.
  • it is forwarded by the first IAB-node to the second IAB-node, which is not limited in this embodiment.
  • the method may also include:
  • the Donor-CU receives the first RRC reconfiguration complete message from the first IAB-node.
  • the Donor-CU may also receive a second RRC reconfiguration complete message from the second IAB-node, and receive a third RRC reconfiguration complete message from the third IAB-node, and the first RRC reconfiguration is complete.
  • the first RRC reconfiguration completion message, the second RRC reconfiguration complete message, the content and structure included in the third RRC reconfiguration complete message and the implementation of the bearer may refer to the embodiments of the first aspect and the second aspect, for example, the first RRC reconfiguration completion message, the second RRC reconfiguration complete message, the third RRC reconfiguration complete message may be carried by an uplink message, that is, the Donor-CU simultaneously receives the first RRC reconfiguration complete message and the second RRC reconfiguration complete message, The third RRC reconfiguration complete message may be carried by three downlink messages respectively, that is, the Donor-CU successively receives the third RRC reconfiguration complete message, the second RRC reconfiguration complete message and the first RRC reconfiguration complete message.
  • the above-mentioned Donor-CU can receive the RRC reconfiguration complete message directly sent by the first IAB-node or the second IAB-node or the third IAB-node, or can also receive the first IAB-node or the second IAB-node or the third IAB -
  • the RRC reconfiguration complete message sent by the node and forwarded by the node will be described in detail in the following sections.
  • the first RRC reconfiguration message and the second RRC reconfiguration message may be carried by one downlink message, or may be carried by two downlink messages respectively, which will be described below.
  • Implementation scenario 1 The above RRC reconfiguration message is carried by two downlink messages respectively, and the difference from the existing method is that the signaling carrying the second RRC reconfiguration message is the same as the signaling carrying the first RRC reconfiguration message. sent before.
  • the RRC reconfiguration message sent by the Donor-CU for its child node has been sent to the first IAB-node, and is sent to the first IAB-node by the first IAB-node.
  • An IAB-node caches and forwards it until it switches to the second parent node. Thereby, the first IAB-node and its sub-nodes can simultaneously update the network topology.
  • FIG. 13 is a schematic diagram of the message sending method. As shown in FIG. 13 , the method includes:
  • the Donor-CU sends a second Radio Resource Control (RRC) reconfiguration message to the first IAB-node for path migration of the second IAB-node;
  • RRC Radio Resource Control
  • the Donor-CU sends a first radio resource control (RRC) reconfiguration message for the first IAB-node path migration to the first parent node;
  • RRC radio resource control
  • the first parent node forwards the first RRC reconfiguration message to the first IAB-node;
  • the first IAB-node performs random access to the second parent node
  • the first IAB-node forwards the second RRC reconfiguration message to the second IAB-node;
  • the method may further include:
  • the Donor-CU sends a third RRC reconfiguration message for the path migration of the third IAB-node to the second IAB-node;
  • the second RRC reconfiguration message is carried by the first downlink F1AP message, and the distribution unit (DU) of the first IAB-node receives the first downlink F1AP sent by the Donor-CU message, thereby receiving the second RRC reconfiguration message carried in the first downlink F1AP message.
  • the first downlink F1AP message also includes first buffer indication information; the first buffer indication information is used to indicate the The first IAB-node caches the second RRC reconfiguration message until it receives the first indication information described later and releases it.
  • the first downlink F1AP message may be a UE context modification request message.
  • the first RRC reconfiguration message is carried by a downlink F1AP message sent by the Donor-CU to the first parent node, and the downlink F1AP message is sent by the first parent node to the downlink F1AP message.
  • the first RRC reconfiguration message in is forwarded to the first IAB-node.
  • the F1AP message may be a UE context modification request message.
  • the above-mentioned downlink F1AP message may also include the above-mentioned first context identifier of the UE, etc., and the specific reference may be made to the prior art, which will not be repeated here.
  • the first IAB-node performs a random access process. For this implementation, reference may be made to the prior art, which will not be repeated here.
  • the random access is successful, that is, after the MT (MAC layer) of the first IAB-node completes the random access to the second parent node, in 1305, the first IAB-node sends the second RRC reconfiguration message to the second parent node. Forwarded to the second IAB-node.
  • the first indication information is sent to the distribution unit (DU) of the first IAB-node; the distribution unit (DU) of the first IAB-node DU) forwards the second RRC reconfiguration message to the second IAB-node when receiving the first indication information.
  • the first RRC reconfiguration message includes the first parameter for changing the transmission path configuration for the first IAB-node and/or includes the first path relocation indication information, it indicates that the first RRC reconfiguration message is used for the first IAB-node.
  • a path relocation of an IAB-node the MT of the first IAB-node sends first indication information to the DU of the first IAB-node, the meaning of the first parameter and/or the first path relocation indication information, please refer to the first aspect embodiment, which will not be repeated here.
  • the first RRC reconfiguration message further includes configuration information of the first indication information; the configuration information of the first indication information is used to indicate that the MT of the first IAB-node can, when the random access succeeds, Send the first indication information to the distribution unit (DU) of the first IAB-node.
  • the configuration information of the first indication information is used to indicate that the MT of the first IAB-node can, when the random access succeeds, Send the first indication information to the distribution unit (DU) of the first IAB-node.
  • the MT of the first IAB-node sends the first indication information to the DU of the first IAB-node; or, the first RRC reconfiguration message
  • the configuration message includes the first parameter and/or the first path relocation indication information, and the configuration information including the first indication information
  • the MT of the first IAB-node sends the first IAB-node to the DU of the first IAB-node. an instruction message.
  • the first downlink F1AP message further includes the aforementioned first buffer indication information
  • the second RRC reconfiguration message is forwarded to the second IAB-node.
  • the aforementioned first indication information, the configuration information of the first indication information, the first cache indication information, the first path migration indication information, etc. may be the newly added information element IE in the message, and its value may be a default value,
  • the embodiments of the present application are not limited thereto.
  • the third RRC reconfiguration message is carried by the second downlink F1AP message, and the distribution unit (DU) of the second IAB-node receives the Donor - the second downlink F1AP message sent by the CU, thereby receiving the third RRC reconfiguration message carried in the second downlink F1AP message, for example, the second downlink F1AP message also includes second buffer indication information; the second buffer The indication information is used to instruct the second IAB-node to buffer the third RRC reconfiguration message until it is released after receiving the second indication information.
  • the second IAB-node when the second IAB-node receives the second RRC reconfiguration message forwarded by the first IAB-node in 1306, the second IAB-node forwards the third RRC reconfiguration message to the first IAB-node
  • the mobile terminal (MT) of the second IAB-node when it sends second indication information to the distribution unit (DU) of the second IAB-node;
  • the distribution unit (DU) of the second IAB-node forwards the third RRC reconfiguration message to the third IAB-node.
  • the second RRC reconfiguration message when the second RRC reconfiguration message includes the second parameter for changing the transmission path configuration for the second IAB-node and/or includes the second path migration indication information, it indicates that the second RRC reconfiguration message is used for the second IAB-node.
  • the MT of the second IAB-node sends second indication information to the DU of the second IAB-node, the meaning of the second parameter and/or the second path relocation indication information, please refer to the second aspect
  • the structure and content of the third RRC reconfiguration message please refer to the embodiment of the second aspect, which will not be repeated here.
  • the second RRC reconfiguration message further includes configuration information of the second indication information; the configuration information of the second indication information is used to indicate that the second IAB-node can receive the second RRC reconfiguration message, the second indication information is sent to the distribution unit (DU) of the second IAB-node.
  • the MT of the second IAB-node sends the second indication information to the DU of the second IAB-node; or, the second RRC reconfiguration message
  • the configuration message includes the second parameter and/or the second path relocation indication information, and the configuration information including the second indication information
  • the MT of the second IAB-node sends the second IAB-node to the DU of the second IAB-node.
  • the second downlink F1AP message further includes the foregoing second buffer indication information
  • the third The RRC reconfiguration message is forwarded to the third IAB-node.
  • the aforementioned second indication information, the configuration information of the second indication information, the second cache indication information, the second path migration indication information, etc. may be the newly added information element IE in the message, and its value may be a default value,
  • the embodiments of the present application are not limited thereto.
  • the method further includes:
  • the first IAB-node sends a first RRC reconfiguration complete message to the Donor-CU;
  • the first IAB-node receives the second RRC reconfiguration complete message sent by the second IAB-node;
  • the first IAB-node forwards the second RRC reconfiguration complete message to the Donor-CU;
  • the second IAB-node receives the third RRC reconfiguration complete message sent by the third IAB-node;
  • the second IAB-node forwards the third RRC reconfiguration complete message to the Donor-CU.
  • the first IAB-node after the first IAB-node reconfiguration is completed, the first IAB-node sends the first RRC reconfiguration complete message to the second parent node, and the second parent node sends the first RRC reconfiguration complete message to the second parent node.
  • An RRC reconfiguration complete message is forwarded to the Donor-CU, wherein the second parent node may send an uplink F1AP message to the Donor-CU, and the uplink F1AP message carries the first RRC reconfiguration complete message.
  • the second parent node may send an uplink F1AP message to the Donor-CU
  • the uplink F1AP message carries the first RRC reconfiguration complete message.
  • the second IAB-node sends the second RRC reconfiguration complete message to the first IAB-node, the first IAB-node
  • the node forwards the second RRC reconfiguration complete message to the Donor-CU, where the first IAB-node may send the first uplink F1AP message to the Donor-CU, and the first uplink F1AP message carries the second RRC reconfiguration Done message.
  • the third IAB-node after the third IAB-node reconfiguration is complete, the third IAB-node sends the third RRC reconfiguration complete message to the second IAB-node, the second IAB-node The node forwards the third RRC reconfiguration complete message to the Donor-CU, where the second IAB-node may send a second uplink F1AP message to the Donor-CU, and the second uplink F1AP message carries the third RRC reconfiguration Done message.
  • FIG. 14 is a schematic diagram of the message sending method. As shown in FIG. 14 , the method includes:
  • the Donor-CU sends a third RRC reconfiguration message for the path migration of the third IAB-node to the second IAB-node;
  • the Donor-CU sends a second wireless RRC reconfiguration message to the first IAB-node for path migration of the second IAB-node;
  • the Donor-CU sends a first wireless RRC reconfiguration message for the first IAB-node path migration to the first parent node;
  • the first parent node forwards the first RRC reconfiguration message to the first IAB-node
  • the first IAB-node performs random access to the second parent node
  • the method may also include:
  • the first IAB-node triggers an RRC re-establishment process
  • the first IAB-node sends path migration failure indication information to the second IAB-node.
  • the first IAB-node forwards the second RRC reconfiguration message to the second IAB-node, or clears the second RRC reconfiguration message.
  • the second IAB-node triggers an RRC re-establishment process when receiving the path migration failure indication information
  • the method may further include:
  • the second IAB-node forwards the path migration failure indication information to the third IAB-node;
  • the second IAB-node forwards the third RRC reconfiguration message to the third IAB-node, or clears the third RRC reconfiguration message.
  • the RRC re-establishment process may refer to the prior art, and the implementation of 1406 may refer to the second aspect 1002 of the embodiment is not repeated here.
  • the first IAB-node when the first RRC reconfiguration message includes first parameters and/or first path relocation indication information for changing transmission path configuration for the first IAB-node, the first IAB-node The node sends the path migration failure indication information to the second IAB-node.
  • the first RRC reconfiguration message further includes configuration information of the path relocation failure indication information, where the configuration information of the path relocation failure indication information is used to indicate that the first IAB-node can, when random access fails, Send path migration failure indication information to the second IAB-node.
  • the first IAB-node when the random access of the first IAB-node fails, if the first RRC reconfiguration message contains the configuration information of the path relocation failure indication information, the first IAB-node sends the path relocation failure indication information to the second IAB-node , or, if the first RRC reconfiguration message contains the first parameter and/or the first path relocation indication information, and the configuration information of the path relocation failure indication information, the first IAB-node sends the second IAB-node the Path migration failure indication information.
  • the first IAB-node forwards the second RRC reconfiguration message to the second IAB-node, or clears the second RRC reconfiguration message.
  • This step is optional, and the embodiments of the present application are not limited thereto.
  • the implementations of 1409-1411 are similar to those of 1406-1408, and details are not repeated here.
  • FIG. 15 is a schematic diagram of the message sending method. As shown in FIG. 15 , the method includes:
  • the Donor-CU sends a third RRC reconfiguration message for the path migration of the third IAB-node to the second IAB-node;
  • the Donor-CU sends a second RRC reconfiguration message for the path migration of the second IAB-node to the first IAB-node;
  • the Donor-CU sends a first RRC reconfiguration message for the first IAB-node path migration to the first parent node;
  • the first parent node forwards the first RRC reconfiguration message to the first IAB-node;
  • the first IAB-node performs random access to the second parent node
  • the first IAB-node triggers an RRC re-establishment process
  • the first IAB-node sends path migration failure indication information to the second IAB-node;
  • the first IAB-node forwards the second RRC reconfiguration message to the second IAB-node.
  • the second IAB-node When receiving the path migration failure indication information and the second RRC reconfiguration message, the second IAB-node does not perform the RRC re-establishment process, but falls back to the original path configuration.
  • the second IAB-node forwards the path migration failure indication information to the third IAB-node;
  • the second IAB-node forwards the third RRC reconfiguration message to the third IAB-node;
  • the third IAB-node when receiving the path migration failure indication information and the third RRC reconfiguration message, the third IAB-node does not perform the RRC re-establishment process, but falls back to the original path configuration.
  • the difference from FIG. 14 is that the first IAB-node is not optional to forward the second RRC reconfiguration message to the second IAB-node, but must forward it, that is, 1507 is mandatory step, otherwise, the packet data convergence protocol PDCP of the second IAB-node will be abnormal.
  • the first IAB-node forwards the second RRC reconfiguration message, reference may be made to the above 1305, and details are not repeated here.
  • Implementation scenario 2 The difference from implementation scenario 1 is that each of the above RRC reconfiguration messages is carried by one downlink message, thereby not only reducing service interruption time, but also saving signaling overhead.
  • FIG. 16 is a schematic diagram of the message sending method. As shown in FIG. 16 , the method includes:
  • the Donor-CU sends a first RRC reconfiguration message for the first IAB-node path migration and a second RRC reconfiguration message for the second IAB-node path migration to the first parent node;
  • the first parent node forwards the first RRC reconfiguration message and the second RRC reconfiguration message to the first IAB-node;
  • the first IAB-node performs random access to the second parent node
  • the first IAB-node forwards the second RRC reconfiguration message to the second IAB-node;
  • the method may further include:
  • the Donor-CU sends a third RRC reconfiguration message for the third IAB-node path migration to the first parent node; in 1602, the first parent node also forwards the third RRC reconfiguration message to the The first IAB-node, in 1604, the first IAB-node also forwards the third RRC reconfiguration message to the second IAB-node;
  • the second IAB-node receives the second RRC reconfiguration message and the third RRC reconfiguration message, forward the third RRC reconfiguration message to the third IAB-node.
  • the second RRC reconfiguration message is carried by the first RRC reconfiguration message, and the third RRC reconfiguration message is included in the second RRC reconfiguration message.
  • the content of the information element contained in each RRC reconfiguration message is as described above, and will not be repeated here.
  • the Donor-CU carries the above-mentioned first RRC reconfiguration message, second RRC reconfiguration message, and third RRC reconfiguration message in one downlink F1AP message.
  • the downlink F1AP message may be UE context modification Request message (UE CONTEXT SETUP REQUEST).
  • UE CONTEXT SETUP REQUEST may also include the first context identifier of the above-mentioned UE, etc. For details, reference may be made to the prior art, which will not be repeated here.
  • Figure 19A is a schematic diagram of the structure of the downlink F1AP message.
  • the first RRC reconfiguration message is carried by the downlink F1AP message sent by the Donor-CU to the first parent node, and the second RRC reconfiguration message is included in the first RRC reconfiguration message.
  • the third RRC reconfiguration message is included in the second RRC reconfiguration message.
  • the first RRC reconfiguration message further includes identification information of the second IAB-node.
  • the identification information is the cell identification of the parent node of the second IAB-node (for example, the DU cell identification of the first IAB-node) and the cell radio network temporary identification C-RNTI of the second IAB-node in the parent cell (for example, the second IAB-node).
  • the CNTI of the MT of the IAB-node in the DU cell of the first IAB-node), or the identification information is the UE F1AP identification of the second IAB-node in its parent node (for example, the MT of the second IAB-node is in the first DU UE F1AP ID in DU of IAB-node).
  • the second RRC reconfiguration message also includes identification information of the third IAB-node, where the identification information is the parent cell identification of the third IAB-node (for example, the DU cell identification of the second IAB-node) and the first The cell wireless network temporary identification C-RNTI of the third IAB-node in the parent cell (for example, the CNTI of the MT of the third IAB-node in the DU cell of the second IAB-node), or the identification information is the third IAB- The UE F1AP ID of the node in its parent node (for example, the DU UE F1AP ID of the MT of the third IAB-node in the DU of the second IAB-node).
  • the identification information is the parent cell identification of the third IAB-node (for example, the DU cell identification of the second IAB-node) and the first The cell wireless network temporary identification C-RNTI of the third IAB-node in the parent cell (for example,
  • the first parent node after receiving the F1AP message, the first parent node sends the first RRC reconfiguration message therein to the first IAB-node, and in 1604 and 1605, the first IAB-node reconfigures from the first RRC
  • the second RRC reconfiguration message is extracted from the message and forwarded to the second IAB-node.
  • the second IAB-node extracts the third RRC reconfiguration message from it and forwards it to the third IAB-node. .
  • the second RRC reconfiguration message is sent to the DU of the first IAB-node, and then forwarded to the second IAB-node.
  • the first RRC reconfiguration message includes the first parameter for changing the transmission path configuration for the first IAB-node and/or includes the first path relocation indication information, it indicates that the first RRC reconfiguration message is used for the first IAB-node.
  • a path relocation of an IAB-node the MT of the first IAB-node sends a second RRC reconfiguration message to the DU of the first IAB-node, the meaning of the first parameter and/or the first path relocation indication information, please refer to Section Embodiments of one aspect are not repeated here.
  • the mobile terminal (MT) of the second IAB-node receives the second RRC reconfiguration message, it sends the third RRC reconfiguration message to the DU of the second IAB-node, and then forwards it to the third IAB-node.
  • the second RRC reconfiguration message when the second RRC reconfiguration message includes the second parameter for changing the transmission path configuration for the second IAB-node and/or includes the second path migration indication information, it indicates that the second RRC reconfiguration message is used for the second IAB-node.
  • the MT of the second IAB-node sends a third RRC reconfiguration message to the DU of the second IAB-node, the meaning of the second parameter and/or the second path migration indication information, please refer to Section The embodiments of the second aspect will not be repeated here.
  • the third RRC reconfiguration message is used for the path migration of the third IAB-node, so the third RRC reconfiguration message includes the third parameter for changing the transmission path configuration for the third IAB-node, the third IAB-node After the node receives the third RRC configuration message, it can perform path migration.
  • the third parameter is similar to that of the first parameter, and details are not repeated here.
  • the third RRC reconfiguration message may further include a fourth RRC reconfiguration message for path migration of its child nodes, the third IAB-node
  • the node receives the third RRC reconfiguration message, it forwards the fourth RRC reconfiguration message to its child node, and the specific forwarding implementation is the same as that of the second IAB-node, which is not repeated here.
  • the Donor-CU does not need to send a downlink F1AP message for the first IAB-node, the second IAB-node and the third IAB-node respectively, which saves signaling overhead, and through layer-by-layer message forwarding, the first IAB-node , the second IAB-node and the third IAB-node can receive their respective RRC reconfiguration messages almost simultaneously.
  • the first IAB-node performs message forwarding when the random access succeeds (and the second parent node succeeds in random access), so that the first IAB-node, the second IAB-node and the third IAB-node can be divided at the same time. Update the network topology to reduce service interruption time.
  • the method may further include:
  • the first IAB-node sends a first RRC reconfiguration complete message to the Donor-CU;
  • the first IAB-node receives the second RRC reconfiguration complete message sent by the second IAB-node;
  • the first IAB-node forwards the second RRC reconfiguration complete message to the Donor-CU;
  • the second IAB-node receives the third RRC reconfiguration complete message sent by the third IAB-node;
  • the second IAB-node forwards the third RRC reconfiguration complete message to the Donor-CU.
  • Fig. 17 is another schematic diagram of a message sending method.
  • the difference from Fig. 16 is that the RRC reconfiguration complete message of each IAB-node is not sent through different upstream messages, but is sent by the second parent node through the same upstream F1AP The message is carried and sent to the Donor-CU, thereby further reducing signaling overhead.
  • the method includes: operations 1701-1705 that are the same as operations 1601-1605 in FIG. 16 , in addition, the method may further include:
  • the second IAB-node receives the third RRC reconfiguration complete message sent by the third IAB-node;
  • the first IAB-node receives the second RRC reconfiguration complete message sent by the second IAB-node;
  • the first IAB-node sends a first RRC reconfiguration complete message to the second parent node;
  • the second parent node forwards the first RRC reconfiguration complete message to the Donor-CU.
  • the second IAB-node includes the third RRC reconfiguration complete message in the second RRC reconfiguration complete message and sends to the first IAB-node
  • the first IAB -The node includes the second RRC reconfiguration complete message in the first RRC reconfiguration complete message and sends it to the second parent node
  • the second parent node sends an uplink F1AP message to the Donor-CU
  • the uplink F1AP message carries the first RRC reconfiguration complete message.
  • An RRC reconfiguration complete message is an RRC reconfiguration complete message.
  • FIG. 19B is a schematic diagram of the structure of the uplink F1AP message.
  • the first RRC reconfiguration complete message is carried by the uplink F1AP message sent by the second parent node to the Donor-CU, and the second RRC reconfiguration complete message is included in the first RRC reconfiguration complete message.
  • the third RRC reconfiguration complete message is included in the second RRC reconfiguration complete message.
  • the first RRC reconfiguration complete message further includes identification information of the second IAB-node.
  • the second RRC reconfiguration complete message also includes the identification information of the third IAB-node, and the identification information is as described above and will not be repeated here.
  • the third IAB-node completes the RRC reconfiguration, sends a third RRC reconfiguration complete message to the second IAB-node and performs F1 transmission path migration;
  • the second IAB-node receives The third RRC reconfiguration complete message completes its own RRC reconfiguration, and the third RRC reconfiguration complete message is included in the second RRC reconfiguration complete message and sent to the first IAB-node to implement F1 transmission path migration;
  • the first IAB -The node receives the second RRC reconfiguration complete message, completes its own RRC reconfiguration, includes the second RRC reconfiguration complete message in the first RRC reconfiguration complete message and sends it to its second parent node, and implements the F1 transmission path Migration, the second parent node sends the first RRC reconfiguration complete message to the Donor-CU through an uplink F1AP message.
  • the uplink RRC messages of IAB-node and its child nodes are carried by F1AP and transmitted by the backhaul RLC channel (that is, forwarded by the BAP layer), so there is no need to wait for the RRC reconfiguration completion message of the child node to be sent before sending its own RRC reconfiguration complete message, therefore, in order to carry the RRC reconfiguration complete message of each IAB node through an uplink F1AP message, the first RRC reconfiguration message may further include completion message sending timing configuration information, the completion message sending timing configuration information Used to instruct the first IAB-node to send its own RRC reconfiguration complete message after receiving the RRC reconfiguration complete message sent by the child node
  • the first RRC reconfiguration complete message sent by the first IAB-node is the first uplink data sent by the first IAB-node using the new F1 transmission path.
  • the first IAB-node cannot send the first RRC reconfiguration complete message until it receives the second RRC reconfiguration complete message. Therefore, the first IAB-node starts from receiving the first RRC reconfiguration message to sending the first RRC reconfiguration complete message. During this period no other upstream data should be sent using the new F1 transmission path.
  • the first IAB-node when the first IAB-node receives the first RRC reconfiguration message, it suspends all uplink transmissions (including scheduling requests and buffer status reports), including the transmission of data radio bearers and BH RLC channels, and sends the first RRC After the reconfiguration complete message, resume the transmission of the data radio bearer and the BH RLC channel, or resume the uplink transmission after receiving the second RRC reconfiguration complete message.
  • the priority of the RRC signaling message is higher than the data priority. , after the uplink transmission is resumed, it can ensure that the first RRC reconfiguration complete message is sent preferentially.
  • 16-17 show the information exchange of each IAB-node when the random access of the first IAB-node succeeds.
  • the method may further include: implementing the first IAB-node random access. 1405-1411 or 1505-1511, the repetition will not be repeated.
  • Implementation scenario 3 The difference from implementation scenario 2 is that the message structure of the downlink F1AP message sent by the Donor-CU to the first parent node is different.
  • FIG. 20A is a schematic diagram of the structure of the downlink F1AP message.
  • the downlink F1AP message carries the first RRC reconfiguration message, and the first RRC reconfiguration message includes the Donor-CU send message.
  • the third downlink F1AP message to the first IAB-node, the second RRC reconfiguration message is carried by the third downlink F1AP message, and the second RRC reconfiguration message includes the first IAB-node sent by the Donor-CU to the second IAB-node.
  • Four downlink F1AP messages, and the third RRC reconfiguration message is carried by the fourth downlink F1AP message.
  • the third downlink F1AP message also includes the identification information of the second IAB-node (for example, the DU UE F1AP ID of the second IAB-node), and the fourth downlink F1AP message also includes the identification information of the third IAB-node (for example, DU UE F1AP ID of the third IAB-node).
  • FIG. 18 is a schematic diagram of the message sending method. As shown in FIG. 18 , the method includes:
  • the Donor-CU sends a downlink F1AP message with the structure shown in Figure 20A to the first parent node;
  • the first parent node extracts the first RRC reconfiguration message and forwards it to the MT of the first IAB-node;
  • the first IAB-node performs random access to the second parent node
  • the MT of the first IAB-node extracts the third downlink F1AP message from the first RRC reconfiguration message, and sends the third downlink F1AP message to the DU of the first IAB-node;
  • the DU of the first IAB-node forwards the second RRC reconfiguration message in the third downlink F1AP message to the MT of the second IAB-node;
  • the MT of the second IAB-node extracts the fourth downlink F1AP message from the second RRC reconfiguration message, and sends the fourth downlink F1AP message to the DU of the second IAB-node;
  • the DU of the second IAB-node forwards the third RRC reconfiguration message in the fourth downlink F1AP message to the MT of the third IAB-node;
  • the first RRC reconfiguration message when the first RRC reconfiguration message includes a first parameter for changing the transmission path configuration for the first IAB-node and/or includes first path relocation indication information, it indicates that the first RRC reconfiguration message
  • the RRC reconfiguration message is used for the path migration of the first IAB-node.
  • the MT of the first IAB-node extracts the third downlink F1AP message from the first RRC reconfiguration message, and sends the third downlink F1AP message to the DU of the first IAB-node.
  • the meaning of the first parameter and/or the first path relocation indication information please refer to the embodiment of the first aspect, which will not be repeated here.
  • the second RRC reconfiguration message when the second RRC reconfiguration message includes a second parameter for changing the transmission path configuration for the second IAB-node and/or includes second path relocation indication information, it indicates that the second RRC reconfiguration message is for During the path migration of the second IAB-node, the MT of the second IAB-node extracts the fourth downlink F1AP message from the second RRC reconfiguration message, and sends the fourth downlink F1AP message to the DU of the second IAB-node,
  • the second parameter and/or the second path migration indication information please refer to the embodiment of the second aspect, and details are not repeated here.
  • the third RRC reconfiguration message is used for the path migration of the third IAB-node, so the third RRC reconfiguration message includes the third parameter for changing the transmission path configuration for the third IAB-node, the third IAB-node After the node receives the third RRC configuration message, it can perform path migration.
  • the third parameter is similar to that of the first parameter, which will not be repeated here.
  • the third RRC reconfiguration message may further include a fifth downlink F1AP message, and the fifth downlink F1AP message includes path migration for its child nodes
  • the fourth RRC reconfiguration message the third IAB-node forwards the fourth RRC reconfiguration message to its child node when receiving the third RRC reconfiguration message, and the specific forwarding implementation is the same as that of the second IAB-node.
  • the nodes are the same and will not be repeated here.
  • the third IAB-node performs path migration after receiving the third RRC reconfiguration message, and does not need to perform a forwarding action. For details, reference may be made to the prior art, which will not be repeated here.
  • the Donor-CU does not need to send a downlink F1AP message for the first IAB-node, the second IAB-node and the third IAB-node respectively, which saves signaling overhead, and through layer-by-layer message forwarding, the first IAB-node,
  • the second IAB-node and the third IAB-node can receive their respective RRC reconfiguration messages almost simultaneously.
  • the first IAB-node performs message forwarding when the random access succeeds (and the second parent node succeeds in random access), so that the first IAB-node, the second IAB-node and the third IAB-node can be divided at the same time. Update the network topology to reduce service interruption time.
  • the downlink F1AP message in FIG. 20A may be a UE CONTEXT SETUP REQUEST message.
  • the above-mentioned UE CONTEXT SETUP REQUEST may also include topology-related reconfiguration information for the BH RLC channel reconfiguration of the first IAB-node, and the reconfiguration information includes: return RLC channel mapping relationship reconfiguration information, and/or the first IAB-node. Return RLC channel modification information between an IAB-node and its child nodes.
  • the returned RLC channel mapping relationship reconfiguration information refers to the mapping relationship between the BH RLC channel between the first IAB-node and the second IAB-node and the BH RLC channel between the first IAB-node and the second parent node
  • the return RLC channel modification information refers to the addition, modification and deletion related information of the BH RLC channel between the first IAB-node and the second IAB-node, for example, modifying the related information includes modifying the quality of service QoS of the BH RLC channel parameter.
  • the difference between this embodiment and the second implementation scenario is that the message structure of the uplink F1AP message sent by the second parent node to the Donor-CU is different.
  • FIG. 20B is a schematic diagram of the structure of the uplink F1AP message, as shown in FIG. As shown in FIG.
  • the third RRC reconfiguration complete message is carried by the fourth uplink F1AP message of the second IAB-node
  • the fourth uplink F1AP message is carried by the second RRC reconfiguration complete message
  • the second RRC reconfiguration complete message is carried by
  • the third uplink F1AP message of the first IAB-node is carried
  • the third uplink F1AP message is carried by the first RRC reconfiguration complete message
  • the first RRC reconfiguration complete message is included in the uplink F1AP message sent by the second parent node to the Donor-CU (eg UL RRC MESSAGE TRNASFOR).
  • the third upstream F1AP message includes identification information of the second IAB-node
  • the fourth upstream F1AP message includes identification information of the third IAB-node.
  • the implementation of the identification information is consistent with the identification information in the downlink F1AP message. It is not repeated here.
  • the method may further include:
  • the DU of the second IAB-node receives the third RRC reconfiguration complete message sent by the MT of the third IAB-node;
  • the DU of the second IAB-node includes the third RRC reconfiguration complete message in the fourth uplink F1AP message and sends it to the MT of the second IAB-node;
  • the MT of the first IAB-node includes the fourth uplink F1AP message in the second RRC reconfiguration complete message and sends the DU to the first IAB-node;
  • the DU of the first IAB-node includes the second RRC reconfiguration complete message in the third uplink F1AP message and sends it to the MT of the first IAB-node;
  • the MT of the first IAB-node includes the third uplink F1AP message in the first RRC reconfiguration complete message and sends it to the second parent node;
  • the second parent node sends an uplink F1AP message (eg, UL RRC MESSAGE TRNASFOR) to the Donor-CU, where the uplink F1AP message includes the first RRC reconfiguration complete message.
  • an uplink F1AP message eg, UL RRC MESSAGE TRNASFOR
  • the third IAB-node completes the RRC reconfiguration, sends a third RRC reconfiguration complete message to the second IAB-node and performs F1 transmission path migration;
  • the second IAB-node receives The third RRC reconfiguration complete message completes its own RRC reconfiguration, the third RRC reconfiguration complete message is included in the fourth uplink F1AP message, and the fourth F1AP message is included in the second RRC reconfiguration complete message to send Give the first IAB-node and implement F1 transmission path migration;
  • the first IAB-node receives the second RRC reconfiguration complete message, completes its own RRC reconfiguration, and includes the second RRC reconfiguration complete message in the third uplink F1AP message , and include the third F1AP message in the first RRC reconfiguration complete message and send it to its second parent node, and implement F1 transmission path migration, the second parent node carries the first RRC reconfiguration through an uplink F1AP message Completion message is sent to Donor-
  • the uplink RRC messages of IAB-node and its child nodes are carried by F1AP and transmitted by the backhaul RLC channel (that is, forwarded by the BAP layer), so there is no need to wait for the RRC reconfiguration completion message of the child node to be sent before sending its own RRC reconfiguration complete message, therefore, in order to carry the RRC reconfiguration complete message of each IAB node through an uplink F1AP message, the first RRC reconfiguration message may further include a completion message sending timing configuration message, the completion message sending timing configuration message Used to instruct the first IAB-node to send its own RRC reconfiguration complete message after receiving the RRC reconfiguration complete message sent by the child node
  • the first RRC reconfiguration complete message sent by the first IAB-node is the first uplink data sent by the first IAB-node using the new F1 transmission path.
  • the first IAB-node cannot send the first RRC reconfiguration complete message until it receives the second RRC reconfiguration complete message. Therefore, the first IAB-node starts from receiving the first RRC reconfiguration message to sending the first RRC reconfiguration complete message. During this period no other upstream data should be sent using the new F1 transmission path.
  • the first IAB-node when the first IAB-node receives the first RRC reconfiguration message, it suspends all uplink transmissions (including scheduling requests and buffer status reports), including the transmission of data radio bearers and BH RLC channels, and after sending the first RRC reconfiguration message After the RRC reconfiguration complete message, the transmission of the data radio bearer and the BH RLC channel is resumed, or after the second RRC reconfiguration complete message is received, the uplink transmission is resumed. At this time, the priority of the RRC signaling message is higher than the data priority. level, after the uplink transmission is resumed, the first RRC reconfiguration complete message can be guaranteed to be sent first.
  • the method may further include: implementing 1405- 1411 or 1505-1511, the repetition will not be repeated.
  • An embodiment of the present application provides a message sending apparatus.
  • FIG. 21 is a schematic diagram of an apparatus for sending a message according to an embodiment of the present application.
  • the apparatus may be, for example, an IAB node in an IAB system, or one or some components or components configured in the IAB node.
  • the IAB system includes a Donor device and an IAB node, and the embodiments of this application are described from the side of the first IAB-node.
  • the implementation principle of the message sending apparatus of the embodiment of the present application is similar to that of the embodiment of the first aspect, and the same content is not repeated.
  • the message sending apparatus 2100 in the embodiment of the present application includes:
  • the first receiving unit 2101 which receives a second Radio Resource Control (RRC) reconfiguration message for the second IAB-node path migration from the Donor-CU; wherein, the second IAB-node is the The downstream child node of the first IAB-node;
  • RRC Radio Resource Control
  • a second receiving unit 2102 which receives a first RRC reconfiguration message for the first IAB-node path migration from the Donor-CU;
  • the first sending unit 2103 which forwards the second RRC reconfiguration message to the second IAB-node when the random access of the first IAB-node succeeds.
  • the first receiving unit 2101, the second receiving unit 2102, and the first sending unit 2103 please refer to 801-803 in the embodiments of the first aspect and the first IAB-node in the first to third implementation scenarios implementation, and the repeated places will not be repeated.
  • the second RRC reconfiguration message is carried by the first downlink F1AP message sent by the Donor-CU.
  • the first sending unit 2103 includes a first sending module and a second sending module not shown; when the random access of the mobile terminal (MT) of the first IAB-node is successful, the first sending module Send the first indication information to the distribution unit (DU) of the first IAB-node; when the distribution unit (DU) of the first IAB-node receives the first indication information, the second sending module replays the second RRC The configuration message is forwarded to the second IAB-node.
  • the first sending module on the MT of the first IAB-node sends a message to the first IAB-node.
  • a DU of an IAB-node sends the first indication information.
  • the first parameter configured for the first IAB-node to change the transmission path includes a default backhaul RLC channel, a default BAP route or an IP address configured for the first IAB-node.
  • the first sending module on the MT of the first IAB-node sends the first sending module to the DU of the first IAB-node Indication information; the first path relocation indication information is used to indicate that the first RRC reconfiguration message is a reconfiguration message for the first IAB-node to perform path relocation.
  • the first RRC reconfiguration message further includes configuration information of the first indication information; the configuration information of the first indication information is used to indicate that the MT of the first IAB-node succeeds in random access , the first sending module sends the first indication information to the distribution unit (DU) of the first IAB-node.
  • the configuration information of the first indication information is used to indicate that the MT of the first IAB-node succeeds in random access
  • the first sending module sends the first indication information to the distribution unit (DU) of the first IAB-node.
  • the first downlink F1AP message further includes first buffer indication information; the first buffer indication information is used to instruct the first IAB-node to buffer the second RRC reconfiguration message until received Release after the first indication information.
  • the second RRC reconfiguration message is carried by the first RRC reconfiguration message.
  • the first RRC reconfiguration message further includes identification information of the second IAB-node.
  • the second RRC reconfiguration message is carried by a third downlink F1AP message from the Donor-CU, and the third downlink F1AP message is carried by the first RRC reconfiguration message.
  • the third downlink F1AP message further includes identification information of the second IAB-node.
  • the first sending unit 2103 includes a third sending module and a fourth sending module (not shown); when the MT of the first IAB-node succeeds in random access, the third sending module sends a message to the first IAB-node.
  • a DU of an IAB-node sends the third downlink F1AP message; when the DU of the first IAB-node receives the third downlink F1AP message, the fourth sending module resets the second RRC in the third downlink F1AP message
  • the configuration message is forwarded to the second IAB-node.
  • the first sending unit 2103 when random access to the first IAB-node fails, the first sending unit 2103 further sends path migration failure indication information to the second IAB-node.
  • the apparatus further includes: a first processing unit not shown, configured to forward the second RRC reconfiguration message to the second IAB-node, or clear the second RRC reconfiguration message Configuration messages.
  • the first sending unit 2103 when the first RRC reconfiguration message includes the first parameter and/or the first path relocation indication information for changing the transmission path configuration for the first IAB-node, the first sending unit 2103 sends a message to the first IAB-node. 2.
  • the IAB-node sends the path migration failure indication information.
  • the first RRC reconfiguration message further includes configuration information of the path relocation failure indication information, and the configuration information of the path relocation failure indication information is used to indicate that the first IAB-node fails in random access. , sending path migration failure indication information to the second IAB-node.
  • the apparatus when the random access of the first IAB-node succeeds, the apparatus further includes: a second sending unit 2104 and a third receiving unit 2105 (optional); the second sending unit 2104 sends a message to the The Donor-CU sends the first RRC reconfiguration complete message; the third receiving unit 2105 receives the second RRC reconfiguration complete message sent by the second IAB-node.
  • the second sending unit 2104 forwards the second RRC reconfiguration complete message to the Donor-CU, where the second RRC reconfiguration complete message is carried by the first uplink F1AP message.
  • the second sending unit 2104 includes the second RRC reconfiguration complete message in the first RRC reconfiguration complete message and forwards it to the Donor-CU.
  • the second sending unit 2104 includes a first receiving module not shown, a fifth sending module, and a sixth sending module, and the first receiving module on the DU of the first IAB-node receives the second IAB - the second RRC reconfiguration complete message sent by the node; the fifth sending module on the DU of the first IAB-node sends the third uplink F1AP message containing the second RRC reconfiguration complete message to the first IAB- MT of the node; the sixth sending module on the MT of the first IAB-node includes the third uplink F1AP message in the first RRC reconfiguration complete message and forwards it to the Donor-CU.
  • the message sending apparatus 2100 in this embodiment of the present application 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 information related to the network topology update configured for its child nodes is sent by the Donor-CU to the IAB-node and cached in the IAB-node, and the IAB-node switches to the new node.
  • the IAB-node forwards the information related to the network topology update configured by Donor-CU for its child nodes to its child nodes, so that the IAB-node and its child nodes can perform the network topology almost simultaneously. Update to reduce service interruption time due to node migration.
  • An embodiment of the present application provides a message sending apparatus.
  • FIG. 22 is a schematic diagram of an apparatus for sending a message according to an embodiment of the present application.
  • the apparatus may be an IAB node in an IAB system, or may be one or some components or components configured in the IAB node.
  • the IAB system includes a Donor device and an IAB node, and the embodiment of this application is described from the side of the second IAB-node.
  • the implementation principle of the message sending apparatus of the embodiment of the present application is similar to that of the embodiment of the second aspect, and the same content is not repeated.
  • the message sending apparatus 2200 in this embodiment of the present application includes:
  • the fourth receiving unit 2201 which receives the third RRC reconfiguration message for the third IAB-node path migration from the Donor-CU;
  • the third sending unit 2202 when receiving the second RRC reconfiguration message sent by the Donor-CU and forwarded by the first IAB-node, forwards the third RRC reconfiguration message to the third IAB-node, the second RRC reconfiguration message
  • the RRC reconfiguration message is used for the second IAB-node path migration
  • the third IAB-node is a downstream child node of the second IAB-node, and the second IAB-node is a downstream child node of the first IAB-node.
  • the third RRC reconfiguration message is carried by the second downlink F1AP message sent by the Donor-CU.
  • the third sending unit 2202 includes: a seventh sending module and an eighth sending module not shown; when the MT of the second IAB-node receives the second RRC reconfiguration message, the seventh The sending module sends the second indication information to the DU of the second IAB-node; when the DU of the second IAB-node receives the second indication information, the eighth sending module forwards the third RRC reconfiguration message to the third RRC reconfiguration message.
  • a seventh sending module and an eighth sending module not shown when the MT of the second IAB-node receives the second RRC reconfiguration message, the seventh The sending module sends the second indication information to the DU of the second IAB-node; when the DU of the second IAB-node receives the second indication information, the eighth sending module forwards the third RRC reconfiguration message to the third RRC reconfiguration message.
  • the seventh sending module on the MT of the second IAB-node sends a message to the second IAB-node.
  • the DU of the second IAB-node sends the second indication information.
  • the second parameter configured for the second IAB-node to change the transmission path includes a default backhaul RLC channel, a default BAP route, or an IP address configured for the second IAB-node.
  • the seventh sending module on the MT of the second IAB-node sends the second Indication information; the second path relocation indication information is used to indicate that the second RRC reconfiguration message is a reconfiguration message for the second IAB-node to perform path relocation.
  • the second RRC reconfiguration message when the present apparatus is applied to the Donor-DU change after the first IAB-node is switched to the new parent node, the second RRC reconfiguration message is used for the second IAB-node between the Donor-DU path migration between.
  • the second path relocation indication information is used to indicate that the second IAB-node is performing path relocation between Donor-DUs, that is, when the second RRC message includes the second path relocation indication information, it indicates that the second RRC reconfiguration message is for A reconfiguration message for path migration between different Donor-DUs at the second IAB-node.
  • the second RRC reconfiguration message further includes configuration information of the second indication information; the configuration information of the second indication information is used to indicate that the MT of the second IAB-node receives the second indication During the RRC reconfiguration message, the second indication information is sent to the distribution unit (DU) of the second IAB-node.
  • the configuration information of the second indication information is used to indicate that the MT of the second IAB-node receives the second indication
  • the second indication information is sent to the distribution unit (DU) of the second IAB-node.
  • the second downlink F1AP message further includes second buffer indication information; the second buffer indication information is used to instruct the second IAB-node to buffer the third RRC reconfiguration message until receiving the Release after the second indication message.
  • the third RRC reconfiguration message is included in the second RRC reconfiguration message sent by the Donor-CU and forwarded by the first IAB-node.
  • the second RRC reconfiguration message further includes identification information of the third IAB-node.
  • the third RRC reconfiguration message is carried by a fourth downlink F1AP message sent by the Donor-CU, and the fourth downlink F1AP message is carried by the third RRC reconfiguration message.
  • the fourth downlink F1AP message further includes the identification information of the third IAB-node.
  • the third sending unit 2202 includes: a ninth sending module and a tenth sending module not shown; the MT of the second IAB-node is sent by the Donor-CU after receiving and sent by the first IAB-node When the second RRC reconfiguration message is forwarded, the ninth sending module sends the fourth downlink F1AP message to the DU of the second IAB-node;
  • the tenth sending module forwards the third RRC reconfiguration message in the fourth downlink F1AP message to the third IAB-node.
  • the apparatus when the second IAB-node receives the second RRC reconfiguration message, the apparatus further includes: a fourth sending unit 2203 and a fifth receiving unit 2204 (optional); a fourth sending unit 2203 Send a second RRC reconfiguration complete message to the first IAB-node;
  • the fifth receiving unit 2204 receives the third RRC reconfiguration complete message sent by the third IAB-node.
  • the fourth sending unit 2203 is further configured to forward the third RRC reconfiguration complete message to the Donor-CU, where the third RRC reconfiguration complete message is carried by the second uplink F1AP message.
  • the fourth sending unit 2203 is further configured to include the third RRC reconfiguration complete message in the second RRC reconfiguration complete message and forward it to the Donor-CU.
  • the fourth sending unit 2203 further includes a second receiving module not shown, an eleventh sending module and a twelfth sending module; the second receiving module on the DU of the second IAB-node receives the The third RRC reconfiguration complete message sent by the third IAB-node; the eleventh sending module on the DU of the second IAB-node sends the fourth uplink F1AP message containing the third RRC reconfiguration complete message to the MT of the second IAB-node; the twelfth sending module on the MT of the th IAB-node includes the fourth uplink F1AP message in the second RRC reconfiguration complete message and forwards it to the Donor-CU.
  • the information related to the network topology update configured for its child nodes is sent by the Donor-CU to the IAB-node and cached in the IAB-node, and the IAB-node switches to the new node.
  • the IAB-node forwards the information related to the network topology update configured by Donor-CU for its child node to its child node. Forwards information related to the network topology update configured by Donor-CU for its child nodes, so that IAB-node and its child nodes can update the network topology at almost the same time, reducing service interruption time caused by node migration.
  • FIG. 23 is a schematic diagram of an apparatus for sending a message according to an embodiment of the present application.
  • the apparatus may be, for example, an IAB node in an IAB system, or one or some components or components configured in the IAB node.
  • the IAB system includes a Donor device and an IAB node, and the embodiment of this application is described from the side of the second IAB-node.
  • the implementation principle of the message sending apparatus of the embodiment of the present application is similar to that of the embodiment of the second aspect, and the same content is not repeated.
  • the message sending apparatus 2300 in the embodiment of the present application includes:
  • the sixth receiving unit 2301 which receives the third RRC reconfiguration message for the third IAB-node path migration from the Donor-CU;
  • a seventh receiving unit 2302 which receives the path migration failure indication information sent when the first IAB-node fails to randomly access
  • the second processing unit 2303 which triggers the RRC re-establishment process or falls back to the original path configuration
  • the third IAB-node is a downstream child node of the second IAB-node, and the second IAB-node is a downstream child node of the first IAB-node.
  • the apparatus further includes: a fifth sending unit 2304, which forwards the path migration failure indication information to the third IAB-node.
  • the second processing unit 2303 is further configured to forward the third RRC reconfiguration message to the third IAB-node, or clear the third RRC reconfiguration message.
  • the third RRC reconfiguration message is carried by the second downlink F1AP message sent by the Donor-CU; the second processing unit 2303 further includes: a thirteenth sending module and a fourteenth sending module; the The thirteenth sending module on the MT of the second IAB-node sends the second indication information to the DU of the second IAB-node; when the DU of the second IAB-node receives the second indication information, it sends the fourteenth The module forwards the third RRC reconfiguration message carried by the second downlink F1AP message to the third IAB-node.
  • the sixth receiving unit 2301 is further configured to receive a message sent by the Donor-CU to the first IAB-node and forwarded by the first IAB-node for the path migration of the second IAB-node The second RRC reconfiguration message.
  • the IAB-node when the random access of the IAB-node switches to the new parent node fails, it triggers RRC re-establishment and indicates to its child nodes that the path migration fails, and its child nodes also trigger RRC re-establishment.
  • the IAB-node and its sub-nodes can re-establish RRC almost at the same time, reducing the service interruption time caused by the path migration failure. or,
  • the IAB-node When the random access of the IAB-node switches to the new parent node fails, it triggers RRC re-establishment, forwards the RRC reconfiguration of its child node to the child node and indicates the path migration failure to its child node, so that the child node falls back.
  • the IAB-node migration fails, the IAB-node and its child nodes can fall back to the original path configuration at the same time. Otherwise, if the child node performs path migration and generates uplink data according to the new path configuration, these uplink data will be discarded and retransmitted by the UE subsequently, resulting in increased uplink data transmission delay. This method can avoid the extension of data transmission time due to path migration failure.
  • the message sending apparatuses 2200-2300 in this embodiment of the present application 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.
  • FIGS. 22-23 only exemplarily show 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.
  • An embodiment of the present application provides a message sending apparatus.
  • FIG. 24 is a schematic diagram of an apparatus for sending a message according to an embodiment of the present application.
  • the apparatus may be a Donor device in an IAB system, or may be one or some components or components configured in the Donor device.
  • the IAB system includes a Donor device and an IAB node, and the embodiments of this application are described from the side of the Donor-CU.
  • the implementation principle of the message sending apparatus of the embodiment of the present application is similar to that of the embodiment of the third aspect, and the same content is not repeated.
  • FIG. 24 is a schematic diagram of a message sending apparatus according to an embodiment of the present application.
  • a message sending apparatus 2400 according to an embodiment of the present application includes:
  • the sixth sending unit 2401 is configured to send a second Radio Resource Control (RRC) reconfiguration message for the path migration of the second IAB-node to the first IAB-node, so that the first IAB-node is in random access When successful, forward the second RRC reconfiguration message to the second IAB-node;
  • RRC Radio Resource Control
  • a seventh sending unit 2402 configured to send a first Radio Resource Control (RRC) reconfiguration message for path migration of the first IAB-node to the first IAB-node.
  • RRC Radio Resource Control
  • the second RRC reconfiguration message is carried by the first downlink F1AP message sent by the Donor-CU.
  • the first RRC reconfiguration message includes a first parameter for changing the transmission path configuration for the first IAB-node.
  • the first parameter includes a default backhaul RLC channel, a default BAP route or an IP address configured for the first IAB-node.
  • the first RRC reconfiguration message further includes first path relocation indication information; the first path relocation indication information is used to indicate that the first RRC reconfiguration message is for the first IAB-node to perform Reconfiguration message for path migration.
  • the first RRC reconfiguration message further includes configuration information of the first indication information; the configuration information of the first indication information is used to indicate that the MT of the first IAB-node succeeds in random access , and send the first indication information to the distribution unit (DU) of the first IAB-node.
  • the first downlink F1AP message further includes first buffer indication information; the first buffer indication information is used to instruct the first IAB-node to buffer the second RRC reconfiguration message until received Release after the first indication information.
  • the second RRC reconfiguration message is carried by the first RRC reconfiguration message.
  • the first RRC reconfiguration message further includes identification information of the second IAB-node.
  • the second RRC reconfiguration message is carried by the third downlink F1AP message
  • the third downlink F1AP message is carried by the first RRC reconfiguration message
  • the third downlink F1AP message further includes identification information of the second IAB-node.
  • the first RRC reconfiguration message further includes configuration information of the path relocation failure indication information, and the configuration information of the path relocation failure indication information is used to indicate that the first IAB-node fails in random access. , sending path migration failure indication information to the second IAB-node.
  • the second RRC reconfiguration message includes a second parameter for changing the transmission path configuration for the second IAB-node.
  • the second parameter includes a default backhaul RLC channel, a default BAP route or an IP address configured for the second IAB-node.
  • the second RRC reconfiguration message further includes second path relocation indication information; the second path relocation indication information is used to indicate that the second RRC reconfiguration message is for the second IAB-node to perform Reconfiguration message for path migration.
  • the second RRC reconfiguration message further includes configuration information of the second indication information; the configuration information of the second indication information is used to indicate that the MT of the second IAB-node receives the second indication During the RRC reconfiguration message, the second indication information is sent to the DU of the second IAB-node.
  • the apparatus further includes: an eighth sending unit 2403 (optional), configured to send a third RRC reconfiguration message for path migration of the third IAB-node to the second IAB-node .
  • the third RRC reconfiguration message is carried by the second downlink F1AP message sent by the Donor-CU.
  • the second downlink F1AP message further includes second buffer indication information; the second buffer indication information is used to instruct the second IAB-node to buffer the third RRC reconfiguration message until receiving the Release after the second indication message.
  • the third RRC reconfiguration message is included in the second RRC reconfiguration message sent by the Donor-CU and forwarded by the first IAB-node.
  • the second RRC reconfiguration message further includes identification information of the third IAB-node.
  • the third RRC reconfiguration message is carried by a fourth downlink F1AP message, and the fourth downlink F1AP message is carried by the second RRC reconfiguration message.
  • the fourth downlink F1AP message further includes identification information of the third IAB-node.
  • the apparatus further includes: an eighth receiving unit (optional, not shown), which receives the first RRC reconfiguration complete message sent by the first IAB-node.
  • the eighth receiving unit is further configured to receive a second RRC reconfiguration complete message sent by the second IAB-node, where the second RRC reconfiguration complete message is sent by the first IAB-node It is carried in the upstream F1AP message.
  • the first RRC reconfiguration complete message further includes a third uplink F1AP message
  • the third uplink F1AP message includes a second RRC reconfiguration complete message
  • the first RRC reconfiguration complete message further includes a second RRC reconfiguration message.
  • the message sending apparatus 2400 in this embodiment of the present application 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. 24 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.
  • FIG. 25 is a schematic diagram of the communication system 2500.
  • the communication system 2500 includes a Donor device 2500 and IAB nodes 2501, 2502, 2503, 2504, and 2505, wherein,
  • the IAB node 2503 is the migration IAB node (the first IAB-node)
  • the IAB node 2501 is the source node (the first parent node) of the IAB node 2503
  • the IAB node 2502 is the target node (the second parent node) of the IAB node 2503
  • the Donor The device 2500 acts as a Donor-CU
  • the IAB node 2504 is the downstream child node of the IAB node 2503
  • the IAB node 2505 is the downstream child node of the IAB node 2504 .
  • FIG. 25 only takes the above-mentioned Donor device and the IAB node as examples for description, but the embodiment of the present application is not limited thereto.
  • the network architecture of the Donro device and the IAB node reference may be made to related technologies, and the description is omitted here.
  • the IAB node 2503 is configured to perform the method performed by the first IAB-node in the embodiments of the first aspect, and may include the apparatus of FIG. 21 .
  • the IAB node 2504 is configured to perform the method performed by the second IAB-node in the embodiments of the second aspect, and may comprise the apparatus of FIG. 22 or 23 .
  • the Donor device 2500 is configured to perform the method performed by the Donor-CU in the embodiments of the third aspect, and may include the apparatus of FIG. 24 .
  • the IAB node 2501 corresponding to the first parent node, is configured to receive the downlink F1AP message including the first RRC reconfiguration message in the first aspect embodiment sent by the Donor-CU, or receive the downlink F1AP message,
  • the structure of the downlink F1AP message is shown in FIG. 19A or 20A , which is also used to forward the first RRC reconfiguration message in the F1AP message to the IAB node 2503 .
  • the IAB node 2502 corresponding to the second parent node, is configured to receive the first RRC reconfiguration complete message sent by the IAB node 2503, and include the first RRC reconfiguration complete message in the uplink F1AP message for sending For the Donor-CU, the structure of the upstream F1AP message is shown in Figure 19B or 20B.
  • the embodiment of the present application also provides an IAB node.
  • FIG. 26 is a schematic diagram of an IAB node according to an embodiment of the present application.
  • the IAB node 2600 may include a processor 2601 and a memory 2602 ; the memory 2602 stores data and programs, and is coupled to the processor 2601 .
  • 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 2601 may be configured to execute a program to implement the method performed by the IAB-node or the first parent node or the second parent node as in the embodiment of the first or second aspect.
  • the IAB node 2600 may further include: a communication module 2603 , an input unit 2604 , a display 2605 , and a power supply 2606 .
  • 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 IAB node 2600 does not necessarily include all the components shown in FIG. 26 , and the above components are not required; in addition, the IAB node 2600 may also include components not shown in FIG. 26 . There is technology.
  • the embodiment of the present application also provides a Donor device.
  • FIG. 27 is a schematic diagram of a Donor device according to an embodiment of the present application.
  • the Donor device 2700 may include: a processor (eg, a central processing unit CPU) 2701 and a memory 2702 ; the memory 2702 is coupled to the processor 2701 .
  • the memory 2702 can store various data; in addition, it also stores information processing programs, and the programs are executed under the control of the central processing unit 2701 .
  • the processor 2701 may be configured to execute a program to implement the method as in the embodiment of the third aspect.
  • the Donor device 2700 may further include: a transceiver 2703, an antenna 2704, and the like; wherein, the functions of the above components are similar to those in the prior art, and are not repeated here. It is worth noting that the Donor device 2700 does not necessarily include all the components shown in FIG. 27 ; in addition, the Donor device 2700 may also include components not shown in FIG. 27 , and reference may be made to the prior art.
  • the embodiment of the present application also provides a computer-readable program, wherein when the program is executed in an IAB node, the program causes a computer to execute the method in the embodiment of the first or second aspect in the IAB node.
  • the embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer to execute the method in the embodiment of the first or second aspect in an IAB node.
  • the embodiments of the present application further provide a computer-readable program, wherein when the program is executed in a Donor device, the program causes a computer to execute the method in the embodiment of the third aspect in the Donor device.
  • the embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer to execute the method in the embodiment of the third aspect in a Donor device.
  • 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.
  • Logic components such as field programmable logic components, microprocessors, processors used in computers, and the like.
  • 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.
  • a message sending method is characterized in that, described method comprises:
  • the first integrated access and backhaul node receives a second Radio Resource Control (RRC) reconfiguration message from the Donor Central Unit (Donor-CU) for path migration of the second IAB-node; wherein, The second IAB-node is a downstream child node of the first IAB-node;
  • RRC Radio Resource Control
  • the first IAB-node forwards the second RRC reconfiguration message to the second IAB-node.
  • step of the first IAB-node forwarding the second RRC reconfiguration message to the second IAB-node comprises:
  • the distribution unit (DU) of the first IAB-node forwards the second RRC reconfiguration message to the second IAB-node when receiving the first indication information.
  • the first RRC reconfiguration message includes when changing the first parameter configured for the transmission path for the first IAB-node, the MT of the first IAB-node sends the The DU of the first IAB-node sends the first indication information.
  • the first parameter configured for changing the transmission path for the first IAB-node comprises a default backhaul RLC channel, a default BAP configured for the first IAB-node route or IP address.
  • the first RRC reconfiguration message further includes configuration information of the first indication information; the configuration information of the first indication information is used to indicate the first IAB-node
  • the MT sends first indication information to the distribution unit (DU) of the first IAB-node.
  • first downlink F1AP message further includes first buffer indication information; the first buffer indication information is used to instruct the first IAB-node to buffer the first buffer. Two RRC reconfiguration messages are released until the first indication information is received.
  • step of forwarding the second RRC reconfiguration message to the second IAB-node by the first IAB-node when the random access succeeds comprises:
  • the MT of the first IAB-node sends the third downlink F1AP message to the DU of the first IAB-node;
  • the DU of the first IAB-node When the DU of the first IAB-node receives the third downlink F1AP message, it forwards the second RRC reconfiguration message in the third downlink F1AP message to the second IAB-node.
  • the first IAB-node forwards the second RRC reconfiguration message to the second IAB-node, or clears the second RRC reconfiguration message.
  • the first RRC reconfiguration message further includes configuration information of path migration failure indication information, and the configuration information of the path migration failure indication information is used to indicate the first IAB -
  • the node sends path migration failure indication information to the second IAB-node.
  • the first IAB-node receives the second RRC reconfiguration complete message sent by the second IAB-node.
  • the first IAB-node forwards the second RRC reconfiguration complete message to the Donor-CU, where the second RRC reconfiguration complete message is carried by the first uplink F1AP message.
  • the first IAB-node includes the second RRC reconfiguration complete message in the first RRC reconfiguration complete message and forwards it to the Donor-CU.
  • the DU of the first IAB-node receives the second RRC reconfiguration complete message sent by the second IAB-node;
  • the DU of the first IAB-node sends a third uplink F1AP message including the second RRC reconfiguration complete message to the MT of the first IAB-node;
  • the MT of the first IAB-node includes the third uplink F1AP message in the first RRC reconfiguration complete message and forwards it to the Donor-CU.
  • a message sending method characterized in that the method comprises:
  • the second IAB-node receives the third RRC reconfiguration message for the path migration of the third IAB-node from the Donor-CU;
  • the second IAB-node When the second IAB-node receives the second RRC reconfiguration message sent by the Donor-CU and forwarded by the first IAB-node, it forwards the third RRC reconfiguration message to the third IAB-node, The second RRC reconfiguration message is used for the second IAB-node path migration;
  • the third IAB-node is a downstream child node of the second IAB-node, and the second IAB-node is a downstream child node of the first IAB-node.
  • the step of forwarding the third RRC reconfiguration message by the IAB-node includes:
  • the MT of the second IAB-node When the MT of the second IAB-node receives the second RRC reconfiguration message, it sends second indication information to the DU of the second IAB-node;
  • the DU of the second IAB-node forwards the third RRC reconfiguration message to the third IAB-node when receiving the second indication information.
  • the second RRC reconfiguration message includes the second parameter of the transmission path configuration for the second IAB-node that is changed by the MT of the second IAB-node to the second IAB-node.
  • the DU of the second IAB-node sends second indication information.
  • the second parameter configured for changing the transmission path for the second IAB-node comprises a default backhaul RLC channel and a default BAP configured for the second IAB-node. route or IP address.
  • the second RRC reconfiguration message further includes configuration information of second indication information; the configuration information of the second indication information is used to indicate the second IAB-node
  • the MT sends second indication information to the distribution unit (DU) of the second IAB-node.
  • the second downlink F1AP message further includes second buffer indication information; the second buffer indication information is used to instruct the second IAB-node to buffer the third buffer.
  • the RRC reconfiguration message is released until the second indication information is received.
  • the MT of the second IAB-node When receiving the second RRC reconfiguration message sent by the Donor-CU and forwarded by the first IAB-node, the MT of the second IAB-node sends the second RRC reconfiguration message to the DU of the second IAB-node.
  • the DU of the second IAB-node When the DU of the second IAB-node receives the fourth downlink F1AP message, it forwards the third RRC reconfiguration message in the fourth downlink F1AP message to the third IAB-node.
  • the second IAB-node receives the third RRC reconfiguration complete message sent by the third IAB-node.
  • the second IAB-node forwards the third RRC reconfiguration complete message to the Donor-CU, where the third RRC reconfiguration complete message is carried by the second uplink F1AP message.
  • the second IAB-node includes the third RRC reconfiguration complete message in the second RRC reconfiguration complete message and forwards it to the Donor-CU.
  • the DU of the second IAB-node receives the third RRC reconfiguration complete message sent by the third IAB-node;
  • the DU of the second IAB-node sends a fourth uplink F1AP message including the third RRC reconfiguration complete message to the MT of the second IAB-node;
  • the MT of the IAB-node includes the fourth uplink F1AP message in the second RRC reconfiguration complete message and forwards it to the Donor-CU.
  • a message sending method characterized in that the method comprises:
  • the second IAB-node receives the third RRC reconfiguration message for the path migration of the third IAB-node from the Donor-CU;
  • the second IAB-node receives the path migration failure indication information sent when the first IAB-node fails to randomly access
  • the second IAB-node triggers the RRC re-establishment process or falls back to the original path configuration
  • the third IAB-node is a downstream child node of the second IAB-node, and the second IAB-node is a downstream child node of the first IAB-node.
  • the second IAB-node forwards the path migration failure indication information to the third IAB-node.
  • the second IAB-node forwards the third RRC reconfiguration message to the third IAB-node, or clears the third RRC reconfiguration message.
  • the MT of the second IAB-node sends second indication information to the DU of the second IAB-node;
  • the DU of the second IAB-node When the DU of the second IAB-node receives the second indication information, it forwards the third RRC reconfiguration message carried by the second downlink F1AP message to the third IAB-node.
  • the second IAB-node receives the second RRC replay for the path migration of the second IAB-node, which is sent by the Donor-CU to the first IAB-node, and forwarded by the first IAB-node. Configuration messages.
  • a message sending method characterized in that the method comprises:
  • the Donor-CU sends a second Radio Resource Control (RRC) reconfiguration message for the second IAB-node path relocation to the first IAB-node, so that the first IAB-node will
  • RRC Radio Resource Control
  • the Donor-CU sends a first Radio Resource Control (RRC) reconfiguration message to the first IAB-node for path migration of the first IAB-node.
  • RRC Radio Resource Control
  • the first parameter comprises a default backhaul RLC channel, a default BAP route or an IP address configured for the first IAB-node.
  • the first RRC reconfiguration message includes first path relocation indication information; the first path relocation indication information is used to indicate that the first RRC reconfiguration message is for A reconfiguration message for path migration at the first IAB-node.
  • the MT sends first indication information to the distribution unit (DU) of the first IAB-node.
  • first downlink F1AP message further includes first buffer indication information; the first buffer indication information is used to instruct the first IAB-node to buffer the first buffer. Two RRC reconfiguration messages are released until the first indication information is received.
  • the node sends path migration failure indication information to the second IAB-node.
  • the second RRC reconfiguration message includes second path relocation indication information; the second path relocation indication information is used to indicate that the second RRC reconfiguration message is a A reconfiguration message for path migration at the second IAB-node.
  • the second RRC reconfiguration message further includes configuration information of second indication information; the configuration information of the second indication information is used to indicate the second IAB-node
  • the MT sends second indication information to the DU of the second IAB-node.
  • the Donor-CU sends a third RRC reconfiguration message for path migration of the third IAB-node to the second IAB-node.
  • the second downlink F1AP message further includes second buffer indication information; the second buffer indication information is used to instruct the second IAB-node to buffer the third buffer.
  • the RRC reconfiguration message is released until the second indication information is received.
  • the Donor-CU receives the first RRC reconfiguration complete message sent by the first IAB-node.
  • the Donor-CU receives a second RRC reconfiguration complete message sent by the second IAB-node, where the second RRC reconfiguration complete message is carried by the first uplink F1AP message sent by the first IAB-node.
  • a Donor device comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the computer program to implement the method according to any one of appendix 44 to 70 .
  • An IAB-node comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the computer program to implement any one of appendix 1 to 43 method.
  • a communication system comprising a Donor device, a first IAB-node, and a second IAB-node, wherein the Donor device is configured to perform the method of any one of Supplements 44 to 70, the first The IAB-node is configured to execute the method described in any one of Supplementary Notes 1 to 21, and the second IAB-node is configured to execute the method described in any one of Supplementary Notes 22 to 43.

Landscapes

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

Abstract

本申请实施例提供了一种消息发送方法，装置以及系统，该方法包括：第一集成的接入和回传节点(IAB-node)接收来自宿主中心单元(Donor-CU)的用于第二IAB-node路径迁移的第二无线资源控制(RRC)重配置消息；其中，该第二IAB-node为该第一IAB-node的下游子节点；该第一IAB-node接收来自该Donor-CU的用于该第一IAB-node路径迁移的第一RRC重配置消息；该第一IAB-node在随机接入成功时，向该第二IAB-node转发该第二RRC重配置消息。

Description

消息发送方法、装置和系统 技术领域
本申请涉及通信领域。
背景技术
未来无缝的蜂窝网络部署需要非常灵活和超密集的NR小区部署，超密集网络是5G的目标之一，部署一个无需有线回传的新无线(new radio，NR)网络对于实现5G的超密集网络非常重要。由于5G毫米波使小区覆盖范围缩小，无线自回传系统还需要是多跳的才能满足部署需求。5G的高带宽、大规模多输入多输出MIMO和波束系统使5G比LTE更容易开发超密集NR小区的无线自回传系统，为了开发这种带有无线自回传的多跳系统，3GPP在R16开始了IAB(Integrated access and backhaul，接入回传一体化)项目的研究和标准化。
图1是IAB系统的一个示意图，如图1所示，在IAB系统中，中继节点同时支持接入(access)和回传(backhaul)功能，中继节点的无线传输链路在时域、频域或空域上复用接入链路(access link)和回传链路(backhaul link)，接入链路和回传链路可以使用相同或不同的频段。
在IAB网络架构如下，中继节点指的是IAB-node(IAB节点)，其同时支持接入和回传功能。网络侧最后一跳接入节点称为IAB-donnor(IAB宿主)，其支持gNB功能并支持IAB-node接入。所有的UE数据可以通过一跳或多跳经IAB-node回传到IAB-Donor。
IAB-node的功能分为两部分，一部分是gNB-DU功能，称作IAB-DU(分布单元)，另一部分是UE功能，称作IAB-MT(移动终端)。IAB-DU实现网络侧设备功能，连接到下游的child IAB-node(子IAB节点)，对UE以及下游child IAB-node提供NR空口接入并与IAB Donor-CU之间建立有F1连接。IAB-MT实现部分终端设备功能，连接到上游的parent IAB-node(父IAB节点)或IAB-Donor DU，IAB-MT包括物理层、层二、RRC(Radio Resource Control，无线资源控制)和NAS(Non-Access Stratum，非接入层)层功能，还间接的连接到IAB Donor-CU以及核心网(Core Network，CN)。
在IAB系统中，IAB-node可以通过独立组网(SA，Standalone)模式或非独立组网(EN-DC，E-UTRA-NRDualConnectivity)模式接入网络。图2是SA模式的IAB架构的示意图。图3是EN-DC模式的IAB架构的示意图。
图4是一个IAB节点(IAB-node)与父节点(parent IAB-node)和子节点(child IAB-node)的示意图。如图4所示，IAB节点的IAB-DU作为网络侧与子节点的IAB-MT连接，IAB节点的IAB-MT作为终端侧与父节点的IAB-DU连接。。
图5是IAB-DU和IAB-Donor CU之间的F1用户面(F1-U)协议栈的示意图。图6是IAB-DU和IAB-Donor CU之间的F1控制面(F1-C)协议栈的示意图。
如图5和图6所示，F1-U和F1-C是建立在IAB-DU和IAB-Donor-CU之间的传输(IP)层之上，图5和图6中经过两跳无线回传和一跳有线回传。在回传链路上，传输(IP)层承载在回传自适应协议(BAP)子层上，IAB-node中的BAP实体实现IAB系统的路由功能，由IAB-Donor CU提供路由表。BAP PDU(协议数据单元)在回传链路的RLC(无线链路控制)信道中传输，回传链路的多个RLC信道可以被IAB-Donor配置为承载不同的优先级和QoS(服务质量)的业务，由BAP实体将BAP PDU映射到不同的回传RLC信道上。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
在R16中，IAB系统已经支持了IAB-node在同一个Donor-CU下的不同DU之间移动时引起的拓扑和路由的自适应改变。IAB-node在同一个Donor-CU下移动时(此时，该IAB-node称为Migrating IAB-node)，还保持与下游子IAB-node和UE的拓扑关系。但IAB-node在移动过程中，如果断开了与原来的父IAB-node的连接，连接到新的父IAB-node，则会导致从IAB-node以及IAB-node的子节点到Donor-CU传输路径的改变，也就是网络拓扑改变，比如，IAB-node切换到新的父节点，或与新的父节点建立双连接时引起的网络拓扑改变。
图7是IAB-node移动导致网络拓扑改变的一个示意图。如图7所示，IAB-node5从IAB-node3下的小区切换到IAB-node 4下的小区之后，IAB-node5及其下游子节点 IAB-node 6到Donor-CU的传输路径由经过IAB-node1和IAB-node 2变为经过IAB-node2和IAB-node 4，即网络拓扑发生了改变。
目前，针对IAB-node在同一个Donor-CU中移动时网络拓扑的更新过程而言，IAB-node改变父节点时，Donor-CU可以通过RRC重配置消息为IAB-node配置网络拓扑更新相关的配置信息，其中，默认路由标识包含了目的Donor-DU的BAP地址和路径ID。当IAB-node切换到新的父节点之后，IAB-node开始应用上述配置信息，对于IAB-node的下游子节点，也通过相同的方法进行网络拓扑更新相关的配置。
发明人发现，现有方法中，无法使切换到新父节点的IAB-node及其子节点同时进行F1路径迁移，因此，会导致IAB-node路径迁移过程中的较长的服务中断时间，目前对子节点的网络拓扑更新是在IAB-node完成到新的父节点的接入之后进行的，子节点在IAB-node之后进行网络拓扑更新，由于拓扑更新后Donor-DU(父节点)发生改变，子节点根据原来的路径配置产生的上行数据携带的是原Donor-DU的地址，与新的Donor-DU的地址不同，这些上行数据会被新的Donor-DU丢弃，导致子节点根据原来的路径配置产生的上行数据无法发送到CU，被丢弃的上行数据会被UE重传，因此导致较长的数据传输时延和服务中断时间。
另外，IAB-node的移动导致网络拓扑的更新(topology adaptation)过程中，Donor-CU需要给IAB-node及其每个下游子节点发送网络拓扑更新相关的配置消息。但是，对于每个节点的配置消息都需要单独发送，导致大量信令消息开销，也同时会导致较长的服务中断时间。
为了解决上述问题的至少一种或其它类似问题，本申请实施例提供了一种消息发送方法、装置和系统。
根据本申请实施例的一方面，提供一种消息发送装置，应用于第一集成的接入和回传节点(IAB-node)，所述装置包括：
第一接收单元，其接收来自宿主中心单元(Donor-CU)的用于第二IAB-node路径迁移的第二无线资源控制(RRC)重配置消息；其中，所述第二IAB-node为所述第一IAB-node的下游子节点；
第二接收单元，其接收来自所述Donor-CU的用于所述第一IAB-node路径迁移的第一RRC重配置消息；
第一发送单元，其在第一IAB-node随机接入成功时，向所述第二IAB-node转发 所述第二RRC重配置消息。
根据本申请实施例的一方面，提供一种消息发送装置，应用于第二集成的接入和回传节点(IAB-node)，所述装置包括：
第四接收单元，其接收来自Donor-CU的用于第三IAB-node路径迁移的第三RRC重配置消息；
第三发送单元，其接收到所述Donor-CU发送并由第一IAB-node转发的第二RRC重配置消息时，向所述第三IAB-node转发所述第三RRC重配置消息，所述第二RRC重配置消息用于所述第二IAB-node路径迁移；
其中，所述第三IAB-node为所述第二IAB-node的下游子节点，所述第二IAB-node为所述第一IAB-node的下游子节点。
根据本申请实施例的一方面，提供一种消息发送装置，应用于第二集成的接入和回传节点(IAB-node)，所述装置包括：
第六接收单元，其接收来自Donor-CU的用于第三IAB-node路径迁移的第三RRC重配置消息；
第七接收单元，其接收第一IAB-node随机接入失败时发送的路径迁移失败指示信息；
第二处理单元，其触发RRC重建立过程或回退到原路径配置；
其中，所述第三IAB-node为所述第二IAB-node的下游子节点，所述第二IAB-node为所述第一IAB-node的下游子节点。
本申请实施例的有益效果之一在于：IAB-node在切换到新的父节点前，为其子节点配置的网络拓扑更新相关的信息由Donor-CU发送至IAB-node并缓存在IAB-node，在IAB-node切换到新的父节点的随机接入成功时，IAB-node向其子节点转发Donor-CU为其子节点配置的网络拓扑更新相关的信息，这样，可使IAB-node及其子节点几乎同时进行网络拓扑更新，减少因节点迁移导致的服务中断时间。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附附记的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的 特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部分，用于例示本申请的实施方式，并与文字描述一起来阐释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。在附图中：
图1是IAB系统的一个示意图；
图2是SA模式的IAB架构的示意图；
图3是EN-DC模式的IAB架构的示意图；
图4是父节点(parent IAB-node)和子节点(child IAB-node)的示意图；
图5是IAB系统的F1-U协议栈的示意图；
图6是IAB系统的F1-C协议栈的示意图；
图7是IAB节点在同一个Donor下的不同DU之间移动的一个方法示意图；
图8是本申请实施例的消息发送方法的一个示意图；
图9是本申请实施例的消息发送方法的一个示意图；
图10是本申请实施例的消息发送方法的一个示意图；
图11是本申请实施例的消息发送方法的一个示意图；
图12是本申请实施例的消息发送方法的一个示意图；
图13-15是本申请实施例的消息发送方法的一个场景的示意图；
图16-17是本申请实施例的消息发送方法的再一个场景的示意图；
图18是本申请实施例的消息发送方法的再一个场景的示意图；
图19A是本申请实施例的下行消息结构示意图；
图19B是本申请实施例的上行消息结构示意图；
图20A是本申请实施例的下行消息结构示意图；
图20B是本申请实施例的上行消息结构示意图；
图21是本申请实施例的消息发送装置的一个示意图；
图22是本申请实施例的消息发送装置的另一个示意图；
图23是本申请实施例的消息发送装置的又一个示意图；
图24是本申请实施例的消息发送装置的再一个示意图；
图25是本申请实施例的通信系统的一个示意图；
图26是本申请实施例的IAB节点的一个示意图；
图27是本申请实施例的Donor设备的一个示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附附记的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如新无线(NR，New Radio)、长期演进(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、6G等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(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)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备，也可以称为“终端设备”(TE，Terminal Equipment)。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
例如上图7中，IAB-node3是IAB-node4的父节点，IAB-node4是IAB-node5的父节点，当IAB-node3切换到新的父节点IAB-node2之后，网络拓扑发生变化，即IAB-node3、IAB-node4和IAB-node5与Donor-CU之间的传输路径改变。Donor CU给IAB-node3、IAB-node4及IAB-node5发送网络拓扑更新相关的配置消息，使F1传输路径由原路径切换至新路径。对IAB-node4及IAB-node5的网络拓扑更新是在IAB-node3完成到新的父节点的接入之后进行的，也就是IAB-node4及IAB-node5在IAB-node3之后进行网络拓扑更新。导致IAB-node4及IAB-node5按照原来的配置发送的上行数据被Donor-DU2丢弃，引起较长的传输时延和服务中断时间。
另外，现有技术中，Donor-Cu针对IAB-node3及其每个子节点，都要分别发送一条承载网络拓扑更新相关配置信息的下行F1AP消息(F1 Application Protocol，F1应用协议)，即DL F1AP MESSAGE至IAB-node3及其每个子节点各自的父节点(见附图7中消息A，B，C)。针对消息B，只能在IAB-node3路径迁移成功后才下发，针对消息C，只能在IAB-node4路径迁移成功后才下发，这会导致大量信令消息开销，也同时会导致较长的服务中断时间。
在本申请中，IAB-node在切换到新的父节点前，为其子节点配置的网络拓扑更新相关的信息由Donor-CU发送至IAB-node并缓存在IAB-node，在IAB-node切换到新的父节点的随机接入成功时，IAB-node向其子节点转发Donor-CU为其子节点配置的网络拓扑更新相关的信息，这样，可使IAB-node及其子节点几乎同时进行网络拓扑更新，减少因节点迁移导致的服务中断时间。
本申请以IAB-node切换到新的父节点为例进行说明，但本申请实施例并不以此作为限制，本申请还可以应用于IAB-node与新的父节点建立双连接时引起的网络拓扑改变。下面结合附图对本申请的各种实施方式进行说明。这些实施方式只是示例性的，不是对本申请的限制。
例如，在本申请各实施例中，第一IAB-node作为迁移节点(例如图7 IAB-node3)是Donor-CU控制下的IAB节点，该第一IAB-node从第一父节点(例如图7 IAB-node1)迁移(切换)到第二父节点(例如图7 IAB-node2)，第二IAB-node(例如图7 IAB-node4)为第一IAB-node的下游子节点，第三IAB-node(例如图7 IAB-node5)为第二IAB-node的下游子节点。需要说明的是，第二IAB-node或第三IAB-node的数量可以是一个或至少两个，第三IAB-node也可以有其他子节点，本申请实施例并不以此作为限制， 以下为方便说明，以附图7中IAB-node4作为第二IAB-node，IAB-node5作为第三IAB-node且IAB-node5不具有其他子节点为例进行说明。
第一方面的实施例
本申请实施例提供一种消息发送方法，从第一IAB-node侧进行说明。
本方法应用于第一IAB-node切换到新的父节点导致该第一IAB-node及其子节点进行路径迁移的情况下。图8是本实施例消息发送方法一示意图，如图8所示，该方法包括：
801，第一IAB-node接收来自Donor-CU的用于第二IAB-node路径迁移的第二无线资源控制(RRC)重配置消息；
802，该第一IAB-node接收来自该Donor-CU的用于该第一IAB-node路径迁移的第一RRC重配置消息；
803，该第一IAB-node在随机接入成功时，向该第二IAB-node转发该第二RRC重配置消息。
在一些实施例中，在801和802中第一RRC重配置消息和第二RRC重配置消息都是由Donor-CU配置生成的，来自Donor-CU的第一或第二RRC重配置消息可以是由Donor-CU直接发送至该第一IAB-node的，也可以是由Donor-CU发送至第一父节点，并由第一父节点转发至该第一IAB-node的，本申请实施例并不以此作为限制。
在一些实施例中，在803中，第一IAB-node确定该第一RRC重配置消息是用于该第一IAB-node路径迁移时才向该第二IAB-node转发该第二RRC重配置消息。第一RRC重配置消息包含为该第一IAB-node改变传输路径配置的第一参数时，第一IAB-node可以确定该第一RRC重配置消息是用于该第一IAB-node路径迁移。该第一参数包括为该第一IAB-node配置的默认回传无线链路控制(BH RLC)信道、默认回传适配协议(Backhaul Adaptation Protocol，BAP)路由或网际互联协议IP地址。其中，该默认BH RLC信道可以是上行F1-C和非F1数据使用的BH RLC信道；该默认BAP路由可以是上行F1-C和非F1数据使用的路由，包括路径标识和目的BAP地址；该IP地址表示可路由至切换至第二父节点后新的Donor-DU(例如图7的Donor-DU2)的IP地址，该第一IAB-node在接收到第一RRC重配置消息包含上述第一参数时，从而确定该第一RRC重配置消息是用于路径迁移的配置消息。
在一些实施例中，第一IAB-node通过该第一RRC重配置消息包含第一路径迁移指示信息确定该第一RRC重配置消息是用于路径迁移的配置消息。第一RRC重配置消息包含上述改变传输路径配置的参数的情况下，该RRC消息也可能不是用于路径迁移，因此需要向第一IAB-node显示指示进行路径迁移相关的RRC重配置，其中，该第一路径迁移指示信息用于指示该第一RRC重配置消息是用于第一IAB-node进行路径迁移的重配置消息。
在一些实施例中，本方法应用于第一IAB-node在不同Donor-DU进行路径迁移的情况下(切换到新的父节点后Donor-DU改变)，则该第一RRC重配置消息是用于该第一IAB-node在Donor-DU之间的路径迁移。该第一路径迁移指示信息用于指示第一IAB-node正在进行Donor-DU之间的路径迁移，也即第一RRC消息包含第一路径迁移指示信息时表明该第一RRC重配置消息是用于第一IAB-node在不同的Donor-DU之间进行路径迁移的重配置消息。
在一些实施例中，在801和802中，该第一RRC重配置消息和第二RRC重配置消息可以由一条下行消息承载，即该第一IAB-node同时接收到该第一RRC重配置消息和第二RRC重配置消息，或者由两条下行消息分别承载，即该第一IAB-node先后接收到第二RRC重配置消息和第一RRC重配置消息，后述将会分情况进行详细说明。
在一些实施例中，在803中，第一IAB-node切换到第二父节点并进行路径迁移，其中，该第一IAB-node需要执行随机接入，以切换到第二父节点，第一RRC重配置消息包含第一IAB-node切换到第二父节点的相关信息。该随机接入过程可以参考现有技术中IAB节点的随机接入，此处不再赘述，只有在随机接入成功时，才触发转发缓存的该第二RRC重配置消息。在随机接入失败时，该第一IAB-node触发RRC重建立，该RRC重建立过程可以参考现有技术中IAB-node的RRC重建立，此处不再赘述。此外，该第一IAB-node还需要向其子节点发送路径迁移失败指示信息，可选的，也可以将该第二RRC重配置消息也转发给其子节点或者清除该第二RRC重配置消息，关于随机接入失败时其子节点的行为具体将在后述第二方面的实施例进行说明。
在一些实施例中，在803中，在随机接入成功时，该方法还可以包括：该第一IAB-node向该Donor-CU发送第一RRC重配置完成消息；此外，该第一IAB-node还可以接收该第二IAB-node发送的第二RRC重配置完成消息，可选的，还可以将所 述第二RRC重配置完成消息转发给该Donor-CU，其中，该第一RRC重配置完成消息和第二RRC重配置完成消息可以由一条上行消息承载，或者由两条上行消息分别承载，上述发送给Donor-CU可以是直接发送给Donor-CU，也可以是经由第二父节点转发给该Donor-CU，后述将会分情况进行详细说明。
由此，IAB-node在切换到新的父节点前，为其子节点配置的网络拓扑更新相关的信息由Donor-CU发送至IAB-node并缓存在IAB-node，在IAB-node切换到新的父节点的随机接入成功时，IAB-node向其子节点转发Donor-CU为其子节点配置的网络拓扑更新相关的信息，这样，可以使IAB-node及其子节点几乎同时进行网络拓扑更新，减少因节点迁移导致的服务中断时间。
第二方面的实施例
本申请实施例提供一种消息发送方法，从第二IAB-node侧进行说明，该第三IAB-node侧的行为与第二IAB-node侧行为类似，此处不再一一举例。
在一些实施例中，第二IAB-node接收来自Donor-CU的用于第三IAB-node路径迁移的第三RRC重配置消息。
在一些实施例中，第三RRC重配置消息是由Donor-CU配置生成的，来自Donor-CU的第三RRC重配置消息可以是由Donor-CU直接发送至该第二IAB-node的，也可以是由Donor-CU发送至第一IAB-node，并由第一IAB-node转发至该第二IAB-node的，也可以是由Donor-CU发送至第一父节点，并由第一父节点转发至该第一IAB-node，再由该第一IAB-node转发至第二IAB-node的，本申请实施例并不以此作为限制。
在一些实施例中，在第一IAB-node随机接入成功(随机接入完成)时，第二IAB-node接收第一IAB-node转发的第二RRC重配置消息，并在接收到该第二RRC重配置消息时，向该第三IAB-node转发该第三RRC重配置消息；在第一IAB-node随机接入失败(也可以看作随机接入未完成或无法完成或无法正确完成)时，第二IAB-node接收第一IAB-node发送的路径迁移失败指示信息，并触发RRC重建立过程或回退到原路径配置，以下分别进行说明。
图9是第一IAB-node随机接入成功时第二IAB-node侧消息发送方法示意图，如图9所示，该方法包括：
901，第二IAB-node接收来自Donor-CU的用于第三IAB-node路径迁移的第三RRC重配置消息；
902，该第二IAB-node接收到该Donor-CU发送并由第一IAB-node转发的第二RRC重配置消息时，向该第三IAB-node转发该第三RRC重配置消息，该第二RRC重配置消息用于该第二IAB-node路径迁移。
在一些实施例中，在902前，该方法还可以包括(未图示)：该第二IAB-node接收到该Donor-CU发送并由第一IAB-node转发的第二RRC重配置消息，该第二RRC重配置消息的实施方式如前所述，此处不再赘述，该第二RRC重配置消息和该第三RRC重配置消息可以由一条下行消息承载，或者由两条下行消息分别承载，后述将会分情况进行详细说明。
在一些实施例中，在902中，在收到第二RRC重配置消息时，第二IAB-node进行路径迁移，同时触发该第二IAB-node向该第三IAB-node转发缓存的第三RRC重配置消息。由于第二IAB-node不改变父节点(父节点仍然是第一IAB-node)，第二RRC重配置消息不包含切换信息，第二IAB-node无需执行随机接入过程。
在一些实施例中，在902中，该第二IAB-node确定该第二RRC重配置消息是用于该第二IAB-node路径迁移的配置消息时，才向该第三IAB-node转发该第三RRC重配置消息。可以通过如下两种方式确定该第二RRC重配置消息是用于该第二IAB-node路径迁移，例如，该第二RRC重配置消息包含为该第二IAB-node改变传输路径配置的第二参数，或者，包含第二路径迁移指示信息。该第二参数和第二路径迁移指示信息的实施方式与前述第一参数和第一路径迁移指示信息的实施方式相同，此处不再赘述。
此外，在收到该第二RRC重配置消息时，该方法还可以包括：(未图示)该第二IAB-node向该第一IAB-node发送第二RRC重配置完成消息；以及该第二IAB-node接收该第三IAB-node发送的第三RRC重配置完成消息。可选的，还可以将该第三RRC重配置完成消息转发给该Donor-CU，其中，该第二RRC重配置完成消息和第三RRC重配置完成消息可以由一条上行消息承载，或者由两条上行消息分别承载，上述发送给Donor-CU可以是直接发送给Donor-CU，也可以是经由第一IAB节点和/或第二父节点转发给该Donor-CU，后述将会分情况进行详细说明。
由此，IAB-node在切换到新的父节点前，为其子节点配置的网络拓扑更新相关 的信息由Donor-CU发送至IAB-node并缓存在IAB-node，在IAB-node切换到新的父节点的随机接入成功时，IAB-node向其子节点转发Donor-CU为其子节点配置的网络拓扑更新相关的信息，子节点在接收到该相关的信息时，再向其子节点转发Donor-CU为其子节点配置的网络拓扑更新相关的信息，这样，IAB-node及其子节点可以几乎同时进行网络拓扑更新，减少因节点迁移导致的服务中断时间。
图10是第一IAB-node随机接入失败时第二IAB-node侧消息发送方法示意图，如图10所示，该方法包括：
1001，第二IAB-node接收来自Donor-CU的用于第三IAB-node路径迁移的第三RRC重配置消息；
1002，该第二IAB-node接收第一IAB-node随机接入失败时发送的路径迁移失败指示信息；
1003，该第二IAB-node触发RRC重建立过程。
在一些实施例中，该1001的实施方式如前所述，此处不再赘述。
在一些实施例中，在1002中，如果T304定时器超时，则表示第一IAB-node随机接入失败(也可以看作随机接入未完成或无法完成或无法正确完成)，第一IAB-node向第二IAB-node发送路径迁移失败指示信息，以使得该第二IAB-node执行RRC重建立过程，第一IAB-node可以将该第二RRC重配置消息也转发给第二IAB-node或者清除该第二RRC重配置消息，对应的，在1002中，该方法还可以包括：该第二IAB-node接收该Donor-CU发送至所述第一IAB-node，并由该第一IAB-node转发的用于该第二IAB-node路径迁移的第二RRC重配置消息。
在一些实施例中，该方法还可以包括：(未图示)该第二IAB-node向第三IAB-node转发1002中接收到的路径迁移失败指示信息，以触发该第三IAB-node执行RRC重建立。
在一些实施例中，该方法还可以包括：(未图示)该第二IAB-node向该第三IAB-node转发该第三RRC重配置消息，或者清除该第三RRC重配置消息，其具体实施方式可以参考第一IAB-node侧，此处不再一一赘述。
在一些实施例中，在1003中，该第二IAB-node触发RRC重建立过程，该RRC重建立过程可以参考现有技术中IAB-node的RRC重建立，此处不再赘述。
由此，IAB-node在切换到新的父节点的随机接入失败时，触发RRC重建立并向 其子节点指示路径迁移失败，同时其子节点也触发RRC重建立，这样，在IAB-node迁移失败时，IAB-node及其子节点可以几乎同时进行RRC重建立，减少因路径迁移失败导致的服务中断时间。
图11是第一IAB-node随机接入失败时第二IAB-node侧又一消息发送方法示意图，如图11所示，该方法包括
1101，第二IAB-node接收来自Donor-CU的用于第三IAB-node路径迁移的第三RRC重配置消息；
1102，该第二IAB-node接收该Donor-CU发送至该第一IAB-node，并由该第一IAB-node转发的用于该第二IAB-node路径迁移的第二RRC重配置消息；
1103，该第二IAB-node接收第一IAB-node随机接入失败时发送的路径迁移失败指示信息；
1104，该第二IAB-node回退到原路径配置。
在一些实施例中，该1101，1103的实施方式如前所述，此处不再赘述。
在一些实施例中，该第一IAB-node向该第二IAB-node发送该路径迁移失败指示信息以及第二RRC重配置消息，以使得该第二IAB-node回退到原路径配置；与前述附图10中的区别在于，该第二IAB-node不进行RRC重建立，即虽然收到该第二RRC重配置消息，但不执行该重配置，而仅仅执行回退到原路径配置，因此，该第一IAB-node不是可选的向该第二IAB-node转发该第二RRC重配置消息，而是必须转发，即1102是必选步骤，否则，第二IAB-node的分组数据汇聚协议PDCP会因没收到第二RRC重配置消息发生异常。
在一些实施例中，该方法还可以包括：(未图示)该第二IAB-node向该第三IAB-node转发该第三RRC重配置消息，以及第二IAB-node向第三IAB-node转发1103中接收到的路径迁移失败指示信息，以使得第三IAB-node回退到原路径配置，具体实施方式可以参考第一IAB-node侧，此处不再一一赘述。
由此，IAB-node在切换到新的父节点的随机接入失败时，触发RRC重建立，将其子节点的RRC重配置转发给子节点并向其子节点指示路径迁移失败，从而使子节点回退到原来的路径配置，这样，在IAB-node迁移失败时，IAB-node及其子节点可以同时回退到原来的路径配置中。否则，若子节点执行路径迁移并按照新的路径配置产生上行数据，这些上行数据后续将会被丢弃并由UE重新传输，导致上行数据传输 时延增加。本方法可避免因路径迁移失败导致的数据传输时间延长。
第三方面的实施例
本申请实施例提供一种消息发送方法，从Donor-CU侧进行说明。
图12是该消息发送方法一示意图，如图12所示，该方法包括：
1201，Donor-CU向第一IAB-node发送用于第二IAB-node路径迁移的第二无线资源控制(RRC)重配置消息，以使该第一IAB-node在随机接入成功时将该第二RRC重配置消息转发给该第二IAB-node；
1202，该Donor-CU向该第一IAB-node发送用于第一IAB-node路径迁移的第一无线资源控制(RRC)重配置消息。
在一些实施例中，在第二IAB-node还有子节点时，该方法还可以包括：
1203，该Donor-CU向该第二IAB-node发送用于第三IAB-node路径迁移的第三RRC重配置消息。
在一些实施例中，该Donor-CU生成该第一RRC重配置消息，该第二RRC重配置消息，该第三RRC重配置消息，该第一RRC重配置消息，该第二RRC重配置消息,该第三RRC重配置消息包含的内容和结构以及承载的实施方式可以参考第一方面和第二方面的实施例，例如，在1201～1203中，该第一RRC重配置消息，第二RRC重配置消息，该第三RRC重配置消息可以由一条下行消息承载，即该Donor-CU同时发送该第一RRC重配置消息，第二RRC重配置消息，该第三RRC重配置消息，或者由三条下行消息分别承载，即该Donor-CU先后发送该第三RRC重配置消息，第二RRC重配置消息和该第一RRC重配置消息，后述将会分情况进行详细说明。
在一些实施例中，Donor-CU向该第一IAB-node发送的行为可以是直接向该第一IAB-node发送而不经过其他中继节点，也可以是经过第一父节点转发至该第一IAB-node处，Donor-CU向该第二IAB-node发送的行为可以是直接向该第二IAB-node发送而不经过其他中继节点，也可以是经过第一父节点转发至该第一IAB-node处，再由该第一IAB-node转发至该第二IAB-node侧，本实施例并不以此作为限制。
在一些实施例中，该方法还可以包括：
1204，该Donor-CU接收来自第一IAB-node的第一RRC重配置完成消息。可选的，该Donor-CU还可以接收来自第二IAB-node的第二RRC重配置完成消息，以及 接收来自第三IAB-node的第三RRC重配置完成消息，该第一RRC重配置完成消息，该第二RRC重配置完成消息,该第三RRC重配置完成消息包含的内容和结构以及承载的实施方式可以参考第一方面和第二方面的实施例，例如，该第一RRC重配置完成消息，第二RRC重配置完成消息，该第三RRC重配置完成消息可以由一条上行消息承载，即该Donor-CU同时接收该第一RRC重配置完成消息，第二RRC重配置完成消息，该第三RRC重配置完成消息，或者由三条下行消息分别承载，即该Donor-CU先后接收该第三RRC重配置完成消息，第二RRC重配置完成消息和该第一RRC重配置完成消息。上述Donor-CU可以接收第一IAB-node或第二IAB-node或第三IAB-node直接发送的RRC重配置完成消息，也可以接收第一IAB-node或第二IAB-node或第三IAB-node发送的，经由节点转发的RRC重配置完成消息，后述将会分情况进行详细说明。
以上通过第一方面至第三方面的实施例对本申请实施例的消息发送方法做了说明。为了使本申请实施例的方法更加清楚易懂，下面通过信息交互的流程对本申请实施例的方法进行说明。
如前所述，第一RRC重配置消息，第二RRC重配置消息可以由一条下行消息承载，也可以分别由两条下行消息承载，以下分别进行说明。
实施场景一：上述RRC重配置消息分别由两条下行消息承载，且与现有方法不同之处在于，承载该第二RRC重配置消息的信令在承载该第一RRC重配置消息的信令之前发送。这样，第一IAB-node在收到第一RRC重配置消息并切换到第二父节点之前，Donor-CU为其子节点发送的RRC重配置消息已发至第一IAB-node，并由第一IAB-node缓存直至切换到第二父节点时转发。由此使得第一IAB-node及其子节点可以同时进行网络拓扑更新。
图13是该消息发送方法示意图，如图13所示，该方法包括：
1301，Donor-CU向第一IAB-node发送用于第二IAB-node路径迁移的第二无线资源控制(RRC)重配置消息；
1302，该Donor-CU向第一父节点发送用于第一IAB-node路径迁移的第一无线资源控制(RRC)重配置消息；
1303，该第一父节点将该第一RRC重配置消息转发至该第一IAB-node；
1304，该第一IAB-node对第二父节点执行随机接入；
1305，在随机接入成功时，该第一IAB-node将该第二RRC重配置消息转发至第二IAB-node；
可选的，在第二IAB-node还有子节点第三IAB-node时，该方法还可以包括：
1300，Donor-CU向第二IAB-node发送用于第三IAB-node路径迁移的第三RRC重配置消息；
1306，在第二IAB-node接收到该第二RRC重配置消息时，将该第三RRC重配置消息转发至第三IAB-node。
在一些实施例中，在1301中，该第二RRC重配置消息由第一下行F1AP消息携带，该第一IAB-node的分布单元(DU)接收该Donor-CU发送的第一下行F1AP消息，由此接收该第一下行F1AP消息中携带的该第二RRC重配置消息，例如，该第一下行F1AP消息还包含第一缓存指示信息；该第一缓存指示信息用于指示该第一IAB-node缓存该第二RRC重配置消息，直到收到后述第一指示信息后释放。作为一个示例，该第一下行F1AP消息可以是UE上下文修改请求消息。
在一些实施例中，在1302-1303中，该第一RRC重配置消息由该Donor-CU发送至该第一父节点的一个下行F1AP消息携带，并由该第一父节点将该下行F1AP消息中的第一RRC重配置消息转发至该第一IAB-node处，作为一个示例，该F1AP消息可以是UE上下文修改请求消息。上述下行F1AP消息还可以包含上述UE的第一上下文标识等，具体可以参考现有技术，此处不再一一赘述。
在一些实施例中，在1304中该第一IAB-node进行随机接入过程，该实施方式可以参考现有技术，此处不再赘述。在随机接入成功时，即该第一IAB-node的MT(MAC层)完成到第二父节点的随机接入后，在1305中，该第一IAB-node将该第二RRC重配置消息转发至第二IAB-node。具体的，该第一IAB-node的移动终端(MT)随机接入成功时，向该第一IAB-node的分布单元(DU)发送第一指示信息；该第一IAB-node的分布单元(DU)收到该第一指示信息时将该第二RRC重配置消息转发给该第二IAB-node。其中，在该第一RRC重配置消息包含为该第一IAB-node改变传输路径配置的第一参数和/或包含第一路径迁移指示信息时，表示该第一RRC重配置消息是用于第一IAB-node的路径迁移，该第一IAB-node的MT向该第一IAB-node的DU发送第一指示信息，第一参数和/或第一路径迁移指示信息的含义请参考第一 方面的实施例，此处不再赘述。
在一些实施例中，该第一RRC重配置消息还包含第一指示信息的配置信息；该第一指示信息的配置信息用于指示该第一IAB-node的MT可以在随机接入成功时，向该第一IAB-node的分布单元(DU)发送第一指示信息。在该第一RRC重配置消息包含该第一指示信息的配置信息时，该第一IAB-node的MT向该第一IAB-node的DU发送该第一指示信息；或者，该第一RRC重配置消息包含该第一参数和/或第一路径迁移指示信息，以及包含所述第一指示信息的配置信息时，该第一IAB-node的MT向该第一IAB-node的DU发送该第一指示信息。
在一些实施例中，在该第一下行F1AP消息中还包括前述第一缓存指示信息时，在1305中，该第一IAB-node的DU在收到该第一指示信息时，将该第二RRC重配置消息转发给第二IAB-node。
如前所述的第一指示信息，第一指示信息的配置信息，第一缓存指示信息，第一路径迁移指示信息等可以是在消息中新增的信息元IE，其值可以是默认值，本申请实施例并不以此作为限制。
在一些实施例中，在1300中，在一些实施例中，在1301中，该第三RRC重配置消息由第二下行F1AP消息携带，该第二IAB-node的分布单元(DU)接收该Donor-CU发送的第二下行F1AP消息，由此接收该第二下行F1AP消息中携带的该第三RRC重配置消息，例如，该第二下行F1AP消息还包含第二缓存指示信息；该第二缓存指示信息用于指示该第二IAB-node缓存该第三RRC重配置消息，直到收到上述第二指示信息后释放。
在一些实施例中，在1306中该第二IAB-node接收到该第一IAB-node转发的第二RRC重配置消息时，该第二IAB-node将该第三RRC重配置消息转发至第三IAB-node，具体的，该第二IAB-node的移动终端(MT)接收到该第二RRC重配置消息时，向该第二IAB-node的分布单元(DU)发送第二指示信息；该第二IAB-node的分布单元(DU)收到该第二指示信息时将该第三RRC重配置消息转发给该第三IAB-node。其中，在该第二RRC重配置消息包含为该第二IAB-node改变传输路径配置的第二参数和/或包含第二路径迁移指示信息时，表示该第二RRC重配置消息是用于第二IAB-node的路径迁移，该第二IAB-node的MT向该第二IAB-node的DU发送第二指示信息，第二参数和/或第二路径迁移指示信息的含义请参考第二方面的实 施例，另外，第三RRC重配置消息的结构和内容请参考第二方面的实施例，此处不再赘述。
在一些实施例中，该第二RRC重配置消息还包含第二指示信息的配置信息；该第二指示信息的配置信息用于指示该第二IAB-node可以在接收到该第二RRC重配置消息时，向该第二IAB-node的分布单元(DU)发送第二指示信息。在该第二RRC重配置消息包含该第二指示信息的配置信息时，该第二IAB-node的MT向该第二IAB-node的DU发送该第二指示信息；或者，该第二RRC重配置消息包含该第二参数和/或第二路径迁移指示信息，以及包含所述第二指示信息的配置信息时，该第二IAB-node的MT向该第二IAB-node的DU发送该第二指示信息。
在一些实施例中，在该第二下行F1AP消息中还包括前述第二缓存指示信息时，在1306中，该第二IAB-node的DU在收到该第二指示信息时，将该第三RRC重配置消息转发给第三IAB-node。
如前所述的第二指示信息，第二指示信息的配置信息，第二缓存指示信息，第二路径迁移指示信息等可以是在消息中新增的信息元IE，其值可以是默认值，本申请实施例并不以此作为限制。
在一些实施例中，在第一IAB-node在随机接入成功时，该方法还包括：
1307，该第一IAB-node向该Donor-CU发送第一RRC重配置完成消息；
1308，该第一IAB-node接收该第二IAB-node发送的第二RRC重配置完成消息；
1309，该第一IAB-node将该第二RRC重配置完成消息转发给Donor-CU；
1310，该第二IAB-node接收该第三IAB-node发送的第三RRC重配置完成消息；
1311，该第二IAB-node将该第三RRC重配置完成消息转发给该Donor-CU。
在一些实施例中，在1307中，在第一IAB-node重配置完成后，第一IAB-node将该第一RRC重配置完成消息发送给第二父节点，该第二父节点将该第一RRC重配置完成消息转发给Donor-CU，其中，该第二父节点可以向Donor-CU发送一个上行F1AP消息，由该上行F1AP消息承载该第一RRC重配置完成消息，具体可以参考现有技术。
在一些实施例中，在1308和1309中，在第二IAB-node重配置完成后，第二IAB-node将该第二RRC重配置完成消息发送给第一IAB-node，该第一IAB-node将该第二RRC重配置完成消息转发给Donor-CU，其中，该第一IAB-node可以向 Donor-CU发送第一上行F1AP消息，由该第一上行F1AP消息承载该第二RRC重配置完成消息。
在一些实施例中，在1310和1311中，在第三IAB-node重配置完成后，第三IAB-node将该第三RRC重配置完成消息发送给第二IAB-node，该第二IAB-node将该第三RRC重配置完成消息转发给Donor-CU，其中，该第二IAB-node可以向Donor-CU发送第二上行F1AP消息，由该第二上行F1AP消息承载该第三RRC重配置完成消息。
图14是该消息发送方法示意图，如图14所示，该方法包括：
1400，Donor-CU向第二IAB-node发送用于第三IAB-node路径迁移的第三RRC重配置消息；
1401，Donor-CU向第一IAB-node发送用于第二IAB-node路径迁移的第二无线RRC重配置消息；
1402，该Donor-CU向第一父节点发送用于第一IAB-node路径迁移的第一无线RRC重配置消息；
1403，该第一父节点将该第一RRC重配置消息转发至该第一IAB-node；
1404，该第一IAB-node对第二父节点执行随机接入；
其中，1400-1404的实施方式与1300-1304的实施方式相同，此处不再赘述。
在一些实施例中，该方法还可以包括：
1405，在该第一IAB-node随机接入失败时，第一IAB-node触发RRC重建立过程；
1406，该第一IAB-node向该第二IAB-node发送路径迁移失败指示信息。
1407，该第一IAB-node将该第二RRC重配置消息转发给该第二IAB-node，或者，清除该第二RRC重配置消息。
1408，该第二IAB-node在接收到该路径迁移失败指示信息时，触发RRC重建立过程；
可选的，该方法还可以包括：
1409，该第二IAB-node向该第三IAB-node转发该路径迁移失败指示信息；
1410，该第三IAB-node在接收到该路径迁移失败指示信息时，触发RRC重建立过程；
1411，该第二IAB-node向该第三IAB-node转发该第三RRC重配置消息，或者清除该第三RRC重配置消息。
在一些实施例中，在1405和1408中，在T304超时时，表示随机接入失败或未完成或未成功，该RRC重建立的过程可以参考现有技术，1406的实施方式可以参考第二方面实施例的1002，此处不再赘述，。
在一些实施例中，在1406中，在该第一RRC重配置消息包含为该第一IAB-node改变传输路径配置的第一参数和/或第一路径迁移指示信息时，该第一IAB-node向该第二IAB-node发送该路径迁移失败指示信息。
在一些实施例中，该第一RRC重配置消息还包括路径迁移失败指示信息的配置信息，该路径迁移失败指示信息的配置信息用于指示该第一IAB-node可以在随机接入失败时，向该第二IAB-node发送路径迁移失败指示信息。例如，第一IAB-node随机接入失败时，如果第一RRC重配置消息包含路径迁移失败指示信息的配置信息，该第一IAB-node向该第二IAB-node发送该路径迁移失败指示信息，或者，如果第一RRC重配置消息包含第一参数和/或第一路径迁移指示信息，以及路径迁移失败指示信息的配置信息时，该第一IAB-node向该第二IAB-node发送该路径迁移失败指示信息。
在一些实施例中，在1407中，该第一IAB-node将该第二RRC重配置消息转发给该第二IAB-node，或者，清除该第二RRC重配置消息。该步骤是可选的，本申请实施例并不以此作为限制，另外，1409-1411的实施方式与1406-1408类似，此处不再赘述。
图15是该消息发送方法示意图，如图15所示，该方法包括：
1500，Donor-CU向第二IAB-node发送用于第三IAB-node路径迁移的第三RRC重配置消息；
1501，Donor-CU向第一IAB-node发送用于第二IAB-node路径迁移的第二RRC重配置消息；
1502，该Donor-CU向第一父节点发送用于第一IAB-node路径迁移的第一RRC重配置消息；
1503，该第一父节点将该第一RRC重配置消息转发至该第一IAB-node；
1504，该第一IAB-node对第二父节点执行随机接入；
1505，在该第一IAB-node随机接入失败时，第一IAB-node触发RRC重建立过程；
1506，该第一IAB-node向该第二IAB-node发送路径迁移失败指示信息；
其中，1500-1506的实施方式与1400-1406的实施方式相同，此处不再赘述。
1507，该第一IAB-node将该第二RRC重配置消息转发给该第二IAB-node。
1508，该第二IAB-node在接收到该路径迁移失败指示信息和该第二RRC重配置消息时，不进行RRC重建立过程，而是回退到原路径配置。
1509，该第二IAB-node向该第三IAB-node转发该路径迁移失败指示信息；
1510，该第二IAB-node向该第三IAB-node转发该第三RRC重配置消息；
1511，该第三IAB-node在接收到该路径迁移失败指示信息和该第三RRC重配置消息时，不进行RRC重建立过程，而是回退到原路径配置。
在一些实施例中，与图14不同之处在于，该第一IAB-node不是可选的向该第二IAB-node转发该第二RRC重配置消息，而是必须转发，即1507是必选步骤，否则，第二IAB-node的分组数据汇聚协议PDCP会出现异常。关于第一IAB-node如何转发该第二RRC重配置消息，可参考上述1305，不再赘述。
其中1508的实施方式可以参考第二方面实施例的1104,1509-1511的实施方式与1506-1508类似，此处不再赘述。
实施场景二：与实施场景一的不同之处在于，上述各个RRC重配置消息由一条下行消息承载，由此，不仅可以减少服务中断时间，还能够节省信令开销。
图16是该消息发送方法示意图，如图16所示，该方法包括：
1601，该Donor-CU向第一父节点发送用于第一IAB-node路径迁移的第一RRC重配置消息和用于第二IAB-node路径迁移的第二RRC重配置消息；
1602，该第一父节点将该第一RRC重配置消息和该第二RRC重配置消息转发至该第一IAB-node；
1603，该第一IAB-node对第二父节点执行随机接入；
1604，在随机接入成功时，该第一IAB-node将该第二RRC重配置消息转发至第二IAB-node；
可选的，在第二IAB-node还有子节点第三IAB-node时，该方法还可以包括：
在1601中，Donor-CU向第一父节点发送用于第三IAB-node路径迁移的第三RRC重配置消息；在1602中，该第一父节点还将第三RRC重配置消息转发至该第一IAB-node，在1604中，该第一IAB-node还将第三RRC重配置消息转发至第二IAB-node；
1605，在第二IAB-node接收到该第二RRC重配置消息和该第三RRC重配置消息时，将该第三RRC重配置消息转发至第三IAB-node。
在一些实施例中，该第二RRC重配置消息由该第一RRC重配置消息携带，该第三RRC重配置消息被包含在该第二RRC重配置消息中。各个RRC重配置消息中包含的信息元内容如前所述，此处不再重复。
在1601中，Donor-CU将上述第一RRC重配置消息，第二RRC重配置消息，第三RRC重配置消息都由一条下行F1AP消息携带，作为一个示例，该下行F1AP消息可以是UE上下文修改请求消息(UE CONTEXT SETUP REQUEST)。上述UE CONTEXT SETUP REQUEST还可以包含上述UE的第一上下文标识等，具体可以参考现有技术，此处不再一一赘述。
图19A是该下行F1AP消息结构示意图，如图19A所示，第一RRC重配置消息由Donor-CU发送给第一父节点的下行F1AP消息携带，第二RRC重配置消息包含在第一RRC重配置消息中，第三RRC重配置消息包含在第二RRC重配置消息中。
另外，为了让第一IAB-node识别发送给第二IAB-node的第二RRC重配置消息，该第一RRC重配置消息还包括该第二IAB-node的标识信息。该标识信息是第二IAB-node的父节点小区标识(例如第一IAB-node的DU小区标识)以及第二IAB-node在父节点小区中的小区无线网络临时标识C-RNTI(例如第二IAB-node的MT在第一IAB-node的DU小区中的CNTI)，或者该标识信息是第二IAB-node在其父节点中的UE F1AP标识(例如第二IAB-node的MT在第一IAB-node的DU中的DU UE F1AP ID)。同样的，该第二RRC重配置消息还包含该第三IAB-node的标识信息，该标识信息是第三IAB-node的父节点小区标识(例如第二IAB-node的DU小区标识)以及第三IAB-node在父节点小区中的小区无线网络临时标识C-RNTI(例如第三IAB-node的MT在第二IAB-node的DU小区中的CNTI)，或者该标识信息是第三IAB-node在其父节点中的UE F1AP标识(例如第三IAB-node的MT在第二IAB-node的DU中的DU UE F1AP ID)。
在一些实施例中，第一父节点接收到F1AP消息后，将其中的第一RRC重配置消息发送给第一IAB-node，在1604和1605中，第一IAB-node从第一RRC重配置消息中提取第二RRC重配置消息并转发至第二IAB-node，第二IAB-node接收到第二RRC重配置消息后，从中提取第三RRC重配置消息，并转发至第三IAB-node。具体的，该第一IAB-node的移动终端(MT)随机接入成功时，将该第二RRC重配置消息发送给第一IAB-node的DU，然后转发给该第二IAB-node。其中，在该第一RRC重配置消息包含为该第一IAB-node改变传输路径配置的第一参数和/或包含第一路径迁移指示信息时，表示该第一RRC重配置消息是用于第一IAB-node的路径迁移，该第一IAB-node的MT向该第一IAB-node的DU发送第二RRC重配置消息，第一参数和/或第一路径迁移指示信息的含义请参考第一方面的实施例，此处不再赘述。该第二IAB-node的移动终端(MT)收到该第二RRC重配置消息时，将第三RRC重配置消息发送给第二IAB-node的DU，然后转发给该第三IAB-node。其中，在该第二RRC重配置消息包含为该第二IAB-node改变传输路径配置的第二参数和/或包含第二路径迁移指示信息时，表示该第二RRC重配置消息是用于第二IAB-node的路径迁移，该第二IAB-node的MT向该第二IAB-node的DU发送第三RRC重配置消息，第二参数和/或第二路径迁移指示信息的含义请参考第二方面的实施例，此处不再赘述。
另外，该第三RRC重配置消息是用于第三IAB-node的路径迁移，因此该第三RRC重配置消息包含为该第三IAB-node改变传输路径配置的第三参数，第三IAB-node接收到第三RRC配置消息后，可以进行路径迁移，路径迁移的操作可以参考现有技术，第三参数的含义与第一参数的含义类似，此处不再赘述。
在一些实施例中，在第三IAB-node还有子节点时，该第三RRC重配置消息中还可以包括用于其子节点的路径迁移的第四RRC重配置消息，该第三IAB-node在接收到第三RRC重配置消息时，将其中的第四RRC重配置消息转发给其子节点，具体的转发实施方式与第二IAB-node相同，此处不再赘述。
这样，Donor-CU无需针对第一IAB-node，第二IAB-node以及第三IAB-node分别发送一条下行F1AP消息，节省了信令开销，而且通过层层的消息转发，第一IAB-node，第二IAB-node以及第三IAB-node几乎可以同时收到各自的RRC重配置消息。另外，第一IAB-node在随机接入成功(与第二父节点随机接入成功)时，进 行消息转发，可以使得第一IAB-node，第二IAB-node以及第三IAB-node分同时进行网络拓扑的更新，减少了服务中断时间。
在一些实施例中，在第一IAB-node在随机接入成功时，该方法还可以包括：
1606，该第一IAB-node向该Donor-CU发送第一RRC重配置完成消息；
1607，该第一IAB-node接收该第二IAB-node发送的第二RRC重配置完成消息；
1608，该第一IAB-node将该第二RRC重配置完成消息转发给Donor-CU；
1609，该第二IAB-node接收该第三IAB-node发送的第三RRC重配置完成消息；
1610，该第二IAB-node将该第三RRC重配置完成消息转发给该Donor-CU。
在一些实施例中，上述1606-1610的实施方式可以参考实施场景一中的1307-1311，此处不再重复。
图17是消息发送方法又一示意图，与图16的不同之处在于，各个IAB-node的RRC重配置完成消息不是通过不同的上行消息发送的，而是由第二父节点通过同一条上行F1AP消息携带并发送给Donor-CU的，从而进一步减少信令开销，如图17所示，该方法包括：与图16中操作1601-1605相同的操作1701-1705，此外，该方法还可以包括：
1706，该第二IAB-node接收该第三IAB-node发送的第三RRC重配置完成消息；
1707，该第一IAB-node接收该第二IAB-node发送的第二RRC重配置完成消息；
1708，该第一IAB-node向该第二父节点发送第一RRC重配置完成消息；
1709，该第二父节点将该第一RRC重配置完成消息转发给Donor-CU。
在一些实施例中，在1707-1709中，该第二IAB-node将该第三RRC重配置完成消息包含在该第二RRC重配置完成消息中发送给第一IAB-node，该第一IAB-node将该第二RRC重配置完成消息包含在该第一RRC重配置完成消息中发送给第二父节点，该第二父节点向Donor-CU发送上行F1AP消息，由上行F1AP消息承载该第一RRC重配置完成消息。
图19B是该上行F1AP消息结构示意图，如图19B所示，第一RRC重配置完成消息由第二父节点发送给Donor-CU的上行F1AP消息携带，第二RRC重配置完成消息包含在第一RRC重配置完成消息中，第三RRC重配置完成消息包含在第二RRC重配置完成消息中。
另外，为了让Donor-CU识别来自第二IAB-node的第二RRC重配置完成消息， 该第一RRC重配置完成消息还包括该第二IAB-node的标识信息。同样的，该第二RRC重配置完成消息还包含该第三IAB-node的标识信息，该标识信息如前所述，此处不再赘述。
在一些实施例中，在1706-1709中，第三IAB-node完成RRC重配置，向第二IAB-node发送第三RRC重配置完成消息并执行F1传输路径迁移；第二IAB-node接收到第三RRC重配置完成消息，完成自己的RRC重配置，将第三RRC重配置完成消息包含在第二RRC重配置完成消息中发送给第一IAB-node并实现F1传输路径迁移；第一IAB-node接收到第二RRC重配置完成消息，完成自己的RRC重配置，将第二RRC重配置完成消息包含在第一RRC重配置完成消息中发送给其第二父节点，并实现F1传输路径迁移，第二父节点通过一条上行F1AP消息携带该第一RRC重配置完成消息发送给Donor-CU。
目前，对于IAB-node其子节点的上行RRC消息是通过F1AP承载，并且由回传RLC信道传输(即BAP层转发)，因此无需等待收到子节点的RRC重配置完成消息后再发送自身的RRC重配置完成消息，因此，为了通过一条上行F1AP消息携带各个IAB节点的RRC重配置完成消息，该第一RRC重配置消息中还可以包括完成消息发送时机配置信息，该完成消息发送时机配置信息用于指示该第一IAB-node在接收到子节点发送的RRC重配置完成消息后再发送自己的RRC重配置完成消息
在一些实施例中，第一IAB-node发送的第一RRC重配置完成消息是第一IAB-node使用新的F1传输路径发送的第一个上行数据。但是第一IAB-node在收到第二RRC重配置完成消息才能发送第一RRC重配置完成消息，因此第一IAB-node从收到第一RRC重配置消息到发送第一RRC重配置完成消息期间不应该使用新的F1传输路径发送其他上行数据。在1702中，第一IAB-node收到第一RRC重配置消息时，挂起所有上行传输(包括调度请求和缓存状态报告)，包括数据无线承载以及BH RLC信道的传输，在发送第一RRC重配置完成消息后，恢复数据无线承载以及BH RLC信道的传输，或者在收到第二RRC重配置完成消息后，恢复上行传输，这时，由于RRC信令消息的优先级高于数据优先级，恢复上行传输后，能保证第一RRC重配置完成消息优先发送。
上述图16-17中示出了第一IAB-node随机接入成功时各个IAB-node的信息交互，在第一IAB-node随机接入失败时，该方法还可以包括：实施场景一中的1405-1411 或1505-1511，重复之处不再赘述。
实施场景三：与实施场景二的不同之处在于Donor-CU向第一父节点发送的下行F1AP消息的消息结构不同。
以下说明该下行消息结构，图20A是该下行F1AP消息结构示意图，如图20A所示，该下行F1AP消息中携带该第一RRC重配置消息，该第一RRC重配置消息中包含Donor-CU发给该第一IAB-node的第三下行F1AP消息，第二RRC重配置消息由第三下行F1AP消息携带，该第二RRC重配置消息中包含Donor-CU发给该第二IAB-node的第四下行F1AP消息，第三RRC重配置消息由该第四下行F1AP消息携带。该第三下行F1AP消息中还包括第二IAB-node的标识信息(例如第二IAB-node的DU UE F1AP ID)，该第四下行F1AP消息中还包括第三IAB-node的标识信息(例如第三IAB-node的DU UE F1AP ID)。
图18是该消息发送方法示意图，如图18所示，该方法包括：
1801，该Donor-CU向第一父节点发送如图20A所示结构的下行F1AP消息；
1802，该第一父节点提取该第一RRC重配置消息转发至该第一IAB-node的MT；
1803，该第一IAB-node对第二父节点执行随机接入；
1804，在随机接入成功时，该第一IAB-node的MT从第一RRC重配置消息中提取第三下行F1AP消息，并向第一IAB-node的DU发送第三下行F1AP消息；
1805，第一IAB-node的DU将第三下行F1AP消息中的第二RRC重配置消息转发给第二IAB-node的MT；
1806，该第二IAB-node的MT从第二RRC重配置消息中提取第四下行F1AP消息，并向第二IAB-node的DU发送该第四下行F1AP消息；
1807，该第二IAB-node的DU将第四下行F1AP消息中的第三RRC重配置消息转发给第三IAB-node的MT；
在一些实施例中，在1804中，在该第一RRC重配置消息包含为该第一IAB-node改变传输路径配置的第一参数和/或包含第一路径迁移指示信息时，表示该第一RRC重配置消息是用于第一IAB-node的路径迁移，该第一IAB-node的MT从第一RRC重配置消息中提取第三下行F1AP消息，并向第一IAB-node的DU发送第三下行F1AP消息，第一参数和/或第一路径迁移指示信息的含义请参考第一方面的实施例，此处 不再赘述。在1806中，在该第二RRC重配置消息包含为该第二IAB-node改变传输路径配置的第二参数和/或包含第二路径迁移指示信息时，表示该第二RRC重配置消息是用于第二IAB-node的路径迁移，该第二IAB-node的MT从第二RRC重配置消息中提取第四下行F1AP消息，并向第二IAB-node的DU发送该第四下行F1AP消息，第二参数和/或第二路径迁移指示信息的含义请参考第二方面的实施例，此处不再赘述。
另外，该第三RRC重配置消息是用于第三IAB-node的路径迁移，因此该第三RRC重配置消息包含为该第三IAB-node改变传输路径配置的第三参数，第三IAB-node接收到第三RRC配置消息后，可以进行路径迁移，路径迁移的操作可以参考现有技术，第三参数的含义与第一参数的含义类似，此处不再赘述。
在一些实施例中，在第三IAB-node还有子节点时，该第三RRC重配置消息中还可以包括第五下行F1AP消息，第五下行F1AP消息中包括用于其子节点的路径迁移的第四RRC重配置消息，该第三IAB-node在接收到第三RRC重配置消息时，将其中的第四RRC重配置消息转发给其子节点，具体的转发实施方式与第二IAB-node相同，此处不再赘述。在第三IAB-node没有子节点时，该第三IAB-node在接收到第三RRC重配置消息后进行路径迁移，不需要执行转发动作，具体可以参考现有技术，此处不再赘述。
这样Donor-CU无需针对第一IAB-node，第二IAB-node以及第三IAB-node分别发送一条下行F1AP消息，节省了信令开销，而且通过层层的消息转发，第一IAB-node，第二IAB-node以及第三IAB-node几乎可以同时收到各自的RRC重配置消息。另外，第一IAB-node在随机接入成功(与第二父节点随机接入成功)时，进行消息转发，可以使得第一IAB-node，第二IAB-node以及第三IAB-node分同时进行网络拓扑的更新，减少了服务中断时间。
在一些实施例中，图20A中的下行F1AP消息可以是UE上下文修改请求消息(UE CONTEXT SETUP REQUEST)。上述UE CONTEXT SETUP REQUEST还可以包含为第一IAB-node的BH RLC信道重配置的与拓扑相关的重配置信息，该重配置信息包括：回传RLC信道映射关系重配置信息，和/或该第一IAB-node和其子节点之间的回传RLC信道修改信息。
例如，该回传RLC信道映射关系重配置信息是指第一IAB-node和第二IAB-node 之间的BH RLC信道与第一IAB-node和第二父节点之间BH RLC信道的映射关系，该回传RLC信道修改信息是指第一IAB-node和第二IAB-node之间的BH RLC信道的增加、修改、删除相关信息，例如修改相关信息包括修改该BH RLC信道的服务质量QoS参数。
本实施例与实施场景二的不同之处还在于第二父节点向Donor-CU发送的上行F1AP消息的消息结构不同。
以下说明该上行消息结构，上述第一RRC重配置完成消息，第二RRC重配置完成消息，第三RRC重配置完成消息都由一条上行F1AP消息携带，图20B是该上行F1AP消息结构示意图，如图20B所示，第三RRC重配置完成消息由第二IAB-node的第四上行F1AP消息携带，第四上行F1AP消息携带由第二RRC重配置完成消息携带，第二RRC重配置完成消息由第一IAB-node的第三上行F1AP消息携带，第三上行F1AP消息由第一RRC重配置完成消息携带，第一RRC重配置完成消息包含在第二父节点发送至Donor-CU的上行F1AP消息(例如UL RRC MESSAGE TRNASFOR)中。该第三上行F1AP消息包括第二IAB-node的标识信息，该第四上行F1AP消息包括该第三IAB-node的标识信息，该标识信息的实施方式与下行F1AP消息中的标识信息一致，此处不再赘述。
在一些实施例中，在随机接入成功时，该方法还可以包括：
1808，该第二IAB-node的DU接收该第三IAB-node的MT发送的该第三RRC重配置完成消息；
1809，该第二IAB-node的DU将该第三RRC重配置完成消息包含在第四上行F1AP消息中发送给该第二IAB-node的MT；
1810，该第IAB-node的MT将该第四上行F1AP消息包含在该第二RRC重配置完成消息中发送给第一IAB-node的DU；
1811，该第一IAB-node的DU将该第二RRC重配置完成消息包含在第三上行F1AP消息中发送给该第一IAB-node的MT；
1812，该第一IAB-node的MT将该第三上行F1AP消息包含在该第一RRC重配置完成消息中发送给第二父节点；
1813，该第二父节点向该Donor-CU发送上行F1AP消息(例如UL RRC MESSAGE TRNASFOR)，该上行F1AP消息包含第一RRC重配置完成消息。
在一些实施例中，在1808-1813中，第三IAB-node完成RRC重配置，向第二IAB-node发送第三RRC重配置完成消息并执行F1传输路径迁移；第二IAB-node接收到第三RRC重配置完成消息，完成自己的RRC重配置，将第三RRC重配置完成消息包含在第四上行F1AP消息中，并将该第四F1AP消息包含在第二RRC重配置完成消息中发送给第一IAB-node并实现F1传输路径迁移；第一IAB-node接收到第二RRC重配置完成消息，完成自己的RRC重配置，将第二RRC重配置完成消息包含在第三上行F1AP消息中，并将该第三F1AP消息包含在第一RRC重配置完成消息中发送给其第二父节点，并实现F1传输路径迁移，第二父节点通过一条上行F1AP消息携带该第一RRC重配置完成消息发送给Donor-CU。
目前，对于IAB-node其子节点的上行RRC消息是通过F1AP承载，并且由回传RLC信道传输(即BAP层转发)，因此无需等待收到子节点的RRC重配置完成消息后再发送自身的RRC重配置完成消息，因此，为了通过一条上行F1AP消息携带各个IAB节点的RRC重配置完成消息，该第一RRC重配置消息中还可以包括完成消息发送时机配置消息，该完成消息发送时机配置消息用于指示该第一IAB-node在接收到子节点发送的RRC重配置完成消息后再发送自己的RRC重配置完成消息
在一些实施例中，第一IAB-node发送的第一RRC重配置完成消息是第一IAB-node使用新的F1传输路径发送的第一个上行数据。但是第一IAB-node在收到第二RRC重配置完成消息才能发送第一RRC重配置完成消息，因此第一IAB-node从收到第一RRC重配置消息到发送第一RRC重配置完成消息期间不应该使用新的F1传输路径发送其他上行数据。在1802中，第一IAB-node收到第一RRC重配置消息时，挂起所有上行传输(包括调度请求和缓存状态报告)，包括数据无线承载以及BH RLC信道的传输，在发送完第一RRC重配置完成消息后，恢复数据无线承载以及BH RLC信道的传输，或者在收到第二RRC重配置完成消息后，恢复上行传输，这时，由于RRC信令消息的优先级高于数据优先级，恢复上行传输后，能保证第一RRC重配置完成消息优先发送。
上述图18中示出了第一IAB-node随机接入成功时各个IAB-node的信息交互，在第一IAB-node随机接入失败时，该方法还可以包括：实施场景一中的1405-1411或1505-1511，重复之处不再赘述。
值得注意的是，以上附图8-18仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图8-18的记载。
此外，以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
第四方面的实施例
本申请实施例提供一种消息发送装置。
图21是本申请实施例的消息发送装置的一个示意图，该装置例如可以是IAB系统中的IAB节点，也可以是配置于该IAB节点中的某个或某些部件或者组件。该IAB系统包括Donor设备和IAB节点，本申请实施例从第一IAB-node的一侧进行说明。其中，本申请实施例的消息发送装置的实施原理与第一方面的实施例类似，内容相同之处不再重复说明。
如图21所示，本申请实施例的消息发送装置2100包括：
第一接收单元2101，其接收来自宿主中心单元(Donor-CU)的用于第二IAB-node路径迁移的第二无线资源控制(RRC)重配置消息；其中，该第二IAB-node为该第一IAB-node的下游子节点；
第二接收单元2102，其接收来自该Donor-CU的用于该第一IAB-node路径迁移的第一RRC重配置消息；
第一发送单元2103，其在该第一IAB-node随机接入成功时，向该第二IAB-node转发该第二RRC重配置消息。
在一些实施例中，第一接收单元2101，第二接收单元2102，第一发送单元2103的实施方式请参考第一方面的实施例中801-803以及实施场景一至三中的第一IAB-node的实施方式，重复之处不再赘述。
在一些实施例中，该第二RRC重配置消息由该Donor-CU发送的第一下行F1AP消息携带。
在一些实施例中，其中，第一发送单元2103包括未图示的第一发送模块和第二 发送模块；该第一IAB-node的移动终端(MT)随机接入成功时，第一发送模块向该第一IAB-node的分布单元(DU)发送第一指示信息；该第一IAB-node的分布单元(DU)收到该第一指示信息时，第二发送模块将该第二RRC重配置消息转发给该第二IAB-node。
在一些实施例中，其中，该第一RRC重配置消息包含为该第一IAB-node改变传输路径配置的第一参数时，该第一IAB-node的MT上的第一发送模块向该第一IAB-node的DU发送第一指示信息。
在一些实施例中，其中，该为该第一IAB-node改变传输路径配置的第一参数包括为该第一IAB-node配置的默认回传RLC信道、默认BAP路由或IP地址。
在一些实施例中，其中，该第一RRC重配置消息包含第一路径迁移指示信息时，该第一IAB-node的MT上的第一发送模块向该第一IAB-node的DU发送第一指示信息；该第一路径迁移指示信息用于指示该第一RRC重配置消息是用于第一IAB-node进行路径迁移的重配置消息。
在一些实施例中，其中，该第一RRC重配置消息还包含第一指示信息的配置信息；该第一指示信息的配置信息用于指示该第一IAB-node的MT在随机接入成功时，第一发送模块向该第一IAB-node的分布单元(DU)发送第一指示信息。
在一些实施例中，其中，该第一下行F1AP消息还包含第一缓存指示信息；该第一缓存指示信息用于指示该第一IAB-node缓存该第二RRC重配置消息，直到收到该第一指示信息后释放。
在一些实施例中，其中，该第二RRC重配置消息由该第一RRC重配置消息携带。
在一些实施例中，其中，该第一RRC重配置消息还包括该第二IAB-node的标识信息。
在一些实施例中，其中，该第二RRC重配置消息由来自该Donor-CU的第三下行F1AP消息携带，该第三下行F1AP消息由该第一RRC重配置消息携带。
在一些实施例中，其中，该第三下行F1AP消息还包含该第二IAB-node的标识信息。
在一些实施例中，其中，第一发送单元2103包括未图示的第三发送模块和第四发送模块；该第一IAB-node的MT在随机接入成功时，第三发送模块向该第一IAB-node的DU发送该第三下行F1AP消息；该第一IAB-node的DU收到该第三下 行F1AP消息时，第四发送模块将该第三下行F1AP消息中的该第二RRC重配置消息转发给该第二IAB-node。
在一些实施例中，在该第一IAB-node随机接入失败时，第一发送单元2103还向该第二IAB-node发送路径迁移失败指示信息。
在一些实施例中，其中，该装置还包括：未图示的第一处理单元，其用于将该第二RRC重配置消息转发给该第二IAB-node，或者，清除该第二RRC重配置消息。
在一些实施例中，其中，该第一RRC重配置消息包含为该第一IAB-node改变传输路径配置的第一参数和/或第一路径迁移指示信息时，第一发送单元2103向该第二IAB-node发送该路径迁移失败指示信息。
在一些实施例中，其中，该第一RRC重配置消息还包括路径迁移失败指示信息的配置信息，该路径迁移失败指示信息的配置信息用于指示该第一IAB-node在随机接入失败时，向该第二IAB-node发送路径迁移失败指示信息。
在一些实施例中，其中，该第一IAB-node在随机接入成功时，该装置还包括：第二发送单元2104和第三接收单元2105(可选)；该第二发送单元2104向该Donor-CU发送第一RRC重配置完成消息；第三接收单元2105接收该第二IAB-node发送的第二RRC重配置完成消息。
在一些实施例中，第二发送单元2104将该第二RRC重配置完成消息转发给该Donor-CU，该第二RRC重配置完成消息由第一上行F1AP消息携带。
在一些实施例中，第二发送单元2104将该第二RRC重配置完成消息包含在该第一RRC重配置完成消息中转发给该Donor-CU。
在一些实施例中，第二发送单元2104包括未图示的第一接收模块，第五发送模块，第六发送模块，该第一IAB-node的DU上的第一接收模块接收该第二IAB-node发送的该第二RRC重配置完成消息；该第一IAB-node的DU上的第五发送模块将包含该第二RRC重配置完成消息的第三上行F1AP消息发送给该第一IAB-node的MT；该第一IAB-node的MT上的第六发送模块将该第三上行F1AP消息包含在该第一RRC重配置完成消息中转发给该Donor-CU。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的消息发送装置2100还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图21中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由此，IAB-node在切换到新的父节点前，为其子节点配置的网络拓扑更新相关的信息由Donor-CU发送至IAB-node并缓存在IAB-node，在IAB-node切换到新的父节点的随机接入成功时，IAB-node向其子节点转发Donor-CU为其子节点配置的网络拓扑更新相关的信息，这样，可以使IAB-node及其子节点几乎同时进行网络拓扑更新，减少因节点迁移导致的服务中断时间。
第五方面的实施例
本申请实施例提供一种消息发送装置。
图22是本申请实施例的消息发送装置的一个示意图，该装置例如可以是IAB系统中的IAB节点，也可以是配置于该IAB节点中的某个或某些部件或者组件。该IAB系统包括Donor设备和IAB节点，本申请实施例从第二IAB-node的一侧进行说明。其中，本申请实施例的消息发送装置的实施原理与第二方面的实施例类似，内容相同之处不再重复说明。
如图22所示，本申请实施例的消息发送装置2200包括：
第四接收单元2201，其接收来自Donor-CU的用于第三IAB-node路径迁移的第三RRC重配置消息；
第三发送单元2202，其接收到该Donor-CU发送并由第一IAB-node转发的第二RRC重配置消息时，向该第三IAB-node转发该第三RRC重配置消息，该第二RRC重配置消息用于该第二IAB-node路径迁移；
其中，该第三IAB-node为该第二IAB-node的下游子节点，该第二IAB-node为该第一IAB-node的下游子节点。
在一些实施例中，其中，该第三RRC重配置消息由该Donor-CU发送的第二下行F1AP消息携带。
在一些实施例中，其中，第三发送单元2202包括：未图示的第七发送模块和第八发送模块；该第二IAB-node的MT接收到该第二RRC重配置消息时，第七发送模 块向该第二IAB-node的DU发送第二指示信息；该第二IAB-node的DU收到该第二指示信息时，第八发送模块将该第三RRC重配置消息转发给该第三IAB-node。
在一些实施例中，其中，该第二RRC重配置消息包含为该第二IAB-node改变传输路径配置的第二参数时，该第二IAB-node的MT上的第七发送模块向该第二IAB-node的DU发送第二指示信息。
在一些实施例中，其中，该为该第二IAB-node改变传输路径配置的第二参数包括为该第二IAB-node配置的默认回传RLC信道、默认BAP路由或IP地址。
在一些实施例中，其中，该第二RRC重配置消息包含第二路径迁移指示信息时，该第二IAB-node的MT上的第七发送模块向该第一IAB-node的DU发送第二指示信息；该第二路径迁移指示信息用于指示该第二RRC重配置消息是用于第二IAB-node进行路径迁移的重配置消息。
在一些实施例中，本装置应用于第一IAB-node切换到新的父节点后Donor-DU改变时，则该第二RRC重配置消息是用于该第二IAB-node在Donor-DU之间的路径迁移。该第二路径迁移指示信息用于指示第二IAB-node正在进行Donor-DU之间的路径迁移，也即第二RRC消息包含第二路径迁移指示信息时表明该第二RRC重配置消息是用于第二IAB-node在不同的Donor-DU之间进行路径迁移的重配置消息。
在一些实施例中，其中，该第二RRC重配置消息还包含第二指示信息的配置信息；该第二指示信息的配置信息用于指示该第二IAB-node的MT在收到该第二RRC重配置消息时，向该第二IAB-node的分布单元(DU)发送第二指示信息。
在一些实施例中，其中，该第二下行F1AP消息还包含第二缓存指示信息；该第二缓存指示信息用于指示该第二IAB-node缓存该第三RRC重配置消息，直到收到该第二指示信息后释放。
在一些实施例中，其中，该第三RRC重配置消息被包含在由该Donor-CU发送并由该第一IAB-node转发的该第二RRC重配置消息中。
在一些实施例中，其中，该第二RRC重配置消息还包含该第三IAB-node的标识信息。
在一些实施例中，其中，该第三RRC重配置消息由该Donor-CU发送的第四下行F1AP消息携带，该第四下行F1AP消息由该第三RRC重配置消息携带。
在一些实施例中，其中，该第四下行F1AP消息还包含该第三IAB-node的标识 信息。
在一些实施例中，第三发送单元2202包括：未图示的第九发送模块和第十发送模块；该第二IAB-node的MT在接收到由Donor-CU发送并由第一IAB-node转发的该第二RRC重配置消息时，第九发送模块向该第二IAB-node的DU发送该第四下行F1AP消息；
该第二IAB-node的DU收到该第四下行F1AP消息时，第十发送模块将该第四下行F1AP消息中的该第三RRC重配置消息转发给该第三IAB-node。
在一些实施例中，其中，该第二IAB-node接收到该第二RRC重配置消息时，该装置还包括：第四发送单元2203和第五接收单元2204(可选)；第四发送单元2203向该第一IAB-node发送第二RRC重配置完成消息；
第五接收单元2204接收该第三IAB-node发送的第三RRC重配置完成消息。
在一些实施例中，第四发送单元2203还用于将该第三RRC重配置完成消息转发给该Donor-CU，该第三RRC重配置完成消息由第二上行F1AP消息携带。
在一些实施例中，第四发送单元2203还用于将该第三RRC重配置完成消息包含在该第二RRC重配置完成消息中转发给该Donor-CU。
在一些实施例中，第四发送单元2203还包括未图示的第二接收模块，第十一发送模块和第十二发送模块；该第二IAB-node的DU上的第二接收模块接收该第三IAB-node发送的该第三RRC重配置完成消息；该第二IAB-node的DU上的第十一发送模块将包含该第三RRC重配置完成消息的第四上行F1AP消息发送给该第二IAB-node的MT；该第IAB-node的MT上的第十二发送模块将该第四上行F1AP消息包含在该第二RRC重配置完成消息中转发给该Donor-CU。
由此，IAB-node在切换到新的父节点前，为其子节点配置的网络拓扑更新相关的信息由Donor-CU发送至IAB-node并缓存在IAB-node，在IAB-node切换到新的父节点的随机接入成功时，IAB-node向其子节点转发Donor-CU为其子节点配置的网络拓扑更新相关的信息，子节点在接收到该相关的信息时，再向其子节点转发Donor-CU为其子节点配置的网络拓扑更新相关的信息，这样，IAB-node及其子节点可以几乎同时进行网络拓扑更新，减少因节点迁移导致的服务中断时间。
图23是本申请实施例的消息发送装置的一个示意图，该装置例如可以是IAB系统中的IAB节点，也可以是配置于该IAB节点中的某个或某些部件或者组件。该IAB 系统包括Donor设备和IAB节点，本申请实施例从第二IAB-node的一侧进行说明。其中，本申请实施例的消息发送装置的实施原理与第二方面的实施例类似，内容相同之处不再重复说明。
如图23所示，本申请实施例的消息发送装置2300包括：
第六接收单元2301，其接收来自Donor-CU的用于第三IAB-node路径迁移的第三RRC重配置消息；
第七接收单元2302，其接收第一IAB-node随机接入失败时发送的路径迁移失败指示信息；
第二处理单元2303，其触发RRC重建立过程或回退到原路径配置；
其中，该第三IAB-node为该第二IAB-node的下游子节点，该第二IAB-node为该第一IAB-node的下游子节点。
在一些实施例中，该装置还包括：第五发送单元2304，其向该第三IAB-node转发该路径迁移失败指示信息。
在一些实施例中，该第二处理单元2303还用于向该第三IAB-node转发该第三RRC重配置消息，或者清除该第三RRC重配置消息。
在一些实施例中，其中，该第三RRC重配置消息由该Donor-CU发送的第二下行F1AP消息承载；第二处理单元2303还包括：第十三发送模块和第十四发送模块；该第二IAB-node的MT上的第十三发送模块向该第二IAB-node的DU发送第二指示信息；该第二IAB-node的DU收到该第二指示信息时，第十四发送模块将由该第二下行F1AP消息承载的第三RRC重配置消息转发给该第三IAB-node。
在一些实施例中，该第六接收单元2301还用于接收该Donor-CU发送至该第一IAB-node，并由该第一IAB-node转发的用于该第二IAB-node路径迁移的第二RRC重配置消息。
由此，IAB-node在切换到新的父节点的随机接入失败时，触发RRC重建立并向其子节点指示路径迁移失败，同时其子节点也触发RRC重建立，这样，在IAB-node迁移失败时，IAB-node及其子节点可以几乎同时进行RRC重建立，减少因路径迁移失败导致的服务中断时间。或者，
IAB-node在切换到新的父节点的随机接入失败时，触发RRC重建立，将其子节点的RRC重配置转发给子节点并向其子节点指示路径迁移失败，从而使子节点回退 到原来的路径配置，这样，在IAB-node迁移失败时，IAB-node及其子节点可以同时回退到原来的路径配置中。否则，若子节点执行路径迁移并按照新的路径配置产生上行数据，这些上行数据后续将会被丢弃并由UE重新传输，导致上行数据传输时延增加。本方法可避免因路径迁移失败导致的数据传输时间延长。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的消息发送装置2200-2300还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图22-23中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
第六方面的实施例
本申请实施例提供一种消息发送装置。
图24是本申请实施例的消息发送装置的一个示意图，该装置例如可以是IAB系统中的Donor设备，也可以是配置于该Donor设备中的某个或某些部件或者组件。该IAB系统包括Donor设备和IAB节点，本申请实施例从Donor-CU的一侧进行说明。其中，本申请实施例的消息发送装置的实施原理与第三方面的实施例类似，内容相同之处不再重复说明。
图24是本申请实施例的消息发送装置的一个示意图，如图24所示，本申请实施例的消息发送装置2400包括：
第六发送单元2401，其用于向第一IAB-node发送用于第二IAB-node路径迁移的第二无线资源控制(RRC)重配置消息，以使该第一IAB-node在随机接入成功时将该第二RRC重配置消息转发给该第二IAB-node；
第七发送单元2402，其用于向该第一IAB-node发送用于第一IAB-node路径迁移的第一无线资源控制(RRC)重配置消息。
在一些实施例中，其中，该第二RRC重配置消息由该Donor-CU发送的第一下行F1AP消息携带。
在一些实施例中，其中，该第一RRC重配置消息包含为该第一IAB-node改变传 输路径配置的第一参数。
在一些实施例中，其中，该第一参数包括为该第一IAB-node配置的默认回传RLC信道、默认BAP路由或IP地址。
在一些实施例中，其中，该第一RRC重配置消息还包含第一路径迁移指示信息；该第一路径迁移指示信息用于指示该第一RRC重配置消息是用于第一IAB-node进行路径迁移的重配置消息。
在一些实施例中，其中，该第一RRC重配置消息还包含第一指示信息的配置信息；该第一指示信息的配置信息用于指示该第一IAB-node的MT在随机接入成功时，向该第一IAB-node的分布单元(DU)发送第一指示信息。
在一些实施例中，其中，该第一下行F1AP消息还包含第一缓存指示信息；该第一缓存指示信息用于指示该第一IAB-node缓存该第二RRC重配置消息，直到收到该第一指示信息后释放。
在一些实施例中，其中，该第二RRC重配置消息由该第一RRC重配置消息携带。
在一些实施例中，其中，该第一RRC重配置消息还包含该第二IAB-node的标识信息。
在一些实施例中，其中，该第二RRC重配置消息由该第三下行F1AP消息携带，该第三下行F1AP消息由该第一RRC重配置消息携带。
在一些实施例中，其中，该第三下行F1AP消息还包含该第二IAB-node的标识信息。
在一些实施例中，其中，该第一RRC重配置消息还包含路径迁移失败指示信息的配置信息，该路径迁移失败指示信息的配置信息用于指示该第一IAB-node在随机接入失败时，向该第二IAB-node发送路径迁移失败指示信息。
在一些实施例中，其中，该第二RRC重配置消息包含为该第二IAB-node改变传输路径配置的第二参数。
在一些实施例中，其中，该第二参数包括为该第二IAB-node配置的默认回传RLC信道、默认BAP路由或IP地址。
在一些实施例中，其中，该第二RRC重配置消息还包含第二路径迁移指示信息；该第二路径迁移指示信息用于指示该第二RRC重配置消息是用于第二IAB-node进行路径迁移的重配置消息。
在一些实施例中，其中，该第二RRC重配置消息还包含第二指示信息的配置信息；该第二指示信息的配置信息用于指示该第二IAB-node的MT在收到该第二RRC重配置消息时，向该第二IAB-node的DU发送第二指示信息。
在一些实施例中，其中，该装置还包括：第八发送单元2403(可选)，其用于向该第二IAB-node发送用于第三IAB-node路径迁移的第三RRC重配置消息。
在一些实施例中，其中，该第三RRC重配置消息由该Donor-CU发送的第二下行F1AP消息携带。
在一些实施例中，其中，该第二下行F1AP消息还包含第二缓存指示信息；该第二缓存指示信息用于指示该第二IAB-node缓存该第三RRC重配置消息，直到收到该第二指示信息后释放。
在一些实施例中，其中，该第三RRC重配置消息被包含在由该Donor-CU发送并由该第一IAB-node转发的该第二RRC重配置消息中。
在一些实施例中，其中，该第二RRC重配置消息还包含该第三IAB-node的标识信息。
在一些实施例中，其中，该第三RRC重配置消息由第四下行F1AP消息携带，该第四下行F1AP消息由该第二RRC重配置消息携带。
在一些实施例中，其中，该第四下行F1AP消息还包含该第三IAB-node的标识信息。
在一些实施例中，其特征在于，该装置还包括：第八接收单元(可选，未图示)，其接收该第一IAB-node发送的第一RRC重配置完成消息。
在一些实施例中，该第八接收单元还用于接收该第二IAB-node发送的第二RRC重配置完成消息，该第二RRC重配置完成消息由该第一IAB-node发送的第一上行F1AP消息携带。
在一些实施例中，该第一RRC重配置完成消息中还包含第三上行F1AP消息，该第三上行F1AP消息包含第二RRC重配置完成消息。
在一些实施例中，其特征在于，该第一RRC重配置完成消息还包含第二RRC重配置消息。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的消息发送装置2400还可以包括其它部件或者模块，关于这 些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图24中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
第七方面的实施例
本申请实施例提供了一种通信系统，图25是该通信系统2500的示意图，如图25所示，该通信系统2500包括Donor设备2500、IAB节点2501，2502，2503，2504，2505，其中，IAB节点2503为迁移IAB节点(第一IAB-node)，IAB节点2501作为IAB节点2503的源节点(第一父节点)，IAB节点2502作为IAB节点2503的目标节点(第二父节点)，Donor设备2500作为Donor-CU，IAB节点2504是IAB节点2503的下游子节点，IAB节点2505是IAB节点2504的下游子节点。
为简单起见，图25仅以上述Donor设备和IAB节点为例进行说明，但本申请实施例不限于此。关于Donro设备、IAB节点的网络架构可以参考相关技术，此处省略说明。
在一些实施例中，IAB节点2503被配置为执行第一方面的实施例中第一IAB-node所执行的方法，可以包含图21的装置。在一些实施例中，IAB节点2504被配置为执行第二方面的实施例中第二IAB-node所执行的方法，可以包含图22或23的装置。在一些实施例中，Donor设备2500被配置为执行第三方面的实施例中Donor-CU所执行的方法，可以包括图24的装置。关于Donor设备2500各IAB节点的相关内容请参见第一方面至第三方面的实施例，此处省略说明。
在一些实施例中，IAB节点2501，对应第一父节点，其用于接收Donor-CU发送的第一方面实施例中的包含第一RRC重配置消息的下行F1AP消息，或者接收下行F1AP消息，该下行F1AP消息的结构如图19A或20A所示，其还用于向IAB节点2503转发该F1AP消息中的第一RRC重配置消息。
在一些实施例中，IAB节点2502，对应第二父节点，其用于接收IAB节点2503发送的第一RRC重配置完成消息，并将该第一RRC重配置完成消息包含在上行F1AP消息中发送给Donor-CU，该上行F1AP消息的结构如图19B或20B所示。
本申请实施例还提供一种IAB节点。
图26是本申请实施例的IAB节点的示意图。如图26所示，该IAB节点2600可以包括处理器2601和存储器2602；存储器2602存储有数据和程序，并耦合到处理器2601。值得注意的是，该图是示例性的；还可以使用其它类型的结构，来补充或代替该结构，以实现电信功能或其它功能。
例如，处理器2601可以被配置为执行程序而实现如第一或第二方面的实施例中的IAB-node或第一父节点或第二父节点执行的方法。
如图26所示，该IAB节点2600还可以包括：通信模块2603、输入单元2604、显示器2605、电源2606。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，IAB节点2600也并不是必须要包括图26中所示的所有部件，上述部件并不是必需的；此外，IAB节点2600还可以包括图26中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种Donor设备。
图27是本申请实施例的Donor设备的示意图。如图27所示，Donor设备2700可以包括：处理器(例如中央处理器CPU)2701和存储器2702；存储器2702耦合到处理器2701。其中该存储器2702可存储各种数据；此外还存储信息处理的程序，并且在中央处理器2701的控制下执行该程序。
例如，处理器2701可以被配置为执行程序而实现如第三方面的实施例中的方法。
此外，如图27所示，Donor设备2700还可以包括：收发机2703和天线2704等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，Donor设备2700也并不是必须要包括图27中所示的所有部件；此外，Donor设备2700还可以包括图27中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机可读程序，其中当在IAB节点中执行所述程序时，所述程序使得计算机在所述IAB节点中执行第一或第二方面的实施例中的方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在IAB节点中执行第一或第二方面的实施例中的方法。
本申请实施例还提供一种计算机可读程序，其中当在Donor设备中执行所述程序时，所述程序使得计算机在所述Donor设备中执行第三方面的实施例中的方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在Donor设备中执行第三方面的实施例中的方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。逻辑部件例如现场可编程逻辑部件、微处理器、计算机中使用的处理器等。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本 申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于本实施例公开的上述实施方式，还公开了如下的附记：
1.一种消息发送方法，其特征在于，所述方法包括：
第一集成的接入和回传节点(IAB-node)接收来自宿主中心单元(Donor-CU)的用于第二IAB-node路径迁移的第二无线资源控制(RRC)重配置消息；其中，所述第二IAB-node为所述第一IAB-node的下游子节点；
所述第一IAB-node接收来自所述Donor-CU的用于所述第一IAB-node路径迁移的第一RRC重配置消息；
所述第一IAB-node在随机接入成功时，向所述第二IAB-node转发所述第二RRC重配置消息。
2.根据附记1所述的方法，其中，所述第二RRC重配置消息由所述Donor-CU发送的第一下行F1AP消息携带。
3.根据附记2所述的方法，其中，所述第一IAB-node在随机接入成功时，向所述第二IAB-node转发所述第二RRC重配置消息的步骤包括：
所述第一IAB-node的移动终端(MT)随机接入成功时，向所述第一IAB-node的分布单元(DU)发送第一指示信息；
所述第一IAB-node的分布单元(DU)收到所述第一指示信息时将所述第二RRC重配置消息转发给所述第二IAB-node。
4.根据附记3所述的方法，其中，所述第一RRC重配置消息包含为所述第一IAB-node改变传输路径配置的第一参数时，所述第一IAB-node的MT向所述第一IAB-node的DU发送第一指示信息。
5.根据附记4所述的方法，其中，所述为所述第一IAB-node改变传输路径配置的第一参数包括为所述第一IAB-node配置的默认回传RLC信道、默认BAP路由或IP地址。
6.根据附记3所述的方法，其中，所述第一RRC重配置消息包含第一路径迁移指示信息时，所述第一IAB-node的MT向所述第二IAB-node的DU发送所述第一指示信息；所述第一路径迁移指示信息指示所述第一RRC重配置消息是用于第一IAB-node进行路径迁移的重配置消息。
7.根据附记3所述的方法，其中，所述第一RRC重配置消息还包含第一指示信息的配置信息；所述第一指示信息的配置信息用于指示所述第一IAB-node的MT在随机接入成功时，向所述第一IAB-node的分布单元(DU)发送第一指示信息。
8.根据附记4所述的方法，其中，所述第一下行F1AP消息还包含第一缓存指示信息；所述第一缓存指示信息用于指示所述第一IAB-node缓存所述第二RRC重配置消息，直到收到所述第一指示信息后释放。
9.根据附记1所述的方法，其中，所述第二RRC重配置消息由所述第一RRC重配置消息携带。
10.根据附记9所述的方法，其中，所述第一RRC重配置消息还包括所述第二IAB-node的标识信息。
11.根据附记1所述的方法，其中，所述第二RRC重配置消息由来自所述Donor-CU的第三下行F1AP消息携带，，所述第三下行F1AP消息由所述第一RRC重配置消息携带。
12.根据附记11所述的方法，其中，所述第三下行F1AP消息还包含所述第二IAB-node的标识信息。
13.根据附记11所述的方法，其中，所述第一IAB-node在随机接入成功时，向所述第二IAB-node转发所述第二RRC重配置消息的步骤，包括：
所述第一IAB-node的MT在随机接入成功时，向所述第一IAB-node的DU发送所述第三下行F1AP消息；
所述第一IAB-node的DU收到所述第三下行F1AP消息时，将所述第三下行F1AP消息中的所述第二RRC重配置消息转发给所述第二IAB-node。
14.根据附记1所述的方法，其中，所述方法还包括：
在所述第一IAB-node随机接入失败时，向所述第二IAB-node发送路径迁移失败指示信息。
15.根据附记14所述的方法，其中，所述方法还包括：
所述第一IAB-node将所述第二RRC重配置消息转发给所述第二IAB-node，或者，清除所述第二RRC重配置消息。
16.根据附记14所述的方法，其中，所述第一RRC重配置消息包含为所述第一IAB-node改变传输路径配置的第一参数和/或第一路径迁移指示信息时，向所述第二 IAB-node发送所述路径迁移失败指示信息。
17.根据附记14所述的方法，其中，所述第一RRC重配置消息还包括路径迁移失败指示信息的配置信息，所述路径迁移失败指示信息的配置信息用于指示所述第一IAB-node在随机接入失败时，向所述第二IAB-node发送路径迁移失败指示信息。
18.根据附记1所述的方法，其中，所述第一IAB-node在随机接入成功时，所述方法还包括：
所述第一IAB-node向所述Donor-CU发送第一RRC重配置完成消息；
所述第一IAB-node接收所述第二IAB-node发送的第二RRC重配置完成消息。
19.根据附记18所述的方法，所述方法还包括：
所述第一IAB-node将所述第二RRC重配置完成消息转发给所述Donor-CU，所述第二RRC重配置完成消息由第一上行F1AP消息携带。
20.根据附记18所述的方法，其中，所述方法还包括：
所述第一IAB-node将所述第二RRC重配置完成消息包含在所述第一RRC重配置完成消息中转发给所述Donor-CU。
21.根据附记18所述的方法，其中，所述方法还包括：
所述第一IAB-node的DU接收所述第二IAB-node发送的所述第二RRC重配置完成消息；
所述第一IAB-node的DU将包含所述第二RRC重配置完成消息的第三上行F1AP消息发送给所述第一IAB-node的MT；
所述第一IAB-node的MT将所述第三上行F1AP消息包含在所述第一RRC重配置完成消息中转发给所述Donor-CU。
22.一种消息发送方法，其特征在于，所述方法包括：
第二IAB-node接收来自Donor-CU的用于第三IAB-node路径迁移的第三RRC重配置消息；
所述第二IAB-node接收到所述Donor-CU发送并由第一IAB-node转发的第二RRC重配置消息时，向所述第三IAB-node转发所述第三RRC重配置消息，所述第二RRC重配置消息用于所述第二IAB-node路径迁移；
其中，所述第三IAB-node为所述第二IAB-node的下游子节点，所述第二IAB-node为所述第一IAB-node的下游子节点。
23.根据附记22所述的方法，其中，所述第三RRC重配置消息由所述Donor-CU发送的第二下行F1AP消息携带。
24.根据附记22所述的方法，其中，第二IAB-node接收到所述Donor-CU发送并由第一IAB-node转发的所述第二RRC重配置消息时，向所述第三IAB-node转发所述第三RRC重配置消息的步骤，包括：
所述第二IAB-node的MT接收到所述第二RRC重配置消息时，向所述第二IAB-node的DU发送第二指示信息；
所述第二IAB-node的DU收到所述第二指示信息时将所述第三RRC重配置消息转发给所述第三IAB-node。
25.根据附记24所述的方法，其中，所述第二RRC重配置消息包含为所述第二IAB-node改变传输路径配置的第二参数时，所述第二IAB-node的MT向所述第二IAB-node的DU发送第二指示信息。
26.根据附记25所述的方法，其中，所述为所述第二IAB-node改变传输路径配置的第二参数包括为所述第二IAB-node配置的默认回传RLC信道、默认BAP路由或IP地址。
27.根据附记24所述的方法，其中，所述第二RRC重配置消息包含第二路径迁移指示信息时，所述第二IAB-node的MT向所述第二IAB-node的DU发送所述第二指示信息；所述第二路径迁移指示信息用于指示所述第二RRC重配置消息是用于第二IAB-node进行路径迁移的重配置消息。
28.根据附记24所述的方法，其中，所述第二RRC重配置消息还包含第二指示信息的配置信息；所述第二指示信息的配置信息用于指示所述第二IAB-node的MT在收到所述第二RRC重配置消息时，向所述第二IAB-node的分布单元(DU)发送第二指示信息。
29.根据附记23所述的方法，其中，所述第二下行F1AP消息还包含第二缓存指示信息；所述第二缓存指示信息用于指示所述第二IAB-node缓存所述第三RRC重配置消息，直到收到所述第二指示信息后释放。
30.根据附记22所述的方法，其中，所述第三RRC重配置消息被包含在由所述Donor-CU发送并由所述第一IAB-node转发的所述第二RRC重配置消息中。
31.根据附记30所述的方法，其中，所述第二RRC重配置消息还包含所述第三 IAB-node的标识信息。
32.根据附记22所述的方法，其中，所述第三RRC重配置消息由所述Donor-CU发送的第四下行F1AP消息携带，所述第四下行F1AP消息由所述第三RRC重配置消息携带。
33.根据附记32所述的方法，其中，所述第四下行F1AP消息还包含所述第三IAB-node的标识信息。
34.根据附记32所述的方法，其中，第二IAB-node接收到由Donor-CU发送并由第一IAB-node转发的所述第二RRC重配置消息时，向所述第三IAB-node转发所述第三RRC重配置消息的步骤，包括：
所述第二IAB-node的MT在接收到由Donor-CU发送并由第一IAB-node转发的所述第二RRC重配置消息时，向所述第二IAB-node的DU发送所述第四下行F1AP消息；
所述第二IAB-node的DU收到所述第四下行F1AP消息时，将所述第四下行F1AP消息中的所述第三RRC重配置消息转发给所述第三IAB-node。
35.根据附记22所述的方法，其中，所述第二IAB-node接收到所述第二RRC重配置消息时，所述方法还包括：
所述第二IAB-node向所述第一IAB-node发送第二RRC重配置完成消息；
所述第二IAB-node接收所述第三IAB-node发送的第三RRC重配置完成消息。
36.根据附记35所述的方法，所述方法还包括：
所述第二IAB-node将所述第三RRC重配置完成消息转发给所述Donor-CU，所述第三RRC重配置完成消息由第二上行F1AP消息携带。
37.根据附记36所述的方法，其中，所述方法还包括：
所述第二IAB-node将所述第三RRC重配置完成消息包含在所述第二RRC重配置完成消息中转发给所述Donor-CU。
38.根据附记35所述的方法，其中，所述方法还包括：
所述第二IAB-node的DU接收所述第三IAB-node发送的所述第三RRC重配置完成消息；
所述第二IAB-node的DU将包含所述第三RRC重配置完成消息的第四上行F1AP消息发送给所述第二IAB-node的MT；
所述第IAB-node的MT将所述第四上行F1AP消息包含在所述第二RRC重配置完成消息中转发给所述Donor-CU。
39.一种消息发送方法，其特征在于，所述方法包括：
第二IAB-node接收来自Donor-CU的用于第三IAB-node路径迁移的第三RRC重配置消息；
所述第二IAB-node接收第一IAB-node随机接入失败时发送的路径迁移失败指示信息；
所述第二IAB-node触发RRC重建立过程或回退到原路径配置；
其中，所述第三IAB-node为所述第二IAB-node的下游子节点，所述第二IAB-node为所述第一IAB-node的下游子节点。
40.根据附记39所述的方法，其中，所述方法还包括：
所述第二IAB-node向所述第三IAB-node转发所述路径迁移失败指示信息。
41.根据附记39所述的方法，其中，所述方法还包括：
所述第二IAB-node向所述第三IAB-node转发所述第三RRC重配置消息，或者清除所述第三RRC重配置消息。
42.根据附记41所述的方法，其中，所述第三RRC重配置消息由所述Donor-CU发送的第二下行F1AP消息承载；转发所述第三RRC重配置消息的步骤包括：
所述第二IAB-node的MT向所述第二IAB-node的DU发送第二指示信息；
所述第二IAB-node的DU收到所述第二指示信息时，将由所述第二下行F1AP消息承载的第三RRC重配置消息转发给所述第三IAB-node。
43.根据附记39所述的方法，其中，所述方法还包括：
所述第二IAB-node接收所述Donor-CU发送至所述第一IAB-node，并由所述第一IAB-node转发的用于所述第二IAB-node路径迁移的第二RRC重配置消息。
44.一种消息发送方法，其特征在于，所述方法包括：
Donor-CU向第一IAB-node发送用于第二IAB-node路径迁移的第二无线资源控制(RRC)重配置消息，以使所述第一IAB-node在随机接入成功时将所述第二RRC重配置消息转发给所述第二IAB-node；
所述Donor-CU向所述第一IAB-node发送用于第一IAB-node路径迁移的第一无线资源控制(RRC)重配置消息。
45.根据附记44所述的方法，其中，所述第二RRC重配置消息由所述Donor-CU发送的第一下行F1AP消息携带。
46.根据附记45所述的方法，其中，所述第一RRC重配置消息包含为所述第一IAB-node改变传输路径配置的第一参数。
47.根据附记46所述的方法，其中，所述第一参数包括为所述第一IAB-node配置的默认回传RLC信道、默认BAP路由或IP地址。
48.根据附记45所述的方法，其中，所述第一RRC重配置消息包含第一路径迁移指示信息；所述第一路径迁移指示信息用于指示所述第一RRC重配置消息是用于第一IAB-node进行路径迁移的重配置消息。
49.根据附记45所述的方法，其中，所述第一RRC重配置消息还包含第一指示信息的配置信息；所述第一指示信息的配置信息用于指示所述第一IAB-node的MT在随机接入成功时，向所述第一IAB-node的分布单元(DU)发送第一指示信息。
50.根据附记45所述的方法，其中，所述第一下行F1AP消息还包含第一缓存指示信息；所述第一缓存指示信息用于指示所述第一IAB-node缓存所述第二RRC重配置消息，直到收到所述第一指示信息后释放。
51.根据附记44所述的方法，其中，所述第二RRC重配置消息由所述第一RRC重配置消息携带。
52.根据附记51所述的方法，其中，所述第一RRC重配置消息还包含所述第二IAB-node的标识信息。
53.根据附记44所述的方法，其中，所述第二RRC重配置消息由所述第三下行F1AP消息携带，所述第三下行F1AP消息由所述第一RRC重配置消息携带。
54.根据附记53所述的方法，其中，所述第三下行F1AP消息还包含所述第二IAB-node的标识信息。
55.根据附记44所述的方法，其中，所述第一RRC重配置消息还包含路径迁移失败指示信息的配置信息，所述路径迁移失败指示信息的配置信息用于指示所述第一IAB-node在随机接入失败时，向所述第二IAB-node发送路径迁移失败指示信息。
56.根据附记44所述的方法，其中，所述第二RRC重配置消息包含为所述第二IAB-node改变传输路径配置的第二参数。
57.根据附记56所述的方法，其中，所述第二参数包括为所述第二IAB-node配 置的默认回传RLC信道、默认BAP路由或IP地址。
58.根据附记55所述的方法，其中，所述第二RRC重配置消息包含第二路径迁移指示信息；所述第二路径迁移指示信息用于指示所述第二RRC重配置消息是用于第二IAB-node进行路径迁移的重配置消息。
59.根据附记56所述的方法，其中，所述第二RRC重配置消息还包含第二指示信息的配置信息；所述第二指示信息的配置信息用于指示所述第二IAB-node的MT在收到所述第二RRC重配置消息时，向所述第二IAB-node的DU发送第二指示信息。
60.根据附记44所述的方法，其中，所述方法还包括：
所述Donor-CU向所述第二IAB-node发送用于第三IAB-node路径迁移的第三RRC重配置消息。
61.根据附记60所述的方法，其中，所述第三RRC重配置消息由所述Donor-CU发送的第二下行F1AP消息携带。
62.根据附记61所述的方法，其中，所述第二下行F1AP消息还包含第二缓存指示信息；所述第二缓存指示信息用于指示所述第二IAB-node缓存所述第三RRC重配置消息，直到收到所述第二指示信息后释放。
63.根据附记60所述的方法，其中，所述第三RRC重配置消息被包含在由所述Donor-CU发送并由所述第一IAB-node转发的所述第二RRC重配置消息中。
64.根据附记63所述的方法，其中，所述第二RRC重配置消息还包含所述第三IAB-node的标识信息。
65.根据附记60所述的方法，其中，所述第三RRC重配置消息由第四下行F1AP消息携带，所述第四下行F1AP消息由所述第二RRC重配置消息携带。
66.根据附记65所述的方法，其中，所述第四下行F1AP消息还包含所述第三IAB-node的标识信息。
67.根据附记44所述的方法，其特征在于，所述方法还包括：
所述Donor-CU接收所述第一IAB-node发送的第一RRC重配置完成消息。
68.根据附记67所述的方法，其特征在于，所述方法还包括：
所述Donor-CU接收所述第二IAB-node发送的第二RRC重配置完成消息，所述第二RRC重配置完成消息由所述第一IAB-node发送的第一上行F1AP消息携带。
69.根据附记67所述的方法，其特征在于，所述第一RRC重配置完成消息中还 包含第三上行F1AP消息，所述第三上行F1AP消息包含第二RRC重配置完成消息。
70.根据附记67所述的方法，其特征在于，所述第一RRC重配置完成消息还包含第二RRC重配置消息。
71.一种Donor设备，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记44至70任一项所述的方法。
72.一种IAB-node，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记1至43任一项所述的方法。
73.一种通信系统，包括Donor设备、第一IAB-node、第二IAB-node，其中，所述Donor设备被配置为执行附记44至70任一项所述的方法，所述第一IAB-node被配置为执行附记1至21任一项所述的方法，所述第二IAB-node被配置为执行附记22至43任一项所述的方法。

Claims (20)

  1. 一种消息发送装置，应用于第一集成的接入和回传节点(IAB-node)，其特征在于，所述装置包括：
    第一接收单元，其接收来自宿主中心单元(Donor-CU)的用于第二IAB-node路径迁移的第二无线资源控制(RRC)重配置消息；其中，所述第二IAB-node为所述第一IAB-node的下游子节点；
    第二接收单元，其接收来自所述Donor-CU的用于所述第一IAB-node路径迁移的第一RRC重配置消息；
    第一发送单元，其在第一IAB-node随机接入成功时，向所述第二IAB-node转发所述第二RRC重配置消息。
  2. 根据权利要求1所述的装置，其中，所述第二RRC重配置消息由所述Donor-CU发送的第一下行F1AP消息携带。
  3. 根据权利要求2所述的装置，其中，所述第一发送单元包括：第一发送模块和第二发送模块；
    所述第一IAB-node的移动终端(MT)随机接入成功时，所述第一发送模块向所述第一IAB-node的分布单元(DU)发送第一指示信息；
    所述第一IAB-node的分布单元(DU)收到所述第一指示信息时，所述第二发送模块将所述第二RRC重配置消息转发给所述第二IAB-node。
  4. 根据权利要求3所述的装置，其中，所述第一RRC重配置消息包含为所述第一IAB-node改变传输路径配置的第一参数时，所述第一IAB-node的MT上的所述第一发送模块向所述第一IAB-node的DU发送第一指示信息。
  5. 根据权利要求4所述的装置，其中，所述为所述第一IAB-node改变传输路径配置的第一参数包括为所述第一IAB-node配置的默认回传RLC信道、默认BAP路由或IP地址。
  6. 根据权利要求3所述的装置，其中，所述第一RRC重配置消息包含第一路径迁移指示信息时，所述第一IAB-node的MT上的所述第一发送模块向所述第一IAB-node的DU发送第一指示信息；所述第一路径迁移指示信息用于指示所述第一RRC重配置消息是用于所述第一IAB-node进行路径迁移的重配置消息。
  7. 根据权利要求3所述的装置，其中，所述第一RRC重配置消息还包含第一指示信息的配置信息；所述第一指示信息的配置信息用于指示所述第一IAB-node的MT在随机接入成功时，向所述第一IAB-node的分布单元(DU)发送第一指示信息。
  8. 根据权利要求4所述的装置，其中，所述第一下行F1AP消息还包含第一缓存指示信息；所述第一缓存指示信息用于指示所述第一IAB-node缓存所述第二RRC重配置消息，直到收到所述第一指示信息后释放。
  9. 根据权利要求1所述的装置，其中，所述第二RRC重配置消息由所述第一RRC重配置消息携带。
  10. 根据权利要求1所述的装置，其中，所述第二RRC重配置消息由来自所述Donor-CU的第三下行F1AP消息携带，，所述第三下行F1AP消息由所述第一RRC重配置消息携带。
  11. 根据权利要求1所述的装置，其中，所述第一发送单元还用于在所述第一IAB-node随机接入失败时，向所述第二IAB-node发送路径迁移失败指示信息。
  12. 根据权利要求11所述的装置，其中，所述第一RRC重配置消息包含为所述第一IAB-node改变传输路径配置的第一参数或第一路径迁移指示信息时，所述第一发送单元向所述第二IAB-node发送所述路径迁移失败指示信息。
  13. 根据权利要求1所述的装置，其中，所述第一IAB-node在随机接入成功时，所述装置还包括：
    第二发送单元，其向所述Donor-CU发送第一RRC重配置完成消息；
    第三接收单元，其接收所述第二IAB-node发送的第二RRC重配置完成消息。
  14. 根据权利要求13所述的装置，其中，所述第二发送单元将所述第二RRC重配置完成消息包含在所述第一RRC重配置完成消息中转发给所述Donor-CU。
  15. 根据权利要求14所述的装置，其中，所述第二发送单元包括：第一接收模块，第五发送模块，第六发送模块；
    所述第一IAB-node的DU上的所述第一接收模块接收所述第二IAB-node发送的所述第二RRC重配置完成消息；
    所述第一IAB-node的DU上的所述第五发送模块将包含所述第二RRC重配置完成消息的第三上行F1AP消息发送给所述第一IAB-node的MT；
    所述第一IAB-node的MT上的所述第六发送模块将所述第三上行F1AP消息包 含在所述第一RRC重配置完成消息中转发给所述Donor-CU。
  16. 一种消息发送装置，应用于第二集成的接入和回传节点(IAB-node)，其特征在于，所述装置包括：
    第四接收单元，其接收来自Donor-CU的用于第三IAB-node路径迁移的第三RRC重配置消息；
    第三发送单元，其接收到所述Donor-CU发送并由第一IAB-node转发的第二RRC重配置消息时，向所述第三IAB-node转发所述第三RRC重配置消息，所述第二RRC重配置消息用于所述第二IAB-node路径迁移；
    其中，所述第三IAB-node为所述第二IAB-node的下游子节点，所述第二IAB-node为所述第一IAB-node的下游子节点。
  17. 根据权利要求16所述的装置，其中，所述第三发送单元包括：第七发送模块和第八发送模块；
    所述第二IAB-node的MT接收到所述第二RRC重配置消息时，所述第七发送模块向所述第二IAB-node的DU发送第二指示信息；
    所述第二IAB-node的DU收到所述第二指示信息时，所述第八发送模块将所述第三RRC重配置消息转发给所述第三IAB-node。
  18. 根据权利要求17所述的装置，其中，所述第二RRC重配置消息包含为所述第二IAB-node改变传输路径配置的第二参数时，所述第七发送模块向所述第二IAB-node的DU发送第二指示信息。
  19. 根据权利要求18所述的装置，其中，所述第二RRC重配置消息包含第二路径迁移指示信息时，所述第七发送模块向所述第二IAB-node的DU发送第二指示信息；所述第二路径迁移指示信息用于指示所述第二RRC重配置消息是用于所述第二IAB-node进行路径迁移的重配置消息。
  20. 一种消息发送装置，应用于第二集成的接入和回传节点(IAB-node)，其特征在于，所述装置包括：
    第六接收单元，其接收来自Donor-CU的用于第三IAB-node路径迁移的第三RRC重配置消息；
    第七接收单元，其接收第一IAB-node随机接入失败时发送的路径迁移失败指示信息；
    第二处理单元，其触发RRC重建立过程或回退到原路径配置；
    其中，所述第三IAB-node为所述第二IAB-node的下游子节点，所述第二IAB-node为所述第一IAB-node的下游子节点。
PCT/CN2021/091967 2021-05-06 2021-05-06 消息发送方法、装置和系统 WO2022233008A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
JP2023566914A JP2024516007A (ja) 2021-05-06 2021-05-06 メッセージ送信方法、装置及びシステム
CN202180097601.7A CN117337598A (zh) 2021-05-06 2021-05-06 消息发送方法、装置和系统
EP21939656.1A EP4336906A1 (en) 2021-05-06 2021-05-06 Message sending method, apparatus and system
PCT/CN2021/091967 WO2022233008A1 (zh) 2021-05-06 2021-05-06 消息发送方法、装置和系统
US18/384,944 US20240057205A1 (en) 2021-05-06 2023-10-30 Message transmission method and apparatus and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/091967 WO2022233008A1 (zh) 2021-05-06 2021-05-06 消息发送方法、装置和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/384,944 Continuation US20240057205A1 (en) 2021-05-06 2023-10-30 Message transmission method and apparatus and system

Publications (1)

Publication Number Publication Date
WO2022233008A1 true WO2022233008A1 (zh) 2022-11-10

Family

ID=83932568

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/091967 WO2022233008A1 (zh) 2021-05-06 2021-05-06 消息发送方法、装置和系统

Country Status (5)

Country Link
US (1) US20240057205A1 (zh)
EP (1) EP4336906A1 (zh)
JP (1) JP2024516007A (zh)
CN (1) CN117337598A (zh)
WO (1) WO2022233008A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170005913A1 (en) * 2015-06-30 2017-01-05 Qualcomm Incorporated Management of network routing domains in communication networks
CN110536350A (zh) * 2019-02-14 2019-12-03 中兴通讯股份有限公司 Iab链路控制方法、通信单元、计算机可读存储介质
CN111757484A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种配置信息的方法与装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170005913A1 (en) * 2015-06-30 2017-01-05 Qualcomm Incorporated Management of network routing domains in communication networks
CN110536350A (zh) * 2019-02-14 2019-12-03 中兴通讯股份有限公司 Iab链路控制方法、通信单元、计算机可读存储介质
CN111757484A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种配置信息的方法与装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
FUJITSU: "Discussion on inter-donor IAB migration", 3GPP DRAFT; R3-206107, vol. RAN WG3, 23 October 2020 (2020-10-23), pages 1 - 7, XP051945691 *
FUJITSU: "Discussion on inter-donor IAB migration", 3GPP DRAFT; R3-210458, vol. RAN WG3, 15 January 2021 (2021-01-15), pages 1 - 7, XP051968903 *

Also Published As

Publication number Publication date
JP2024516007A (ja) 2024-04-11
US20240057205A1 (en) 2024-02-15
CN117337598A (zh) 2024-01-02
EP4336906A1 (en) 2024-03-13

Similar Documents

Publication Publication Date Title
US20220256392A1 (en) Communication method and device
US20230345326A1 (en) Group migrating method and apparatus and system
US20230254729A1 (en) Migration method and apparatus for iab-node
US20230308975A1 (en) Group migration method and apparatus and system
WO2024031289A1 (zh) 网络节点的通信方法、移动节点的通信方法、移动节点和宿主设备
WO2022233008A1 (zh) 消息发送方法、装置和系统
WO2017166291A1 (zh) 一种通信方法、终端、基站和移动性管理设备
JP2024502623A (ja) Ｉａｂの通信方法及び装置
WO2022205252A1 (zh) 发送和接收信号的方法、装置和通信系统
US20240015098A1 (en) Method and apparatus for transmitting and receiving signal and communication system
WO2023197184A1 (zh) Iab宿主设备以及传输地址配置方法
WO2023197185A1 (zh) Iab节点设备、iab宿主设备以及传输地址确定方法
WO2024026803A1 (zh) 移动节点的配置方法和宿主设备
WO2023010298A1 (zh) 信息发送方法，信息处理方法以及装置
WO2022205485A1 (zh) 信息收发方法以及装置
WO2023010364A1 (zh) 集成的接入和回传的通信装置以及方法
WO2023150975A1 (zh) Iab宿主设备以及传输迁移回退方法
WO2023130232A1 (zh) Iab节点设备、iab宿主设备以及路径迁移方法
WO2024026804A1 (zh) 移动节点的配置方法、移动节点和宿主设备
WO2023184542A1 (zh) 配置信息的方法、装置和通信系统
WO2023010367A1 (zh) 终端设备的转移方法、装置和系统
WO2022205251A1 (zh) 信息收发方法，数据发送方法以及装置
WO2015042883A1 (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: 21939656

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180097601.7

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2023566914

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2021939656

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021939656

Country of ref document: EP

Effective date: 20231206