WO2022001503A1 - 一种用于iab网络通信的方法及相关设备 - Google Patents

一种用于iab网络通信的方法及相关设备 Download PDF

Info

Publication number
WO2022001503A1
WO2022001503A1 PCT/CN2021/095773 CN2021095773W WO2022001503A1 WO 2022001503 A1 WO2022001503 A1 WO 2022001503A1 CN 2021095773 W CN2021095773 W CN 2021095773W WO 2022001503 A1 WO2022001503 A1 WO 2022001503A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
information
host
target
interface
Prior art date
Application number
PCT/CN2021/095773
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 JP2022581370A priority Critical patent/JP2023531787A/ja
Priority to EP21832950.6A priority patent/EP4171122A4/en
Publication of WO2022001503A1 publication Critical patent/WO2022001503A1/zh
Priority to US18/146,546 priority patent/US20230130178A1/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
    • 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
    • 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
    • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports
    • 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
    • H04W36/0077—Transmission or use of information for re-establishing the radio link of access information of target 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/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/0085—Hand-off measurements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • 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
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • 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/24—Interfaces between hierarchically similar devices between backbone network devices

Definitions

  • the present application relates to the field of communication technologies, and more particularly, to a method and related equipment for IAB network communication.
  • the fifth generation communication introduces the concepts of Central Unit (CU) and Distributed Unit (DU).
  • a base station such as a next-generation base station (generation nodeB, gNB) may be divided into one gNB-CU and at least one gNB-DU connected to the gNB-CU according to the protocol layer.
  • the gNB-DU may include a radio link control (Radio Link Control, RLC) layer function, a MAC layer function and a physical (Physical, PHY) layer function.
  • the CU may include a Packet Data Convergence Protocol (PDCP) layer function, a Service Data Adaptation Protocol (Service Data Adaptation Protocol, SDAP) layer function and a Radio Resource Control (Radio Resource Control, RRC) layer function. Since the gNB-CU and the gNB-DU are connected by wire and communicate through the F1 interface, the prior art does not involve the problem of handover of the gNB-DU.
  • PDCP Packet Data Convergence Protocol
  • SDAP Service Data
  • the IAB node can choose to connect to different IAB hosts, or, switch between different IAB hosts.
  • the present application provides a communication method and related equipment, which can efficiently connect an IAB node to different IAB hosts, or perform efficient handover between different IAB hosts.
  • the present application provides a communication method, the method may include: the source IAB host of the IAB node sends first information to the target IAB host of the IAB node, where the first information includes a request for establishing a first F1 interface information. After receiving the first information, the target IAB host sends second information to the source IAB host, where the second information includes feedback information of the above request information.
  • the first F1 interface refers to a communication interface between the DU of the IAB node and the CU of the target IAB host.
  • exemplary beneficial effects include: through the interaction of the source IAB host and the target IAB host with the relevant information for establishing the first F1 interface, the DU of the IAB node can quickly obtain its configuration information on the target IAB host , so as to achieve efficient handover.
  • the target IAB host can also flexibly indicate the establishment of the first F1 interface through feedback information, thereby improving the efficiency of establishing the first F1 interface.
  • the feedback information sent by the source IAB host to the target IAB host is response information for establishing the first F1 interface.
  • the source IAB host After receiving the response information, the source IAB host sends third information to the IAB node, where the third information includes the above-mentioned response information.
  • exemplary beneficial effects include: the source IAB host can determine that the target IAB host agrees to establish the first F1 interface according to the received response information for establishing the first F1 interface. Further, the IAB node is notified of the response information for establishing the first F1 interface, so that the IAB node can quickly establish the first F1 interface.
  • the feedback information sent by the source IAB host to the target IAB host is the indication information that the first F1 interface fails to be established.
  • exemplary beneficial effects include: the source IAB host can determine that the target IAB host refuses or cannot establish the first F1 interface according to the received indication information that the first F1 interface fails to be established. Further, the source IAB host can determine whether to continue to send the first information to the target IAB host to try to establish the first F1 interface, thereby improving the success rate of establishing the first F1 interface.
  • the above request information for establishing the first F1 interface includes at least one of the following: the DU identifier of the IAB node, the DU name of the IAB node, and the serving cell of the cell served by the IAB node. information, the system information sent by the DU of the IAB node, the radio resource control (radio resource control, RRC) version supported by the DU of the IAB node, and the transport layer address information of the DU of the IAB node.
  • RRC radio resource control
  • exemplary beneficial effects include: by carrying the relevant information for establishing the first F1 interface, implicitly instructing the target IAB host to request the establishment of the first F1 interface, and providing the target IAB host with establishing the first F1 interface Information required for the F1 interface.
  • the above-mentioned response information for establishing the first F1 interface includes at least one of the following: information used to identify the host of the target IAB, activation information of a cell served by the IAB node, and the target IAB
  • the RRC version supported by the CU of the host the transport layer address information of the CU of the target IAB host, and the synchronization signal block transmission configuration (synchronization signal block transmission configuration, STC) of the DU of the IAB node.
  • the information for identifying the target IAB host may include any one of the following: the identification or name of the target IAB host, the CU identification or name of the target IAB host, and the base station identification or name of the target IAB host.
  • exemplary beneficial effects include: the target IAB host can implicitly indicate to the source IAB host that it agrees to establish the first F1 interface through the response information carrying the relevant information for establishing the first F1 interface, and the source IAB The host provides the IAB node with the information required to establish the first F1 interface.
  • the information used to identify the target IAB host can be used as an explicit indication information to indicate to the IAB node that the response information corresponds to the target IAB host, so that the IAB node can determine the received information Whether it is the information for establishing the first F1 interface or the information for updating the configuration of the second F1 interface.
  • the second F1 interface is a communication interface between the DU of the IAB node and the CU of the source IAB host.
  • the above-mentioned first information is carried in the handover request message of the IAB node sent by the source IAB host to the target IAB host.
  • exemplary beneficial effects include: by carrying the first information in the existing message, signaling overhead can be saved.
  • the above-mentioned second information is carried in the handover request response message of the IAB node sent by the target IAB host to the source IAB host.
  • exemplary beneficial effects include: by carrying the second information in the existing message, signaling overhead can be saved.
  • the above-mentioned third information is carried in the RRC reconfiguration message sent by the source IAB host to the IAB node.
  • exemplary beneficial effects include: by carrying the third information in the existing message, signaling overhead can be saved.
  • the above-mentioned third information is carried in the F1 interface application protocol (F1 application protocol, F1AP) message of the second F1 interface sent by the source IAB host to the IAB node, wherein the second The F1 interface is a communication interface between the DU of the IAB node and the CU of the source IAB host.
  • F1 interface application protocol F1 application protocol, F1AP
  • exemplary beneficial effects include: the target IAB host can send the above-mentioned second information in the form of an F1AP container (container) information element to the IAB node through the source IAB host, which can prevent the source IAB host from parsing the first information. second information, thereby increasing the security of the transmission of the second information.
  • changes to existing RRC reconfiguration messages can be avoided.
  • the F1AP message of the second F1 interface when the above-mentioned third information is carried in the F1AP message of the second F1 interface, the F1AP message of the second F1 interface further includes indication information, and the indication information is used to indicate the above-mentioned first F1AP message.
  • the third information corresponds to the target IAB host.
  • exemplary beneficial effects include: enabling the IAB node to determine, according to the indication information, whether the information carried in the F1AP message of the second F1 interface is information for establishing the first F1 interface or for updating the first F1 interface. Two F1 interface configuration information.
  • the source IAB host receives fourth information from the target IAB host, where the fourth information includes IP address information of the target IAB host, and the IP address information is used between the target IAB host and the IAB node.
  • SCTP stream control transmission protocol
  • the source IAB host sends fifth information to the IAB node, where the fifth information includes the IP address information.
  • exemplary beneficial effects include: sending its own IP address information to the IAB node through the target IAB host, so that the IAB node can quickly establish an SCTP coupling with the target IAB host according to the IP address information, and also improve the The success rate of SCTP coupling establishment between target IAB host and IAB node.
  • the IP address information includes at least one of the following: the IP address or IP address type or IP address prefix or the number of IP addresses used for the target IAB host of the first F1 interface, used for The IP address or IP address type or IP address prefix or number of IP addresses of the first F1-C interface or the target IAB host of the F1-C service, used for the first F1-U interface or the target IAB host of the F1-U service IP address or IP address type or IP address prefix or number of IP addresses.
  • the first F1-C interface is a control plane interface of the first F1 interface
  • the first F1-U interface is a user plane interface of the first F1 interface
  • the above-mentioned F1-C service includes passing through the first F1-C interface.
  • the service of the interface, the above-mentioned F1-U service includes the service passing through the first F1-U interface.
  • the above-mentioned fourth information is carried in the handover request response message of the IAB node sent by the target IAB host to the source IAB host.
  • exemplary beneficial effects include: by carrying the second information in the existing message, signaling overhead can be saved.
  • the above fifth information is carried in an RRC reconfiguration message sent by the source IAB host to the IAB node.
  • exemplary beneficial effects include: by carrying the second information in the existing message, signaling overhead can be saved.
  • the source IAB host receives sixth information from the target IAB host, and the sixth information includes the information used to establish the subordinate device context of the IAB node in the IAB node and/or the target IAB host. Request information.
  • the source IAB host sends seventh information to the IAB node, where the seventh information includes the request information.
  • the source IAB host receives the response information from the IAB node for establishing the subordinate device context of the IAB node in the IAB node and/or the target IAB host.
  • the subordinate equipment of the IAB node includes an IAB sub-node of the IAB node or a terminal device accessing the IAB node.
  • the source IAB host After receiving the response information, the source IAB host sends the response information to the target IAB host.
  • exemplary beneficial effects include: through the source IAB host and the target IAB host interacting with the relevant information about the context of the subordinate device of the IAB node, the target IAB host can obtain the context of the subordinate device of the IAB node faster, thereby realizing efficient switching. .
  • the above-mentioned request information for establishing the subordinate device context of the IAB node in the IAB node and/or the target IAB host includes at least one of the following: an F1 interface application corresponding to the subordinate device of the IAB node.
  • Protocol identifier the establishment list of secondary cells (secondary cell, Scell) served by the IAB node, the establishment list of signaling radio bearers (signaling radio bearer, SRB) between the IAB node and the subordinate equipment of the IAB node, the IAB node and the The data radio bearer (DRB) establishment list between the subordinate devices of the IAB node and the backhaul RLC channel (BH RLC CH) establishment list between the IAB node and the subordinate devices of the IAB node , the user plane data routing rules of the IAB node, and the user plane bearer mapping rules of the IAB node.
  • DRB data radio bearer
  • exemplary beneficial effects include: the target IAB host can hide information from the source IAB host to the source IAB host through a request message carrying relevant information for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host.
  • the formula indicates a request to establish the IAB node subordinate device context in the IAB node and/or the target IAB host, and provides the IAB node through the source IAB host with the IAB node and/or the target IAB host. required information.
  • the above-mentioned response information for establishing the subordinate device context of the IAB node in the IAB node and/or the target IAB host includes at least one of the following: the IAB node is the subordinate device of the IAB node.
  • the assigned cell radio network temporary identifier (C-RNTI), the DRB list between the IAB node and the subordinate devices of the IAB node that has been successfully established or failed to establish, the IAB node that has been established successfully or failed to establish and The SRB list between the subordinate devices of the IAB node, the BH RLC CH list between the IAB node and the subordinate devices of the IAB node that has been successfully established or failed to establish, and the Scell list served by the IAB node that has been successfully established or failed to establish.
  • C-RNTI The assigned cell radio network temporary identifier
  • exemplary beneficial effects include: the target host node can be made to obtain the relevant information of establishing the subordinate device context of the IAB node in the IAB node and/or the target IAB host, and the IAB node and/or the target IAB in advance.
  • the subordinate device context of the IAB node is established in the host.
  • the above seventh information is carried in an RRC reconfiguration message sent by the source IAB host to the IAB node.
  • exemplary beneficial effects include: by carrying the second information in the existing message, signaling overhead can be saved.
  • the above seventh information and the above third information are carried in the same message.
  • exemplary beneficial effects include: by combining the third information and the seventh information, signaling overhead can be saved.
  • the third information and the seventh information together the data communication between the IAB node and the target IAB host can be established more quickly, thereby improving the communication efficiency of the IAB network.
  • the source IAB host receives the sixth information from the target IAB host, specifically, the source IAB host receives the sixth information from the target IAB host through the core network device.
  • exemplary beneficial effects include: enabling the source IAB host and the target IAB host to exchange the sixth information through the core network device, ensuring the establishment of the subordinate device context of the IAB node between the IAB node and the target IAB host .
  • the source IAB host sends the response information for establishing the subordinate device context of the IAB node in the IAB node and/or the target IAB host to the target IAB host, specifically, through the core
  • the network device sends the response information for establishing the subordinate device context of the IAB node in the IAB node and/or the target IAB host to the target IAB host.
  • exemplary beneficial effects include: enabling the source IAB host and the target IAB host to exchange the response information through the core network device, ensuring the establishment of the subordinate device context of the IAB node between the IAB node and the target IAB host.
  • the source IAB host receives the fourth information from the target IAB host, specifically, the source IAB host receives the fourth information from the target IAB host through the core network device.
  • exemplary beneficial effects include: enabling the source IAB host and the target IAB host to exchange the fourth information through the core network device, ensuring the rapid establishment of the initial SCTP coupling between the IAB node and the target IAB host.
  • the source IAB host sends the first information to the target IAB host of the IAB node. Specifically, the source IAB host sends the first information to the target IAB host of the IAB node through the core network device.
  • exemplary beneficial effects include: enabling the source IAB host and the target IAB host to exchange the first information through the core network device, ensuring the establishment of the first FI interface.
  • the source IAB host receives the second information from the target IAB host, specifically, the source IAB host receives the second information from the target IAB host through a core network device.
  • exemplary beneficial effects include: enabling the source IAB host and the target IAB host to exchange the second information through the core network device, ensuring that the IAB node can obtain feedback information from the target IAB host for the first information.
  • the present application provides a communication method, which may include: an IAB node receiving IP address information of the target IAB host from the target IAB host.
  • the IP address information is used to establish the initial SCTP association between the target IAB host and the IAB node.
  • exemplary beneficial effects include: sending its own IP address information to the IAB node through the target IAB host, so that the IAB node can quickly establish an SCTP coupling with the target IAB host according to the IP address information, and also improve the The success rate of SCTP coupling establishment between target IAB host and IAB node.
  • the IP address information includes at least one of the following: the IP address or IP address type or IP address prefix or the number of IP addresses used for the target IAB host of the first F1 interface, used for The IP address or IP address type or IP address prefix or number of IP addresses of the first F1-C interface or the target IAB host of the F1-C service, used for the first F1-U interface or the target IAB host of the F1-U service IP address or IP address type or IP address prefix or number of IP addresses.
  • the first F1 interface refers to the communication interface between the DU of the IAB node and the CU of the target IAB host
  • the first F1-C interface is the control plane interface of the first F1 interface
  • the first F1-C interface is the control plane interface of the first F1 interface.
  • the U interface is the user plane interface of the first F1 interface
  • the above-mentioned F1-C service includes the service through the first F1-C interface
  • the above-mentioned F1-U service includes the service through the first F1-U interface.
  • the IP address information of the target IAB host is carried in the handover request response message of the IAB node sent by the target IAB host to the source IAB host.
  • exemplary beneficial effects include: by carrying the IP address information of the target IAB host in the existing message, signaling overhead can be saved.
  • the IP address information of the target IAB host is carried in the RRC reconfiguration message sent by the source IAB host to the IAB node.
  • exemplary beneficial effects include: by carrying the IP address information of the target IAB host in the existing message, signaling overhead can be saved.
  • the source IAB host receives the IP address information of the target IAB host from the target IAB host. Specifically, the source IAB host receives the IP address information of the target IAB host from the target IAB host through the core network device. IP address information.
  • exemplary beneficial effects include: enabling the source IAB host and the target IAB host to exchange the IP address information of the target IAB host through the core network device, ensuring the initial SCTP coupling between the IAB node and the target IAB host. Build quickly.
  • the present application provides a communication method, the method may include: the target IAB host of the IAB node receives first information from the source IAB host of the IAB node, where the first information includes a method for establishing a first F1 interface request information.
  • the target IAB host sends second information to the source IAB host, where the second information includes feedback information of the request information.
  • the first F1 interface is a communication interface between the distributed unit of the IAB node and the centralized unit of the target IAB host.
  • the target IAB host sends the IP address information of the first F1 interface to the IAB through the source IAB host, and the IP address information of the first F1 interface is used for the target IAB host and the IAB The establishment of the initial flow control transport protocol coupling between nodes.
  • the target IAB host sends the IAB node through the source IAB host request information for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host. Subsequently, the target IAB host receives, through the source IAB host, response information from the IAB node for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host.
  • the subordinate equipment of the IAB node includes an IAB sub-node of the IAB node or a terminal device accessing the IAB node.
  • the target IAB host establishes an initial SCTP coupling with the IAB node according to the IP address, where the IP address is the IP address included in the IP address information carried in the fourth information.
  • the present application provides a communication method, which may include: an IAB node receiving third information from a source IAB host, where the third information includes response information for establishing the first F1 interface.
  • the first F1 interface is a communication interface between the distributed unit of the IAB node and the centralized unit of the target IAB host.
  • the response information for establishing the first F1 interface is carried in the application protocol message of the second F1 interface sent by the source IAB host to the IAB node, and the second F1 interface
  • the application protocol message includes indication information, and the indication information is used to indicate that the information included in the application protocol message of the second F1 interface is the information corresponding to the target IAB host or the information for establishing the first F1 interface, the IAB
  • the node determines that the information included in the application protocol message of the second F1 interface is information corresponding to the target IAB host or information used to establish the first F1 interface.
  • the second F1 interface is a communication interface between the DU of the IAB node and the CU of the source IAB host.
  • the IAB node receives fifth information from the source IAB host, where the fifth information includes IP address information of the first F1 interface, and the IP address information of the first F1 interface is used for the target The establishment of the initial flow control transport protocol coupling between the IAB host and the IAB node.
  • the IAB node establishes an initial SCTP coupling with the target IAB host according to the IP address, where the IP address is obtained according to the fifth information.
  • the IAB node receives seventh information from the source IAB host, where the seventh information includes a request for establishing the IAB node subordinate device context in the IAB node and/or the target IAB host information. Subsequently, the IAB node sends, through the source IAB host, to the target IAB host, response information for establishing the subordinate device context of the IAB node in the IAB node and/or the target IAB host.
  • the subordinate equipment of the IAB node includes an IAB sub-node of the IAB node or a terminal device accessing the IAB node.
  • the present application provides a communication device including a module for performing any one of the methods of the first to fourth aspects and any design thereof.
  • the present application provides a communication device, comprising a processor and a memory, the processor is coupled to the memory, and the processor is used to implement any one of the methods of the first to fourth aspects and any design thereof method.
  • the present application provides a communication device, comprising at least one processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices other than the communication device and transmit to the processor or transfer signals from the processor The signal of the processor is sent to other communication devices other than the communication device, and the processor is used to implement any one of the methods of the first aspect to the fourth aspect and any one of its designs through a logic circuit or executing code instructions.
  • the apparatus may be an IAB node or a source IAB host or a target IAB host or a chip or an integrated device in any of the methods of the first to fourth aspects and any design thereof. circuit.
  • the communication device may further include at least one memory, and the memory stores the related program instructions.
  • the present application provides a communication device having a function or operation to implement any one of the methods of the first aspect to the fourth aspect and any of the methods in any design thereof, and the function or operation It can be realized by hardware, or can be realized by executing corresponding software by hardware.
  • the hardware or software includes one or more units (modules) corresponding to the above functions or operations, such as a transceiver unit and a processing unit.
  • the present application provides a computer-readable storage medium, where relevant program instructions are stored in the computer-readable storage medium, and when the involved program instructions are executed, the communication device implements the first aspect to the first The method of the four aspects and any of the methods in any design thereof.
  • the present application provides a computer program product, the computer program product includes related program instructions, when the related program instructions are executed, to implement the methods of the first to fourth aspects and any of the designs thereof any method.
  • the present application further provides a chip for implementing any one of the methods of the first aspect to the fourth aspect and any of the designs thereof.
  • the present application provides a communication system, which includes at least one communication device according to the fifth aspect to the eighth aspect and any designs thereof.
  • FIG. 1A is a schematic diagram of a possible communication system of the present application.
  • FIG. 1B is a schematic diagram of an IAB host provided in an embodiment of the present application.
  • 1C is a schematic diagram of a control plane protocol stack in an IAB network provided by an embodiment of the present application.
  • 1D is a schematic diagram of a user plane protocol stack in an IAB network provided by an embodiment of the present application.
  • FIG. 1E is a schematic diagram of an IAB node handover provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of an apparatus provided by an embodiment of the present application.
  • the fifth-generation mobile communication has put forward more stringent requirements in all aspects of the 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 small stations need to be densely deployed.
  • the integrated access and backhaul (IAB) technology provides an idea for solving the above two problems: the access link and the backhaul link both use the wireless transmission scheme to avoid Fiber deployment.
  • the relay node RN RN, Relay Node
  • IAB node IAB node
  • the wireless backhaul link is connected to the donor node (IAB donor) or the donor base station (DgNB, Donor gNodeB) for transmission.
  • IAB donor donor node
  • DgNB donor base station
  • Donor gNodeB donor base station
  • Using an IAB node can share antennas for access and backhaul, reducing the number of antennas at the base station.
  • the user equipment in FIG. 1A may be an access terminal equipment, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal equipment, a mobile equipment, a user terminal equipment, a wireless terminal equipment, a user agent, or a user equipment, etc. .
  • It can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication capable Handheld devices, computing devices, other processing devices connected to wireless modems, in-vehicle devices, wearable devices (such as smart watches, smart bracelets, etc.), smart furniture or home appliances, terminal devices in 5G networks, future evolution Terminal equipment in public land mobile network (PLMN), or vehicle equipment in vehicle to everything (V2X), customer premises equipment (CPE), etc.
  • PLMN public land mobile network
  • V2X vehicle equipment in vehicle to everything
  • CPE customer premises equipment
  • the IAB node in Figure 1A may be composed of a mobile terminal (MT) and a distributed unit (DU), wherein, when the IAB node faces its parent node, it can be regarded as a terminal device, that is, an MT When an IAB node faces its subordinate device (the subordinate device may be another IAB sub-node, or a normal UE), it can be regarded as a network device, that is, it acts as a DU.
  • MT mobile terminal
  • DU distributed unit
  • the IAB donor (IAB donor) in FIG. 1A may be a donor base station, and the IAB donor may be referred to as a DgNB (ie, a donor gNodeB) for short in a 5G network.
  • the IAB host can be a complete entity, or can be a centralized unit (CU) (referred to as Donor-CU or gNB-CU in this application) and a distributed unit (DU) (in this application) It exists in the form of separation of Donor-DU or gNB-DU for short.
  • the IAB host can be a gNB located in a 5G radio access network (5G RAN).
  • the IAB host may be composed of gNB-CU and gNB-DU.
  • the gNB-CU and the gNB-DU are connected through an F1 interface, and the F1 interface may further include a control plane interface (F1-C) and a user plane interface (F1-U).
  • the CU and the core network are connected through a next generation (NG) interface.
  • the gNB-CU or Donor-CU may also be a user plane (UP) (referred to as CU-UP in this application) and a control plane (CP) (referred to as CU-CP in this application)
  • UP user plane
  • CP control plane
  • CU-CP control plane
  • One gNB-CU may include one gNB-CU-CP and at least one gNB-CU-UP.
  • one Donor-CU may include one Donor-CU-CP and at least one Donor-CU-UP.
  • the network management device in FIG. 1A may be an operation, management and maintenance network element (operation, administration and maintenance, OAM).
  • the network management equipment may include a network element management system (element management system, EMS), and a network management system (network management system, NMS).
  • the network management device may be a functional network element located in a next generation core network (Next Generation Core, NGC) or a 5G core network (5G core, 5GC).
  • NGC next generation core network
  • 5G core 5G core
  • the network management device may also be a functional network element deployed in the backbone network behind the 5GC, or the network management device may also be deployed in other locations, and this application does not limit the specific deployment location of the network management device.
  • the IAB node is connected to the core network via the IAB host.
  • the IAB node is connected to the 5GC via the IAB host.
  • the IAB node Under the dual connectivity (DC) or multi-connectivity (MC) 5G architecture (for example: non-standalone (NSA), or NR-NR DC scenarios, etc.), on the main path , the IAB node can be connected to an evolved packet core (EPC) via an evolved base station (evolved NodeB, eNB), or can be connected to a 5G core network via an IAB host.
  • EPC evolved packet core
  • eNB evolved NodeB
  • the IAB network supports the networking of multi-hop IAB nodes and multi-connection IAB nodes. Therefore, there may be multiple transmission paths between the terminal and the IAB host.
  • On a path there is a definite hierarchical relationship between the IAB nodes, and between the IAB nodes and the IAB hosts connected to the IAB nodes, and each IAB node regards the node that provides the backhaul service as a parent node. Accordingly, each IAB node can be regarded as a child node of its parent node.
  • the parent node of IAB node 1 is the IAB host
  • 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 node 4
  • the parent node of IAB node 5 is IAB node 2.
  • the uplink data packets of the terminal can be transmitted to the IAB host through one or more IAB nodes, and then sent by the IAB host to the mobile gateway device (such as the user plane function (UPF) network element in the 5G network), and the downlink data
  • the mobile gateway device such as the user plane function (UPF) network element in the 5G network
  • terminal 1 and IAB host There are two available paths for data packet transmission between terminal 1 and IAB host, namely: terminal 1 ⁇ IAB node 4 ⁇ IAB node 3 ⁇ IAB node 1 ⁇ IAB host, terminal 1 ⁇ IAB node 4 ⁇ IAB node 2 ⁇ IAB node 1 ⁇ IAB host.
  • terminal 2 ⁇ IAB node 4 ⁇ IAB node 3 ⁇ IAB node 1 ⁇ IAB host terminal 2 ⁇ IAB node 4 ⁇ IAB node 2 ⁇ IAB Node 1 ⁇ IAB host, terminal 2 ⁇ IAB node 5 ⁇ IAB node 2 ⁇ IAB node 1 ⁇ IAB host.
  • the intermediate IAB nodes on the upstream path from the IAB node to the IAB host can be referred to as the upstream nodes of the IAB node.
  • the IAB node 1 and the IAB node 2 in FIG. 1A can be referred to as the upstream IAB nodes of the IAB node 5 .
  • the subordinate devices of the IAB node may include devices that directly access the IAB node, such as a child node of the IAB node or a UE that accesses the IAB node.
  • IAB node 1A can be referred to as subordinate devices of IAB node 1
  • IAB node 5 can be referred to as subordinate devices of IAB node 2
  • terminal 1 and terminal 2 can be referred to as subordinate devices of IAB node 4.
  • the device, the terminal 1 may be referred to as a subordinate device of the IAB node 4 .
  • a transmission path between a terminal and an IAB host may include one or more IAB nodes.
  • Each IAB node needs to maintain the wireless backhaul link facing the parent node, and also needs to maintain the wireless link with the child nodes.
  • a wireless access link is formed between the IAB node and a sub-node (ie, a terminal).
  • an IAB node is a node that provides backhaul services for other IAB nodes, there is a wireless backhaul link between the IAB node and child nodes (ie, other IAB nodes).
  • terminal 1 accesses IAB node 4 through a wireless
  • the backhaul link is connected to the IAB node 3
  • the IAB node 3 is connected to the IAB node 1 through the wireless backhaul link
  • the IAB node 1 is connected to the IAB host through the wireless backhaul link.
  • the above IAB networking scenario is just an example.
  • the IAB host and the IAB nodes under another IAB host are composed Dual connections are terminal services, etc., which will not be listed here.
  • the access IAB node in the embodiments of the present application refers to the IAB node accessed by the terminal, and the intermediate IAB node refers to the IAB node that provides wireless backhaul services for the IAB node (eg, the access IAB node or other intermediate IAB nodes).
  • IAB node 4 is the access IAB node
  • IAB node 3 and IAB node 1 are intermediate IAB nodes.
  • an IAB node is an access IAB node for a terminal that accesses the IAB node.
  • an IAB node is specifically an access IAB node.
  • the node or the intermediate IAB node is not fixed and needs to be determined according to the specific application scenario.
  • FIG. 1C and FIG. 1D are respectively a schematic diagram of a control plane protocol stack and a schematic diagram of a user plane protocol stack in an IAB network provided by an embodiment of the present application, which will be described below with reference to FIGS. 1C and 1D .
  • a Uu interface is established between the terminal 1 and the IAB2-DU, and the peer-to-peer protocol layers include the RLC layer, the MAC layer, and the PHY layer.
  • the IAB2-DU and the IAB donor CU1 establish an F1-C interface, and the peer-to-peer protocol layers include the F1 application protocol (F1AP) layer and the stream control transmission protocol (SCTP) layer.
  • the IAB donor DU 1 and the IAB donor CU 1 are connected by wire, and the peer-to-peer protocol layers include the Internet Protocol (IP) layer, L2 and L1.
  • IP Internet Protocol
  • BL is established between IAB node 2 and IAB node 3, between IAB node 3 and IAB node 1, and between IAB node 1 and IAB donor DU 1, and the peer-to-peer protocol layer includes the backhaul adaptation protocol (Bakhaul Adaptation). Protocol, BAP) layer, RLC layer, MAC layer and PHY layer.
  • BAP backhaul adaptation protocol
  • RLC backhaul adaptation protocol
  • MAC media access control
  • PHY PHY
  • a peer-to-peer RRC layer and a PDCP layer are established between the terminal 1 and the IAB donor CU 1, and a peer-to-peer IP layer is established between the IAB2-DU and the IAB donor DU 1.
  • control plane protocol stack of the IAB network is compared with the control plane protocol stack of the single air interface.
  • the DU connected to the IAB node realizes the function of the gNB-DU of the single air interface (that is, establishing a peer RLC layer, MAC layer with the terminal). and the functions of the PHY layer, as well as the functions of the F1AP layer and SCTP layer that establish peering with the CU).
  • the DU connected to the IAB node in the IAB network realizes the function of the single air interface gNB-DU; the IAB donor CU realizes the function of the single air interface gNB-CU.
  • RRC messages are encapsulated and transmitted in F1AP messages between the access IAB node and the IAB donor CU.
  • the terminal 1 encapsulates the RRC message in the PDCP protocol data unit (protocol data unit, PDU), and sends it to the IAB2-DU after being processed by the RLC layer, the MAC layer and the PHY layer in sequence.
  • PDU protocol data unit
  • IAB2-DU obtains PDCP PDU after processing by PHY layer, MAC layer and RLC layer in turn, encapsulates PDCP PDU in F1AP message, and obtains IP packet after processing by SCTP layer and IP layer in sequence
  • IAB2-MT separates IP packet It is sent to IAB3-DU after being processed by BAP layer, RLC layer, MAC layer and PHY layer.
  • the IAB3-DU is processed by the PHY layer, the MAC layer, the RLC layer and the BAP layer to obtain an IP packet, and then the IAB3-MT adopts an operation similar to the IAB2-MT to send the IP packet to the IAB1-DU.
  • IAB1 -MT sends the IP packet to IAB donor DU 1.
  • the IP packet is sent to the IAB donor CU 1, and the IAB donor CU 1 sequentially processes the IP packet through the SCTP layer, the F1AP layer and the PDCP layer to obtain the RRC message.
  • the downstream direction is similar and will not be described here.
  • a Uu interface is established between the terminal 1 and the IAB2-DU, and the peer-to-peer protocol layers include an RLC layer, a MAC layer, and a PHY layer.
  • IAB2-DU and IAB donor CU 1 establish an F1-U interface, and the peer-to-peer protocol layers include the GPRS tunneling protocol for the user plane (GTP-U) layer, the user datagram protocol (user datagram protocol, UDP) layer.
  • GTP-U GPRS tunneling protocol for the user plane
  • UDP user datagram protocol
  • the IAB donor DU 1 and the IAB donor CU 1 are connected through a wired connection, and the equivalent protocol layers include the IP layer, L2 and L1.
  • BL is established between IAB node 2 and IAB node 3, between IAB node 3 and IAB node 1, and between IAB node 1 and IAB donor DU 1, and the peer-to-peer protocol layers include BAP layer, RLC layer, and MAC layer. and the PHY layer.
  • a peer-to-peer SDAP layer and a PDCP layer are established between the terminal 1 and the IAB donor CU 1, and a peer-to-peer IP layer is established between the IAB2-DU and the IAB donor DU 1.
  • the user plane protocol stack of the IAB network is compared with the user plane protocol stack of the single air interface.
  • the DU of the IAB access node realizes the function of the single air interface gNB-DU; the IAB donor CU realizes the function of the single air interface gNB-CU.
  • PDCP packets are encapsulated and transmitted in the GTP-U tunnel between the access IAB node and the IAB donor CU.
  • the GTP-U tunnel is established on the F1-U interface.
  • FIG. 1C and FIG. 1D describe the protocol stack in the IAB scenario shown in FIG. 1A as an example.
  • an IAB node may have one or more roles, and the IAB node may have protocol stacks of the one or more roles; or, the IAB node may have a set of protocol stacks, and the protocol stack may Different roles are processed using the protocol layers corresponding to different roles.
  • the following is an example of the protocol stack in which the IAB node has the one or more roles:
  • the MT of the IAB node has the protocol stack of a common terminal, such as the protocol stack of the terminal 1 in FIG. 1C and FIG. 1D , that is, the RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer.
  • the RRC message of the IAB node is encapsulated in the F1AP message between the parent node of the IAB node and the IAB donor CU; on the user plane, the PDCP data packet of the IAB node is encapsulated between the parent node of the IAB node and the IAB donor CU. transmitted in the GTP-U tunnel.
  • the IAB node can still act as a common terminal, for example, transmit its own uplink and/or downlink data packets (such as OAM data packets) with the IAB donor, and perform measurement through the RRC layer etc.
  • uplink and/or downlink data packets such as OAM data packets
  • the IAB node After the IAB node accesses the IAB network, the IAB node can provide access services for the terminal, so as to play the role of an access IAB node. At this time, the IAB node has the protocol stack for accessing the IAB node, such as FIG. 1C and FIG. The protocol stack of IAB node 2 in 1D.
  • the interface of the IAB node facing its parent node can have two sets of protocol stacks, one set is the protocol stack of the common terminal, and the other set is the protocol stack that provides backhaul services for the terminal (ie: access The protocol stack of the IAB node).
  • the same protocol layer of the two sets of protocol stacks may be shared, for example, the two sets of protocol stacks correspond to the same RLC layer, MAC layer, PHY layer, or BAP layer.
  • the IAB node After the IAB node accesses the IAB network, the IAB node can play the role of an intermediate IAB node. At this time, the IAB node has the protocol stack of the intermediate IAB node, such as IAB node 3 or IAB node 1 in Figure 1C and Figure 1D the protocol stack.
  • the interface of the IAB node facing its parent node can have two sets of protocol stacks, one set is the protocol stack of the common terminal, and the other set is the protocol stack that provides the return service for the child IAB node (ie: The protocol stack of the intermediate IAB node).
  • the same protocol layer of the two sets of protocol stacks may be shared, for example, the two sets of protocol stacks correspond to the same RLC layer, MAC layer, PHY layer, or BAP layer.
  • the IAB node can assume the roles of the access IAB node and the intermediate IAB node at the same time.
  • the IAB node can be the access IAB node for some terminals, and the intermediate IAB node for other terminals.
  • the IAB node There may be three sets of protocol stacks, one set is the protocol stack of the above-mentioned common terminal, the other set is the protocol stack of the access IAB node, and the other set is the protocol stack of the intermediate IAB node.
  • the same protocol layer of the three sets of protocol stacks may be shared, for example, the three sets of protocol stacks all correspond to the same RLC layer, MAC layer, PHY layer, or BAP layer.
  • Figures 1C and 1D take the IAB network as an example.
  • the contents of Figures 1C and 1D are also applicable to other types of relay networks other than the IAB network.
  • the control plane protocol stack architecture of the relay network can be Referring to FIG. 1C
  • the user plane protocol stack architecture of the relay network may refer to FIG. 1D .
  • the IAB nodes in Figure 1C and Figure 1D can be replaced by relays, for example, IAB node 2 can be replaced by relay node 2, IAB node 3 can be replaced by relay node 3, and IAB node 1 can be replaced by relay nodes 1.
  • the IAB donor 1 can be replaced by the host node 1.
  • the host node has CU and DU protocol stacks. The rest of the content is the same as that described in Figure 1C and Figure 1D.
  • the IAB node in the IAB network (the IAB node 3 in FIG. 1E ) can be switched.
  • the IAB node switches from the source parent node (IAB node 1 in Figure 1E) to the target parent node (IAB node 2 in Figure 1E), and changes the connected IAB host, that is, from the source IAB host (as in Figure 1E ) IAB donor 1) switching to the target IAB host (as shown in IAB donor 2 in Figure 1E), can be referred to as switching across IAB hosts, or switching across donor CUs (inter-donor CU migrating).
  • the IAB node switches from the source parent node (IAB node 1 in Figure 1E) to the target parent node (IAB node 2 in Figure 1E), but does not change the IAB host, this switching can be called switching inside the IAB host, Or switching inside the donor CU (intra-donor CU migrating).
  • the child nodes of the IAB node (as shown in IAB node 4 in FIG. 1E ) can follow the IAB node to switch, that is, also switch from the source IAB host to the target IAB host.
  • the method provided by the embodiment of the present application is applicable to the handover of the IAB node, and is also applicable to the scenario in which the child node of the IAB node follows the IAB node for handover.
  • the handover method of the child node of the IAB node can also refer to the handover method of the IAB node provided in this application,
  • the MT of the IAB node may be abbreviated as IAB-MT
  • the DU of the IAB node may be abbreviated as IAB-DU
  • the CU of the IAB host may be abbreviated as Donor-CU
  • the DU of the IAB host may be abbreviated as Donor-DU.
  • the IAB host connected to the IAB node may be referred to as the IAB host of the IAB node for short.
  • the IAB node may directly access the IAB host, or the IAB node may be connected to the IAB host through other IAB nodes.
  • the IAB host connected to the IAB node may be referred to as the IAB host of the IAB node for short.
  • a cell served by an IAB-hosted IAB node may include a cell served by an IAB-hosted DU or a cell deployed by an IAB-hosted DU.
  • the IAB node may directly access the IAB host, or the IAB node may be connected to the IAB host through other IAB nodes.
  • FIG. 2 shows a communication method according to an embodiment of the present application, and the communication method 200 includes:
  • the IAB node sends a measurement report to the source IAB host.
  • the measurement report may be used to report the signal quality measurement result of the neighboring cell.
  • the measurement report can be carried in an RRC message, and when the RRC message is transmitted between the source parent node and the source IAB host, it can be encapsulated in an F1AP message between the source parent node and the source IAB host.
  • S202 The source IAB host sends a handover request message of the IAB node to the target IAB host.
  • the source IAB host determines the target parent node to be handed over by the IAB node (or IAB-MT) based on the measurement report, and sends a handover request to the target host node.
  • the handover request message of the IAB node is used to request the target IAB host to switch the IAB node (or IAB-MT) from the source IAB host to the target IAB host.
  • the handover request message of the IAB node is used to request the target IAB host to handover the IAB node (or IAB-MT) from the source parent node to the target parent node.
  • S203 The target IAB host sends a handover request response message of the IAB node to the source IAB host.
  • the handover request response message of the IAB node is used to indicate to the source IAB host that the target IAB host agrees to the access of the IAB node.
  • the handover request response may include part or all of the RRC reconfiguration message sent by the source IAB host to the IAB node (or IAB-MT). Some configuration required when accessing the process.
  • the source IAB host sends an RRC reconfiguration message to the IAB node (or IAB-MT) through the source parent node.
  • the RRC reconfiguration message includes some configurations required when the IAB node (or the IAB-MT) performs the random access procedure with the target parent node.
  • the RRC reconfiguration message is transmitted between the source parent node and the source IAB host, it can be encapsulated in an F1AP message between the source parent node and the source IAB host.
  • S205 A random access procedure is performed between the IAB node (or IAB-MT) and the target parent node.
  • an RRC connection can be established between the IAB node (or IAB-MT) and the target IAB host through the target parent node.
  • the IAB node (or IAB-MT) sends an RRC reconfiguration complete message to the target IAB host through the target parent node.
  • the RRC reconfiguration complete message is used to indicate to the target host node that the RRC connection establishment is complete.
  • the RRC reconfiguration complete message when transmitted between the target parent node and the target host node, it can be encapsulated in the F1AP message between the target parent node and the target host node.
  • the IAB node may establish an initial SCTP association with the target IAB host by using multiple IP addresses configured by the network management device. For example, the IAB node may select one IP address from multiple IP addresses to establish an initial SCTP association with the target IAB host. When the IAB node fails to establish the initial SCTP association with the target IAB host by using one of the IP addresses, the IAB node can re-select an IP address and continue to establish the initial SCTP association with the target IAB host.
  • the IAB node can send an F1 interface establishment request to the target IAB host through the target parent node.
  • the F1 interface establishment request carries relevant information for establishing the first F1 interface.
  • the F1 interface establishment request is used to request the target IAB host to establish the first F1 interface.
  • the first F1 interface is a communication interface between the DU of the IAB node and the CU of the target IAB host.
  • 3GPP 3rd generation partnership project
  • TS technical standard
  • S209 The target IAB host sends an F1 interface establishment response message to the IAB node.
  • the target IAB host can send the F1 interface establishment response to the IAB node through the target parent node.
  • the F1 interface establishment response carries relevant information for establishing the first F1 interface.
  • the F1 interface establishment response is used to indicate to the IAB node that the target IAB host agrees to establish the first F1 interface.
  • S210 The target IAB host sends configuration update information to the IAB node.
  • the target IAB host can also send the configuration update information of the IAB-DU to the IAB node, and the IAB-DU configuration update information can be carried in the target IAB host ( Or the target Donor CU) sends the CU configuration update (GNB-CU CONFIGURATION UPDATE) message to the IAB node.
  • the target IAB host Or the target Donor CU sends the CU configuration update (GNB-CU CONFIGURATION UPDATE) message to the IAB node.
  • FIG. 3 shows a communication method according to an embodiment of the present application, and the communication method 300 includes:
  • S301 The source IAB host of the IAB node sends first information to the target IAB host of the IAB node.
  • the IAB node may be directly connected to the source IAB host, or the IAB node may be connected to the source IAB host through one or more upstream IAB nodes.
  • the target IAB host may be the source IAB host determined according to the measurement report from the IAB node. Likewise, after the IAB node switches to the target IAB host, the IAB node may directly access the target IAB host, or the IAB node may be connected to the target IAB host through one or more upstream IAB nodes.
  • the IAB node may be a switching IAB node that needs to switch the parent node, that is, the source IAB host determines that the switching IAB node needs to be switched from the source parent node to the target parent node.
  • the IAB node may also be a child node of the handover IAB node, that is, the IAB node may be handed over together with the handover IAB node.
  • the IAB node may be IAB node 3 in the left diagram of FIG. 1E, or may be IAB node 4 in the left diagram of FIG. 1E.
  • the source Donor-CU of the IAB node may send the first information to the target Donor-CU of the IAB node.
  • the first information may be referred to as an F1 handover request.
  • the first information may be exchanged between the source IAB host and the target IAB host through an X2 interface or an Xn interface.
  • the X2 interface generally refers to the interface between the eNB and the eNB
  • the Xn interface generally refers to the interface between the gNB and the gNB.
  • the first information may be carried in an X2 interface application protocol (X2 application protocol, X2AP) message or an Xn interface application protocol (Xn application protocol, XnAP) message between the source IAB host and the target IAB host.
  • the first information may be carried in the handover request message of the IAB node sent by the source IAB host to the target IAB host (for the handover request message of the IAB node, please refer to the explanation in S202).
  • the first information may be encapsulated into an F1AP information element container (container), and then carried in the X2AP message or the XnAP message.
  • F1AP information element container container
  • the source IAB host and the target IAB host may transfer and exchange the first information through the S1 interface or the Ng interface with the core network device.
  • the S1 interface generally refers to the interface between the eNB and the EPC
  • the Ng interface generally refers to the interface between the gNB and the NGC.
  • the source IAB host sends the first information to the core network device through the S1 interface or the Ng interface, and after receiving the first information, the core network device forwards the first information to the target IAB host through the S1 interface or the Ng interface.
  • the core network device may be a mobility management entity (mobility management entity, MME) or an access management function (access management function, AMF).
  • the first information may be carried in a handover request message (handover required) sent by the source IAB host to the core network device and in a handover request message (handover request) sent by the core network device to the target IAB host.
  • a handover request message (handover required) sent by the source IAB host to the core network device
  • a handover request message (handover request) sent by the core network device to the target IAB host.
  • the first information includes request information for establishing the first F1 interface.
  • the first information may be an F1 interface setup request (F1SETUP REQUEST).
  • the first F1 interface may refer to a communication interface between the IAB-DU and the target Donor-CU.
  • the request information for establishing the first F1 interface may include all or part of the content of the F1 establishment request message (the F1 establishment request message may refer to the explanation in S208).
  • the request information for establishing the first F1 interface may include at least one of the following information: IAB-DU identifier (ID), IAB-DU name (name), serving cell information (served) of the cell served by the IAB node cell information of a cell served by the IAB node), the system information configuration sent by the DU of the IAB node (such as synchronization signal and PBCH block (synchronization signal and physical broadcast channel block, SSB) related configuration), the DU of the IAB node The supported RRC version and the transport layer address information of the DU of the IAB node.
  • ID IAB-DU identifier
  • name name
  • serving cell information serving cell information of the cell served by the IAB node cell information of a cell served by the IAB node
  • the system information configuration sent by the DU of the IAB node such as synchronization signal and PBCH block (synchronization signal and physical broadcast channel block, SSB) related configuration
  • the DU of the IAB node The supported RRC version and the transport
  • the SSB-related configuration may include SSB frequency, SSB period, SSB carrier interval, SSB offset (Offset), or SSB duration (Duration) and the like.
  • the cells served by the IAB node may include cells served by DUs of the IAB node or cells deployed by the DUs of the IAB node. According to the present design, by carrying the relevant information for establishing the first F1 interface in the request information for establishing the first F1 interface, the target IAB host is implicitly instructed to request the establishment of the first F1 interface, and the target IAB host is provided with Information required to establish the first F1 interface.
  • the information included in the request information for establishing the first F1 interface may be acquired by the source IAB host from the IAB node in advance.
  • the source IAB host stores the content of the message when the previous IAB node initiated the F1 interface establishment request to it, or the source IAB host requests the IAB node to send the request information for establishing the first F1 interface to the source IAB host. all or part of the information.
  • the target IAB host sends the second information to the source IAB host.
  • the target Donor-CU of the IAB node may send the second information to the source Donor-CU of the IAB node.
  • the second information may be referred to as an F1 handover response.
  • the second information can be exchanged between the source IAB host and the target IAB host through an X2 or Xn interface.
  • the second information may be carried in an X2AP or XnAP message between the source IAB host and the target IAB host.
  • the second information may be carried in the handover request response message of the IAB node sent by the target IAB host to the source IAB host (for the handover response message of the IAB node, please refer to the explanation in S203).
  • the second information may be encapsulated into an F1AP information element container (container), and then carried in the X2AP message or the XnAP message.
  • the source IAB host and the target IAB host can transfer and exchange the second information through the S1 or Ng interface with the core network device.
  • the target IAB host sends the second information to the core network device through the S1 or Ng interface, and after receiving the second information, the core network device forwards the second information to the source IAB host through the S1 or Ng interface.
  • the second information may be carried in the handover request acknowledgement (handover request acknowledge, handover request ACK) sent by the target IAB host to the core network device and the handover command (handover command) sent by the core network device to the source IAB host. middle.
  • the source IAB host and the target IAB host can exchange the second information through the core network device, which ensures that the IAB node can obtain the feedback information of the target IAB host for the first information.
  • the second information includes feedback information of the request information.
  • the feedback information may be generated by the target IAB host according to the received first information.
  • the feedback information may be response information for establishing the first F1 interface.
  • the feedback information may be an F1 interface setup response (F1SETUP RESPONSE).
  • the response information for establishing the first F1 interface may include all or part of the content of the F1 establishment response message (the F1 establishment response message may refer to the explanation in S209).
  • the response information for establishing the first F1 interface includes at least one of the following information: information used to identify the target IAB host, activation information of a cell served by the IAB node, and information supported by the CU of the target IAB host.
  • the activation information of the cell served by the IAB node may include information of one or more cells that need to be activated.
  • the information for identifying the target IAB host may include any of the following: the identification (ID) or name (name) of the target IAB host, the CU identification (ID) or name (name) of the target IAB host, the target IAB host base station identification (gNB ID) or name (name).
  • the target IAB host can implicitly indicate to the source IAB host that it agrees to establish the first F1 interface by carrying the relevant information for establishing the first F1 interface in the response information for establishing the first F1 interface, and through The source IAB host provides the IAB node with the information needed to establish the first F1 interface.
  • the information used to identify the target IAB host can be used as an explicit indication information to indicate to the IAB node that the response information corresponds to the target IAB host, so that the IAB node can determine the received information Whether it is the information for establishing the first F1 interface or the information for updating the configuration of the second F1 interface.
  • the second F1 interface is a communication interface between the DU of the IAB node and the CU of the source IAB host.
  • the feedback information may be indication information that the establishment of the first F1 interface fails.
  • the feedback information may be F1 interface setup failure (F1 SETUP FAILURE).
  • the F1 SETUP FAILURE can refer to Section 9.2.1.6 in the 3rd generation partnership project (3GPP) technical standard (TS) 38.473 V16.1.0 version.
  • 3GPP 3rd generation partnership project
  • TS technical standard 38.473 V16.1.0 version.
  • the subsequent operations of the embodiments of the present application may not be performed continuously.
  • the source IAB host may determine to re-execute S301 according to the feedback information, that is, continue to send the first information to the target IAB host to try to establish the first F1 interface.
  • the source IAB host may determine not to re-execute S301 according to the feedback information, for example, the source IAB host may refer to method 200 to perform operations.
  • the source IAB host can determine that the target IAB host refuses or cannot establish the first F1 interface according to the received indication information of the failure to establish the first F1 interface. Further, the source IAB host can determine whether to continue to send the first information to the target IAB host to try to establish the first F1 interface, thereby improving the success rate of establishing the first F1 interface.
  • S303 The source IAB host sends the third information to the IAB node.
  • the source IAB host can send third information to the IAB node after receiving the response information, where the third information includes the information used for establishing the first F1 interface response information.
  • the source IAB host may send the third information to the IAB through the source parent node of the IAB node.
  • the source IAB host may carry the response information for establishing the first F1 interface in the RRC reconfiguration message (or the source Donor CU) sent by the source IAB host (or the source Donor CU) to the IAB node (or IAB-MT).
  • the RRC reconfiguration message can refer to the explanation in S204).
  • the MT of the IAB node After the MT of the IAB node receives the response information for establishing the first F1 interface, it can send the DU to the IAB node through the internal interface.
  • signaling overhead can be saved.
  • the source IAB host may carry the response information for establishing the first F1 interface in other existing RRC messages sent by the source IAB host (or source Donor CU) to the IAB node (or IAB-MT) or In the RRC message that carries the response information alone.
  • the MT of the IAB node After the MT of the IAB node receives the response information for establishing the first F1 interface, it can send the DU to the IAB node through the internal interface.
  • the source IAB host may carry the response information for establishing the first F1 interface on the F1AP of the second F1 interface sent by the source IAB host (or source Donor CU) to the IAB node (or IAB-DU).
  • the second F1 interface is a communication interface between the DU of the IAB node and the CU of the source IAB host.
  • the source IAB host can use the second information As the third information, it is transparently transmitted to the IAB node.
  • the target IAB host can send the above second information in the form of an F1AP container (container) cell to the IAB node through the source IAB host, which can prevent the source IAB host from parsing the second information, thereby increasing the number of the second information. 2.
  • the security of information transmission In addition, changes to existing RRC reconfiguration messages can be avoided.
  • the response information for establishing the first F1 interface is carried in the F1AP message of the second F1 interface, so that the IAB node can determine that the information carried in the F1AP message of the second F1 interface is for establishing the first F1 interface.
  • the information of the F1 interface is also the information used to update the configuration of the second F1 interface.
  • the F1AP message of the second F1 interface may include indication information, and the indication information is used to indicate that the information included in the F1AP message of the second F1 interface is related to The information corresponding to the target IAB host or the information used to establish the first F1 interface.
  • the indication information may be carried in the F1AP message of the second F1 interface together with the response information for establishing the first F1 interface.
  • the indication information may be included in the response information for establishing the first F1 interface, for example, the information used to identify the target IAB host included in the response information for establishing the first F1 interface may be used as the indication information.
  • the IAB node can determine, according to the indication information carried in the F1AP message of the second F1 interface, whether the information carried in the F1AP message of the second F1 interface is the information for establishing the first F1 interface, or whether to use the information carried in the F1AP message of the second F1 interface It is used to update the information of the configuration of the second F1 interface, so that different subsequent processing can be performed.
  • the indication information may not be explicitly carried in the F1AP message of the second F1 interface.
  • a new procedure may be specified between the source IAB host and the IAB node, which is a set of procedures specially used to send the relevant information for establishing the first F1 interface from the target IAB host to the IAB node in advance.
  • the IAB node may determine, according to information received before the F1AP message of the second F1 interface, whether the information included in the F1AP message of the second F1 interface is information corresponding to the target IAB host or is used to establish the first Information about the F1 interface.
  • the IAB node may determine, according to the received indication information included in the F1AP message of the second F1 interface, that the response information for establishing the first F1 interface included in the F1AP message of the second F1 interface is the same as the response information included in the F1AP message of the second F1 interface.
  • the target IAB host determines that the information carried in the F1AP message of the second F1 interface is information for establishing the first F1 interface, rather than information for updating the configuration of the second F1 interface.
  • the IAB node configures the first F1 interface according to the received third information.
  • the third information may be referred to as an F1 handover command.
  • S303 is an optional operation, that is, this embodiment may not include this operation.
  • the feedback information is the F1 interface establishment failure information, it is not necessary to continue to execute S303.
  • the DU of the IAB node can obtain its configuration information on the target IAB host more quickly, thereby realizing efficient handover.
  • the target IAB host can also flexibly indicate the establishment of the first F1 interface through feedback information, thereby improving the efficiency of establishing the first F1 interface.
  • S304 The target IAB host sends fourth information to the source IAB host.
  • the target IAB host For the specific method for the target IAB host to send the fourth information to the source IAB host, reference may be made to the method for the target IAB host to send the second information to the source IAB host in S302, which will not be repeated here.
  • the fourth information and the second information may be carried in the same message.
  • the fourth information includes IP address information of the target IAB host, where the IP address information is used for establishing an initial SCTP association between the target IAB host and the IAB node.
  • the target IAB host sends its own IP address information to the IAB node, so that the IAB node can quickly establish the SCTP coupling with the target IAB host according to the IP address information, and the target IAB host and the IAB node are also improved.
  • the IP address information of the target IAB host includes at least one of the following: the IP address of the target IAB host for the first F1 interface, the IP address type for the target IAB host of the first F1 interface, and the first F1 interface for the IP address of the target IAB host.
  • the number of IP addresses of the target IAB host of the interface or F1-C service, used for the first F1-U interface or the IP address of the target IAB host of the F1-U service, used for the first F1-U interface or F1-U service The IP address type of the target IAB host for the first F1-U interface or the IP address prefix of the target IAB host of the F1-U service, the IP address of the target IAB host for the first F1-U interface or the F1-U service number of addresses.
  • the first F1-C interface is a control plane interface of the first F1 interface
  • the first F1-U interface is a user plane interface of the first F1 interface
  • the above-mentioned F1-C service includes passing through the first F1-C interface.
  • the service of the interface, the above-mentioned F1-U service includes the service passing through the first F1-U interface.
  • the IP address type may include IPv4 and/or IPv6 type.
  • the IP address of the target IAB host used for the first F1 interface includes the IP address of the CU corresponding to the first F1 interface, for example, the IP address of the Donor-CU.
  • the IP address used for the first F1-C interface or the target IAB host of the F1-C service includes the IP address of the CU corresponding to the first F1-C interface, for example, the IP address of the Donor-CU-CP.
  • the IP address of the target IAB host used for the first F1-U interface or the F1-U service includes the IP address of the CU side corresponding to the first F1-U interface, for example, the IP address of the Donor-CU-UP.
  • the sending of the fourth information by the target IAB host to the source IAB host may be based on a request of the IAB node.
  • the IAB node sends IP address request information to the source IAB host, where the IP address request information is used to request an IP address from the target IAB host.
  • the source IAB host forwards the IP address request information to the target IAB host.
  • the sending of the fourth information by the target IAB host to the source IAB host may be based on the first information from the source IAB host.
  • S305 The source IAB host sends fifth information to the IAB node.
  • the source IAB host After receiving the fourth information, the source IAB host sends fifth information to the IAB node, where the fifth information includes the IP address information.
  • the source IAB host For a specific method for the source IAB host to send the fifth information to the IAB node, reference may be made to the method for the source IAB host to send the third information to the IAB node in S303, which will not be repeated here.
  • the fifth information and the third information may be carried in the same message.
  • S304-S305 may be executed before S301-S303, or may be executed after S308, and the embodiment of the present application does not limit the execution timing of S304-S305.
  • S304 and S305 are optional operations, that is, this embodiment may not include these two operations.
  • the network management device still configures multiple IP addresses in advance (refer to the assignment of IP addresses in operation S207).
  • S306 The target IAB host sends sixth information to the source IAB host.
  • the sixth information includes request information for establishing a subordinate device context of the IAB node in the IAB node and/or the target IAB host, where the request information is used for requesting to establish an IAB in the IAB node and/or the target IAB host Node subordinate device context.
  • the subordinate equipment of the IAB node includes an IAB sub-node of the IAB node or a terminal device accessing the IAB node.
  • the request information for establishing the subordinate device context of the IAB node in the IAB node and/or the target IAB host may include a user context establishment request message in the F1AP process (for details of the content included in the user context establishment request message, please refer to 3GPP Section 9.2.2.1 of TS38.473 V16.1.0) in whole or in part.
  • the request information for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host includes at least one of the following: an F1 interface application protocol identifier corresponding to the subordinate device of the IAB node, the IAB node serving The Scell establishment list, the SRB establishment list between the IAB node and the subordinate equipment of the IAB node, the DRB establishment list between the IAB node and the subordinate equipment of the IAB node, the IAB node and the subordinate equipment of the IAB node (or the IAB node The BH RLC CH establishment list between the child nodes), the user plane data routing rules of the IAB node, and the user plane bearer mapping rules of the IAB node.
  • an F1 interface application protocol identifier corresponding to the subordinate device of the IAB node
  • the IAB node serving The Scell establishment list, the SRB establishment list between the IAB node and the subordinate equipment of the IAB node, the DRB establishment list between
  • the target IAB host can carry the request information for establishing the subordinate device context of the IAB node in the IAB node and/or the target IAB host to be used in the IAB node and/or the target IAB host.
  • Establish the relevant information of the subordinate device context of the IAB node implicitly instruct the source IAB host to request to establish the subordinate device context of the IAB node in the IAB node and/or the target IAB host, and provide the IAB node with the IAB node through the source IAB host.
  • the information required by the node and/or the target IAB host to establish the context of the subordinate device of the IAB node is required by the node and/or the target IAB host to establish the context of the subordinate device of the IAB node.
  • the target IAB host For a specific method for the target IAB host to send the sixth information to the source IAB host, reference may be made to the method for the target IAB host to send the second information to the source IAB host in S302, which will not be repeated here. At least one of the second information, the fourth information and the sixth information can be carried in the same message, which can save signaling overhead. In addition, the data communication between the IAB node and the target IAB host can be established more quickly, thereby improving the communication efficiency of the IAB network.
  • S307 The source IAB host sends seventh information to the IAB node.
  • the source IAB host After receiving the sixth information, the source IAB host sends seventh information to the IAB node, where the seventh information includes the request information for establishing the subordinate device context of the IAB node in the IAB node and/or the target IAB host.
  • the source IAB host For a specific method for the source IAB host to send the seventh information to the IAB node, reference may be made to the method for the source IAB host to send the third information to the IAB node in S303, and details are not described herein again. At least one of the third information, the fifth information and the seventh information can be carried in the same message, which can save signaling overhead. In addition, the data communication between the IAB node and the target IAB host can be established more quickly, thereby improving the communication efficiency of the IAB network.
  • the IAB node sends the feedback information of the seventh information to the target IAB host.
  • the feedback information of the seventh information may be response information for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host.
  • the response information for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host may include a user context establishment response message in the F1AP process (for details of the content included in the user context establishment response message, please refer to 3GPP Part or all of the content of Section 9.2.2.2 in TS38.473 V16.1.0).
  • the response information for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host includes at least one of the following: the C-RNTI allocated by the IAB node for the subordinate device of the IAB node, and the establishment of The list of DRBs between the IAB node and the subordinate devices of the IAB node that succeeded or failed to be established, the list of SRBs between the IAB node and the subordinate devices of the IAB node that was established successfully or failed, the IAB node that was established successfully or failed to be established.
  • the IAB node when the IAB node is connected to the source IAB host through the source parent node, the IAB node can first send the feedback information of the seventh information to the source IAB host through the source parent node, and then the source IAB host sends the target The IAB host sends feedback information of the seventh information.
  • the IAB node may carry the feedback information of the seventh information in any existing RRC message sent by the IAB node (or IAB-MT) to the source IAB host (or Donor CU) or carry the response independently information in the RRC message.
  • the IAB node may carry the feedback information of the seventh information in the F1AP message of the second F1 interface sent by the IAB node (or IAB-DU) to the source IAB host (or Donor CU), wherein the The second F1 interface is a communication interface between the DU of the IAB node and the CU of the source IAB host.
  • the feedback information of the seventh information may be indication information that the context of the subordinate device of the IAB node fails to be established in the IAB node and/or the target IAB host.
  • the feedback information may be CONTEXT SETUP FAILURE.
  • the CONTEXT SETUP FAILURE can refer to Section 9.2.2.3 in 3GPP TS38.473 V16.1.0 version.
  • the target IAB host can determine to re-execute S306 according to the feedback information, that is, continue to send the sixth information to the source IAB host, and the source IAB host continues to send the seventh information to the IAB node, in order to try to use the IAB node and/or The IAB node subordinate device context is established in the target IAB host.
  • the target IAB host can determine not to re-execute S306 according to the feedback information. For example, it can wait for the IAB node to switch to the target IAB host, and then try to establish the IAB node subordinate device context in the IAB node and/or the target IAB host. .
  • the target IAB host can obtain the context of the subordinate device of the IAB node faster, reducing the time for the IAB node to switch across the donor CU, thereby realizing Efficient switching.
  • S306 to S308 are optional operations, that is, this embodiment may not include these three operations.
  • the three operations can wait until the IAB node switches to the target IAB host, and then complete the establishment of the subordinate device context through the target IAB host and the IAB node.
  • S309 An initial SCTP coupling is established between the IAB node and the target IAB host.
  • the initial SCTP coupling may be established between the IAB node and the target IAB host CU.
  • the IAB node uses the IP address to establish an initial SCTP association with the target IAB host.
  • the IP address may be selected from multiple IP addresses configured by the network management device, or the IP address may be obtained according to the fifth information in S305.
  • the IAB node may associate the relevant information of the first F1 interface with the SCTP coupling, and/or the IAB node may subordinate the IAB node established in the IAB node and/or the target IAB host.
  • the device context is associated with this SCTP association.
  • the target IAB host can send IAB-DU configuration update information to the IAB node, and the IAB-DU configuration update information can be carried in the GNB-CU CONFIGURATION UPDATE sent by the target IAB host (or target Donor CU) to the IAB node. information.
  • the IAB node may associate the relevant information of the first F1 interface with the SCTP coupling according to the configuration update information, and/or associate the IAB node subordinate device context established in the IAB node and/or the target IAB host associated with this SCTP coupling.
  • the IAB node may delete other SCTP associations on the IAB node DU according to the configuration update information.
  • the IP address used in the subsequent SCTP coupling may also be obtained according to the IP address information in the fifth information in S305.
  • the IP address used for subsequent SCTP coupling is obtained according to the GNB-CU CONFIGURATION UPDATE information sent by the target IAB host (or the target Donor CU) to the IAB node.
  • S309 may be executed after S304 to S305, or may be executed after S308, and the embodiment of the present application does not limit the execution timing of S309.
  • FIG. 4 shows a communication method according to an embodiment of the present application, and the communication method 400 includes:
  • the target IAB host of the IAB node sends fourth information to the source IAB host of the IAB node.
  • the target Donor-CU of the IAB node may send the second information to the source Donor-CU of the IAB node.
  • the IAB node may be directly connected to the source IAB host, or the IAB node may be connected to the source IAB host through one or more upstream IAB nodes.
  • the target IAB host may be the source IAB host determined according to the measurement report from the IAB node. Likewise, after the IAB node switches to the target IAB host, the IAB node may directly access the target IAB host, or the IAB node may be connected to the target IAB host through one or more upstream IAB nodes.
  • the IAB node may be a switching IAB node that needs to switch the parent node, that is, the source IAB host determines that the switching IAB node needs to be switched from the source parent node to the target parent node.
  • the IAB node may also be a child node of the handover IAB node, that is, the IAB node may be handed over together with the handover IAB node.
  • the IAB node may be IAB node 3 in the left diagram of FIG. 1E, or may be IAB node 4 in the left diagram of FIG. 1E.
  • the fourth information can be exchanged between the source IAB host and the target IAB host through the X2 or Xn interface.
  • the fourth information may be carried in an X2AP or XnAP message between the source IAB host and the target IAB host.
  • the fourth information may be carried in the handover request response message of the IAB node sent by the target IAB host to the source IAB host (for the handover response message of the IAB node, please refer to the explanation in S203).
  • the fourth information may be encapsulated into an F1AP information element container (container), and then carried in the X2AP message or the XnAP message.
  • tainer F1AP information element container
  • the source IAB host and the target IAB host may transfer and exchange the fourth information through the S1 or Ng interface with the core network device.
  • the target IAB host sends the fourth information to the core network device through the S1 or Ng interface, and after receiving the fourth information, the core network device forwards the fourth information to the source IAB host through the S1 or Ng interface.
  • the fourth information includes IP address information of the target IAB host, where the IP address information is used for establishing an initial SCTP association between the target IAB host and the IAB node.
  • the IP address information can also be used to establish a subsequent SCTP coupling between the target IAB host and the IAB node. That is, the IP address information may include both an IP address used for initial SCTP association establishment, and an IP address used for subsequent SCTP association establishment.
  • the IP address information includes at least one of the following: the IP address of the target IAB host for the first F1 interface, the IP address type for the target IAB host of the first F1 interface, the target for the first F1 interface
  • the IP address prefix of the IAB host the number of IP addresses used for the target IAB host of the first F1 interface, the IP address of the target IAB host used for the first F1-C interface or the F1-C service, used for the first F1 - IP address type of the target IAB host of the C interface or F1-C service, used for the IP address prefix of the target IAB host of the first F1-C interface or F1-C service, used for the first F1-C interface or F1-
  • the first F1-C interface is a control plane interface of the first F1 interface
  • the first F1-U interface is a user plane interface of the first F1 interface
  • the above-mentioned F1-C service includes passing through the first F1-C interface.
  • the service of the interface, the above-mentioned F1-U service includes the service passing through the first F1-U interface.
  • the IP address type may include IPv4 and/or IPv6 type.
  • the IP address of the target IAB host used for the first F1 interface includes the IP address of the CU corresponding to the first F1 interface, for example, the IP address of the Donor-CU.
  • the IP address used for the first F1-C interface or the target IAB host of the F1-C service includes the IP address of the CU corresponding to the first F1-C interface, for example, the IP address of the Donor-CU-CP.
  • the IP address of the target IAB host used for the first F1-U interface or the F1-U service includes the IP address of the CU side corresponding to the first F1-U interface, for example, the IP address of the Donor-CU-UP.
  • the sending of the fourth information by the target IAB host to the source IAB host may be based on a request of the IAB node.
  • the IAB node sends IP address request information to the source IAB host, where the IP address request information is used to request an IP address from the target IAB host.
  • the source IAB host forwards the IP address request information to the target IAB host.
  • sending the fourth information by the target IAB host to the source IAB host may be based on a handover request message from the IAB node of the source IAB host (for the handover request message of the IAB node, please refer to the explanation in S202).
  • the source IAB host sends fifth information to the IAB node.
  • the source IAB host After receiving the fourth information, the source IAB host sends fifth information to the IAB node, where the fifth information includes the IP address information. Specifically, when the IAB node is connected to the source IAB host through the source parent node, the source IAB host may send the fifth information to the IAB through the source parent node of the IAB node.
  • the source IAB host may carry the IP address information in the RRC reconfiguration message sent by the source IAB host to the IAB node (for the RRC reconfiguration message, please refer to the explanation in S204).
  • the MT of the IAB node After the MT of the IAB node receives the IP address information, it can send the DU to the IAB node through the internal interface.
  • the source IAB host may carry the IP address information in the F1AP message of the second F1 interface sent by the source IAB host to the IAB node, where the second F1 interface is the DU of the IAB node and the source IAB host.
  • the communication interface between the CUs For example, when the fourth information is encapsulated into an F1AP information element container (container), and then carried in an X2AP message or an XnAP message and sent by the target IAB host to the source IAB host, the source IAB host can use the fourth information As the fifth information, it is transparently transmitted to the IAB node.
  • an F1AP information element container container
  • S403 An initial SCTP coupling is established between the IAB node and the target IAB host.
  • the initial SCTP coupling may be established between the IAB node and the target IAB host CU.
  • the IAB node uses the IP address to establish an initial SCTP association with the target IAB host.
  • the IP address is obtained according to the IP address information in the fifth information in S402.
  • the IP address used in the subsequent SCTP coupling may also be obtained according to the IP address information in the fifth information in S402.
  • the IP address used for subsequent SCTP coupling is obtained according to the GNB-CU CONFIGURATION UPDATE information sent by the target IAB host (or the target Donor CU) to the IAB node after the first F1 interface is successfully established.
  • the embodiment of the present application provides a fast SCTP coupling establishment method.
  • the target IAB host sends its own IP address information to the IAB node, so that the IAB node can quickly establish SCTP with the target IAB host according to the IP address information.
  • the coupling also improves the success rate of SCTP coupling establishment between the target IAB host and the IAB node.
  • an embodiment of the present application provides a communication device, and the communication device may be a relay device or a network device in any of the communication methods provided in any of the foregoing embodiments and any possible designs thereof, or User equipment, the relay device or network device or user equipment may be included in the communication method provided in any of the foregoing embodiments, for performing method steps or operations or behaviors performed by the relay device or network device or user equipment of the corresponding at least one unit.
  • the setting of the at least one unit may have a one-to-one correspondence with method steps or operations or behaviors performed by the relay device, network device, or user equipment.
  • FIG. 5 is a schematic block diagram of a communication apparatus 500 provided by an embodiment of the present application. The structure and functions of the communication apparatus 500 will be described in detail below with reference to FIG. 5 .
  • the communication apparatus 500 may include: a sending module 501 and an obtaining module 502.
  • the communication device 500 may be applied to a source IAB host.
  • the sending module 501 is specifically configured to send first information to the target IAB host of the IAB node, where the first information includes request information for establishing the first F1 interface.
  • the obtaining module 502 is specifically configured to obtain second information from the target IAB host, where the second information includes feedback information of the above request information.
  • the first F1 interface refers to a communication interface between the DU of the IAB node and the CU of the target IAB host.
  • the request information for establishing the first F1 interface may include at least one of the following information: IAB-DU identification (ID), IAB-DU name (name), serving cell information (served cell) of the cell served by the IAB node information of a cell served by the IAB node), the system information configuration (such as synchronization signal and PBCH block (synchronization signal and physical broadcast channel block, SSB) related configuration) sent by the DU of the IAB node, supported by the DU of the IAB node
  • the RRC version the transport layer address information of the DU of this IAB node.
  • the SSB-related configuration may include SSB frequency, SSB period, SSB carrier interval, SSB offset (Offset), or SSB duration (Duration) and the like.
  • the sending module 501 may also be configured to send third information to the IAB node, where the third information includes the above-mentioned response information.
  • the response information for establishing the first F1 interface includes at least one of the following information: information used to identify the target IAB host, activation information of the cell served by the IAB node, RRC supported by the CU of the target IAB host version, the transport layer address information of the CU hosted by the target IAB, and the synchronization signal block transmission configuration (STC) of the DU of the IAB node.
  • the activation information of the cell served by the IAB node may include information of one or more cells that need to be activated.
  • the information for identifying the target IAB host may include any of the following: the identification (ID) or name (name) of the target IAB host, the CU identification (ID) or name (name) of the target IAB host, the target IAB host base station identification (gNB ID) or name (name).
  • the sending module 501 may also continue to send the first information to the target IAB host of the IAB node.
  • the obtaining module 502 can also be used to receive fourth information from the target IAB host, where the fourth information includes IP address information of the target IAB host, and the IP address information is used for initializing between the target IAB host and the IAB node. Establishment of SCTP coupling. Further, the sending module 501 may also be configured to send fifth information to the IAB node, where the fifth information includes the IP address information.
  • the IP address information includes at least one of the following: the IP address used for the target IAB host of the first F1 interface, the IP address type used for the target IAB host of the first F1 interface, and the IP address type used for the first F1 interface
  • the IP address prefix of the target IAB host of the first F1 interface the number of IP addresses used for the target IAB host of the first F1 interface, the IP address of the target IAB host for the first F1-C interface or the F1-C service, and the number of IP addresses used for the first F1-C interface or the target IAB host of the F1-C service.
  • the first F1-C interface is a control plane interface of the first F1 interface
  • the first F1-U interface is a user plane interface of the first F1 interface
  • the above-mentioned F1-C service includes passing through the first F1-C interface.
  • the service of the interface, the above-mentioned F1-U service includes the service passing through the first F1-U interface.
  • the IP address type may include IPv4 and/or IPv6 type.
  • the obtaining module 502 can also be used to receive sixth information from the target IAB host, where the sixth information includes a request for establishing the context of the IAB node subordinate device in the IAB node and/or the target IAB host information.
  • the sending module 501 may also be configured to send seventh information to the IAB node, where the seventh information includes the request information.
  • the obtaining module 502 may also be configured to receive response information from the IAB node for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host.
  • the subordinate equipment of the IAB node includes an IAB sub-node of the IAB node or a terminal device accessing the IAB node.
  • the sending module 501 may also be configured to send the response information to the target IAB host.
  • the request information for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host includes at least one of the following: the F1 interface application protocol identifier corresponding to the subordinate device of the IAB node, the service provider of the IAB node
  • the response information for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host includes at least one of the following: the C-RNTI allocated by the IAB node for the subordinate devices of the IAB node, established successfully or established
  • FIG. 6 is a schematic block diagram of a communication apparatus 600 provided by an embodiment of the present application. The structure and functions of the communication apparatus 600 will be described in detail below with reference to FIG. 6 .
  • the communication apparatus 600 may include an obtaining module 601 and a sending module 602 , and optionally, may further include a processing module 603 .
  • the communication device 600 can be applied to a target IAB host.
  • the obtaining module 601 is specifically configured to receive first information from the source IAB host, where the first information includes request information for establishing the first F1 interface.
  • the first F1 interface is a communication interface between the distributed unit of the IAB node and the centralized unit of the target IAB host.
  • the sending module 602 is specifically configured to send second information to the source IAB host, where the second information includes feedback information of the above request information.
  • the request information for establishing the first F1 interface may include at least one of the following information: IAB-DU identification (ID), IAB-DU name (name), serving cell information (served cell) of the cell served by the IAB node information of a cell served by the IAB node), the system information configuration (such as synchronization signal and PBCH block (synchronization signal and physical broadcast channel block, SSB) related configuration) sent by the DU of the IAB node, supported by the DU of the IAB node The RRC version, the transport layer address information of the DU of this IAB node.
  • the SSB-related configuration may include SSB frequency, SSB period, SSB carrier interval, SSB offset (Offset), or SSB duration (Duration) and the like.
  • the response information for establishing the first F1 interface includes at least one of the following information: information used to identify the target IAB host, activation information of the cell served by the IAB node, RRC version supported by the CU of the target IAB host, The transport layer address information of the CU hosted by the target IAB, and the synchronization signal block transmission configuration (synchronization signal block transmission configuration, STC) of the DU of the IAB node.
  • the activation information of the cell served by the IAB node may include information of one or more cells that need to be activated.
  • the information for identifying the target IAB host may include any of the following: the identification (ID) or name (name) of the target IAB host, the CU identification (ID) or name (name) of the target IAB host, the target IAB host base station identification (gNB ID) or name (name).
  • the sending module 602 can also be used to send fourth information to the source IAB host, where the fourth information includes IP address information of the target IAB host, and the IP address information is used for the initial SCTP between the target IAB host and the IAB node. Conjugation establishment.
  • the IP address information includes at least one of the following: the IP address used for the target IAB host of the first F1 interface, the IP address type used for the target IAB host of the first F1 interface, and the IP address type used for the first F1 interface
  • the IP address prefix of the target IAB host of the first F1 interface the number of IP addresses used for the target IAB host of the first F1 interface, the IP address of the target IAB host for the first F1-C interface or the F1-C service, and the number of IP addresses used for the first F1-C interface or the target IAB host of the F1-C service.
  • the first F1-C interface is a control plane interface of the first F1 interface
  • the first F1-U interface is a user plane interface of the first F1 interface
  • the above-mentioned F1-C service includes passing through the first F1-C interface.
  • the service of the interface, the above-mentioned F1-U service includes the service passing through the first F1-U interface.
  • the IP address type may include IPv4 and/or IPv6 type.
  • the sending module 602 can also be used to send sixth information to the source IAB host, where the sixth information includes request information for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host.
  • the obtaining module 601 may also be configured to receive, from the source IAB host, the response information from the IAB node for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host.
  • the request information for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host includes at least one of the following: the F1 interface application protocol identifier corresponding to the subordinate device of the IAB node, the service provider of the IAB node
  • the response information for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host includes at least one of the following: the C-RNTI allocated by the IAB node for the subordinate devices of the IAB node, established successfully or established
  • the communication apparatus 600 may further include a processing module 603 .
  • the processing module 603 is specifically configured to establish an initial SCTP association with the IAB node according to the IP address.
  • the IP address is the IP address included in the IP address information carried in the fourth information.
  • the communication device 600 may be applied to an IAB node.
  • the obtaining module 601 is specifically configured to receive third information from the source IAB host, where the third information includes the response information for establishing the first F1 interface.
  • the first F1 interface is a communication interface between the distributed unit of the IAB node and the centralized unit of the target IAB host.
  • the response information for establishing the first F1 interface is carried on the second F1 interface (the DU of the IAB node and the CU of the source IAB host) sent by the source IAB host (or the source Donor CU) to the IAB node (or IAB-DU)
  • the F1AP message of the second F1 interface is included in the F1AP message of the second F1 interface
  • indication information may be included in the F1AP message of the second F1 interface, and the indication information is used to indicate that the information included in the F1AP message of the second F1 interface corresponds to the target IAB host information or the information used to establish the first F1 interface.
  • the processing module 603 may determine, according to the indication information included in the F1AP message of the second F1 interface obtained by the obtaining module 601, that the information included in the F1AP message of the second F1 interface is the information corresponding to the target IAB host or is Information for establishing the first F1 interface.
  • the obtaining module 601 may also be configured to obtain fifth information from the source IAB host, where the fifth information includes IP address information.
  • the IP address information includes at least one of the following: the IP address used for the target IAB host of the first F1 interface, the IP address type used for the target IAB host of the first F1 interface, and the IP address type used for the first F1 interface
  • the IP address prefix of the target IAB host of the first F1 interface the number of IP addresses used for the target IAB host of the first F1 interface, the IP address of the target IAB host for the first F1-C interface or the F1-C service, and the number of IP addresses used for the first F1-C interface or the target IAB host of the F1-C service.
  • the first F1-C interface is a control plane interface of the first F1 interface
  • the first F1-U interface is a user plane interface of the first F1 interface
  • the above-mentioned F1-C service includes passing through the first F1-C interface.
  • the service of the interface, the above-mentioned F1-U service includes the service passing through the first F1-U interface.
  • the IP address type may include IPv4 and/or IPv6 type.
  • the obtaining module 601 can also be used to obtain seventh information from the source IAB host, where the seventh information includes request information for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host. .
  • the request information for establishing the context of the subordinate device of the IAB node in the IAB node and/or the target IAB host includes at least one of the following: the F1 interface application protocol identifier corresponding to the subordinate device of the IAB node, the service provider of the IAB node
  • the sending module 602 is also used to send the feedback information of the seventh information to the source IAB host, where the feedback information of the seventh information is used to establish the subordinate equipment of the IAB node in the IAB node and/or the target IAB host. Context response information.
  • the response information for establishing the context of the subordinate equipment of the IAB node in the IAB node and/or the target IAB host includes at least one of the following: the C-RNTI allocated by the IAB node for the subordinate equipment of the IAB node, the establishment is successful Or establish the DRB list between the IAB node and the subordinate equipment of the IAB node that fails, establish the SRB list between the IAB node and the subordinate equipment of the IAB node that succeeds or fails to establish, and establish the IAB node and fail to establish successfully.
  • the communication apparatus 600 may further include a processing module 603 .
  • the processing module 603 is specifically configured to establish an initial SCTP coupling with the target IAB host according to the IP address.
  • the IP address is obtained by the communication device 600 according to the fifth information.
  • an embodiment of the present application further provides an apparatus 700 , and the structure and functions of the apparatus 700 will be described in detail below with reference to FIG. 7 , a schematic block diagram of the apparatus 700 .
  • the apparatus may include at least one processor 701 .
  • an interface circuit 702 is also included.
  • the apparatus 700 can be made to implement the communication method provided in any of the foregoing embodiments and any of the possible designs.
  • the processor 701 is used to implement the communication method and any possible design provided by any of the foregoing embodiments by using a logic circuit or executing code instructions.
  • the interface circuit 702 can be used to receive program instructions and transmit them to the processor, or the interface circuit 702 can be used for the apparatus 700 to communicate and interact with other communication devices, such as interactive control signaling and/or service data.
  • the interface circuit 702 can be used to receive signals from other devices other than the device 700 and transmit to the processor 701 or send signals from the processor 701 to other communication devices other than the device 700 .
  • the interface circuit 702 may be a code and/or data read/write interface circuit, or the interface circuit 702 may be a signal transmission interface circuit between the communication processor and the transceiver.
  • the communication apparatus 700 may further include at least one memory 703, and the memory 703 may be used to store required program instructions and/or data.
  • the apparatus 700 may further include a power supply circuit 704, and the power supply circuit 704 may be used to supply power to the processor 701.
  • the power supply circuit 704 may be located in the same chip as the processor 701, or may be located where the processor 701 is located. outside the chip inside another chip.
  • the apparatus 700 may further include a bus 705 , and various parts of the apparatus 700 may be interconnected through the bus 705 .
  • the processor in the embodiment of the present application may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), application-specific integrated circuits (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM enhanced synchronous dynamic random access memory
  • ESDRAM Synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM, DR RAM
  • the power supply circuit described in the embodiments of the present application includes, but is not limited to, at least one of the following: a power supply line, a power supply subsystem, a power management chip, a power consumption management processor, or a power consumption management control circuit.
  • the transceiver device, the interface circuit, or the transceiver described in the embodiments of the present application may include a separate transmitter and/or a separate receiver, or the transmitter and the receiver may be integrated.
  • Transceiver devices, interface circuits, or transceivers may operate under the direction of a corresponding processor.
  • the transmitter may correspond to the transmitter in the physical device
  • the receiver may correspond to the receiver in the physical device.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the device embodiments described above are only illustrative.
  • the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined. Either it can be integrated into another system, or some features can be omitted, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • “implemented by software” may mean that the processor reads and executes the program instructions stored in the memory to realize the functions corresponding to the above modules or units, wherein the processor refers to a processing circuit with the function of executing program instructions, Including but not limited to at least one of the following: central processing unit (CPU), microprocessor, digital signal processing (DSP), microcontroller (MCU), or artificial intelligence processing Various types of processing circuits that can run program instructions, such as a processor. In other embodiments, the processor may also include circuits for other processing functions (eg, hardware circuits for hardware acceleration, bus and interface circuits, etc.).
  • the processor may be presented in the form of an integrated chip, for example, in the form of an integrated chip whose processing function only includes the function of executing software instructions, or in the form of a system on a chip (SoC), that is, on a chip , in addition to including a processing circuit (usually called a "core") capable of running program instructions, it also includes other hardware circuits for implementing specific functions (of course, these hardware circuits can also be implemented independently based on ASIC and FPGA), correspondingly Yes, in addition to the function of executing software instructions, the processing function may also include various hardware acceleration functions (such as AI calculation, encoding and decoding, compression and decompression, etc.).
  • SoC system on a chip
  • the hardware processing circuit can be composed of discrete hardware components or an integrated circuit. In order to reduce power consumption and reduce size, it is usually implemented in the form of integrated circuits.
  • the hardware processing circuit may include an ASIC, or a programmable logic device (programmable logic device, PLD); wherein, the PLD may in turn include an FPGA, a complex programmable logic device (complex programmable logic device, CPLD), and the like.
  • These hardware processing circuits can be a single semiconductor chip packaged separately (such as packaged into an ASIC); they can also be integrated with other circuits (such as CPU, DSP) and packaged into a semiconductor chip, for example, can be formed on a silicon substrate
  • a variety of hardware circuits and CPUs are individually packaged into a chip, which is also called SoC, or circuits and CPUs for implementing FPGA functions can also be formed on a silicon substrate and individually enclosed into a single chip. Also known as a programmable system on a chip (system on a programmable chip, SoPC).
  • the unit described as a separate component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or may be distributed to multiple on the network unit. Some or all of the units may be selected according to actual needs to achieve the purpose of the solutions of the embodiments of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium.
  • the medium may include several instructions to cause a computer device, such as a personal computer, a server, or a network device, or a processor to perform all or part of the operations of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium may include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, etc. that can store program codes medium or computer-readable storage medium.
  • transmission may include the following three situations: data transmission, data reception, or data transmission and data reception.
  • data may include service data, and/or signaling data.
  • At least one means one or more. “Includes at least one of the following: A, B, C.” means that it may include A, or B, or C, or A and B, or A and C, or B and C, or A, B and C.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • general packet radio service general packet radio service
  • GPRS general packet radio service
  • long term evolution long term evolution
  • LTE long term evolution
  • LTE frequency division duplex frequency division duplex
  • TDD LTE Time division duplex
  • WiMAX worldwide interoperability for microwave access
  • 5G 5th generation
  • NR new radio

Landscapes

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

Abstract

本申请实施例提供了一种用于接入回传一体化(integrated access and backhaul,IAB)网络通信的方法及相关设备。该方法包括：IAB节点的源IAB宿主向该IAB节点的目标IAB宿主发送用于建立第一F1接口的请求信息，其中，该第一F1接口为该IAB节点的分布式单元和该目标IAB宿主的集中式单元之间的通信接口。随后，该目标IAB宿主向该源IAB宿主发送该请求信息的反馈信息。通过源IAB宿主与目标IAB宿主交互用于建立第一F1接口的相关信息，可以使IAB节点的分布式单元(distributed unit，DU)更快地获取其在目标IAB宿主上的配置信息，从而实现高效的切换。

Description

一种用于IAB网络通信的方法及相关设备
本申请要求于2020年06月30日提交中国专利局，申请号为202010624351.5，申请名称为“一种用于IAB网络通信的方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，并且更具体地，涉及一种用于IAB网络通信的方法及相关设备。
背景技术
第五代通信(fifth generation,5G)中引入了集中式单元(Central Unit，CU)和分布式单元(Distributed Unit，DU)的概念。基站，如下一代基站(generation nodeB，gNB)，可以按照协议层划分为一个gNB-CU和连接到该gNB-CU的至少一个gNB-DU。该gNB-DU可以包括无线链路控制(Radio Link Control，RLC)层功能，MAC层功能和物理(Physical，PHY)层功能。该CU可以包括分组数据汇聚层协议(Packet Data Convergence Protocol，PDCP)层功能，业务数据适配协议(Service Data Adaptation Protocol，SDAP)层功能以及无线资源控制(Radio Resource Control，RRC)层功能。由于gNB-CU与gNB-DU之间是通过有线连接，并通过F1接口进行通信，所以现有技术并没有涉及gNB-DU的切换问题。
在5G引入了接入回传一体化(Integrated access and backhaul,IAB)网络以及IAB节点之后，由于IAB节点的DU与IAB宿主的CU之间是通过无线连接的，所以IAB节点可以选择连接到不同的IAB宿主，或者，在不同的IAB宿主之间进行切换。
然而，IAB节点如何高效地连接到不同的IAB宿主，或者，在不同的IAB宿主之间进行高效的切换，现有技术并没有给出解决方案。
发明内容
有鉴于此，本申请提供了一种通信方法及相关设备，可以实现IAB节点高效地连接到不同的IAB宿主，或者，在不同的IAB宿主之间进行高效的切换。
第一方面，本申请提供了一种通信方法，该方法可以包括：IAB节点的源IAB宿主向IAB节点的目标IAB宿主发送第一信息，该第一信息包括用于建立第一F1接口的请求信息。目标IAB宿主接收该第一信息后，向该源IAB宿主发送第二信息，该第二信息包括上述请求信息的反馈信息。其中，第一F1接口指的是该IAB节点的DU和该目标IAB宿主的CU之间的通信接口。通过本方法，示例性的有益效果包括：通过源IAB宿主与目标IAB宿主交互用于建立第一F1接口的相关信息，可以使IAB节点的DU更快地获取其在目标IAB宿主上的配置信息，从而实现高效的切换。另外，目标IAB宿主也可以通过反馈信息，灵活指示该第一F1接口的建立情况，从而提高该第一F1接口建立的效率。
第一方面的一种可行设计中，上述源IAB宿主发给目标IAB宿主的反馈信息为用于建立第一F1接口的响应信息。源IAB宿主收到该响应信息后，向IAB节点发送第三信息，该第三信息中包括上述响应信息。通过本方法，示例性的有益效果包括：源IAB宿主可以根据收到的用于建立第一F1接口的响应信息，确定该目标IAB宿主同意建立该第一F1接口。进一 步的，向IAB节点通知该用于建立第一F1接口的响应信息，以便IAB节点快速建立该第一F1接口。
第一方面的一种可行设计中，上述源IAB宿主发给目标IAB宿主的反馈信息为该第一F1接口建立失败的指示信息。通过本方法，示例性的有益效果包括：源IAB宿主可以根据收到的该第一F1接口建立失败的指示信息，确定该目标IAB宿主拒绝或者无法建立该第一F1接口。进一步的，源IAB宿主可以确定是否继续向该目标IAB宿主发送第一信息，以尝试建立该第一F1接口，从而提高该第一F1接口建立的成功率。
第一方面的一种可行设计中，上述用于建立第一F1接口的请求信息包括以下中至少一个：该IAB节点的DU标识，该IAB节点的DU名称，该IAB节点服务的小区的服务小区信息，该IAB节点的DU发送的系统信息，该IAB节点的DU所支持的无线资源控制(radio resource control，RRC)版本，该IAB节点的DU的传输层地址信息。通过本方法，示例性的有益效果包括：可以通过携带用于建立第一F1接口的相关信息，向目标IAB宿主隐式指示请求建立该第一F1接口，并向目标IAB宿主提供建立该第一F1接口所需的信息。
第一方面的一种可行设计中，上述用于建立第一F1接口的响应信息包括以下中至少一个：用于标识该目标IAB宿主的信息，该IAB节点服务的小区的激活信息，该目标IAB宿主的CU所支持的RRC版本，该目标IAB宿主的CU的传输层地址信息，该IAB节点的DU的同步信号块发送配置(synchronization signal block transmission configuration，STC)。该用于标识该目标IAB宿主的信息可以包括以下任一个：目标IAB宿主的标识或名称，目标IAB宿主的CU标识或名称，目标IAB宿主的基站标识或名称。通过本方法，示例性的有益效果包括：目标IAB宿主可以通过携带用于建立第一F1接口的相关信息的响应信息，向源IAB宿主隐式指示同意建立该第一F1接口，并通过源IAB宿主向IAB节点提供建立该第一F1接口所需的信息。另外，该用于标识该目标IAB宿主的信息可以作为一种显式的指示信息，用于向该IAB节点指示该响应信息是与该目标IAB宿主对应，可以使得该IAB节点确定收到的信息是用于建立第一F1接口的信息还是用于更新第二F1接口配置的信息。其中，该第二F1接口为IAB节点的DU和源IAB宿主的CU之间的通信接口。
第一方面的一种可行设计中，将上述第一信息承载在源IAB宿主向目标IAB宿主发送的IAB节点的切换请求消息中。通过本方法，示例性的有益效果包括：通过将第一信息承载在现有消息中，可以节省信令开销。
第一方面的一种可行设计中，将上述第二信息承载在目标IAB宿主向源IAB宿主发送的IAB节点的切换请求响应消息中。通过本方法，示例性的有益效果包括：通过将第二信息承载在现有消息中，可以节省信令开销。
第一方面的一种可行设计中，将上述第三信息承载在源IAB宿主向所述IAB节点发送的RRC重配置消息中。通过本方法，示例性的有益效果包括：通过将第三信息承载在现有消息中，可以节省信令开销。
第一方面的一种可行设计中，将上述第三信息承载在源IAB宿主向该IAB节点发送的第二F1接口的F1接口应用协议(F1 application protocol，F1AP)消息中，其中，该第二F1接口为IAB节点的DU和源IAB宿主的CU之间的通信接口。通过本方法，示例性的有益效果包括：目标IAB宿主可以将上述第二信息以F1AP封装容器(container)信元的形式，通过源IAB宿主发送给该IAB节点，可以避免源IAB宿主解析该第二信息，从而增加该第二信息传递的安全性。另外，可以避免对现有RRC重配置消息进行改动。
第一方面的一种可行设计中，当上述第三信息承载在该第二F1接口的F1AP消息中时， 该第二F1接口的F1AP消息中还包括指示信息，该指示信息用于指示上述第三信息与目标IAB宿主对应。通过本方法，示例性的有益效果包括：可以使得该IAB节点根据该指示信息，确定该第二F1接口的F1AP消息中携带的信息是用于建立第一F1接口的信息，还是用于更新第二F1接口配置的信息。
第一方面的一种可行设计中，源IAB宿主接收来自目标IAB宿主的第四信息，该第四信息包括目标IAB宿主的IP地址信息，该IP地址信息用于目标IAB宿主与IAB节点之间初始流控制传输协议(stream control transmission protocol，SCTP)偶联(association)的建立。源IAB宿主收到该IP地址信息后，向IAB节点发送第五信息，该第五信息包括该IP地址信息。通过本方法，示例性的有益效果包括：通过目标IAB宿主向IAB节点发送自己的IP地址信息，可以使得IAB节点根据该IP地址信息，快速建立与目标IAB宿主之间的SCTP偶联，也提高了目标IAB宿主与IAB节点之间SCTP偶联建立的成功率。
第一方面的一种可行设计中，该IP地址信息包括以下中至少一个：用于该第一F1接口的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数。其中，该第一F1-C接口为该第一F1接口的控制面接口，第一F1-U接口为该第一F1接口的用户面接口,上述F1-C业务包括经过该第一F1-C接口的业务，上述F1-U业务包括经过第一F1-U接口的业务。通过本方法，示例性的有益效果包括：使得目标IAB宿主可以根据需要选择某一种IP地址信息，再通过源IAB宿主将该IP地址信息发送给IAB节点。
第一方面的一种可行设计中，上述第四信息承载在目标IAB宿主向源IAB宿主发送的IAB节点的切换请求响应消息中。通过本方法，示例性的有益效果包括：通过将第二信息承载在现有消息中，可以节省信令开销。
第一方面的一种可行设计中，上述第五信息承载在源IAB宿主向IAB节点发送的RRC重配置消息中。通过本方法，示例性的有益效果包括：通过将第二信息承载在现有消息中，可以节省信令开销。
第一方面的一种可行设计中，源IAB宿主接收来自目标IAB宿主的第六信息，该第六信息包括用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息。源IAB宿主收到该第六信息后，向IAB节点发送第七信息，该第七信息包括该请求信息。进一步的，源IAB宿主接收来自IAB节点的用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息。其中，该IAB节点下属设备包括该IAB节点的IAB子节点或者接入该IAB节点的终端设备。源IAB宿主收到该响应信息后，向目标IAB宿主发送该响应信息。通过本方法，示例性的有益效果包括：通过源IAB宿主与目标IAB宿主交互关于IAB节点下属设备上下文的相关信息，可以使目标IAB宿主更快地获取IAB节点下属设备上下文，从而实现高效的切换。
第一方面的一种可行设计中，上述用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息包括以下中至少一个：IAB节点下属设备对应的F1接口应用协议标识，该IAB节点服务的辅小区(secondary cell，Scell)建立列表，该IAB节点和该IAB节点下属设备之间的信令无线承载(signaling radio bearer，SRB)建立列表，该IAB节点和该IAB节点下属设备之间的数据无线承载(data radio bearer，DRB)建立列表，该IAB节点和该IAB节点下属设备之间的回传无线链路控制信道(backhaul RLC channel，BH RLC CH) 建立列表，该IAB节点的用户面数据路由规则，该IAB节点的用户面承载映射规则。通过本方法，示例性的有益效果包括：目标IAB宿主可以通过携带用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的相关信息的请求消息，向源IAB宿主隐式指示请求在该IAB节点和/或该目标IAB宿主中建立IAB节点下属设备上下文，并通过源IAB宿主向IAB节点提供在该IAB节点和/或该目标IAB宿主中建立IAB节点下属设备上下文所需的信息。
第一方面的一种可行设计中，上述用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息包括以下中至少一个：该IAB节点为该IAB节点下属设备分配的小区无线网络临时标识(cell radio network temporary identifier，C-RNTI)，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的DRB列表，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的SRB列表，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的BH RLC CH列表、建立成功或建立失败的该IAB节点服务的Scell列表。通过本方法，示例性的有益效果包括：可以使得目标宿主节点获得在该IAB节点和/或该目标IAB宿主中建立IAB节点下属设备上下文的相关信息，提前在该IAB节点和/或该目标IAB宿主中建立好IAB节点下属设备上下文。
第一方面的一种可行设计中，上述第七信息承载在源IAB宿主向IAB节点发送的RRC重配置消息中。通过本方法，示例性的有益效果包括：通过将第二信息承载在现有消息中，可以节省信令开销。
第一方面的一种可行设计中，上述第七信息和上述第三信息承载在同一条消息中。通过本方法，示例性的有益效果包括：通过将第三信息和第七信息合并，可以节省信令开销。另外，将第三信息和第七信息一起发送，可以更快地建立起IAB节点与目标IAB宿主之间的数据通信，从而提高IAB网络的通信效率。
第一方面的一种可行设计中，源IAB宿主接收来自该目标IAB宿主的第六信息，具体是，源IAB宿主通过核心网设备接收来自该目标IAB宿主的该第六信息。通过本方法，示例性的有益效果包括：使得源IAB宿主和目标IAB宿主可以通过核心网设备交互该第六信息，保证了该IAB节点与该目标IAB宿主之间该IAB节点下属设备上下文的建立。
第一方面的一种可行设计中，源IAB宿主向该目标IAB宿主发送该用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息，具体是，通过核心网设备向该目标IAB宿主发送该用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息。通过本方法，示例性的有益效果包括：使得源IAB宿主和目标IAB宿主可以通过核心网设备交互该响应信息，保证了该IAB节点与该目标IAB宿主之间该IAB节点下属设备上下文的建立。
第一方面的一种可行设计中，源IAB宿主接收来自该目标IAB宿主的第四信息，具体是，源IAB宿主通过核心网设备接收来自该目标IAB宿主的该第四信息。通过本方法，示例性的有益效果包括：使得源IAB宿主和目标IAB宿主可以通过核心网设备交互该第四信息，保证了该IAB节点与目标IAB宿主之间初始SCTP偶联的快速建立。
第一方面的一种可行设计中，源IAB宿主向该IAB节点的目标IAB宿主发送第一信息，具体是，源IAB宿主通过核心网设备向该IAB节点的目标IAB宿主发送该第一信息。通过本方法，示例性的有益效果包括：使得源IAB宿主和目标IAB宿主可以通过核心网设备交互该第一信息，保证了该第一FI接口的建立。
第一方面的一种可行设计中，源IAB宿主接收来自该目标IAB宿主的第二信息，具体是， 源IAB宿主通过核心网设备接收来自该目标IAB宿主的该第二信息。通过本方法，示例性的有益效果包括：使得源IAB宿主和目标IAB宿主可以通过核心网设备交互该第二信息，保证了该IAB节点可以获得目标IAB宿主针对第一信息的反馈信息。
第二方面，本申请提供了一种通信方法，该方法可以包括：IAB节点接收来自目标IAB宿主的该目标IAB宿主的IP地址信息。该IP地址信息用于目标IAB宿主与IAB节点之间初始SCTP偶联的建立。通过本方法，示例性的有益效果包括：通过目标IAB宿主向IAB节点发送自己的IP地址信息，可以使得IAB节点根据该IP地址信息，快速建立与目标IAB宿主之间的SCTP偶联，也提高了目标IAB宿主与IAB节点之间SCTP偶联建立的成功率。
第二方面的一种可行设计中，该IP地址信息包括以下中至少一个：用于该第一F1接口的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数。其中，该第一F1接口指的是该IAB节点的DU和该目标IAB宿主的CU之间的通信接口，该第一F1-C接口为该第一F1接口的控制面接口，第一F1-U接口为该第一F1接口的用户面接口,上述F1-C业务包括经过该第一F1-C接口的业务，上述F1-U业务包括经过第一F1-U接口的业务。通过本方法，示例性的有益效果包括：使得目标IAB宿主可以根据需要选择某一种IP地址信息，再通过源IAB宿主将该IP地址信息发送给IAB节点。
第二方面的一种可行设计中，上述目标IAB宿主的IP地址信息承载在目标IAB宿主向源IAB宿主发送的IAB节点的切换请求响应消息中。通过本方法，示例性的有益效果包括：通过将目标IAB宿主的IP地址信息承载在现有消息中，可以节省信令开销。
第二方面的一种可行设计中，上述目标IAB宿主的IP地址信息承载在源IAB宿主向IAB节点发送的RRC重配置消息中。通过本方法，示例性的有益效果包括：通过将目标IAB宿主的IP地址信息承载在现有消息中，可以节省信令开销。
第二方面的一种可行设计中，源IAB宿主接收来自该目标IAB宿主的目标IAB宿主的IP地址信息，具体是，源IAB宿主通过核心网设备接收来自该目标IAB宿主的该目标IAB宿主的IP地址信息。通过本方法，示例性的有益效果包括：使得源IAB宿主和目标IAB宿主可以通过核心网设备交互该目标IAB宿主的IP地址信息，保证了该IAB节点与目标IAB宿主之间初始SCTP偶联的快速建立。
第三方面，本申请提供了一种通信方法，该方法可以包括：IAB节点的目标IAB宿主接收来自该IAB节点的源IAB宿主的第一信息，该第一信息包括用于建立第一F1接口的请求信息。目标IAB宿主向该源IAB宿主发送第二信息，该第二信息包括该请求信息的反馈信息。其中，该第一F1接口为该IAB节点的分布式单元和该目标IAB宿主的集中式单元之间的通信接口。
第三方面的一种可行设计中，目标IAB宿主通过该源IAB宿主向该IAB发送该第一F1接口的IP地址信息，该第一F1接口的IP地址信息用于该目标IAB宿主与该IAB节点之间初始流控制传输协议偶联的建立。
第三方面的一种可行设计中，目标IAB宿主通过该源IAB宿主向该IAB节点发送用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息。随后，目标IAB宿主通过该源IAB宿主接收来自该IAB节点的用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息。其中，该IAB节点下属设备包括该IAB 节点的IAB子节点或者接入该IAB节点的终端设备。
第三方面的一种可行设计中，目标IAB宿主根据IP地址与IAB节点建立初始SCTP偶联，其中，该IP地址是第四信息中携带的IP地址信息中包含的IP地址。
第四方面，本申请提供了一种通信方法，该方法可以包括：IAB节点接收来自源IAB宿主的第三信息，该第三信息包括用于建立第一F1接口的响应信息。其中，该第一F1接口为该IAB节点的分布式单元和该目标IAB宿主的集中式单元之间的通信接口。
第四方面的一种可行设计中，当该用于建立第一F1接口的响应信息承载在源IAB宿主向该IAB节点发送的第二F1接口的应用协议消息中时，且该第二F1接口的应用协议消息中包括指示信息，该指示信息用于指示该第二F1接口的应用协议消息中包括的信息是与该目标IAB宿主对应的信息或者是用于建立第一F1接口的信息，IAB节点根据该指示信息，确定该第二F1接口的应用协议消息中包括的信息是与该目标IAB宿主对应的信息或者是用于建立第一F1接口的信息。其中，该第二F1接口为该IAB节点的DU和该源IAB宿主的CU之间的通信接口。
第四方面的一种可行设计中，IAB节点接收来自源IAB宿主的第五信息，该第五信息包括该第一F1接口的IP地址信息，该第一F1接口的IP地址信息用于该目标IAB宿主与该IAB节点之间初始流控制传输协议偶联的建立。
第四方面的一种可行设计中，IAB节点根据IP地址与目标IAB宿主建立初始SCTP偶联，其中，该IP地址是根据第五信息获得的。
第四方面的一种可行设计中，IAB节点接收来自源IAB宿主的第七信息，该第七信息包括用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息。随后，IAB节点通过该源IAB宿主向该目标IAB宿主发送用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息。其中，该IAB节点下属设备包括该IAB节点的IAB子节点或者接入该IAB节点的终端设备。
第五方面，本申请提供一种通信装置，该装置包括用于执行第一方面至第四方面的方法及其任一设计中的任一种方法的模块。
第六方面，本申请提供一种通信装置，包括处理器和存储器，该处理器和该存储器耦合，该处理器用于实现第一方面至第四方面的方法及其任一设计中的任一种方法。第七方面，本申请提供一种通信装置，包括至少一个处理器和接口电路，该接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置，该处理器通过逻辑电路或执行代码指令用于实现第一方面至第四方面的方法及其任一设计中的任一种方法。
在一个可能的设计中，该装置可以是第一方面至第四方面的方法及其任一设计中的任一种方法中的IAB节点或者源IAB宿主或者目标IAB宿主或者是其中的芯片或者集成电路。
可选的，该通信装置还可以包括至少一个存储器，该存储器存储有涉及的程序指令。
第八方面，本申请提供一种通信装置，该装置具有实现上述第一方面至第四方面的方法及其任一设计中的方法中的任一种方法的功能或操作，所述功能或操作可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能或操作相对应的单元(模块)，比如包括收发单元和处理单元。
第九方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质中存储有涉及的程序指令，该涉及的程序指令被运行时，以使得该通信装置实现第一方面至第四方面的 方法及其任一设计中的任一种方法。
第十方面，本申请提供了一种计算机程序产品，该计算机程序产品包含涉及的程序指令，该涉及的程序指令被执行时，以实现第一方面至第四方面的方法及其任一设计中的任一种方法。
第十一方面，本申请还提供一种芯片，所述芯片用于实现第一方面至第四方面的方法及其任一设计中的任一种方法。
第十二方面，本申请提供了一种通信系统，该通信系统包括第五方面至第八方面及其任一设计中至少一种通信装置。
附图说明
可以包括在说明书中并且构成说明书的一部分的附图与说明书一起示出了本申请的示例性实施例，或特征和方面，并且用于解释本申请的原理，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以包括根据这些附图获得其他的附图。
图1A是本申请一种可能的通信系统的示意图；
图1B是本申请实施例提供的一种IAB宿主的示意图；
图1C是本申请实施例提供的IAB网络中的控制面协议栈的示意图；
图1D是本申请实施例提供的IAB网络中的用户面协议栈的示意图；
图1E是本申请实施例提供的一种IAB节点切换的示意图；
图2是本申请实施例提供的一种通信方法的示意图；
图3是本申请实施例提供的一种通信方法的示意图；
图4是本申请实施例提供的一种通信方法的示意图；
图5是本申请实施例提供的一种通信装置的示意性框图；
图6是本申请实施例提供的一种通信装置的示意性框图；
图7是本申请实施例提供的一种装置的示意性框图。
具体实施方式
相较于第四代移动通信系统，第五代移动通信(5G)针对网络各项性能指标，全方位得都提出了更严苛的要求。例如，容量指标提升1000倍，更广的覆盖需求、超高可靠超低时延等。一方面，考虑到高频载波频率资源丰富，在热点区域，为满足5G超高容量需求，利用高频小站组网愈发流行。高频载波传播特性较差，受遮挡衰减严重，覆盖范围不广，故而需要大量密集部署小站，相应地，为这些大量密集部署的小站提供光纤回传的代价很高，施工难度大，因此需要经济便捷的回传方案；另一方面，从广覆盖需求的角度出发，在一些偏远地区提供网络覆盖，光纤的部署难度大，成本高，也需要设计灵活便利的接入和回传方案。接入回传一体化(Integrated access and backhaul,IAB)技术为解决上述两个问题提供了思路：其接入链路(Access Link)和回传链路(Backhaul Link)皆采用无线传输方案，避免光纤部署。在IAB网络中，中继节点RN(RN，Relay Node)或者叫IAB节点(IAB node)，可以为用户设备(UE，User equipment)提供无线接入服务，所述UE的业务数据由IAB节点通过无线回传链路连接到宿主节点(IAB donor)或者说宿主基站(DgNB，Donor gNodeB)传输。使用IAB节点，可以使得进行接入和回传共享天线，减少基站的天线数目。
下面将结合附图，对本申请实施例进行描述，附图中以虚线标识的特征或内容可理解为本申请实施例的可选操作或者可选结构。
图1A中的用户设备可以是接入终端设备、用户单元、用户站、移动站、移动台、远方站、远程终端设备、移动设备、用户终端设备、无线终端设备、用户代理、或者用户装置等。还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备、连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备(如智能手表、智能手环等)、还可以为智能家具或家电、5G网络中的终端设备、未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备、或者车联网(vehicle to everything，V2X)中的车辆设备,客户前置设备(customer premises equipment，CPE)等，本申请对用户设备的具体实现形式并不做限定。
图1A中的IAB节点可以由移动终端(mobile termination，MT)和分布式单元DU(distributed unit，DU)组成，其中，当IAB节点面向其父节点时，可以被看做是终端设备，即MT的角色；当IAB节点面向其下属设备(下属设备可能是另一IAB子节点，或者普通UE)时，其可被看做网络设备，即作为DU的角色。
图1A中的IAB宿主(IAB donor)可以为宿主基站，IAB宿主在5G网络中可以简称为DgNB(即donor gNodeB)。IAB宿主可以是一个完整的实体，还可以是以集中式单元(centralized unit，CU)(本申请中简称为Donor-CU或者gNB-CU)和分布式单元(distributed unit，DU)(本申请中简称为Donor-DU或者gNB-DU)分离的形态存在，如图1B所示，IAB宿主可以是位于5G无线接入网(5G radio access network,5G RAN)中的gNB。该IAB宿主可以是由gNB-CU和gNB-DU组成。gNB-CU和gNB-DU通过F1接口相连，F1接口又可以进一步包括控制面接口(F1-C)和用户面接口(F1-U)。CU和核心网之间通过下一代(next generation，NG)接口相连。其中，gNB-CU或者Donor-CU还可以是以用户面(User plane，UP)(本申请中简称为CU-UP)和控制面(Control plane，CP)(本申请中简称为CU-CP)分离的形态存在，即gNB-CU或者Donor-CU由CU-CP和CU-UP组成。一个gNB-CU可以包括一个gNB-CU-CP和至少一个gNB-CU-UP。或者，一个Donor-CU可以包括一个Donor-CU-CP和至少一个Donor-CU-UP。
图1A中的网管设备可以为操作、管理和维护网元(operation,administration and maintenance，OAM)。网管设备可以包括网元管理系统(element management system，EMS)，网络管理系统(network management system，NMS)。图1B所示，网管设备可以是位于下一代核心网(Next Generation Core，NGC)或者5G核心网(5G core，5GC)中的功能网元。或者，网管设备也可以是部署在5GC后面的骨干网中的功能网元，或者，网管设备还可以部署在其他位置，本申请并不限定网管设备具体部署的位置。
IAB节点经IAB宿主连接到核心网。例如，在独立组网(standalone，SA)的5G架构下，IAB节点经IAB宿主连接到5GC。在双连接(dual connectivity,DC)或者多连接(Multi-Connectivity，MC)的5G架构下(例如：非独立组网(non-standalone，NSA)，或者NR-NR DC场景等)，主路径上，IAB节点可以经演进型基站(evolved NodeB，eNB)连接到演进分组核心网(evolved packet core，EPC)，也可以经IAB宿主连接到5G核心网。
为了保证业务传输的可靠性，IAB网络支持多跳IAB节点和多连接IAB节点组网。因此，在终端和IAB宿主之间可能存在多条传输路径。在一条路径上，IAB节点之间，以及IAB节点和IAB节点连接的IAB宿主之间有确定的层级关系，每个IAB节点将为其提供回传服务 的节点视为父节点。相应地，每个IAB节点可视为其父节点的子节点。
示例性的，参见图1A，IAB节点1的父节点为IAB宿主，IAB节点1又为IAB节点2和IAB节点3的父节点，IAB节点2和IAB节点3均为IAB节点4的父节点，IAB节点5的父节点为IAB节点2。终端的上行数据包可以经一个或多个IAB节点传输至IAB宿主后，再由IAB宿主发送至移动网关设备(例如5G网络中的用户面功能(user plane function，UPF)网元)，下行数据包将由IAB宿主从移动网关设备处接收后，再经一个或多个IAB节点发送至终端。终端1和IAB宿主之间数据包的传输有两条可用的路径，分别为：终端1→IAB节点4→IAB节点3→IAB节点1→IAB宿主，终端1→IAB节点4→IAB节点2→IAB节点1→IAB宿主。终端2和IAB宿主之间数据包的传输有三条可用的路径，分别为：终端2→IAB节点4→IAB节点3→IAB节点1→IAB宿主，终端2→IAB节点4→IAB节点2→IAB节点1→IAB宿主，终端2→IAB节点5→IAB节点2→IAB节点1→IAB宿主。IAB节点到IAB宿主的上行路径上的中间IAB节点都可以称之为IAB节点的上游节点，例如图1A中的IAB节点1和IAB节点2都可以称之为IAB节点5的上游IAB节点。示例性的，IAB节点的下属设备可以包括直接接入该IAB节点的设备，例如IAB节点的子节点或者接入该IAB节点的UE。图1A中的IAB节点2和IAB节点3可以称之为IAB节点1的下属设备，IAB节点5可以称之为IAB节点2的下属设备，终端1和终端2可以称之为IAB节点4的下属设备，终端1可以称之为IAB节点4的下属设备。
可以理解的是，在IAB网络中，终端和IAB宿主之间的一条传输路径上，可以包含一个或多个IAB节点。每个IAB节点需要维护面向父节点的无线回传链路，还需要维护和子节点的无线链路。若一个IAB节点是终端接入的节点，该IAB节点和子节点(即终端)之间是无线接入链路。若一个IAB节点是为其他IAB节点提供回传服务的节点，该IAB节点和子节点(即其他IAB节点)之间是无线回传链路。示例性的，参见图1A，在路径“终端1→IAB节点4→IAB节点3→IAB节点1→IAB宿主”中，终端1通过无线接入链路接入IAB节点4，IAB节点4通过无线回传链路接入IAB节点3，IAB节点3通过无线回传链路接入IAB节点1，IAB节点1通过无线回传链路接入IAB宿主。
上述IAB组网场景仅仅是示例性的，在多跳和多连接结合的IAB场景中，IAB组网场景还有更多其他的可能性，例如，IAB宿主和另一IAB宿主下的IAB节点组成双连接为终端服务等，此处不再一一列举。
本申请实施例中的接入IAB节点是指终端接入的IAB节点，中间IAB节点是指为IAB节点(例如，接入IAB节点或其他中间IAB节点)提供无线回传服务的IAB节点。示例性的，参见图1A，在路径终端1→IAB节点4→IAB节点3→IAB节点1→IAB宿主”中，IAB节点4为接入IAB节点，IAB节点3和IAB节点1为中间IAB节点。需要说明的是，一个IAB节点针对接入该IAB节点的终端而言，是接入IAB节点。针对接入其他IAB节点的终端，是中间IAB节点。因此，一个IAB节点具体是接入IAB节点还是中间IAB节点，并不是固定的，需要根据具体的应用场景确定。
图1C和图1D分别是本申请实施例提供的IAB网络中的控制面协议栈的示意图和用户面协议栈的示意图，下面结合图1C和图1D进行说明。
对于控制面而言，如图1C所示，终端1和IAB2-DU之间建立有Uu接口，对等的协议层包括RLC层、MAC层和PHY层。IAB2-DU和IAB donor CU 1建立有F1-C接口，对等的协议层包括F1应用协议(F1 application protocol，F1AP)层、流控制传输协议(stream control transmission protocol，SCTP)层。IAB donor DU 1和IAB donor CU 1之间通过有线连接，对 等的协议层包括互联网协议IP(internet protocol)层、L2和L1。IAB node 2和IAB node 3之间、IAB node 3和IAB node 1之间，以及IAB node 1和IAB donor DU 1之间均建立有BL，对等的协议层包括回传适配协议(Bakhaul Adaptation Protocol，BAP)层、RLC层、MAC层以及PHY层。另外，终端1和IAB donor CU 1之间建立有对等的RRC层和PDCP层，IAB2-DU和IAB donor DU 1之间建立有对等的IP层。
可以看出，IAB网络的控制面协议栈与单空口的控制面协议栈相比，接入IAB节点的DU实现了单空口的gNB-DU的功能(即与终端建立对等RLC层、MAC层和PHY层的功能，以及与CU建立对等的F1AP层、SCTP层的功能)。可以理解，IAB网络中接入IAB节点的DU实现了单空口的gNB-DU的功能；IAB donor CU实现了单空口的gNB-CU的功能。
在控制面上，RRC消息封装在接入IAB节点和IAB donor CU之间的F1AP消息中传输。具体地，在上行方向上，终端1将RRC消息封装在PDCP协议数据单元(protocol data unit，PDU)中，并依次经过RLC层、MAC层和PHY层的处理后发送至IAB2-DU。IAB2-DU依次经过PHY层、MAC层和RLC层的处理后得到PDCP PDU，将PDCP PDU封装在F1AP消息中，并依次经过SCTP层、IP层处理后得到IP包，IAB2-MT将IP包分别通过BAP层、RLC层、MAC层和PHY层的处理后发送至IAB3-DU。IAB3-DU依次经过PHY层、MAC层、RLC层和BAP层的处理后得到IP包，然后IAB3-MT采用类似于IAB2-MT的操作，将该IP包发送至IAB1-DU，同理，IAB1-MT将该IP包发送至IAB donor DU 1。IAB donor DU 1解析得到IP包后，将该IP包发送至IAB donor CU 1，IAB donor CU 1将该IP包依次通过SCTP层、F1AP层和PDCP层的处理后得到RRC消息。下行方向类似，在此不再描述。
对于用户面而言，如图1D所示，终端1和IAB2-DU之间建立有Uu接口，对等的协议层包括RLC层、MAC层和PHY层。IAB2-DU和IAB donor CU 1建立有F1-U接口，对等的协议层包括GPRS用户面隧道协议(GPRS tunnelling protocol for the user plane，GTP-U)层、用户数据报协议(user datagram protocol，UDP)层。IAB donor DU 1和IAB donor CU 1之间通过有线连接，对等的协议层包括IP层、L2和L1。IAB node 2和IAB node 3之间、IAB node 3和IAB node 1之间，以及IAB node 1和IAB donor DU 1之间均建立有BL，对等的协议层包括BAP层、RLC层、MAC层以及PHY层。另外，终端1和IAB donor CU 1之间建立有对等的SDAP层和PDCP层，IAB2-DU和IAB donor DU 1之间建立有对等的IP层。
可以看出，IAB网络的用户面协议栈与单空口的用户面协议栈相比，IAB接入节点的DU实现了单空口的gNB-DU的部分功能(即与终端建立对等RLC层、MAC层和PHY层的功能，以及与IAB donor CU 1建立对等的GTP-U层、UDP层的功能)。可以理解，IAB接入节点的DU实现了单空口的gNB-DU的功能；IAB donor CU实现了单空口的gNB-CU的功能。
在用户面上，PDCP数据包封装在接入IAB节点和IAB donor CU之间的GTP-U隧道中传输。GTP-U隧道建立在F1-U接口上。
图1C和图1D以图1A所示的IAB场景下的协议栈为例进行了描述。需要说明的是，一个IAB节点可能具备一个或者多个角色，该IAB节点可以拥有该一个或者多个角色的协议栈；或者，IAB节点可以具有一套协议栈，该协议栈可以针对IAB节点的不同角色，使用不同角色对应的协议层进行处理。下面以该IAB节点拥有该一个或者多个角色的协议栈为例进行说明：
(1)普通终端的协议栈
IAB节点在接入IAB网络时，可以充当普通终端的角色。此时，该IAB节点的MT具有普通终端的协议栈，例如图1C和图1D中的终端1的协议栈，即RRC层、PDCP层、RLC 层、MAC层和PHY层，其中，控制面上，IAB节点的RRC消息是封装在IAB节点的父节点与IAB donor CU之间的F1AP消息中传输的；用户面上，IAB节点的PDCP数据包封装在IAB节点的父节点与IAB donor CU之间的GTP-U隧道中传输的。
另外，该IAB节点接入IAB网络后，该IAB节点仍然可以充当普通终端的角色，例如，与IAB donor传输自己的上行和/或下行的数据包(例如OAM数据包)，通过RRC层执行测量等等。
(2)接入IAB节点的协议栈
IAB节点在接入IAB网络后，该IAB节点可以为终端提供接入服务，从而充当一个接入IAB节点的角色，此时，该IAB节点具有接入IAB节点的协议栈，例如图1C和图1D中的IAB node 2的协议栈。
在这种情况下，该IAB节点面向其父节点的接口上可以有两套协议栈，一套是普通终端的协议栈，另一套是为终端提供回传服务的协议栈(即：接入IAB节点的协议栈)。可选的，该两套协议栈的相同的协议层可以共享，例如该两套协议栈均对应相同的RLC层，MAC层，PHY层，或者BAP层。
(3)中间IAB节点的协议栈
IAB节点在接入IAB网络后，该IAB节点可以充当一个中间IAB节点的角色，此时，该IAB节点具有中间IAB节点的协议栈，例如图1C和图1D中的IAB node 3或者IAB node 1的协议栈。
在这种情况下，该IAB节点面向其父节点的接口上可以有两套协议栈，一套是普通终端的协议栈，另一套是为子IAB节点提供回传服务的协议栈(即：中间IAB节点的协议栈)。可选的，该两套协议栈的相同的协议层可以共享，例如该两套协议栈均对应相同的RLC层，MAC层，PHY层，或者BAP层。
另外，IAB节点可以同时承担接入IAB节点和中间IAB节点的角色，例如，IAB节点可以针对某些终端是接入IAB节点，针对另一些终端而言，是中间IAB节点，此时该IAB节点可以有三套协议栈，一套为上述普通终端的协议栈，一套为接入IAB节点的协议栈，一套为中间IAB节点的协议栈。可选的，该三套协议栈的相同的协议层可以共享，例如该三套协议栈均对应相同的RLC层，MAC层，PHY层，或者BAP层。
需要说明的是，图1C和图1D以IAB网络为例进行了介绍，图1C和图1D的内容同样适用于IAB网络以外的其他类型中继网络，该中继网络的控制面协议栈架构可以参考图1C，该中继网络的用户面协议栈架构可以参考图1D。图1C和图1D中的IAB节点可以替换成中继(relay)，例如IAB node 2可以替换成中继节点2，IAB node 3可以替换成中继节点3，IAB node 1可以替换成中继节点1，IAB donor 1可以替换成宿主节点1，宿主节点具有CU和DU协议栈，其余内容与图1C和图1D中描述的内容相同，具体可以参考图1C和图1D的描述，在此不再赘述。
如图1E所示，IAB网络中的IAB节点(如图1E中的IAB node 3)可以发生切换。
IAB节点从源父节点(如图1E中的IAB node 1)切换至目标父节点(如图1E中的IAB node 2)，且改变连接的IAB宿主，即从源IAB宿主(如图1E中的IAB donor 1)切换至目标IAB宿主(如图1E中的IAB donor 2)，可以称为跨IAB宿主的切换，或者跨donor CU的切换(inter-donor CU migrating)。
IAB节点从源父节点(如图1E中的IAB node 1)切换至目标父节点(如图1E中的IAB node 2)，但不改变IAB宿主，这种切换可以称为IAB宿主内部的切换，或者donor CU内部的切 换(intra-donor CU migrating)。
IAB节点的子节点(如图1E中的IAB node 4)可以跟随该IAB节点进行切换，即也从源IAB宿主切换到目标IAB宿主。本申请实施例提供的方法适用于该IAB节点的切换，同样也适用于该IAB节点的子节点跟随该IAB节点进行切换的场景。
IAB节点的子节点的切换方法也可以参考本申请提供的IAB节点的切换方法，
本申请中，IAB节点的MT可以简称为IAB-MT,IAB节点的DU可以简称为IAB-DU，IAB宿主的CU可以简称为Donor-CU，IAB宿主的DU可以简称为Donor-DU。
本申请中，IAB节点连接的IAB宿主可以简称为IAB节点的IAB宿主。其中，该IAB节点可以直接接入该IAB宿主，或者，该IAB节点可以通过其他IAB节点连接到该IAB宿主。
本申请中，IAB节点连接的IAB宿主可以简称为IAB节点的IAB宿主。IAB节点的IAB宿主服务的小区可以包括IAB宿主的DU所服务的小区或者由IAB宿主的DU部署的小区。其中，该IAB节点可以直接接入该IAB宿主，或者，该IAB节点可以通过其他IAB节点连接到该IAB宿主。
图2所示为本申请的一种实施例的通信方法，该通信方法200包括：
S201：IAB节点向源IAB宿主发送测量报告。
其中，测量报告可以用于上报邻区的信号质量测量结果。测量报告可以携带在RRC消息中，该RRC消息在源父节点和源IAB宿主之间传输时，可以封装在源父节点和源IAB宿主之间的F1AP消息中。
S202：源IAB宿主向目标IAB宿主发送IAB节点的切换请求消息。
源IAB宿主基于测量报告确定IAB节点(或IAB-MT)将要切换的目标父节点，向目标宿主节点发送切换请求。该IAB节点的切换请求消息用于向目标IAB宿主请求将该IAB节点(或IAB-MT)从源IAB宿主切换至该目标IAB宿主。或者，该IAB节点的切换请求消息用于向目标IAB宿主请求将该IAB节点(或IAB-MT)从源父节点切换至该目标父节点。
S203：目标IAB宿主向源IAB宿主发送IAB节点的切换请求响应消息。
该IAB节点的切换请求响应消息用于向源IAB宿主指示该目标IAB宿主同意该IAB节点的接入。其中，该切换请求响应中可以包括源IAB宿主向IAB节点(或IAB-MT)发送的RRC重配置消息中的部分或全部内容，例如，IAB节点(或IAB-MT)与目标父节点进行随机接入流程时需要的一些配置。
S204：源IAB宿主通过源父节点向IAB节点(或IAB-MT)发送RRC重配置消息。
其中，RRC重配置消息包括IAB节点(或IAB-MT)与目标父节点进行随机接入流程时需要的一些配置。该RRC重配置消息在源父节点和源IAB宿主之间传输时，可以封装在源父节点和源IAB宿主之间的F1AP消息中。
S205：IAB节点(或IAB-MT)与目标父节点之间执行随机接入流程。
通过S205，IAB节点(或IAB-MT)通过目标父节点与目标IAB宿主之间可以建立RRC连接。
S206：IAB节点(或IAB-MT)通过目标父节点向目标IAB宿主发送RRC重配置完成消息。
其中，RRC重配置完成消息用于向目标宿主节点指示RRC连接建立完成。
其中，RRC重配置完成消息在目标父节点和目标宿主节点之间传输时，可以封装在目标 父节点和目标宿主节点之间的F1AP消息中。
S207：IAB节点和目标IAB宿主建立初始SCTP偶联。
示例性的，IAB节点可以使用网管设备配置的多个IP地址与目标IAB宿主建立初始SCTP偶联。例如，IAB节点可以从多个IP地址中选择一个IP地址与目标IAB宿主建立初始SCTP偶联。当IAB节点使用其中一个IP地址与目标IAB宿主建立初始SCTP偶联失败后，IAB节点可以重新选择一个IP地址，继续与目标IAB宿主建立初始SCTP偶联。
S208：IAB节点向目标IAB宿主发送F1接口建立请求消息。
IAB节点可以通过目标父节点向目标IAB宿主发送F1接口建立请求。示例性的，该F1接口建立请求中携带有用于建立第一F1接口的相关信息。该F1接口建立请求用于向目标IAB宿主请求建立第一F1接口。该第一F1接口为该IAB节点的DU和该目标IAB宿主的CU之间的通信接口。该F1接口建立请求消息中包括的内容具体可以参考第三代合作伙伴项目(the 3rd generation partnership project,3GPP)技术标准(technical standard,TS)38.473V16.1.0版本中的9.2.1.4章节。
S209：目标IAB宿主向IAB节点发送F1接口建立响应消息。
目标IAB宿主可以通过目标父节点向IAB节点发送F1接口建立响应。示例性的，该F1接口建立响应中携带有用于建立第一F1接口的相关信息。该F1接口建立响应用于向IAB节点指示该目标IAB宿主同意建立该第一F1接口。该F1接口建立响应消息中包括的内容具体可以参考3GPP TS 38.473V16.1.0版本中的9.2.1.5章节。
S210：目标IAB宿主向IAB节点发送配置更新信息。
可选的，在IAB节点与目标IAB宿主之间完成F1接口建立之后，目标IAB宿主还可以向IAB节点发送IAB-DU的配置更新信息，该IAB-DU配置更新信息可以承载在目标IAB宿主(或者目标Donor CU)发送给IAB节点的CU配置更新(GNB-CU CONFIGURATION UPDATE)信息中。
图3所示为本申请的一种实施例的通信方法，该通信方法300包括：
S301：IAB节点的源IAB宿主向该IAB节点的目标IAB宿主发送第一信息。
该IAB节点可以是直接接入到该源IAB宿主，或者，该IAB节点可以是通过一个或者多个上游IAB节点连接到该源IAB宿主。该目标IAB宿主可以是源IAB宿主根据来自IAB节点的测量报告确定的。同样，在IAB节点切换到目标IAB宿主之后，该IAB节点可以是直接接入到该目标IAB宿主，或者，该IAB节点可以是通过一个或者多个上游IAB节点连接到该目标IAB宿主。
该IAB节点可以是需要切换父节点的切换IAB节点，即该源IAB宿主确定该切换IAB节点需要从源父节点切换至目标父节点。或者，该IAB节点也可以是该切换IAB节点的子节点，即该IAB节点可以跟随该切换IAB节点一起切换。例如，该IAB节点可以是图1E左图中的IAB node 3，也可以是图1E左图中的IAB node 4。
具体的，可以是IAB节点的源Donor-CU向该IAB节点的目标Donor-CU发送该第一信息。示例性的，第一信息可以称之为F1切换请求。
示例性的，源IAB宿主和目标IAB宿主之间可以通过X2接口或Xn接口交互该第一信息。X2接口一般指的是eNB和eNB之间的接口，Xn接口一般指的是gNB和gNB之间的接口。该第一信息可以承载在源IAB宿主和目标IAB宿主之间的X2接口应用协议(X2 application protocol，X2AP)消息或Xn接口应用协议(Xn application protocol，XnAP)消息 中。示例性的，该第一信息可以携带在源IAB宿主向目标IAB宿主发送的IAB节点的切换请求消息中(IAB节点的切换请求消息可以参考S202中的解释)。或者，该第一信息可以封装成F1AP信元容器(container)后，再携带在X2AP消息或者XnAP消息中。通过将第一信息，承载在现有消息中，可以节省信令开销。
可选的，源IAB宿主和目标IAB宿主之间可以通过与核心网设备之间的S1接口或Ng接口中转并交互该第一信息。S1接口一般指的是eNB和EPC之间的接口，Ng接口一般指的是gNB和NGC之间的接口。示例性的，源IAB宿主通过S1接口或Ng接口向核心网设备发送该第一信息，核心网设备收到该第一信息后，再通过S1接口或Ng接口向目标IAB宿主转发该第一信息。其中，核心网设备可以是移动性管理实体(mobility management entity，MME)或者接入管理功能网元(access management function，AMF)。示例性的，该第一信息可以承载在源IAB宿主发送给核心网设备的切换请求消息(handover required)以及和核心网设备发送给目标IAB宿主的切换请求消息(handover request)中。通过本设计，可以使得源IAB宿主和目标IAB宿主可以通过核心网设备交互该第一信息，保证了该第一FI接口的建立。
该第一信息包括用于建立第一F1接口的请求信息。例如，该第一信息可以为F1接口建立请求(F1SETUP REQUEST)。该第一F1接口可以指的该IAB-DU和该目标Donor-CU之间的通信接口。该用于建立第一F1接口的请求信息可以包括F1建立请求消息(F1建立请求消息可以参考S208中的解释)中的全部或部分内容。具体的，该用于建立第一F1接口的请求信息可以包括以下至少一种信息：IAB-DU标识(ID)，IAB-DU名称(name)，该IAB节点服务的小区的服务小区信息(served cell information of a cell served by the IAB node)，该IAB节点的DU发送的系统信息配置(如同步信号和PBCH块(synchronization signal and physical broadcast channel block，SSB)相关配置)，该IAB节点的DU所支持的RRC版本，该IAB节点的DU的传输层地址信息。其中，该SSB相关配置可以包括SSB频率，SSB周期，SSB载波间隔，SSB偏置(Offset)，或者SSB持续时间(Duration)等。示例性的，IAB节点服务的小区可以包括IAB节点的DU所服务的小区或者由IAB节点的DU部署的小区。根据本设计，通过在用于建立第一F1接口的请求信息中携带用于建立第一F1接口的相关信息，向目标IAB宿主隐式指示请求建立该第一F1接口，并向目标IAB宿主提供建立该第一F1接口所需的信息。
该用于建立第一F1接口的请求信息中包括的信息可以是源IAB宿主事先从IAB节点获取的。例如，源IAB宿主中保存有之前IAB节点对其发起F1接口建立请求时的消息内容，或者，源IAB宿主请求IAB节点向该源IAB宿主发送该用于建立第一F1接口的请求信息中包括的全部或者部分信息。
S302：目标IAB宿主向源IAB宿主发送第二信息。
具体的，可以是IAB节点的目标Donor-CU向该IAB节点的源Donor-CU发送该第二信息。示例性的，第二信息可以称之为F1切换响应。
示例性的，源IAB宿主和目标IAB宿主之间可以通过X2或Xn接口交互该第二信息。该第二信息可以承载在源IAB宿主和目标IAB宿主之间的X2AP或XnAP消息中。示例性的，该第二信息可以携带在目标IAB宿主向源IAB宿主发送的IAB节点的切换请求响应消息中(IAB节点的切换响应消息可以参考S203中的解释)。或者，该第二信息可以封装成F1AP信元容器(container)后，再携带在X2AP消息或者XnAP消息中。通过将第二信息，承载在现有消息中，可以节省信令开销。
可选的，源IAB宿主和目标IAB宿主之间可以通过与核心网设备之间的S1或Ng接口 中转并交互该第二信息。示例性的，目标IAB宿主通过S1或Ng接口向核心网设备发送该第二信息，核心网设备收到该第二信息后，再通过S1或Ng接口向源IAB宿主转发该第二信息。示例性的，该第二信息可以承载在目标IAB宿主发送给核心网设备的切换请求应答消息(handover request acknowledge，handover request ACK)以及和核心网设备发送给源IAB宿主的切换命令(handover command)中。通过本设计，可以使得源IAB宿主和目标IAB宿主可以通过核心网设备交互该第二信息，保证了该IAB节点可以获得目标IAB宿主针对第一信息的反馈信息。
该第二信息包括请求信息的反馈信息。该反馈信息可以是目标IAB宿主根据接收到的第一信息生成的。
示例性的，当该目标IAB宿主同意建立该第一F1接口，该反馈信息可以为用于建立第一F1接口的响应信息。例如，该反馈信息可以为F1接口建立响应(F1SETUP RESPONSE)。该用于建立第一F1接口的响应信息可以包括F1建立响应消息(F1建立响应消息可以参考S209中的解释)中的全部或部分内容。具体的，该用于建立第一F1接口的响应信息包括以下至少一种信息：用于标识该目标IAB宿主的信息，该IAB节点服务的小区的激活信息，该目标IAB宿主的CU所支持的RRC版本，该目标IAB宿主的CU的传输层地址信息，该IAB节点的DU的同步信号块发送配置(synchronization signal block transmission configuration，STC)。其中，该IAB节点服务的小区的激活信息可以包括一个或多个需要激活的小区的信息。其中，该用于标识该目标IAB宿主的信息可以包括以下任一个：目标IAB宿主的标识(ID)或名称(name)，目标IAB宿主的CU标识(ID)或名称(name)，目标IAB宿主的基站标识(gNB ID)或名称(name)。通过本设计，目标IAB宿主可以通过在用于建立第一F1接口的响应信息中携带用于建立第一F1接口的相关信息，向源IAB宿主隐式指示同意建立该第一F1接口，并通过源IAB宿主向IAB节点提供建立该第一F1接口所需的信息。另外，该用于标识该目标IAB宿主的信息可以作为一种显式的指示信息，用于向该IAB节点指示该响应信息是与该目标IAB宿主对应，可以使得该IAB节点确定收到的信息是用于建立第一F1接口的信息还是用于更新第二F1接口配置的信息。其中，该第二F1接口为IAB节点的DU和源IAB宿主的CU之间的通信接口。
示例性的，当该目标IAB宿主拒绝或者无法建立该第一F1接口，该反馈信息可以为该第一F1接口建立失败的指示信息。例如，该反馈信息可以为F1接口建立失败(F1 SETUP FAILURE)。该F1 SETUP FAILURE可以参考第三代合作伙伴项目(the 3rd generation partnership project,3GPP)技术标准(technical standard,TS)38.473 V16.1.0版本中的9.2.1.6章节。在这种情况下，可以不继续执行本申请实施例的后续操作。可选的，源IAB宿主可以根据该反馈信息，确定重新执行S301，即继续向该目标IAB宿主发送第一信息，以尝试建立该第一F1接口。或者，源IAB宿主可以根据该反馈信息，确定不重新执行S301，例如，源IAB宿主可以参照方法200进行操作。通过本设计，源IAB宿主可以根据收到的该第一F1接口建立失败的指示信息，确定该目标IAB宿主拒绝或者无法建立该第一F1接口。进一步的，源IAB宿主可以确定是否继续向该目标IAB宿主发送第一信息，以尝试建立该第一F1接口，从而提高该第一F1接口建立的成功率。
S303：源IAB宿主向IAB节点发送第三信息。
当该反馈信息为用于建立第一F1接口的响应信息时，源IAB宿主可以在收到该响应信息后，向IAB节点发送第三信息，该第三信息包括该用于建立第一F1接口的响应信息。
具体的，当该IAB节点是通过源父节点连接到该源IAB宿主时，源IAB宿主可以是通 过该IAB节点的源父节点向该IAB发送该第三信息。
示例性的，该源IAB宿主可以将该用于建立第一F1接口的响应信息承载在源IAB宿主(或者源Donor CU)向该IAB节点(或者IAB-MT)发送的RRC重配置消息中(RRC重配置消息可以参考S204中的解释)。该IAB节点的MT接收到该用于建立第一F1接口的响应信息之后，可以通过内部接口发送给该IAB节点的DU。通过将第三信息，承载在现有消息中，可以节省信令开销。
可选的，该源IAB宿主可以将该用于建立第一F1接口的响应信息承载在源IAB宿主(或者源Donor CU)向该IAB节点(或者IAB-MT)发送的其他现有RRC消息或者单独承载该响应信息的RRC消息中。该IAB节点的MT接收到该用于建立第一F1接口的响应信息之后，可以通过内部接口发送给该IAB节点的DU。
可选的，该源IAB宿主可以将该用于建立第一F1接口的响应信息承载在源IAB宿主(或者源Donor CU)向该IAB节点(或者IAB-DU)发送的第二F1接口的F1AP消息中，其中，该第二F1接口为IAB节点的DU和源IAB宿主的CU之间的通信接口。例如，当该第二信息是被封装成F1AP信元容器(container)后，再携带在X2AP消息或者XnAP消息中被目标IAB宿主发送给源IAB宿主时，该源IAB宿主可以将该第二信息作为第三信息，透传给该IAB节点。通过本设计，目标IAB宿主可以将上述第二信息以F1AP封装容器(container)信元的形式，通过源IAB宿主发送给该IAB节点，可以避免源IAB宿主解析该第二信息，从而增加该第二信息传递的安全性。另外，可以避免对现有RRC重配置消息进行改动。
当该用于建立第一F1接口的响应信息承载在该第二F1接口的F1AP消息中时，为了使得该IAB节点可以确定该第二F1接口的F1AP消息中携带的信息是用于建立第一F1接口的信息，还是用于更新第二F1接口配置的信息，该第二F1接口的F1AP消息中可以包括指示信息，该指示信息用于指示第二F1接口的F1AP消息中包括的信息是与该目标IAB宿主对应的信息或者是用于建立第一F1接口的信息。示例性的，该指示信息可以和用于建立第一F1接口的响应信息一起承载在该第二F1接口的F1AP消息中。可选的，该指示信息可以包括在用于建立第一F1接口的响应信息中，例如，可以将该用于建立第一F1接口的响应信息中包括的用于标识该目标IAB宿主的信息作为该指示信息。通过本设计，可以使得该IAB节点根据该第二F1接口的F1AP消息中携带的指示信息，确定该第二F1接口的F1AP消息中携带的信息是用于建立第一F1接口的信息，还是用于更新第二F1接口配置的信息，从而可以进行不同的后续处理。
可选的，该第二F1接口的F1AP消息中也可以不用显式携带该指示信息。例如，源IAB宿主和IAB节点之间可以规定一个新的流程，该流程是专门用于提前向该IAB节点发送来自目标IAB宿主的用于建立第一F1接口的相关信息的一套流程。例如，该IAB节点可以根据在该第二F1接口的F1AP消息之前接收的信息来确定该第二F1接口的F1AP消息中包括的信息是与该目标IAB宿主对应的信息或者是用于建立第一F1接口的信息。
示例性的，该IAB节点可以根据接收到的第二F1接口的F1AP消息中包括的指示信息，确定该第二F1接口的F1AP消息中包括的用于建立第一F1接口的响应信息是与该目标IAB宿主对应的，即确定该第二F1接口的F1AP消息中携带的信息是用于建立第一F1接口的信息，而不是用于更新第二F1接口配置的信息。该IAB节点根据接收到的第三信息配置该第一F1接口。
示例性的，第三信息可以称之为F1切换命令。
S303是可选的操作，即本实施例可以不包括这个操作。例如当该反馈信息是F1接口建 立失败信息时，不需要继续执行S303。
根据上述方法，通过源IAB宿主与目标IAB宿主交互用于建立第一F1接口的相关信息，可以使IAB节点的DU更快地获取其在目标IAB宿主上的配置信息，从而实现高效的切换。另外，目标IAB宿主也可以通过反馈信息，灵活指示该第一F1接口的建立情况，从而提高该第一F1接口建立的效率。
S304：目标IAB宿主向源IAB宿主发送第四信息。
目标IAB宿主向源IAB宿主发送第四信息的具体方法可以参考S302中目标IAB宿主向源IAB宿主发送第二信息的方法，在此不再赘述。第四信息和第二信息可以承载在同一条消息中。
该第四信息包括目标IAB宿主的IP地址信息，该IP地址信息用于目标IAB宿主与IAB节点之间初始SCTP偶联的建立。根据本方法，通过目标IAB宿主向IAB节点发送自己的IP地址信息，可以使得IAB节点根据该IP地址信息，快速建立与目标IAB宿主之间的SCTP偶联，也提高了目标IAB宿主与IAB节点之间SCTP偶联建立的成功率。
该目标IAB宿主的IP地址信息包括以下中至少一个：用于该第一F1接口的目标IAB宿主的IP地址，用于该第一F1接口的目标IAB宿主的IP地址类型，用于该第一F1接口的目标IAB宿主的IP地址前缀，用于该第一F1接口的目标IAB宿主的IP地址个数，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址类型，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址前缀，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址个数，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址类型，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址前缀，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址个数。其中，该第一F1-C接口为该第一F1接口的控制面接口，第一F1-U接口为该第一F1接口的用户面接口,上述F1-C业务包括经过该第一F1-C接口的业务，上述F1-U业务包括经过第一F1-U接口的业务。其中，IP地址类型可以包括IPv4和/或IPv6类型。通过本设计，目标IAB宿主可以根据需要选择某一种IP地址信息，再通过源IAB宿主将该IP地址信息发送给IAB节点。
其中，用于该第一F1接口的目标IAB宿主的IP地址包括该第一F1接口对应的CU端的IP地址，例如，Donor-CU的IP地址。用于该第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址包括该第一F1-C接口对应的CU端的IP地址，例如，Donor-CU-CP的IP地址。用于该第一F1-U接口或者F1-U业务的的目标IAB宿主的IP地址包括该第一F1-U接口对应的CU端的IP地址，例如，Donor-CU-UP的IP地址。
可选的，该目标IAB宿主向该源IAB宿主发送第四信息可以是基于该IAB节点的请求。例如，IAB节点向源IAB宿主发送IP地址请求信息，该IP地址请求信息用于向目标IAB宿主请求IP地址。源IAB宿主向该目标IAB宿主转发该IP地址请求信息。或者，该目标IAB宿主向该源IAB宿主发送第四信息可以是基于来自源IAB宿主的第一信息。
S305：源IAB宿主向IAB节点发送第五信息。
源IAB宿主收到该第四信息后，向IAB节点发送第五信息，该第五信息包括该IP地址信息。
源IAB宿主向IAB节点发送第五信息的具体的方法可以参考S303中源IAB宿主向IAB节点发送第三信息的方法，在此不再赘述。第五信息和第三信息可以承载在同一条消息中。
S304～S305可以是在S301～S303之前执行，也可以是在S308之后执行，本申请实施例不 限制S304～S305的执行时机。
S304和S305是可选的操作，即本实施例可以不包括这两个操作。例如还是由网管设备事先配置多个IP地址(可以参考操作S207中IP地址的分配)。
S306：目标IAB宿主向源IAB宿主发送第六信息。
该第六信息包括用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息，该请求信息用于请求在该IAB节点和/或该目标IAB宿主中建立IAB节点下属设备上下文。其中，该IAB节点下属设备包括该IAB节点的IAB子节点或者接入该IAB节点的终端设备。
该用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息可以包括F1AP流程中用户上下文建立请求消息(该用户上下文建立请求消息中包括的内容具体可以参考3GPP TS38.473 V16.1.0版本中的9.2.2.1章节)的部分或全部内容。具体的，该用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息包括以下中至少一个：IAB节点下属设备对应的F1接口应用协议标识，该IAB节点服务的Scell建立列表，该IAB节点和该IAB节点下属设备之间的SRB建立列表，该IAB节点和该IAB节点下属设备之间的DRB建立列表，该IAB节点和该IAB节点下属设备(或者IAB节点的子节点)之间的BH RLC CH建立列表，该IAB节点的用户面数据路由规则，该IAB节点的用户面承载映射规则。
通过本设计，目标IAB宿主可以通过在用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息中携带用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的相关信息，向源IAB宿主隐式指示请求在该IAB节点和/或该目标IAB宿主中建立IAB节点下属设备上下文，并通过源IAB宿主向IAB节点提供在该IAB节点和/或该目标IAB宿主中建立IAB节点下属设备上下文所需的信息。
目标IAB宿主向源IAB宿主发送第六信息的具体方法可以参考S302中目标IAB宿主向源IAB宿主发送第二信息的方法，在此不再赘述。第二信息，第四信息以及第六信息中的至少一个信息可以承载在同一条消息中，这样可以节省信令开销。另外，可以更快地建立起IAB节点与目标IAB宿主之间的数据通信，从而提高IAB网络的通信效率。
S307：源IAB宿主向IAB节点发送第七信息。
源IAB宿主收到该第六信息后，向IAB节点发送第七信息，该第七信息包括该用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息。
源IAB宿主向IAB节点发送第七信息的具体的方法可以参考S303中源IAB宿主向IAB节点发送第三信息的方法，在此不再赘述。第三信息，第五信息以及第七信息中的至少一个信息可以承载在同一条消息中，这样可以节省信令开销。另外，可以更快地建立起IAB节点与目标IAB宿主之间的数据通信，从而提高IAB网络的通信效率。
S308：IAB节点向目标IAB宿主发送第七信息的反馈信息。
该第七信息的反馈信息可以为用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息。
该用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息可以包括F1AP流程中用户上下文建立响应消息(该用户上下文建立响应消息中包括的内容具体可以参考3GPP TS38.473 V16.1.0版本中的9.2.2.2章节)的部分或全部内容。具体的，该用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息包括以下中至少一个：该IAB节点为该IAB节点下属设备分配的C-RNTI，建立成功或建立失 败的该IAB节点和该IAB节点下属设备之间的DRB列表，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的SRB列表，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的BH RLC CH列表、建立成功或建立失败的该IAB节点服务的Scell列表。
具体的，当该IAB节点是通过源父节点连接到该源IAB宿主时，该IAB节点可以先通过源父节点向源IAB宿主发送该第七信息的反馈信息，该源IAB宿主再向该目标IAB宿主发送该第七信息的反馈信息。
示例性的，该IAB节点可以将该第七信息的反馈信息承载在该IAB节点(或者IAB-MT)向该源IAB宿主(或者Donor CU)发送的任一条现有RRC消息或者单独承载该响应信息的RRC消息中。可选的，该IAB节点可以将该第七信息的反馈信息承载在IAB节点(或者IAB-DU)向该源IAB宿主(或者Donor CU)发送的第二F1接口的F1AP消息中，其中，该第二F1接口为IAB节点的DU和源IAB宿主的CU之间的通信接口。
该源IAB宿主向该目标IAB宿主发送该第七信息的反馈信息的具体方法可以参考S301中源IAB宿主向目标IAB宿主发送第一信息的方法，在此不再赘述。
可选的，该第七信息的反馈信息可以为在该IAB节点和/或该目标IAB宿主中建立IAB节点下属设备上下文失败的指示信息。例如，该反馈信息可以为上下文建立失败(CONTEXT SETUP FAILURE)。该CONTEXT SETUP FAILURE可以参考3GPP TS38.473 V16.1.0版本中的9.2.2.3章节。可选的，目标IAB宿主可以根据该反馈信息，确定重新执行S306，即继续向源IAB宿主发送第六信息，源IAB宿主继续向IAB节点发送第七信息，以尝试在该IAB节点和/或该目标IAB宿主中建立IAB节点下属设备上下文。或者，目标IAB宿主可以根据该反馈信息，确定不重新执行S306，例如，可以等IAB节点切换到目标IAB宿主之后，再尝试在该IAB节点和/或该目标IAB宿主中建立IAB节点下属设备上下文。
根据上述方法，通过源IAB宿主与目标IAB宿主交互关于IAB节点下属设备上下文的相关信息，可以使目标IAB宿主更快地获取IAB节点下属设备上下文，减少IAB节点跨donor CU切换的时间，从而实现高效的切换。
S306～S308是可选的操作，即本实施例可以不包括这三个操作。例如，该三个操作可以等到IAB节点切换至目标IAB宿主之后，再通过目标IAB宿主与IAB节点完成下属设备上下文建立。
S309：IAB节点和目标IAB宿主之间建立初始SCTP偶联。
具体的，可以是IAB节点和目标IAB宿主CU之间建立初始SCTP偶联。IAB节点使用IP地址和目标IAB宿主之间建立初始SCTP偶联。该IP地址可以是从网管设备配置的多个IP地址中选择的，或者该IP地址是根据S305中的第五信息获得的。
进一步的，该IAB节点可以将该第一F1接口的相关信息和该SCTP偶联关联起来，和/或，该IAB节点可以将在该IAB节点和/或该目标IAB宿主中建立的IAB节点下属设备上下文和该SCTP偶联关联起来。示例性的，该目标IAB宿主可以向IAB节点发送IAB-DU的配置更新信息，该IAB-DU配置更新信息可以承载在目标IAB宿主(或者目标Donor CU)发送给IAB节点的GNB-CU CONFIGURATION UPDATE信息中。该IAB节点可以根据该配置更新信息将该第一F1接口的相关信息和该SCTP偶联关联起来，和/或，将在该IAB节点和/或该目标IAB宿主中建立的IAB节点下属设备上下文和该SCTP偶联关联起来。
可选的，该IAB节点可以根据该配置更新信息删除该IAB节点DU上的其他SCTP偶联。
进一步的，后续SCTP偶联使用的IP地址也可以是根据S305中的第五信息中的IP地址信息获得的。或者，后续SCTP偶联使用的IP地址是根据目标IAB宿主(或者目标Donor CU) 发送给该IAB节点的GNB-CU CONFIGURATION UPDATE信息获得的。
S309可以是在S304～S305之后执行，也可以是在S308之后执行，本申请实施例不限制S309的执行时机。
图4所示为本申请的一种实施例的通信方法，该通信方法400包括：
S401：IAB节点的目标IAB宿主向该IAB节点的源IAB宿主发送第四信息。
具体的，可以是IAB节点的目标Donor-CU向该IAB节点的源Donor-CU发送该第二信息。
该IAB节点可以是直接接入到该源IAB宿主，或者，该IAB节点可以是通过一个或者多个上游IAB节点连接到该源IAB宿主。该目标IAB宿主可以是源IAB宿主根据来自IAB节点的测量报告确定的。同样，在IAB节点切换到目标IAB宿主之后，该IAB节点可以是直接接入到该目标IAB宿主，或者，该IAB节点可以是通过一个或者多个上游IAB节点连接到该目标IAB宿主。
该IAB节点可以是需要切换父节点的切换IAB节点，即该源IAB宿主确定该切换IAB节点需要从源父节点切换至目标父节点。或者，该IAB节点也可以是该切换IAB节点的子节点，即该IAB节点可以跟随该切换IAB节点一起切换。例如，该IAB节点可以是图1E左图中的IAB node 3，也可以是图1E左图中的IAB node 4。
示例性的，源IAB宿主和目标IAB宿主之间可以通过X2或Xn接口交互该第四信息。该第四信息可以承载在源IAB宿主和目标IAB宿主之间的X2AP或XnAP消息中。示例性的，该第四信息可以携带在目标IAB宿主向源IAB宿主发送的IAB节点的切换请求响应消息中(IAB节点的切换响应消息可以参考S203中的解释)。或者，该第四信息可以封装成F1AP信元容器(container)后，再携带在X2AP消息或者XnAP消息中。
可选的，源IAB宿主和目标IAB宿主之间可以通过与核心网设备之间的S1或Ng接口中转并交互该第四信息。示例性的，目标IAB宿主通过S1或Ng接口向核心网设备发送该第四信息，核心网设备收到该第四信息后，再通过S1或Ng接口向源IAB宿主转发该第四信息。
该第四信息包括目标IAB宿主的IP地址信息，该IP地址信息用于目标IAB宿主与IAB节点之间初始SCTP偶联的建立。可选的，该IP地址信息还可以用于目标IAB宿主与IAB节点之间后续SCTP偶联的建立。也就是说，该IP地址信息既可以包括用于初始SCTP偶联建立的IP地址，也可以包括用于后续SCTP偶联建立的IP地址。
该IP地址信息包括以下中至少一个：用于该第一F1接口的目标IAB宿主的IP地址，用于该第一F1接口的目标IAB宿主的IP地址类型，用于该第一F1接口的目标IAB宿主的IP地址前缀，用于该第一F1接口的目标IAB宿主的IP地址个数，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址类型，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址前缀，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址个数，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址类型，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址前缀，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址个数。其中，该第一F1-C接口为该第一F1接口的控制面接口，第一F1-U接口为该第一F1接口的用户面接口,上述F1-C业务包括经过该第一F1-C接口的业务，上述F1-U业务包括经过第一F1-U接口的业务。其中，IP地址类型可以包括IPv4和/或IPv6类型。
其中，用于该第一F1接口的目标IAB宿主的IP地址包括该第一F1接口对应的CU端的IP地址，例如，Donor-CU的IP地址。用于该第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址包括该第一F1-C接口对应的CU端的IP地址，例如，Donor-CU-CP的IP地址。用于该第一F1-U接口或者F1-U业务的的目标IAB宿主的IP地址包括该第一F1-U接口对应的CU端的IP地址，例如，Donor-CU-UP的IP地址。
可选的，该目标IAB宿主向该源IAB宿主发送第四信息可以是基于该IAB节点的请求。例如，IAB节点向源IAB宿主发送IP地址请求信息，该IP地址请求信息用于向目标IAB宿主请求IP地址。源IAB宿主向该目标IAB宿主转发该IP地址请求信息。或者，该目标IAB宿主向该源IAB宿主发送第四信息可以是基于来自源IAB宿主的IAB节点的切换请求消息(该IAB节点的切换请求消息可以参考S202中的解释)。
S402：源IAB宿主向IAB节点发送第五信息。
源IAB宿主收到该第四信息后，向IAB节点发送第五信息，该第五信息包括该IP地址信息。具体的，当该IAB节点是通过源父节点连接到该源IAB宿主时，源IAB宿主可以是通过该IAB节点的源父节点向该IAB发送该第五信息。
示例性的，该源IAB宿主可以将该IP地址信息承载在源IAB宿主向该IAB节点发送的RRC重配置消息中(RRC重配置消息可以参考S204中的解释)。该IAB节点的MT接收到该IP地址信息之后，可以通过内部接口发送给该IAB节点的DU。
可选的，该源IAB宿主可以将该IP地址信息承载在源IAB宿主向该IAB节点发送的第二F1接口的F1AP消息中，其中，该第二F1接口为IAB节点的DU和源IAB宿主的CU之间的通信接口。例如，当该第四信息是被封装成F1AP信元容器(container)后，再携带在X2AP消息或者XnAP消息中被目标IAB宿主发送给源IAB宿主时，该源IAB宿主可以将该第四信息作为第五信息，透传给该IAB节点。
S403：IAB节点和目标IAB宿主之间建立初始SCTP偶联。
具体的，可以是IAB节点和目标IAB宿主CU之间建立初始SCTP偶联。IAB节点使用IP地址和目标IAB宿主之间建立初始SCTP偶联。该IP地址是根据S402中的第五信息中的IP地址信息获得的。
进一步的，后续SCTP偶联使用的IP地址也可以是根据S402中的第五信息中的IP地址信息获得的。或者，后续SCTP偶联使用的IP地址是根据第一F1接口建立成功后，目标IAB宿主(或者目标Donor CU)发送给该IAB节点的GNB-CU CONFIGURATION UPDATE信息获得的。
本申请实施例提供了一种快速的SCTP偶联建立方法，通过目标IAB宿主向IAB节点发送自己的IP地址信息，可以使得IAB节点根据该IP地址信息，快速建立与目标IAB宿主之间的SCTP偶联，也提高了目标IAB宿主与IAB节点之间SCTP偶联建立的成功率。
基于上述相类似的技术构思，本申请实施例提供了一种通信设备，该通信设备可以是前述任一实施例所提供的通信方法及其任一可能的设计中的中继设备或者网络设备或者用户设备，该中继设备或者网络设备或者用户设备可以包括在前述任一实施例所提供的通信方法中，用于执行该中继设备或者网络设备或者用户设备所进行的方法步骤或操作或行为的相应的至少一个单元。其中，该至少一个单元的设置，可以与该中继设备或者网络设备或者用户设备进行的方法步骤或操作或行为具有一一对应的关系。
图5是本申请实施例提供的一种通信装置500的示意性框图，下面将结合图5，对通信装置500的结构和功能进行具体的描述。该通信装置500可以包括：发送模块501和获取模 块502。
在本申请的一示例中，该通信装置500可应用于源IAB宿主。发送模块501具体用于向IAB节点的目标IAB宿主发送第一信息，该第一信息包括用于建立第一F1接口的请求信息。获取模块502具体用于获取来自所述目标IAB宿主的第二信息，该第二信息包括上述请求信息的反馈信息。其中，第一F1接口指的是该IAB节点的DU和该目标IAB宿主的CU之间的通信接口。
其中，该用于建立第一F1接口的请求信息可以包括以下至少一种信息：IAB-DU标识(ID)，IAB-DU名称(name)，该IAB节点服务的小区的服务小区信息(served cell information of a cell served by the IAB node)，该IAB节点的DU发送的系统信息配置(如同步信号和PBCH块(synchronization signal and physical broadcast channel block，SSB)相关配置)，该IAB节点的DU所支持的RRC版本，该IAB节点的DU的传输层地址信息。其中，该SSB相关配置可以包括SSB频率，SSB周期，SSB载波间隔，SSB偏置(Offset)，或者SSB持续时间(Duration)等。
当该反馈信息为用于建立第一F1接口的响应信息时，发送模块501还可以用于向IAB节点发送第三信息，该第三信息中包括上述响应信息。
其中，该用于建立第一F1接口的响应信息包括以下至少一种信息：用于标识该目标IAB宿主的信息，该IAB节点服务的小区的激活信息，该目标IAB宿主的CU所支持的RRC版本，该目标IAB宿主的CU的传输层地址信息，该IAB节点的DU的同步信号块发送配置(synchronization signal block transmission configuration，STC)。其中，该IAB节点服务的小区的激活信息可以包括一个或多个需要激活的小区的信息。其中，该用于标识该目标IAB宿主的信息可以包括以下任一个：目标IAB宿主的标识(ID)或名称(name)，目标IAB宿主的CU标识(ID)或名称(name)，目标IAB宿主的基站标识(gNB ID)或名称(name)。
当该反馈信息为该第一F1接口建立失败的指示信息时，发送模块501还可以继续向IAB节点的目标IAB宿主发送第一信息。
可选的，该获取模块502还可以用于接收来自目标IAB宿主的第四信息，该第四信息包括目标IAB宿主的IP地址信息，该IP地址信息用于目标IAB宿主与IAB节点之间初始SCTP偶联的建立。进一步的，该发送模块501还可以用于向IAB节点发送第五信息，该第五信息包括该IP地址信息。
其中，该IP地址信息包括以下中至少一个：用于该第一F1接口的目标IAB宿主的IP地址，用于该第一F1接口的目标IAB宿主的IP地址类型，用于该第一F1接口的目标IAB宿主的IP地址前缀，用于该第一F1接口的目标IAB宿主的IP地址个数，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址类型，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址前缀，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址个数，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址类型，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址前缀，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址个数。其中，该第一F1-C接口为该第一F1接口的控制面接口，第一F1-U接口为该第一F1接口的用户面接口,上述F1-C业务包括经过该第一F1-C接口的业务，上述F1-U业务包括经过第一F1-U接口的业务。其中，IP地址类型可以包括IPv4和/或IPv6类型。
可选的，该获取模块502还可以用于接收来自目标IAB宿主的第六信息，该第六信息包 括用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息。进一步的，该发送模块501还可以用于向IAB节点发送第七信息，该第七信息包括该请求信息。进一步的，该获取模块502还可以用于接收来自IAB节点的用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息。其中，该IAB节点下属设备包括该IAB节点的IAB子节点或者接入该IAB节点的终端设备。进一步的，该发送模块501还可以用于向目标IAB宿主发送该响应信息。
其中，该用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息包括以下中至少一个：IAB节点下属设备对应的F1接口应用协议标识，该IAB节点服务的Scell建立列表，该IAB节点和该IAB节点下属设备之间的SRB建立列表，该IAB节点和该IAB节点下属设备之间的DRB建立列表，该IAB节点和该IAB节点下属设备(或者IAB节点的子节点)之间的BH RLC CH建立列表，该IAB节点的用户面数据路由规则，该IAB节点的用户面承载映射规则。该用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息包括以下中至少一个：该IAB节点为该IAB节点下属设备分配的C-RNTI，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的DRB列表，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的SRB列表，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的BH RLC CH列表、建立成功或建立失败的该IAB节点服务的Scell列表。
图6是本申请实施例提供的一种通信装置600的示意性框图，下面将结合图6，对通信装置600的结构和功能进行具体的描述。该通信装置600，可以包括获取模块601和发送模块602，可选的，还可以包括处理模块603。
在本申请的一示例中，该通信装置600可应用于目标IAB宿主。获取模块601具体用于接收来自源IAB宿主的第一信息，该第一信息包括用于建立第一F1接口的请求信息。其中，该第一F1接口为该IAB节点的分布式单元和该目标IAB宿主的集中式单元之间的通信接口。
发送模块602具体用于向源IAB宿主发送第二信息，该第二信息包括上述请求信息的反馈信息。
其中，该用于建立第一F1接口的请求信息可以包括以下至少一种信息：IAB-DU标识(ID)，IAB-DU名称(name)，该IAB节点服务的小区的服务小区信息(served cell information of a cell served by the IAB node)，该IAB节点的DU发送的系统信息配置(如同步信号和PBCH块(synchronization signal and physical broadcast channel block，SSB)相关配置)，该IAB节点的DU所支持的RRC版本，该IAB节点的DU的传输层地址信息。其中，该SSB相关配置可以包括SSB频率，SSB周期，SSB载波间隔，SSB偏置(Offset)，或者SSB持续时间(Duration)等。该用于建立第一F1接口的响应信息包括以下至少一种信息：用于标识该目标IAB宿主的信息，该IAB节点服务的小区的激活信息，该目标IAB宿主的CU所支持的RRC版本，该目标IAB宿主的CU的传输层地址信息，该IAB节点的DU的同步信号块发送配置(synchronization signal block transmission configuration，STC)。其中，该IAB节点服务的小区的激活信息可以包括一个或多个需要激活的小区的信息。其中，该用于标识该目标IAB宿主的信息可以包括以下任一个：目标IAB宿主的标识(ID)或名称(name)，目标IAB宿主的CU标识(ID)或名称(name)，目标IAB宿主的基站标识(gNB ID)或名称(name)。
可选的，该发送模块602还可以用于向源IAB宿主发送第四信息，该第四信息包括目标IAB宿主的IP地址信息，该IP地址信息用于目标IAB宿主与IAB节点之间初始SCTP偶联的建立。
其中，该IP地址信息包括以下中至少一个：用于该第一F1接口的目标IAB宿主的IP地址，用于该第一F1接口的目标IAB宿主的IP地址类型，用于该第一F1接口的目标IAB宿主的IP地址前缀，用于该第一F1接口的目标IAB宿主的IP地址个数，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址类型，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址前缀，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址个数，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址类型，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址前缀，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址个数。其中，该第一F1-C接口为该第一F1接口的控制面接口，第一F1-U接口为该第一F1接口的用户面接口,上述F1-C业务包括经过该第一F1-C接口的业务，上述F1-U业务包括经过第一F1-U接口的业务。其中，IP地址类型可以包括IPv4和/或IPv6类型。
可选的，该发送模块602还可以用于向源IAB宿主发送第六信息，该第六信息包括用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息。进一步的，该获取模块601还可以用于从源IAB宿主接收来自IAB节点的用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息。
其中，该用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息包括以下中至少一个：IAB节点下属设备对应的F1接口应用协议标识，该IAB节点服务的Scell建立列表，该IAB节点和该IAB节点下属设备之间的SRB建立列表，该IAB节点和该IAB节点下属设备之间的DRB建立列表，该IAB节点和该IAB节点下属设备(或者IAB节点的子节点)之间的BH RLC CH建立列表，该IAB节点的用户面数据路由规则，该IAB节点的用户面承载映射规则。该用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息包括以下中至少一个：该IAB节点为该IAB节点下属设备分配的C-RNTI，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的DRB列表，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的SRB列表，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的BH RLC CH列表、建立成功或建立失败的该IAB节点服务的Scell列表。
可选的，该通信装置600还可以包括处理模块603。该处理模块603具体用于根据IP地址与IAB节点建立初始SCTP偶联。其中，该IP地址是第四信息中携带的IP地址信息中包含的IP地址。
在本申请的另一示例中，该通信装置600可应用于IAB节点。获取模块601具体用于接收来自源IAB宿主的第三信息，该第三信息包括该用于建立第一F1接口的响应信息。其中，该第一F1接口为该IAB节点的分布式单元和该目标IAB宿主的集中式单元之间的通信接口。
当该用于建立第一F1接口的响应信息承载在源IAB宿主(或者源Donor CU)向该IAB节点(或者IAB-DU)发送的第二F1接口(IAB节点的DU和源IAB宿主的CU之间的通信接口)的F1AP消息中时，该第二F1接口的F1AP消息中可以包括指示信息，该指示信息用于指示第二F1接口的F1AP消息中包括的信息是与该目标IAB宿主对应的信息或者是用于建立第一F1接口的信息。此时，处理模块603可以根据获取模块601获取的第二F1接口的F1AP消息中包括的指示信息，确定该第二F1接口的F1AP消息中包括的信息是与该目标IAB宿主对应的信息或者是用于建立第一F1接口的信息。
可选的，获取模块601还可以用于获取来自源IAB宿主的第五信息，该第五信息包括IP 地址信息。
其中，该IP地址信息包括以下中至少一个：用于该第一F1接口的目标IAB宿主的IP地址，用于该第一F1接口的目标IAB宿主的IP地址类型，用于该第一F1接口的目标IAB宿主的IP地址前缀，用于该第一F1接口的目标IAB宿主的IP地址个数，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址类型，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址前缀，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址个数，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址类型，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址前缀，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址个数。其中，该第一F1-C接口为该第一F1接口的控制面接口，第一F1-U接口为该第一F1接口的用户面接口,上述F1-C业务包括经过该第一F1-C接口的业务，上述F1-U业务包括经过第一F1-U接口的业务。其中，IP地址类型可以包括IPv4和/或IPv6类型。
可选的，获取模块601还可以用于获取来自源IAB宿主的第七信息，该第七信息包括用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息。
其中，该用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的请求信息包括以下中至少一个：IAB节点下属设备对应的F1接口应用协议标识，该IAB节点服务的Scell建立列表，该IAB节点和该IAB节点下属设备之间的SRB建立列表，该IAB节点和该IAB节点下属设备之间的DRB建立列表，该IAB节点和该IAB节点下属设备(或者IAB节点的子节点)之间的BH RLC CH建立列表，该IAB节点的用户面数据路由规则，该IAB节点的用户面承载映射规则。
进一步的，发送模块602还用于向源IAB宿主发送该第七信息的反馈信息，该第七信息的反馈信息为用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息。
其中，该用于在该IAB节点和/或该目标IAB宿主中建立该IAB节点下属设备上下文的响应信息包括以下中至少一个：该IAB节点为该IAB节点下属设备分配的C-RNTI，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的DRB列表，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的SRB列表，建立成功或建立失败的该IAB节点和该IAB节点下属设备之间的BH RLC CH列表、建立成功或建立失败的该IAB节点服务的Scell列表。
可选的，该通信装置600还可以包括处理模块603。该处理模块603具体用于根据IP地址与目标IAB宿主建立初始SCTP偶联。其中，该IP地址是该通信装置600根据第五信息获得的。
基于相同的技术构思，本申请实施例还提供了一种装置700，下面将结合装置700的示意性框图图7，对装置700的结构和功能进行具体的描述。该装置可以包括至少一个处理器701。可选的还包括接口电路702。当涉及的程序指令在该至少一个处理器701中执行时，可以使得该装置700实现前述任一实施例所提供的通信方法及其中任一可能的设计。或者，该处理器701通过逻辑电路或执行代码指令用于实现前述任一实施例所提供的通信方法及其中任一可能的设计。该接口电路702，可以用于接收程序指令并传输至所述处理器，或者，该接口电路702可以用于装置700与其他通信设备进行通信交互，比如交互控制信令和/或业务数据等。示例性的，该接口电路702可以用于接收来自该装置700之外的其它装置的信号并 传输至该处理器701或将来自该处理器701的信号发送给该装置700之外的其它通信装置。该接口电路702可以为代码和/或数据读写接口电路，或者，该接口电路702可以为通信处理器与收发机之间的信号传输接口电路。可选的，该通信装置700还可以包括至少一个存储器703，该存储器703可以用于存储所需的涉及的程序指令和/或数据。可选的，该装置700还可以包括供电电路704，该供电电路704可以用于为该处理器701供电，该供电电路704可以与处理器701位于同一个芯片内，或者，位于处理器701所在的芯片之外的另一个芯片内。可选的，该装置700还可以包括总线705，该装置700中的各个部分可以通过总线705互联。
应理解，本申请实施例中的处理器可以为中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、或者分立硬件组件等。通用处理器可以是微处理器，或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或者可以包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，RAM)可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic random access memory，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)、或者直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
本申请实施例所述的供电电路包括但不限于如下至少一个：供电线路，供电子系统、电源管理芯片、功耗管理处理器、或者功耗管理控制电路。
本申请实施例所述的收发装置、接口电路、或者收发器中可以包括单独的发送器，和/或，单独的接收器，也可以是发送器和接收器集成一体。收发装置、接口电路、或者收发器可以在相应的处理器的指示下工作。可选的，发送器可以对应物理设备中发射机，接收器可以对应物理设备中的接收机。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，该模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元或者算法操作，能够通过硬件实现，或者，通过软件实现，或者，通过软件和硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请中，“通过软件实现”可以指处理器读取并执行存储在存储器中的程序指令来实现上述模块或单元所对应的功能，其中，处理器是指具有执行程序指令功能的处理电路，包括但不限于以下至少一种：中央处理单元(central processing unit，CPU)、微处理器、数字信号处理器(digital signal processing，DSP)、微控制器(microcontroller unit，MCU)、或人工智能处理器等各类能够运行程序指令的处理电路。在另一些实施例中，处理器还可以包括其他处理功能的电路(如用于硬件加速的硬件电路、总线和接口电路等)。处理器可以以集成芯片的形式呈现，例如，以处理功能仅包括执行软件指令功能的集成芯片的形式呈现，或者还可以片上系统(system on a chip，SoC)的形式呈现，即在一个芯片上，除了包括能够运行程序指令的处理电路(通常被称为“核”)外，还包括其他用于实现特定功能的硬件电路(当然，这些硬件电路也可以是基于ASIC、FPGA单独实现)，相应的，处理功能除了包括执行软件指令功能外，还可以包括各种硬件加速功能(如AI计算、编解码、压缩解压等)。
本申请中，“通过硬件实现”是指通过不具有程序指令处理功能的硬件处理电路来实现上述模块或者单元的功能，该硬件处理电路可以通过分立的硬件元器件组成，也可以是集成电路。为了减少功耗、降低尺寸，通常会采用集成电路的形式来实现。硬件处理电路可以包括ASIC，或者可编程逻辑器件(programmable logic device，PLD)；其中，PLD又可包括FPGA、复杂可编程逻辑器件(complex programmable logic device，CPLD)等等。这些硬件处理电路可以是单独封装的一块半导体芯片(如封装成一个ASIC)；也可以跟其他电路(如CPU、DSP)集成在一起后封装成一个半导体芯片，例如，可以在一个硅基上形成多种硬件电路以及CPU，并单独封装成一个芯片，这种芯片也称为SoC，或者也可以在硅基上形成用于实现FPGA功能的电路以及CPU，并单独封闭成一个芯片，这种芯片也称为可编程片上系统(system on a programmable chip，SoPC)。
需要说明的是，本申请在通过软件、硬件或者软件硬件结合的方式实现时，可以使用不同的软件、硬件，并不限定只使用一种软件或者硬件。例如，其中，其中一个模块或者单元可以使用CPU来实现，另一个模块或者单元可以使用DSP来实现。同理，当使用硬件实现时，其中一个模块或者单元可以使用ASIC来实现，另一个模块或者单元可以使用FPGA实现。当然，也不限定部分或者所有的模块或者单元使用同一种软件(如都通过CPU)或者同一种硬件(如都通过ASIC)来实现。此外，对于本领域技术人员，可以知道，软件通常来说灵活性更好，但性能不如硬件，而硬件正好相反，因此，本领域技术人员可以结合实际需求来选择软件或者硬件或者两者结合的形式来实现。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详细描述的部分，可以参见其他实施例的相关描述。本申请实施例之间可以结合，实施例中的某些技术特征也可以从具体实施例中解耦出来，结合现有技术可以解决本申请实施例涉及的技术问题。
本申请实施例中，作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者所述技术方案的全部或部分可以以软件产品的形式体现出来，所述计算机软件产品存储在一个存储介质中，可以包括若干指令用以使得一台计算机设备，例如可以是个人计算机，服务器，或者网络设备等，或处理器(processor)执行本申请各个实施例所述方法的全部或部分操作。而前述的存储介质可以包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟、或者光盘等各种可以存储程序代码的介质或计算机可读存储介质。
在本申请的描述中，“第一”，“第二”，“S201”，或“S202”等词汇，仅用于区分描述以及上下文行文方便的目的，不同的次序编号本身不具有特定技术含义，不能理解为指示或暗示相对重要性，也不能理解为指示或暗示操作的执行顺序。
本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如“A和/或B”可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。另外，本文中字符“/”，表示前后关联对象是一种“或”的关系。
本申请中，“传输”可以包括以下三种情况：数据的发送，数据的接收，或者数据的发送和数据的接收。本申请中，“数据”可以包括业务数据，和/或，信令数据。
本申请中术语“包括”或“具有”及其任何变形，意图在于覆盖不排他的包括，例如，包括了一系列步骤的过程/方法，或一系列单元的系统/产品/设备，不必限于清楚地列出的那些步骤或单元，而是可以包括没有清楚地列出的或对于这些过程/方法/产品/设备固有的其它步骤或单元。
在本申请的描述中，“至少一个”，表示一个或者多个。“包括以下至少一个：A，B，C。”表示可以包括A，或者包括B，或者包括C，或者包括A和B，或者包括A和C，或者包括B和C，或者包括A，B和C。
本申请实施例提供的方案可适用于各种通信系统，例如：全球移动通讯(global system of mobile communication，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、第五代(5th generation，5G)移动通信系统、或者新无线(new radio，NR)系统，以及其他可用于提供移动通信服务的网络系统等，本申请不做限定。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。

Claims (74)

  1. 一种通信方法，其特征在于，应用于接入回传一体化IAB节点的源IAB宿主，包括：
    向所述IAB节点的目标IAB宿主发送第一信息，所述第一信息包括用于建立第一F1接口的请求信息；
    接收来自所述目标IAB宿主的第二信息，所述第二信息包括所述请求信息的反馈信息；
    其中，所述第一F1接口为所述IAB节点的分布式单元DU和所述目标IAB宿主的集中式单元CU之间的通信接口。
  2. 根据权利要求1所述的方法，其特征在于，所述反馈信息为用于建立第一F1接口的响应信息，所述方法还包括：
    向所述IAB节点发送第三信息，所述第三信息包括所述用于建立第一F1接口的响应信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述用于建立第一F1接口的请求信息包括以下中至少一个：所述IAB节点的DU标识，所述IAB节点的DU名称，所述IAB节点服务的小区的服务小区信息，所述IAB节点的DU发送的系统信息，所述IAB节点的DU所支持的无线资源控制RRC版本，所述IAB节点的DU的传输层地址信息。
  4. 根据权利要求2或3所述的方法，其特征在于，所述用于建立第一F1接口的响应信息包括以下中至少一个：用于标识所述目标IAB宿主的信息，所述IAB节点服务的小区的激活信息，所述目标IAB宿主的CU所支持的RRC版本，所述目标IAB宿主的CU的传输层地址信息，所述IAB节点的DU的同步信号块发送配置STC。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一信息承载在所述源IAB宿主向所述目标IAB宿主发送的所述IAB节点的切换请求消息中。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述第二信息承载在所述目标IAB宿主向所述源IAB宿主发送的所述IAB节点的切换请求响应消息中。
  7. 根据权利要求2至6中任一项所述的方法，其特征在于，所述第三信息承载在所述源IAB宿主向所述IAB节点发送的无线资源控制RRC重配置消息中；或者，
    所述第三信息承载在所述源IAB宿主向所述IAB节点发送的第二F1接口的F1接口应用协议F1AP消息中，其中，所述第二F1接口为所述IAB节点的DU和所述源IAB宿主的CU之间的通信接口。
  8. 根据权利要求7所述的方法，其特征在于，当所述第三信息承载在所述第二F1接口的F1AP消息中时，所述第二F1接口的F1AP消息中还包括指示信息，所述指示信息用于指示所述第三信息与所述目标IAB宿主对应。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述目标IAB宿主的第四信息，所述第四信息包括所述目标IAB宿主的IP地址信息，所述IP地址信息用于所述目标IAB宿主与所述IAB节点之间初始流控制传输协议SCTP偶联的建立；
    向所述IAB节点发送第五信息，所述第五信息包括所述IP地址信息。
  10. 根据权利要求9所述的方法，其特征在于，所述第四信息承载在所述目标IAB宿主向所述源IAB宿主发送的所述IAB节点的切换请求响应消息中。
  11. 根据权利要求9至10中任一项所述的方法，其特征在于，所述第五信息承载在所述源IAB宿主向所述IAB节点发送的无线资源控制RRC重配置消息中。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述目标IAB宿主的第六信息，所述第六信息包括用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的请求信息；
    向所述IAB节点发送所述第七信息，所述第七信息包括所述用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的请求信息；
    接收来自所述IAB节点的用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的响应信息；
    向所述目标IAB宿主发送所述用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的响应信息；
    其中，所述IAB节点下属设备包括所述IAB节点的IAB子节点或者接入所述IAB节点的终端设备。
  13. 根据权利要求12所述的方法，其特征在于，所述第七信息承载在所述源IAB宿主向所述IAB节点发送的无线资源控制RRC重配置消息中，或者，所述第七信息和所述第三信息承载在同一条消息中。
  14. 根据权利要求12或13所述的方法，其特征在于，接收来自所述目标IAB宿主的第六信息，包括：
    通过核心网设备接收来自所述目标IAB宿主的所述第六信息；
    向所述目标IAB宿主发送所述用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的响应信息，包括：
    通过核心网设备向所述目标IAB宿主发送所述用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的响应信息。
  15. 根据权利要求9至14中任一项所述的方法，其特征在于，接收来自所述目标IAB宿主的第四信息，包括：
    通过核心网设备接收来自所述目标IAB宿主的所述第四信息。
  16. 根据权利要求1至15中任一项所述的方法，其特征在于，向所述IAB节点的目标IAB宿主发送第一信息，包括：
    通过核心网设备向所述IAB节点的目标IAB宿主发送所述第一信息；
    接收来自所述目标IAB宿主的第二信息，包括：
    通过核心网设备接收来自所述目标IAB宿主的所述第二信息。
  17. 一种通信方法，其特征在于，应用于接入回传一体化IAB节点的目标IAB宿主，包括：
    接收来自所述IAB节点的源IAB宿主的第一信息，所述第一信息包括用于建立第一F1接口的请求信息；
    向所述源IAB宿主发送第二信息，所述第二信息包括所述请求信息的反馈信息；
    其中，所述第一F1接口为所述IAB节点的分布式单元DU和所述目标IAB宿主的集中式单元CU之间的通信接口。
  18. 根据权利要求17所述的方法，其特征在于，所述方法还包括：
    通过所述源IAB宿主向所述IAB发送所述第一F1接口的IP地址信息，所述第一F1接口的IP地址信息用于所述目标IAB宿主与所述IAB节点之间初始流控制传输协议SCTP偶联的建立。
  19. 根据权利要求17或18所述的方法，其特征在于，所述方法还包括：
    通过所述源IAB宿主向所述IAB节点发送用于在所述IAB节点和/或所述目标IAB宿主 中建立所述IAB节点下属设备上下文的请求信息；
    通过所述源IAB宿主接收来自所述IAB节点的用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的响应信息；
    其中，所述IAB节点下属设备包括所述IAB节点的IAB子节点或者接入所述IAB节点的终端设备。
  20. 根据权利要求19所述的方法，其特征在于，通过所述源IAB宿主向所述IAB节点发送所述用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的请求信息，包括：
    通过核心网设备和所述源IAB宿主向所述IAB节点发送所述用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的请求信息；
    通过所述源IAB宿主接收来自所述IAB节点的所述用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的响应信息，包括：
    通过核心网设备和所述源IAB宿主接收来自所述IAB节点的所述用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的响应信息。
  21. 根据权利要求17至20中任一项所述的方法，其特征在于，通过所述源IAB宿主向所述IAB发送所述第一F1接口的IP地址信息，包括：
    通过核心网设备和所述源IAB宿主向所述IAB发送所述第一F1接口的IP地址信息。
  22. 根据权利要求17至21中任一项所述的方法，其特征在于，接收来自所述IAB节点的源IAB宿主的第一信息，包括：
    通过核心网设备接收来自所述IAB节点的源IAB宿主的所述第一信息；
    向所述源IAB宿主发送第二信息，包括：
    通过核心网设备向所述IAB节点的源IAB宿主发送所述第二信息。
  23. 一种通信方法，其特征在于，应用于接入回传一体化IAB节点，包括：
    接收来自源IAB宿主的第三信息，所述第三信息包括用于建立第一F1接口的响应信息；
    其中，所述第一F1接口为所述IAB节点的分布式单元DU和所述目标IAB宿主的集中式单元CU之间的通信接口。
  24. 根据权利要求23所述的方法，其特征在于，所述方法还包括：
    接收来自源IAB宿主的第五信息，所述第五信息包括所述第一F1接口的IP地址信息，所述第一F1接口的IP地址信息用于所述目标IAB宿主与所述IAB节点之间初始流控制传输协议SCTP偶联的建立。
  25. 根据权利要求24或25所述的方法，其特征在于，所述方法还包括：
    接收来自源IAB宿主的第七信息，所述第七信息包括用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的请求信息；
    通过所述源IAB宿主向所述目标IAB宿主发送用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的响应信息；
    其中，所述IAB节点下属设备包括所述IAB节点的IAB子节点或者接入所述IAB节点的终端设备。
  26. 一种通信方法，其特征在于，应用于接入回传一体化IAB节点，包括：
    接收来自目标IAB宿主的所述目标IAB宿主的IP地址信息，其中，所述IP地址信息用于目标IAB宿主与IAB节点之间初始流控制传输协议SCTP偶联的建立；
    基于所述目标IAB宿主的IP地址信息，建立所述目标IAB宿主与所述IAB节点之间初 始SCTP偶联。
  27. 根据权利要求26所述的方法，其特征在于，所述IP地址信息包括以下中至少一个：用于所述第一F1接口的目标IAB宿主的互联网协议IP地址或者IP地址类型或者IP地址前缀或者IP地址个数，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数。其中，所述第一F1接口指的是所述IAB节点的DU和所述目标IAB宿主的CU之间的通信接口，所述第一F1-C接口为所述第一F1接口的控制面接口，第一F1-U接口为所述第一F1接口的用户面接口,上述F1-C业务包括经过所述第一F1-C接口的业务，上述F1-U业务包括经过第一F1-U接口的业务。
  28. 根据权利要求26或27所述的方法，其特征在于，所述目标IAB宿主的IP地址信息承载在目标IAB宿主向源IAB宿主发送的IAB节点的切换请求响应消息中。
  29. 根据权利要求26-28中任一项所述的方法，其特征在于，所述目标IAB宿主的IP地址信息承载在源IAB宿主向IAB节点发送的RRC重配置消息中。
  30. 一种通信方法，其特征在于，应用于目标接入回传一体化IAB宿主，包括：
    向IAB节点发送所述目标IAB宿主的IP地址信息，其中，所述IP地址信息用于所述目标IAB宿主与IAB节点之间初始流控制传输协议SCTP偶联的建立；
    基于所述目标IAB宿主的IP地址信息，建立所述目标IAB宿主与所述IAB节点之间初始SCTP偶联。
  31. 根据权利要求30所述的方法，其特征在于，向IAB节点发送所述目标IAB宿主的IP地址信息，包括：
    通过核心网设备和源IAB宿主向所述IAB节点发送所述目标IAB宿主的IP地址信息。
  32. 根据权利要求30或31所述的方法，其特征在于，所述IP地址信息包括以下中至少一个：用于所述第一F1接口的目标IAB宿主的互联网协议IP地址或者IP地址类型或者IP地址前缀或者IP地址个数，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数。其中，所述第一F1接口指的是所述IAB节点的DU和所述目标IAB宿主的CU之间的通信接口，所述第一F1-C接口为所述第一F1接口的控制面接口，第一F1-U接口为所述第一F1接口的用户面接口,上述F1-C业务包括经过所述第一F1-C接口的业务，上述F1-U业务包括经过第一F1-U接口的业务。
  33. 根据权利要求30-32中任一项所述的方法，其特征在于，所述目标IAB宿主的IP地址信息承载在目标IAB宿主向源IAB宿主发送的IAB节点的切换请求响应消息中。
  34. 根据权利要求30-33中任一项所述的方法，其特征在于，所述目标IAB宿主的IP地址信息承载在源IAB宿主向IAB节点发送的RRC重配置消息中。
  35. 一种通信装置，其特征在于，包括：
    发送模块，用于向所述IAB节点的目标IAB宿主发送第一信息，所述第一信息包括用于建立第一F1接口的请求信息；
    获取模块，用于接收来自所述目标IAB宿主的第二信息，所述第二信息包括所述请求信息的反馈信息；
    其中，所述第一F1接口为所述IAB节点的分布式单元DU和所述目标IAB宿主的集中 式单元CU之间的通信接口。
  36. 根据权利要求35所述的装置，其特征在于，所述反馈信息为用于建立第一F1接口的响应信息，所述发送模块还用于向所述IAB节点发送第三信息，所述第三信息包括所述用于建立第一F1接口的响应信息。
  37. 根据权利要求35或36所述的装置，其特征在于，所述用于建立第一F1接口的请求信息包括以下中至少一个：所述IAB节点的DU标识，所述IAB节点的DU名称，所述IAB节点服务的小区的服务小区信息，所述IAB节点的DU发送的系统信息，所述IAB节点的DU所支持的无线资源控制RRC版本，所述IAB节点的DU的传输层地址信息。
  38. 根据权利要求36或37所述的装置，其特征在于，所述用于建立第一F1接口的响应信息包括以下中至少一个：用于标识所述目标IAB宿主的信息，所述IAB节点服务的小区的激活信息，所述目标IAB宿主的CU所支持的RRC版本，所述目标IAB宿主的CU的传输层地址信息，所述IAB节点的DU的同步信号块发送配置STC。
  39. 根据权利要求35至38中任一项所述的装置，其特征在于，所述第一信息承载在所述源IAB宿主向所述目标IAB宿主发送的所述IAB节点的切换请求消息中。
  40. 根据权利要求35至39中任一项所述的装置，其特征在于，所述第二信息承载在所述目标IAB宿主向所述源IAB宿主发送的所述IAB节点的切换请求响应消息中。
  41. 根据权利要求36至40中任一项所述的装置，其特征在于，所述第三信息承载在所述源IAB宿主向所述IAB节点发送的无线资源控制RRC重配置消息中；或者，
    所述第三信息承载在所述源IAB宿主向所述IAB节点发送的第二F1接口的F1接口应用协议F1AP消息中，其中，所述第二F1接口为所述IAB节点的DU和所述源IAB宿主的CU之间的通信接口。
  42. 根据权利要求41所述的装置，其特征在于，当所述第三信息承载在所述第二F1接口的F1AP消息中时，所述第二F1接口的F1AP消息中还包括指示信息，所述指示信息用于指示所述第三信息与所述目标IAB宿主对应。
  43. 根据权利要求35至42中任一项所述的装置，其特征在于，
    所述获取模块还用于接收来自所述目标IAB宿主的第四信息，所述第四信息包括所述目标IAB宿主的IP地址信息，所述IP地址信息用于所述目标IAB宿主与所述IAB节点之间初始流控制传输协议SCTP偶联的建立；
    所述发送模块还用于向所述IAB节点发送第五信息，所述第五信息包括所述IP地址信息。
  44. 根据权利要求43所述的装置，其特征在于，所述第四信息承载在所述目标IAB宿主向所述源IAB宿主发送的所述IAB节点的切换请求响应消息中。
  45. 根据权利要求43至44中任一项所述的装置，其特征在于，所述第五信息承载在所述源IAB宿主向所述IAB节点发送的无线资源控制RRC重配置消息中。
  46. 根据权利要求35至45中任一项所述的装置，其特征在于，
    所述获取模块还用于接收来自所述目标IAB宿主的第六信息，所述第六信息包括用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的请求信息；
    所述发送模块还用于向所述IAB节点发送所述第七信息，所述第七信息包括所述用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的请求信息；
    所述获取模块还用于接收来自所述IAB节点的用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的响应信息；
    所述发送模块还用于向所述目标IAB宿主发送所述用于在所述IAB节点和/或所述目标 IAB宿主中建立所述IAB节点下属设备上下文的响应信息；
    其中，所述IAB节点下属设备包括所述IAB节点的IAB子节点或者接入所述IAB节点的终端设备。
  47. 根据权利要求46所述的装置，其特征在于，所述第七信息承载在所述源IAB宿主向所述IAB节点发送的无线资源控制RRC重配置消息中，或者，所述第七信息和所述第三信息承载在同一条消息中。
  48. 根据权利要求46或47所述的装置，其特征在于，
    所述获取模块具体用于通过核心网设备接收来自所述目标IAB宿主的所述第六信息；
    所述发送模块具体用于通过核心网设备向所述目标IAB宿主发送所述用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的响应信息。
  49. 根据权利要求43至48中任一项所述的装置，其特征在于，
    所述获取模块具体用于通过核心网设备接收来自所述目标IAB宿主的所述第四信息。
  50. 根据权利要求35至49中任一项所述的装置，其特征在于，
    所述发送模块具体用于通过核心网设备向所述IAB节点的目标IAB宿主发送所述第一信息；
    所述获取模块具体用于通过核心网设备接收来自所述目标IAB宿主的所述第二信息。
  51. 一种通信装置，其特征在于，包括：
    获取模块，用于接收来自所述IAB节点的源IAB宿主的第一信息，所述第一信息包括用于建立第一F1接口的请求信息；
    发送模块，用于向所述源IAB宿主发送第二信息，所述第二信息包括所述请求信息的反馈信息；
    其中，所述第一F1接口为所述IAB节点的分布式单元DU和所述目标IAB宿主的集中式单元CU之间的通信接口。
  52. 根据权利要求51所述的装置，其特征在于，
    所述发送模块，还用于通过所述源IAB宿主向所述IAB发送所述第一F1接口的IP地址信息，所述第一F1接口的IP地址信息用于所述目标IAB宿主与所述IAB节点之间初始流控制传输协议SCTP偶联的建立。
  53. 根据权利要求51或52所述的装置，其特征在于，
    所述发送模块，还用于通过所述源IAB宿主向所述IAB节点发送用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的请求信息；
    所述获取模块，还用于通过所述源IAB宿主接收来自所述IAB节点的用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的响应信息；
    其中，所述IAB节点下属设备包括所述IAB节点的IAB子节点或者接入所述IAB节点的终端设备。
  54. 根据权利要求53所述的装置，其特征在于，
    所述发送模块具体用于通过核心网设备和所述源IAB宿主向所述IAB节点发送所述用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的请求信息；
    所述获取模块具体用于通过核心网设备和所述源IAB宿主接收来自所述IAB节点的所述用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的响应信息。
  55. 根据权利要求51至54中任一项所述的装置，其特征在于，
    所述发送模块具体用于通过核心网设备和所述源IAB宿主向所述IAB发送所述第一F1接口的IP地址信息。
  56. 根据权利要求51至55中任一项所述的装置，其特征在于，
    所述获取模块具体用于通过核心网设备接收来自所述IAB节点的源IAB宿主的所述第一信息；
    所述发送模块具体用于通过核心网设备向所述IAB节点的源IAB宿主发送所述第二信息。
  57. 一种通信装置，其特征在于，包括：
    获取模块，用于接收来自源IAB宿主的第三信息，所述第三信息包括用于建立第一F1接口的响应信息；
    其中，所述第一F1接口为所述IAB节点的分布式单元DU和所述目标IAB宿主的集中式单元CU之间的通信接口。
  58. 根据权利要求57所述的装置，其特征在于，
    所述获取模块，还用于接收来自源IAB宿主的第五信息，所述第五信息包括所述第一F1接口的IP地址信息，所述第一F1接口的IP地址信息用于所述目标IAB宿主与所述IAB节点之间初始流控制传输协议SCTP偶联的建立。
  59. 根据权利要求58或59所述的装置，其特征在于，
    所述获取模块，还用于接收来自源IAB宿主的第七信息，所述第七信息包括用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的请求信息；
    发送模块，用于通过所述源IAB宿主向所述目标IAB宿主发送用于在所述IAB节点和/或所述目标IAB宿主中建立所述IAB节点下属设备上下文的响应信息；
    其中，所述IAB节点下属设备包括所述IAB节点的IAB子节点或者接入所述IAB节点的终端设备。
  60. 一种通信装置，其特征在于，包括：
    获取模块，用于接收来自目标IAB宿主的所述目标IAB宿主的IP地址信息，其中，所述IP地址信息用于目标IAB宿主与IAB节点之间初始流控制传输协议SCTP偶联的建立；
    处理模块，用于基于所述目标IAB宿主的IP地址信息，建立所述目标IAB宿主与所述IAB节点之间初始SCTP偶联。
  61. 根据权利要求60所述的装置，其特征在于，所述IP地址信息包括以下中至少一个：用于所述第一F1接口的目标IAB宿主的互联网协议IP地址或者IP地址类型或者IP地址前缀或者IP地址个数，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数。其中，所述第一F1接口指的是所述IAB节点的DU和所述目标IAB宿主的CU之间的通信接口，所述第一F1-C接口为所述第一F1接口的控制面接口，第一F1-U接口为所述第一F1接口的用户面接口,上述F1-C业务包括经过所述第一F1-C接口的业务，上述F1-U业务包括经过第一F1-U接口的业务。
  62. 根据权利要求60或61所述的装置，其特征在于，所述目标IAB宿主的IP地址信息承载在目标IAB宿主向源IAB宿主发送的IAB节点的切换请求响应消息中。
  63. 根据权利要求60-62中任一项所述的装置，其特征在于，所述目标IAB宿主的IP地址信息承载在源IAB宿主向IAB节点发送的RRC重配置消息中。
  64. 一种通信装置，其特征在于，包括：
    发送模块，用于向IAB节点发送所述目标IAB宿主的IP地址信息，其中，所述IP地址信息用于所述目标IAB宿主与IAB节点之间初始流控制传输协议SCTP偶联的建立；
    处理模块，用于基于所述目标IAB宿主的IP地址信息，建立所述目标IAB宿主与所述IAB节点之间初始SCTP偶联。
  65. 根据权利要求64所述的装置，其特征在于，
    发送模块具体用于通过核心网设备和源IAB宿主向所述IAB节点发送所述目标IAB宿主的IP地址信息。
  66. 根据权利要求64或65所述的装置，其特征在于，所述IP地址信息包括以下中至少一个：用于所述第一F1接口的目标IAB宿主的互联网协议IP地址或者IP地址类型或者IP地址前缀或者IP地址个数，用于第一F1-C接口或者F1-C业务的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数，用于第一F1-U接口或者F1-U业务的目标IAB宿主的IP地址或者IP地址类型或者IP地址前缀或者IP地址个数。其中，所述第一F1接口指的是所述IAB节点的DU和所述目标IAB宿主的CU之间的通信接口，所述第一F1-C接口为所述第一F1接口的控制面接口，第一F1-U接口为所述第一F1接口的用户面接口,上述F1-C业务包括经过所述第一F1-C接口的业务，上述F1-U业务包括经过第一F1-U接口的业务。
  67. 根据权利要求64-66中任一项所述的装置，其特征在于，所述目标IAB宿主的IP地址信息承载在目标IAB宿主向源IAB宿主发送的IAB节点的切换请求响应消息中。
  68. 根据权利要求64-67中任一项所述的装置，其特征在于，所述目标IAB宿主的IP地址信息承载在源IAB宿主向IAB节点发送的RRC重配置消息中。
  69. 一种通信装置，其特征在于，包括：至少一个处理器和接口，所述接口用于接收和/或发送信号，所述处理器被配置用于使能如权利要求1至16中任一项所述的方法被执行。
  70. 一种通信装置，其特征在于，包括：至少一个处理器和接口，所述接口用于接收和/或发送信号，所述处理器被配置用于使能如权利要求17至22，30至34中任一项所述的方法被执行。
  71. 一种通信装置，其特征在于，包括：至少一个处理器和接口，所述接口用于接收和/或发送信号，所述处理器被配置用于使能如权利要求23至29中任一项所述的方法被执行。
  72. 一种通信系统，其特征在于，包括如权利要求26所述的通信装置，如权利要求27所述的通信装置，以及如权利要求28所述的通信装置。
  73. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序指令，当所述计算机程序指令被处理器执行时，使得如权利要求1至16中任一项所述的方法被实现，或，使得如权利要求17至22中任一项所述的方法被实现，或，使得如权利要求23至25中任一项所述的方法被实现。
  74. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序指令，当所述计算机程序指令被处理器运行时，使得如权利要求1-16中任一项所述的方法被实现，或者，如权利要求17-22中任一项所述的方法被实现，或者，如权利要求23-25中任一项所述的方法被实现。
PCT/CN2021/095773 2020-06-30 2021-05-25 一种用于iab网络通信的方法及相关设备 WO2022001503A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2022581370A JP2023531787A (ja) 2020-06-30 2021-05-25 Ｉａｂネットワーク通信方法及び関連デバイス
EP21832950.6A EP4171122A4 (en) 2020-06-30 2021-05-25 IAB NETWORK COMMUNICATION METHOD AND APPARATUS
US18/146,546 US20230130178A1 (en) 2020-06-30 2022-12-27 Iab network communication method and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010624351.5 2020-06-30
CN202010624351.5A CN113873587B (zh) 2020-06-30 2020-06-30 一种用于iab网络通信的方法及相关设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/146,546 Continuation US20230130178A1 (en) 2020-06-30 2022-12-27 Iab network communication method and related device

Publications (1)

Publication Number Publication Date
WO2022001503A1 true WO2022001503A1 (zh) 2022-01-06

Family

ID=78982053

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/095773 WO2022001503A1 (zh) 2020-06-30 2021-05-25 一种用于iab网络通信的方法及相关设备

Country Status (5)

Country Link
US (1) US20230130178A1 (zh)
EP (1) EP4171122A4 (zh)
JP (1) JP2023531787A (zh)
CN (1) CN113873587B (zh)
WO (1) WO2022001503A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023240174A1 (en) * 2022-06-10 2023-12-14 Qualcomm Incorporated F1 connection options in integrated access and backhaul handover scenarios
GB2624000A (en) * 2022-11-03 2024-05-08 Canon Kk Migration of nodes in an IAB communication system

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023150974A1 (zh) * 2022-02-10 2023-08-17 富士通株式会社 Iab宿主设备以及传输迁移管理方法
CN117641353A (zh) * 2022-08-12 2024-03-01 华为技术有限公司 通信方法、装置和系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019139524A1 (en) * 2018-01-11 2019-07-18 Telefonaktiebolaget Lm Ericsson (Publ) Packet forwarding in integrated access backhaul (iab) networks
CN110636570A (zh) * 2018-06-25 2019-12-31 中兴通讯股份有限公司 Iab网络中iab节点信息的处理方法及装置
CN110740485A (zh) * 2019-09-30 2020-01-31 河南牧业经济学院 集成接入和回程系统的节点选择方法及其装置
CN111093286A (zh) * 2019-08-15 2020-05-01 中兴通讯股份有限公司 连接建立方法、装置、集合接入回传节点及存储介质
CN111586744A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 一种iab节点的切换方法及装置

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109246746A (zh) * 2017-05-05 2019-01-18 北京三星通信技术研究有限公司 前向接口的建立、ue接入和切换方法及装置
CN109246747B (zh) * 2017-05-05 2021-09-21 北京三星通信技术研究有限公司 前向接口的建立方法、ue接入方法、ue切换方法及装置
CN109391963B (zh) * 2017-08-11 2022-03-11 华为技术有限公司 一种传输方法和网络设备
CN109729529A (zh) * 2017-10-31 2019-05-07 上海华为技术有限公司 实现网元间通信的方法、基站及存储介质
CN110351807B (zh) * 2018-04-04 2023-07-14 中兴通讯股份有限公司 接入选择方法及装置
CN110351700B (zh) * 2018-04-05 2022-06-17 中兴通讯股份有限公司 一种自接入回传链路的中继转发方法及节点
CN110475368B (zh) * 2018-05-10 2022-12-20 中兴通讯股份有限公司 信息传输方法及装置
CN110475381B (zh) * 2018-05-11 2021-09-03 华为技术有限公司 通信方法、设备和系统
US20190394084A1 (en) * 2018-06-20 2019-12-26 Industrial Technology Research Institute Network link topology adaptation method for intergrated access and backhaul node and intergrated access and backhaul node using the same
US11477712B2 (en) * 2018-06-21 2022-10-18 Google Llc Maintaining communication and signaling interfaces through a network role transition
CN110649997B (zh) * 2018-06-26 2021-07-20 大唐移动通信设备有限公司 数据处理方法及装置
CN110662266B (zh) * 2018-06-29 2021-02-09 华为技术有限公司 Iab节点的切换方法、iab节点和宿主基站
CN110662297B (zh) * 2018-06-29 2022-07-22 大唐移动通信设备有限公司 一种信令处理方法、节点及装置
CN112868254A (zh) * 2018-08-23 2021-05-28 瑞典爱立信有限公司 集成接入回程（iab）拓扑适配-控制平面（cp）处置
CN110958642B (zh) * 2018-09-27 2022-04-22 华为技术有限公司 用于无线回传网络的数据传输方法和装置
WO2020067736A1 (en) * 2018-09-27 2020-04-02 Lg Electronics Inc. Method and apparatus for preventing loss of uplink data in wireless communication system
CN110536350A (zh) * 2019-02-14 2019-12-03 中兴通讯股份有限公司 Iab链路控制方法、通信单元、计算机可读存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019139524A1 (en) * 2018-01-11 2019-07-18 Telefonaktiebolaget Lm Ericsson (Publ) Packet forwarding in integrated access backhaul (iab) networks
CN110636570A (zh) * 2018-06-25 2019-12-31 中兴通讯股份有限公司 Iab网络中iab节点信息的处理方法及装置
CN111586744A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 一种iab节点的切换方法及装置
CN111093286A (zh) * 2019-08-15 2020-05-01 中兴通讯股份有限公司 连接建立方法、装置、集合接入回传节点及存储介质
CN110740485A (zh) * 2019-09-30 2020-01-31 河南牧业经济学院 集成接入和回程系统的节点选择方法及其装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.473
See also references of EP4171122A4

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023240174A1 (en) * 2022-06-10 2023-12-14 Qualcomm Incorporated F1 connection options in integrated access and backhaul handover scenarios
GB2624000A (en) * 2022-11-03 2024-05-08 Canon Kk Migration of nodes in an IAB communication system
GB2624064A (en) * 2022-11-03 2024-05-08 Canon Kk Migration of nodes in an IAB communication system

Also Published As

Publication number Publication date
US20230130178A1 (en) 2023-04-27
EP4171122A1 (en) 2023-04-26
EP4171122A4 (en) 2024-01-10
CN113873587A (zh) 2021-12-31
JP2023531787A (ja) 2023-07-25
CN113873587B (zh) 2023-09-22

Similar Documents

Publication Publication Date Title
WO2022001503A1 (zh) 一种用于iab网络通信的方法及相关设备
WO2021147107A1 (zh) 一种通信方法及装置
US11343874B2 (en) Relay transmission method and device
WO2022082679A1 (zh) 一种通信方法及相关设备
WO2023011245A1 (zh) 通信方法和通信装置
WO2022011496A1 (zh) 一种通信方法和通信装置
US20230247521A1 (en) Lossless data transmission communication method, apparatus, and system
WO2021249153A1 (zh) 一种中继通信方法及相关设备
WO2020029080A1 (zh) 切换网络的方法、网络节点、芯片和通信系统
WO2022151298A1 (zh) 群组迁移方法、装置和系统
WO2022082690A1 (zh) 群组切换的方法、装置和系统
JP2023545849A (ja) Ｉａｂノードのマイグレーション方法及び装置
WO2022067781A1 (zh) 一种通信方法及相关设备
US20240073762A1 (en) Communication method, apparatus, and system
RU2806798C1 (ru) Способ и устройство связи
WO2022068164A1 (zh) 一种通信方法及相关设备
WO2023125274A1 (zh) 一种通信方法及相关设备
WO2024046294A1 (zh) 通信方法和装置
WO2023010367A1 (zh) 终端设备的转移方法、装置和系统
WO2023131094A1 (zh) 通信方法及通信装置
WO2024093719A1 (zh) 一种数据传输的方法和装置
RU2780823C2 (ru) Устройство и способ обработки беспроводной связи по транзитному соединению
WO2023246746A1 (zh) 一种通信方法及相关设备
WO2022226986A1 (en) Method and apparatus for wireless communication
WO2022082691A1 (zh) Iab网络的rlf恢复方法、装置以及相关设备

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022581370

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021832950

Country of ref document: EP

Effective date: 20230117

NENP Non-entry into the national phase

Ref country code: DE