WO2022233317A1 - 一种iab节点连接更新方法及装置 - Google Patents

一种iab节点连接更新方法及装置 Download PDF

Info

Publication number
WO2022233317A1
WO2022233317A1 PCT/CN2022/091157 CN2022091157W WO2022233317A1 WO 2022233317 A1 WO2022233317 A1 WO 2022233317A1 CN 2022091157 W CN2022091157 W CN 2022091157W WO 2022233317 A1 WO2022233317 A1 WO 2022233317A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
iab node
node
host
target
Prior art date
Application number
PCT/CN2022/091157
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 EP22798657.7A priority Critical patent/EP4325937A1/en
Priority to KR1020237042215A priority patent/KR20240005065A/ko
Publication of WO2022233317A1 publication Critical patent/WO2022233317A1/zh
Priority to US18/502,261 priority patent/US20240073971A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • 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/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/248—Connectivity information update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • 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
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/087—Reselecting an access point between radio units of access points

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and device for updating an IAB node connection.
  • the 5th generation mobile networks (5G) puts forward more stringent requirements in all aspects for various network performance indicators. For example, the capacity index has been increased by 1000 times, wider coverage requirements, ultra-high reliability and ultra-low latency, etc.
  • the capacity index has been increased by 1000 times, wider coverage requirements, ultra-high reliability and ultra-low latency, etc.
  • the use of high-frequency small stations to form a network is becoming more and more popular.
  • high-frequency carriers have poor propagation characteristics, are severely attenuated by occlusion, and have limited coverage, so a large number of high-frequency small cells need to be densely deployed.
  • the cost of providing optical fiber backhaul for these densely deployed high-frequency small cells is very high. High, construction is difficult, so an economical and convenient backhaul solution is required; on the other hand, from the perspective of wide coverage requirements, to provide network coverage in some remote areas, the deployment of optical fibers is difficult and costly, and flexible and convenient design is also required. Access and backhaul scenarios.
  • the embodiment of the present application proposes an IAB node connection update method and device, which can realize the handover of the DU part of the IAB node and the handover of the serving cell between two different IAB hosts.
  • an embodiment of the present application proposes an IAB node connection update method, which is applied to a first IAB node.
  • the first IAB node includes an MT part and a DU part, which can be provided for one or more subordinate UEs and/or subordinate IAB nodes.
  • the first IAB node is connected to the source IAB host before the connection update, and is connected to the target IAB host after the connection update, and the method includes:
  • the DU part of the first IAB node establishes an F1 connection with the target IAB host.
  • the first indication information is used to trigger the DU part of the first IAB node to establish an F1 connection with the target IAB host in time to reduce the delay.
  • the above method further includes:
  • the cell served by the DU part of the first IAB node is changed from the cell hosted by the source IAB to the cell hosted by the target IAB.
  • receiving the first indication information includes:
  • the first indication information from the operation, management and maintenance OAM is received.
  • the first indication information is the IP address of the target IAB host.
  • the first indication information includes the IP address of the target IAB host, and explicit indication information for instructing the DU part of the first IAB node to initiate establishing an F1 connection with the target IAB host.
  • receiving the first indication information from the operation, management and maintenance OAM includes:
  • the target cell is the cell accessed by the first IAB node after connection update
  • the first indication information from the operation, management and maintenance OAM is received.
  • receiving the first indication information from the source IAB host includes:
  • the source IAB host sending a measurement report to the source IAB host; wherein, the first indication information is determined by the source IAB host based on the measurement report;
  • the first indication information from the source IAB host is received.
  • receiving the first indication information from the source IAB host includes:
  • the MT part of the first IAB node performs a radio resource control RRC re-establishment process after a radio link failure occurs, and connects with the target IAB host after accessing the target cell; wherein, the first indication information is that the source IAB host is based on the request for the first IAB host. Determined by a request message for the context of an IAB node, the request message for requesting the context of the first IAB node is sent by the target IAB host to the source IAB host;
  • the first indication information from the source IAB host is received.
  • the changing the cell served by the DU part of the first IAB node from the cell hosted by the source IAB to the cell hosted by the target IAB includes:
  • the cell served by the DU part of the first IAB node is changed from the cell hosted by the source IAB to the cell hosted by the target IAB;
  • the configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • RRC configuration information or
  • the configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • RRC configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • the receiving the second indication information includes:
  • the MT part of the first IAB node is still connected to the source IAB host, and the MT part of the first IAB node receives the second indication information carried by the radio resource control RRC message from the source IAB host; or
  • the DU part of the first IAB node receives the second indication information carried by the F1 application protocol F1AP message from the source IAB host;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell hosted by the target IAB.
  • receiving the second indication information includes:
  • the MT part of the first IAB node has been connected to the target IAB host, and the MT part of the first IAB node receives the second indication information carried by the radio resource control RRC message from the target IAB host;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB;
  • the DU part of the first IAB node receives the second indication information carried by the F1 application protocol F1AP message from the target IAB host;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB.
  • the subordinate UE and/or subordinate IAB node of the first IAB node receives configuration information, including:
  • the DU part of the first IAB node receives the F1 application protocol F1AP message from the source IAB host, the F1 application protocol F1AP message carries an RRC message container, and the RRC message container is encapsulated with the subordinate UE of the first IAB node and/or the subordinate IAB node.
  • RRC message ;
  • the F1 application protocol F1AP message carries the third indication information, after successfully sending the RRC message to the subordinate UE and/or subordinate IAB node of the first IAB node, determine the subordinate UE and/or subordinate IAB of the first IAB node The node receives configuration information; or
  • the F1 application protocol F1AP message is carried in the data packet of the first sequence number
  • the subordinate IAB node receives the configuration information, wherein the first sequence number is the data packet sequence number of the SCTP layer of the flow control transmission protocol, and is configured by the source IAB host to the first IAB node.
  • the third indication information is indication information used to instruct the first IAB node to stop scheduling data transmission to its subordinate UEs and/or subordinate IAB nodes;
  • the third indication information is used to indicate that in the RRC message carried in the RRC message container, the subordinate UE and/or subordinate IAB node including the first IAB node is changed to the target IAB host in the cell served by the DU part of the first IAB node After accessing the cell under the host of the target IAB, the RRC configuration information required by the cell under the host of the target IAB, where the cell under the host of the target IAB is the DU part of the first IAB node after the serving cell is changed to the cell under the host of the target IAB. 's district.
  • the above method further includes:
  • the RRC message of the IAB node includes that the subordinate UE of the first IAB node and/or the subordinate IAB node needs to access the cell hosted by the target IAB after the cell served by the DU part of the first IAB node is changed to the cell hosted by the target IAB. the RRC configuration information, then
  • the above method further includes:
  • the DU part of the first IAB node broadcasts fourth indication information, where the fourth indication information is used to instruct the subordinate UE and/or subordinate IAB node of the first IAB node to take effect configuration information; or
  • the duration information is indicated to the subordinate UEs and/or subordinate IAB nodes of the first IAB node, where the duration information is used to indicate the moment when the subordinate UEs and/or subordinate IAB nodes of the first IAB node take effect of the configuration information.
  • an embodiment of the present application also proposes an IAB node connection update method, which is applied to the source IAB host.
  • the first IAB node is connected to the source IAB host before the connection update.
  • the first IAB node includes an MT part and a DU part, which can be Providing access and backhaul services for one or more subordinate UEs and/or subordinate IAB nodes, and the first IAB node is connected to the target IAB host after the connection is updated, and the method includes:
  • the embodiment of the present application triggers the DU part of the first IAB node to establish an F1 connection with the target IAB host in time through the first indication information, thereby reducing the delay.
  • the above method further includes:
  • the above method further includes:
  • the first indication information is the IP address of the target IAB host.
  • the first indication information includes the IP address of the target IAB host, and explicit indication information for instructing the DU part of the first IAB node to initiate establishing an F1 connection with the target IAB host.
  • sending the first indication information to the first IAB node includes:
  • the source IAB host determines the first indication information
  • sending the first indication information to the first IAB node includes:
  • the MT part of the first IAB node is connected to the target IAB donor after performing the RRC re-establishment procedure of the radio resource control after the radio link failure occurs, and then receives the request from the target IAB donor for requesting the first IAB from the target IAB donor.
  • the request message for the context of the node based on the request message for requesting the context of the first IAB node, to determine the first indication information, wherein the target cell is the cell accessed by the first IAB node after connection update;
  • sending the second indication information to the first IAB node includes:
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB.
  • the above method further includes:
  • the F1 application protocol F1AP message carries the RRC message container and the third indication information, and the RRC message container is encapsulated with the subordinate UE and/or subordinate IAB node of the first IAB node
  • the RRC message so that the first IAB node determines that the subordinate UE and/or the subordinate IAB node of the first IAB node has received the configuration information after successfully sending the RRC message to the subordinate UE and/or subordinate IAB node of the first IAB node ;
  • the configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • RRC configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • the third indication information is indication information used to instruct the first IAB node to stop scheduling data transmission to its subordinate UEs and/or subordinate IAB nodes;
  • the third indication information is used to indicate that the RRC message carried in the RRC message container includes the RRC configuration information required by the subordinate UE and/or subordinate IAB node of the first IAB node to access the cell under the target IAB host, wherein the target IAB host
  • the cell below is the cell served by the DU part of the first IAB node after the cell it serves is changed to the cell hosted by the target IAB.
  • an embodiment of the present application proposes an IAB node connection update method, which is applied to a target IAB host.
  • the first IAB node is connected to the target IAB host after the connection is updated.
  • the first IAB node includes an MT part and a DU part, which can be One or more subordinate UEs and/or subordinate IAB nodes provide access and backhaul services, and the first IAB node is connected to the source IAB host before the connection update, and the method includes:
  • the first indication information is the IP address of the target IAB host, or
  • the first indication information includes the IP address of the target IAB host, and explicit indication information for instructing the DU part of the first IAB node to initiate establishing an F1 connection with the target IAB host.
  • an embodiment of the present application proposes an IAB node connection update method, which is applied to a subordinate node, where the subordinate node is a subordinate UE and/or a subordinate IAB node of the first IAB node, wherein the first IAB node includes an MT part and DU part, can provide access and backhaul services for one or more subordinate UEs and/or subordinate IAB nodes, the first IAB node is connected to the source IAB host before the connection update, and is connected to the target IAB host after the connection update,
  • the method includes:
  • the configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • RRC configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • the configuration information includes fifth indication information, where the fifth indication information is used to indicate the delayed effective configuration information
  • Effective configuration information including:
  • the configuration information is validated.
  • the above method further includes:
  • Effective configuration information including:
  • the configuration information takes effect according to the time when the configuration information takes effect.
  • the effective configuration information includes:
  • the configuration information takes effect
  • the target cell is the cell served by the DU part of the first IAB node after the cell it serves is changed to a cell hosted by the target IAB, and is identified by the target cell identifier in the configuration information.
  • the effective configuration information includes:
  • an embodiment of the present application proposes an IAB node connection update device, which is applied to a first IAB node.
  • the first IAB node includes an MT part and a DU part, and can provide one or more subordinate UEs and/or subordinate IAB nodes.
  • the first IAB node is connected to the source IAB host before the connection update, and is connected to the target IAB host after the connection update, and the device includes:
  • the first transceiver module is configured to receive the first indication information
  • the connection module is configured to establish an F1 connection between the DU part of the first IAB node and the target IAB host according to the first indication information.
  • the above device also includes:
  • the changing module is used to change the cell served by the DU part of the first IAB node from the cell hosted by the source IAB to the cell hosted by the target IAB.
  • the first transceiver module includes:
  • the first transceiver sub-module is configured to receive the first indication information from the source IAB host; or
  • the second transceiver sub-module is configured to receive the first indication information from the operation, management and maintenance OAM.
  • the first indication information is the IP address of the target IAB host.
  • the first indication information includes the IP address of the target IAB host, and explicit indication information for instructing the DU part of the first IAB node to initiate establishing an F1 connection with the target IAB host.
  • the second transceiver sub-module is specifically used for:
  • the target cell is the cell accessed by the first IAB node after connection update
  • the first indication information from the operation, management and maintenance OAM is received.
  • the first transceiver sub-module is specifically used for:
  • the source IAB host sending a measurement report to the source IAB host; wherein, the first indication information is determined by the source IAB host based on the measurement report;
  • the first indication information from the source IAB host is received.
  • the first transceiver sub-module is specifically used for:
  • the MT part of the first IAB node performs a radio resource control RRC re-establishment process after a radio link failure occurs, and connects with the target IAB host after accessing the target cell; wherein, the first indication information is that the source IAB host is based on the request for the first IAB host. Determined by a request message for the context of an IAB node, the request message for requesting the context of the first IAB node is sent by the target IAB host to the source IAB host;
  • the first indication information from the source IAB host is received.
  • the third transceiver sub-module is configured to receive the second indication information
  • the changing submodule is configured to change the cell served by the DU part of the first IAB node from the cell hosted by the source IAB to the cell hosted by the target IAB according to the second indication information;
  • the first determining module is configured to determine that the subordinate UE and/or subordinate IAB node of the first IAB node have received the configuration information
  • the change submodule is used to change the cell served by the DU part of the first IAB node from the cell hosted by the source IAB to the cell hosted by the target IAB;
  • the configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • RRC configuration information or
  • the third transceiver sub-module is configured to receive the second indication information, and determine that the subordinate UE and/or subordinate IAB node of the first IAB node have received the configuration information;
  • the change submodule is used to change the cell served by the DU part of the first IAB node from the cell hosted by the source IAB to the cell hosted by the target IAB;
  • the configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • RRC configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • the third transceiver sub-module is specifically used for:
  • the MT part of the first IAB node is still connected to the source IAB host, and the MT part of the first IAB node receives the second indication information carried by the radio resource control RRC message from the source IAB host;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB;
  • the DU part of the first IAB node receives the second indication information carried by the F1 application protocol F1AP message from the source IAB host;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB.
  • the third transceiver sub-module is specifically used for:
  • the MT part of the first IAB node has been connected to the target IAB host, and the MT part of the first IAB node receives the second indication information carried by the radio resource control RRC message from the target IAB host;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB;
  • the DU part of the first IAB node receives the second indication information carried by the F1 application protocol F1AP message from the target IAB host;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB.
  • the first determining module is specifically used for:
  • the DU part of the first IAB node receives the F1 application protocol F1AP message from the source IAB host, the F1 application protocol F1AP message carries an RRC message container, and the RRC message container is encapsulated with the subordinate UE of the first IAB node and/or the subordinate IAB node.
  • RRC message ;
  • the F1 application protocol F1AP message carries the third indication information, after successfully sending the RRC message to the subordinate UE and/or subordinate IAB node of the first IAB node, determine the subordinate UE and/or subordinate IAB of the first IAB node The node receives configuration information; or
  • the F1 application protocol F1AP message is carried in the data packet of the first sequence number
  • the subordinate IAB node receives the configuration information, wherein the first sequence number is the data packet sequence number of the SCTP layer of the flow control transmission protocol, and is configured by the source IAB host to the first IAB node.
  • the third indication information is indication information used to instruct the first IAB node to stop scheduling data transmission to its subordinate UEs and/or subordinate IAB nodes;
  • the third indication information is used to indicate that the RRC message carried in the RRC message container includes the RRC configuration information required by the subordinate UE and/or subordinate IAB node of the first IAB node to access the cell under the target IAB host, wherein, The cell hosted by the target IAB is the cell served by the DU part of the first IAB node after the cell it serves is changed to the cell hosted by the target IAB.
  • the above device also includes:
  • the second determining module is configured to determine the first IAB node carried in the F1 application protocol F1AP message according to the third indication information carried in the F1 application protocol F1AP message or according to the data packet of the first sequence number carried in the F1 application protocol F1AP message
  • the RRC message of the subordinate UE and/or the subordinate IAB node includes that the subordinate UE and/or the subordinate IAB node of the first IAB node access the target after the cell served by the DU part of the first IAB node is changed to the cell hosted by the target IAB.
  • the above device also includes:
  • the broadcast module is used for the DU part of the first IAB node to broadcast fourth indication information, and the fourth indication information is used to indicate the subordinate UE of the first IAB node and/or the subordinate IAB node effective configuration information;
  • the second transceiver module is used for indicating duration information to the subordinate UE and/or subordinate IAB node of the first IAB node, and the duration information is used to indicate the moment when the subordinate UE and/or subordinate IAB node of the first IAB node takes effect of the configuration information.
  • an embodiment of the present application proposes an IAB node connection update device, which is applied to the source IAB host, the first IAB node is connected to the source IAB host before the connection update, and the first IAB node includes an MT part and a DU part, which can be One or more subordinate UEs and/or subordinate IAB nodes provide access and backhaul services, and the first IAB node is connected to the target IAB host after the connection is updated, and the apparatus includes:
  • the third determining module is configured to determine that the DU part of the first IAB node needs to perform connection update to establish an F1 connection with the target IAB host;
  • the third transceiver module is configured to send first indication information to the first IAB node, where the first indication information is used to instruct the DU part of the first IAB node to establish an F1 connection with the target IAB host.
  • the above device further includes:
  • the fourth transceiver module is used to send second indication information to the first IAB node, where the second indication information is used to instruct the cell served by the DU part of the first IAB node to change from the cell hosted by the source IAB to the cell hosted by the target IAB .
  • the above device further includes:
  • the fifth transceiver module is used to send the first request message to the target IAB host, and the first request message is used to request the IP address of the target IAB host;
  • the fifth transceiver module is also used to receive the first response message from the target IAB host, and the first response message includes the IP address of the target IAB host;
  • the first indication information is the IP address of the target IAB host.
  • the first indication information includes the IP address of the target IAB host, and explicit indication information for instructing the DU part of the first IAB node to initiate establishing an F1 connection with the target IAB host.
  • sending the first indication information to the first IAB node includes:
  • the source IAB host determines the first indication information
  • sending the first indication information to the first IAB node includes:
  • the MT part of the first IAB node is connected to the target IAB donor after performing the RRC re-establishment procedure of the radio resource control after the radio link failure occurs, and then receives the request from the target IAB donor for requesting the first IAB from the target IAB donor.
  • the request message for the context of the node based on the request message for requesting the context of the first IAB node, to determine the first indication information, wherein the target cell is the cell accessed by the first IAB node after connection update;
  • the fourth transceiver module is specifically used for:
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB.
  • the above device further includes:
  • the sixth transceiver module is used to send the F1 application protocol F1AP message to the DU part of the first IAB node, the F1 application protocol F1AP message carries the RRC message container and the third indication information, and the RRC message container is encapsulated with the subordinate UE of the first IAB node. and/or the RRC message of the subordinate IAB node, so that the first IAB node determines the subordinate UE and/or subordinate IAB node of the first IAB node after successfully sending the RRC message to the subordinate UE and/or subordinate IAB node of the first IAB node
  • the IAB node receives the configuration information;
  • the configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • RRC configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • the third indication information is indication information used to instruct the first IAB node to stop scheduling data transmission to its subordinate UEs and/or subordinate IAB nodes;
  • the third indication information is used to indicate that the RRC message carried in the RRC message container includes the RRC configuration information required by the subordinate UE and/or subordinate IAB node of the first IAB node to access the cell under the target IAB host, wherein the target IAB host
  • the cell below is the cell served by the DU part of the first IAB node after the cell it serves is changed to the cell hosted by the target IAB.
  • an embodiment of the present application proposes an IAB node connection update device, which is applied to a target IAB host.
  • the first IAB node is connected to the target IAB host after the connection is updated.
  • the first IAB node includes an MT part and a DU part, which can be One or more subordinate UEs and/or subordinate IAB nodes provide access and backhaul services, and the first IAB node is connected to the source IAB host before the connection update, and the apparatus includes:
  • the fourth determining module is used to determine that the DU part of the first IAB node needs to establish an F1 connection with the target IAB host;
  • the seventh transceiver module is configured to send first indication information to the first IAB node, where the first indication information is used to instruct the first IAB node to establish an F1 connection with the target IAB host.
  • the first indication information is the IP address of the target IAB host, or
  • the first indication information includes the IP address of the target IAB host, and explicit indication information for instructing the DU part of the first IAB node to initiate establishing an F1 connection with the target IAB host.
  • an embodiment of the present application proposes an IAB node connection update device, which is applied to a subordinate node, where the subordinate node is a subordinate UE and/or a subordinate IAB node of a first IAB node, and the first IAB node includes an MT part and a DU part, Access and backhaul services can be provided for one or more subordinate UEs and/or subordinate IAB nodes.
  • the first IAB node is connected to the source IAB host before the connection is updated, and is connected to the target IAB host after the connection is updated.
  • the device includes:
  • the eighth transceiver module is configured to receive the configuration information of the DU part from the first IAB node;
  • the configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • RRC configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • the validating module is used for validating configuration information.
  • the configuration information includes fifth indication information, where the fifth indication information is used to indicate the delayed effective configuration information
  • the configuration information is validated.
  • the above device further includes:
  • the ninth transceiver module is used to receive the duration information from the first IAB node, and the duration information is used to indicate the moment when the subordinate UE of the first IAB node and/or the subordinate IAB node takes effect of the configuration information;
  • the configuration information takes effect according to the time when the configuration information takes effect.
  • the validation module is specifically used to:
  • the configuration information takes effect
  • the target cell is the cell served by the DU part of the first IAB node after the cell it serves is changed to a cell hosted by the target IAB, and is identified by the target cell identifier in the configuration information.
  • the validation module is specifically used to:
  • an embodiment of the present application provides an IAB node connection update device, including at least one processor, the processor is configured to execute a program stored in a memory, and when the program is executed, the IAB node connection update device is made Device execution:
  • the embodiments of the present application provide a computer program product containing instructions, when the computer program product is run on a computer, the method as in the first aspect and various possible implementations thereof is executed by the computer; or The method in the second aspect and its various possible implementations is performed by the computer; or the method in the third aspect and its various possible implementations is performed by the computer; or the fourth aspect and its various possible implementations are performed by the computer. Methods in implementations are performed by the computer.
  • an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the first aspect and its various possible implementations or as in the second aspect and its various possible implementations; or as in the third aspect and its various possible implementations; or as in the fourth aspect and its various The methods in one possible implementation are executed.
  • FIG. 1 is a schematic diagram of an IAB independent networking in a possible implementation manner
  • FIG. 2 is a schematic diagram of an IAB non-independent networking in a possible implementation manner
  • FIG. 3 is a schematic diagram of an IAB network user plane provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of an IAB network control plane provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a scenario in which an IAB node performs cross-host topology update switching according to an embodiment of the present application
  • FIG. 6 is an architectural diagram of an IAB node connected to an IAB donor through a wireless backhaul link provided by an embodiment of the present application;
  • FIG. 7 is a schematic diagram of topology update between IAB hosts according to an embodiment of the present application.
  • FIG. 8(a)-FIG. 8(c) are schematic flowcharts of a method for updating an IAB node connection according to an embodiment of the present application
  • FIG. 9 is a schematic diagram of establishing a dual link for an IAB node provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a short BSR format or a truncated short BSR format in a possible implementation
  • FIG. 11 is a schematic diagram of a long BSR format or a truncated long BSR format in a possible implementation
  • FIG. 12 is a schematic diagram of a new short BSR format or a new truncated short BSR format provided by an embodiment of the present application;
  • FIG. 13 is a schematic diagram of a new long BSR format or a new truncated long BSR format provided by an embodiment of the present application;
  • FIG. 14 is a schematic structural diagram of an IAB node connection update apparatus provided by an embodiment of the present application.
  • FIG. 15 is another schematic structural diagram of an IAB node connection update apparatus provided by an embodiment of the present application.
  • 16 is another schematic structural diagram of an IAB node connection update apparatus provided by an embodiment of the present application.
  • FIG. 17 is another schematic structural diagram of an IAB node connection update apparatus provided by an embodiment of the present application.
  • the term "and/or" in this application is only an association relationship to describe associated objects, which means that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone and exists simultaneously A and B, there are three cases of B alone.
  • the terms "first”, “second” and “third” in the description and claims of the embodiments of the present application are used to distinguish different objects, rather than used to describe a specific order of the objects.
  • the first transceiving module, the second transceiving module, the third transceiving module, etc. are used to distinguish different transceiving modules, rather than being used to describe a specific order of the target objects.
  • words such as “exemplary”, “for example” or “for example” are used to mean serving as an example, illustration or illustration. Any embodiment or design described in the embodiments of the present application as “exemplary,” “for example,” or “eg,” should not be construed as being advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present the related concepts in a specific manner. In the description of the embodiments of the present application, unless otherwise specified, the meaning of "plurality” refers to two or more.
  • an IAB node In an integrated access and backhaul (IAB) network, an IAB node (IAB node), also known as a relay node (Relay Node, RN), can provide wireless access to user equipment (User Equipment, UE). access service.
  • the service data of the UE is transmitted by the IAB node connected to the IAB donor (IAB donor) through a wireless backhaul link.
  • the IAB host may also be referred to as a donor node (donor node) or a donor base station (Donor gNodeB, DgNB).
  • An IAB node can consist of a mobile terminal (MT) (or MT called IAB node, or IAB-MT) and a distributed unit (DU) (or DU called IAB node, or IAB-DU) ) part.
  • MT mobile terminal
  • DU distributed unit
  • IAB node IAB-DU
  • IAB node when the IAB node faces its parent node, it can act as a terminal device, that is, the role of MT; when the IAB node faces its child node (the child node may be another IAB node, or a common UE), it is regarded as a network device. , that is, the role as DU.
  • the MT part of the IAB node has part or all of the functions of the UE.
  • the IAB host can be an access network element with a complete base station function, or an access network element in the form of a centralized unit (centralized unit, CU) and a distributed unit (distributed unit, DU) separated.
  • the IAB host is connected to the core network (eg connected to the 5G core network, 5GC) network elements serving the UE and provides wireless backhaul functions for the IAB nodes.
  • the centralized unit of the IAB host is abbreviated as donor CU (or called the CU of the IAB host, or IAB-donor-CU, or IAB donor CU, or directly called CU), and the distributed unit of the IAB host is abbreviated as It is a donor DU (or DU called IAB host, or IAB-donor-DU, or IAB donor DU, or directly called DU), where the CU of IAB host may also be the control plane (control plane, CP) and user In the form of user plane (UP) separation, for example, the CU of the IAB host can be composed of one CU-CP (or IAB donor CU-CP, or IAB-donor-CU-CP) and one (or more) CU-UP (or IAB donor CU-UP, or IAB-donor-CU-UP).
  • the IAB node can be made to support dual connectivity (DC) or multi-connectivity (multi-connectivity) to deal with possible abnormal situations in the backhaul link, such as link interruption. Or blocking (blockage) and load fluctuations and other abnormalities, improve the reliability of transmission. Therefore, the IAB network supports multi-hop networking and can also support multi-connection networking. Between the UE served by the IAB node and the IAB host, there is at least one transmission path consisting of multi-segment links.
  • each IAB node regards the adjacent nodes that provide access and backhaul services as a parent node, and accordingly, each IAB node can be regarded as a child node of its parent node.
  • the parent node of IAB node 1 is IAB donor, and IAB node 1 is the parent node of IAB node 2 and IAB node 3. Both IAB node 2 and IAB node 3 are the parent nodes of IAB node4, and IAB The parent node of node 5 is IAB node 2.
  • the uplink data packets of the UE can be transmitted to the IAB donor through one or more IAB nodes, and then sent by the IAB donor to the mobile gateway device (such as the user plane functional unit UPF in the 5G core network), and the downlink data packets will be sent by the IAB donor from the mobile gateway device. After being received by the gateway device, it is sent to the UE through the IAB node.
  • FIG. 1 shows an IAB independent (standalone, SA) networking scenario, where both the IAB node and the UE only establish connections with the network through the air interface of the NR standard.
  • the IAB independent networking scenario shown in FIG. 1 is only exemplary. As shown in Figure 1, the path numbered 1 represents the access link, and the path numbered 2 represents the backhaul link. In the IAB scenario combining multi-hop and multi-connection, there are more other possibilities.
  • the IAB donor in Figure 1 and the IAB node under another IAB donor form dual connections to serve the UE (that is, the UE supports dual connections, One of the connection 1 directly accesses the cell served by the donor DU, and the other connection 2 is to establish a connection with the IAB node X.
  • the IAB node X connected to is different from the IAB donor corresponding to the UE connection 1) and so on. Not listed in the application.
  • the IAB network also supports non-standalone (NSA) networking.
  • the IAB node supports 4G and 5G network dual connectivity, namely EN-DC (E-UTRAN NR Dual Connectivity), in which the LTE base station eNB is the master base station (Master eNB, MeNB), which provides the LTE air interface ( LTE Uu) connection, and establish S1 interface with 4G core network evolved packet core network (evolved packet core, EPC) for user plane and control plane transmission.
  • the IAB donor gNB is the secondary base station, which provides the NR air interface (NR Uu) connection for the IAB node, and establishes an S1 interface with the core network EPC for user plane transmission.
  • NR Uu NR air interface
  • the UE also supports EN-DC.
  • the UE is connected to the primary base station eNB through the LTE Uu interface, and is connected to the secondary base station IAB node through the NR Uu interface.
  • the secondary base station of the UE can also be an IAB donor gNB.
  • FIG. 2 is only an example of a non-independent networking.
  • the NSA scenario of the IAB network also supports multi-hop IAB networking.
  • the UE in Figure 2 can be another IAB node, that is, the IAB node can be connected to the IAB donor gNB through a multi-hop wireless backhaul link.
  • the IAB non-independent networking scenario in this application may also be referred to as the EN-DC networking scenario of the IAB.
  • BAP Backhaul Adaptation Protocol
  • RLC Link Control
  • the F1 interface supports the user plane protocol (F1-U/F1 * -U) and the control plane protocol (F1-C/F1 * -C).
  • the user plane protocol includes one or more of the following protocol layers: General Packet Radio Service (GPRS) tunneling protocol user plane (GTP-U), user datagram protocol (user datagram) Protocol, UDP), Internet Protocol (internet protocol, IP) and other protocol layers, see Figure 3;
  • the control plane protocol of the F1 interface includes one or more of the following: F1 application protocol (F1 application protocol, F1AP), flow protocol layers such as stream control transport protocol (SCTP), IP, etc., see FIG. 4 .
  • the IAB node and the IAB donor can perform interface management, manage the IAB-DU, and perform UE context-related configuration.
  • the user plane of the F1/F1 * interface the user plane data transmission and downlink transmission status feedback functions can be performed between the IAB node and the IAB donor.
  • each IAB node and its parent node are connected to the same IAB donor, and each IAB-MT and IAB-DU can be considered to be managed by the same IAB donor. Therefore, topology management and routing configuration, quality of service (QoS) management, etc. in an IAB network composed of IAB nodes under an IAB donor are all subject to an IAB donor (specifically, an IAB-donor-CU, or IAB-donor-CU-CP) controlled.
  • an IAB donor specifically, an IAB-donor-CU, or IAB-donor-CU-CP
  • the IAB donor specifically, IAB-donor-CU, or IAB-donor-CU-CP
  • the IAB donor will know where the IAB node passes.
  • a parent node is connected to the network, if the IAB donor is in the form of CU and DU separated, you can also know which IAB-donor-DU the IAB node is connected to (that is, the IAB-donor-DU connected to the parent node), Subsequently, if the topology update of the IAB node occurs (such as adding a new parent node, or changing the parent node), it is controlled by the IAB donor (specifically, IAB-donor-CU, or IAB-donor-CU-CP) completed below. That is to say, the IAB donor can know the network topology state composed of all IAB nodes and IAB-donor-DUs under it.
  • the identity management and routing configuration of the IAB nodes are centrally managed by the IAB-donor-CU.
  • the above identification management includes the allocation of the BAP address of the IAB node/IAB-donor-DU and the allocation of the BAP path ID configured for each routing path.
  • a specific transmission path from an IAB node A to an IAB node B can be uniquely identified by a BAP routing ID.
  • Each BAP routing ID contains the BAP address part of the target IAB node and the path label BAP path ID part.
  • the BAP routing ID part can uniquely identify a transmission path to a target IAB node, without collision of BAP address and/or the entire BAP routing ID.
  • the so-called BAP address conflict situation that is, a BAP address may be considered by one or some IAB nodes to identify two or more different target IAB nodes; the BAP routing ID conflict situation refers to a BAP routing ID It will be considered by one or some IAB nodes to identify two or more different transmission paths.
  • the IAB nodes are all connected to the same IAB host.
  • the IAB node can be connected to multiple IAB hosts, or when the MT part and the DU part of the IAB node do not belong to the same IAB host management, the services of one IAB node or the UE connected to the IAB node may appear.
  • IAB nodes managed by IAB donor CU1 that is, both IAB-MT and IAB-DU are managed by the IAB donor CU1
  • IAB donor CU1 IAB donor CU1
  • IAB nodes jointly managed by the donor CU2 IAB-MT and IAB-DU are respectively connected to two different IAB donor CUs
  • the IAB nodes managed by the IAB donor CU2 that is, the IAB-MT and IAB-DU are both managed by the IAB donor CU2 ).
  • IAB donor CU1 there are only two CUs of different IAB hosts: IAB donor CU1 and IAB donor CU2, but in actual situations, among the nodes through which the above-mentioned services pass, there may be other IAB donor CUs.
  • An IAB node controlled by eg IAB donor CU3 is also included in the path, or an IAB node jointly managed by two other IAB donor CUs.
  • IAB nodes and IAB-donor-DUs managed by different hosts may be connected to each other through one or more Backhaul Links, and different IAB hosts are controlled/
  • BAP address BAP layer node identifier
  • BAP routing ID routing identifier
  • different IAB hosts may configure the same BAP address for different IAB nodes, or for different paths.
  • the same BAP routing ID is configured, that is, the conflict of BAP address or BAP routing ID occurs, which will cause one or some IAB nodes to receive a packet containing a BAP routing ID, but the destination IAB of the packet cannot be determined.
  • Which node is and which is the routing path indicated by the BAP routing ID may cause the packet to be unable to be routed correctly.
  • an embodiment of the present application proposes an IAB node connection update method, which can be applied to the scenario in which the IAB node performs cross-host topology update switching as shown in FIG. 5 provided by the embodiment of the present application.
  • IAB node 3 is updated from the source IAB host CU1 to the target IAB host CU2
  • MT3 needs to access the new parent node
  • its DU part such as DU3b
  • the IAB host that is, the target IAB host CU2 establishes a connection.
  • the IAB-DU needs to establish an F1 connection with the target host CU.
  • IAB node 3 can be connected and updated from the source IAB host CU1 to the target IAB host CU2 for the IAB node 3 to switch from the source IAB host CU1 to the target IAB host CU2, or it can be connected to the IAB node 3 in the wireless backhaul chain.
  • the IAB node 3 can update the transport layer coupling of the F1 connection used for the bearer between the two with the source IAB host CU1, and perform IPsec security negotiation again; or, the IAB node 3 can also communicate with the new IAB host CU, That is, a new transport layer association is established between the target IAB host CU2, a new IPsec security mechanism is negotiated, and an F1 connection is established.
  • the embodiments of the present application may be applied to an IAB network of a stand-alone network (SA), and may also be applied to an IAB network of a non-stand-alone network (NSA).
  • SA stand-alone network
  • NSA non-stand-alone network
  • FIG. 6 is an architectural diagram of an IAB node connected to an IAB donor through a wireless backhaul link provided by an embodiment of the present application.
  • the above IAB node connection update method can be applied to the architecture diagram shown in FIG. 6 .
  • the IAB node works in SA mode, the IAB node can be single-connected to one parent node, or double-connected to two parent nodes, where the two parent nodes can be controlled by the same IAB donor, or controlled by different IAB donors respectively.
  • the F1 interface can be established between the DU part of the IAB node and an IAB donor, and the IAB donor can be connected to the 5G core network (5G core, 5GC), that is, the dashed part marked 1 in Figure 6.
  • 5G core network 5G core, 5GC
  • the IAB-donor-CU-CP is connected to the control plane network elements (eg access and mobility management functions AMF) in the 5GC via the NG control plane interface, and where the IAB-donor-CU-UP is connected to the To the user plane network element (such as the user plane function UPF) in 5GC; when the IAB node works in the NSA mode (or EN-DC mode), the IAB-donor-CU-UP can be connected to the EPC through the S1 user plane interface ( For example, connected to a service gateway (serving gateway, SGW), there is an LTE Uu air interface connection between the MeNB and the MT of the IAB node, there is an X2-C interface between the MeNB and the IAB-donor-CU-CP, and the MeNB is connected to the S1 interface through the S1 interface.
  • EPC including S1 interface user plane, and S1 interface control plane). That is, the dashed line part numbered 2 in FIG. 6 .
  • the MeNB in FIG. 6 can also be replaced with a 5G base station gNB, and the LTE-Uu interface in the dashed line marked 2 in FIG. 6 is correspondingly replaced with an NR-Uu interface, and the gNB can be used with the 5GC
  • the interface between the user plane and/or the control plane is established between the gNB and the IAB-donor to provide dual-connection services for the IAB node.
  • the gNB can play the role of the primary base station of the IAB node, or the role of the secondary base station.
  • FIG. 7 shows a schematic diagram of topology update between IAB hosts.
  • the node where the handover occurs is IAB node 2 (referred to as IAB node 2, or IAB 2 for short), that is, the first IAB node mentioned below.
  • the IAB node 2 can provide access and backhaul services for one or more UEs/sub-nodes.
  • a UE1 that is connected to a cell served by the DU part of the IAB node 2 is shown, and a sub-node IAB node 3 (also called a subordinate IAB node of the IAB node 2) is also shown under the IAB node 3.
  • sub-node IAB node 3 also called a subordinate IAB node of the IAB node 2
  • IAB node 2 may have one or more grandchild nodes
  • IAB node 3 may serve more UEs, or child nodes, or grandchild nodes, as shown in Figure 7. Not all shown.
  • these IAB nodes or UEs connected to the IAB donor via the IAB node 2 are referred to as subordinate nodes of the IAB node 2, that is, subordinate IAB nodes and/or subordinate UEs.
  • the grandchild node of a node may be a subordinate node connected to the node through at least two hop wireless links.
  • IAB node 5 can be regarded as the grandchild node of IAB node 1.
  • IAB node 2 After IAB node 2 is connected from the source parent node (ie S parent IAB node 1 shown in Figure 7) to the target parent node (ie T parent IAB node 4 shown in Figure 7) after performing handover, its subordinate IAB node 3, as well as UE1 and UE2 can also follow IAB node 2 to perform handover.
  • the MT part and the DU part of an IAB node may be connected to two different IAB hosts respectively.
  • the MT part of the IAB node 2 has been connected to the target IAB host CU2, that is, the IAB host mentioned below, but the IAB2-DU part is still connected to the source IAB donor CU1, the source IAB host mentioned below, the subordinate nodes (IAB node 3) and UEs (UE1, UE2, UE3) of IAB node 2 are also still connected to IAB donor CU1.
  • the IAB node 3 needs to communicate with the IAB node CU1, and the relevant data packets need to be transmitted through the path shown by the solid line 1, that is, through the IAB node 2 (belonging to the node jointly managed by the two IAB donors), and the IAB node 4 and IAB donor DU2 (both of which belong to nodes managed by IAB donor CU2), in addition, will be transmitted via the IP transport network between IAB donor DU2 and IAB donor CU1.
  • an IAB node performs a connection update across IAB hosts, which can also be understood as an IAB node performing a connection update between two different IAB hosts, that is, the IAB node that the IAB node connects to before the connection update is different from the IAB host it connects to The target IAB host to connect to after the update.
  • the connection update here may be a connection update based on handover of the IAB node, or a connection update based on the MT part of the IAB node performing link recovery (eg, RRC re-establishment).
  • the topology update shown in Figure 7 can also be applied to the IAB node 2 when the backhaul link fails, and the IAB node 4 is connected to the IAB node 4 when performing link recovery (specifically, it can be is the cell served by the DU part of the IAB node 4), and then the MT part of the IAB node 2 can perform an RRC re-establishment process with the IAB donor CU2.
  • FIG. 8( a ) shows a schematic flowchart of an IAB node connection update method proposed by an embodiment of the present application, and the schematic flowchart includes S802-S806.
  • the IAB node connection update method can be applied to the first IAB node, the source IAB host, the target IAB host, and subordinate nodes, that is, subordinate UEs and/or subordinate IAB nodes of the first IAB node.
  • the first IAB node includes an MT part and a DU part, and can provide access and backhaul services for one or more subordinate UEs and/or subordinate IAB nodes.
  • the first IAB node is connected to the source IAB host before the connection update, and the connection is updated. After connecting to the target IAB host.
  • the IAB node connection update method as shown in Figure 8(a) provided by the embodiment of the present application is implemented through the following steps:
  • the source IAB host determines that the DU part of the first IAB node needs to perform connection update to establish an F1 connection with the target IAB host.
  • the first IAB node sends a measurement report to the source IAB host.
  • the source IAB host receives the measurement report.
  • the source IAB host determines whether the first IAB node performs cross-IAB host handover according to the relationship between the signal quality in the measurement report and the preset signal quality threshold.
  • the source IAB host determines that the first IAB node needs to perform cross-IAB host handover, and the DU part of the first IAB node needs to perform connection update to establish an F1 connection with the new IAB host, that is, the target IAB host.
  • the MT part of the first IAB node performs a radio resource control RRC re-establishment process after a radio link failure occurs to access the target cell and then connects to the target IAB host.
  • the target IAB host sends a request message for requesting the context of the first IAB node to the source IAB host.
  • the source IAB host determines according to the above request message that the DU part of the first IAB node needs to perform connection update to establish an F1 connection with the new IAB host, that is, the target IAB host establishes an F1 connection.
  • the DU part of the first IAB node performs a process of connection update and establishing an F1 connection with the target IAB host, including the establishment of an F1 interface between the two, and may also include: The establishment process of the Stream Control Transport Protocol (SCTP) coupling (or called the Transport Network Layer coupling), and/or the security negotiation between the two (for example, the security mechanism based on the IPSec protocol) and parameter negotiation process).
  • SCTP Stream Control Transport Protocol
  • security negotiation between the two for example, the security mechanism based on the IPSec protocol
  • parameter negotiation process for example, the security mechanism based on the IPSec protocol
  • the DU part of the first IAB node may be between the target IAB host (specifically, the target IAB host CU or CU-CP) before the MT part of the first IAB node performs cross-IAB host handover. Establish an F1 connection.
  • the DU part of IAB2 ie IAB2-DU
  • the DU part of IAB2 can communicate with the CU of the target IAB host (ie, in FIG. 7 ) before the MT part of IAB2 (ie IAB2-MT) performs handover.
  • the process of establishing an F1 connection is performed between the target IAB donor CU2), in this case, the IAB2-DU needs to establish an F1 connection with the target IAB donor CU2 via the source parent node IAB node 1 and the source IAB donor DU1, that is, The transmission path indicated by the dotted line 2 in FIG. 7 .
  • the IAB2-DU can also establish an F1 connection with the target IAB donor CU2 after the IAB2-MT performs the handover. In this case, the IAB2-DU can pass through the target parent node IAB node 4 and the transmission composed of the target IAB donor DU2 An F1 connection is established between the path and the target IAB donor CU2.
  • IAB node 2 may need to maintain two different F1 connections with source IAB donor CU1 and target IAB donor CU2 at the same time
  • the DU part in IAB node 2 can have multiple different logical DUs, such as in Figure 7
  • the IAB2-DU and IAB2-DU', IAB2-DU maintains the F1 connection with the source IAB donor CU1
  • IAB2-DU' maintains the F1 connection with the target IAB donor CU2.
  • this application does not limit whether the number of logical DUs contained in an IAB node is one or more.
  • the operation of the source IAB host when the source IAB host includes the DU of the IAB host and the CU of the IAB host, the operation of the source IAB host, such as the communication with the first IAB node or the target IAB host, can be specifically It is understood to be an operation performed by the CU hosted by the source IAB.
  • the source IAB host includes the IAB host DU, the IAB host CU-CP and the IAB host CU-UP
  • the operation or action of the source IAB host such as the communication with the first IAB node/target IAB host, can be specifically understood as the source IAB The operation or action being performed by the host CU-CP.
  • the operation of the target IAB host can be specifically understood as being performed by the CU of the target IAB host operate.
  • the target IAB host includes the IAB host DU, the IAB host CU-CP, and the IAB host CU-UP
  • the operation of the target IAB host such as the communication with the first IAB node/source IAB host, can be specifically understood as being performed by the target IAB host.
  • the first IAB node receives first indication information, where the first indication information is used to instruct the first IAB node to establish an F1 connection with the target IAB host.
  • the above-mentioned first indication information can be the IP address of the target IAB host.
  • the IP address information of the target IAB host is used as a kind of implicit indication information, that is, the first IAB node receives the IP address of the target IAB host sent by the source IAB host. After the message of the information, it can trigger the establishment of an F1 connection with the target IAB host.
  • the above-mentioned first indication information may also be IP address information of the target IAB host, and explicit indication information for instructing the DU part of the first IAB node to initiate establishing an F1 connection with the target IAB host.
  • the IP address information of the above-mentioned target IAB host specifically includes at least one of the following: the IP address used by the control plane of the target IAB host (specifically can be the IP address of the target IAB donor CU, or the IP address of the target IAB donor CU-CP), the target The IP address of the security gateway (Security Gateway) hosted by the IAB and/or the IP address used by the user plane of the target IAB host (specifically, the IP address of the target IAB donor CU-UP).
  • the source IAB host sends first indication information to the first IAB node, where the first indication information is used to instruct the DU part of the first IAB node to establish an F1 connection with the target IAB host.
  • the first IAB node receives the first indication information from the source IAB host, wherein the source IAB host determines in step S802 that the DU part of the first IAB node needs to perform a connection update to establish an F1 connection with the target IAB host Then, the first indication information is further determined, and then the first indication information is sent to the first IAB node.
  • the source IAB host sends a first request message to the target IAB host, where the first request message is used to request the IP address of the target IAB host.
  • the source IAB host receives a first response message from the target IAB host, where the first response message includes IP address information of the target IAB host.
  • the first IAB node receives the first indication information from the operation, management and maintenance OAM. Specifically, the first IAB node reports the identity of the target cell of the first IAB node to the operation, management and maintenance OAM. Based on the identity of the target cell, the OAM determines the target IAB host, and then provides the first indication information to the first IAB node. The first IAB node triggers the establishment process of the F1 connection with the target IAB host based on the IP address of the target IAB host received from the OAM.
  • the source IAB host determines to perform handover for the first IAB node according to the measurement report reported by the first IAB node, it can The IAB node provides the first configuration information of the target cell, which includes the identity of the target cell of the first IAB node.
  • the target cell is the host of the target IAB that needs to be accessed after the MT part of the first IAB node performs handover. community.
  • the MT part of the first IAB node when the first IAB node performs link recovery, the MT part of the first IAB node performs RRC re-establishment, selects the target cell for access, and reads the system information of the target cell in the process of reading the system information of the target cell. , to obtain the identity of the target cell.
  • the target cell is the cell under the target IAB host selected and accessed by the MT part of the first IAB node during the RRC re-establishment process.
  • the first IAB node receives the first indication information from the target IAB host.
  • the target IAB host specifically, the CU or CU-CP of the target IAB host
  • the context information of the first IAB node obtained by the IAB host can know that the first IAB node performing re-establishment is an IAB node (rather than an ordinary UE), and the target IAB host further determines that it needs to communicate with the DU part of the first IAB node
  • the first indication information can be sent to the first IAB node (specifically, it can be sent to the MT part of the first IAB node).
  • the DU part of the first IAB node establishes an F1 connection with the target IAB host.
  • the DU part of the first IAB node triggers the establishment of an F1 connection with the target IAB host according to the first indication information from the source IAB host or from the operation management and maintenance OAM or from the target IAB host.
  • the connection update of the DU part of the first IAB node needs to be performed between CUs of different IAB hosts (for example, the F1 connection of the DU of the first IAB node is switched or re-established between CUs of different IAB hosts. ), the establishment of an F1 connection between the first IAB node and the CU of the target IAB host can be triggered in time to reduce the delay.
  • the IAB node connection update method provided by the embodiment of the present application further includes various steps as shown in FIG. 8(b), and each step is as follows:
  • the first IAB node receives the second indication information.
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell hosted by the target IAB.
  • the first IAB node receives the second indication information from the source IAB host.
  • the source IAB host specifically may be the CU of the source IAB host
  • the second indication information carried in the message.
  • the MT part of the first IAB node can indicate to the DU part of the first IAB node through the internal interface a cell handover that can be served, or directly through the internal interface.
  • the second indication information is forwarded to the DU part of the first IAB node.
  • the CU of the source IAB host determines to send the second indication information to the first IAB node
  • an F1 connection is maintained with the DU part of the first IAB node, it can directly send the information to the first IAB node.
  • the DU part of the first IAB node sends the second indication information carried by the F1 application protocol F1AP message, correspondingly, the DU part of the first IAB node receives the second indication information carried by the F1 application protocol F1AP message from the source IAB host CU.
  • the MT part of the first IAB node has been connected to the target IAB host, and the first IAB node may receive the second indication information from the target IAB host.
  • the CU of the source IAB host can first send the seventh indication information to the CU of the target IAB host, so that the CU of the target IAB host can learn the second indication information of the cell that can send the handover service to the first IAB node , and then the CU hosted by the target IAB sends an RRC message to the MT part of the first IAB node, which carries the second indication information.
  • the CU of the source IAB host may also carry the identifier of the first IAB node, which may be, for example, the first IAB node is between the CU of the source IAB host and the CU of the target IAB host.
  • the identifier assigned on the Xn interface such as the NG-RAN node UE XnAP ID allocated by the CU of the source IAB host for the MT part of the first IAB node, and/or the CU of the target IAB host is allocated for the MT part of the first IAB node NG-RAN node UE XnAP ID.
  • the seventh indication information and the second indication information may be the same indication information, or may be different indication information.
  • the target IAB host CU After receiving the seventh indication information from the CU of the source IAB host, the target IAB host CU sends the The resource control RRC message sends the second indication information to the MT part of the first IAB node.
  • the MT part of the first IAB node receives the second indication information carried by the target IAB host through the radio resource control RRC message, and can indicate to the DU part of the first IAB node through the internal interface the cell handover that can be served, or The second indication information is directly forwarded to the DU part of the first IAB node through the internal interface.
  • an F1 connection between the CU of the target IAB host and the DU of the first IAB node, which can be used to carry the F1 application protocol F1AP message, and the target IAB host receives the seventh indication from the source IAB host.
  • an F1AP message is sent to the second IAB node, and the F1 application protocol F1AP message may contain the second indication information, and correspondingly, the DU part of the first IAB node receives The second indication information carried by the target IAB host through the F1 application protocol F1AP message.
  • the source IAB host may, after sending configuration information to all subordinate nodes of the first IAB node, determine that the DU of the first IAB node can switch the cell it serves to the target IAB host. cell, and then determine that the second indication information can be sent to the first IAB node, and then the source IAB host can directly send the second indication information to the second node, or send the above seventh indication information to the target IAB host, and then the target IAB host can send the second indication information to the target IAB host.
  • the first IAB node sends the second indication information.
  • the above configuration information is that the subordinate node of the first IAB node (the subordinate node may specifically be a subordinate UE or a subordinate IAB node) accesses the target IAB after the cell served by the DU part of the first IAB node is changed to a cell hosted by the target IAB.
  • RRC configuration information required by the cell under the host As an example, in this embodiment, the subordinate nodes of the first IAB node may only include child nodes of the first IAB node (the child nodes may be UEs or UEs in the cell served by the DU accessing the first IAB node. child IAB nodes).
  • the first IAB node changes the cell served by its DU part from the cell hosted by the source IAB to the cell hosted by the target IAB.
  • the first IAB node receives the second indication information sent by the source IAB host or the target IAB host in S808. According to the second indication information, the first IAB node changes the cell served by its DU part from the cell hosted by the source IAB to the cell hosted by the target IAB.
  • the first IAB node determines that its subordinate node has received the configuration information, and the first IAB node changes the cell served by the DU part of the first IAB node from the cell hosted by the source IAB to The cell under the target IAB host.
  • the above configuration information is the RRC configuration information required by the subordinate node of the first IAB node to access the cell hosted by the target IAB after the cell served by the DU part of the first IAB node is changed to the cell hosted by the target IAB.
  • the subordinate nodes of the first IAB node may only include child nodes of the first IAB node (the child nodes may be UEs or UEs in the cell served by the DU accessing the first IAB node. child IAB node), for example, after the first IAB node can determine that all its child nodes have received the configuration information, the first IAB node changes the cell served by its DU part from the cell hosted by the source IAB to the one hosted by the target IAB community.
  • the first IAB node receives the second indication information, and determines that its subordinate node has received the configuration information, and the first IAB node changes the cell served by its DU part from the source The cell under the IAB host is changed to the cell under the target IAB host.
  • the above configuration information is the RRC configuration information required by the subordinate node of the first IAB node to access the cell hosted by the target IAB after the cell served by the DU part of the first IAB node is changed to the cell hosted by the target IAB.
  • the subordinate nodes of the first IAB node may only include sub-nodes of the first IAB node (the sub-nodes may be those in the cell served by the DU accessing the first IAB node.
  • the first IAB node receives the second indication information, and determines that all its sub-nodes (including the UE and sub-IAB node accessing the cell served by the DU part of the first IAB node) have received the configuration After receiving the information, the first IAB node changes the cell served by its DU part from the cell hosted by the source IAB to the cell hosted by the target IAB.
  • the specific method for determining that the subordinate node of the first IAB node (taking the first subordinate node as an example) receives the configuration information is as follows:
  • the first subordinate node of the first IAB node is specifically a child node of the first IAB node, and the DU part of the first IAB node receives the F1 application protocol F1AP message from the source IAB host, and the F1AP message carries the RRC message container, the RRC message container
  • the RRC message of the first subordinate node of the first IAB node is encapsulated in it; the first IAB node determines that the RRC message contains the configuration information of the subordinate node, and after the RRC message is successfully sent to the first subordinate node, determines the first subordinate node.
  • a subordinate node receives configuration information.
  • the configuration information is the RRC configuration information required by the first subordinate node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • the cell is the cell served by the DU part of the first IAB node after the cell it serves is changed to the cell hosted by the target IAB.
  • the configuration information may specifically be a handover command of the subordinate node, and the handover command may be understood as the ReconfigurationwithSync IE in the RRC message.
  • the subordinate nodes of the first IAB node access the cell hosted by the target IAB after the cell served by the DU part of the first IAB node is changed to the cell hosted by the target IAB.
  • the method for the first IAB node to determine that the RRC message encapsulated in the RRC message container carried by the F1 application protocol F1AP message carries the configuration information of the subordinate node is as follows:
  • the first method when the CU of the source IAB host sends an RRC message to the DU of the first IAB node, wherein the RRC message carries the configuration information of the subordinate nodes of the first IAB node, the RRC message is encapsulated in the F1AP message , at the same time, in the F1AP message, the instruction information for stopping the data transmission of the subordinate node of the first IAB node can be carried (for example, the Transmission Action Indicator IE is carried in the F1AP message, and the value of the IE is stop), then the first If an IAB node receives an F1AP message including the RRC message of its subordinate node, and the F1AP message contains instruction information to stop scheduling data transmission for the subordinate nodes of the first IAB node, the first IAB node can It is judged that the RRC message carried in the F1AP message contains the configuration information of the subordinate node.
  • the RRC message carried in the F1AP message is implicitly instructed to include configuration information required by the subordinate node. Based on the configuration information, the subordinate node can access the cell hosted by the target IAB served by the DU of the first IAB node.
  • the second method when the CU of the source IAB host sends an RRC message to the first IAB node, wherein the RRC message carries the configuration information of the subordinate nodes of the first IAB node, which may be included in the F1AP message of the RRC message, Explicit indication information is directly included, which is used to indicate that the RRC message included in the F1AP message includes the configuration information of the subordinate nodes of the first IAB node.
  • the third method the CU of the source IAB host indicates a data packet sequence number to the first IAB node, and the F1AP message encapsulated in the data packet corresponding to the data packet sequence number contains the configuration information of the subordinate nodes, which is convenient for the first IAB node. Identify the configuration information of its subordinate nodes.
  • the packet sequence number may be the sequence number of the SCTP layer. It can be understood that, if the data packet corresponding to the specific sequence number value transmitted on the specific SCTP coupling carries configuration information, the CU of the source IAB host can not only indicate a data packet sequence number to the first IAB node, but also is to indicate a specific SCTP coupling identifier, and/or a specific SCTP stream ID.
  • the SCTP coupling identifier may be identified by any one or more items of IP quintuple information (source IP address, destination IP address, source port number, destination port number, and protocol type).
  • the fourth method after the first IAB node receives the F1AP message including the RRC message of its subordinate node, its DU part does not care whether the RRC message contained in the F1AP message carries the configuration information of the subordinate node, as long as the source IAB is determined
  • the host CU starts to send configuration information to its subordinate nodes, and after receiving the F1AP message containing the RRC message of the subordinate node, the first IAB node considers that the RRC message in the F1AP message contains the configuration information of the subordinate node.
  • the CU of the source IAB host or the CU of the target IAB host may send a notification message to the first IAB node, and the notification message may be used to indicate that the source IAB host CU starts to send to the subordinate nodes of the first IAB node.
  • Sending the configuration information can be used to instruct the first IAB node to start monitoring and counting the reception and transmission of RRC messages of its subordinate nodes.
  • the CU of the source IAB host determines to send the configuration information of the subordinate nodes of the first IAB node, it can send the notification information to the first IAB node, or send the notification information to the first IAB node through the target IAB host.
  • the IAB node connection update method provided by the embodiment of the present application further includes various steps as shown in FIG. 8( c ), and each step is specifically as follows:
  • the subordinate node of the first IAB node receives the configuration information of the DU part from the first IAB node.
  • the subordinate node of the first IAB node is the subordinate UE and/or the subordinate IAB node of the first IAB node, and may specifically be a sub-node of the first IAB node (for example, accessing the DU part of the first IAB node) UE and/or child IAB node of the serving cell).
  • the subordinate node of the first IAB node receives the RRC message sent by the DU part of the first IAB node in S810.
  • the RRC message contains configuration information.
  • the configuration information is the RRC configuration information required by the subordinate node to access the cell hosted by the target IAB after the cell served by the DU part of the first IAB node is changed to the cell hosted by the target IAB.
  • the subordinate nodes of the first IAB node take effect of the configuration information.
  • the subordinate node of the first IAB node may specifically be a child node of the first IAB node (eg, a UE and/or a child IAB node accessing a cell served by the DU part of the first IAB node).
  • a child node of the first IAB node eg, a UE and/or a child IAB node accessing a cell served by the DU part of the first IAB node.
  • the first IAB node determines that the RRC message of the first subordinate node of the first IAB node carried in the F1 application protocol F1AP message received by the first IAB node includes the first subordinate node configuration information, the RRC message is buffered first, and after receiving the second indication information, the first IAB node sends the buffered RRC message to the first subordinate node. In this way, it is possible to ensure that its subordinate nodes receive the configuration information in a similar time, and perform connection update according to the configuration information.
  • the manner in which the first IAB node determines that the RRC message of the first subordinate node of the first IAB node carried in the received F1 application protocol F1AP message includes the configuration information of the first subordinate node can be performed with reference to the description in step S810. understand.
  • the configuration information of the first subordinate node is that after the cell served by the first subordinate node in the DU part of the first IAB node is changed to a cell hosted by the target IAB, access to the cell hosted by the target IAB needs to be RRC configuration information.
  • the first IAB node does not need to cache the RRC message of the subordinate nodes of the first IAB node, where the RRC message includes the configuration information of the subordinate nodes of the first IAB node, but the first IAB node does not need to cache the RRC message of the subordinate node of the first IAB node.
  • the subordinate nodes of an IAB node may not take effect first.
  • the DU part of the first IAB node can be sent to the first IAB node.
  • All subordinate nodes broadcast a fourth indication information, and the fourth indication information is used to indicate the subordinate UE and/or subordinate IAB node of the first IAB node to take effect of configuration information.
  • the subordinate node of the first IAB node obtains the RRC message including its configuration information, it obtains fifth indication information, and the fifth indication information is used for the subordinate node to indicate the configuration information in the RRC message for delaying the validating.
  • the fifth indication information may be carried by the source IAB host in the RRC message of the subordinate node of the first IAB node generated by the source IAB host, or may be carried by the first IAB node in the MAC that encapsulates the RRC message.
  • the RRC message includes that the subordinate node accesses the target IAB after the cell served by the DU part of the first IAB node is changed to the cell hosted by the target IAB RRC configuration information required by the cell under the host.
  • the first IAB node does not need to cache the RRC message containing the configuration information of the subordinate node, but after the subordinate node of the first IAB node receives the configuration information, it may not take effect first, Instead, the time when the configuration information takes effect is determined based on the duration information indicated by the first IAB node.
  • the above-mentioned duration information may be carried in the RRC message containing the configuration information of the subordinate nodes of the first IAB node, may also be carried in the MAC PDU encapsulated with the RRC message, or carried in the backhaul adaptation protocol.
  • the control PDU of the (Backhaul Adaptation Protocol, BAP) layer is sent to the subordinate nodes.
  • the subordinate UE and/or subordinate IAB node of the first IAB node may start a timer after receiving the RRC message containing the above configuration information based on the duration information, and then take effect of the configuration in the RRC message after the timer expires information, according to the configuration information to access the cell under the host of the target IAB (that is, after the cell served by the DU part of the first IAB node is changed to the cell under the host of the target IAB, the cell served by the DU part of the first IAB node ).
  • the subordinate node of the first IAB node may not take effect first, but perform cell search, and when the subordinate node searches for the target cell, the configuration information takes effect.
  • the target cell is the cell served by the DU part of the first IAB node after the cell it serves is changed to a cell hosted by the target IAB, and is identified by the target cell identifier in the configuration information.
  • the effective configuration information of the subordinate nodes of the above-mentioned first IAB node may include that the subordinate nodes of the first IAB node access the target cell specified in the configuration information according to the configuration information, and establish a connection with the target IAB host.
  • the first IAB node has multiple subordinate nodes, these subordinate nodes receive their respective configuration information successively. If the subordinate node of the first IAB node (for example, subordinate node X) that receives the configuration information first, immediately executes the configuration according to the configuration in the configuration information. The connection is updated. At this time, if the DU part of the first IAB node has not switched the cell it serves to the cell hosted by the target IAB, the subordinate node X may not be able to find the target cell at all. In this case, the subordinate node will also be caused. X performs RRC re-establishment.
  • subordinate node of the first IAB node for example, subordinate node X
  • all subordinate nodes of the same level that is, all sub-nodes that access the cells served by the DU part of the first IAB node
  • the configuration information takes effect within the system to reduce service interruption and delay and improve user experience.
  • the IAB node in addition to considering the topology update caused by the migration of the IAB node or the connection to the new IAB host after performing RRC re-establishment, there is also a dual IAB node.
  • Link In a possible implementation, the IAB node can support dual links within a host node (it can be regarded as the NR-DC of the IAB node, and both the primary station and the secondary station communicate with the IAB node based on NR air interface technology), and also Dual linking of EN-DC scenarios can be supported.
  • the IAB node can form an NR-DC based on the establishment of dual links with two different gNBs, which can be the service data or information of the IAB node and/or subordinate nodes.
  • the transmission provides multiple transmission paths to improve the flexibility and robustness of service data or signaling transmission.
  • the IAB node will only establish an F1 connection (or the control plane of the F1 connection) with one of them, and the base station that establishes the F1 connection with the IAB node is the IAB node.
  • the IAB host IAB donor. Therefore, in the process of establishing a cross-gNB dual link by the IAB node, it is necessary to determine which base station the IAB node's donor node (IAB donor, or the donor base station donor gNB) is.
  • the IAB node is connected to two gNBs, but only establishes a wireless backhaul link on the link corresponding to one of the cell groups (cell group, CG), and establishes a wireless backhaul link on the other CG with the corresponding link
  • the base station establishes the NR Uu interface and does not establish the BH link.
  • the IAB node (specifically, the MT part of the IAB node) first establishes a dual link based on the NR access technology with the two base stations (gNB 1 and gNB 2) according to the way that the UE establishes a dual link (which can be called a dual link).
  • NR-DC NR-DC
  • gNB1 is the master station (MN, master node) of the IAB node
  • gNB2 is the secondary station (SN, secondary node) of the IAB node.
  • the IAB node is the cell served by the DU of gNB1 and the DU of gNB2 directly.
  • the IAB node may also Access is the cell served by other IAB nodes connected to gNB1 and/or gNB2.
  • both gNB1 and gNB2 have the function of IAB donor, that is, they can serve as the host base station of the IAB node to provide services for the IAB node, then in order to determine one of the base stations as the host base station of the IAB node, this application provides the following three methods:
  • the first method is determined by the MN of the IAB node.
  • the MN has the ability of IAB donor, and decides itself as the host base station of the IAB node, so that the MN of the IAB node can generate the second configuration information for the IAB node, which is the startup (setup) of the DU part of the IAB node. ) to prepare, the second configuration information can be used to establish an SCTP association (SCTP association) between the DU part of the IAB node and the MN, conduct security mechanism negotiation (such as IPsec-based security negotiation), and establish an F1 connection, etc.
  • SCTP association SCTP association
  • security mechanism negotiation such as IPsec-based security negotiation
  • the second configuration information required by the MN to prepare for the startup of the DU part of the IAB node may include one or more of the following contents: the IP address of the MN (specifically, the IP address of the MN to be connected as the IAB node) The IP address of the CU, or the IP address of the MN's CU-CP), the IP address of the IAB node, the wireless backhaul RLC channel of the IAB node on the link between the master cell group (MCG) and the parent node ( configuration information of backhaul RLC channel, BH RLC CH), BAP layer identifier (BAP address) of IAB node, default BH RLC CH (default BH RLC CH) identifier between IAB node and parent node on MCG, IAB node The default BAP routing ID (default BAP routing ID) of the upstream, and the BAP layer ID (BAP address) of the parent node on the MCG of the IAB node.
  • the second configuration information may be carried by the MN in
  • the MN selects the SN as the host base station of the IAB node.
  • the SN is required to generate the third configuration information for the IAB node to prepare for the setup of the DU part of the IAB node.
  • the third configuration information can be used to establish SCTP association (SCTP association) between the DU part of the IAB node and the SN, conduct security mechanism negotiation (for example, IPsec-based security negotiation), establish F1 connection, and so on.
  • the third configuration information may include one or more of the following: the IP address of the SN (specifically, the IP address of the CU of the SN to be connected as the IAB node, or the IP address of the CU-CP of the SN), the IP address of the IAB The IP address of the node, the configuration information of the BH RLC CH on the link between the IAB node and the parent node on the SCG (Master cell group), the BAP layer identifier of the IAB node, the parent on the IAB node and the SCG The ID of the default BH RLC CH on the link between nodes, the default BAP routing ID (default BAP routing ID) of the uplink of the IAB node, and the BAP layer ID of the parent node on the SCG of the IAB node.
  • the IP address of the SN specifically, the IP address of the CU of the SN to be connected as the IAB node, or the IP address of the CU-CP of the SN
  • the IP address of the node the configuration
  • the MN needs to notify the SN after determining that the SN is used as the donor base station of the IAB node.
  • the SN is required as the host base station of the IAB node.
  • the third configuration information can be carried by the SN in the RRC message generated by the SN and sent to the IAB node, or the SN can encapsulate the third configuration information in the RRC message container of the Xn interface and send it to the MN, and then the MN sends it to the IAB node.
  • the MN (eg gNB1 in FIG. 9 ) can send a second request message (eg, a secondary station addition request (S-Node addition Request) message, or other messages to the SN (eg gNB2 in FIG. 9 ), specifically for The name of the message is not limited), which carries ninth indication information, and the ninth indication information is used to indicate that the MN wants the SN to be the host node of the IAB node.
  • a second request message eg, a secondary station addition request (S-Node addition Request) message, or other messages to the SN (eg gNB2 in FIG. 9 ), specifically for The name of the message is not limited
  • the ninth indication information is used to indicate that the MN wants the SN to be the host node of the IAB node.
  • the SN can be used as the secondary station of the IAB node and as the host base station of the IAB node, the SN can carry it in the confirmation message (such as S-Node Addition Request Acknowledge) returned to the MN to notify the MN, and the SN confirmation can be used as Information about the host base station of the IAB node.
  • the SN confirmation can be used as the information of the IAB node host base station, which can be an explicit confirmation indication or an implicit indication by carrying the third configuration information.
  • the MN and SN can know whether the other party has this capability through the signaling interaction of the Xn interface, or whether the other party has this capability through the OAM configuration. .
  • the second method is determined by the network management equipment of the IAB node (ie, operation management and maintenance OAM).
  • the IAB node can use the identity of the cell corresponding to the MCG to which it is connected (it may only include the identity of the primary cell on the MCG, or the identity of all cells in the MCG), and the identity of the cell corresponding to the SCG (can only include the identity of the cell on the SCG).
  • the primary cell identity, or the identity of all cells in the SCG) is reported to the OAM first.
  • the OAM can determine the MN as the host base station of the IAB node based on the identity of the cell corresponding to the MCG reported by the IAB node, and can also determine the SN as the host base station of the IAB node based on the identity of the cell corresponding to the SCG reported by the IAB node.
  • OAM After OAM determines whether the MN or SN is the host base station of the IAB node, it can configure the IP address of the selected host base station (specifically, the IP address of the CU of the host base station, or the IP address of the CU-CP) to the IAB node. , so that the IAB node can initiate an F1 connection to the node corresponding to the IP address.
  • the OAM can also send the tenth indication information to the base station selected as the donor base station of the IAB node (gNB1 or gNB2 in Figure 9), to indicate that the base station needs to be the donor base station of the IAB node.
  • the OAM of the IAB node needs to first connect to the OAM (referred to as OAM-IAB) of the base station selected as the donor base station of the IAB node
  • the donor sends notification information (which may include the identity of the donor base station, such as the IP address, or the gNB ID of the donor base station, or the identity of the CU of the donor base station, etc.), and then the OAM-donor sends the first message to the selected donor base station.
  • notification information which may include the identity of the donor base station, such as the IP address, or the gNB ID of the donor base station, or the identity of the CU of the donor base station, etc.
  • the OAM can directly send configuration information to the IAB node to indicate whether the MN or the SN of the IAB node is selected as the home base station. (either the base station corresponding to the MCG or the base station corresponding to the SCG).
  • the IAB node knows whether the host base station is an MN or an SN based on the configuration information received from the OAM, it can directly report a notification message to the base station selected as the host base station through the RRC message, which is used to notify that the base station is the host node of the IAB node. .
  • the IAB node can also report to the MN whether the node selected as the donor base station is an MN or an SN through an RRC message; if it is an SN, the MN can continue to use the method in the first mode, and send the instruction information through the request message of the Xn interface. To the SN, it is used to notify that the SN is selected as the donor base station of the IAB node.
  • the third method is decided by the IAB node at its own discretion.
  • the IAB node (specifically, the MT part of the IAB node) establishes a dual link with the MN and the SN, it can obtain the IP address of the MN in advance (specifically, the IP address of the CU part of the MN, or the IP address of the MN's CU-CP). IP address), and the IP address of the SN (specifically, it can be the IP address of the CU part of the SN, or the IP address of the CU-CP of the SN). or the IAB node obtains the IP addresses of the MN and SN from the MN/SN, or the IAB node obtains the IP address of the MN from the MN, and obtains the IP address of the SN from the SN, etc.
  • the IAB node selects the MN or SN as its host base station by itself, and then can directly report a notification message to the base station selected as the host base station through the RRC message to notify that the base station is the host node of the IAB node.
  • the IAB node can also report to the MN whether the node selected as the donor base station is an MN or an SN through an RRC message; if it is an SN, the MN can continue to use the method in the first mode, and send the instruction information through the request message of the Xn interface. To the SN, it is used to notify that the SN is selected as the donor base station of the IAB node.
  • the default BAP routing ID in the second configuration information will be used to route the upstream data packets (such as the upstream data packets containing the IPsec negotiation process, including the four-step handshake established by SCTP coupling).
  • the upstream data packets such as the upstream data packets containing the IPsec negotiation process, including the four-step handshake established by SCTP coupling.
  • these uplink data packets during the initial startup process will be mapped to the default BH RLC CH.
  • the parent node transmits, so the IAB node needs to know which link the default configuration (default BAP routing ID, and/or default BH RLC CH ID) in the second configuration information is on (or referred to as the default wireless backhaul of the IAB node).
  • link, the configuration information of the default BH link), or the IAB node needs to confirm which CG is the CG served by the host base station (the CG served by the donor corresponds to the default BH link of the IAB node), and then the IAB node will use it.
  • the default link performs the steps required for the initiation of subsequent DUs.
  • the IAB node can determine the link corresponding to the CG served by the host base station, that is, its default wireless For the backhaul link, the default BAP routing ID, default BH RLC CH ID and other configuration information obtained by the IAB node correspond to the default wireless backhaul link.
  • the link between the IAB node and the parent node corresponding to its MCG is the default wireless backhaul link; otherwise, if the SN is the home base station of the IAB node, the IAB node and its The link between the parent nodes corresponding to the SCG is the default wireless backhaul link.
  • the IAB node may receive the configuration information (that is, the second configuration information or the third configuration information, which includes the default BAP routing ID and the default BH RLC CH ID) that includes the DU part of the configuration information required for startup.
  • the configuration information When the configuration information is received, first determine whether the received configuration information is generated by the SN (that is, the configuration information is the third configuration information) or generated by the MN (that is, the configuration information is the second configuration information). If it is determined to be generated by SN, the IAB node considers that the link between it and the parent node corresponding to the SCG is the default BH link; if it is determined to be generated by the MN, the IAB node considers the link between it and the parent node corresponding to the MCG. The link is default BH link. The IAB node determines whether the configuration information is generated by the SN or by the MN. Specifically, there are several possible methods as follows:
  • Method 1 If only one of the two CGs of the IAB node needs to establish a BH link, and the other CG uses the NR Uu interface to communicate directly with the corresponding base station, the IAB node can determine the corresponding The configuration information corresponding to which CG contains the configuration related to the BH RLC CH (for example, the related configuration information of the BH RLC CH that needs to be added or modified), and accordingly, the IAB node determines that the serving base station corresponding to the CG is the donor base station , the link between the IAB node and the parent node corresponding to the CG is the link served by the donor base station, which can be regarded as the default BH link of the IAB node.
  • the serving base station corresponding to the CG is the donor base station
  • the link between the IAB node and the parent node corresponding to the CG is the link served by the donor base station, which can be regarded as the default BH link of the IAB node.
  • the IAB node can determine which base station is the host base station and which CG corresponds to according to the way it receives the configuration information (including default BAP routing ID, default BH RLC CH ID) required for starting its DU part.
  • the link is the default BH link.
  • the IAB node determines the SN as its home base station, and the IAB node The link between the parent node corresponding to its SCG is its default BH link; or, if the RRC message received by the IAB node from SRB1 or SRB2 (that is, the RRC message generated by the MN, specifically the RRC reconfiguration message) contains The configuration information required for the DU part of the above-mentioned IAB node to start, and the configuration information is an RRC message container (RRC container, which can be specifically included in, for example, MRDC-SecondaryCellGroupConfig IE) contained in the RRC message generated by the MN.
  • RRC container which can be specifically included in, for example, MRDC-SecondaryCellGroupConfig IE
  • the IAB node determines that the SN is the home base station, and the link between the IAB node and its parent node corresponding to the SCG is the default BH link;
  • the RRC message received by the SRB2 contains the configuration information required for the startup of the DU part of the IAB node, and the configuration information is directly included in the RRC generated by the MN. If the message is not encapsulated in the RRC message container, the IAB node determines that the MN is the home base station, and the link between the IAB node and the parent node corresponding to the MCG is the default BH link.
  • a suitable base station in the case of establishing dual links between the IAB node and multiple host nodes, can be flexibly determined as the host node of the IAB node, and the DU part of the IAB node can be guaranteed to be compatible with the selected node.
  • the F1 connection is established between the host nodes of the IAB node, which is convenient to provide services for the subordinate nodes in the dual-link scenario of the IAB node. It can not only ensure the normal operation of the IAB node, but also improve the flexibility and robustness of service data or signaling transmission.
  • the IAB node performs intra-host migration or performs cross-host migration, and migrates from the source parent node to the target parent node. If the IAB donor DU connected to the IAB node before and after the migration is different, the IAB node needs to obtain a new IP address, and will use the new IP address to perform the TNL (Transport network layer) migration process.
  • the IAB node performs intra-host migration or performs cross-host migration. is its MT part) in the process of performing RRC re-establishment, the scenario of intra-host migration or cross-host migration realized due to reconstruction to the target parent node.
  • the source parent node and the target parent node of the IAB node are respectively connected to two different IAB donor DUs under the same IAB donor (which can be recorded as source IAB donor DU and target IAB donor DU respectively),
  • the IAB node needs to obtain the IP address related to the target IAB donor DU, and the IAB node performs the TNL migration process, that is, the IAB node negotiates new IPsce security protection related parameters with the IAB donor CU based on the IP address, and can also communicate with the IAB donor CU.
  • a new transport layer association (TNL association, or SCTP association) is established between them, and then the F1 connection between the IAB node and the IAB donor CU is migrated to the target transmission path (that is, part or all of the user plane of the F1 interface
  • the service, and/or the service of part or all of the control plane of the F1 interface, is transmitted via the target transmission path), and the target transmission path is the transmission path between the IAB node through the target parent node and the target IAB donor DU and the IAB donor CU.
  • the IAB donor CU may also be referred to as the source IAB donor CU.
  • the source parent node of the IAB node is connected to the source IAB donor DU under the source IAB donor, and the target parent node is connected to the target IAB donor DU under the target IAB donor, and the IAB node also needs to obtain and target IAB The IP address associated with the donor DU.
  • the IAB node performs the TNL migration process, that is, the IAB node negotiates new IPsce security protection-related parameters with the source IAB donor CU based on the IP address, and also A new transport layer association (TNL association, or SCTP association) can be established with the source IAB donor CU, and then the F1 connection between the IAB node and the source IAB donor CU is migrated to the target transmission path (that is, the F1 interface part or all of the user plane services, and/or, part or all of the control plane services of the F1 interface, are transmitted via the target transmission path), the target transmission path is the IAB node through the target parent node and the target IAB donor DU and the source IAB donor Transmission path between CUs.
  • TNL migration process that is, the IAB node negotiates new IPsce security protection-related parameters with the source IAB donor CU based on the IP address, and also A new transport layer association (TNL association, or SCTP association) can be established with the source IAB donor CU, and
  • the IAB node If the IAB node needs to establish an F1 connection with the target IAB host after the migration, the IAB node performs the TNL migration process, that is, the IAB node negotiates new IPsce security protection related parameters with the target IAB donor CU based on the IP address, and also A new transport layer association (TNL association, or SCTP Association) can be established with the target IAB donor CU, and then the F1 connection between the IAB node and the target IAB donor CU is migrated to the target transmission path (that is, the F1 interface part or all of the user plane services, and/or, part or all of the control plane services of the F1 interface, are transmitted via the target transmission path), the target transmission path is the IAB node through the target parent node and the target IAB donor DU and the target IAB donor Transmission path between CUs.
  • TNL migration process that is, the IAB node negotiates new IPsce security protection related parameters with the target IAB donor CU based on the IP address, and also A new
  • scenario migration process is performed by the IAB node
  • the TNL process also needs to be performed for the subordinate IAB node of the IAB node.
  • IAB node 2 performs cross-host migration and needs to perform a TNL migration process
  • its child node IAB node 3 also needs to perform a similar TNL migration process.
  • each node needs to obtain necessary configuration information related to TNL migration through an RRC message, including: the new IP address to be used on the target path, and also needs to obtain the IP address corresponding to the target transmission path.
  • the default upstream routing ID (default BAP routing ID) and the default BH RLC CH (default BH RLC CH, identified by the default BH RLC CH ID) are used to transmit the IAB node that needs to be sent to the IAB donor CU during the TNL process upstream message).
  • These necessary configuration information related to TNL migration is sent to each IAB node through RRC messages by the source IAB donor CU to which the MT part of each IAB node is connected. It is understandable that there may be multi-level subordinate nodes such as child nodes and grandchild nodes under the IAB node that performs the migration. If the TNL migration is performed in order from top to bottom, that is, each subordinate node completes the TNL migration of the upper-level node.
  • the entire IAB node migration process After starting to perform its own TNL migration (including obtaining the necessary configuration information related to TNL, and executing the TNL migration process based on the configuration information), the entire IAB node migration process will continue for a long time, which will cause service interruption and delay to the UE. great influence.
  • two solutions are proposed in the embodiments of the present application.
  • the first IAB node and the second IAB node are both IAB nodes that need to perform TNL migration due to the update of the IAB network topology, and the first IAB node is the parent node of the second IAB node.
  • the first IAB node is IAB node 2 in FIG. 7
  • the second IAB node is IAB node 3 in FIG. 7 .
  • Solution 1 The source IAB donor CU sends an RRC message (referred to as the first RRC message) containing the configuration information related to the TNL migration performed by the second IAB node to the first IAB node in advance, and the first IAB node first caches the second IAB node.
  • the first RRC message of the IAB node and after determining that condition 1 is satisfied, the first RRC message is sent to the second IAB node.
  • the manner may specifically include the following steps:
  • Step 1 the source IAB donor CU sends an RRC message (referred to as the first RRC message) containing the configuration information related to the TNL migration performed by the second IAB node to the first IAB node.
  • the IAB donor CU encapsulates the first RRC message in the F1AP message of the first IAB node, and carries the twelfth indication information in the F1AP message, which is used to instruct the first IAB node to cache the first RRC message therein.
  • Step 2 the first IAB node obtains configuration information, and determines that condition 1 takes effect.
  • the configuration information includes the configuration related to the routing and bearer mapping of the first IAB node on its target path, which can be used to transmit data packets related to TNL migration of the second IAB node.
  • the part related to the routing configuration obtained by the first IAB node includes the routing mapping table item related to the default BAP routing ID of the second IAB node on the target path, that is, it includes: the default BAP routing ID of the second IAB node on its target path BAP routing ID, and the identifier of the next hop node of the first IAB node corresponding to the default BAP routing ID.
  • the part related to the bearer mapping configuration includes the entry related to the default BH RLC CH of the second IAB node on the target path, that is, it includes: the BH RLC CH on the ingress link is the default BH of the second IAB node on the target path In the case of RLC CH, the identifier of the BH RLC CH of the egress link at the corresponding first IAB node.
  • the identity of the BH RLC CH of the egress link is jointly determined by the identity of the next hop node of the first IAB node and the BH RLC CH ID between the first IAB node and the next hop node.
  • the configuration information obtained by the first IAB node may carry thirteenth indication information, which is used to indicate that the first IAB node can send the first RRC message buffered by the first IAB node to the second IAB node.
  • the first IAB node may obtain the configuration information in step 2 from the source IAB donor CU through an RRC message or an F1AP message, or the first IAB node may obtain the configuration information in step 2 through an F1AP message after performing TNL migration.
  • the connected IAB donor CU obtains the configuration information in this step 2.
  • the first IAB node may determine that condition 1 is effective, and it may send the first RRC message to the second IAB node.
  • the first IAB node may determine, according to the thirteenth indication information in the configuration information obtained in step 2, that it can send the first RRC message cached by it to the second IAB node.
  • condition 1 is that the first IAB node receives the thirteenth indication information.
  • the configuration information obtained by the first IAB node in step 2 includes the configuration information related to the route and bearer mapping of the first IAB node on the target path, it is considered that these routes are related to the bearer mapping configuration.
  • condition 1 is that the first IAB node receives The configuration related to routing and bearer mapping on the target path, or the configuration related to routing and bearer mapping received by the first IAB node on its target path that can be used to transmit TNL migration related data packets of the second IAB node.
  • Step 3 the first IAB node sends the first RRC message to the second IAB node.
  • Step 4 the second IAB node performs a TNL migration process based on the first RRC message.
  • Solution 2 The source IAB donor CU sends an RRC message (referred to as the first RRC message) containing the configuration information related to the TNL migration performed by the second IAB node to the second IAB node in advance, and the first RRC message includes the tenth Four indication information is used to instruct the second IAB node to take effect of the first RRC message after the condition 2 is satisfied, and the second IAB node executes the TNL migration process after taking effect of the first RRC message.
  • the first RRC message includes the tenth Four indication information is used to instruct the second IAB node to take effect of the first RRC message after the condition 2 is satisfied
  • the manner may specifically include the following steps:
  • Step 1 the source IAB donor CU sends an RRC message (referred to as the first RRC message) containing the configuration information related to the TNL migration performed by the second IAB node to the second IAB node.
  • the IAB donor CU encapsulates the first RRC message in the F1AP message of the first IAB node, and the first IAB node sends the first RRC message contained therein to the second IAB node after receiving the F1AP message.
  • the first RRC message includes fourteenth indication information, which is used to instruct the second IAB node not to take effect of the first RRC message first, or to instruct the second IAB node to take effect only after condition 2 is satisfied. RRC message.
  • Step 2 the first IAB node obtains configuration information, and determines that condition 1 takes effect.
  • the configuration information includes the configuration related to the routing and bearer mapping of the first IAB node on its target path, which can be used to transmit data packets related to TNL migration of the second IAB node.
  • the part related to the routing configuration obtained by the first IAB node includes the routing mapping table item related to the default BAP routing ID of the second IAB node on the target path, that is, it includes: the default BAP routing ID of the second IAB node on its target path BAP routing ID, and the identifier of the next hop node of the first IAB node corresponding to the default BAP routing ID.
  • the part related to the bearer mapping configuration includes the entry related to the default BH RLC CH of the second IAB node on the target path, that is, it includes: the BH RLC CH on the ingress link is the default BH of the second IAB node on the target path In the case of RLC CH, the identifier of the BH RLC CH of the egress link at the corresponding first IAB node.
  • the identity of the BH RLC CH of the egress link is jointly determined by the identity of the next hop node of the first IAB node and the BH RLC CH ID between the first IAB node and the next hop node.
  • the configuration information obtained by the first IAB node may carry thirteenth indication information, which is used to indicate that the first IAB node can send the first RRC message buffered by the first IAB node to the second IAB node.
  • the first IAB node may obtain the configuration information in step 2 from the source IAB donor CU through an RRC message or an F1AP message, or the first IAB node may obtain the configuration information in step 2 through an F1AP message after performing TNL migration.
  • the connected IAB donor CU obtains the configuration information in this step 2.
  • the first IAB node may determine that condition 1 is effective, and it may send the first RRC message to the second IAB node.
  • the first IAB node may determine, according to the thirteenth indication information in the configuration information obtained in step 2, that it can send the first RRC message cached by it to the second IAB node.
  • condition 1 is that the first IAB node receives the thirteenth indication information.
  • the configuration information obtained by the first IAB node in step 2 includes the configuration information related to the route and bearer mapping of the first IAB node on the target path, it is considered that these routes are related to the bearer mapping configuration.
  • condition 1 is that the first IAB node receives The configuration related to routing and bearer mapping on the target path, or the configuration related to routing and bearer mapping received by the first IAB node on its target path that can be used to transmit TNL migration related data packets of the second IAB node.
  • Step 3 the first IAB node sends fifteenth indication information to the second IAB node, and based on the fifteenth indication information, the second IAB node determines that the condition 2 takes effect.
  • the first IAB node sends fifteenth indication information to the second IAB node.
  • the fifteenth indication information can be carried in the control PDU (BAP control PDU) of the BAP layer and sent to the second IAB node, or carried in the control element (MAC control element, MAC CE) of the MAC layer and sent to the second IAB sent by the node, or sent to the second IAB node after being carried by the downlink control information (Downlink Control Information, DCI) of the physical layer.
  • BAP control PDU control PDU
  • MAC control element MAC control element
  • Step 4 the second IAB node performs a TNL migration process based on the first RRC message.
  • the IAB node and the subordinate nodes can perform the TNL migration process in a very compact manner, avoiding the subordinate nodes due to the connection establishment to the upstream node and the If you do not know the configuration acquisition status, and make unnecessary TNL migration attempts in advance, the migration will fail, and you need to try again, which will prolong the execution time of the entire topology update process, and avoid the entire topology caused by the subordinate nodes performing TNL migration too late.
  • the execution time of the update process is stretched. In this way, the impact of the IAB migration process on the service interruption duration of the UE can be effectively reduced.
  • the embodiment of the present application can also implement that the IAB node selects a buffer status report (Buffer status report, BSR) format when the wireless backhaul link supports logical channel group (Logical channel group, LCG) extension.
  • BSR buffer status report
  • LCG Logical channel group
  • LCG ID the identifier of the logical channel group, with a length of 3 bits.
  • LCG i In the Long BSR (Long BSR) format, the value of this field is 1, indicating that the BSR contains the Buffer Size field of logical channel group i, if the value of this field is 0, it indicates that the BSR does not contain logical channels Buffer Size field of group i.
  • this field In the format of Long truncated BSR (truncated long BSR), this field is used to indicate whether logical channel group i has data to be sent. Specifically, the value of this field is 1 to indicate that logical channel group i has data to be sent. A value of 0 indicates that logical channel group i has no data to send. Among them, i is an integer, and the value range is 0 ⁇ i ⁇ 7.
  • Buffer Size It is used to indicate the sum of the amount of data to be sent corresponding to all logical channels in a logical channel group.
  • the data amount of each logical channel group refers to the corresponding statistics of each logical channel in the logical channel group after the MAC PDU is grouped.
  • the unit of data amount is byte.
  • the Buffer Size field corresponding to each LCG is 5 bits in length in short BSR or short truncated BSR format, and 8 bits in length in long BSR or long truncated BSR.
  • a possible implementation is that there may be multiple IAB nodes within the jurisdiction of the IAB host, and each wireless backhaul node can provide access and Backhaul service, considering that the UEs served by these IAB nodes may have many different types of services, and the QoS requirements of different types of services of these different UEs are also different.
  • the BH RLC CH is used to provide different QoS guarantees for data or signaling in the wireless backhaul link. In a wireless backhaul link, the maximum number of BH RLC CHs can reach more than 60,000, and each BH RLC CH corresponds to a logical channel.
  • the MT part of the IAB node will report the BSR to the parent node, which is used to inform the parent node of the data volume of the uplink data packets to be sent.
  • the BSR can be regarded as a way for the child node to request uplink scheduling resources from the parent node. , so that the DU part of the parent node allocates uplink transmission resources for it.
  • the amount of buffered data is reported with LCG as the granularity.
  • BSR can have many different formats, for example, in short BSR type or short truncated BSR type, see Figure 10, it can only contain the cache status information of one LCG; while in long BSR type or Long truncated BSR type, see Figure 11 Can contain up to 8 LCGs of cache status information.
  • Each logical channel group generally contains logical channels with similar scheduling requirements, and the specific logical channels in each logical channel group are determined by the parent node of the IAB node and the configuration information is generated, and then passed through the IAB host ( When the IAB host is CU-DU separation, it is specifically the IAB host CU; when the IAB host CU is CP-UP separation, it can also be the RRC message of the IAB host CU-CP) sent to the IAB node.
  • each logical channel group may contain thousands of logical channels, and the scheduling requirements of these thousands of logical channels may vary greatly. Therefore, in this application, it is considered to expand the number of LCGs of the wireless backhaul link, so that the logical channels with large differences in scheduling requirements can be configured in different logical channel groups respectively, so as to improve the rationality and fairness of scheduling.
  • the maximum value of the extended LCG may be, for example, 16, 32, 64, and 256, and the specific value is not limited in this embodiment of the present application.
  • the logical channel group ID (Logical Channel Group ID, LCG ID) also needs to be expanded.
  • LCG ID Logical Channel Group ID
  • the LCG ID may be expanded to 4 bits.
  • the maximum value of LCG is extended to 256, then the LCG ID needs to be extended to 8bits.
  • the BSR format also needs to be expanded, and a new BSR format needs to be introduced.
  • the maximum value of LCG is extended to 256, it is necessary to introduce a new short BSR format that supports extended LCG, a new truncated short BSR format that supports extended LCG, and a new long BSR format that supports extended LCG and supports extended LCG
  • the new truncated long BSR format it is assumed that the new short BSR format and the new truncated short BSR format are shown in Figure 12 below. In another possible example, it is assumed that the new long BSR format is shown in Figure 13 below.
  • the embodiments of the present application Not limited.
  • the present application proposes the following to report the buffered data volume information on the wireless backhaul link
  • the scheme for selecting the BSR format of the IAB node is applicable to the IAB node (specifically, it can be the MT part of the IAB node).
  • an IAB node when configured with an extended LCG, when the IAB node needs to report a BSR, it adopts a new BSR format that supports the extended LCG.
  • the IAB node is configured with an extended LCG, and the BSR needs to include the buffer status information in at least one extended LCG, a new BSR format that supports the extended LCG is adopted;
  • the existing BSR format that is, the short BSR/short truncated BSR/long BSR/long truncated BSR format specified by the existing protocol, or collectively referred to as legacy BSR.
  • legacy BSR the existing BSR format
  • the IAB node is configured with an extended LCG, but all the LCG IDs that need to report the cache status are legacy LCGs, and the existing BSR format is still used.
  • the IAB node can still use the existing BSR format to report the buffered data volume information in some cases, which can be to a certain extent. save on reporting costs.
  • the number of LCGs and the length of the LCG ID on the wireless backhaul link can still be configured, and based on the number of configured LCG IDs and/or the length of the LCG ID, the IAB node can determine a new BSR format that supports the extended LCG . Wherein, the IAB node obtains the configuration information of the number of LCGs and/or the length of the LCG ID on the wireless backhaul link between it and the parent node.
  • the donor is assigned to the IAB node; or after being determined by the IAB donor, it is directly assigned to the IAB node; or after being determined by the IAB donor, it is first assigned to the parent node of the IAB node, and then assigned to the IAB by the parent node of the IAB node. node.
  • X 256
  • the maximum number of LCGs between the IAB node and the parent node is configured to be 16, and the length of the LCG ID is 4 bits
  • the IAB node needs to use the BSR that supports the extended LCG.
  • a new BSR format that supports extended LCGs corresponding to a maximum number of 16 LCGs can be selected.
  • the format of the short BSR that supports extended LCG and the maximum number of extended LCGs is 16 can be the lowest 4 corresponding to the first byte (Oct 1) in the format shown in Figure 12.
  • the bits are set to reserved bits, or the lowest 4 bits corresponding to the first byte (Oct 1) are set together with the highest 4 (or 2) bits in the second byte For the Buffer Size field, set the lowest 4 (or 6) bits in the second byte as reserved bits.
  • the format of the long BSR that supports extended LCG and the maximum number of extended LCGs is 16 can be in the format shown in Figure 13, the first byte (Oct 1) and the second byte (Oct 2) is set to the bitmap corresponding to the LCG ID from the maximum value (LCG 15) to the minimum value (LCG 0), and the part after the third byte is set to correspond to the LCG whose value is 1 in the bitmap Buffer size field of .
  • the embodiment of the present application does not limit the specific setting of the new BSR format that the wireless backhaul link supports different LCG ID lengths or supports different extended LCG numbers.
  • the logical channel group whose LCG ID is greater than 7 can be regarded as an extended LCG, and the LCG ID is ⁇ 0, 1, 2, 3, 4, 5, 6, 7
  • the logical channel group with the value in ⁇ is regarded as a legacy LCG.
  • the IAB node adopts which of the new BSR formats that support extended LCG (new short BSR format, new truncated short BSR format, new long BSR format, new truncated long BSR format), it is still It is determined according to the specific requirements of the report, which is similar to the way that the current IAB node or UE selects a format from ⁇ short BSR, short truncated BSR, long BSR, long truncated BSR ⁇ . For example, if the IAB node only needs to send When the parent node reports the buffer status information in an extended LCG on the wireless backhaul link, the new short BSR format may be used.
  • the IAB node can select an appropriate BSR format for BSR reporting according to the actual situation of the link between it and the parent node, which can save energy Signaling overhead.
  • FIG. 14 is a schematic structural diagram of an apparatus for updating an IAB node connection according to an embodiment of the present application, where the apparatus is used to implement the method described in the foregoing method embodiment.
  • the apparatus includes: a first transceiver module 1402 and a connection module 1404;
  • the first transceiver module 1402 is configured to receive the first indication information
  • the connection module 1404 is configured to establish an F1 connection between the DU part of the first IAB node and the target IAB host according to the first indication information.
  • the above device also includes:
  • the changing module is used to change the cell served by the DU part of the first IAB node from the cell hosted by the source IAB to the cell hosted by the target IAB.
  • the first transceiver module 1402 includes:
  • the first transceiver sub-module is configured to receive the first indication information from the source IAB host; or
  • the second transceiver sub-module is configured to receive the first indication information from the operation, management and maintenance OAM.
  • the first indication information is the IP address of the target IAB host.
  • the first indication information includes the IP address of the target IAB host, and explicit indication information for instructing the DU part of the first IAB node to initiate establishing an F1 connection with the target IAB host.
  • the second transceiver sub-module is specifically used for:
  • the target cell is the cell accessed by the first IAB node after connection update
  • the first indication information from the operation, management and maintenance OAM is received.
  • the first transceiver sub-module is specifically used for:
  • the source IAB host sending a measurement report to the source IAB host; wherein, the first indication information is determined by the source IAB host based on the measurement report;
  • the first indication information from the source IAB host is received.
  • the first transceiver sub-module is specifically used for:
  • the MT part of the first IAB node performs a radio resource control RRC re-establishment process after a radio link failure occurs, and connects with the target IAB host after accessing the target cell; wherein, the first indication information is that the source IAB host is based on the request for the first IAB host. Determined by a request message for the context of an IAB node, the request message for requesting the context of the first IAB node is sent by the target IAB host to the source IAB host;
  • the first indication information from the source IAB host is received.
  • the third transceiver sub-module is configured to receive the second indication information
  • the changing submodule is configured to change the cell served by the DU part of the first IAB node from the cell hosted by the source IAB to the cell hosted by the target IAB according to the second indication information;
  • the first determining module is configured to determine that the subordinate UE and/or subordinate IAB node of the first IAB node have received the configuration information
  • the change submodule is used to change the cell served by the DU part of the first IAB node from the cell hosted by the source IAB to the cell hosted by the target IAB;
  • the configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • RRC configuration information or
  • the third transceiver sub-module is configured to receive the second indication information, and determine that the subordinate UE and/or subordinate IAB node of the first IAB node have received the configuration information;
  • the change submodule is used to change the cell served by the DU part of the first IAB node from the cell hosted by the source IAB to the cell hosted by the target IAB;
  • the configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • RRC configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • the third transceiver sub-module is specifically used for:
  • the MT part of the first IAB node is still connected to the source IAB host, and the MT part of the first IAB node receives the second indication information carried by the radio resource control RRC message from the source IAB host;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB;
  • the DU part of the first IAB node receives the second indication information carried by the F1 application protocol F1AP message from the source IAB host;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB.
  • the third transceiver sub-module is specifically used for:
  • the MT part of the first IAB node has been connected to the target IAB host, and the MT part of the first IAB node receives the second indication information carried by the radio resource control RRC message from the target IAB host;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB;
  • the DU part of the first IAB node receives the second indication information carried by the F1 application protocol F1AP message from the target IAB host;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB.
  • the first determining module is specifically used for:
  • the DU part of the first IAB node receives the F1 application protocol F1AP message from the source IAB host, the F1 application protocol F1AP message carries an RRC message container, and the RRC message container is encapsulated with the subordinate UE of the first IAB node and/or the subordinate IAB node.
  • RRC message ;
  • the F1 application protocol F1AP message carries the third indication information, after successfully sending the RRC message to the subordinate UE and/or subordinate IAB node of the first IAB node, determine the subordinate UE and/or subordinate IAB of the first IAB node The node receives configuration information; or
  • the F1 application protocol F1AP message is carried in the data packet of the first sequence number
  • the subordinate IAB node receives the configuration information, wherein the first sequence number is the data packet sequence number of the SCTP layer of the flow control transmission protocol, and is configured by the source IAB host to the first IAB node.
  • the third indication information is indication information used to instruct the first IAB node to stop scheduling data transmission to its subordinate UEs and/or subordinate IAB nodes;
  • the third indication information is used to indicate that the RRC message carried in the RRC message container includes the RRC configuration information required by the subordinate UE and/or subordinate IAB node of the first IAB node to access the cell under the target IAB host, wherein, The cell hosted by the target IAB is the cell served by the DU part of the first IAB node after the cell it serves is changed to the cell hosted by the target IAB.
  • the above device also includes:
  • the second determining module is configured to determine the first IAB node carried in the F1 application protocol F1AP message according to the third indication information carried in the F1 application protocol F1AP message or according to the data packet of the first sequence number carried in the F1 application protocol F1AP message
  • the RRC message of the subordinate UE and/or the subordinate IAB node includes that the subordinate UE and/or the subordinate IAB node of the first IAB node access the target after the cell served by the DU part of the first IAB node is changed to the cell hosted by the target IAB.
  • the above device also includes:
  • the broadcasting module is used for the DU part of the first IAB node to broadcast fourth indication information, and the fourth indication information is used to indicate the subordinate UE and/or subordinate IAB node of the first IAB node to take effect configuration information; or
  • the second transceiver module is used for indicating duration information to the subordinate UE and/or subordinate IAB node of the first IAB node, and the duration information is used to indicate the moment when the subordinate UE and/or subordinate IAB node of the first IAB node takes effect of the configuration information.
  • FIG. 15 is a schematic structural diagram of an apparatus for updating an IAB node connection provided by an embodiment of the present application, and the apparatus is used to implement the method described in the foregoing method embodiment.
  • the apparatus includes: a third determination module 1502 and a third transceiver module 1504;
  • the third determining module 1502 is configured to determine that the DU part of the first IAB node needs to perform a connection update to establish an F1 connection with the target IAB host;
  • the third transceiver module 1504 is configured to send first indication information to the first IAB node, where the first indication information is used to instruct the DU part of the first IAB node to establish an F1 connection with the target IAB host.
  • the above device further includes:
  • the fourth transceiver module is used to send second indication information to the first IAB node, where the second indication information is used to instruct the cell served by the DU part of the first IAB node to change from the cell hosted by the source IAB to the cell hosted by the target IAB .
  • the above device further includes:
  • the fifth transceiver module is used to send the first request message to the target IAB host, and the first request message is used to request the IP address of the target IAB host;
  • the fifth transceiver module is also used to receive the first response message from the target IAB host, and the first response message includes the IP address of the target IAB host;
  • the first indication information is the IP address of the target IAB host.
  • the first indication information includes the IP address of the target IAB host, and explicit indication information for instructing the DU part of the first IAB node to initiate establishing an F1 connection with the target IAB host.
  • sending the first indication information to the first IAB node includes:
  • the source IAB host determines the first indication information
  • sending the first indication information to the first IAB node includes:
  • the MT part of the first IAB node is connected to the target IAB donor after performing the RRC re-establishment procedure of the radio resource control after the radio link failure occurs, and then receives the request from the target IAB donor for requesting the first IAB from the target IAB donor.
  • the request message for the context of the node based on the request message for requesting the context of the first IAB node, to determine the first indication information, wherein the target cell is the cell accessed by the first IAB node after connection update;
  • the fourth transceiver module is specifically used for:
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB;
  • the second indication information is used to indicate that the cell served by the DU part of the first IAB node can be changed to the cell under the host of the target IAB.
  • the above device further includes:
  • the sixth transceiver module is used to send the F1 application protocol F1AP message to the DU part of the first IAB node, the F1 application protocol F1AP message carries the RRC message container and the third indication information, and the RRC message container is encapsulated with the subordinate UE of the first IAB node. and/or the RRC message of the subordinate IAB node, so that the first IAB node determines the subordinate UE and/or subordinate IAB node of the first IAB node after successfully sending the RRC message to the subordinate UE and/or subordinate IAB node of the first IAB node
  • the IAB node receives the configuration information;
  • the configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • RRC configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • the third indication information is indication information used to instruct the first IAB node to stop scheduling data transmission to its subordinate UEs and/or subordinate IAB nodes;
  • the third indication information is used to indicate that the RRC message carried in the RRC message container includes the RRC configuration information required by the subordinate UE and/or subordinate IAB node of the first IAB node to access the cell under the target IAB host, wherein the target IAB host
  • the cell below is the cell served by the DU part of the first IAB node after the cell it serves is changed to the cell hosted by the target IAB.
  • FIG. 16 is a schematic structural diagram of an apparatus for updating an IAB node connection provided by an embodiment of the present application, where the apparatus is used to implement the method described in the foregoing method embodiment.
  • the apparatus includes: a fourth determination module 1602 and a seventh transceiver module 1604;
  • the fourth determining module 1602 is configured to determine that the DU part of the first IAB node needs to establish an F1 connection with the target IAB host;
  • the seventh transceiver module 1604 is configured to send first indication information to the first IAB node, where the first indication information is used to instruct the first IAB node to establish an F1 connection with the target IAB host.
  • the first indication information is the IP address of the target IAB host, or
  • the first indication information includes the IP address of the target IAB host, and explicit indication information for instructing the DU part of the first IAB node to initiate establishing an F1 connection with the target IAB host.
  • FIG. 17 is a schematic structural diagram of an apparatus for updating an IAB node connection provided by an embodiment of the present application, where the apparatus is used to implement the method described in the foregoing method embodiment.
  • the apparatus includes: an eighth transceiver module 1702 and a validating module 1704;
  • the eighth transceiver module 1702 is configured to receive the configuration information of the DU part from the first IAB node;
  • the configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • RRC configuration information is required by the subordinate UE of the first IAB node and/or the subordinate IAB node to access the cell under the target IAB host after the cell served by the DU part of the first IAB node is changed to the cell under the target IAB host.
  • the validation module 1704 is used for validating the configuration information.
  • the configuration information includes fifth indication information, where the fifth indication information is used to indicate the delayed effective configuration information
  • the validating module 1704 is specifically used for:
  • the configuration information is validated.
  • the above device further includes:
  • the ninth transceiver module is used to receive the duration information from the first IAB node, and the duration information is used to indicate the moment when the subordinate UE of the first IAB node and/or the subordinate IAB node takes effect of the configuration information;
  • the validating module 1704 is specifically used for:
  • the configuration information takes effect according to the time when the configuration information takes effect.
  • the validation module 1704 is specifically used for:
  • the configuration information takes effect
  • the target cell is the cell served by the DU part of the first IAB node after the cell it serves is changed to a cell hosted by the target IAB, and is identified by the target cell identifier in the configuration information.
  • the validation module 1704 is specifically used for:
  • the schematic structural diagram of IAB node connection update as shown in FIG. 14 , 15 , 16 , or 17 provided in this embodiment of the present application may also perform various steps in Embodiment 2, Embodiment 3, or Embodiment 4.
  • An embodiment of the present application further provides an IAB node connection update device, including at least one processor, the processor is configured to execute a program stored in a memory, and when the program is executed, the device executes as shown in Figure 8(a) ), each step of the method for updating the connection of the IAB node as shown in FIG. 8(b) and/or FIG. 8(c).
  • an IAB node connection update device including at least one processor, the processor is configured to execute a program stored in a memory, and when the program is executed, the device executes as shown in Figure 8(a) ), each step of the method for updating the connection of the IAB node as shown in FIG. 8(b) and/or FIG. 8(c).
  • An embodiment of the present application provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium.
  • a computer program is stored on the computer-readable storage medium.
  • FIG. 8(a) When the computer program is executed by a processor, as shown in FIG. 8(a), FIG. 8(b) and/or Or each step of the IAB node connection update method as shown in FIG. 8(c) is performed.
  • the embodiments of the present application also provide a computer program product including instructions, when the computer program product is run on a computer, the computer is made to execute as shown in Fig. 8(a), as shown in Fig. 8 (b) and/or each step of the IAB node connection update method as shown in FIG. 8(c).

Landscapes

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

Abstract

本申请实施例公开了一种IAB节点连接更新方法及装置，方法包括：源IAB宿主确定所述第一IAB节点的DU部分需要执行连接更新与所述目标IAB宿主建立F1连接；第一IAB节点接收第一指示信息；根据所述第一指示信息，所述第一IAB节点的DU部分与所述目标IAB宿主建立F1连接。通过上述方法，在需要将第一IAB节点的DU部分在不同IAB宿主的CU之间进行连接更新的情况下，可以及时触发第一IAB节点与目标IAB宿主的CU之间建立F1连接，减小时延。

Description

一种IAB节点连接更新方法及装置
本申请要求于2021年05月07日提交中国国家知识产权局、申请号为202110497401.2、申请名称为“一种IAB节点连接更新方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种IAB节点连接更新方法及装置。
背景技术
相较于第四代移动通信网络(4th generation mobile networks,4G)，第五代移动通信网络(5th generation mobile networks,5G)针对网络各项性能指标，全方位地提出了更严苛的要求。例如，容量指标提升1000倍，更广的覆盖需求、超高可靠超低时延等。一方面，考虑到高频载波频率资源丰富，在热点区域，为满足5G超高容量需求，利用高频小站组网愈发流行。然而，高频载波传播特性较差，受遮挡衰减严重，覆盖范围不广，故而需要大量密集部署高频小站，相应地，为这些大量密集部署的高频小站提供光纤回传的代价很高，施工难度大，因此需要经济便捷的回传方案；另一方面，从广覆盖需求的角度出发，在一些偏远地区提供网络覆盖，光纤的部署难度大，成本高，也需要设计灵活便利的接入和回传方案。
发明内容
本申请实施例提出一种IAB节点连接更新方法及装置，能够实现在两个不同的IAB宿主之间进行IAB节点的DU部分的切换和服务的小区的切换。
第一方面，本申请实施例提出一种IAB节点连接更新方法，应用于第一IAB节点，第一IAB节点包含MT部分和DU部分，可以为一个或多个下属UE和/或下属IAB节点提供接入和回传服务，第一IAB节点在连接更新前连接到源IAB宿主，在连接更新后连接到目标IAB宿主，该方法包括：
接收第一指示信息；
根据第一指示信息，第一IAB节点的DU部分与目标IAB宿主建立F1连接。
本申请实施例利用第一指示信息，及时触发第一IAB节点的DU部分与目标IAB宿主建立F1连接，减小时延。
在一种可能的实现中，上述方法还包括：
将第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区。
在一种可能的实现中，接收第一指示信息，包括：
接收来自源IAB宿主的第一指示信息；或者
接收来自操作管理维护OAM的第一指示信息。
在一种可能的实现中，第一指示信息为目标IAB宿主的IP地址；或者，
第一指示信息包括目标IAB宿主的IP地址，以及用于指示第一IAB节点的DU部分发起与目标IAB宿主之间建立F1连接的显式指示信息。
在一种可能的实现中，接收来自操作管理维护OAM的第一指示信息，包括：
确定目标小区的标识，目标小区是第一IAB节点进行连接更新后接入的小区；
将目标小区的标识发送至操作管理维护OAM，以使得操作管理维护OAM基于目标小区的标识，确定目标IAB宿主；
接收来自操作管理维护OAM的第一指示信息。
在一种可能的实现中，接收来自源IAB宿主的第一指示信息，包括：
向源IAB宿主发送测量报告；其中，第一指示信息为源IAB宿主基于测量报告确定的；
接收来自源IAB宿主的第一指示信息。
在一种可能的实现中，接收来自源IAB宿主的第一指示信息，包括：
第一IAB节点的MT部分在发生无线链路失败后执行无线资源控制RRC重建立过程，接入目标小区后与目标IAB宿主进行连接；其中，第一指示信息为源IAB宿主基于用于请求第一IAB节点的上下文的请求消息确定的，用于请求所述第一IAB节点的上下文的请求消息是由目标IAB宿主向源IAB宿主发送的；
接收来自源IAB宿主的第一指示信息。
在一种可能的实现中，所述将第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区，包括：
接收第二指示信息；
根据第二指示信息，将第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区；或者
确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息；
将第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区；
其中，配置信息为第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息；或者
接收第二指示信息，并确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息；
将第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区；
其中，配置信息为第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息。
在一种可能的实现中，所述接收第二指示信息，包括：
所述第一IAB节点的MT部分仍然连接至所述源IAB宿主，所述第一IAB节点的MT部分接收来自所述源IAB宿主通过无线资源控制RRC消息携带的所述第二指示信 息；或者
所述第一IAB节点的DU部分接收来自所述源IAB宿主通过F1应用协议F1AP消息携带的所述第二指示信息；
其中，所述第二指示信息用于指示可以将所述第一IAB节点的DU部分所服务的小区变更至所述目标IAB宿主下的小区。
在一种可能的实现中，接收第二指示信息，包括：
第一IAB节点的MT部分已连接至目标IAB宿主，第一IAB节点的MT部分接收来自目标IAB宿主通过无线资源控制RRC消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区；或者
第一IAB节点的DU部分接收来自目标IAB宿主通过F1应用协议F1AP消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区。
在一种可能的实现中，确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息，包括：
第一IAB节点的DU部分从源IAB宿主接收到F1应用协议F1AP消息，F1应用协议F1AP消息中携带RRC消息容器，RRC消息容器中封装有第一IAB节点的下属UE和/或下属IAB节点的RRC消息；
若F1应用协议F1AP消息中携带有第三指示信息，则在将RRC消息成功发送至第一IAB节点的下属UE和/或下属IAB节点后，确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息；或者
若F1应用协议F1AP消息被携带在第一序号的数据包中，则在将RRC消息成功发送至第一IAB节点的下属UE和/或下属IAB节点后，确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息，其中，第一序号是流控传输协议SCTP层的数据包序号，由所述源IAB宿主配置给第一IAB节点。
在一种可能的实现中，第三指示信息为用于指示第一IAB节点停止对其下属UE和/或下属IAB节点进行数据传输调度的指示信息；或者
第三指示信息为用于指示RRC消息容器中携带的RRC消息中，包含第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息，其中，目标IAB宿主下的小区是第一IAB节点的DU部分在其服务的小区变更为目标IAB宿主下的小区后所服务的小区。
在一种可能的实现中，上述方法还包括：
根据F1应用协议F1AP消息中携带的第三指示信息或者根据F1应用协议F1AP消息被携带在第一序号的数据包，确定F1应用协议F1AP消息中携带的第一IAB节点的下属UE和/或下属IAB节点的RRC消息包含第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息，则
先缓存第一IAB节点的下属UE和/或下属IAB节点的RRC消息，在接收到第二指示信息后，再向第一IAB节点的下属UE和/或下属IAB节点发送其RRC消息。
在一种可能的实现中，上述方法还包括：
第一IAB节点的DU部分广播第四指示信息，第四指示信息用于指示第一IAB节点的下属UE和/或下属IAB节点生效配置信息；或者
向第一IAB节点的下属UE和/或下属IAB节点指示时长信息，时长信息用于指示第一IAB节点的下属UE和/或下属IAB节点生效配置信息的时刻。
第二方面，本申请实施例还提出一种IAB节点连接更新方法，应用于源IAB宿主，第一IAB节点在连接更新前连接到源IAB宿主，第一IAB节点包含MT部分和DU部分，可以为一个或多个下属UE和/或下属IAB节点提供接入和回传服务，且第一IAB节点在连接更新后连接到目标IAB宿主，该方法包括：
确定第一IAB节点的DU部分需要执行连接更新与目标IAB宿主建立F1连接；
向第一IAB节点发送第一指示信息，第一指示信息用于指示第一IAB节点的DU部分与目标IAB宿主建立F1连接。
本申请实施例通过第一指示信息，及时触发第一IAB节点的DU部分与目标IAB宿主建立F1连接，减小时延。
在一种可能的实现中，上述方法还包括：
向第一IAB节点发送第二指示信息，第二指示信息用于指示第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区。
在一种可能的实现中，上述方法还包括：
向目标IAB宿主发送第一请求消息，第一请求消息用于请求目标IAB宿主的IP地址；
接收来自目标IAB宿主的第一响应消息，第一响应消息包括目标IAB宿主的IP地址；
其中，第一指示信息为目标IAB宿主的IP地址；或者，
第一指示信息包括目标IAB宿主的IP地址，以及用于指示第一IAB节点的DU部分发起与目标IAB宿主之间建立F1连接的显式指示信息。
在一种可能的实现中，向第一IAB节点发送第一指示信息，包括：
接收来自第一IAB节点的测量报告；基于测量报告，源IAB宿主确定第一指示信息；
向第一IAB节点发送第一指示信息。
在一种可能的实现中，向第一IAB节点发送第一指示信息，包括：
在第一IAB节点的MT部分在发生无线链路失败后执行无线资源控制RRC重建立过程接入目标小区后与目标IAB宿主进行连接的情况下，接收来自目标IAB宿主的用于请求第一IAB节点的上下文的请求消息，基于用于请求第一IAB节点的上下文的请求消息，确定第一指示信息，其中，目标小区是第一IAB节点进行连接更新后接入的小区；
向第一IAB节点发送第一指示信息。
在一种可能的实现中，向第一IAB节点发送第二指示信息，包括：
在第一IAB节点的MT部分仍然连接至源IAB宿主的情况下，向第一IAB节点的MT部分发送通过无线资源控制RRC消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区；或者
向第一IAB节点的DU部分发送通过F1应用协议F1AP消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区。
在一种可能的实现中，上述方法还包括：
向第一IAB节点的DU部分发送F1应用协议F1AP消息，F1应用协议F1AP消息中携带RRC消息容器和第三指示信息，RRC消息容器中封装有第一IAB节点的下属UE和/或下属IAB节点的RRC消息，以使得第一IAB节点在将RRC消息成功发送至第一IAB节点的下属UE和/或下属IAB节点后，确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息；
其中，配置信息为第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息。
在一种可能的实现中，第三指示信息为用于指示第一IAB节点停止对其下属UE和/或下属IAB节点进行数据传输调度的指示信息；或者
第三指示信息用于指示RRC消息容器中携带的RRC消息中，包含第一IAB节点的下属UE和/或下属IAB节点接入目标IAB宿主下的小区需要的RRC配置信息，其中，目标IAB宿主下的小区是第一IAB节点的DU部分在其服务的小区变更为目标IAB宿主下的小区后所服务的小区。
第三方面，本申请实施例提出一种IAB节点连接更新方法，应用于目标IAB宿主，第一IAB节点在连接更新后连接到目标IAB宿主，第一IAB节点包含MT部分和DU部分，可以为一个或多个下属UE和/或下属IAB节点提供接入和回传服务，且第一IAB节点在连接更新前连接到源IAB宿主，该方法包括：
确定第一IAB节点的DU部分需要与目标IAB宿主建立F1连接；
向第一IAB节点发送第一指示信息，第一指示信息用于指示第一IAB节点与目标IAB宿主建立F1连接。
在一种可能的实现中，第一指示信息为目标IAB宿主的IP地址，或者
第一指示信息包括目标IAB宿主的IP地址，以及用于指示第一IAB节点的DU部分发起与目标IAB宿主之间建立F1连接的显式指示信息。
第四方面，本申请实施例提出一种IAB节点连接更新方法，应用于下属节点，下属节点为第一IAB节点的下属UE和/或下属IAB节点，其特征在于，第一IAB节点包含MT部分和DU部分，可以为一个或多个下属UE和/或下属IAB节点提供接入和回传服务，第一IAB节点在连接更新前连接到源IAB宿主，在连接更新后连接到目标 IAB宿主，该方法包括：
接收来自第一IAB节点的DU部分的配置信息；
其中，配置信息为第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息；
生效配置信息。
在一种可能的实现中，配置信息包括第五指示信息，第五指示信息用于指示延迟生效配置信息；
生效配置信息，包括：
接收来自第一IAB节点的DU部分的第四指示信息；
根据第四指示信息，生效配置信息。
在一种可能的实现中，上述方法还包括：
接收来自第一IAB节点的时长信息，时长信息用于指示下属节点生效配置信息的时刻；
生效配置信息，包括：
根据生效配置信息的时刻，生效配置信息。
在一种可能的实现中，生效配置信息，包括：
在下属节点搜索到目标小区的情况下，生效配置信息；
其中，目标小区是第一IAB节点的DU部分在其服务的小区变更为目标IAB宿主下的小区后所服务的小区，由配置信息中的目标小区标识进行标识。
在一种可能的实现中，生效配置信息，包括：
根据配置信息，接入到目标小区，与目标IAB宿主建立连接。
第五方面，本申请实施例提出一种IAB节点连接更新装置，应用于第一IAB节点，第一IAB节点包含MT部分和DU部分，可以为一个或多个下属UE和/或下属IAB节点提供接入和回传服务，第一IAB节点在连接更新前连接到源IAB宿主，在连接更新后连接到目标IAB宿主，该装置包括：
第一收发模块用于接收第一指示信息；
连接模块用于根据第一指示信息，第一IAB节点的DU部分与目标IAB宿主建立F1连接。
一种可能的实现中，上述装置还包括：
变更模块用于将第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区。
一种可能的实现中，第一收发模块，包括：
第一收发子模块用于接收来自源IAB宿主的第一指示信息；或者
第二收发子模块用于接收来自操作管理维护OAM的第一指示信息。
一种可能的实现中，第一指示信息为目标IAB宿主的IP地址；或者，
第一指示信息包括目标IAB宿主的IP地址，以及用于指示第一IAB节点的DU部分发起与目标IAB宿主之间建立F1连接的显式指示信息。
一种可能的实现中，所述第二收发子模块具体用于：
确定目标小区的标识，目标小区是第一IAB节点进行连接更新后接入的小区；
将目标小区的标识发送至操作管理维护OAM，以使得操作管理维护OAM基于目标小区的标识，确定目标IAB宿主；
接收来自操作管理维护OAM的第一指示信息。
一种可能的实现中，第一收发子模块具体用于：
向源IAB宿主发送测量报告；其中，第一指示信息为源IAB宿主基于测量报告确定的；
接收来自源IAB宿主的第一指示信息。
一种可能的实现中，第一收发子模块具体用于：
第一IAB节点的MT部分在发生无线链路失败后执行无线资源控制RRC重建立过程，接入目标小区后与目标IAB宿主进行连接；其中，第一指示信息为源IAB宿主基于用于请求第一IAB节点的上下文的请求消息确定的，用于请求所述第一IAB节点的上下文的请求消息是由目标IAB宿主向源IAB宿主发送的；
接收来自源IAB宿主的第一指示信息。
一种可能的实现中，变更模块，包括：
第三收发子模块用于接收第二指示信息；
变更子模块用于根据第二指示信息，将第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区；或者
第一确定模块用于确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息；
变更子模块用于将第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区；
其中，配置信息为第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息；或者
第三收发子模块用于接收第二指示信息，并确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息；
变更子模块用于将第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区；
其中，配置信息为第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息。
一种可能的实现中，第三收发子模块具体用于：
第一IAB节点的MT部分仍然连接至源IAB宿主，第一IAB节点的MT部分接收来自源IAB宿主通过无线资源控制RRC消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区；或者
第一IAB节点的DU部分接收来自源IAB宿主通过F1应用协议F1AP消息携带 的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区。
一种可能的实现中，第三收发子模块具体用于：
第一IAB节点的MT部分已连接至目标IAB宿主，第一IAB节点的MT部分接收来自目标IAB宿主通过无线资源控制RRC消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区；或者
第一IAB节点的DU部分接收来自目标IAB宿主通过F1应用协议F1AP消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区。
一种可能的实现中，第一确定模块具体用于：
第一IAB节点的DU部分从源IAB宿主接收到F1应用协议F1AP消息，F1应用协议F1AP消息中携带RRC消息容器，RRC消息容器中封装有第一IAB节点的下属UE和/或下属IAB节点的RRC消息；
若F1应用协议F1AP消息中携带有第三指示信息，则在将RRC消息成功发送至第一IAB节点的下属UE和/或下属IAB节点后，确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息；或者
若F1应用协议F1AP消息被携带在第一序号的数据包中，则在将RRC消息成功发送至第一IAB节点的下属UE和/或下属IAB节点后，确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息，其中，第一序号是流控传输协议SCTP层的数据包序号，由源IAB宿主配置给第一IAB节点。
一种可能的实现中，第三指示信息为用于指示第一IAB节点停止对其下属UE和/或下属IAB节点进行数据传输调度的指示信息；或者
所述第三指示信息为用于指示RRC消息容器中携带的RRC消息中，包含第一IAB节点的下属UE和/或下属IAB节点接入目标IAB宿主下的小区需要的RRC配置信息，其中，目标IAB宿主下的小区是第一IAB节点的DU部分在其服务的小区变更为目标IAB宿主下的小区后所服务的小区。
一种可能的实现中，上述装置还包括：
第二确定模块用于根据F1应用协议F1AP消息中携带的第三指示信息或者根据F1应用协议F1AP消息被携带在第一序号的数据包，确定F1应用协议F1AP消息中携带的第一IAB节点的下属UE和/或下属IAB节点的RRC消息包含第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息，则
先缓存第一IAB节点的下属UE和/或下属IAB节点的RRC消息，在接收到第二指示信息后，再向第一IAB节点的下属UE和/或下属IAB节点发送其RRC消息。
一种可能的实现中，上述装置还包括：
广播模块用于第一IAB节点的DU部分广播第四指示信息，第四指示信息用于指 示第一IAB节点的下属UE和/或下属IAB节点生效配置信息；或者
第二收发模块用于向第一IAB节点的下属UE和/或下属IAB节点指示时长信息，时长信息用于指示第一IAB节点的下属UE和/或下属IAB节点生效配置信息的时刻。
需要说明的是，第五方面及其各种可能的实现中的IAB节点连接更新装置的有益效果，可以参见第一方面中相应方法的有益效果，此处不再赘述。
第六方面，本申请实施例提出一种IAB节点连接更新装置，应用于源IAB宿主，第一IAB节点在连接更新前连接到源IAB宿主，第一IAB节点包含MT部分和DU部分，可以为一个或多个下属UE和/或下属IAB节点提供接入和回传服务，且第一IAB节点在连接更新后连接到目标IAB宿主，该装置包括：
第三确定模块用于确定第一IAB节点的DU部分需要执行连接更新与目标IAB宿主建立F1连接；
第三收发模块用于向第一IAB节点发送第一指示信息，第一指示信息用于指示第一IAB节点的DU部分与目标IAB宿主建立F1连接。
在一种可能的实现中，上述装置还包括：
第四收发模块用于向第一IAB节点发送第二指示信息，第二指示信息用于指示第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区。
在一种可能的实现中，上述装置还包括：
第五收发模块用于向目标IAB宿主发送第一请求消息，第一请求消息用于请求目标IAB宿主的IP地址；
第五收发模块还用于接收来自目标IAB宿主的第一响应消息，第一响应消息包括目标IAB宿主的IP地址；
其中，第一指示信息为目标IAB宿主的IP地址；或者，
第一指示信息包括目标IAB宿主的IP地址，以及用于指示第一IAB节点的DU部分发起与目标IAB宿主之间建立F1连接的显式指示信息。
在一种可能的实现中，向第一IAB节点发送第一指示信息，包括：
接收来自第一IAB节点的测量报告；基于测量报告，源IAB宿主确定第一指示信息；
向第一IAB节点发送第一指示信息。
在一种可能的实现中，向第一IAB节点发送第一指示信息，包括：
在第一IAB节点的MT部分在发生无线链路失败后执行无线资源控制RRC重建立过程接入目标小区后与目标IAB宿主进行连接的情况下，接收来自目标IAB宿主的用于请求第一IAB节点的上下文的请求消息，基于用于请求第一IAB节点的上下文的请求消息，确定第一指示信息，其中，目标小区是第一IAB节点进行连接更新后接入的小区；
向第一IAB节点发送第一指示信息。
在一种可能的实现中，第四收发模块具体用于：
在第一IAB节点的MT部分仍然连接至源IAB宿主的情况下，向第一IAB节点的 MT部分发送通过无线资源控制RRC消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区；或者
向第一IAB节点的DU部分发送通过F1应用协议F1AP消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区。
在一种可能的实现中，上述装置还包括：
第六收发模块用于向第一IAB节点的DU部分发送F1应用协议F1AP消息，F1应用协议F1AP消息中携带RRC消息容器和第三指示信息，RRC消息容器中封装有第一IAB节点的下属UE和/或下属IAB节点的RRC消息，以使得第一IAB节点在将RRC消息成功发送至第一IAB节点的下属UE和/或下属IAB节点后，确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息；
其中，配置信息为第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息。
在一种可能的实现中，第三指示信息为用于指示第一IAB节点停止对其下属UE和/或下属IAB节点进行数据传输调度的指示信息；或者
第三指示信息用于指示RRC消息容器中携带的RRC消息中，包含第一IAB节点的下属UE和/或下属IAB节点接入目标IAB宿主下的小区需要的RRC配置信息，其中，目标IAB宿主下的小区是第一IAB节点的DU部分在其服务的小区变更为目标IAB宿主下的小区后所服务的小区。
需要说明的是，第六方面及其各种可能的实现中的IAB节点连接更新装置的有益效果，可以参见第二方面中相应方法的有益效果，此处不再赘述。
第七方面，本申请实施例提出一种IAB节点连接更新装置，应用于目标IAB宿主，第一IAB节点在连接更新后连接到目标IAB宿主，第一IAB节点包含MT部分和DU部分，可以为一个或多个下属UE和/或下属IAB节点提供接入和回传服务，且第一IAB节点在连接更新前连接到源IAB宿主，该装置包括：
第四确定模块用于确定第一IAB节点的DU部分需要与目标IAB宿主建立F1连接；
第七收发模块用于向第一IAB节点发送第一指示信息，第一指示信息用于指示第一IAB节点与目标IAB宿主建立F1连接。
在一种可能的实现中，第一指示信息为目标IAB宿主的IP地址，或者
第一指示信息包括目标IAB宿主的IP地址，以及用于指示第一IAB节点的DU部分发起与目标IAB宿主之间建立F1连接的显式指示信息。
需要说明的是，第七方面及其各种可能的实现中的IAB节点连接更新装置的有益效果，可以参见第三方面中相应方法的有益效果，此处不再赘述。
第八方面，本申请实施例提出一种IAB节点连接更新装置，应用于下属节点，下 属节点为第一IAB节点的下属UE和/或下属IAB节点，第一IAB节点包含MT部分和DU部分，可以为一个或多个下属UE和/或下属IAB节点提供接入和回传服务，第一IAB节点在连接更新前连接到源IAB宿主，在连接更新后连接到目标IAB宿主，该装置包括：
第八收发模块用于接收来自第一IAB节点的DU部分的配置信息；
其中，配置信息为第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息；
生效模块用于生效配置信息。
在一种可能的实现中，配置信息包括第五指示信息，第五指示信息用于指示延迟生效配置信息；
生效模块具体用于：
接收来自第一IAB节点的DU部分的第四指示信息；
根据第四指示信息，生效配置信息。
在一种可能的实现中，上述装置还包括：
第九收发模块用于接收来自第一IAB节点的时长信息，时长信息用于指示第一IAB节点的下属UE和/或下属IAB节点生效配置信息的时刻；
生效模块具体用于：
根据生效配置信息的时刻，生效配置信息。
在一种可能的实现中，生效模块具体用于：
在下属节点搜索到目标小区的情况下，生效配置信息；
其中，目标小区是第一IAB节点的DU部分在其服务的小区变更为目标IAB宿主下的小区后所服务的小区，由配置信息中的目标小区标识进行标识。
在一种可能的实现中，生效模块具体用于：
根据配置信息，接入到目标小区，与目标IAB宿主建立连接。
需要说明的是，第八方面及其各种可能的实现中的IAB节点连接更新装置的有益效果，可以参见第四方面中相应方法的有益效果，此处不再赘述。
第九方面，本申请实施例提出一种IAB节点连接更新装置，包括至少一个处理器，所述处理器用于执行存储器中存储的程序，当所述程序被执行时，使得所述IAB节点连接更新装置执行：
如第一方面及其各种可能的实现中的方法；或
如第二方面及其各种可能的实现中的方法；或
如第三方面及其各种可能的实现中的方法；或
如第四方面及其各种可能的实现中的方法。
第十方面，本申请实施例提出一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得如第一方面及其各种可能的实现中的方法被该计算机执行；或者如第二方面及其各种可能的实现中的方法被该计算机执行；或者如第三方面 及其各种可能的实现中的方法被该计算机执行；或者如第四方面及其各种可能的实现中的方法被该计算机执行。
第十一方面，本申请实施例提出一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时，如第一方面及其各种可能的实现中的方法被执行；或者如第二方面及其各种可能的实现中的方法被执行；或者如第三方面及其各种可能的实现中的方法被执行；或者如第四方面及其各种可能的实现中的方法被执行。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对实施例所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些图获得其他的附图。
图1为一种可能的实现方式中的IAB独立组网的示意图；
图2为一种可能的实现方式中的IAB非独立组网的示意图；
图3为本申请实施例提供的IAB网络用户面示意图；
图4为本申请实施例提供的IAB网络控制面示意图；
图5为本申请实施例提供的IAB节点执行跨宿主拓扑更新切换的场景的示意图；
图6为本申请实施例提供的IAB节点通过无线回传链路连接到IAB donor的架构图；
图7为本申请实施例提供的IAB宿主间的拓扑更新示意图；
图8(a)-图8(c)为本申请实施例提供的一种IAB节点连接更新方法的流程示意图；
图9为本申请实施例提供的IAB节点建立双链接的示意图；
图10为一种可能的实现方式中的短BSR格式或截断的短BSR格式的示意图；
图11为一种可能的实现方式中的长BSR格式或截断的长BSR格式的示意图；
图12为本申请实施例提供的新的短BSR格式或新的截断的短BSR格式的示意图；
图13为本申请实施例提供的新的长BSR格式或新的截断的长BSR格式的示意图；
图14为本申请实施例提供的一种IAB节点连接更新装置的结构示意图；
图15为本申请实施例提供的一种IAB节点连接更新装置的又一结构示意图；
图16为本申请实施例提供的一种IAB节点连接更新装置的另一结构示意图；
图17为本申请实施例提供的一种IAB节点连接更新装置的另一结构示意图。
具体实施方式
为了使本申请实施例的目的、技术方案和优点更加清楚，下面结合附图对本申请实施例具体实施方式做详细描述。
需要说明的是，本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B， 单独存在B这三种情况。本申请实施例的说明书和权利要求书中的术语“第一”、“第二”和“第三”等是用于区别不同的对象，而不是用于描述对象的特定顺序。例如，第一收发模块、第二收发模块和第三收发模块等是用于区别不同的收发模块，而不是用于描述目标对象的特定顺序。在本申请实施例中，“示例性的”、“举例来说”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”、“举例来说”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。在本申请实施例的描述中，除非另有说明，“多个”的含义是指两个或两个以上。
在接入回传一体化(Integrated access and backhaul，IAB)网络中，IAB节点(IAB node)，也称为中继节点(Relay Node，RN)，可以为用户设备(User Equipment，UE)提供无线接入服务。所述UE的业务数据由IAB节点通过无线回传链路连接到IAB宿主(IAB donor)传输。本申请中IAB宿主也可称为宿主节点(donor node)或宿主基站(Donor gNodeB，DgNB)。IAB节点可以由移动终端(mobile termination，MT)(或称为IAB节点的MT，或IAB-MT)部分和分布式单元(distributed unit，DU)(或称为IAB节点的DU，或IAB-DU)部分组成。其中，当IAB节点面向其父节点时，可以作为终端设备，即MT的角色；当IAB节点面向其子节点(子节点可能是另一IAB节点，或者普通UE)时，其被视为网络设备，即作为DU的角色。其中IAB节点的MT部分，具有UE的部分或全部功能。IAB宿主可以是一个具有完整基站功能的接入网网元，还可以是集中式单元(centralized unit，CU)和分布式单元(distributed unit，DU)分离形态的接入网网元。IAB宿主连接到为UE服务的核心网(例如连接到5G核心网，5GC)网元，并为IAB节点提供无线回传功能。为便于表述，将IAB宿主的集中式单元简称为donor CU(或称为IAB宿主的CU，或IAB-donor-CU，或IAB donor CU,或直接称为CU)，IAB宿主的分布式单元简称为donor DU(或称为IAB宿主的DU，或IAB-donor-DU，或IAB donor DU,或直接称为DU)，其中IAB宿主的CU还有可能是控制面(control plane，CP)和用户面(user plane，UP)分离的形态，例如IAB宿主的CU可由一个CU-CP(或称为IAB donor CU-CP,或IAB-donor-CU-CP)和一个(或多个)CU-UP(或称为IAB donor CU-UP，或IAB-donor-CU-UP)组成。
在5G当前的标准中，考虑到高频载波的覆盖范围小，为了保障网络的覆盖性能，在IAB网络中可能采用多跳组网。此外，考虑到业务传输可靠性的需求，可以使IAB节点支持双连接(Dual connectivity，DC)或者多连接(multi-connectivity)，以应对回传链路可能发生的异常情况，例如链路的中断或阻塞(blockage)及负载波动等异常，提高传输的可靠性保障。因此，IAB网络支持多跳组网，还可以支持多连接组网。在由IAB节点服务的UE和IAB宿主之间，存在至少一条由多段链路组成的传输路径。在一条传输路径上，包含多个节点，如UE，一个或多个IAB节点，IAB宿主(若IAB宿主为CU和DU分离的形态，则还包含IAB-donor-DU部分，和IAB-donor-CU部分)。每个IAB节点将为其提供接入和回传服务的相邻节点视为父节点，相应地，每个IAB节点可视为其父节点的子节点。
例如，如图1所示，IAB node 1的父节点为IAB donor，IAB node 1又为IAB node  2和IAB node 3的父节点，IAB node 2和IAB node 3均为IAB node4的父节点，IAB node 5的父节点为IAB node 2。UE的上行数据包可以经一个或多个IAB节点传输至IAB donor后，再由IAB donor发送至移动网关设备(例如5G核心网中的用户平面功能单元UPF)，下行数据包将由IAB donor从移动网关设备处接收后，再通过IAB节点发送至UE。图1示出的为IAB独立(standalone，SA)组网场景，IAB节点和UE均仅通过NR制式的空口与网络建立连接。
图1所示的IAB独立组网场景仅仅是示例性的。如图1所示，标号为1的路径代表接入链路，标号为2的路径代表回传链路。在多跳和多连接结合的IAB场景中，还有更多其他的可能性，例如图1中的IAB donor和另一IAB donor下的IAB node组成双连接为UE服务(即UE支持双连接，其中一个连接1直接接入donor DU服务的小区，另一个连接2是与IAB node X建立连接，该IAB node X所连接到的IAB donor不同于UE连接1所对应的IAB donor)等，在本申请中不一一列举。
如图2所示，IAB网络还支持非独立(non-standalone,NSA)组网。参见图2，IAB节点支持4G和5G网络双连接，即EN-DC(E-UTRAN NR Dual Connectivity)，其中LTE的基站eNB为主基站(Master eNB，MeNB)，为IAB节点提供LTE的空口(LTE Uu)连接，并与4G核心网演进型分组核心网(evolved packet core，EPC)建立S1接口进行用户面和控制面传输。IAB donor gNB为辅基站，为IAB节点提供NR的空口(NR Uu)连接，并与核心网EPC建立S1接口进行用户面传输。类似的，UE也支持EN-DC，UE通过LTE Uu接口连接到主基站eNB，通过NR Uu接口连接到辅基站IAB node，UE的辅基站也可以是IAB donor gNB。
需要说明的是，图2仅为非独立组网的示例。IAB网络的NSA场景也同样支持多跳IAB组网，例如图2中的UE可以为另一个IAB节点，即IAB节点可以通过多跳无线回传链路连接到IAB donor gNB。本申请中的IAB非独立组网场景，也可以被称之为IAB的EN-DC组网场景。
在一种可能的实现中，确定在上述IAB网络的无线回传链路引入一个新的协议层—回传适配协议(Backhaul Adaptation Protocol，BAP)层，该协议层位于无线链路控制(Radio Link Control，RLC)层之上，可用于实现数据包在无线回传链路的路由，以及承载映射等功能。
在IAB节点(IAB节点的DU部分)和IAB宿主(或者donor CU)之间，需要建立F1接口(或者被称为F1 *接口，在本申请中，可统一称为F1接口，但对名称并不做限定)，该F1接口支持用户面协议(F1-U/F1 *-U)和控制面协议(F1-C/F1 *-C)。其中，用户面协议包括以下协议层的一个或多个：通用分组无线服务(General Packet Radio Service，GPRS)隧道协议用户面(GPRS tunnelling protocol user plane，GTP-U)，用户数据报协议(user datagram protocol，UDP)、因特网协议(internet protocol，IP)等协议层，可参见图3；该F1接口的控制面协议包括以下中的一个或者多个：F1应用协议(F1 application protocol，F1AP)、流控传输协议(stream control transport protocol，SCTP)、IP等协议层，可参见图4。
通过F1/F1 *接口的控制面，IAB节点和IAB donor之间可以进行执行接口管理、对IAB-DU进行管理，以及执行UE上下文相关的配置等。通过F1/F1 *接口的用户面， IAB节点和IAB donor之间可以执行用户面数据的传输，以及下行传输状态反馈等功能。
在一种可能的实现中，每个IAB节点和其父节点连接到同一个IAB donor上，每个IAB-MT和IAB-DU，可以被视为是受同一个IAB donor管理的。因此，一个IAB donor下的IAB节点组成的IAB网络中的拓扑管理和路由配置，服务质量(Quality of Service,QoS)管理等，都是受一个IAB donor(具体可以是IAB-donor-CU，或者IAB-donor-CU-CP)控制的。例如，图1所示的独立组网场景，每个IAB节点在入网的过程中，IAB donor(具体可以是IAB-donor-CU，或者IAB-donor-CU-CP)会知道IAB节点是通过哪一个父节点连接入网的，若IAB donor是CU和DU分离的形态，还可以知道该IAB节点所连接的IAB-donor-DU是哪一个(就是父节点所连接到的IAB-donor-DU)，后续，IAB节点如果发生了拓扑更新(例如添加了新的父节点，或者改变了父节点)都是在IAB donor(具体可以是IAB-donor-CU，或者IAB-donor-CU-CP)的控制下完成的。也就是说，IAB donor是可以获知其下的所有IAB节点和IAB-donor-DU组成的网络拓扑状态的。因此，IAB节点的标识管理和路由配置是由IAB-donor-CU来进行集中式管理的。上述标识管理包含了对IAB节点/IAB-donor-DU的BAP address的分配和对每条路由路径配置的BAP path ID的分配。从某个IAB节点A到某个IAB节点B的一条特定的传输路径，可以用一个BAP routing ID来唯一标识，每个BAP routing ID中，包含目标IAB节点的BAP address部分，以及路径标签BAP path ID部分。
由于上述一种可能的实现中，仅考虑经过IAB节点的数据包在一个IAB donor控制的IAB节点之间的回传链路传输，因此，可以保证数据包中携带的BAP层头中的路由信息BAP routing ID部分能唯一的标识到一个目标IAB节点的一个传输路径，不会发生BAP address和/或整个BAP routing ID冲突的情况。所谓的BAP address冲突的情况，即一个BAP address可能会被某个或某些IAB节点认为标识了两个或两个以上的不同目标IAB节点；BAP routing ID冲突的情况，是指一个BAP routing ID会被某个或某些IAB节点认为标识了两个或两个以上的不同传输路径。此处的某个或某些IAB节点，具体指的是IAB-donor-DU，或IAB node。
上述一种可能的实现中，仅仅考虑了IAB节点都连接到同一个IAB宿主的场景。但当IAB节点可以连接到多个IAB宿主的时候，或者当IAB节点的MT部分和DU部分不属于同一个IAB宿主管理的时候，可能会出现一个IAB节点的业务或者IAB节点下连接的UE的业务需要经由几类不同的节点所传输，这几类不同的节点可能包含IAB donor CU1所管理的IAB节点(即IAB-MT和IAB-DU都受该IAB donor CU1管理)，IAB donor CU1和IAB donor CU2共同管理的IAB节点(IAB-MT和IAB-DU分别连接到两个不同的IAB donor CU)，IAB donor CU2管理的IAB节点(即IAB-MT和IAB-DU都受该IAB donor CU2管理)。需要说明的是，在本申请实施例中只有两个不同的IAB宿主的CU：IAB donor CU1和IAB donor CU2，但是实际情况中，上述业务所经由的节点中，可能还有受其他IAB donor CU(例如IAB donor CU3)控制的IAB节点也包含在路径中，或者受两个其他IAB donor CU共同管理的IAB节点。
在这种跨宿主组网的情况下，不同宿主管理的IAB节点和IAB-donor-DU可能会相 互通过一个或多个回传链路(Backhaul Link)连接，而不同IAB宿主给各自所控制/管理的IAB节点进行BAP层节点标识(BAP address)或路由标识(BAP routing ID)配置的时候，可能会出现不同的IAB宿主为各自不同的IAB节点配置出相同的BAP address，或者为不同的路径配置出相同的BAP routing ID，即出现BAP address或BAP routing ID冲突的问题，会导致某个或某些IAB节点收到了包含某个BAP routing ID的数据包时，无法确定该数据包的目的IAB节点是哪一个，以及该BAP routing ID所指示的路由路径是哪一个，可能会造成无法对该数据包进行正确的路由传输。
针对上述问题，本申请实施例提出一种IAB节点连接更新方法，该方法可以适用于本申请实施例提供的如图5所示的IAB节点执行跨宿主拓扑更新切换的场景。在该场景中，IAB node 3在从源IAB宿主CU1连接更新至目标IAB宿主CU2后，除了其MT部分，即MT3要接入新的父节点之外，其DU部分，例如DU3b也需要与新的IAB宿主，即目标IAB宿主CU2建立连接。需说明的是，在实际部署的时候，一个IAB节点内可以只有一个DU，在拓扑更新过程中，IAB-DU要与目标宿主CU建立F1连接。
需要说明的是，IAB node 3从源IAB宿主CU1连接更新至目标IAB宿主CU2可以为IAB node 3从源IAB宿主CU1切换连接至目标IAB宿主CU2，也可以为针对IAB node 3在无线回传链路发生了无线链路失败(Radio link failure，RLF)之后，执行链路恢复时选择到新的IAB宿主下的一个小区，并成功执行了无线资源控制(Radio Resource Control，RRC)重建立，则该IAB node 3可以与源IAB宿主CU1之间更新两者之间用于承载的F1连接的传输层偶联，以及重新进行IPsec安全协商；或者，该IAB node 3还可以与新IAB宿主CU，即目标IAB宿主CU2之间建立新的传输层偶联，以及协商新的IPsec安全机制，建立F1连接。
本申请实施例可以适用于独立组网(SA)的IAB网络，还可以适用于非独立组网(NSA)的IAB网络。
图6为本申请实施例提供的IAB节点通过无线回传链路连接到IAB donor的架构图。上述一种IAB节点连接更新方法可以适用于如图6所示的架构图。当IAB节点工作在SA模式时，IAB node可以单连接到一个父节点，或者双连接到两个父节点，其中这两个父节点可以由同一个IAB donor控制，或者分别由不同的IAB donor控制。IAB node的DU部分与一个IAB donor之间建立F1接口即可，该IAB donor可以连接到5G核心网(5G core，5GC)，即图6中的标号为1的虚线部分。其中IAB-donor-CU-CP与通过NG控制面接口连接到5GC中的控制面网元(例如接入和移动性管理功能AMF)，其中IAB-donor-CU-UP与通过NG用户面接口连接到5GC中的用户面网元(例如用户面功能UPF)；当IAB节点工作在NSA模式(或者说EN-DC模式)时，IAB-donor-CU-UP可以通过S1用户面接口连接到EPC(例如连接到业务网关(serving gateway，SGW))，MeNB与IAB node的MT之间有LTE Uu空口连接，MeNB与IAB-donor-CU-CP之间有X2-C接口，MeNB通过S1接口连接到EPC(包括S1接口用户面，以及S1接口控制面)。即图6中的标号为2的虚线部分。
在一种可能的实现中，图6中的MeNB也可以换成5G的基站gNB，图6中的标号为2的虚线部分LTE-Uu接口相应的被替换为NR-Uu接口，gNB可以和5GC之间建立用户面和/或控制面的接口，gNB和IAB-donor为IAB节点提供双连接服务，gNB可以作 为IAB节点的主基站的角色，或者辅基站的角色。
图7示出了IAB宿主间的拓扑更新示意图。如图7所示，发生切换的节点为IAB节点2(简称为IAB node 2，或者IAB 2)，即下文中提及的第一IAB节点。该IAB node 2可以为一个或多个UE/子节点提供接入和回传服务。在图7中，示出了接入到IAB node 2的DU部分所服务的小区的一个UE1，以及一个子节点IAB node 3(也称为IAB node 2的下属IAB节点)，IAB node 3下还有两个UE，即UE2和UE3，接入到IAB node 4的DU部分所服务的小区中。可以理解的是，实际网络部署的场景中，IAB node 2还有可能有一个或者多个孙节点，IAB node 3下还可能服务更多的UE，或子节点，或孙节点，在图7中没有一一示出。
为了便于表述，将这些经由IAB node 2连接到IAB donor的IAB节点或者UE，称之为IAB node 2的下属节点，即下属IAB节点和/或下属UE。本申请中，一个节点的孙节点，可以是经过至少两跳无线链路连接到该节点的下属节点，例如图1所示的示例中，IAB node 5可以视为IAB node 1的孙节点。
IAB node 2从源父节点(即图7中所示的S parent IAB node 1)在执行切换后连接到目标父节点(即图7中所示的T parent IAB node 4)后，其下属的IAB node 3，以及UE1和UE2也可以跟随IAB node 2执行切换。
在IAB节点执行跨IAB宿主切换过程中，由于IAB节点和其下属节点都需要切换连接到新的IAB宿主，因此执行的顺序有很多种可能性，比如从上至下，或者从下至上，或者任意的顺序，因此在整个IAB节点与下属UE和下属IAB节点的迁移过程中，可能会出现一个IAB节点的MT部分和DU部分，分别连接到两个不同的IAB宿主的情况。比如在图7所示的场景中，当IAB2-MT已经完成切换，IAB node 2的MT部分已经连接至目标IAB宿主CU2，即下文中提及的IAB宿主，但是IAB2-DU部分还连接在源IAB donor CU1，即下文中提及的源IAB宿主，IAB node 2的下属节点(IAB node 3)以及UE(UE1，UE2，UE3)也仍然连接到IAB donor CU1。这种情况下，IAB node 3要与IAB node CU1通信，相关数据包，需要经过实线1所示的路径传输，即经由IAB node 2(属于由两个IAB donor共同管理的节点)，以及IAB node 4和IAB donor DU2(这两个都属于由IAB donor CU2管理的节点)，此外，还将经由IAB donor DU2和IAB donor CU1之间的IP传输网络被传输。
本申请中，IAB节点执行跨IAB宿主的连接更新，也可以理解为IAB节点在两个不同的IAB宿主之间执行连接更新，即IAB节点在连接更新前连接到的IAB宿主不同于其在连接更新后连接到的目标IAB宿主。此处的连接更新，可以是基于IAB节点的切换的连接更新，或者基于IAB节点的MT部分执行链路恢复(如RRC重建立)的连接更新。
除了IAB node 2发生切换的场景，图7所示的拓扑更新，还可以适用于IAB node 2在发生了回传链路失败的情况下，执行链路恢复时接入到IAB node 4(具体可以是IAB node 4的DU部分)所服务的小区，然后IAB node 2的MT部分可以与IAB donor CU2之间执行RRC重建立过程。
实施例1：
图8(a)示出了本申请实施例提出的一种IAB节点连接更新方法的流程示意图， 该流程示意图包括S802-S806。
下面对本申请实施例提供的如图8所示的一种IAB节点连接更新方法进行详细介绍。在本申请实施例中，该IAB节点连接更新方法可以应用于第一IAB节点、源IAB宿主、目标IAB宿主以及下属节点，即第一IAB节点的下属UE和/或下属IAB节点。第一IAB节点包含MT部分和DU部分，可以为一个或多个下属UE和/或下属IAB节点提供接入和回传服务，第一IAB节点在连接更新前连接到源IAB宿主，在连接更新后连接到目标IAB宿主。
在一种可能的实现中，通过以下步骤实现本申请实施例提供的如图8(a)所示的IAB节点连接更新方法：
S802，源IAB宿主确定第一IAB节点的DU部分需要执行连接更新与目标IAB宿主建立F1连接。
在本申请实施例中，在一种可能的实现中，第一IAB节点向源IAB宿主发送测量报告。源IAB宿主接收测量报告。源IAB宿主根据测量报告中信号质量与预设信号质量阈值的关系，确定第一IAB节点是否进行跨IAB宿主的切换。例如，当测量报告中第一IAB节点接入的源IAB宿主下的小区A的信号质量小于预设信号质量阈值TH1，而第一IAB节点测量的目标宿主下的小区B的信号质量大于预设信号质量阈值TH2时，源IAB宿主确定第一IAB节点需要执行跨IAB宿主的切换，且第一IAB节点的DU部分需要执行连接更新与新的IAB宿主，即目标IAB宿主建立F1连接。
在本申请实施例中，在另一种可能的实现中，在第一IAB节点的MT部分在发生无线链路失败后执行无线资源控制RRC重建立过程接入目标小区后与目标IAB宿主进行连接的情况下，目标IAB宿主向源IAB宿主发送用于请求第一IAB节点的上下文的请求消息。源IAB宿主根据上述请求消息确定第一IAB节点的DU部分需要执行连接更新与新的IAB宿主建立F1连接，即目标IAB宿主建立F1连接。
需要说明的是，本申请实施例中，第一IAB节点的DU部分执行连接更新与目标IAB宿主建立F1连接的过程，包括两者之间F1接口的建立，还可以包括：两者之间的流控传输协议(Stream control transport protocol，SCTP)偶联(或者称为传输网络层Transport Network Layer偶联)的建立过程，和/或两者之间进行安全协商(例如基于IPSec协议的安全安全机制和参数协商过程)。
还需要说明的是，第一IAB节点的DU部分，可以在第一IAB节点的MT部分执行跨IAB宿主切换之前，即与目标IAB宿主(具体可以是目标IAB宿主CU或CU-CP)之间建立F1连接。以图7中IAB2为第一IAB节点为例，IAB2的DU部分(即IAB2-DU)可以在IAB2的MT部分(即IAB2-MT)执行切换之前，与目标IAB宿主的CU(即图7中的目标IAB donor CU2)之间执行建立F1连接的过程，这种情况下，IAB2-DU需要经由源父节点IAB node 1，以及源IAB donor DU1，与目标IAB donor CU2之间建立F1连接，即图7中虚线2所指示的传输路径。IAB2-DU还可以在IAB2-MT执行切换之后，与目标IAB donor CU2之间建立F1连接，这种情况下，IAB2-DU可以经过目标父节点IAB node 4，以及目标IAB donor DU2所组成的传输路径与目标IAB donor CU2之间建立F1连接。考虑到IAB node 2可能会同时需要维护与源IAB donor CU1和目标IAB donor CU2之间的两个不同的F1连接，IAB node 2中的DU部分可以 有多个不同的逻辑DU，例如图7中的IAB2-DU和IAB2-DU’，IAB2-DU维护与源IAB donor CU1之间的F1连接，IAB2-DU’维护与目标IAB donor CU2之间的F1连接。但本申请对IAB node中包含的逻辑DU的数量是一个还是多个不予以限定。
需说明的是，本申请实施例中，当源IAB宿主包括IAB宿主的DU和IAB宿主的CU时，源IAB宿主的操作，例如与第一IAB节点或目标IAB宿主之间的通信，具体可以理解为是由源IAB宿主的CU执行的操作。当源IAB宿主包括IAB宿主DU、IAB宿主CU-CP和IAB宿主CU-UP时，源IAB宿主的操作或动作，例如与第一IAB节点/目标IAB宿主的通信，具体可以理解为是源IAB宿主CU-CP在执行的操作或动作。当目标IAB宿主包括IAB宿主的DU和IAB宿主的CU时，目标IAB宿主的操作，例如与第一IAB节点/源IAB宿主之间的通信，具体可以理解为是由目标IAB宿主的CU执行的操作。当目标IAB宿主包括IAB宿主DU、IAB宿主CU-CP和IAB宿主CU-UP时，目标IAB宿主的操作，例如与第一IAB节点/源IAB宿主之间的通信，具体可以理解为是由目标IAB宿主的CU-CP执行的操作。
S804，第一IAB节点接收第一指示信息，第一指示信息用于指示第一IAB节点与目标IAB宿主之间建立F1连接。
上述第一指示信息可以为目标IAB宿主的IP地址，此时目标IAB宿主的IP地址信息作为一种隐式指示信息，即第一IAB节点收到源IAB宿主发送的包含目标IAB宿主的IP地址信息的消息后，就可以触发与目标IAB宿主之间建立F1连接。上述第一指示信息也可以为目标IAB宿主的IP地址信息，以及用于指示第一IAB节点的DU部分发起与目标IAB宿主之间建立F1连接的显式指示信息。上述目标IAB宿主的IP地址信息具体包括以下至少一项：目标IAB宿主的控制面使用的IP地址(具体可以是目标IAB donor CU的IP地址，或目标IAB donor CU-CP的IP地址)，目标IAB宿主的安全网关(Security Gateway)的IP地址和/或目标IAB宿主的用户面使用的IP地址(具体可以是目标IAB donor CU-UP的IP地址)。源IAB宿主将第一指示信息发送至第一IAB节点，第一指示信息用于指示第一IAB节点的DU部分与目标IAB宿主建立F1连接。
在一种可能的实现中，第一IAB节点从源IAB宿主接收第一指示信息，其中，源IAB宿主在步骤S802中确定第一IAB节点的DU部分需要执行连接更新与目标IAB宿主建立F1连接后，进而确定第一指示信息，然后向第一IAB节点发送该第一指示信息。作为一种可能的示例，源IAB宿主向目标IAB宿主发送第一请求消息，第一请求消息用于请求目标IAB宿主的IP地址。源IAB宿主接收来自目标IAB宿主的第一响应消息，第一响应消息包括目标IAB宿主的IP地址信息。
在本申请实施例中，在另一种可能的实现中，第一IAB节点接收来自操作管理维护OAM的第一指示信息。具体地，第一IAB节点向操作管理维护OAM上报第一IAB节点的目标小区的标识。OAM基于该目标小区的标识，确定目标IAB宿主，然后向第一IAB节点提供上述第一指示信息。第一IAB节点基于从OAM收到的目标IAB宿主的IP地址，触发与目标IAB宿主之间的F1连接的建立过程。对于第一IAB节点如何获取其目标小区的标识，一种可能的示例中，当源IAB宿主根据第一IAB节点上报的测量报告确定要为第一IAB节点执行切换的时候，可以先向第一IAB节点提供 目标小区的第一配置信息，其中包含第一IAB节点的目标小区的标识，这种情况下，目标小区是第一IAB节点的MT部分执行切换后需要接入的目标IAB宿主下的小区。或者，另一可能的示例中，在第一IAB节点执行链路恢复的情况下，第一IAB节点的MT部分进行RRC重建立，选择目标小区接入，在读取目标小区的系统信息过程中，获得目标小区的标识，这种情况下，目标小区是第一IAB节点的MT部分在执行RRC重建立过程所选择并接入的目标IAB宿主下的小区。
作为又一种可能的实施方式，第一IAB节点从目标IAB宿主接收第一指示信息。在第一IAB节点执行基于链路恢复的连接更新时，目标IAB宿主(具体可以是目标IAB宿主的CU或CU-CP)在第一IAB节点的MT部分执行RRC重建立成功后，基于从源IAB宿主获取的该第一IAB节点的上下文信息，可以知道执行重建立的第一IAB节点是一个IAB节点(而不是一个普通的UE)，目标IAB宿主进而确定需要与第一IAB节点的DU部分建立F1连接，就可以发第一指示信息给第一IAB节点(具体可以是发送给第一IAB节点的MT部分)。
S806，根据第一指示信息，第一IAB节点的DU部分与目标IAB宿主建立F1连接。
在本申请实施例中，第一IAB节点的DU部分根据来自源IAB宿主或来自操作管理维护OAM或来自目标IAB宿主的第一指示信息，触发与目标IAB宿主建立F1连接。
通过上述方法，在需要将第一IAB节点的DU部分在不同IAB宿主的CU之间进行连接更新(例如第一IAB节点的DU的F1连接在不同IAB宿主的CU之间进行切换或者进行重建立)的情况下，可以及时触发第一IAB节点与目标IAB宿主的CU之间建立F1连接，减小时延。
在一种可能的实现中，本申请实施例提供的IAB节点连接更新方法还包括如图8(b)所示的各个步骤，各个步骤具体如下：
S808，第一IAB节点接收第二指示信息。
第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区。
在本申请实施例中，在一种可能的实现中，第一IAB节点从源IAB宿主接收第二指示信息。作为一种示例，在第一IAB节点的MT部分仍然连接至源IAB宿主的情况下，源IAB宿主(具体可以是源IAB宿主的CU)向第一IAB节点的MT部分发送通过无线资源控制RRC消息携带的第二指示信息。可选的，第一IAB节点的MT部分在收到来自源IAB宿主的第二指示信息后，可以通过内部接口向第一IAB节点的DU部分指示可以进行服务的小区切换，或者直接通过内部接口向第一IAB节点的DU部分转发该第二指示信息。或者作为又一种示例，源IAB宿主的CU在确定要向第一IAB节点发送第二指示信息时，若与第一IAB节点的DU部分之间维持有F1连接，可以直接向第一IAB节点的DU部分发送通过F1应用协议F1AP消息携带的第二指示信息，相应的，第一IAB节点的DU部分接收来自源IAB宿主CU通过F1应用协议F1AP消息携带的第二指示信息。
在本申请实施例中，在另一种可能的实现中，第一IAB节点的MT部分已连接至目标IAB宿主，第一IAB节点可以从目标IAB宿主接收第二指示信息。作为一种示 例，可以由源IAB宿主的CU将第七指示信息先发送给目标IAB宿主的CU，使得目标IAB宿主的CU可以获知可以向第一IAB节点发送切换服务的小区的第二指示信息，再由目标IAB宿主的CU向第一IAB节点的MT部分发送RRC消息，其中携带第二指示信息。可选的，在发送第七指示信息的时候，源IAB宿主的CU还可以携带第一IAB节点的标识，具体可以是例如第一IAB节点在源IAB宿主的CU和目标IAB宿主的CU之间的Xn接口上被分配的标识，例如源IAB宿主的CU为第一IAB节点的MT部分分配的NG-RAN node UE XnAP ID，和/或目标IAB宿主的CU为第一IAB节点的MT部分分配的NG-RAN node UE XnAP ID。另外可选的，第七指示信息和第二指示信息可以是同一个指示信息，或者也可以是不同的指示信息，目标IAB宿主CU从源IAB宿主的CU收到第七指示信息后就通过无线资源控制RRC消息向第一IAB节点的MT部分发送第二指示信息。可选的，第一IAB节点的MT部分接收来自目标IAB宿主通过无线资源控制RRC消息携带的第二指示信息，可以通过内部接口向第一IAB节点的DU部分指示可以进行服务的小区切换，或者直接通过内部接口向第一IAB节点的DU部分转发该第二指示信息。或者，作为又一种示例，目标IAB宿主的CU与第一IAB节点的DU之间有F1连接，可以用于承载F1应用协议F1AP消息，目标IAB宿主在接收到来自源IAB宿主的第七指示信息确定可以向第一IAB节点发送第二指示信息时，向第二IAB节点发送F1AP消息，该F1应用协议F1AP消息中可以包含该第二指示信息，相应地，第一IAB节点的DU部分接收来自目标IAB宿主通过F1应用协议F1AP消息携带的第二指示信息。
作为一种可能的实施方式，源IAB宿主的可以在给第一IAB节点的所有下属节点发送了配置信息后，确定第一IAB节点的DU可以将其所服务的小区切换为目标IAB宿主下的小区，进而确定可以向第一IAB节点发送第二指示信息，然后源IAB宿主可以直接向第二节点发送第二指示信息，或者向目标IAB宿主发送上述第七指示信息，再由目标IAB宿主向第一IAB节点发送第二指示信息。上述配置信息为第一IAB节点的下属节点(下属节点具体可以是下属UE或下属IAB节点)在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息。作为一种示例，本实施方式中，第一IAB节点的下属节点，可以仅包含第一IAB节点的子节点(子节点可以是接入到第一IAB节点的DU所服务的小区中的UE或子IAB节点)。
S810，第一IAB节点将其DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区。
在本申请实施例中，在一种可能的实现中，第一IAB节点接收S808中源IAB宿主或目标IAB宿主发送的第二指示信息。根据第二指示信息，第一IAB节点将其DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区。
在本申请实施例中，在另一种可能的实现中，第一IAB节点确定其下属节点接收到配置信息，第一IAB节点将其DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区。其中，上述配置信息为第一IAB节点的下属节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息。作为一种示例，本实施方式中，第一IAB节点的下属 节点，可以仅包含第一IAB节点的子节点(子节点可以是接入到第一IAB节点的DU所服务的小区中的UE或子IAB节点)，例如，第一IAB节点可以确定其所有子节点均接收到配置信息后，第一IAB节点将其DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区。
在本申请实施例中，在又一种可能的实现中，第一IAB节点接收第二指示信息，并确定其下属节点接收到配置信息，第一IAB节点将其DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区。其中，上述配置信息为第一IAB节点的下属节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息。作为一种可能的示例，本实施方式中，第一IAB节点的下属节点，可以仅包含第一IAB节点的子节点(子节点可以是接入到第一IAB节点的DU所服务的小区中的UE或子IAB节点)，例如，第一IAB节点接收第二指示信息，并在确定其所有子节点(包括接入第一IAB节点的DU部分所服务小区的UE和子IAB节点)均接收到配置信息后，第一IAB节点将其DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区。
需要说明的是，上述确定第一IAB节点的下属节点(以第一下属节点为例)接收到配置信息的具体方法如下：
第一IAB节点的第一下属节点具体是第一IAB节点的子节点，第一IAB节点的DU部分从源IAB宿主接收到F1应用协议F1AP消息，该F1AP消息中携带RRC消息容器，RRC消息容器中封装有第一IAB节点的第一下属节点的RRC消息；第一IAB节点确定该RRC消息中包含有下属节点的配置信息，并将该RRC消息成功发送至第一下属节点后，确定该第一下属节点的接收到配置信息。其中，配置信息为第一下属节点在第一IAB节点的DU部分所服务的小区变更为述目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息，目标IAB宿主下的小区是第一IAB节点的DU部分在其服务的小区变更为目标IAB宿主下的小区后所服务的小区。
需要说明的是，上述第一IAB节点的DU部分从源IAB宿主接收到F1应用协议F1AP消息后，需要进一步确定F1应用协议F1AP消息携带的RRC消息容器中封装的RRC消息携带有下属节点的配置信息，该配置信息具体可以为下属节点的切换命令，所述切换命令可以理解为RRC消息中的ReconfigurationwithSync IE。基于该切换命令中提供的配置内容，第一IAB节点的下属节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区。可选的，本申请实施例中，第一IAB节点确定F1应用协议F1AP消息携带的RRC消息容器中封装的RRC消息携带有下属节点的配置信息的方法如下：
第一种方法：源IAB宿主的CU在发送RRC消息给第一IAB节点的DU时，其中，该RRC消息携带有第一IAB节点的下属节点的配置信息，将该RRC消息封装在F1AP消息中，同时可以在该F1AP消息中，携带停止对该第一IAB节点的下属节点进行数据传输的指示信息(例如在F1AP消息中携带Transmission Action Indicator IE，且该IE的取值为stop)，则第一IAB节点若收到一个包含其下属节点的RRC消息的F1AP消息，且该F1AP消息中有该停止对该第一IAB节点的下属节点进行数据传输调度的指示信息，则该第一IAB节点可以判断该F1AP消息中所携带的RRC消息中包含该下 属节点的配置信息。相当于利用携带停止对第一IAB节点的下属节点进行数据传输的指示信息，隐式指示F1AP消息中携带的RRC消息包含下属节点所需配置信息。基于该配置信息，该下属节点可以接入由第一IAB节点的DU所服务的目标IAB宿主下的小区。
第二种方法：源IAB宿主的CU在向第一IAB节点发送RRC消息时，其中，该RRC消息携带有第一IAB节点的下属节点的配置信息，可以在包含该RRC消息的F1AP消息中，直接包含一个显式的指示信息，用于指示该F1AP消息中所包含的RRC消息中包含有第一IAB节点的下属节点的配置信息。
第三种方法：源IAB宿主的CU向第一IAB节点指示一个数据包序号，该数据包序号所对应的数据包中封装的F1AP消息，即包含有下属节点的配置信息，便于第一IAB节点识别出其下属节点的配置信息。例如，该数据包序号可以是SCTP层的序号。可以理解的是，如果是特定的SCTP偶联上传输的特定序号值对应的数据包中携带有配置信息，则源IAB宿主的CU除了向第一IAB节点指示一个数据包序号之外，还可以是指示特定的SCTP偶联标识，和/或特定的SCTP stream ID。所述SCTP偶联标识，可以由IP五元组信息(源IP地址，目的IP地址，源端口号，目的端口号，协议类型)中的任意一个或多项来标识。
第四种方法：第一IAB节点在收到包含其下属节点的RRC消息的F1AP消息后，其DU部分不用管F1AP消息中包含的RRC消息是否携带有下属节点的配置信息，只要在确定源IAB宿主CU开始向其下属节点发送配置信息，则第一IAB节点在收到包含下属节点的RRC消息的F1AP消息后，就认为该F1AP消息中的RRC消息包含了下属节点的配置信息。这种方法中，可选的，源IAB宿主的CU或目标IAB宿主的CU可以给第一IAB节点发送一个通知信息，该通知信息可用于表明源IAB宿主CU开始向第一IAB节点的下属节点发送配置信息，可以用于指示第一IAB节点开始监测统计其下属节点的RRC消息的接收和发送情况。例如，源IAB宿主的CU在确定要发送第一IAB节点的下属节点的配置信息时，可以给第一IAB节点发送该通知信息，或者通过目标IAB宿主向第一IAB节点发送该通知信息。
在一种可能的实现中，本申请实施例提供的IAB节点连接更新方法还包括如图8(c)所示的各个步骤，各个步骤具体如下：
S812，第一IAB节点的下属节点接收来自第一IAB节点的DU部分的配置信息。
在本申请实施例中，第一IAB节点的下属节点为第一IAB节点的下属UE和/或下属IAB节点，具体可以是第一IAB节点的子节点(例如接入第一IAB节点的DU部分所服务小区的UE和/或子IAB节点)。
在本申请实施例中，第一IAB节点的下属节点接收S810中第一IAB节点的DU部分发送的RRC消息。该RRC消息包含配置信息。其中该配置信息，为该下属节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息。
S814，第一IAB节点的下属节点生效配置信息。
其中，本申请实施例中，第一IAB节点的下属节点，具体可以为第一IAB节点的子节点(例如接入第一IAB节点的DU部分所服务小区的UE和/或子IAB节点)。
本申请实施例中，在一种可能的实现中，在第一IAB节点确定其接收到的F1应用协议F1AP消息中携带的第一IAB节点的第一下属节点的RRC消息包含该第一下属节点的配置信息，则先缓存该RRC消息，第一IAB节点在接收到第二指示信息后，再向该第一下属节点发送缓存的RRC消息。如此可以尽量保证其下属节点在相近的时间内收到配置信息，按照配置信息执行连接更新。其中，第一IAB节点确定其接收到的F1应用协议F1AP消息中携带的第一IAB节点的第一下属节点的RRC消息包含第一下属节点的配置信息的方式，可以参考步骤S810中的描述进行理解。其中，所述第一下属节点的配置信息，为该第一下属节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入该目标IAB宿主下的小区需要的RRC配置信息。
本申请实施例中，在另一种可能的实现中，第一IAB节点无需缓存第一IAB节点的下属节点的RRC消息，其中，RRC消息包含第一IAB节点的下属节点的配置信息，但是第一IAB节点的下属节点收到各自的配置信息后，可以先不生效，等第一IAB节点将其所有下属节点的包含配置信息的RRC消息都发送完成后，第一IAB节点的DU部分可以给所有下属节点广播一个第四指示信息，第四指示信息用于指示第一IAB节点的下属UE和/或下属IAB节点生效配置信息。这种方式中，第一IAB节点的下属节点在获取包含其配置信息的RRC消息时，获取第五指示信息，该第五指示信息用于该下属节点指示延迟生效RRC消息中的配置信息。一种可能的示例中，第五指示信息，可以由源IAB宿主携带在其生成的第一IAB节点的下属节点的RRC消息中，或者可以由第一IAB节点携带在封装有该RRC消息的MAC层协议数据单元PDU中(例如携带在MAC CE中)，该RRC消息中包含该下属节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入该目标IAB宿主下的小区需要的RRC配置信息。
本申请实施例中，在又一种可能的实现中，第一IAB节点无需缓存包含下属节点的配置信息的RRC消息，但是第一IAB节点的下属节点收到配置信息后，可以先不生效，而是基于第一IAB节点指示的时长信息，确定生效配置信息的时刻。可以理解的是，上述时长信息可以携带在包含所述第一IAB节点的下属节点配置信息的RRC消息中，也可以携带在封装有该RRC消息的MAC PDU中，或者携带在回传适配协议(Backhaul Adaptation Protocol，BAP)层的控制PDU中发送给下属节点。第一IAB节点的下属UE和/或下属IAB节点可以基于收到该时长信息，在接收到包含上述配置信息的RRC消息后启动定时器，然后在定时器超时后，生效该RRC消息中的配置信息，根据该配置信息接入到目标IAB宿主下的小区(即第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，由第一IAB节点的DU部分所服务的小区)。
在另一种可能的实现中，第一IAB节点的下属节点收到配置信息后，可以先不生效，而是进行小区搜索，在下属节点搜索到目标小区的情况下，生效配置信息。其中，目标小区是第一IAB节点的DU部分在其服务的小区变更为目标IAB宿主下的小区后所服务的小区，由配置信息中的目标小区标识进行标识。
需要说明的是，上述第一IAB节点的下属节点生效配置信息，可以包括第一IAB节点的下属节点根据配置信息，接入到配置信息中指定的目标小区，与述目标IAB宿 主建立连接。
需要说明的是，上述S812和S814可以在S810之前执行。
若第一IAB节点有多个下属节点，这些下属节点先后收到各自的配置信息，若先收到配置信息的第一IAB节点的下属节点(例如下属节点X)立刻按照配置信息中的配置执行连接更新，此时如果第一IAB节点的DU部分还没有将其服务的小区切换为目标IAB宿主下的小区，则下属节点X可能根本无法找到目标小区，这种情况下，也会导致下属节点X进行RRC重建立。为此，本申请实施例中考虑使得同一层级的所有下属节点(即接入到第一IAB节点DU部分服务的小区的所有子节点)尽量同步的生效配置信息，或者在一个较短的时间范围内生效配置信息，以减小业务中断时延，提升用户体验。
实施例2：
在本申请实施例中，在IAB节点的拓扑更新过程，除了考虑IAB节点的迁移或是执行RRC重建立后连接到新的IAB宿主下等场景导致的拓扑更新，还有一种是IAB节点的双链接。一种可能的实现中，IAB节点可以支持一个宿主节点内的双链接(可以视为是IAB节点的NR-DC，主站和辅站都与IAB节点之间基于NR空口技术进行通信)，还可以支持EN-DC场景的双链接。考虑到有些IAB节点可能位于两个不同的gNB的覆盖范围，IAB节点可以基于与两个不同的gNB之间建立双链接组成NR-DC，可以为IAB节点和/或下属节点的业务数据或信令传输提供多条传输路径，提升业务数据或信令传输的灵活性和鲁棒性。
可以理解的是，即使IAB节点连接到两个不同的gNB，IAB节点仍然只会与其中一个建立F1连接(或者F1连接的控制面)，该与IAB节点建立F1连接的基站，即该IAB节点的IAB宿主(IAB donor)。因此，在IAB节点建立跨gNB的双链接的过程中，需要确定IAB节点的宿主节点(IAB donor，或者说宿主基站donor gNB)是哪一个基站。
在一种可能的实现中，IAB节点连接到的两个gNB，但只在其中一个小区组(cell group，CG)对应的链路上建立无线回传链路，在另一个CG上与相应的基站建立NR Uu接口，不建立BH链路。
如图9所述，IAB节点(具体可以是IAB node的MT部分)先按照UE建立双链接的方式，与两个基站(gNB 1和gNB2)建立了基于NR接入技术的双链接(可称为NR-DC)，其中，gNB1为IAB node的主站(MN，master node)，gNB2为IAB node的辅站(SN，secondary node)。需要说明的是，图9中，IAB node是直接接入gNB1的DU和gNB2的DU所服务的小区，实际部署场景中，如果gNB 1和/或gNB2支持IAB donor的功能，则IAB node还可能接入的是连接到gNB 1和/或gNB2的其他IAB节点所服务的小区。
若gNB1和gNB2均具有IAB donor的功能，即可以作为IAB node的宿主基站为该IAB node提供服务，则为了确定出其中一个基站作为IAB node的宿主基站，本申请提供以下三种方式：
方式一，由IAB node的MN决定。
一种可能的实现中，MN具有IAB donor的能力，且决定自己作为IAB node的宿主基站，这样IAB node的MN可以为该IAB node生成第二配置信息，为IAB node的 DU部分的启动(setup)做准备，第二配置信息可用于IAB node的DU部分与MN之间建立SCTP偶联(SCTP association)，进行安全机制协商(例如基于IPsec的安全协商)，建立F1连接等。其中，MN为IAB node的DU部分的启动做准备所需要的第二配置信息，可以包括如下内容中的一项或多项：MN的IP地址(具体可以是将要作为IAB node所连接的MN的CU的IP地址，或者MN的CU-CP的IP地址)，IAB node的IP地址，IAB node在主小区组(Master cell group，MCG)和父节点之间链路上的无线回传RLC信道(backhaul RLC channel，BH RLC CH)的配置信息，IAB node的BAP层标识(BAP address)，IAB node与MCG上的父节点之间的缺省BH RLC CH(default BH RLC CH)的标识，IAB node的上行的缺省的BAP路由标识(default BAP routing ID)，IAB node的MCG上的父节点的BAP层标识(BAP address)。第二配置信息可以由MN携带在其生成的RRC消息中发送给IAB node。
在另一种可能的实现中，MN选择SN作为IAB node的宿主基站，这种情况下，需要SN为该IAB node生成第三配置信息，为IAB node的DU部分的启动(setup)做准备，第三配置信息可用于IAB node的DU部分与SN之间建立SCTP偶联(SCTP association)，进行安全机制协商(例如基于IPsec的安全协商)，建立F1连接等。第三配置信息可以包括如下内容中的一项或多项：SN的IP地址(具体可以是将要作为IAB node所连接的SN的CU的IP地址，或者SN的CU-CP的IP地址)，IAB node的IP地址，IAB node在与SCG(主小区组，Master cell group)上的父节点之间链路上的BH RLC CH的配置信息，IAB node的BAP层标识，IAB node与SCG上的父节点之间链路上的缺省BH RLC CH的标识，IAB node的上行的缺省的BAP路由标识(default BAP routing ID)，IAB node的SCG上的父节点的BAP层标识。这种情况下，为了使得SN获知自己需要作为IAB node的宿主基站(donor gNB)，以便于为IAB node生成上述第三配置信息，MN需要在确定将SN作为IAB node的宿主基站后，通知SN需要SN作为IAB node的宿主基站。第三配置信息可以由SN携带在其生成的RRC消息中发送给IAB node，或者SN将第三配置信息通过Xn接口的RRC消息容器封装后发送给MN，再由MN发送给IAB node。具体的，MN(例如图9中的gNB1)可以向SN(例如图9中的gNB2)发送第二请求消息(例如辅站添加请求(S-Node addition Request)消息，或者其他的消息，具体对消息的名称不予限定)，其中携带第九指示信息，该第九指示信息用于表明MN希望SN作为IAB node的宿主节点。相应的，如果SN能够作为IAB node的辅站且作为IAB node的宿主基站，则SN可以在返回给MN的确认消息(例如S-Node Addition Request Acknowledge)中携带用于通知MN，SN确认可以作为IAB node宿主基站的信息。例如，SN确认可以作为IAB node宿主基站的信息，可以是一个显式的确认指示，还可以是通过携带第三配置信息来隐式的指示。
为了使得MN和SN相互之间了解对方是否具备作为IAB node的宿主基站的能力，MN和SN可以通过Xn接口的信令交互获知对方是否具备此能力，或者通过OAM的配置获知对方是否具备此能力。
方式二，由IAB node的网管设备(即操作管理维护OAM)决定。
IAB node可以将其所连接的MCG对应的小区的标识(可以仅包含MCG上的主小区标识，或者MCG中的所有的小区的标识)，以及SCG对应的小区的标识(可以仅包含 SCG上的主小区标识，或者SCG中的所有的小区的标识)先上报给OAM。OAM可以基于IAB节点上报的MCG对应的小区的标识确定MN作为IAB node的宿主基站，还可以基于IAB节点上报的SCG对应的小区的标识确定SN作为IAB node的宿主基站。OAM确定了是MN还是SN作为IAB node的宿主基站后，可以将选定的宿主基站的IP地址(具体可以是该宿主基站的CU的IP地址，或CU-CP的IP地址)配置给IAB node，便于IAB node向该IP地址对应的节点发起F1连接。
为了使得IAB node的宿主基站能获知其为宿主基站的角色，为IAB node生成DU部分启动所需要的第二配置信息(由MN生成)或第三配置信息(由SN生成)，一种可能的方式中，OAM还可以向选定作为IAB node的宿主基站的基站(如图9中的gNB1或gNB2)，发送第十指示信息，用于指示该基站需要作为IAB node的宿主基站。如果IAB node的OAM和选定作为宿主基站的OAM不同，则IAB node的OAM(简称为OAM-IAB)需要先向被选定作为IAB node的宿主基站的基站所连接的OAM(简称为OAM-donor)发送通知信息(其中可以包含宿主基站的标识，例如IP地址，或者宿主基站的gNB ID，或者宿主基站的CU的标识等)，再由该OAM-donor向被选定为宿主基站发送第十一指示信息，用于指示该基站需要作为IAB node的宿主基站。另一种可能的方式中，OAM在确定了是MN还是SN作为IAB node的宿主基站后，可以直接在向IAB node发送配置信息用于指示被选定为宿主基站的是IAB node的MN还是SN(或者是与MCG对应的基站还是与SCG对应的基站)。IAB node基于从OAM收到的配置信息获知宿主基站是MN还是SN后，可以直接通过RRC消息向被选定为宿主基站的基站上报通知消息，用于通知该基站是作为该IAB node的宿主节点。或者，IAB node也可以通过RRC消息向MN上报被选定作为宿主基站的节点是MN还是SN；若为SN，则MN可以继续采用方式一中的方式，通过Xn接口的请求消息携带指示信息发送给SN，用于通知SN被选择作为IAB node的宿主基站。
方式三，由IAB node自行选择决定。
IAB node(具体可以是IAB node的MT部分)在与MN和SN建立了双链接后，可以预先获取到MN的IP地址(具体可以是MN的CU部分的IP地址，或者MN的CU-CP的IP地址)，以及SN的IP地址(具体可以是SN的CU部分的IP地址，或者SN的CU-CP的IP地址)，具体获取方式可以是例如：IAB node从OAM获取MN的IP地址和SN的IP地址，或者IAB node从MN/SN获取到MN和SN的IP地址，或者IAB node从MN获取到MN的IP地址，从SN获取到SN的IP地址等。IAB node自行选择MN或SN作为其宿主基站，然后可以直接通过RRC消息向被选定为宿主基站的基站上报通知消息，用于通知该基站是作为该IAB node的宿主节点。或者，IAB node也可以通过RRC消息向MN上报被选定作为宿主基站的节点是MN还是SN；若为SN，则MN可以继续采用方式一中的方式，通过Xn接口的请求消息携带指示信息发送给SN，用于通知SN被选择作为IAB node的宿主基站。
考虑到IAB节点的DU部分启动的时候，将采用第二配置信息中的default BAP routing ID用来路由上行的数据包(例如包含IPsec协商过程的上行数据包，包含SCTP偶连建立的四步握手过程中的一些发送给donor CU的SCTP CHUNK的上行数据包，以及包含F1 SETUP REQUEST等上行F1AP消息的数据包等)，这些初始启动过程中的上 行数据包将被映射在default BH RLC CH上向父节点传输，因此IAB node需要获知第二配置信息中的default配置(default BAP routing ID，和/或default BH RLC CH ID)是哪一个链路上(或者称为IAB节点的缺省无线回传链路，default BH link)的配置信息，或者说IAB node需要确认哪一个CG是宿主基站所服务的CG(donor服务的CG即对应于IAB node的default BH链路)，然后IAB节点才会利用该缺省链路执行后续DU的启动所需的步骤。为了解决此问题，本申请实施例中也有以下两种不同的实施方式：
作为一种可能的实施方式，在前述内容对如何确定出IAB node双链接的两个基站中的一个作为IAB node的宿主基站的方式的描述中，如果IAB节点已经知道选定的宿主基站是MN还是SN(例如方式二中OAM通知了IAB node，或者方式三中IAB node自行选择)，则IAB node可以确定由宿主基站所服务的CG对应的链路，即为其缺省(default)的无线回传链路，该IAB node所获得的default BAP routing ID，default BH RLC CH ID等配置信息，均对应于该缺省无线回传链路。例如若MN为IAB node的宿主基站，则IAB node和其MCG所对应的父节点之间的链路为缺省无线回传链路，反之若SN为IAB node的宿主基站，则IAB node和其SCG所对应的父节点之间的链路为缺省无线回传链路。
作为另一种可能的实施方式，IAB节点可以在收到包含其DU部分启动所需要的配置信息(即第二配置信息或第三配置信息，其中包含default BAP routing ID，default BH RLC CH ID)的时候，先确定该收到的配置信息是SN生成的(即配置信息为第三配置信息)还是MN生成的(即配置信息为第二配置信息)。若确定出是SN生成的，则IAB node认为其与SCG对应的父节点之间的链路为default BH link；若确定出为MN生成的，则IAB node认为其与MCG对应的父节点之间的链路为default BH link。其中，IAB节点确定配置信息是SN生成的还是MN生成的，具体可以有以下几种可能的方法：
方法1：如果IAB node的两个CG中，只有一个CG需要建立BH链路，另一个CG是采用NR Uu接口与相应的基站直接通信，则IAB node可以通过其接收的RRC消息中，确定对应于哪一个CG相应的配置信息中，包含有BH RLC CH相关的配置(例如有需要添加或修改的BH RLC CH的相关配置信息)，依此，IAB node确定该CG对应的服务基站为宿主基站，该IAB node与该CG对应的父节点之间的链路即为宿主基站所服务的链路，可视为该IAB节点的default BH链路。
方法2：IAB node可以根据其接收到包含其DU部分启动所需要的配置信息(其中包含default BAP routing ID，default BH RLC CH ID)的方式，判断哪一个基站为宿主基站以及哪一个CG对应的链路为default BH链路。例如，若IAB node从SRB3(Signaling radio bearer，信令无线承载)收到的RRC消息中包含上述IAB node的DU部分启动所需要的配置信息，则IAB node确定SN为其宿主基站，该IAB node与其SCG对应的父节点之间的链路为其default BH链路；或者，若IAB node从SRB1或SRB2收到的RRC消息(即MN生成的RRC消息，具体可以是RRC重配置消息)中包含上述IAB node的DU部分启动所需要的配置信息，且该配置信息是被封装在MN生成的RRC消息中所包含的一个RRC消息容器(RRC container，具体可以是包含在例如 MRDC-SecondaryCellGroupConfig IE)中，则IAB node确定SN为其宿主基站，该IAB node与其SCG对应的父节点之间的链路为其default BH链路；或者，如果前面两种情况都不满足，即若IAB node从SRB1或SRB2收到的RRC消息(即MN生成的RRC消息，具体可以是RRC重配置消息)中包含上述IAB node的DU部分启动所需要的配置信息，且该配置信息是直接被包含在MN生成的RRC消息中而非封装在RRC消息容器中，则IAB node确定MN为其宿主基站，该IAB node与其MCG对应的父节点之间的链路为其default BH链路。
通过本申请实施例所述的方法，在IAB node与多个宿主节点建立双链接的情况下，可以灵活的确定合适的基站作为IAB node的宿主节点，并保障IAB node的DU部分与该选定的宿主节点之间建立F1连接，便于在IAB node的双链接场景下为下属节点提供服务。不仅可以保证IAB节点的正常工作，还能提升业务数据或信令传输的灵活性和鲁棒性。
实施例3：
本申请实施例中，在IAB网络拓扑更新场景，例如IAB node执行宿主内的迁移或者执行跨宿主的迁移，从源父节点迁移到目标父节点。若IAB节点在迁移前后所连接到的IAB donor DU不同，IAB节点需要获取新的IP地址，且将会用到新的IP地址执行TNL(传输网络层Transport network layer)的迁移过程。本申请中，IAB节点执行宿主内的迁移或者执行跨宿主的迁移，适用于IAB node基于IAB donor的配置信息通过切换的方式执行宿主内的迁移或跨宿主的迁移，还适用于IAB node(具体是其MT部分)在执行RRC重建立的过程中，由于重建到目标父节点而实现的宿主内的迁移或跨宿主的迁移的场景。
在宿主内的迁移过程中，IAB node的源父节点和目标父节点分别连接到相同IAB donor下的两个不同的IAB donor DU(可分别记为源IAB donor DU，以及目标IAB donor DU)，IAB node需要获取与目标IAB donor DU相关的IP地址，IAB节点执行TNL的迁移过程，即IAB node基于该IP地址与IAB donor CU之间协商新的IPsce安全保护相关参数，还可以与IAB donor CU之间建立新的传输层偶联(TNL association，或者称为SCTP Association)，然后将IAB node与IAB donor CU之间的F1连接迁移到目标传输路径上(即将即将F1接口的部分或全部用户面业务，和/或，F1接口的部分或全部控制面的业务，经由目标传输路径传输)，该目标传输路径是IAB node通过目标父节点以及目标IAB donor DU与IAB donor CU之间的传输路径。在下文中，为便于表述，在这种宿主内的迁移过程中，由于IAB node所连接到的IAB donor CU不变，也可以将该IAB donor CU称之为源IAB donor CU。
在跨宿主的迁移过程中，IAB节点的源父节点连接至源IAB donor下的源IAB donor DU，而目标父节点连接至目标IAB donor下的目标IAB donor DU，IAB node也需要获取与目标IAB donor DU相关的IP地址。若IAB节点在迁移后仍然与源IAB宿主之间维持F1连接，则IAB节点执行TNL的迁移过程，即IAB node基于该IP地址与源IAB donor CU之间协商新的IPsce安全保护相关参数，还可以与源IAB donor CU之间建立新的传输层偶联(TNL association，或者称为SCTP Association)，然后将IAB node与源IAB donor CU之间的F1连接迁移到目标传输路径上(即将F1接口的部分或全部 用户面业务，和/或，F1接口的部分或全部控制面的业务，经由目标传输路径传输)，该目标传输路径是IAB node通过目标父节点以及目标IAB donor DU与源IAB donor CU之间的传输路径。若IAB节点在迁移后需要与目标IAB宿主之间建立F1连接，则IAB节点执行TNL的迁移过程，即IAB node基于该IP地址与目标IAB donor CU之间协商新的IPsce安全保护相关参数，还可以与目标IAB donor CU之间建立新的传输层偶联(TNL association，或者称为SCTP Association)，然后将IAB node与目标IAB donor CU之间的F1连接迁移到目标传输路径上(即将F1接口的部分或全部用户面业务，和/或，F1接口的部分或全部控制面的业务，经由目标传输路径传输)，该目标传输路径是IAB node通过目标父节点以及目标IAB donor DU与目标IAB donor CU之间的传输路径。
无论IAB节点执行的是上述哪一种场景的迁移过程，若涉及到TNL的迁移过程，则该TNL过程对于该IAB节点的下属IAB节点来说同样需要执行。例如图7中，IAB node 2执行跨宿主的迁移，需要进行TNL的迁移过程，其子节点IAB node 3也需要执行类似的TNL迁移过程。其中，每个节点要执行TNL迁移前，需要通过RRC消息获取到与TNL迁移相关的必要配置信息，包括：在目标路径上将会使用的新的IP地址，还需要获取与目标传输路径对应的上行的缺省路由标识(default BAP routing ID)以及缺省的BH RLC CH(default BH RLC CH，由default BH RLC CH ID所标识)，用于传输IAB node在TNL过程中需要发送给IAB donor CU的上行消息)。这些与TNL迁移相关的必要配置信息是由每个IAB节点的MT部分所连接的源IAB donor CU通过RRC消息发送给每个IAB节点的。可以理解的是，执行迁移的IAB节点下面可能有子节点，孙节点等多级的下属节点，若上至下按序执行TNL迁移，即每个下属节点都在上一级节点的TNL迁移完成后才开始执行自己的TNL迁移(包括获取与TNL相关的必要配置信息，基于该配置信息执行TNL迁移过程)，则整个IAB节点迁移的过程会持续很长时间，这样对UE的业务中断时延影响很大。为了减少IAB节点迁移过程中对UE的业务中断的影响，本申请实施例提出两种解决方法。
假设第一IAB节点和第二IAB节点均为因为IAB网络拓扑更新，需要执行TNL迁移的IAB节点，且第一IAB节点为第二IAB节点的父节点。例如第一IAB节点为图7中的IAB node 2，第二IAB节点为图7中的IAB node 3。
解决方法1：源IAB donor CU预先将包含有第二IAB节点执行TNL迁移相关的配置信息的RRC消息(记为第一RRC消息)发送给第一IAB节点，第一IAB节点先缓存该第二IAB节点的第一RRC消息，并在确定条件1满足后，向第二IAB节点发送该第一RRC消息。
作为该解决方法1的一种实施方式，该方式具体可以包含以下步骤：
步骤1，源IAB donor CU发送包含有第二IAB节点执行TNL迁移相关的配置信息的RRC消息(记为第一RRC消息)给第一IAB节点。其中，IAB donor CU将第一RRC消息封装在第一IAB节点的F1AP消息中，并在该F1AP消息中携带第十二指示信息，用于指示第一IAB节点缓存住其中的第一RRC消息。
步骤2，第一IAB节点获取配置信息，确定条件1生效。
在该配置信息中，包含第一IAB节点在其目标路径上的路由和承载映射相关的配 置，可用于传输第二IAB节点的TNL迁移相关的数据包。其中，第一IAB节点获取的路由配置相关的部分，包含与第二IAB节点在目标路径上的default BAP routing ID相关的路由映射表项目，即包含：第二IAB节点在其目标路径上的default BAP routing ID，以及与该default BAP routing ID对应的第一IAB节点的下一跳节点的标识。其中的承载映射配置相关的部分，包含第二IAB节点在目标路径上的default BH RLC CH相关的条目，即包含：入口链路上的BH RLC CH为第二IAB节点在目标路径上的default BH RLC CH时，对应的第一IAB节点处的出口链路的BH RLC CH的标识。出口链路的BH RLC CH的标识，由第一IAB节点的下一跳节点的标识，和第一IAB节点与该下一跳节点之间的BH RLC CH ID共同确定。
可选的，在该步骤中第一IAB节点获取配置信息中，可以携带第十三指示信息，用于指示第一IAB节点可以将其缓存的第一RRC消息发送给第二IAB节点。
具体的，第一IAB节点可以通过RRC消息或F1AP消息从源IAB donor CU获取该步骤2中的配置信息，或者第一IAB节点可以在执行TNL迁移后，通过F1AP消息从其在TNL迁移后所连接到的IAB donor CU获取该步骤2中的配置信息。
具体的，第一IAB节点可以在获取到步骤2中的配置信息后，确定条件1生效，其可以向第二IAB节点发送第一RRC消息。作为一种可能的示例，第一IAB节点可以根据步骤2中获取的配置信息中的第十三指示信息，确定其可以将其缓存的第一RRC消息发送给第二IAB节点，这种情况下，条件1为第一IAB节点收到第十三指示信息。作为另一种可能的示例，第一IAB节点只要在步骤2中获取的配置信息中包含第一IAB节点在目标路径上的路由和承载映射相关的配置，即认为这些路由和承载映射相关的配置可用于传输第二IAB节点的TNL迁移相关的数据包，进而确定其可以将其缓存的第一RRC消息发送给第二IAB节点，这种情况下，条件1为第一IAB节点收到在其目标路径上的路由和承载映射相关的配置，或者第一IAB节点收到在其目标路径上可用于传输第二IAB节点的TNL迁移相关的数据包的路由和承载映射相关的配置。
步骤3，第一IAB节点向第二IAB节点发送第一RRC消息。
步骤4，第二IAB节点基于第一RRC消息执行TNL迁移过程。
解决方法2：源IAB donor CU预先将包含有第二IAB节点执行TNL迁移相关的配置信息的RRC消息(记为第一RRC消息)发送给第二IAB节点，该第一RRC消息中包含第十四指示信息，用于指示第二IAB节点在条件2满足后才生效该第一RRC消息，第二IAB节点在生效第一RRC消息后，执行TNL迁移过程。
作为该解决方法2的一种实施方式，该方式具体可以包含以下步骤：
步骤1，源IAB donor CU发送包含有第二IAB节点执行TNL迁移相关的配置信息的RRC消息(记为第一RRC消息)给第二IAB节点。其中，IAB donor CU将第一RRC消息封装在第一IAB节点的F1AP消息中，第一IAB节点收到该F1AP消息后向第二IAB节点发送其中包含的第一RRC消息。
可选的，在第一RRC消息中，包含第十四指示信息，用于指示第二IAB节点先不生效该第一RRC消息，或者指示第二IAB节点在条件2满足后才生效该第一RRC消息。
步骤2，第一IAB节点获取配置信息，确定条件1生效。
在该配置信息中，包含第一IAB节点在其目标路径上的路由和承载映射相关的配 置，可用于传输第二IAB节点的TNL迁移相关的数据包。其中，第一IAB节点获取的路由配置相关的部分，包含与第二IAB节点在目标路径上的default BAP routing ID相关的路由映射表项目，即包含：第二IAB节点在其目标路径上的default BAP routing ID，以及与该default BAP routing ID对应的第一IAB节点的下一跳节点的标识。其中的承载映射配置相关的部分，包含第二IAB节点在目标路径上的default BH RLC CH相关的条目，即包含：入口链路上的BH RLC CH为第二IAB节点在目标路径上的default BH RLC CH时，对应的第一IAB节点处的出口链路的BH RLC CH的标识。出口链路的BH RLC CH的标识，由第一IAB节点的下一跳节点的标识，和第一IAB节点与该下一跳节点之间的BH RLC CH ID共同确定。
可选的，在该步骤中第一IAB节点获取配置信息中，可以携带第十三指示信息，用于指示第一IAB节点可以将其缓存的第一RRC消息发送给第二IAB节点。
具体的，第一IAB节点可以通过RRC消息或F1AP消息从源IAB donor CU获取该步骤2中的配置信息，或者第一IAB节点可以在执行TNL迁移后，通过F1AP消息从其在TNL迁移后所连接到的IAB donor CU获取该步骤2中的配置信息。
具体的，第一IAB节点可以在获取到步骤2中的配置信息后，确定条件1生效，其可以向第二IAB节点发送第一RRC消息。作为一种可能的示例，第一IAB节点可以根据步骤2中获取的配置信息中的第十三指示信息，确定其可以将其缓存的第一RRC消息发送给第二IAB节点，这种情况下，条件1为第一IAB节点收到第十三指示信息。作为另一种可能的示例，第一IAB节点只要在步骤2中获取的配置信息中包含第一IAB节点在目标路径上的路由和承载映射相关的配置，即认为这些路由和承载映射相关的配置可用于传输第二IAB节点的TNL迁移相关的数据包，进而确定其可以将其缓存的第一RRC消息发送给第二IAB节点，这种情况下，条件1为第一IAB节点收到在其目标路径上的路由和承载映射相关的配置，或者第一IAB节点收到在其目标路径上可用于传输第二IAB节点的TNL迁移相关的数据包的路由和承载映射相关的配置。
步骤3，第一IAB节点向第二IAB节点发送第十五指示信息，基于该第十五指示信息，第二IAB节点确定条件2生效。
具体地，第一IAB节点在确定条件1生效后，向第二IAB节点发送第十五指示信息。所述第十五指示信息，可以携带在BAP层的控制PDU(BAP control PDU)中向第二IAB节点发送，或者携带在MAC层的控制元素(MAC control element，MAC CE)中向第二IAB节点发送，或者通过物理层的下行控制信息(Downlink Control Information，DCI)携带后向第二IAB节点发送。
步骤4，第二IAB节点基于第一RRC消息执行TNL迁移过程。
通过该实施例的两种解决方式，在IAB节点的拓扑更新过程中，IAB节点和下属节点可以以一种非常紧凑的方式执行TNL的迁移过程，避免下属节点由于对上游节点的连接建立情况和配置获取情况不知情，提前做无谓的TNL迁移尝试导致迁移失败，还需要再重新尝试，进而导致整个拓扑更新过程的执行时间被拉长，也可以避免下属节点执行TNL迁移过晚导致的整个拓扑更新过程的执行时间被拉长。这样可以有效降低IAB迁移过程对UE业务中断时长的影响。
实施例4：
本申请实施例还可以实现在无线回传链路支持逻辑信道组(Logical channel group，LCG)扩展的情况下，IAB节点选择缓存状态报告(Buffer status report，BSR)格式。
下面对下文中提及的术语进行详细介绍。
LCG ID：即逻辑信道组的标识，长度为3bits。
LCG i：在Long BSR(长BSR)格式中，该字段取值为1，指示该BSR中包含逻辑信道组i的Buffer Size字段，若该字段取值为0则指示该BSR中不包含逻辑信道组i的Buffer Size字段。在Long truncated BSR(截断的长BSR)的格式中，该字段用于指示逻辑信道组i是否有待发送的data，具体的，该字段取值为1表明逻辑信道组i有数据待发送，取值为0则表明逻辑信道组i没有数据待发送。其中，i为整数，取值范围为0≤i≤7。
Buffer Size：用于表明一个逻辑信道组中的所有逻辑信道对应的待发送数据量之和，每个逻辑信道组的数据量是指MAC PDU组包之后统计的该逻辑信道组中各个逻辑信道对应的待传数据量之和。数据量的单位为字节(byte)。每个LCG对应的Buffer Size字段在short BSR或short truncated BSR格式中长度为5bits，在long BSR或long truncated BSR中的长度为8bits。
在IAB网络中，一种可能的实现方式是，IAB宿主所辖范围内，可能会有多个IAB节点，且每个无线回传节点可以为多个不同的用户设备(UE)提供接入和回传服务，考虑到这些IAB节点所服务的UE可能会有多种不同类型的业务，这些不同UE的不同类型业务的QoS需求也各不相同，因此在无线回传链路，将通过不同的BH RLC CH来提供数据或信令在无线回传链路的不同的QoS保障。在一个无线回传链路，BH RLC CH的最大数量可以达到6万多，每个BH RLC CH对应于一个逻辑信道。在上行传输中，IAB节点的MT部分会向父节点上报BSR，用于将待发送的上行数据包的数据量告知父节点，BSR可以视为子节点向父节点请求上行调度资源的一种方式，以便于父节点的DU部分为其分配上行传输资源。在IAB节点向父节点上报的BSR中，是以LCG为粒度进行缓存数据量上报的。BSR可以有多种不同的格式，例如在short BSR类型或short truncated BSR类型中，参见图10，可以仅包含一个LCG的缓存状态信息；而在long BSR类型或Long truncated BSR类型中，参见图11至多可以包含8个LCG的缓存状态信息。每个逻辑信道组中，一般会包含有相似调度需求的逻辑信道，而每个逻辑信道组中具体有哪些逻辑信道，是由IAB节点的父节点确定并生成了配置信息后，通过IAB宿主(在IAB宿主为CU-DU分离的情况下，具体为IAB宿主CU；在IAB宿主CU为CP-UP分离的情况下，具体还可以是IAB宿主CU-CP)的RRC消息发送给IAB节点的。
在目前协议规范中，支持的逻辑信道组数量只有8个。这个数值对于UE和基站之间的接入链路而言是合理的，因为UE和基站之间的逻辑信道的数量一般也不会超过32个；但是在无线回传链路的逻辑信道被扩展到最多支持6万多个的情况下，每个逻辑信道组可能会包含几千个逻辑信道，而这几千个逻辑信道的调度需求则有可能差异比较大。因此，本申请中，考虑将无线回传链路的LCG数量进行扩展，以便于对调度需求差异大的逻辑信道，能被分别配置在不同的逻辑信道组中，提高调度的合理性和 公平性。对于扩展后的LCG的最大值，可以是例如16、32、64、256等取值，具体数值本申请实施例不予限制。
在逻辑信道组的数量扩展后，一方面，逻辑信道组标识(Logical Channel Group ID，LCG ID)也需要扩展，例如LCG的最大值若扩展为16，则在LCG ID可能会被扩展为4bits，或者，LCG的最大值扩展为256，则LCG ID需要被扩展为8bits。另一方面，LCG ID扩展后，相应地，BSR的格式也需要扩展，需要引入新的BSR格式。例如，若LCG最大的值扩展为256后，需要引入支持扩展LCG的新的短BSR格式和支持扩展LCG的新的截断的短BSR格式，以及支持扩展LCG的新的长BSR格式和支持扩展LCG的新的截断的长BSR格式。一种可能的示例中，假设该新的短BSR格式和新的截断的短BSR格式如下图12所示。另一种可能的示例中，假设新的长BSR格式如下图13所示。对于LCG扩展后需要引入的新的BSR格式(包括例如新的短BSR格式，新的截断的短BSR格式，新的长BSR格式，新的截断的长BSR格式)的具体设计，本申请实施例不予限定。
在逻辑信道组的最大值被扩展后，为了使得IAB节点选择合适的BSR格式进行BSR上报，以尽量减小上报的信令开销，本申请提出以下在无线回传链路进行缓存数据量信息上报的BSR格式选择的方案，适用于IAB节点(具体可以是IAB节点的MT部分)。
一种可能的实施方式中，如果IAB节点被配置了扩展的LCG，则该IAB节点在需要上报BSR的时候，就采用支持扩展LCG的新的BSR的格式。
又一种可能的实施方式中，如果IAB节点被配置了扩展的LCG，且需要在BSR中包含至少一个扩展的LCG中的缓存状态信息，则采用支持扩展LCG的新的BSR格式，否则可以采用现有的BSR格式(即现有协议规定的short BSR/short truncated BSR/long BSR/long truncated BSR格式，或者统称为legacy BSR)。作为一种示例，IAB节点被配置了扩展的LCG，但是所有需要上报缓存状态的LCG ID均为传统(legacy)的LCG，则仍然采用现有的BSR格式。这种方式中，即使在IAB节点和父节点之间的无线回传链路将LCG进行了扩展，IAB节点仍然可以在有些情况下采用现有的BSR格式进行缓存数据量信息上报，可以一定程度的节省上报开销。
又一种可能的实施方式中，虽然协议支持的最大LCG被扩展为数值X(例如X＝16或32，或256)，对X的具体取值不限制，但是IAB节点与父节点之间的无线回传链路上的LCG的个数和LCG ID的长度仍然可被配置，基于配置的LCG ID的个数和/或LCG ID的长度，IAB节点可以确定支持扩展的LCG的新的BSR格式。其中，IAB节点获取其与父节点之间的无线回传链路上的LCG的个数和/或LCG ID的长度的配置信息，具体可以是：由该IAB节点的父节点确定后，通过IAB donor配置给该IAB节点；或者由IAB donor确定后，直接配置给该IAB节点；或者是由IAB donor确定后，先配置给IAB节点的父节点，再由该IAB节点的父节点配置给该IAB节点。作为该实施方式的一种示例，X＝256，但是IAB节点和父节点之间的最大LCG的个数配置为16，LCG ID的长度为4bits，则IAB节点在需要采用支持扩展LCG的BSR的时候，可以选择与支持最大LCG数量为16所对应的支持扩展LCG的新BSR格式。示例性的，支持扩展LCG且扩展后LCG的最大个数为16的short BSR的格式，可以是在图12所示的格式中，将第一个字节(Oct 1)对应的最低的4个比特位设置为保留(Reserved)比特， 或者将第一个字节(Oct 1)对应的最低的4个比特位与第二个字节中的最高的4个(或2个)比特位一起设置为Buffer Size字段，而将第二个字节中的最低的4个(或6个)比特位设置为保留比特。示例性的，支持扩展LCG且扩展后LCG的最大个数为16的long BSR的格式，可以是在图13所示的格式中，将第一个字节(Oct 1)和第二个字节(Oct 2)分别设置为LCG ID从最大值(LCG 15)到最小值(LCG 0)所对应的bitmap，将从第三个字节后的部分设置为与bitmap中取值为1的LCG对应的Buffer size字段。对于无线回传链路支持不同LCG ID长度，或支持不同扩展后的LCG数量的新的BSR格式的具体设置，本申请实施例不予限制。
需要说明的是，为便于理解，本申请中，可以将LCG ID大于7的逻辑信道组，视为扩展的LCG，将LCG ID在{0,1,2,3,4,5,6,7}中取值的逻辑信道组视为传统(legacy)的LCG。
当IAB节点具体是采用支持扩展LCG新的BSR格式中的哪一种(新的短BSR格式，新的截断的短BSR格式，新的长BSR格式，新的截断的长BSR格式)，则仍然是根据上报的具体需求而定，这一点与目前IAB节点或UE从{short BSR，short truncated BSR，long BSR，long truncated BSR}中选择一种格式的方式类似，例如，如果IAB节点只需要向父节点上报无线回传链路上的一个扩展LCG中的缓存状态信息，则采用新的短BSR格式即可。
基于本申请实施例的方案，在无线回传链路上的逻辑信道组被扩展后，IAB节点可以根据其与父节点之间链路的实际情况，选择合适的BSR格式进行BSR上报，可以节省信令开销。
基于与上述方法实施例相同构思，本申请实施例提供了一种IAB节点连接更新装置。图14为本申请实施例提供的一种IAB节点连接更新装置的结构示意图，该装置用于实现上述方法实施例中描述的方法。一种可能的实现中，该装置包括：第一收发模块1402和连接模块1404；
第一收发模块1402用于接收第一指示信息；
连接模块1404用于根据第一指示信息，第一IAB节点的DU部分与目标IAB宿主建立F1连接。
一种可能的实现中，上述装置还包括：
变更模块用于将第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区。
一种可能的实现中，第一收发模块1402，包括：
第一收发子模块用于接收来自源IAB宿主的第一指示信息；或者
第二收发子模块用于接收来自操作管理维护OAM的第一指示信息。
一种可能的实现中，第一指示信息为目标IAB宿主的IP地址；或者，
第一指示信息包括目标IAB宿主的IP地址，以及用于指示第一IAB节点的DU部分发起与目标IAB宿主之间建立F1连接的显式指示信息。
一种可能的实现中，所述第二收发子模块具体用于：
确定目标小区的标识，目标小区是第一IAB节点进行连接更新后接入的小区；
将目标小区的标识发送至操作管理维护OAM，以使得操作管理维护OAM基于目标小区的标识，确定目标IAB宿主；
接收来自操作管理维护OAM的第一指示信息。
一种可能的实现中，第一收发子模块具体用于：
向源IAB宿主发送测量报告；其中，第一指示信息为源IAB宿主基于测量报告确定的；
接收来自源IAB宿主的第一指示信息。
一种可能的实现中，第一收发子模块具体用于：
第一IAB节点的MT部分在发生无线链路失败后执行无线资源控制RRC重建立过程，接入目标小区后与目标IAB宿主进行连接；其中，第一指示信息为源IAB宿主基于用于请求第一IAB节点的上下文的请求消息确定的，用于请求所述第一IAB节点的上下文的请求消息是由目标IAB宿主向源IAB宿主发送的；
接收来自源IAB宿主的第一指示信息。
一种可能的实现中，变更模块，包括：
第三收发子模块用于接收第二指示信息；
变更子模块用于根据第二指示信息，将第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区；或者
第一确定模块用于确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息；
变更子模块用于将第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区；
其中，配置信息为第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息；或者
第三收发子模块用于接收第二指示信息，并确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息；
变更子模块用于将第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区；
其中，配置信息为第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息。
一种可能的实现中，第三收发子模块具体用于：
第一IAB节点的MT部分仍然连接至源IAB宿主，第一IAB节点的MT部分接收来自源IAB宿主通过无线资源控制RRC消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区；或者
第一IAB节点的DU部分接收来自源IAB宿主通过F1应用协议F1AP消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更 至目标IAB宿主下的小区。
一种可能的实现中，第三收发子模块具体用于：
第一IAB节点的MT部分已连接至目标IAB宿主，第一IAB节点的MT部分接收来自目标IAB宿主通过无线资源控制RRC消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区；或者
第一IAB节点的DU部分接收来自目标IAB宿主通过F1应用协议F1AP消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区。
一种可能的实现中，第一确定模块具体用于：
第一IAB节点的DU部分从源IAB宿主接收到F1应用协议F1AP消息，F1应用协议F1AP消息中携带RRC消息容器，RRC消息容器中封装有第一IAB节点的下属UE和/或下属IAB节点的RRC消息；
若F1应用协议F1AP消息中携带有第三指示信息，则在将RRC消息成功发送至第一IAB节点的下属UE和/或下属IAB节点后，确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息；或者
若F1应用协议F1AP消息被携带在第一序号的数据包中，则在将RRC消息成功发送至第一IAB节点的下属UE和/或下属IAB节点后，确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息，其中，第一序号是流控传输协议SCTP层的数据包序号，由源IAB宿主配置给第一IAB节点。
一种可能的实现中，第三指示信息为用于指示第一IAB节点停止对其下属UE和/或下属IAB节点进行数据传输调度的指示信息；或者
所述第三指示信息为用于指示RRC消息容器中携带的RRC消息中，包含第一IAB节点的下属UE和/或下属IAB节点接入目标IAB宿主下的小区需要的RRC配置信息，其中，目标IAB宿主下的小区是第一IAB节点的DU部分在其服务的小区变更为目标IAB宿主下的小区后所服务的小区。
一种可能的实现中，上述装置还包括：
第二确定模块用于根据F1应用协议F1AP消息中携带的第三指示信息或者根据F1应用协议F1AP消息被携带在第一序号的数据包，确定F1应用协议F1AP消息中携带的第一IAB节点的下属UE和/或下属IAB节点的RRC消息包含第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息，则
先缓存第一IAB节点的下属UE和/或下属IAB节点的RRC消息，在接收到第二指示信息后，再向第一IAB节点的下属UE和/或下属IAB节点发送其RRC消息。
一种可能的实现中，上述装置还包括：
广播模块用于第一IAB节点的DU部分广播第四指示信息，第四指示信息用于指示第一IAB节点的下属UE和/或下属IAB节点生效配置信息；或者
第二收发模块用于向第一IAB节点的下属UE和/或下属IAB节点指示时长信息， 时长信息用于指示第一IAB节点的下属UE和/或下属IAB节点生效配置信息的时刻。
基于与上述方法实施例相同构思，本申请实施例又提供了一种IAB节点连接更新装置。图15为本申请实施例提供的一种IAB节点连接更新装置的结构示意图，该装置用于实现上述方法实施例中描述的方法。一种可能的实现中，该装置包括：第三确定模块1502和第三收发模块1504；
第三确定模块1502用于确定第一IAB节点的DU部分需要执行连接更新与目标IAB宿主建立F1连接；
第三收发模块1504用于向第一IAB节点发送第一指示信息，第一指示信息用于指示第一IAB节点的DU部分与目标IAB宿主建立F1连接。
在一种可能的实现中，上述装置还包括：
第四收发模块用于向第一IAB节点发送第二指示信息，第二指示信息用于指示第一IAB节点的DU部分所服务的小区从源IAB宿主下的小区变更至目标IAB宿主下的小区。
在一种可能的实现中，上述装置还包括：
第五收发模块用于向目标IAB宿主发送第一请求消息，第一请求消息用于请求目标IAB宿主的IP地址；
第五收发模块还用于接收来自目标IAB宿主的第一响应消息，第一响应消息包括目标IAB宿主的IP地址；
其中，第一指示信息为目标IAB宿主的IP地址；或者，
第一指示信息包括目标IAB宿主的IP地址，以及用于指示第一IAB节点的DU部分发起与目标IAB宿主之间建立F1连接的显式指示信息。
在一种可能的实现中，向第一IAB节点发送第一指示信息，包括：
接收来自第一IAB节点的测量报告；基于测量报告，源IAB宿主确定第一指示信息；
向第一IAB节点发送第一指示信息。
在一种可能的实现中，向第一IAB节点发送第一指示信息，包括：
在第一IAB节点的MT部分在发生无线链路失败后执行无线资源控制RRC重建立过程接入目标小区后与目标IAB宿主进行连接的情况下，接收来自目标IAB宿主的用于请求第一IAB节点的上下文的请求消息，基于用于请求第一IAB节点的上下文的请求消息，确定第一指示信息，其中，目标小区是第一IAB节点进行连接更新后接入的小区；
向第一IAB节点发送第一指示信息。
在一种可能的实现中，第四收发模块具体用于：
在第一IAB节点的MT部分仍然连接至源IAB宿主的情况下，向第一IAB节点的MT部分发送通过无线资源控制RRC消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区；或者
向第一IAB节点的DU部分发送通过F1应用协议F1AP消息携带的第二指示信息；
其中，第二指示信息用于指示可以将第一IAB节点的DU部分所服务的小区变更至目标IAB宿主下的小区。
在一种可能的实现中，上述装置还包括：
第六收发模块用于向第一IAB节点的DU部分发送F1应用协议F1AP消息，F1应用协议F1AP消息中携带RRC消息容器和第三指示信息，RRC消息容器中封装有第一IAB节点的下属UE和/或下属IAB节点的RRC消息，以使得第一IAB节点在将RRC消息成功发送至第一IAB节点的下属UE和/或下属IAB节点后，确定第一IAB节点的下属UE和/或下属IAB节点接收到配置信息；
其中，配置信息为第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息。
在一种可能的实现中，第三指示信息为用于指示第一IAB节点停止对其下属UE和/或下属IAB节点进行数据传输调度的指示信息；或者
第三指示信息用于指示RRC消息容器中携带的RRC消息中，包含第一IAB节点的下属UE和/或下属IAB节点接入目标IAB宿主下的小区需要的RRC配置信息，其中，目标IAB宿主下的小区是第一IAB节点的DU部分在其服务的小区变更为目标IAB宿主下的小区后所服务的小区。
基于与上述方法实施例相同构思，本申请实施例另提供了一种IAB节点连接更新装置。图16为本申请实施例提供的一种IAB节点连接更新装置的结构示意图，该装置用于实现上述方法实施例中描述的方法。一种可能的实现中，该装置包括：第四确定模块1602和第七收发模块1604；
第四确定模块1602用于确定第一IAB节点的DU部分需要与目标IAB宿主建立F1连接；
第七收发模块1604用于向第一IAB节点发送第一指示信息，第一指示信息用于指示第一IAB节点与目标IAB宿主建立F1连接。
在一种可能的实现中，第一指示信息为目标IAB宿主的IP地址，或者
第一指示信息包括目标IAB宿主的IP地址，以及用于指示第一IAB节点的DU部分发起与目标IAB宿主之间建立F1连接的显式指示信息。
基于与上述方法实施例相同构思，本申请实施例另提供了一种IAB节点连接更新装置。图17为本申请实施例提供的一种IAB节点连接更新装置的结构示意图，该装置用于实现上述方法实施例中描述的方法。一种可能的实现中，该装置包括：第八收发模块1702和生效模块1704；
第八收发模块1702用于接收来自第一IAB节点的DU部分的配置信息；
其中，配置信息为第一IAB节点的下属UE和/或下属IAB节点在第一IAB节点的DU部分所服务的小区变更为目标IAB宿主下的小区后，接入目标IAB宿主下的小区需要的RRC配置信息；
生效模块1704用于生效配置信息。
在一种可能的实现中，配置信息包括第五指示信息，第五指示信息用于指示延迟生效配置信息；
生效模块1704具体用于：
接收来自第一IAB节点的DU部分的第四指示信息；
根据第四指示信息，生效配置信息。
在一种可能的实现中，上述装置还包括：
第九收发模块用于接收来自第一IAB节点的时长信息，时长信息用于指示第一IAB节点的下属UE和/或下属IAB节点生效配置信息的时刻；
生效模块1704具体用于：
根据生效配置信息的时刻，生效配置信息。
在一种可能的实现中，生效模块1704具体用于：
在下属节点搜索到目标小区的情况下，生效配置信息；
其中，目标小区是第一IAB节点的DU部分在其服务的小区变更为目标IAB宿主下的小区后所服务的小区，由配置信息中的目标小区标识进行标识。
在一种可能的实现中，生效模块1704具体用于：
根据配置信息，接入到目标小区，与目标IAB宿主建立连接。
本申请实施例提供的如图14、15、16或17所示的IAB节点连接更新的结构示意图还可以执行实施例2、实施例3或实施例4的各个步骤。
本申请实施例还提供一种IAB节点连接更新装置，包括至少一个处理器，所述处理器用于执行存储器中存储的程序，当所述程序被执行时，使得所述装置执行如图8(a)、如图8(b)和/或如图8(c)所示的IAB节点连接更新方法的各个步骤。
本申请实施例提供了一种计算机可读存储介质，上述计算机可读存储介质上存储有计算机程序，上述计算机程序被处理器执行时，如图8(a)、如图8(b)和/或如图8(c)所示的IAB节点连接更新方法的各个步骤被执行。
基于与上述方法实施例相同构思，本申请实施例还提供了一种包括指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得这个计算机执行如图8(a)、如图8(b)和/或如图8(c)所示的IAB节点连接更新方法的各个步骤。
应说明的是：以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (80)

  1. 一种通信方法，应用于接入回传一体化IAB节点，其特征在于，包括：
    接收所述IAB节点的分布式单元DU部分启动所需要的配置信息；
    根据接收所述配置信息的方式，确定所述IAB节点的主站或所述IAB节点的辅站为所述IAB节点的宿主节点。
  2. 根据权利要求1所述的方法，其特征在于，所述根据接收所述配置信息的方式，确定所述IAB节点的主站或所述IAB节点的辅站为所述IAB节点的宿主节点，包括：
    若所述配置信息为所述IAB节点的主站生成的第二配置信息，则确定所述IAB节点的主站为所述IAB节点的宿主节点；或者
    若所述配置信息为所述IAB节点的辅站生成的第三配置信息，则确定所述IAB节点的辅站为所述IAB节点的宿主节点。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    若所述配置信息为所述IAB节点的主站生成的第二配置信息，则确定与主小区组MCG对应的所述IAB节点与所述IAB节点的父节点之间的链路为缺省的回传链路default BH link；或者
    若所述配置信息为所述IAB节点的辅站生成的第三配置信息，则确定与辅小区组SCG对应的所述IAB节点与所述IAB节点的父节点之间的链路为缺省的回传链路default BH link。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述IAB节点的DU部分启动所需要的配置信息包括：缺省的BH RLC CH标识default BH RLC CH ID，缺省的BAP路由标识default BAP routing ID。
  5. 根据权利要求1-4中任一所述的方法，其特征在于，所述根据接收所述配置信息的方式，确定所述IAB节点的主站或所述IAB节点的辅站为所述IAB节点的宿主节点，包括：
    若所述配置信息被包含在信令无线承载SRB3的无线资源控制RRC消息中，则确定所述IAB节点的辅站为所述IAB节点的宿主节点；或者
    若所述配置信息被封装在信令无线承载SRB1或信令无线承载SRB2的无线资源控制RRC消息所包含的一个RRC消息容器中，则确定所述IAB节点的辅站为所述IAB节点的宿主节点；或者
    若所述配置信息被包含在信令无线承载SRB1或信令无线承载SRB2的无线资源控制RRC消息中，且没有被封装在SRB1或SRB2的无线资源控制RRC消息所包含的一个RRC消息容器中，则确定所述IAB节点的主站为所述IAB节点的宿主节点。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述根据接收所述配置信息的方式，确定所述IAB节点的主站或所述IAB节点的辅站为所述IAB节点的宿主节点，包括：
    若所述配置信息被包含在信令无线承载SRB3的无线资源控制RRC消息中，则确定与辅小区组SCG对应的所述IAB节点与所述IAB节点的父节点之间的链路为其默认回传default BH链路；或者
    若所述配置信息被封装在信令无线承载SRB1或信令无线承载SRB2的无线资源控制RRC消息所包含的一个RRC消息容器中，则确定与其辅小区组SCG对应的所述IAB节点与所述IAB节点的父节点之间的链路为其默认回传default BH链路；或者
    若所述配置信息被包含在信令无线承载SRB1或信令无线承载SRB2的无线资源控制RRC消息中，且没有被封装在SRB1或SRB2的RRC消息所包含的一个RRC消息容器中，则确定与其主小区组MCG对应的所述IAB节点与所述IAB节点的父节点之间的链路为其默认回传default BH链路。
  7. 一种通信方法，应用于接入回传一体化IAB节点的主站，其特征在于，包括：
    确定所述IAB节点的辅站为所述IAB节点的宿主节点；
    向所述IAB节点的辅站发送指示信息，所述指示信息用于通知所述IAB节点的辅站被选择作为所述IAB节点的宿主节点。
  8. 一种通信方法，应用于接入回传一体化IAB节点的辅站，其特征在于，所述方法包括：
    接收来自所述IAB节点的主站的指示信息，所述指示信息用于通知所述IAB节点的辅站被选择作为所述IAB节点的宿主节点；
    生成第三配置信息并向所述IAB节点发送所述第三配置信息，所述第三配置信息包括所述IAB节点的分布式单元DU部分启动所需要的配置信息。
  9. 根据权利要求8所述的方法，其特征在于，所述IAB节点的DU部分启动所需要的配置信息包括如下内容中的一项或多项：所述IAB节点的辅站的IP地址、所述IAB节点的IP地址、与辅小区组SCG对应的所述IAB节点与所述IAB节点的父节点之间链路上的BH RLC CH的配置信息、所述IAB节点的BAP层标识、与辅小区组SCG对应的所述IAB节点与所述IAB节点的父节点之间链路上的缺省BH RLC CH的标识、所述IAB节点的上行的缺省的BAP路由标识、与辅小区组SCG对应的所述IAB节点的父节点的BAP层标识。
  10. 一种通信方法，其特征在于，包括：
    接入回传一体化IAB节点确定被配置了扩展逻辑信道组LCG；
    所述IAB节点确定采用支持扩展LCG的新的缓存状态报告BSR格式上报BSR。
  11. 根据权利要求10所述的方法，其特征在于，所述支持扩展LCG的新的BSR格式包括以下中的一项或多项：新的短BSR格式、新的截断的短BSR格式、新的长BSR格式和新的截断的长BSR格式。
  12. 根据权利要求10或11所述的方法，其特征在于，还包括：
    如果所述IAB节点确定只需要上报无线回传链路上的一个扩展LCG中的缓存状态信息，则所述IAB节点确定采用新的短BSR格式上报BSR。
  13. 根据权利要求10或11所述的方法，其特征在于，还包括：
    如果所述IAB节点确定需要在缓存状态报告BSR中包含至少一个扩展的LCG中的缓存状态信息，则所述IAB节点确定采用支持扩展LCG的新的缓存状态报告BSR 格式上报BSR，其中，所述扩展的LCG的逻辑信道组标识LCG ID大于7。
  14. 根据权利要求10或11所述的方法，其特征在于，还包括：
    如果所述IAB节点确定只需要在缓存状态报告BSR中包含至少一个传统的LCG中的缓存状态信息，则所述IAB节点确定采用不支持扩展LCG的缓存状态报告BSR格式上报BSR，其中，所述传统的LCG的逻辑信道组标识LCG ID小于等于7。
  15. 根据权利要求10-14任一项所述的方法，其特征在于，还包括：
    所述IAB节点接收来自所述IAB节点的宿主节点的无线资源控制RRC消息，所述RRC消息中包括用于配置LCG的配置信息。
  16. 一种IAB节点连接更新方法，应用于第一IAB节点，其特征在于，所述第一IAB节点包含MT部分和DU部分，可以为一个或多个下属UE和/或下属IAB节点提供接入和回传服务，所述第一IAB节点在连接更新前连接到源IAB宿主，在连接更新后连接到目标IAB宿主，所述方法包括：
    接收第一指示信息；
    根据所述第一指示信息，所述第一IAB节点的DU部分与所述目标IAB宿主建立F1连接。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    将所述第一IAB节点的DU部分所服务的小区从所述源IAB宿主下的小区变更至所述目标IAB宿主下的小区。
  18. 根据权利要求16所述的方法，其特征在于，所述接收第一指示信息，包括：
    接收来自所述源IAB宿主的所述第一指示信息；或者
    接收来自操作管理维护OAM的所述第一指示信息。
  19. 根据权利要求18所述的方法，其特征在于，
    所述第一指示信息为所述目标IAB宿主的IP地址；或者
    所述第一指示信息包括所述目标IAB宿主的IP地址，以及用于指示所述第一IAB节点的DU部分发起与所述目标IAB宿主之间建立F1连接的显式指示信息。
  20. 根据权利要求18或19任一项所述的方法，其特征在于，所述接收来自操作管理维护OAM的第一指示信息，包括：
    确定目标小区的标识，所述目标小区是所述第一IAB节点进行连接更新后接入的小区；
    将所述目标小区的标识发送至所述操作管理维护OAM，以使得所述操作管理维护OAM基于所述目标小区的标识，确定所述目标IAB宿主；
    接收来自所述操作管理维护OAM的第一指示信息。
  21. 根据权利要求18或19任一项所述的方法，其特征在于，所述接收来自所述源IAB宿主的第一指示信息，包括：
    向所述源IAB宿主发送测量报告；其中，所述第一指示信息为所述源IAB宿主基于所述测量报告确定的；
    接收来自所述源IAB宿主的所述第一指示信息。
  22. 根据权利要求18或19任一项所述的方法，其特征在于，所述接收来自所述源 IAB宿主的第一指示信息，包括：
    所述第一IAB节点的MT部分在发生无线链路失败后执行无线资源控制RRC重建立过程，接入所述目标小区后与所述目标IAB宿主进行连接；其中，所述第一指示信息为所述源IAB宿主基于用于请求所述第一IAB节点的上下文的请求消息确定的，所述用于请求所述第一IAB节点的上下文的请求消息是由所述目标IAB宿主向所述源IAB宿主发送的；
    接收来自所述源IAB宿主的所述第一指示信息。
  23. 根据权利要求17所述的方法，其特征在于，所述将所述第一IAB节点的DU部分所服务的小区从所述源IAB宿主下的小区变更至所述目标IAB宿主下的小区，包括：
    接收第二指示信息；
    根据所述第二指示信息，将所述第一IAB节点的DU部分所服务的小区从所述源IAB宿主下的小区变更至所述目标IAB宿主下的小区；或者
    确定所述第一IAB节点的下属UE和/或下属IAB节点接收到配置信息；
    将所述第一IAB节点的DU部分所服务的小区从所述源IAB宿主下的小区变更至所述目标IAB宿主下的小区；
    其中，所述配置信息为所述第一IAB节点的下属UE和/或下属IAB节点在所述第一IAB节点的DU部分所服务的小区变更为所述目标IAB宿主下的小区后，接入所述目标IAB宿主下的小区需要的RRC配置信息；或者
    接收第二指示信息，并确定所述第一IAB节点的下属UE和/或下属IAB节点接收到所述配置信息；
    将所述第一IAB节点的DU部分所服务的小区从所述源IAB宿主下的小区变更至所述目标IAB宿主下的小区；
    其中，所述配置信息为所述第一IAB节点的下属UE和/或下属IAB节点在所述第一IAB节点的DU部分所服务的小区变更为所述目标IAB宿主下的小区后，接入所述目标IAB宿主下的小区需要的RRC配置信息。
  24. 根据权利要求23所述的方法，其特征在于，所述接收第二指示信息，包括：
    所述第一IAB节点的MT部分仍然连接至所述源IAB宿主，所述第一IAB节点的MT部分接收来自所述源IAB宿主通过无线资源控制RRC消息携带的所述第二指示信息；
    其中，所述第二指示信息用于指示可以将所述第一IAB节点的DU部分所服务的小区变更至所述目标IAB宿主下的小区；或者
    所述第一IAB节点的DU部分接收来自所述源IAB宿主通过F1应用协议F1AP消息携带的所述第二指示信息；
    其中，所述第二指示信息用于指示可以将所述第一IAB节点的DU部分所服务的小区变更至所述目标IAB宿主下的小区。
  25. 根据权利要求23所述的方法，其特征在于，所述接收第二指示信息，包括：
    所述第一IAB节点的MT部分已连接至所述目标IAB宿主，所述第一IAB节点的MT部分接收来自所述目标IAB宿主通过无线资源控制RRC消息携带的所述第二指示 信息；
    其中，所述第二指示信息用于指示可以将所述第一IAB节点的DU部分所服务的小区变更至所述目标IAB宿主下的小区；或者
    所述第一IAB节点的DU部分接收来自所述目标IAB宿主通过F1应用协议F1AP消息携带的所述第二指示信息；
    其中，所述第二指示信息用于指示可以将所述第一IAB节点的DU部分所服务的小区变更至所述目标IAB宿主下的小区。
  26. 根据权利要求23所述的方法，其特征在于，所述确定所述第一IAB节点的下属UE和/或下属IAB节点接收到配置信息，包括：
    所述第一IAB节点的DU部分从所述源IAB宿主接收到F1应用协议F1AP消息，所述F1应用协议F1AP消息中携带RRC消息容器，所述RRC消息容器中封装有所述第一IAB节点的下属UE和/或下属IAB节点的RRC消息；
    若所述F1应用协议F1AP消息中携带有第三指示信息，则在将所述RRC消息成功发送至所述第一IAB节点的下属UE和/或下属IAB节点后，确定所述第一IAB节点的下属UE和/或下属IAB节点接收到所述配置信息；或者
    若所述F1应用协议F1AP消息被携带在第一序号的数据包中，则在将所述RRC消息成功发送至所述第一IAB节点的下属UE和/或下属IAB节点后，确定所述第一IAB节点的下属UE和/或下属IAB节点接收到所述配置信息，其中，所述第一序号是流控传输协议SCTP层的数据包序号，由所述源IAB宿主配置给所述第一IAB节点。
  27. 根据权利要求26所述的方法，其特征在于，
    所述第三指示信息为用于指示所述第一IAB节点停止对其下属UE和/或下属IAB节点进行数据传输调度的指示信息；或者
    所述第三指示信息为用于指示所述RRC消息容器中携带的RRC消息中，包含所述第一IAB节点的下属UE和/或下属IAB节点在所述第一IAB节点的DU部分所服务的小区变更为所述目标IAB宿主下的小区后，接入所述目标IAB宿主下的小区需要的RRC配置信息，其中，所述目标IAB宿主下的小区是所述第一IAB节点的DU部分在其服务的小区变更为所述目标IAB宿主下的小区后所服务的小区。
  28. 根据权利要求26所述的方法，其特征在于，所述方法还包括：
    根据所述F1应用协议F1AP消息中携带的第三指示信息或者根据所述F1应用协议F1AP消息被携带在第一序号的数据包，确定所述F1应用协议F1AP消息中携带的所述第一IAB节点的下属UE和/或下属IAB节点的RRC消息包含所述第一IAB节点的下属UE和/或下属IAB节点在所述第一IAB节点的DU部分所服务的小区变更为所述目标IAB宿主下的小区后，接入所述目标IAB宿主下的小区需要的RRC配置信息，则
    先缓存所述第一IAB节点的下属UE和/或下属IAB节点的RRC消息，在接收到所述第二指示信息后，再向所述第一IAB节点的下属UE和/或下属IAB节点发送其RRC消息。
  29. 根据权利要求23-28任一项所述的方法，其特征在于，所述方法还包括：
    所述第一IAB节点的DU部分广播第四指示信息，所述第四指示信息用于指示所 述第一IAB节点的下属UE和/或下属IAB节点生效所述配置信息；或者
    向所述第一IAB节点的下属UE和/或下属IAB节点指示时长信息，所述时长信息用于指示所述第一IAB节点的下属UE和/或下属IAB节点生效所述配置信息的时刻。
  30. 一种IAB节点连接更新方法，应用于源IAB宿主，其特征在于，第一IAB节点在连接更新前连接到所述源IAB宿主，所述第一IAB节点包含MT部分和DU部分，可以为一个或多个下属UE和/或下属IAB节点提供接入和回传服务，且所述第一IAB节点在连接更新后连接到目标IAB宿主，所述方法包括：
    确定所述第一IAB节点的DU部分需要执行连接更新与所述目标IAB宿主建立F1连接；
    向所述第一IAB节点发送第一指示信息，所述第一指示信息用于指示所述第一IAB节点的DU部分与所述目标IAB宿主建立F1连接。
  31. 根据权利要求30所述的方法，其特征在于，所述方法还包括：
    向所述第一IAB节点发送第二指示信息，所述第二指示信息用于指示所述第一IAB节点的DU部分所服务的小区从所述源IAB宿主下的小区变更至所述目标IAB宿主下的小区。
  32. 根据权利要求30所述的方法，其特征在于，所述方法还包括：
    向所述目标IAB宿主发送第一请求消息，所述第一请求消息用于请求所述目标IAB宿主的IP地址；
    接收来自所述目标IAB宿主的第一响应消息，所述第一响应消息包括所述目标IAB宿主的IP地址；
    其中，所述第一指示信息为所述目标IAB宿主的IP地址；或者
    所述第一指示信息包括所述目标IAB宿主的IP地址，以及用于指示所述第一IAB节点的DU部分发起与所述目标IAB宿主之间建立F1连接的显式指示信息。
  33. 根据权利要求30所述的方法，其特征在于，所述向所述第一IAB节点发送第一指示信息，包括：
    接收来自所述第一IAB节点的测量报告；基于所述测量报告，所述源IAB宿主确定所述第一指示信息；
    向所述第一IAB节点发送所述第一指示信息。
  34. 根据权利要求30所述的方法，其特征在于，所述向所述第一IAB节点发送第一指示信息，包括：
    在所述第一IAB节点的MT部分在发生无线链路失败后执行无线资源控制RRC重建立过程接入目标小区后与所述目标IAB宿主进行连接的情况下，接收来自所述目标IAB宿主的用于请求所述第一IAB节点的上下文的请求消息，基于所述用于请求所述第一IAB节点的上下文的请求消息，确定所述第一指示信息，所述目标小区是所述第一IAB节点进行连接更新后接入的小区；
    向所述第一IAB节点发送所述第一指示信息。
  35. 根据权利要求31所述的方法，其特征在于，所述向所述第一IAB节点发送第二指示信息，包括：
    在所述第一IAB节点的MT部分仍然连接至所述源IAB宿主的情况下，向所述第一IAB节点的MT部分发送通过无线资源控制RRC消息携带的所述第二指示信息；
    其中，所述第二指示信息用于指示可以将所述第一IAB节点的DU部分所服务的小区变更至所述目标IAB宿主下的小区；或者
    向所述第一IAB节点的DU部分发送通过F1应用协议F1AP消息携带的所述第二指示信息；
    其中，所述第二指示信息用于指示可以将所述第一IAB节点的DU部分所服务的小区变更至所述目标IAB宿主下的小区。
  36. 根据权利要求30-35任一项所述的方法，其特征在于，所述方法还包括：
    向所述第一IAB节点的DU部分发送F1应用协议F1AP消息，所述F1应用协议F1AP消息中携带RRC消息容器和第三指示信息，所述RRC消息容器中封装有所述第一IAB节点的下属UE和/或下属IAB节点的RRC消息，以使得所述第一IAB节点在将所述RRC消息成功发送至所述第一IAB节点的下属UE和/或下属IAB节点后，确定所述第一IAB节点的下属UE和/或下属IAB节点接收到所述配置信息；
    其中，所述配置信息为所述第一IAB节点的下属UE和/或下属IAB节点在所述第一IAB节点的DU部分所服务的小区变更为所述目标IAB宿主下的小区后，接入所述目标IAB宿主下的小区需要的RRC配置信息。
  37. 根据权利要求36所述的方法，其特征在于，
    所述第三指示信息为用于指示所述第一IAB节点停止对其下属UE和/或下属IAB节点进行数据传输调度的指示信息；或者
    所述第三指示信息用于指示所述RRC消息容器中携带的RRC消息中，包含所述第一IAB节点的下属UE和/或下属IAB节点接入所述目标IAB宿主下的小区需要的RRC配置信息，其中，所述目标IAB宿主下的小区是所述第一IAB节点的DU部分在其服务的小区变更为所述目标IAB宿主下的小区后所服务的小区。
  38. 一种通信装置，应用于接入回传一体化IAB节点，其特征在于，所述装置包括：
    用于接收所述IAB节点的分布式单元DU部分启动所需要的配置信息的模块；
    用于根据接收所述配置信息的方式，确定所述IAB节点的主站或所述IAB节点的辅站为所述IAB节点的宿主节点的模块。
  39. 根据权利要求38所述的装置，其特征在于，所述用于根据接收所述配置信息的方式，确定所述IAB节点的主站或所述IAB节点的辅站为所述IAB节点的宿主节点的模块，包括：
    用于若所述配置信息为所述IAB节点的主站生成的第二配置信息，则确定所述IAB节点的主站为所述IAB节点的宿主节点的模块；或者
    用于若所述配置信息为所述IAB节点的辅站生成的第三配置信息，则确定所述IAB节点的辅站为所述IAB节点的宿主节点的模块。
  40. 根据权利要求39所述的装置，其特征在于，所述装置还包括：
    用于若所述配置信息为所述IAB节点的主站生成的第二配置信息，则确定与主小 区组MCG对应的所述IAB节点与所述IAB节点的父节点之间的链路为缺省的回传链路default BH link的模块；或者
    用于若所述配置信息为所述IAB节点的辅站生成的第三配置信息，则确定与辅小区组SCG对应的所述IAB节点与所述IAB节点的父节点之间的链路为缺省的回传链路default BH link的模块。
  41. 根据权利要求38-40任一项所述的装置，其特征在于，所述IAB节点的DU部分启动所需要的配置信息包括：缺省的BH RLC CH标识default BH RLC CH ID，缺省的BAP路由标识default BAP routing ID。
  42. 根据权利要求38-41中任一所述的装置，其特征在于，所述用于根据接收所述配置信息的方式，确定所述IAB节点的主站或所述IAB节点的辅站为所述IAB节点的宿主节点的模块，包括：
    用于若所述配置信息被包含在信令无线承载SRB3的无线资源控制RRC消息中，则确定所述IAB节点的辅站为所述IAB节点的宿主节点的模块；或者
    用于若所述配置信息被封装在信令无线承载SRB1或信令无线承载SRB2的无线资源控制RRC消息所包含的一个RRC消息容器中，则确定所述IAB节点的辅站为所述IAB节点的宿主节点的模块；或者
    用于若所述配置信息被包含在信令无线承载SRB1或信令无线承载SRB2的无线资源控制RRC消息中，且没有被封装在SRB1或SRB2的RRC消息所包含的一个RRC消息容器中，则确定所述IAB节点的主站为所述IAB节点的宿主节点的模块。
  43. 根据权利要求38-42任一项所述的装置，其特征在于，所述用于根据接收所述配置信息的方式，确定所述IAB节点的主站或所述IAB节点的辅站为所述IAB节点的宿主节点的模块，包括：
    用于若所述配置信息被包含在信令无线承载SRB3的无线资源控制RRC消息中，则确定与辅小区组SCG对应的所述IAB节点与所述IAB节点的父节点之间的链路为其默认回传default BH链路的模块；或者
    用于若所述配置信息被封装在信令无线承载SRB1或信令无线承载SRB2的无线资源控制RRC消息所包含的一个RRC消息容器中，则确定与其辅小区组SCG对应的所述IAB节点与所述IAB节点的父节点之间的链路为其默认回传default BH链路的模块；或者
    用于若所述配置信息被包含在信令无线承载SRB1或信令无线承载SRB2的无线资源控制RRC消息中，且没有被封装在SRB1或SRB2的RRC消息所包含的一个RRC消息容器中，则确定与其主小区组MCG对应的所述IAB节点与所述IAB节点的父节点之间的链路为其默认回传default BH链路的模块。
  44. 一种通信装置，应用于接入回传一体化IAB节点的主站，其特征在于，所述装置包括：
    用于确定所述IAB节点的辅站为所述IAB节点的宿主节点的模块；
    用于向所述IAB节点的辅站发送指示信息的模块，所述指示信息用于通知所述IAB节点的辅站被选择作为所述IAB节点的宿主节点。
  45. 一种通信装置，应用于接入回传一体化IAB节点的辅站，其特征在于，所述装置包括：
    用于接收来自所述IAB节点的主站的指示信息的模块，所述指示信息用于通知所述IAB节点的辅站被选择作为所述IAB节点的宿主节点；
    用于生成第三配置信息并向所述IAB节点发送所述第三配置信息的模块，所述第三配置信息包括所述IAB节点的分布式单元DU部分启动所需要的配置信息。
  46. 根据权利要求45所述的装置，其特征在于，所述IAB节点的DU部分启动所需要的配置信息包括如下内容中的一项或多项：所述IAB节点的辅站的IP地址、所述IAB节点的IP地址、与辅小区组SCG对应的所述IAB节点与所述IAB节点的父节点之间链路上的BH RLC CH的配置信息、所述IAB节点的BAP层标识、与辅小区组SCG对应的所述IAB节点与所述IAB节点的父节点之间链路上的缺省BH RLC CH的标识、所述IAB节点的上行的缺省的BAP路由标识、与辅小区组SCG对应的所述IAB节点的父节点的BAP层标识。
  47. 一种通信装置，其特征在于，包括：
    用于确定被配置了扩展逻辑信道组LCG的模块；
    用于确定采用支持扩展LCG的新的缓存状态报告BSR格式上报BSR的模块。
  48. 根据权利要求47所述的装置，其特征在于，所述支持扩展LCG的新的BSR格式包括以下中的一项或多项：新的短BSR格式、新的截断的短BSR格式、新的长BSR格式和新的截断的长BSR格式。
  49. 根据权利要求47或48所述的装置，其特征在于，所述装置还包括：
    用于如果确定所述IAB节点只需要上报无线回传链路上的一个扩展LCG中的缓存状态信息，则确定采用新的短BSR格式上报BSR的模块。
  50. 根据权利要求47或48所述的装置，其特征在于，所述装置还包括：
    用于如果确定所述IAB节点需要在缓存状态报告BSR中包含至少一个扩展的LCG中的缓存状态信息，则确定采用支持扩展LCG的新的缓存状态报告BSR格式上报BSR的模块，其中，所述扩展的LCG的逻辑信道组标识LCG ID大于7。
  51. 根据权利要求47或48所述的装置，其特征在于，所述装置还包括：
    用于如果确定所述IAB节点只需要在缓存状态报告BSR中包含至少一个传统的LCG中的缓存状态信息，则确定采用不支持扩展LCG的缓存状态报告BSR格式上报BSR的模块，其中，所述传统的LCG的逻辑信道组标识LCG ID小于等于7。
  52. 根据权利要求47-51任一项所述的装置，其特征在于，所述装置还包括：
    用于接收来自所述IAB节点的宿主节点的无线资源控制RRC消息的模块，所述RRC消息中包括用于配置LCG的配置信息。
  53. 一种IAB节点连接更新装置，应用于第一IAB节点，其特征在于，所述第一IAB节点包含MT部分和DU部分，可以为一个或多个下属UE和/或下属IAB节点提供接入和回传服务，所述第一IAB节点在连接更新前连接到源IAB宿主，在连接更新 后连接到目标IAB宿主，所述装置包括：
    第一收发模块，用于接收第一指示信息；
    连接模块，用于根据所述第一指示信息，所述第一IAB节点的DU部分与所述目标IAB宿主建立F1连接。
  54. 根据权利要求53所述的装置，其特征在于，所述装置还包括：
    变更模块，用于将所述第一IAB节点的DU部分所服务的小区从所述源IAB宿主下的小区变更至所述目标IAB宿主下的小区。
  55. 根据权利要求53所述的装置，其特征在于，所述第一收发模块，包括：
    第一收发子模块，用于接收来自所述源IAB宿主的第一指示信息；或者
    第二收发子模块，用于接收来自操作管理维护OAM的第一指示信息。
  56. 根据权利要求55所述的装置，其特征在于，
    所述第一指示信息为所述目标IAB宿主的IP地址；或者，
    所述第一指示信息包括所述目标IAB宿主的IP地址，以及用于指示所述第一IAB节点的DU部分发起与所述目标IAB宿主之间建立F1连接的显式指示信息。
  57. 根据权利要求55或56任一项所述的装置，其特征在于，所述第二收发子模块，具体用于：
    确定目标小区的标识，所述目标小区是所述第一IAB节点进行连接更新后接入的小区；
    将所述目标小区的标识发送至所述操作管理维护OAM，以使得所述操作管理维护OAM基于所述目标小区的标识，确定所述目标IAB宿主；
    接收来自所述操作管理维护OAM的第一指示信息。
  58. 根据权利要求55或56任一项所述的装置，其特征在于，所述第一收发子模块，具体用于：
    向所述源IAB宿主发送测量报告；其中，所述第一指示信息为所述源IAB宿主基于所述测量报告确定的；
    接收来自所述源IAB宿主的所述第一指示信息。
  59. 根据权利要求55或56任一项所述的装置，其特征在于，所述第一收发子模块，具体用于：
    所述第一IAB节点的MT部分在发生无线链路失败后执行无线资源控制RRC重建立过程，接入所述目标小区后与所述目标IAB宿主进行连接；其中，所述第一指示信息为所述源IAB宿主基于用于请求所述第一IAB节点的上下文的请求消息确定的，所述用于请求所述第一IAB节点的上下文的请求消息是由所述目标IAB宿主向所述源IAB宿主发送的；
    接收来自所述源IAB宿主的所述第一指示信息。
  60. 根据权利要求54所述的装置，其特征在于，所述变更模块，包括：
    第三收发子模块，用于接收第二指示信息；
    变更子模块，用于根据所述第二指示信息，将所述第一IAB节点的DU部分所服务的小区从所述源IAB宿主下的小区变更至所述目标IAB宿主下的小区；或者
    第一确定模块，用于确定所述第一IAB节点的下属UE和/或下属IAB节点接收到 配置信息；
    所述变更子模块，用于将所述第一IAB节点的DU部分所服务的小区从所述源IAB宿主下的小区变更至所述目标IAB宿主下的小区；
    其中，所述配置信息为所述第一IAB节点的下属UE和/或下属IAB节点在所述第一IAB节点的DU部分所服务的小区变更为所述目标IAB宿主下的小区后，接入所述目标IAB宿主下的小区需要的RRC配置信息；或者
    所述第三收发子模块，用于接收第二指示信息，并确定所述第一IAB节点的下属UE和/或下属IAB节点接收到所述配置信息；
    所述变更子模块，用于将所述第一IAB节点的DU部分所服务的小区从所述源IAB宿主下的小区变更至所述目标IAB宿主下的小区；
    其中，所述配置信息为所述第一IAB节点的下属UE和/或下属IAB节点在所述第一IAB节点的DU部分所服务的小区变更为所述目标IAB宿主下的小区后，接入所述目标IAB宿主下的小区需要的RRC配置信息。
  61. 根据权利要求60所述的装置，其特征在于，所述第三收发子模块，具体用于：
    所述第一IAB节点的MT部分仍然连接至所述源IAB宿主，所述第一IAB节点的MT部分接收来自所述源IAB宿主通过无线资源控制RRC消息携带的所述第二指示信息；
    其中，所述第二指示信息用于指示可以将所述第一IAB节点的DU部分所服务的小区变更至所述目标IAB宿主下的小区；或者
    所述第一IAB节点的DU部分接收来自所述源IAB宿主通过F1应用协议F1AP消息携带的所述第二指示信息；
    其中，所述第二指示信息用于指示可以将所述第一IAB节点的DU部分所服务的小区变更至所述目标IAB宿主下的小区。
  62. 根据权利要求60所述的装置，其特征在于，所述第三收发子模块，具体用于：
    所述第一IAB节点的MT部分已连接至所述目标IAB宿主，所述第一IAB节点的MT部分接收来自所述目标IAB宿主通过无线资源控制RRC消息携带的所述第二指示信息；
    其中，所述第二指示信息用于指示可以将所述第一IAB节点的DU部分所服务的小区变更至所述目标IAB宿主下的小区；或者
    所述第一IAB节点的DU部分接收来自所述目标IAB宿主通过F1应用协议F1AP消息携带的所述第二指示信息；
    其中，所述第二指示信息用于指示可以将所述第一IAB节点的DU部分所服务的小区变更至所述目标IAB宿主下的小区。
  63. 根据权利要求60所述的装置，其特征在于，所述第一确定模块，具体用于：
    所述第一IAB节点的DU部分从所述源IAB宿主接收到F1应用协议F1AP消息，所述F1应用协议F1AP消息中携带RRC消息容器，所述RRC消息容器中封装有所述第一IAB节点的下属UE和/或下属IAB节点的RRC消息；
    若所述F1应用协议F1AP消息中携带有第三指示信息，则在将所述RRC消息成功发送至所述第一IAB节点的下属UE和/或下属IAB节点后，确定所述第一IAB节点的下属UE和/或下属IAB节点接收到所述配置信息；或者
    若所述F1应用协议F1AP消息被携带在第一序号的数据包中，则在将所述RRC消息成功发送至所述第一IAB节点的下属UE和/或下属IAB节点后，确定所述第一IAB节点的下属UE和/或下属IAB节点接收到所述配置信息，其中，所述第一序号是流控传输协议SCTP层的数据包序号，由所述源IAB宿主配置给所述第一IAB节点。
  64. 根据权利要求63所述的装置，其特征在于，
    所述第三指示信息为用于指示所述第一IAB节点停止对其下属UE和/或下属IAB节点进行数据传输调度的指示信息；或者
    所述第三指示信息为用于指示所述RRC消息容器中携带的RRC消息中，包含所述第一IAB节点的下属UE和/或下属IAB节点在所述第一IAB节点的DU部分所服务的小区变更为所述目标IAB宿主下的小区后，接入所述目标IAB宿主下的小区需要的RRC配置信息，其中，所述目标IAB宿主下的小区是所述第一IAB节点的DU部分在其服务的小区变更为所述目标IAB宿主下的小区后所服务的小区。
  65. 根据权利要求63所述的装置，其特征在于，所述装置还包括：
    第二确定模块，用于根据所述F1应用协议F1AP消息中携带的第三指示信息或者根据所述F1应用协议F1AP消息被携带在第一序号的数据包，确定所述F1应用协议F1AP消息中携带的所述第一IAB节点的下属UE和/或下属IAB节点的RRC消息包含所述第一IAB节点的下属UE和/或下属IAB节点在所述第一IAB节点的DU部分所服务的小区变更为所述目标IAB宿主下的小区后，接入所述目标IAB宿主下的小区需要的RRC配置信息，则
    先缓存所述第一IAB节点的下属UE和/或下属IAB节点的RRC消息，在接收到所述第二指示信息后，再向所述第一IAB节点的下属UE和/或下属IAB节点发送其RRC消息。
  66. 根据权利要求60-65任一项所述的装置，其特征在于，所述装置还包括：
    广播模块，用于所述第一IAB节点的DU部分广播第四指示信息，所述第四指示信息用于指示所述第一IAB节点的下属UE和/或下属IAB节点生效所述配置信息；或者
    第二收发模块，用于向所述第一IAB节点的下属UE和/或下属IAB节点指示时长信息，所述时长信息用于指示所述第一IAB节点的下属UE和/或下属IAB节点生效所述配置信息的时刻。
  67. 一种IAB节点连接更新装置，应用于源IAB宿主，其特征在于，第一IAB节点在连接更新前连接到所述源IAB宿主，所述第一IAB节点包含MT部分和DU部分，可以为一个或多个下属UE和/或下属IAB节点提供接入和回传服务，且所述第一IAB节点在连接更新后连接到目标IAB宿主，所述装置包括：
    第三确定模块，用于确定所述第一IAB节点的DU部分需要执行连接更新与所述目标IAB宿主建立F1连接；
    第三收发模块，用于向所述第一IAB节点发送第一指示信息，所述第一指示信息用于指示所述第一IAB节点的DU部分与所述目标IAB宿主建立F1连接。
  68. 根据权利要求67所述的装置，其特征在于，所述装置还包括：
    第四收发模块，用于向所述第一IAB节点发送第二指示信息，所述第二指示信息用于指示所述第一IAB节点的DU部分所服务的小区从所述源IAB宿主下的小区变更至所述目标IAB宿主下的小区。
  69. 根据权利要求67所述的装置，其特征在于，所述装置还包括：
    第五收发模块，用于向所述目标IAB宿主发送第一请求消息，所述第一请求消息用于请求所述目标IAB宿主的IP地址；
    所述第五收发模块，还用于接收来自所述目标IAB宿主的第一响应消息，所述第一响应消息包括所述目标IAB宿主的IP地址；
    其中，所述第一指示信息为所述目标IAB宿主的IP地址；或者，
    所述第一指示信息包括所述目标IAB宿主的IP地址，以及用于指示所述第一IAB节点的DU部分发起与所述目标IAB宿主之间建立F1连接的显式指示信息。
  70. 根据权利要求67所述的装置，其特征在于，所述向所述第一IAB节点发送第一指示信息，包括：
    接收来自所述第一IAB节点的测量报告；基于所述测量报告，所述源IAB宿主确定所述第一指示信息；
    向所述第一IAB节点发送所述第一指示信息。
  71. 根据权利要求67所述的装置，其特征在于，所述向所述第一IAB节点发送第一指示信息，包括：
    在所述第一IAB节点的MT部分在发生无线链路失败后执行无线资源控制RRC重建立过程接入目标小区后与所述目标IAB宿主进行连接的情况下，接收来自所述目标IAB宿主的用于请求所述第一IAB节点的上下文的请求消息，基于所述用于请求所述第一IAB节点的上下文的请求消息，确定所述第一指示信息，其中，所述目标小区是所述第一IAB节点进行连接更新后接入的小区；
    向所述第一IAB节点发送所述第一指示信息。
  72. 根据权利要求68所述的装置，其特征在于，所述第四收发模块，具体用于：
    在所述第一IAB节点的MT部分仍然连接至所述源IAB宿主的情况下，向所述第一IAB节点的MT部分发送通过无线资源控制RRC消息携带的所述第二指示信息；
    其中，所述第二指示信息用于指示可以将所述第一IAB节点的DU部分所服务的小区变更至所述目标IAB宿主下的小区；或者
    向所述第一IAB节点的DU部分发送通过F1应用协议F1AP消息携带的所述第二指示信息；
    其中，所述第二指示信息用于指示可以将所述第一IAB节点的DU部分所服务的小区变更至所述目标IAB宿主下的小区。
  73. 根据权利要求67-72任一项所述的装置，其特征在于，所述装置还包括：
    第六收发模块，用于向所述第一IAB节点的DU部分发送F1应用协议F1AP消息，所述F1应用协议F1AP消息中携带RRC消息容器和第三指示信息，所述RRC消息容器中封装有所述第一IAB节点的下属UE和/或下属IAB节点的RRC消息，以使得所述第一IAB节点在将所述RRC消息成功发送至所述第一IAB节点的下属UE和/或下属IAB节点后，确定所述第一IAB节点的下属UE和/或下属IAB节点接收到所述配置信息；
    其中，所述配置信息为所述第一IAB节点的下属UE和/或下属IAB节点在所述第一IAB节点的DU部分所服务的小区变更为所述目标IAB宿主下的小区后，接入所述目标IAB宿主下的小区需要的RRC配置信息。
  74. 根据权利要求73所述的装置，其特征在于，
    所述第三指示信息为用于指示所述第一IAB节点停止对其下属UE和/或下属IAB节点进行数据传输调度的指示信息；或者
    所述第三指示信息用于指示所述RRC消息容器中携带的RRC消息中，包含所述第一IAB节点的下属UE和/或下属IAB节点接入所述目标IAB宿主下的小区需要的RRC配置信息，其中，所述目标IAB宿主下的小区是所述第一IAB节点的DU部分在其服务的小区变更为所述目标IAB宿主下的小区后所服务的小区。
  75. 一种通信装置，其特征在于，包括至少一个处理器，所述处理器用于执行存储器中存储的指令，以使得如权利要求1-6或权利要求7或权利要求8-9或权利要求10-15任一所述的方法被执行。
  76. 一种IAB节点连接更新装置，其特征在于，包括至少一个处理器，所述处理器用于执行存储器中存储的指令，以使得如权利要求16-29或权利要求30-37任一所述的方法被执行。
  77. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得如权利要求1-6或权利要求7或权利要求8-9或权利要求10-15任一所述的方法被所述计算机执行。
  78. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得如权利要求16-29或权利要求30-37任一所述的方法被所述计算机执行。
  79. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时，
    如权利要求1-6或权利要求7或权利要求8-9或权利要求10-15任一所述的方法被执行。
  80. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时，
    如权利要求16-29或权利要求30-37任一所述的方法被执行。
PCT/CN2022/091157 2021-05-07 2022-05-06 一种iab节点连接更新方法及装置 WO2022233317A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP22798657.7A EP4325937A1 (en) 2021-05-07 2022-05-06 Iab node connection update method and apparatus
KR1020237042215A KR20240005065A (ko) 2021-05-07 2022-05-06 Iab 노드 연결 업데이트 방법 및 장치
US18/502,261 US20240073971A1 (en) 2021-05-07 2023-11-06 Iab node connection update method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110497401.2 2021-05-07
CN202110497401.2A CN115314956A (zh) 2021-05-07 2021-05-07 一种iab节点连接更新方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/502,261 Continuation US20240073971A1 (en) 2021-05-07 2023-11-06 Iab node connection update method and apparatus

Publications (1)

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

Family

ID=83853150

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/091157 WO2022233317A1 (zh) 2021-05-07 2022-05-06 一种iab节点连接更新方法及装置

Country Status (5)

Country Link
US (1) US20240073971A1 (zh)
EP (1) EP4325937A1 (zh)
KR (1) KR20240005065A (zh)
CN (1) CN115314956A (zh)
WO (1) WO2022233317A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024073974A1 (en) * 2023-01-13 2024-04-11 Lenovo (Beijing) Limited Method and apparatus for iab node migration

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020067736A1 (en) * 2018-09-27 2020-04-02 Lg Electronics Inc. Method and apparatus for preventing loss of uplink data in wireless communication system
CN111093286A (zh) * 2019-08-15 2020-05-01 中兴通讯股份有限公司 连接建立方法、装置、集合接入回传节点及存储介质

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020067736A1 (en) * 2018-09-27 2020-04-02 Lg Electronics Inc. Method and apparatus for preventing loss of uplink data in wireless communication system
CN111093286A (zh) * 2019-08-15 2020-05-01 中兴通讯股份有限公司 连接建立方法、装置、集合接入回传节点及存储介质

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "LCID and LCG Extension in IAB Networks", 3GPP DRAFT; R2-1913182, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Chongqing, P. R. of China; 20191014 - 20191018, 3 October 2019 (2019-10-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051791194 *
SAMSUNG: "Discussion on inter-donor topology redundancy for IAB", 3GPP DRAFT; R3-206002, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20201102 - 20201112, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051945593 *
ZTE, SANECHIPS: "Discussion on inter-CU IAB migration handling", 3GPP DRAFT; R3-196689, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Reno, USA; 20191118 - 20191122, 9 November 2019 (2019-11-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051823893 *

Also Published As

Publication number Publication date
US20240073971A1 (en) 2024-02-29
KR20240005065A (ko) 2024-01-11
CN115314956A (zh) 2022-11-08
EP4325937A1 (en) 2024-02-21

Similar Documents

Publication Publication Date Title
US11546811B2 (en) Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
JP7039712B2 (ja) ノードおよび通信方法
US20230111021A1 (en) Communication Method, Apparatus, and System
US8934399B2 (en) Wireless communication system and method for mapping of control messages on the un-interface
US20160044540A1 (en) Double-Connection Implementation Method and Base Station
WO2019233465A1 (zh) 路径时延信息获取方法及相关设备
WO2014032311A1 (zh) 回程链路的信息传输方法及系统、代理设备、接入设备
CN107302773B (zh) 连接的建立方法、装置及系统
US20240073971A1 (en) Iab node connection update method and apparatus
JP2023145706A (ja) 通信制御方法
WO2022151296A1 (zh) 通信方法及装置
US20240032129A1 (en) Communication control method
US20230328607A1 (en) Communication control method
WO2022152079A1 (zh) 一种通信方法及相关设备
US20240073736A1 (en) Communication control method
WO2023131094A1 (zh) 通信方法及通信装置
KR20150073467A (ko) 이중연결 방식을 이용하는 무선통신 시스템에서 상향링크 물리제어채널 구성 방법 및 장치
US20230345346A1 (en) Communication control method
WO2022206317A1 (zh) 一种通信方法以及通信设备
WO2022237357A1 (zh) 通信方法和装置
US20230354139A1 (en) Communication control method
WO2023011621A1 (zh) 一种通信方法及通信装置
US20240031880A1 (en) Integrated access and backhaul donor migration methods and systems
WO2023150974A1 (zh) Iab宿主设备以及传输迁移管理方法
WO2023150975A1 (zh) Iab宿主设备以及传输迁移回退方法

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: 22798657

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022798657

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022798657

Country of ref document: EP

Effective date: 20231114

ENP Entry into the national phase

Ref document number: 20237042215

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1020237042215

Country of ref document: KR

NENP Non-entry into the national phase

Ref country code: DE