WO2025035240A1 - 接入回传一体化节点的集成方法和装置 - Google Patents

接入回传一体化节点的集成方法和装置 Download PDF

Info

Publication number
WO2025035240A1
WO2025035240A1 PCT/CN2023/112456 CN2023112456W WO2025035240A1 WO 2025035240 A1 WO2025035240 A1 WO 2025035240A1 CN 2023112456 W CN2023112456 W CN 2023112456W WO 2025035240 A1 WO2025035240 A1 WO 2025035240A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
host
rrc
node
information
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/CN2023/112456
Other languages
English (en)
French (fr)
Inventor
易粟
李国荣
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
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 Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to PCT/CN2023/112456 priority Critical patent/WO2025035240A1/zh
Priority to CN202380100991.8A priority patent/CN121693962A/zh
Publication of WO2025035240A1 publication Critical patent/WO2025035240A1/zh
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point

Definitions

  • the present application relates to the field of communications.
  • IAB Integrated access and backhaul
  • NG-RAN next generation radio access network
  • This relay node is called an IAB-node, which supports both access and backhaul (BH) through 5G NR (new radio).
  • All IAB nodes are connected to an IAB-donor node through one or more hops. These multi-hop connections form a directed acyclic graph (DAG) topology with the IAB-donor node as the root node.
  • DAG directed acyclic graph
  • the IAB-donor node is responsible for performing centralized resource management, topology management, and routing management in the IAB network topology.
  • the IAB node supports the functions of gNB-DU (distributed unit), which is called IAB-DU. It can serve ordinary UE (user equipment) and IAB child nodes.
  • the IAB node also supports some functions of UE, which can be called IAB-MT (mobile termination).
  • IAB-MT can support functions such as UE physical layer, AS (access stratum), RRC (radio resource control) and NAS (non-access stratum), and can be connected to the IAB parent node.
  • the termination node on the network side is called IAB-donor, which provides network access for IAB-MT or UE through backhaul or access link.
  • IAB-donor is further divided into IAB-donor-CU (central unit) and IAB-donor-DU.
  • IAB-DU and IAB-donor-CU are connected through the F1 interface.
  • gNB and IAB-donor-CU are connected through the Xn interface.
  • IAB introduces the BAP (Backhaul Adaptation Protocol) sublayer.
  • the BAP sublayer is located above the RLC (radio link control) sublayer and below the IP (Internet Protocol) layer, and supports the selection of the destination node and path of the data packet, routing forwarding of the data packet, bearer mapping, flow control feedback, and notification of backhaul link failure.
  • RLC radio link control
  • IP Internet Protocol
  • the IAB node In a multi-hop scenario, in order to realize the relay forwarding of data packets, the IAB node needs to determine the destination node of the data packet, and then determine the next hop node corresponding to the destination node according to the routing table and send the data packet.
  • the IAB node is configured with the mapping of each F1-U (F1 user plane) tunnel (Tunnel), each non-UE associated (Non-UE associated) F1AP message, each UE-associated (UE-associated) F1AP message, and each non-F1 data (Non-F1Traffic) to the BAP routing identifier for the uplink transmission initiated from the IAB node through the F1AP signaling.
  • F1-U F1 user plane
  • the IAB node determines the BAP routing identifier corresponding to different types of uplink IP packets initiated from the IAB node based on the routing identifier mapping information, and encapsulates the BAP subheader containing the BAP routing identifier information for these uplink IP packets.
  • the IAB-donor-CU configures the mapping of different types of downlink data packets to the BAP routing identifier for the IAB-donor-DU (referred to as donor-DU) through the F1AP signaling.
  • donor-DU the IAB-donor-DU determines the BAP routing identifier corresponding to the received downlink IP packet based on the routing identifier mapping information, and encapsulates the BAP subheader containing the BAP routing identifier information for these downlink IP packets.
  • the BAP routing identifier includes the destination BAP address and the path identity from the IAB node to the IAB-donor-DU.
  • the BAP address is also called DESTINATION in the BAP header.
  • Each IAB node and IAB-donor-DU is configured with a BAP address.
  • the integration process of IAB nodes is also called the startup process, which refers to the process in which IAB-MT accesses the network and obtains IAB-related configuration information, and starts some DU functions to provide services for UE.
  • the startup process refers to the process in which IAB-MT accesses the network and obtains IAB-related configuration information, and starts some DU functions to provide services for UE.
  • the IAB-MT accesses the network.
  • the IAB-MT connects to the network as a common UE, and this process basically reuses the initial access process of a common UE.
  • the second stage is BH RLC channel establishment and routing update.
  • RRC can configure a default BH RLC channel and a default BAP routing identifier for non-F1-U traffic.
  • IAB-donor-CU may also establish additional BH RLC channels for IAB-MT for subsequent data transmission in this stage.
  • IAB-donor-CU performs routing configuration for the newly integrated IAB node, IAB-donor-DU, the parent node of the newly integrated IAB node, and all intermediate IAB nodes between the IAB-donor-DU.
  • this stage also includes the IP address allocation process for the newly integrated IAB node.
  • the third stage is IAB-DU startup.
  • IAB-DU uses the IP address obtained in the second stage to initiate SCTP (Stream Control Transmission Protocol) connection establishment and F1 connection establishment process with IAB-donor-CU. After that, the IAB node can start to provide air interface services for UE.
  • SCTP Stream Control Transmission Protocol
  • embodiments of the present application provide an IAB node integration method and device.
  • an integrated device of an IAB node is provided, which is configured in the IAB node, wherein the IAB node includes an MT (mobile terminal) and a DU (distributed unit), wherein:
  • the DU of the IAB node is configured by OAM or the MT of the IAB node is configured by RRC to terminate the CU of the IAB host.
  • F1 terminates the base station identifier of the CU of the IAB host;
  • the DU of the IAB node performs F1 establishment with the CU of the F1 termination IAB host according to the base station identifier.
  • an integrated device of an IAB node is provided, which is configured in an RRC termination IAB host, wherein the RRC termination IAB host includes a CU and a DU, wherein:
  • the CU of the RRC termination IAB host sends first information to the MT of the IAB node, wherein the first information includes identification information of the IAB node and/or identification information of the RRC termination IAB host, so that the DU of the IAB node sends second information related to the first information to the F1 termination IAB host.
  • an integrated device of an IAB node is provided, which is configured in an RRC termination IAB host, wherein the RRC termination IAB host includes a CU and a DU, wherein:
  • the CU of the RRC terminated IAB host receives a first RRC message sent by the MT of the IAB node, the first RRC message including the identification information of the F1 terminated IAB host; the RRC terminated IAB host sends the identification information of the IAB node to the F1 terminated IAB host according to the first RRC message.
  • an integrated device of an IAB node is provided, which is configured in an F1 termination IAB host, wherein the F1 termination IAB host includes a CU and a DU, wherein:
  • the CU of the F1 IAB termination host receives the second information sent by the DU of the IAB node, where the second information is related to the first information, and the first information includes the identification information of the IAB node and/or the RRC termination Identification information of the IAB host.
  • an integrated device of an IAB node is provided, which is configured in an RRC termination IAB host, wherein the RRC termination IAB host includes a CU (central unit) and a DU (distributed unit), wherein:
  • the RRC terminates the CU of the IAB host for the IAB node to determine the base station identifier of the CU of the IAB host that is terminated by F1;
  • the CU of the RRC terminating IAB host sends the base station identifier of the CU of the F1 terminating IAB host to the MT of the IAB node, so that the DU of the IAB node performs F1 establishment with the CU of the F1 terminating IAB host according to the base station identifier.
  • an integrated device of an IAB node is provided, which is configured in an F1 termination IAB host, wherein the F1 termination IAB host includes a CU (central unit) and a DU (distributed unit), wherein:
  • the F1 terminated IAB host receives a first Xn message sent by the CU of the RRC terminated IAB host, and the first Xn message includes the UE XnAP identifier generated by the RRC terminated IAB host for the IAB node and/or the BAP address of the IAB node.
  • a setting device is provided, which is configured in an IAB node, wherein the IAB node includes an MT and a DU, wherein:
  • the MT sends an RRC setup complete message to the RRC termination IAB host, where the RRC setup complete message includes third information, where the third information indicates the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.
  • a setting device is provided, which is configured in an IAB node, wherein the IAB node includes an MT and a DU, wherein:
  • the MT receives a broadcast message sent by the RRC termination IAB host, where the broadcast message indicates a cell supporting mobile IAB;
  • the MT performs cell selection according to the broadcast message.
  • One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, the integration problem of the IAB node is solved, so that the IAB-MT and the collocated IAB-DU can be integrated into different donor-CUs, thereby improving the flexibility of network configuration.
  • FIG1 is a schematic diagram of an example of an IAB network topology
  • FIG2 is a schematic diagram of the integration process of the mobile IAB node according to an embodiment of the present application.
  • FIG3 is a schematic diagram of an IAB node integration method according to an embodiment of the first aspect of the present application.
  • FIG4 is a schematic diagram of the process of IAB-DU configuration during IAB node integration
  • FIG5 is another schematic diagram of the process of IAB-DU setup during IAB node integration
  • FIGS. 6a and 6b are schematic diagrams of two other examples of the IAB node integration method according to the embodiment of the first aspect of the present application;
  • FIG. 7a and 7b are schematic diagrams of two further examples of the IAB node integration method according to the embodiment of the first aspect of the present application.
  • FIG8 is a schematic diagram of an IAB node integration method according to an embodiment of the second aspect of the present application.
  • FIG9 is another schematic diagram of the process of IAB-DU setting during IAB node integration
  • FIG10 is another schematic diagram of the IAB node integration method of the embodiment of the second aspect of the present application.
  • FIG. 11a and 11b are schematic diagrams of two further examples of the IAB node integration method according to the embodiment of the second aspect of the present application.
  • FIG12 is a schematic diagram of a setting method according to an embodiment of the present application.
  • FIG13 is another schematic diagram of a setting method according to an embodiment of the present application.
  • FIG14 is a schematic diagram of an integrated device of an IAB node according to an embodiment of the present application.
  • FIG15 is another schematic diagram of an integrated device of an IAB node according to an embodiment of the present application.
  • FIG16 is another schematic diagram of an integrated device of an IAB node according to an embodiment of the present application.
  • FIG17 is another schematic diagram of an integrated device of an IAB node according to an embodiment of the present application.
  • FIG18 is another schematic diagram of an integrated device of an IAB node according to an embodiment of the present application.
  • FIG19 is a schematic diagram of a setting device according to an embodiment of the present application.
  • FIG20 is another schematic diagram of the setting device according to an embodiment of the present application.
  • FIG21 is a schematic diagram of an IAB node according to an embodiment of the present application.
  • FIG. 22 is a schematic diagram of an IAB-donor node according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements in terms of title, but do not indicate the spatial arrangement or temporal order of these elements, etc., and these elements should not be limited by these terms.
  • the term “and/or” includes any one and all combinations of one or more of the associated listed terms.
  • the terms “comprising”, “including”, “having”, etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.
  • the term “communication network” or “wireless communication network” may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), Enhanced Long Term Evolution (LTE-A), or the like. LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.
  • LTE Long Term Evolution
  • LTE-A Enhanced Long Term Evolution
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • communication between devices in the communication system may be carried out according to communication protocols of any stage, such as but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), etc., and/or other communication protocols currently known or to be developed in the future.
  • 1G generation
  • 2G 2.5G
  • 2.75G 3G
  • 4G 4G
  • 4.5G and future 5G
  • NR New Radio
  • the term "network device” refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • the network device may include, but is not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.
  • Base stations may include, but are not limited to, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include remote radio heads (RRH, Remote Radio Head), remote radio units (RRU, Remote Radio Unit), relays, or low-power nodes (such as femto, pico, etc.).
  • NodeB Node B
  • eNodeB or eNB evolved Node B
  • gNB 5G base station
  • the term “base station” may include some or all of their functions, and each base station may provide communication coverage for a specific geographical area.
  • the term “cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "user equipment” refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be referred to as "terminal equipment” (TE).
  • the terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), a terminal, a user, a subscriber station (SS), an access terminal (AT), a station, and the like.
  • Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDA), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, and IAB-MT, etc.
  • PDA personal digital assistants
  • wireless modems wireless communication devices
  • handheld devices machine-type communication devices
  • machine-type communication devices laptop computers
  • cordless phones smart phones
  • smart watches smart watches
  • digital cameras digital cameras
  • IAB-MT IAB-MT
  • the terminal device may also be a machine or device for monitoring or measuring, such as but not limited to: Machine Type Communications (MTC) Communication) terminals, vehicle-mounted communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and so on.
  • MTC Machine Type Communications
  • D2D device-to-device
  • M2M machine-to-machine
  • FIG. 1 is a schematic diagram of an example of an IAB network topology structure, showing a situation where an MT and a DU of an IAB are terminated to different donor-CUs.
  • the inventors have discovered that the mobility of a mobile IAB (mIAB) or a mobile relay in a larger area faces a challenge, that is, when it is on the move, based on the needs of network coverage and QoS support, the F1 termination host and non-F1 termination host of the IAB node may be different, that is, the MT and DU of the IAB terminate at different IAB-donor-CUs.
  • mIAB mobile IAB
  • a mobile relay in a larger area faces a challenge, that is, when it is on the move, based on the needs of network coverage and QoS support, the F1 termination host and non-F1 termination host of the IAB node may be different, that is, the MT and DU of the IAB terminate at different IAB-donor-CUs.
  • the F1-terminating node refers to the donor-CU that terminates the F1 interface of the IAB node, such as donor-CU2 shown in Figure 1.
  • IAB-DU1 is terminated to donor-CU2 through the F1 connection, so donor-CU2 is the F1 terminating node of IAB node 1.
  • the F1-terminating donor-CU can also be called the donor-CU of the IAB-DU because the IAB-DU is configured by this CU.
  • a non-F1-terminating node refers to a CU with a host function that does not terminate the F1 interface of the IAB node, such as the donor-CU1 shown in Figure 1. Since the non-F1-terminating node has an RRC connection with the IAB-MT, the non-F1-terminating node can also be called the host node serving the IAB-MT, and the non-F1-terminating host CU is also called the host CU of the IAB-MT, or the RRC-terminating donor-CU of the IAB node.
  • IAB-MT1 is connected to the parent node IAB node 2, and then connected to donor-DU1 and donor-CU1.
  • IAB-DU1 and donor-CU2 are connected via F1, but the path of this F1 connection is through IAB node 2, donor-DU1 and finally to donor-CU2.
  • the IAB node 1 Since the RRC interface and the F1 interface of the IAB node 1 are terminated at different donor-CUs, the IAB node 1 is a boundary IAB node.
  • the inventors found that in the existing IAB node integration process, the MT and DU of the IAB node are terminated to the same donor-CU. This cannot achieve the flexibility of mobile IAB nodes and cannot quickly support the topological adaptation between hosts of IAB nodes. Therefore, it is necessary to define how to support the integration of the MT and DU of the IAB node to different donor-CUs. That is, to support the network integration scenario shown in Figure 1 so that the border IAB nodes can also be integrated. However, there is currently no definition of the integration process of the MT and DU of the IAB node connecting to different donor-CUs.
  • the IAB node to which the UE is connected can be mobile.
  • FIG. 2 is a schematic diagram of the integration process of the mobile IAB node according to an embodiment of the present application, showing a general IAB The network integration of a node (IAB node 1 in Figure 2).
  • IAB-MT and IAB-DU of IAB node 1 are integrated into different IAB-donors.
  • IAB-donor 1 is the RRC-terminating IAB donor, that is, the donor to which the MT is connected
  • IAB-donor 2 is the F1-terminating IAB donor, that is, the donor to which the DU is connected.
  • the IAB-MT of IAB node 1 accesses the network in the first phase.
  • the IAB-MT connects to the network as a normal UE, and this process basically reuses the initial access process of a normal UE.
  • the host to which the IAB-MT accesses is donor-CU1.
  • donor-CU1 performs RRC configuration on the IAB-MT, including BH RLC channel establishment, etc., and donor-CU1 also performs routing updates on the IAB nodes between IAB node 1 and donor-DU1, such as IAB node 2, to support BAP routing from IAB node 1 to donor-DU1.
  • the IAB-DU of IAB node 1 establishes an F1 connection to donor-CU2, that is, F1 establishment is performed.
  • An embodiment of the present application provides an IAB node integration method, which is applied to the scenario shown in FIG. 2 .
  • FIG3 is a schematic diagram of an IAB node integration method according to an embodiment of the present application, which is described from one side of the IAB node.
  • the IAB node is, for example, the IAB node 1 in the scenario shown in FIG2 , and includes an MT and a DU.
  • the MT may also be referred to as an IAB-MT, and the DU may be referred to as an IAB-DU.
  • the method includes:
  • the DU of the IAB node is configured by OAM F1 to terminate the base station identifier of the CU of the IAB host;
  • the DU of the IAB node establishes F1 with the CU of the F1 termination IAB host according to the base station identifier.
  • FIG. 3 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order between the various operations can be appropriately adjusted, and other operations can be added or some operations can be reduced.
  • Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description of the above FIG. 3.
  • the base station identifier may be a gNB ID, a Global gNB ID, a Global NG-RAN node ID, etc.
  • the DU of the IAB node 1 needs to perform F1 establishment to the CU of the F1-terminating IAB host.
  • the IAB-DU is configured through OAM (Operation Administration and Maintenance), and the configuration content includes the base station identifier of the CU of the F1-terminating IAB host.
  • the DU of the IAB node can perform F1 establishment with the CU of the F1-terminating IAB host according to the base station identifier, which solves the problem of integrating the MT and DU of the mobile IAB node into different IAB-donors, thereby supporting the configuration flexibility of the IAB node, and supporting the mobility of the IAB node in a wide area, and being able to provide high-quality services for UEs served by mobile IAB nodes.
  • the CU of the IAB host terminated by RRC is different from the CU of the IAB host terminated by F1.
  • the IAB host terminated by RRC is IAB-donor 1
  • the CU of the IAB host terminated by RRC is IAB-Donor-CU1, which is also referred to as “CU1” or “donor-CU1” for the convenience of explanation
  • the IAB host terminated by F1 is IAB-donor 2
  • the CU of the IAB host terminated by F1 is IAB-donor-CU2, which is also referred to as “CU2” or “donor-CU2” for the convenience of explanation.
  • donor-CU1 allocates one or more IP addresses to IAB node 1 through RRC signaling, and these IP addresses are anchored at IAB-donor-DU1.
  • IAB node 1 can initiate TNL establishment and F1 establishment process to the CU (donor-CU2) of the F1 termination IAB host based on the IP address.
  • the IAB node is only configured with the above base station identifier, then the DU of the IAB node can also discover the TNL address of the CU (CU2) of the F1 termination host through the base station identifier, and establish F1 with CU2 based on the above base station identifier and the TNL address.
  • the IAB-DU can use the same method used by the non-IAB gNB-DU to discover the TNL address of donor-CU2 through the base station identifier, such as using the Xn-C TNL address discovery process, etc.
  • the base station identifier such as using the Xn-C TNL address discovery process, etc.
  • the IAB node is configured with both the above-mentioned base station identifier and the TNL address (i.e., IP address) of the CU (CU2) of the F1 termination host.
  • the DU of the IAB node can establish F1 with the CU of the F1 termination IAB host based on the base station identifier and the TNL address.
  • the IAB node is configured with multiple base station identifiers, and the DU of the IAB node can select a base station identifier from the multiple base station identifiers according to a predetermined policy to perform F1 establishment.
  • OAM configures the base station identification information of multiple CUs for the IAB-DU, such as including them in a list to indicate the candidate donor-CU information.
  • the IAB-DU can select one of the donor-CUs (for example, IAB-donor-CU2) then proceeds to F1 establishment.
  • the IAB node is further configured with priorities of multiple base station identifiers, and the DU of the IAB node may select a base station identifier with the highest priority among the multiple base station identifiers to perform F1 establishment.
  • the above list may also include the priority information of the IAB-donor-CU configured by OAM, which further indicates the IAB-DU and helps the IAB-DU to select the IAB-donor-CU.
  • the IAB-donor-CU indicated as high priority is selected first, and in case the F1 establishment fails, another IAB-donor-CU can be selected to establish the F1.
  • the DU of the IAB node initiates TNL establishment and F1 establishment procedures to the CU of the F1 terminating IAB host (IAB-donor-CU2) using the IP address allocated to the IAB node by the CU of the RRC terminating IAB host (IAB-donor-CU1).
  • the F1 setup request message (F1 SETUP REQUEST) may also include the BAP address of the IAB node. Therefore, after receiving the F1 setup request message, the CU (IAB-donor-CU2) that terminates the IAB host of F1 saves the BAP address for the IAB node.
  • IAB-donor-CU2 can use the BAP address as the BAP address used by the IAB node in the topology of IAB-donor-CU1, and IAB-donor-CU2 can also assign a BAP address in the topology of IAB-donor-CU2 to the IAB node.
  • IAB-donor-CU2 may send the allocated BAP address to IAB-DU via F1 SETUP RESPONSE message.
  • BAP Address IE in F1 SETUP RESPONSE message may be reused to indicate that it is the BAP address allocated by IAB-donor-CU2 to the IAB node, but the present application is not limited thereto.
  • the IAB node is equivalent to the topology belonging to two CUs (IAB-donor-CU1 and IAB-donor-CU2) and is configured by the two CUs.
  • the two CUs need to perform further information exchange to perform the IAB transmission migration management process and/or the IAB resource coordination process. These processes interact at the Xn interface between IAB-donor-CU1 and IAB-donor-CU2. Because IAB-donor-CU2 is the F1-terminating IAB host CU of the IAB node, these IAB-related Xn processes are generally initiated by the F1-terminating IAB host CU.
  • IAB-donor-CU2 needs to know the base station identifier of IAB-donor-CU1 and the UE XnAP ID of the IAB node in IAB-donor-CU1, that is, the NG-RAN node UE XnAP ID generated by IAB-donor-CU1 for the IAB node, also known as Non F1-terminating IAB-Donor UE XnAP ID.
  • the relevant information may be transmitted by the IAB node or by IAB-donor-CU1, so that IAB-donor-CU2 obtains the base station information of IAB-donor-CU1 and the UE XnAP ID generated by IAB-donor-CU1 for the IAB node.
  • the relevant information is transmitted by the IAB node.
  • the MT of the IAB node receives the first information sent by the CU (IAB-donor-CU1) of the RRC terminated IAB host, where the first information includes the identification information of the IAB node and/or the identification information of the RRC terminated IAB host; the DU of the IAB node sends the second information related to the above first information to the F1 terminated IAB host.
  • the identification information of the IAB node is, for example, the UE XnAP identification generated by the RRC terminating IAB host for the IAB node; the identification information of the RRC terminating IAB host is, for example, the base station identification information of the CU of the RRC terminating IAB host.
  • the base station identification can be a gNB ID, a Global gNB ID, a Global NG-RAN node ID, etc.
  • the DU of the IAB node can send the above second information to the F1 termination IAB host through the F1 SETUP REQUEST message when establishing F1 with the (future) F1 termination IAB host.
  • the present application is not limited to this, and the DU of the IAB node can also send the above second information through other F1AP signaling after the F1 is established.
  • IAB-donor-CU2 receives the second information, it can be concluded that the MT part of the IAB node does not belong to the topology of IAB-donor-CU2, that is, the MT of the IAB node is terminated on another donor-CU, and the IAB node is a boundary IAB node.
  • IAB-donor-CU2 can also determine that the MT of the IAB node is terminated on another donor-CU by judging that the BAP address of the IAB node in the received F1 SETUP REQUEST message or the IP address used is not within its own topology (that is, not allocated by IAB-donor-CU2).
  • the first information includes the identification information of the IAB node and the identification information of the RRC terminated IAB host.
  • the second information is the same as the first information, so the DU of the IAB node directly sends the first information obtained by the MT of the IAB node to the F1 terminated IAB host.
  • the "same" here means the same content, that is, the first information and the second information contain the same information.
  • the first information includes the identification information of the IAB node but does not include the identification information of the RRC termination IAB host.
  • the second information includes the serving cell identity NCGI of the MT of the IAB node and the identification information of the IAB node.
  • IAB-MT obtains the system information broadcast by IAB-donor-CU1.
  • Cell identification information (NCGI, NR Cell Global Identifier)
  • the cell identification information contains the base station identification
  • IAB-donor-CU1 can only send the UE XnAP ID of the IAB node to IAB-MT
  • the collocated IAB-DU sends the service cell identification NCGI of IAB-MT and the UE XnAP ID to IAB-donor-CU2. Therefore, IAB-donor-CU2 can determine the bit length of the base station identification by some method (such as based on OAM configuration), and then obtain the base station identification from NCGI.
  • the first information may be explicitly included in the RRC reconfiguration message or included in a container of the RRC reconfiguration message.
  • the RRC reconfiguration message includes a first IE, and the first IE includes the above first information;
  • the bap-Config IE of the RRC reconfiguration message includes a second IE or a first field, and the second IE or the first field includes the above first information.
  • the second information may be explicitly included in the F1AP message or included in a container of the F1AP message.
  • the F1AP message includes a third IE, and the third IE includes the above second information.
  • the F1AP message is, for example, an F1 establishment request message, but the present application is not limited thereto.
  • FIG4 is a schematic diagram of the process of IAB-DU configuration in the IAB node integration process, showing the case of IAB-DU configuration based on OAM. As shown in FIG4, the process includes:
  • IAB-donor-CU1 sends an RRC reconfiguration message to IAB-MT;
  • IAB-MT sends an RRC reconfiguration message completion (RRCReconfigurationComplete) message to IAB-donor-CU1;
  • the IAB-DU sends the second information to the IAB-donor-CU2;
  • the 5G core network performs relevant configuration on IAB-donor-CU2;
  • IAB-donor-CU2 feeds back an F1 establishment response message to the IAB-DU, indicating that the IAB-DU setup is completed and the IAB node can start to provide air interface services for the UE;
  • IAB-donor-CU2 sends "IAB TRANSPORT MIGRATION MANAGEMENT REQUEST" to IAB-donor-CU1;
  • IAB-donor-CU1 sends "IAB TRANSPORT MIGRATION MANAGEMENT RESPOSNE" to IAB-donor-CU2.
  • the above 401 and 402 are the process of IAB-donor-CU1 configuring IAB-MT.
  • IAB-donor-CU1 uses RRCReconfiguration message to configure the above first information;
  • the first information includes the UE XnAP ID of the IAB node and the optional base station identifier of IAB-donor-CU1.
  • the first information can be explicitly included in the RRC reconfiguration message or placed in the RRC reconfiguration message.
  • the IAB-DU directly puts the container into a F1 setup request message and sends it to IAB-donor-CU2. That is, the IAB node does not decode the container and directly transmits it transparently.
  • a new IE may be defined in the RRCReconfiguration message to indicate the first information
  • a new sub-IE second IE or field (first field) may be defined in the bap-Config IE in the RRCReconfiguration message to indicate the first information
  • the above 401 and the above 402 may occur in any stage before the third stage shown in FIG. 2 , for example, at any time from the first stage to the stage 2-2, and the present application does not impose any limitation on this.
  • OAM configures the IAB-DU, including the base station identifier of donor-CU2, etc., for the IAB-DU to establish F1 to the donor-CU2.
  • the IAB-DU may use the F1 SETUP REQUEST message to send the above second information.
  • the second information may include relevant identification information of the IAB-donor-CU1 and the UE XnAP ID of the IAB node in the IAB-donor-CU1 (from the first information).
  • the relevant identification information of the IAB-donor-CU1 may be the base station identifier in the first information or the NCGI of the serving cell.
  • the second information may be explicitly included in the F1AP message or placed in a container in the F1AP message. For example, a new IE (third IE) may be defined in the F1 SETUP REQUEST message to indicate the second information.
  • the above 406 and 407 are examples of IAB-related Xn processes between IAB-donor-CU2 and IAB-donor-CU1, which can be performed after the IAB integration process, such as the IAB Transport Migration Management process initiated by IAB-donor-CU2.
  • the present application is not limited to this.
  • IAB-donor-CU2 is able to obtain the base station information of IAB-donor-CU1 and the UE XnAP ID generated by IAB-donor-CU1 for the IAB node from the IAB node.
  • the relevant information is transmitted by IAB-donor-CU1.
  • OAM is configured for IAB-DU.
  • the MT of the IAB node sends a first RRC message to the CU (IAB-donor-CU1) of the RRC terminated IAB host, and the first RRC message includes the identification information of the F1 terminated IAB host configured by OAM, so that the RRC terminated IAB host sends the identification information of the above IAB node to the F1 terminated IAB host.
  • the first RRC message is, for example, a UEAssistanceInformation message; the UEAssistanceInformation message includes a fourth IE, and the fourth IE includes identification information of the F1 termination IAB host.
  • the MT of the IAB node can also terminate the DU and F1 of the IAB node.
  • the UE auxiliary information reporting process is initiated.
  • the IAB node has the ability to provide the identification information of the F1 terminating IAB host, and the IAB node is configured with capability reporting, and the IAB node is in the RRC connection state.
  • the IAB node has the ability to provide the identification information of the F1 terminating IAB host, and the IAB node is configured with capability reporting, then when the IAB is in the RRC connection state, it can initiate the above-mentioned UE auxiliary information reporting process after the F1 between the IAB-DU and CU2 is established.
  • the CU of the RRC-terminating IAB host may send a first Xn message to the F1-terminating IAB host, where the first Xn message includes the UE XnAP identifier generated by the RRC-terminating IAB host for the IAB node and/or the BAP address of the IAB node.
  • the F1 IAB termination host may also feed back a second Xn message to the CU of the RRC IAB termination host, where the second Xn message includes confirmation information.
  • FIG5 is another schematic diagram of the process of IAB-DU configuration in the IAB node integration process, showing the case of IAB-DU configuration based on OAM. As shown in FIG5, the process includes:
  • the 5G core network performs relevant configuration on IAB-donor-CU2;
  • IAB-donor-CU2 replies with an F1 establishment response to IAB-DU;
  • IAB-MT sends RRC message 1 to IAB-donor-CU1, and RRC message 1 includes the base station identifier of IAB-donor-CU2;
  • IAB-donor-CU1 sends an XnAP message 1 to IAB-donor-CU2, where the XnAP message 1 includes the UE XnAP ID and/or the BAP address of the IAB node;
  • IAB-donor-CU2 sends an XnAP message 2 to IAB-donor-CU1, where the XnAP message 2 includes confirmation information;
  • IAB-donor-CU2 sends "IAB TRANSPORT MIGRATION MANAGEMENT REQUEST" to IAB-donor-CU1;
  • IAB-donor-CU1 sends "IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE" to IAB-donor-CU2.
  • the above 501 to 503 are the conventional F1 establishment process from IAB-DU to IAB-donor-CU2, and the details may refer to the relevant technology.
  • the IAB node since the information of IAB-donor-CU2 is configured by OAM for the IAB node, the IAB node can inform IAB-donor-CU1 of the identification information of IAB-donor-CU2, so that IAB-donor-CU1 can send the IAB identification information to IAB-donor-CU2. Therefore, in 504, the IAB node can notify IAB-donor-CU1 through an uplink (UE to network side) RRC message.
  • the RRC message is a first RRC message, which includes the base station identifier of IAB-donor-CU2, that is, the F1-terminating host gNB ID of the IAB node, or the gNB ID of the CU of the IAB-DU collocated with the IAB-MT.
  • the first RRC message may reuse the UEAssistanceInformation message, for example, a new IE (fourth IE) is added to the UEAssistanceInformation message to include the base station identifier of IAB-donor-CU2.
  • a new IE fourth IE
  • the initialization part of the UE auxiliary information in the RRC layer can also be enhanced. For example, if a UE (IAB-MT) capable of providing F1 termination host node information is configured to report, the UE auxiliary information reporting process can be initiated in the connected state (RRC_CONNECTED) after the F1 establishment of the collocated IAB-DU is completed.
  • the above 505 and 506 are the XnAP process between RAN nodes, which is used for IAB-donor-CU1 to send the IAB identification information to IAB-donor-CU2.
  • a new XnAP process may be defined, for example, a UE-associated class 1 IAB process may be defined, which is composed of a first Xn message and a second Xn message. The process is initiated by the non-F1-terminating IAB-donor-CU.
  • the first Xn message contains the UE XnAP ID of the IAB-MT generated by the IAB-donor-CU1, and may also contain the BAP address of the IAB node, which is used by the IAB-donor-CU2 to identify the IAB node.
  • the second Xn message is a confirmation message of the IAB-donor-CU2.
  • the above-mentioned second Xn message is optional.
  • the second Xn message can be omitted.
  • the above 505 and 506 can also reuse the NG-RAN node Configuration Update process.
  • the IAB identification information (UE XnAP ID, BAP address of the IAB node) is included as a new IE in the NG-RAN NODE CONFIGURATION UPDATE message.
  • the above 507 and 508 are examples of IAB-related Xn processes between IAB-donor-CU2 and IAB-donor-CU1, which can be performed after the integration process of the IAB node, such as the IAB Transport Migration Management process initiated by IAB-donor-CU2.
  • the present application is not limited to this.
  • IAB-donor-CU2 is able to obtain the base station information of IAB-donor-CU1 and the UE XnAP ID generated by IAB-donor-CU1 for the IAB node from IAB-donor-CU1.
  • the MT of the IAB node may send an RRC setup complete message to the RRC termination IAB host.
  • the RRC establishment completion message includes third information, where the third information indicates the mobile IAB capability of the IAB node so that the RRC termination IAB host selects an AMF that supports mobile IAB.
  • IAB-MT can perform an RRC connection establishment process on IAB-donor-CU1 and authenticate to the network.
  • IAB-MT can include an indication of the mobile IAB node in the RRCSetupComplete message (RRC connection establishment completion message, also called message 5), which is used for IAB-donor to select an AMF (Access and Mobility Management Function) that supports mobile IAB.
  • RRCSetupComplete message RRC connection establishment completion message, also called message 5
  • AMF Access and Mobility Management Function
  • a cell that broadcasts "supporting mobile IAB” can be selected, that is, the cell is selected as the parent node cell.
  • the broadcast message about supporting the mobile IAB indication can be implemented by the SIB1 (System Information Block 1) message of the base station.
  • SIB1 System Information Block 1
  • Figure 6a is another schematic diagram of the IAB node integration method of the embodiment of the present application
  • Figure 6b is another schematic diagram of the IAB node integration method of the embodiment of the present application. Both examples are described from the side of the RRC-terminated IAB host.
  • the RRC-terminated IAB host is, for example, IAB-donor 1 shown in Figure 2, including CU (IAB-donor-CU1) and DU (IAB-donor-DU1), wherein the same contents as the previous embodiments are not repeated.
  • the method includes:
  • the RRC terminated IAB host sends first information to the MT of the IAB node (step 401), wherein the first information includes identification information of the IAB node and/or identification information of the RRC terminated IAB host, so that the DU of the IAB node sends second information related to the first information to the F1 terminated IAB host (step 403).
  • the identification information of the IAB node may be a UE XnAP identification generated by the RRC termination IAB host for the IAB node; the identification information of the RRC termination IAB host may be the base station identification information of the CU of the RRC termination IAB host.
  • the first information includes the identification information of the IAB node and the RRC terminal
  • the second information includes the identification information of the IAB host, and the second information is the same as the first information; in another example, the first information includes the identification information of the IAB node; the second information includes the serving cell identifier NCGI of the MT of the IAB node and the identification information of the IAB node.
  • the first information may be explicitly included in the RRC reconfiguration message or included in a container of the RRC reconfiguration message.
  • the RRC reconfiguration message includes a first IE, and the first IE includes the above first information; in another example, the bap-Config IE of the RRC reconfiguration message includes a second IE or a first field, and the second IE or the first field includes the above first information.
  • the method includes:
  • the CU of the RRC termination IAB host receives the first RRC message sent by the MT of the IAB node (step 504), and the first RRC message includes the identification information of the F1 termination IAB host; the RRC termination IAB host sends the identification information of the IAB node to the F1 termination IAB host according to the first RRC message.
  • the first RRC message may be a UEAssistanceInformation message; for example, the UEAssistanceInformation message includes a fourth IE, and the fourth IE includes identification information of the above-mentioned F1 termination IAB host.
  • the CU of the RRC terminating IAB host sends a first Xn message to the F1 terminating IAB host (step 505), and the first Xn message includes the UE XnAP identifier generated by the RRC terminating IAB host for the IAB node and/or the BAP address of the IAB node.
  • the CU of the RRC terminated IAB host may also receive a second Xn message sent by the F1 terminated IAB host (step 506), where the second Xn message includes confirmation information.
  • the CU (IAB-donor-CU1) of the RRC-terminated IAB host and the CU (IAB-donor-CU2) of the F1-terminated IAB host are different.
  • the CU of the RRC-terminating IAB host allocates one or more IP addresses to the IAB node, so that the IAB node uses the IP address to initiate TNL establishment and F1 establishment process to the CU of the F1-terminating IAB host.
  • the IP address can be anchored in the DU of the RRC-terminating IAB host.
  • the RRC termination IAB host may also receive an RRC establishment completion message sent by the MT of the IAB node, where the RRC establishment completion message includes third information, where the third information indicates the mobile IAB capability of the IAB node; the RRC termination IAB host selects an AMF that supports mobile IAB according to the third information.
  • the RRC terminated IAB host may also send a broadcast message, which indicates cells supporting mobile IAB; thus, after receiving the broadcast message, the IAB node may select a cell according to the broadcast message.
  • FIG7a is another schematic diagram of the IAB node integration method of the embodiment of the present application
  • FIG7b is another schematic diagram of the IAB node integration method of the embodiment of the present application. Both examples are described from the side of the F1-terminating IAB host.
  • the F1-terminating IAB host is, for example, IAB-donor 2 shown in FIG2, including CU (IAB-donor-CU2) and DU (IAB-donor-DU2), wherein the method of FIG7a corresponds to the method of FIG6a, and the method of FIG7b corresponds to the method of FIG6b, and the contents identical to those in the previous embodiments will not be repeated.
  • the method includes:
  • the F1 IAB termination host receives second information sent by the DU of the IAB node, where the second information is related to the first information, and the first information includes identification information of the IAB node and/or identification information of the RRC IAB termination host.
  • the identification information of the IAB node is the UE XnAP identification generated by the RRC terminating IAB host for the IAB node; the identification information of the RRC terminating IAB host is the base station identification information of the CU of the RRC terminating IAB host.
  • the first information includes identification information of the IAB node and identification information of the RRC termination IAB host, and the second information is the same as the first information; in another example, the first information includes identification information of the IAB node; the second information includes the service cell identifier NCGI of the MT of the IAB node and the identification information of the IAB node.
  • the second information is explicitly included in the F1AP message or included in a container of the F1AP message.
  • the F1AP message may be an F1 establishment request message.
  • the F1AP message may include a third IE, and the third IE includes the second information.
  • the CU of the F1 terminating IAB host receives an F1 establishment request message sent by the DU of the IAB node, where the F1 establishment request message includes the BAP address of the IAB node; the F1 terminating IAB host saves the BAP address for the IAB node.
  • the method includes:
  • the F1 IAB termination host receives a first Xn message sent by the CU of the RRC IAB termination host, where the first Xn message includes the UE XnAP identifier generated by the RRC IAB termination host for the IAB node and/or the BAP address of the IAB node.
  • the F1 terminating IAB host may further send a second Xn message to the CU of the RRC terminating IAB host, where the second Xn message includes confirmation information.
  • the integration problem of the IAB node is solved, so that the IAB-MT and the collocated IAB-DU can be integrated into different donor-CUs, thereby improving the flexibility of network configuration.
  • the embodiment of the present application provides an IAB node integration method, which is applied to the scenario shown in Figure 2.
  • the F1-terminating donor-CU that is, IAB-donor-CU2
  • IAB-donor-CU1 the F1-terminating donor-CU (that is, IAB-donor-CU2) of the IAB node is specified by IAB-donor-CU1. That is, the above-mentioned relevant information of IAB-donor-CU2 is not configured to IAB-DU by OAM, but is configured to IAB-MT by the CU of the RRC terminating IAB host.
  • FIG8 is a schematic diagram of an IAB node integration method according to an embodiment of the present application, which is described from the side of an RRC-terminated IAB host, where the RRC-terminated IAB host is, for example, IAB-donor 1 shown in FIG2 , including CU (IAB-donor-CU1) and DU (IAB-donor-DU1), wherein the same contents as those in the embodiment of the first aspect are not repeated.
  • the method includes:
  • the CU of the RRC-terminated IAB host determines the base station identifier of the CU of the F1-terminated IAB host for the IAB node;
  • the CU of the RRC-terminating IAB host sends the base station identifier of the CU of the F1-terminating IAB host to the MT of the IAB node, so that the DU of the IAB node establishes F1 with the CU of the F1-terminating IAB host according to the base station identifier.
  • FIG8 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order between the various operations can be appropriately adjusted, and other operations can be added or some operations can be reduced.
  • Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description of the above FIG8.
  • the CU of the RRC terminated IAB host is configured with the base station identifier of the F1 terminated IAB host by OAM, thereby obtaining the base station identifier of the CU of the F1 terminated IAB host.
  • OAM configures multiple IAB-donor-CU base station identifiers, and RRC terminates the CU root of the IAB host.
  • a base station identifier is selected from the multiple base station identifiers according to a predetermined strategy.
  • OAM configures multiple IAB-donor-CU base station identifiers and the priority of each base station identifier, and the CU of the RRC-terminated IAB host selects the base station identifier with the highest priority among the multiple base station identifiers.
  • the CU of the RRC termination IAB host selects the F1 termination IAB host by itself according to the information (e.g., neighboring cell information) obtained based on the ANR (Automatic neighbor relations) function, thereby obtaining the base station identifier of the F1 termination IAB host.
  • the information e.g., neighboring cell information
  • ANR Automatic neighbor relations
  • the CU of the RRC termination IAB host sends the base station identifier of the F1 termination IAB host to the MT of the IAB node through an RRC reconfiguration message.
  • the IAB node obtains the base station identifier of the F1 termination IAB host.
  • the base station identifier of the F1 terminating IAB host is obtained, and the DU of the IAB node can establish F1 with the CU of the F1 terminating IAB host according to the base station identifier and the TNL address of the CU of the F1 terminating IAB host discovered through the base station identifier.
  • the base station identifier of the F1 terminating IAB host is obtained, and the DU of the IAB node can establish F1 with the CU of the F1 terminating IAB host according to the base station identifier and the TNL address of the CU of the F1 terminating IAB host discovered through the base station identifier.
  • the CU of the RRC terminated IAB host also sends the TNL address of the CU of the F1 terminated IAB host to the MT of the IAB node through an RRC reconfiguration message.
  • the DU of the IAB node establishes F1 with the CU of the F1 terminated IAB host according to the base station identifier and the TNL address.
  • the RRC reconfiguration message carries the above base station identifier.
  • a new IE (called the fifth IE) may be added to the RRC reconfiguration message or a new sub-IE (called the sixth IE) or field (called the second field) may be defined in the bap-Config IE of the RRC reconfiguration message to indicate the base station identifier and TNL address (optional) of the F1-terminating IAB host.
  • the fifth IE includes the base station identifier and TNL address (optional) of the F1-terminating IAB host; for another example, the sixth IE or the second field includes the base station identifier and TNL address (optional) of the F1-terminating IAB host.
  • the CU of the RRC-terminated IAB host allocates one or more IP addresses to the IAB node, and the IP address is anchored to the DU of the RRC-terminated IAB host.
  • the IAB node can use the allocated IP address to initiate TNL establishment and F1 establishment process to the CU of the F1-terminated IAB host.
  • the embodiment of the first aspect please refer to the embodiment of the first aspect.
  • the CU (IAB-donor-CU1) of the RRC termination IAB host further sends first information to the MT of the IAB node, where the first information includes the identification information of the IAB node and/or the RRC termination IAB host. Identification information; the DU of the IAB node sends the second information related to the above first information to the F1 terminating IAB host.
  • the identification information of the IAB node, the identification information of the RRC termination IAB host, the content related to the first information, and the content related to the second information can refer to the embodiment of the first aspect, and will not be repeated here.
  • the first information may be sent through an RRC reconfiguration message.
  • the first information may be sent through an RRC reconfiguration message together with the base station identifier of the F1 terminating IAB host.
  • the specific process may refer to FIG. 4, except that, in step 401, the RRC reconfiguration message may include not only the first information but also the base station identifier of the F1 terminating IAB host.
  • the CU of the RRC terminating IAB host sends a first Xn message to the F1 terminating IAB host, and the first Xn message includes the UE XnAP identifier generated by the RRC terminating IAB host for the IAB node and/or the BAP address of the IAB node.
  • the first Xn message includes the UE XnAP identifier generated by the RRC terminating IAB host for the IAB node and/or the BAP address of the IAB node.
  • the CU of the RRC terminated IAB host receives a second Xn message sent by the F1 terminated IAB host, where the second Xn message includes confirmation information.
  • the embodiment of the first aspect such as operation 506 shown in FIG. 5 .
  • FIG9 is another schematic diagram of the process of IAB-DU setting in the IAB node integration process, showing the case where IAB-donor-CU1 specifies IAB-donor-CU2. As shown in FIG9 , the process includes:
  • IAB-donor-CU1 sends an RRC reconfiguration message to IAB-MT.
  • the RRC reconfiguration message includes a base station identifier and a TNL address (optional) of IAB-donor-CU2.
  • IAB-MT sends an RRC reconfiguration complete (RRCReconfigurationComplete) message to IAB-donor-CU1;
  • IAB-DU establishes F1 with IAB-donor-CU2;
  • the 5G core network performs relevant configuration on IAB-donor-CU2;
  • IAB-donor-CU2 replies with an F1 establishment response to IAB-DU;
  • IAB-donor-CU1 sends an XnAP message 1 to IAB-donor-CU2, where the XnAP message 1 includes the UE XnAP ID and/or the BAP address of the IAB node;
  • IAB-donor-CU2 sends an XnAP message 2 to IAB-donor-CU1, where the XnAP message 2 includes confirmation information;
  • IAB-donor-CU2 sends "IAB TRANSPORT MIGRATION MANAGEMENT REQUEST" to IAB-donor-CU1;
  • IAB-donor-CU1 sends "IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE" to IAB-donor-CU2.
  • IAB-donor-CU1 broadcasts a list through the cell, which includes one or more base station identifiers of IAB-donor-CUs that support mobile IAB and have IP connection with IAB-donor-DU1.
  • IAB-MT accesses in the first stage, it selects IAB-donor-CU2 by receiving the broadcast message.
  • the selection criteria can be based on OAM configuration, or by comparing the IAB-donor-CU list configured in OAM with the broadcast IAB-donor-CU list to determine whether to access the cell and whether cell reselection is required.
  • the RRC termination IAB host may also receive an RRC establishment completion message sent by the MT of the IAB node, the RRC establishment completion message including third information, the third information indicating the mobile IAB capability of the IAB node; thus, the RRC termination IAB host may select an AMF supporting mobile IAB according to the third information.
  • the RRC termination IAB host may select an AMF supporting mobile IAB according to the third information.
  • the DU of the RRC-terminated IAB host may also send a broadcast message indicating cells supporting mobile IAB so that the IAB node performs cell selection according to the broadcast message.
  • a broadcast message indicating cells supporting mobile IAB so that the IAB node performs cell selection according to the broadcast message.
  • FIG10 is another schematic diagram of the IAB node integration method of the embodiment of the present application, which is described from one side of the IAB node. The contents that are the same as those in the embodiment of the first aspect and the previous embodiment are not repeated. As shown in FIG10 , the method includes:
  • the MT of the IAB node is configured by the CU of the IAB host to terminate the RRC, and the base station identifier of the CU of the IAB host is terminated by F1;
  • the DU of the IAB node establishes F1 with the CU of the F1 termination IAB host according to the base station identifier.
  • the MT of the IAB node is also configured with the TNL address of the CU of the F1 terminating IAB host.
  • the behavior of the IAB node is the same as that of the IAB node in the embodiment of the first aspect, and the description is omitted here.
  • the MT of the IAB node further receives first information from IAB-donor-CU1, and sends second information to IAB-donor-CU2 accordingly.
  • FIG. 11a is another schematic diagram of the IAB node integration method according to an embodiment of the present application
  • FIG. 11b is another schematic diagram of the IAB node integration method according to an embodiment of the present application.
  • Another schematic diagram of the IAB node integration method of the embodiment both examples are described from the side of the F1 terminating IAB host. The same contents as the embodiment of the first aspect and the previous embodiment will not be repeated.
  • the method includes:
  • the F1 IAB termination host receives second information sent by the DU of the IAB node, where the second information is related to the first information, and the first information includes identification information of the IAB node and/or identification information of the RRC IAB termination host.
  • the method includes:
  • the F1 terminated IAB host receives a first Xn message sent by the CU of the RRC terminated IAB host, where the first Xn message includes a UE XnAP identifier generated by the RRC terminated IAB host for the IAB node and/or a BAP address of the IAB node.
  • the F1 terminating IAB host further sends a second Xn message to the CU of the RRC terminating IAB host, where the second Xn message includes confirmation information.
  • the integration problem of the IAB node is solved, so that the IAB-MT and the collocated IAB-DU can be integrated into different donor-CUs, thereby improving the flexibility of network configuration.
  • An embodiment of the present application provides a setting method, which is applied to the scenario shown in Figure 2 and is explained from the side of the IAB node.
  • the IAB node is, for example, the IAB node 1 in the scenario shown in Figure 2, which includes an MT and a DU.
  • the MT can also be called an IAB-MT
  • the DU can be called an IAB-DU.
  • FIG. 12 is a schematic diagram of a setting method according to an embodiment of the present application. As shown in FIG. 12 , the method includes:
  • the MT of the IAB node sends an RRC setup completion message to the RRC termination IAB host, where the RRC setup completion message includes third information, where the third information indicates the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.
  • the IAB-MT performs an RRC connection establishment process on the IAB-donor-CU1 and authenticates the network.
  • the IAB-MT may include an indication of the mobile IAB node in the RRCSetupComplete message (RRC Setup Complete message, also called message 5) for the IAB-donor to select an AMF (Access and Mobility Management Function) that supports mobile IAB.
  • RRCSetupComplete message RRC Setup Complete message, also called message 5
  • AMF Access and Mobility Management Function
  • FIG. 13 is another schematic diagram of a setting method according to an embodiment of the present application. As shown in FIG. 13 , the method includes:
  • the MT of the IAB node receives a broadcast message sent by the RRC termination IAB host, where the broadcast message indicates a cell supporting mobile IAB;
  • the MT of the IAB node selects a cell according to the broadcast message.
  • the broadcast message is, for example, a SIB message, but the present application is not limited thereto.
  • a cell that broadcasts “support for mobile IAB” can be selected, that is, the cell is selected as the parent node cell.
  • the broadcast message about the support for mobile IAB indication can be implemented by a SIB (System Information Block) message of the base station.
  • SIB System Information Block
  • the integration problem of the IAB node is solved, so that the IAB-MT and the collocated IAB-DU can be integrated into different donor-CUs, thereby improving the flexibility of network configuration.
  • An embodiment of the present application provides an integrated device of an IAB node.
  • FIG14 is a schematic diagram of an integrated device of an IAB node according to an embodiment of the present application, which device may be, for example, an IAB node in an IAB network, or may be one or more components or assemblies configured in the IAB node.
  • the IAB node corresponds to the IAB node 1 in FIG2 , and the contents identical to those in the embodiment of the first aspect are not repeated here.
  • the device includes an IAB-MT (mobile terminal) 1401 and an IAB-DU (distributed unit) 1402, wherein the IAB-DU 1402 is configured by OAM or the IAB-MT 1401 is configured by the CU of the RRC-terminated IAB host with the base station identifier of the CU of the F1-terminated IAB host; the IAB-DU 1402 establishes F1 with the CU of the F1-terminated IAB host according to the base station identifier.
  • the IAB-MT mobile terminal
  • IAB-DU distributed unit
  • the RRC terminates the CU of the IAB host and the F1 terminates the CU of the IAB host. different.
  • the IAB-DU 1402 discovers the TNL address of the CU of the F1-terminating IAB host through the base station identifier; the IAB-DU 1402 establishes F1 with the CU of the F1-terminating IAB host according to the base station identifier and the TNL address.
  • the IAB-DU 1402 is also configured by the OAM with the TNL address of the CU of the F1-terminating IAB host; the IAB-DU 1402 establishes F1 with the CU of the F1-terminating IAB host according to the base station identifier and the TNL address.
  • the OAM is configured with multiple base station identifiers, and the IAB-DU 1402 selects a base station identifier from the multiple base station identifiers according to a predetermined strategy to establish F1.
  • the OAM can also configure the priorities of the multiple base station identifiers, and the IAB-DU 1402 selects the base station identifier with the highest priority among the multiple base station identifiers to establish F1.
  • the IAB-DU 1402 uses the IP address allocated by the CU of the RRC-terminating IAB host to the IAB node to initiate TNL establishment and F1 establishment processes to the CU of the F1-terminating IAB host.
  • the F1 establishment request message may include the BAP address of the IAB node; after receiving the F1 establishment request message, the CU of the F1 terminating IAB host saves the BAP address for the IAB node.
  • the number of IP addresses that the CU of the RRC-terminating IAB host can allocate to the IAB node is one or more, and the IP address is anchored to the DU of the RRC-terminating IAB host.
  • the IAB-MT 1401 receives first information sent by the CU of the RRC-terminated IAB host, wherein the first information includes identification information of the IAB node and/or identification information of the RRC-terminated IAB host; the IAB-DU 1402 sends second information related to the first information to the F1-terminated IAB host.
  • the identification information of the IAB node may be the UE XnAP identification generated by the RRC termination IAB host for the IAB node; the identification information of the RRC termination IAB host may be the base station identification information of the CU of the RRC termination IAB host.
  • the first information may include the identification information of the IAB node and the identification information of the RRC termination IAB host, and the second information is the same as the first information; or the first information
  • the second information may include identification information of the IAB node; and the second information includes a serving cell identifier NCGI of the MT of the IAB node and identification information of the IAB node.
  • the first information may be explicitly included in the RRC reconfiguration message or included in a container of the RRC reconfiguration message.
  • the RRC reconfiguration message may include a first IE, which includes the first information; or, the bap-Config IE of the RRC reconfiguration message may include a second IE or a first field, which includes the first information.
  • the second information may be explicitly included in the F1AP message or included in a container of the F1AP message.
  • the F1AP message may be an F1 establishment request message.
  • the F1AP message may include a third IE, and the third IE includes the second information.
  • the IAB-MT 1401 sends a first RRC message to the CU of the RRC termination IAB host, and the first RRC message includes identification information of the F1 termination IAB host, so that the RRC termination IAB host sends the identification information of the IAB node to the F1 termination IAB host.
  • the first RRC message may be a UEAssistanceInformation message; the UEAssistanceInformation message may include a fourth IE, and the fourth IE may include identification information of the F1 termination IAB host.
  • the IAB-MT 1401 can initiate the UE auxiliary information reporting process after the F1 establishment between the IAB-DU 1402 and the F1 termination IAB host is completed; wherein the IAB node has the ability to provide identification information of the F1 termination IAB host, and the IAB node is configured with capability reporting, and the IAB node is in an RRC connected state.
  • the CU of the RRC termination IAB host can send a first Xn message to the F1 termination IAB host, and the first Xn message includes the UE XnAP identifier generated by the RRC termination IAB host for the IAB node and/or the BAP address of the IAB node.
  • the CU of the RRC termination IAB host may receive the second Xn message sent by the F1 termination IAB host, where the second Xn message includes confirmation information.
  • the IAB-MT 1401 sends an RRC establishment completion message to the RRC termination IAB host, wherein the RRC establishment completion message includes third information, wherein the third information indicates the IAB node
  • the RRC termination IAB host selects an AMF that supports mobile IAB.
  • the IAB-MT 1401 receives a broadcast message sent by the RRC terminated IAB host, wherein the broadcast message indicates a cell supporting mobile IAB; the IAB-MT 1401 performs cell selection based on the broadcast message.
  • FIG15 is another schematic diagram of an integrated device of an IAB node according to an embodiment of the present application, which device may be, for example, an IAB host in an IAB network, or may be one or more components or assemblies configured in the IAB host.
  • the IAB host corresponds to the RRC-terminated IAB host in FIG2 , i.e., IAB-donor 1, and the contents identical to those in the embodiment of the first aspect will not be repeated.
  • the integrated device 1500 of the IAB node includes: a central unit (IAB-donor-CU1) 1501 and a distributed unit (IAB-donor-DU1) 1502 .
  • the IAB-donor-CU1 1501 sends first information to the MT of the IAB node, wherein the first information includes identification information of the IAB node and/or identification information of the RRC terminated IAB host, so that the DU of the IAB node sends second information related to the first information to the F1 terminated IAB host.
  • the identification information of the IAB node may be the UE XnAP identification generated by the RRC termination IAB host for the IAB node; the identification information of the RRC termination IAB host may be the base station identification information of the CU of the RRC termination IAB host.
  • the first information may include the identification information of the IAB node and the identification information of the RRC termination IAB host, and the second information is the same as the first information; or, the first information may include the identification information of the IAB node; the second information includes the service cell identifier NCGI of the MT of the IAB node and the identification information of the IAB node.
  • the first information may be explicitly included in the RRC reconfiguration message or included in a container of the RRC reconfiguration message.
  • the RRC reconfiguration message may include a first IE, which includes the first information; or, the bap-Config IE of the RRC reconfiguration message may include a second IE or a first field, which includes the first information.
  • the IAB-donor-CU1 1501 receives a first RRC message sent by the MT of the IAB node, where the first RRC message includes identification information of the F1 terminating IAB host; the IAB-donor-CU1 1501 sends the identification information of the IAB node to the MT according to the first RRC message.
  • the F1 terminates the IAB host.
  • the first RRC message may be a UEAssistanceInformation message; the UEAssistanceInformation message may include a fourth IE, and the fourth IE includes identification information of the F1 termination IAB host.
  • the IAB-donor-CU1 1501 can send a first Xn message to the F1 termination IAB host, and the first Xn message includes the UE XnAP identifier generated by the RRC termination IAB host for the IAB node and/or the BAP address of the IAB node.
  • the IAB-donor-CU1 1501 can also receive a second Xn message sent by the F1 terminating IAB host, and the second Xn message includes confirmation information.
  • the CU of the RRC terminating IAB host is different from the CU of the F1 terminating IAB host.
  • the IAB-donor-CU1 1501 allocates one or more IP addresses to the IAB node so that the IAB node initiates TNL establishment and F1 establishment process to the CU of the F1 terminating IAB host according to the IP address.
  • the IP address is anchored at the DU of the RRC-terminating IAB host.
  • the IAB-donor-CU1 1501 receives an RRC establishment completion message sent by the MT of the IAB node, and the RRC establishment completion message includes third information, and the third information indicates the mobile IAB capability of the IAB node; the IAB-donor-CU1 1501 selects an AMF that supports mobile IAB according to the third information.
  • the IAB-donor-CU1 1501 sends a broadcast message, wherein the broadcast message indicates cells supporting mobile IAB; so that after receiving the broadcast message, the IAB node selects a cell according to the broadcast message.
  • FIG16 is another schematic diagram of an integrated device of an IAB node according to an embodiment of the present application, which device may be, for example, an IAB host in an IAB network, or may be one or more components or assemblies configured in the IAB host.
  • the IAB host corresponds to the F1-terminating IAB host in FIG2 , i.e., IAB-donor 2, and the contents identical to those in the embodiment of the first aspect will not be repeated.
  • the integrated device 1600 of the IAB node includes: a central unit (IAB-donor-CU2) 1601 and a distributed unit (IAB-donor-DU2) 1602 .
  • the IAB-donor-CU2 1601 receives a second signal sent by the DU of the IAB node.
  • the second information is related to the first information, and the first information includes the identification information of the IAB node and/or the identification information of the RRC termination IAB host.
  • the identification information of the IAB node is the UE XnAP identification generated by the RRC termination IAB host for the IAB node; the identification information of the RRC termination IAB host is the base station identification information of the CU of the RRC termination IAB host.
  • the first information includes the identification information of the IAB node and the identification information of the RRC termination IAB host, and the second information is the same as the first information; or, the first information includes the identification information of the IAB node; the second information includes the service cell identifier NCGI of the MT of the IAB node and the identification information of the IAB node.
  • the second information is explicitly included in the F1AP message or included in a container of the F1AP message.
  • the F1AP message may be an F1 establishment request message.
  • the F1AP message may include a third IE, and the third IE includes the second information.
  • the IAB-donor-CU2 1601 receives an F1 establishment request message sent by the DU of the IAB node, and the F1 establishment request message includes the BAP address of the IAB node; the IAB-donor-CU2 saves the BAP address for the IAB node.
  • the IAB-donor-CU2 1601 receives a first Xn message sent by the CU of the RRC termination IAB host, and the first Xn message includes a UE XnAP identifier generated by the RRC termination IAB host for the IAB node and/or a BAP address of the IAB node.
  • the IAB-donor-CU2 1601 may also send a second Xn message to the CU of the RRC terminating IAB host, and the second Xn message includes confirmation information.
  • FIG. 17 is another schematic diagram of an integrated device of an IAB node according to an embodiment of the present application, which device may be, for example, an IAB host in an IAB network, or may be one or more components or assemblies configured in the IAB host.
  • the IAB host corresponds to the RRC-terminated IAB host in FIG. 2 , i.e., IAB-donor 1, and the contents identical to those in the embodiment of the second aspect will not be repeated.
  • the integrated device 1700 of the IAB node includes: a central unit (IAB-donor-CU1) 1701 and a distributed unit (IAB-donor-DU1) 1702 .
  • IAB-donor-CU1 1701 determines the base station identifier of the CU of which F1 terminates the IAB host.
  • the F1 termination IAB host CU base station identifier is sent to the IAB node MT, so that the IAB node DU according to the base station identifier and the F1 termination IAB host CU F1 establishment.
  • IAB-donor-CU1 1701 determines the base station identifier of the F1 terminating IAB host, including:
  • IAB-donor-CU1 1701 is configured by OAM with the base station identifier of the F1 terminating IAB host; or,
  • IAB-donor-CU1 1701 selects the F1 termination IAB host according to the information obtained based on the ANR function, thereby obtaining the base station identifier of the F1 termination IAB host.
  • the OAM can configure multiple base station identifiers, and the IAB-donor-CU1 1701 selects a base station identifier from the multiple base station identifiers according to a predetermined strategy.
  • the OAM may also configure the priorities of the multiple base station identifiers, and the IAB-donor-CU1 1701 selects a base station identifier with the highest priority among the multiple base station identifiers.
  • the IAB-donor-CU1 1701 sends the base station identifier of the F1 terminated IAB host to the MT of the IAB node via an RRC reconfiguration message.
  • the DU of the IAB node may perform F1 establishment with the CU of the F1 terminating IAB host according to the base station identifier and the TNL address of the CU of the F1 terminating IAB host discovered through the base station identifier.
  • the IAB-donor-CU1 1701 can also send the TNL address of the CU of the F1 termination IAB host to the MT of the IAB node through the RRC reconfiguration message; the DU of the IAB node establishes F1 with the CU of the F1 termination IAB host according to the base station identifier and the TNL address.
  • the RRC reconfiguration message may include a fifth IE, and the fifth IE includes the base station identifier of the F1 termination IAB host; or, the bap-Config IE of the RRC reconfiguration message may include a sixth IE or a second field, and the sixth IE or the second field includes the base station identifier.
  • the IAB-donor-CU1 1701 sends a first Xn message to the F1 termination IAB host, and the first Xn message includes a UE XnAP identifier generated by the RRC termination IAB host for the IAB node and/or a BAP address of the IAB node.
  • the IAB-donor-CU1 1701 can also receive a second Xn message sent by the F1 terminating IAB host, and the second Xn message includes confirmation information.
  • the IAB-donor-CU1 1701 allocates one or more IP addresses to the IAB node, and the IP addresses are anchored at the DU of the RRC-terminating IAB host.
  • the IAB-donor-CU1 1701 receives the RRC
  • the RRC establishment completion message includes third information, and the third information indicates the mobile IAB capability of the IAB node; the IAB-donor-CU1 1701 selects an AMF that supports mobile IAB according to the third information.
  • the IAB-donor-DU1 1702 sends a broadcast message indicating cells supporting mobile IAB so that the IAB node performs cell selection based on the broadcast message.
  • FIG18 is another schematic diagram of an integrated device of an IAB node according to an embodiment of the present application, which device may be, for example, an IAB host in an IAB network, or may be one or more components or assemblies configured in the IAB host.
  • the IAB host corresponds to the F1-terminating IAB host in FIG2 , i.e., IAB-donor 2, and the contents identical to those in the embodiment of the second aspect will not be repeated.
  • the integrated device 1800 of the IAB node includes: a central unit (IAB-donor-CU1) 1801 and a distributed unit (IAB-donor-DU1) 1802 .
  • IAB-donor-CU1 1801 receives a first Xn message sent by the CU of the RRC-terminating IAB host, and the first Xn message includes a UE XnAP identifier generated by the RRC-terminating IAB host for the IAB node and/or a BAP address of the IAB node.
  • IAB-donor-CU1 1801 also sends a second Xn message to the CU of the RRC terminating IAB host, and the second Xn message includes confirmation information.
  • the embodiment of the present application provides a setting device.
  • the device may be, for example, an IAB node in an IAB network, or may be one or more components or assemblies configured in the IAB node.
  • the IAB node corresponds to the IAB node 1 in FIG. 2 , and the contents identical to those of the embodiments of the first aspect to the embodiments of the third aspect are not repeated.
  • FIG19 is a schematic diagram of a setting device according to an embodiment of the present application.
  • the device 1900 includes: a mobile terminal (IAB-MT) 1901 and a distributed unit (IAB-DU) 1902 .
  • IAB-MT mobile terminal
  • IAB-DU distributed unit
  • IAB-MT 1901 sends an RRC establishment completion message to the RRC termination IAB host, and the RRC establishment completion message includes third information, and the third information indicates the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.
  • FIG20 is another schematic diagram of a setting device according to an embodiment of the present application.
  • the device 2000 includes: a mobile terminal (IAB-MT) 2001 and a distributed unit (IAB-DU) 2002 .
  • IAB-MT mobile terminal
  • IAB-DU distributed unit
  • the IAB-MT 2001 receives a broadcast message sent by the RRC termination IAB host, wherein the broadcast message indicates a cell supporting mobile IAB; the IAB-MT 2001 performs cell selection according to the broadcast message.
  • the above-mentioned broadcast message is a SIB message, but the present application is not limited to this.
  • FIG. 14 to FIG. 20 only exemplarily illustrate the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned various components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.
  • the integration problem of the IAB node is solved, so that the IAB-MT and the collocated IAB-DU can be integrated into different donor-CUs, thereby improving the flexibility of network configuration.
  • the embodiment of the present application provides an IAB communication system, including an IAB node and an IAB-donor node, wherein the IAB node is configured to execute the method executed by the IAB node in the embodiment of any one of the first aspect to the third aspect, and the IAB-donor node is configured to execute the method executed by IAB-donor 1 or IAB-donor 2 in the embodiment of any one of the first aspect to the third aspect.
  • IAB node is configured to execute the method executed by the IAB node in the embodiment of any one of the first aspect to the third aspect
  • IAB-donor node is configured to execute the method executed by IAB-donor 1 or IAB-donor 2 in the embodiment of any one of the first aspect to the third aspect.
  • An embodiment of the present application further provides an IAB node, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method performed by the IAB node in the embodiment of any one of the first to third aspects.
  • FIG21 is a schematic diagram of an IAB node according to an embodiment of the present application.
  • the IAB node 2100 may include a processor 2101 and a memory 2102; the memory 2102 stores data and programs and is coupled to the processor 2101. It is worth noting that the figure is exemplary; other types of structures may also be used to supplement or replace the structure to implement telecommunication functions or other functions.
  • the processor 2101 may be configured to execute a program to implement a method performed by the IAB node in the embodiment of any one of the first aspect to the third aspect.
  • the IAB node 2100 may further include: a communication module 2103, an input unit 2104, a display 2105, and a power supply 2106.
  • the functions of the above components are similar to those in the prior art and will not be described in detail here. It is worth noting that the IAB node 2100 does not necessarily include all the components shown in FIG. 21 , and the above components are not necessary; in addition, the IAB node 2100 may also include components not shown in FIG. 21 , and reference may be made to the prior art.
  • An embodiment of the present application also provides an IAB-donor node, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method performed by IAB-donor 1 or IAB-donor 2 in the embodiment of any one of the first to third aspects.
  • FIG22 is a schematic diagram of an IAB-donor node according to an embodiment of the present application.
  • an IAB-donor node 2200 may include: a central processing unit (CPU) 2201 and a memory 2202; the memory 2202 is coupled to the CPU 2201.
  • the memory 2202 may store various data; in addition, it may store information processing programs, and execute the programs under the control of the CPU 2201 to receive various information sent by the IAB node and send various information to the IAB node.
  • processor 2201 can be configured to execute a program to implement a method performed by IAB-donor 1 or IAB-donor 2 in an embodiment of any one of the first to third aspects.
  • the IAB-donor node 2200 may also include: a transceiver 2203 and an antenna 2204, etc.; wherein the functions of the above components are similar to those of the prior art and are not described in detail here. It is worth noting that the IAB-donor node 2200 does not necessarily include all the components shown in FIG22; in addition, the IAB-donor node 2200 may also include components not shown in FIG22, and reference may be made to the prior art.
  • An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in an IAB node, the program enables a computer to execute in the IAB node the method performed by the IAB node in the embodiment of any one of the first to third aspects.
  • An embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute in the IAB node the method executed by the IAB node in the embodiment of any one of the first aspect to the third aspect.
  • An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in an IAB-donor node, the program causes the computer to execute in the IAB-donor node the method performed by IAB-donor 1 or IAB-donor 2 in the embodiment of any one of the first to third aspects.
  • the embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to perform the implementation of any one of the first to third aspects in an IAB-donor node.
  • the above devices and methods of the present application can be implemented by hardware, or by hardware combined with software.
  • the present application relates to such a computer-readable program, which, when executed by a logic component, enables the logic component to implement the above-mentioned devices or components, or enables the logic component to implement the various methods or steps described above.
  • the logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, etc.
  • the present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.
  • the method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams shown in the figure and/or one or more combinations of the functional block diagrams may correspond to various software modules of the computer program flow or to various hardware modules.
  • These software modules may correspond to the various steps shown in the figure, respectively.
  • These hardware modules may be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).
  • FPGA field programmable gate array
  • the software module may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • a storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor.
  • the processor and the storage medium may be located in an ASIC.
  • the software module may be stored in a memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal.
  • the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.
  • the functional blocks described in the drawings and/or one or more combinations of functional blocks it can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component or any appropriate combination thereof for performing the functions described in the present application.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • it can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.
  • An IAB node integration method applied to the IAB node, the IAB node includes an MT (mobile terminal) and a DU (distributed unit), wherein the method comprises:
  • the DU of the IAB node is configured by OAM or the MT of the IAB node is configured by RRC to terminate the CU of the IAB host.
  • F1 terminates the base station identifier of the CU of the IAB host;
  • the DU of the IAB node performs F1 establishment with the CU of the F1 termination IAB host according to the base station identifier.
  • the CU of the RRC-terminated IAB host is different from the CU of the F1-terminated IAB host.
  • the DU of the IAB node discovers the TNL address of the CU of the F1-terminating IAB host through the base station identifier;
  • the DU of the IAB node performs F1 establishment with the CU of the F1 termination IAB host according to the base station identifier and the TNL address.
  • the DU of the IAB node is also configured by the OAM with the TNL address of the CU of the F1-terminating IAB host;
  • the DU of the IAB node performs F1 establishment with the CU of the F1 termination IAB host according to the base station identifier and the TNL address.
  • the OAM is configured with multiple base station identifiers.
  • the DU of the IAB node selects a base station identifier from the multiple base station identifiers according to a predetermined strategy, and performs F1 establishment.
  • the OAM further configures the priorities of the multiple base station identifiers
  • the DU of the IAB node selects a base station identifier with the highest priority among the multiple base station identifiers to perform F1 establishment.
  • the DU of the IAB node initiates a TNL establishment and F1 establishment process to the CU of the F1 termination IAB host using the IP address allocated to the IAB node by the CU of the RRC termination IAB host.
  • the BAP address of the IAB node is included;
  • the CU of the F1 terminating IAB host After receiving the F1 establishment request message, the CU of the F1 terminating IAB host saves the BAP address for the IAB node.
  • the number of IP addresses allocated by the CU of the RRC terminating IAB host to the IAB node is one or more, and the IP address is anchored at the DU of the RRC terminating IAB host.
  • the MT of the IAB node receives first information sent by the CU of the RRC termination IAB host, where the first information includes identification information of the IAB node and/or identification information of the RRC termination IAB host;
  • the DU of the IAB node sends second information related to the first information to the F1 terminating IAB host.
  • the identification information of the IAB node is the UE XnAP identification generated by the RRC termination IAB host for the IAB node;
  • the identification information of the RRC termination IAB host is the base station identification information of the CU of the RRC termination IAB host.
  • the first information includes identification information of the IAB node and identification information of the RRC termination IAB host, and the second information is the same as the first information; or,
  • the first information includes identification information of the IAB node; the second information includes a serving cell identifier NCGI of the MT of the IAB node and identification information of the IAB node.
  • the first information is explicitly included in the RRC reconfiguration message or is included in a container of the RRC reconfiguration message.
  • the RRC reconfiguration message includes a first IE, and the first IE includes the first information; or,
  • the bap-Config IE of the RRC reconfiguration message includes a second IE or a first field, and the second IE or the first field includes the first information.
  • the second information is explicitly included in the F1AP message or included in a container of the F1AP message.
  • the F1AP message is an F1 establishment request message.
  • the F1AP message includes a third IE, and the third IE includes the second information.
  • the MT of the IAB node sends a first RRC message to the CU of the RRC termination IAB host, where the first RRC message includes identification information of the F1 termination IAB host, so that the RRC termination IAB host sends the identification information of the IAB node to the F1 termination IAB host.
  • the first RRC message is a UEAssistanceInformation message
  • the UEAssistanceInformation message includes a fourth IE, and the fourth IE includes identification information of the F1 termination IAB host.
  • the MT of the IAB node initiates a UE assistance information reporting process after the DU of the IAB node and the F1 of the F1 termination IAB host are established;
  • the IAB node has the capability of providing identification information of the F1 terminating IAB host, the IAB node is configured with capability reporting, and the IAB node is in an RRC connected state.
  • the CU of the RRC termination IAB host sends a first Xn message to the F1 termination IAB host, where the first Xn message includes the UE XnAP identifier generated by the RRC termination IAB host for the IAB node and/or the BAP address of the IAB node.
  • the CU of the RRC termination IAB host receives a second Xn message sent by the F1 termination IAB host, where the second Xn message includes confirmation information.
  • the MT of the IAB node sends an RRC setup completion message to the RRC termination IAB host, where the RRC setup completion message includes third information, where the third information indicates the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.
  • the MT of the IAB node receives a broadcast message sent by the RRC termination IAB host, where the broadcast message indicates a cell supporting mobile IAB;
  • the IAB node performs cell selection according to the broadcast message.
  • An IAB node integration method applied to an RRC termination IAB host, wherein the RRC termination IAB host includes a CU and a DU, wherein the method comprises:
  • the RRC termination IAB host sends first information to the MT of the IAB node, wherein the first information includes identification information of the IAB node and/or identification information of the RRC termination IAB host, so that the DU of the IAB node sends second information related to the first information to the F1 termination IAB host.
  • the identification information of the IAB node is the UE XnAP identification generated by the RRC termination IAB host for the IAB node;
  • the identification information of the RRC termination IAB host is the base station identification information of the CU of the RRC termination IAB host.
  • the first information includes identification information of the IAB node and identification information of the RRC termination IAB host, and the second information is the same as the first information; or,
  • the first information includes identification information of the IAB node; the second information includes a serving cell identifier NCGI of the MT of the IAB node and identification information of the IAB node.
  • the first information is explicitly included in the RRC reconfiguration message or is included in a container of the RRC reconfiguration message.
  • the RRC reconfiguration message includes a first IE, and the first IE includes the first information; or,
  • the bap-Config IE of the RRC reconfiguration message includes a second IE or a first field, wherein the second IE Or the first field contains the first information.
  • An IAB node integration method applied to an RRC termination IAB host, wherein the RRC termination IAB host includes a CU and a DU, wherein the method further includes:
  • the CU of the RRC termination IAB host receives a first RRC message sent by the MT of the IAB node, where the first RRC message includes identification information of the F1 termination IAB host;
  • the RRC termination IAB host sends the identification information of the IAB node to the F1 termination IAB host according to the first RRC message.
  • the first RRC message is a UEAssistanceInformation message
  • the UEAssistanceInformation message includes a fourth IE, and the fourth IE includes identification information of the F1 termination IAB host.
  • the CU of the RRC-terminated IAB host is different from the CU of the F1-terminated IAB host.
  • the CU of the RRC terminating IAB host allocates one or more IP addresses to the IAB node, so that the IAB node uses the IP addresses to initiate TNL establishment and F1 establishment processes to the CU of the F1 terminating IAB host.
  • the IP address is anchored at the DU of the RRC-terminating IAB host.
  • the RRC termination IAB host receives an RRC establishment completion message sent by the MT of the IAB node, wherein the RRC establishment completion message includes third information, and the third information indicates a mobile IAB of the IAB node. ability;
  • the RRC termination IAB host selects an AMF supporting mobile IAB according to the third information.
  • the RRC terminated IAB host sends a broadcast message, wherein the broadcast message indicates cells supporting mobile IAB, so that the IAB node selects a cell according to the broadcast message after receiving the broadcast message.
  • An IAB node integration method applied to an F1 termination IAB host, wherein the F1 termination IAB host includes a CU and a DU, wherein the method comprises:
  • the F1 IAB termination host receives second information sent by the DU of the IAB node, where the second information is related to the first information, and the first information includes identification information of the IAB node and/or identification information of the RRC IAB termination host.
  • the identification information of the IAB node is the UE XnAP identification generated by the RRC termination IAB host for the IAB node;
  • the identification information of the RRC termination IAB host is the base station identification information of the CU of the RRC termination IAB host.
  • the first information includes identification information of the IAB node and identification information of the RRC termination IAB host, and the second information is the same as the first information; or,
  • the first information includes identification information of the IAB node; the second information includes a serving cell identifier NCGI of the MT of the IAB node and identification information of the IAB node.
  • the second information is explicitly included in the F1AP message or included in a container of the F1AP message.
  • the F1AP message is an F1 establishment request message.
  • the F1AP message includes a third IE, and the third IE includes the second information.
  • the CU of the F1 terminating IAB host receives the F1 establishment request message sent by the DU of the IAB node.
  • the establishment request message includes the BAP address of the IAB node;
  • the F1 terminating IAB host stores the BAP address for the IAB node.
  • An IAB node integration method applied to an RRC termination IAB host, the RRC termination IAB host includes a CU (central unit) and a DU (distributed unit), wherein the method comprises:
  • the CU of the RRC-terminated IAB host determines the base station identifier of the CU of the F1-terminated IAB host for the IAB node;
  • the CU of the RRC terminating IAB host sends the base station identifier of the CU of the F1 terminating IAB host to the MT of the IAB node, so that the DU of the IAB node performs F1 establishment with the CU of the F1 terminating IAB host according to the base station identifier.
  • the CU of the RRC termination IAB host is configured with the base station identifier of the F1 termination IAB host by OAM; or,
  • the CU of the RRC IAB termination host selects the F1 IAB termination host according to the information obtained based on the ANR function, thereby obtaining the base station identifier of the F1 IAB termination host.
  • the OAM is configured with multiple base station identifiers.
  • the CU of the RRC termination IAB host selects a base station identifier from the multiple base station identifiers according to a predetermined policy.
  • the OAM further configures the priorities of the multiple base station identifiers
  • the CU of the RRC termination IAB host selects a base station identifier with the highest priority among the multiple base station identifiers.
  • the CU of the RRC terminated IAB host sends the base station identifier of the F1 terminated IAB host to the MT of the IAB node through an RRC reconfiguration message.
  • the DU of the IAB node performs F1 establishment with the CU of the F1 terminating IAB host according to the base station identifier and the TNL address of the CU of the F1 terminating IAB host discovered through the base station identifier.
  • the CU of the RRC-terminating IAB host also sends the TNL address of the CU of the F1-terminating IAB host to the MT of the IAB node through an RRC reconfiguration message;
  • the DU of the IAB node performs F1 establishment with the CU of the F1 termination IAB host according to the base station identifier and the TNL address.
  • the RRC reconfiguration message includes a fifth IE, and the fifth IE includes a base station identifier of the F1 termination IAB host; or
  • the bap-Config IE of the RRC reconfiguration message includes a sixth IE or a second field, and the sixth IE or the second field includes the base station identifier.
  • the CU of the RRC terminated IAB host sends first information to the MT of the IAB node, wherein the first information includes identification information of the IAB node and/or identification information of the RRC terminated IAB host; so that the DU of the IAB node sends second information related to the first information to the F1 terminated IAB host.
  • the identification information of the IAB node is the UE XnAP identification generated by the RRC termination IAB host for the IAB node;
  • the identification information of the RRC termination IAB host is the base station identification information of the CU of the RRC termination IAB host.
  • the first information includes identification information of the IAB node and identification information of the RRC termination IAB host, and the second information is the same as the first information; or,
  • the first information includes identification information of the IAB node; the second information includes a serving cell identifier NCGI of the MT of the IAB node and identification information of the IAB node.
  • the first information is explicitly included in the RRC reconfiguration message or is included in a container of the RRC reconfiguration message.
  • the RRC reconfiguration message includes a first IE, and the first IE includes the first information; or,
  • the bap-Config IE of the RRC reconfiguration message includes a second IE or a first field, wherein the second The IE or the first field contains the first information.
  • the second information is explicitly included in the F1AP message or included in a container of the F1AP message.
  • the F1AP message is an F1 establishment request message.
  • the F1AP message includes a third IE, and the third IE includes the second information.
  • the CU of the RRC termination IAB host sends a first Xn message to the F1 termination IAB host, where the first Xn message includes the UE XnAP identifier generated by the RRC termination IAB host for the IAB node and/or the BAP address of the IAB node.
  • the CU of the RRC termination IAB host receives a second Xn message sent by the F1 termination IAB host, where the second Xn message includes confirmation information.
  • the CU of the RRC-terminating IAB host allocates one or more IP addresses to the IAB node, and the IP addresses are anchored at the DU of the RRC-terminating IAB host.
  • the RRC termination IAB host receives an RRC establishment completion message sent by the MT of the IAB node, where the RRC establishment completion message includes third information, and the third information indicates a mobile IAB capability of the IAB node;
  • the RRC termination IAB host selects an AMF supporting mobile IAB according to the third information.
  • the DU of the RRC-terminated IAB host sends a broadcast message, where the broadcast message indicates cells supporting mobile IAB, so that the IAB node performs cell selection according to the broadcast message.
  • An IAB node integration method applied to an F1 termination IAB host, wherein the F1 termination IAB host includes a CU (central unit) and a DU (distributed unit), wherein the method comprises:
  • the F1 IAB termination host receives the first Xn message sent by the CU of the RRC IAB termination host,
  • the first Xn message includes the UE XnAP identifier generated by the RRC termination IAB host for the IAB node and/or the BAP address of the IAB node.
  • the F1 terminated IAB host sends a second Xn message to the CU of the RRC terminated IAB host, where the second Xn message includes confirmation information.
  • the MT of the IAB node sends an RRC establishment completion message to the RRC termination IAB host, where the RRC establishment completion message includes third information, where the third information indicates the mobile IAB capability of the IAB node, so that the RRC termination IAB host selects an AMF that supports mobile IAB.
  • the MT of the IAB node receives a broadcast message sent by the RRC termination IAB host, where the broadcast message indicates a cell supporting mobile IAB;
  • the MT of the IAB node performs cell selection according to the broadcast message.
  • the broadcast message is a SIB message.
  • An IAB node comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 1 to 24 and 61-63.
  • An IAB-donor node comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 25 to 60.
  • An IAB communication system comprising an IAB node and an IAB-donor node, wherein the IAB node is configured to execute the method described in any one of Notes 1 to 24 and 61 to 63, and the IAB-donor node is configured to execute the method described in any one of Notes 25 to 60.

Landscapes

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

Abstract

本申请实施例提供了一种IAB(接入回传一体化)节点的集成方法和装置，所述方法包括：IAB节点的DU被OAM配置或IAB节点的MT被RRC终结IAB宿主的CU配置F1终结IAB宿主的CU的基站标识；所述IAB节点的DU根据所述基站标识与所述F1终结IAB宿主的CU进行F1建立。由此，解决了IAB节点的集成问题，使得IAB-MT和并置的IAB-DU能够集成到不同的donor-CU上，提高了网络配置的灵活性。

Description

接入回传一体化节点的集成方法和装置 技术领域
本申请涉及通信领域。
背景技术
接入回传一体化(IAB：integrated access and backhaul)在下一代无线接入网络(NG-RAN：next generation radio access network)中实现了无线中继的功能。这个中继节点称为IAB节点(IAB-node)，它通过5G NR(new radio，新无线)同时支持接入和回传(BH：backhaul)。所有IAB节点通过一跳或者多跳来连接到一个IAB宿主(IAB-donor)节点。这些多跳连接形成了一个以IAB宿主节点为根节点的有向无环图(DAG：Directed Acyclic Graph)拓扑结构。IAB宿主节点负责执行IAB网络拓扑中集中式的资源管理、拓扑管理和路由管理。
IAB节点支持gNB-DU(distributed unit，分布式单元)的功能，称之为IAB-DU，可以服务普通UE(user equipment，用户设备)和IAB子节点。IAB节点同时支持UE的部分功能，可称之为IAB-MT(mobile termination，移动终端)。IAB-MT可支持如UE物理层、AS(access stratum，接入层)、RRC(radio resource control，无线资源控制)和NAS(non-access stratum，非接入层)功能，可以连接到IAB父节点。在网络侧的终结节点称之为IAB-donor，其通过回传或接入链路为IAB-MT或UE提供网络接入。IAB-donor又进一步分为IAB-donor-CU(central unit，中央单元)和IAB-donor-DU。IAB-DU和IAB-donor-CU之间通过F1接口连接。在独立组网场景下，gNB与IAB-donor-CU之间通过Xn接口连接。
为了支持数据包的多跳路由转发，IAB引入了BAP(Backhaul Adaptation Protocol，回传适配协议)子层。BAP子层位于RLC(radio link control，无线链路控制)子层之上IP(Internet Protocol，网络协议)层之下，支持数据包目的节点及路径的选择、数据包的路由转发、承载映射、流控反馈、回传链路失败通知等功能。
在多跳场景下，为了实现数据包的中继转发，IAB节点需要确定数据包到达的目的节点，然后根据路由表确定到达目的节点对应的下一跳节点并发送该数据包。在上述场景下，由IAB-donor-CU(简称为donor-CU，或CU，或gNB-CU)通过F1AP(F1 应用协议)信令为IAB节点配置从IAB节点发起的上行传输的每个F1-U(F1用户面)隧道(Tunnel)、每个非UE关联的(Non-UE associated)F1AP消息、每个UE关联的(UE-associated)F1AP消息、每个非F1数据(Non-F1Traffic)到BAP路由标识的映射。IAB节点根据路由标识映射信息确定从IAB节点发起的不同类型的上行IP包对应的BAP路由标识，并为这些上行IP包封装包含BAP路由标识信息的BAP子头。IAB-donor-CU通过F1AP信令为IAB-donor-DU(简称为donor-DU)配置不同类型的下行数据包到BAP路由标识的映射。IAB-donor-DU根据路由标识映射信息确定收到的下行IP包对应的BAP路由标识，并为这些下行IP包封装包含BAP路由标识信息的BAP子头。
BAP路由标识包括目的BAP地址和从IAB节点到IAB-donor-DU之间的路径标识(path identity)。BAP地址在BAP报头中也被称为DESTINATION(目的地)。每个IAB节点及IAB-donor-DU都被配置了BAP地址。
IAB节点的集成(integration)过程也叫启动过程，是指IAB-MT接入网络并获得IAB相关配置信息，启动DU部分功能为UE提供服务的过程。以独立组网下的IAB节点的集成过程为例，可以分为三个阶段。
第一阶段，IAB-MT接入网络。在该阶段中，IAB-MT作为普通UE连接至网络，这个过程基本重用普通的UE的初始接入过程。
第二阶段，BH RLC信道建立和路由更新。在该阶段，RRC可以配置用于非F1-U流量的一个缺省的BH RLC信道和一个缺省的BAP路由标识。IAB-donor-CU还可能在该阶段中为IAB-MT建立额外的BH RLC信道用于后续的数据传输。IAB-donor-CU对新集成的IAB节点、IAB-donor-DU、新集成的IAB节点的父节点，以及与IAB-donor-DU之间的所有中间IAB节点进行路由配置。另外，该阶段还包括新集成的IAB节点的IP地址分配过程。
第三阶段是IAB-DU启动。IAB-DU使用第二阶段中获得的IP地址发起与IAB-donor-CU的SCTP(Stream Control Transmission Protocol，流控制传输协议)连接建立和F1连接建立过程。之后该IAB节点可以开始为UE提供空口服务。
以上是简单的描述，具体参考现有技术。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申 请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
发明人发现，在现有的IAB节点集成过程中，IAB节点的MT和DU都终结到同一个donor-CU。这样不能达到移动IAB节点的灵活性，不能快速支持IAB节点的宿主间的拓扑适配。因此，如何支持IAB节点的MT和DU集成到不同的donor-CU上是业界的一个研究目标。
针对上述问题或者类似问题或者其他场景下的类似问题，本申请实施例提供了一种IAB节点的集成方法和装置。
根据本申请实施例的一方面，提供一种IAB节点的集成装置，配置于IAB节点，所述IAB节点包括MT(移动终端)和DU(分布式单元)，其中，
所述IAB节点的DU被OAM配置或所述IAB节点的MT被RRC终结IAB宿主的CU配置F1终结IAB宿主的CU的基站标识；
所述IAB节点的DU根据所述基站标识与所述F1终结IAB宿主的CU进行F1建立。
根据本申请实施例的另一方面，提供一种IAB节点的集成装置，配置于RRC终结IAB宿主，所述RRC终结IAB宿主包括CU和DU，其中，
所述RRC终结IAB宿主的CU向所述IAB节点的MT发送第一信息，所述第一信息包含所述IAB节点的标识信息和/或所述RRC终结IAB宿主的标识信息，以便所述IAB节点的DU将与所述第一信息相关的第二信息发送给所述F1终结IAB宿主。
根据本申请实施例的另一方面，提供一种IAB节点的集成装置，配置于RRC终结IAB宿主，所述RRC终结IAB宿主包括CU和DU，其中，
RRC终结IAB宿主的CU接收IAB节点的MT发送的第一RRC消息，该第一RRC消息包含上述F1终结IAB宿主的标识信息；RRC终结IAB宿主根据该第一RRC消息，将IAB节点的标识信息发送给F1终结IAB宿主。
根据本申请实施例的再一方面，提供一种IAB节点的集成装置，配置于F1终结IAB宿主，所述F1终结IAB宿主包括CU和DU，其中，
所述F1终结IAB宿主的CU接收IAB节点的DU发送的第二信息，所述第二信息与第一信息相关，所述第一信息包含所述IAB节点的标识信息和/或所述RRC终结 IAB宿主的标识信息。
根据本申请实施例的又一方面，提供一种IAB节点的集成装置，配置于RRC终结IAB宿主，所述RRC终结IAB宿主包括CU(中央单元)和DU(分布式单元)，其中，
所述RRC终结IAB宿主的CU为IAB节点确定F1终结IAB宿主的CU的基站标识；
所述RRC终结IAB宿主的CU将所述F1终结IAB宿主的CU的基站标识发送给所述IAB节点的MT，以便所述IAB节点的DU根据所述基站标识与所述F1终结IAB宿主的CU进行F1建立。
根据本申请实施例的又一方面，提供一种IAB节点的集成装置，配置于F1终结IAB宿主，所述F1终结IAB宿主包括CU(中央单元)和DU(分布式单元)，其中，
所述F1终结IAB宿主接收RRC终结IAB宿主的CU发送的第一Xn消息，所述第一Xn消息包含所述RRC终结IAB宿主为IAB节点生成的UE XnAP标识和/或所述IAB节点的BAP地址。
根据本申请实施例的再一方面，提供一种设置装置，配置于IAB节点，所述IAB节点包括MT和DU，其中，
所述MT向RRC终结IAB宿主发送RRC建立完成消息，所述RRC建立完成消息包括第三信息，所述第三信息指示了所述IAB节点的移动IAB能力，以便所述RRC终结IAB宿主选择一个支持移动IAB的AMF。
根据本申请实施例的又一方面，提供一种设置装置，配置于IAB节点，所述IAB节点包括MT和DU，其中，
所述MT接收RRC终结IAB宿主发送的广播消息，所述广播消息指示了支持移动IAB的小区；
所述MT根据所述广播消息进行小区选择。
本申请实施例的有益效果之一在于：根据本申请实施例，解决了IAB节点的集成问题，使得IAB-MT和并置的IAB-DU能够集成到不同的donor-CU上，提高了网络配置的灵活性。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在 所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部分，用于例示本申请的实施方式，并与文字描述一起来阐释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。在附图中：
图1是IAB网络拓扑结构的一个示例的示意图；
图2是本申请实施例的移动IAB节点的集成过程的一示意图；
图3是本申请第一方面的实施例的IAB节点的集成方法的一示意图；
图4是IAB节点集成过程中的IAB-DU设置的流程的一个示意图；
图5是IAB节点集成过程中的IAB-DU设置的流程的另一个示意图；
图6a和图6b是本申请第一方面的实施例的IAB节点的集成方法的另两个示例的示意图；
图7a和图7b是本申请第一方面的实施例的IAB节点的集成方法的又两个示例的示意图；
图8是本申请第二方面的实施例的IAB节点的集成方法的一示意图；
图9是IAB节点集成过程中的IAB-DU设置的流程的又一个示意图；
图10是本申请第二方面的实施例的IAB节点的集成方法的另一示意图；
图11a和图11b是本申请第二方面的实施例的IAB节点的集成方法的又两个示例的示意图；
图12是本申请实施例的设置方法的一示意图；
图13是本申请实施例的设置方法的另一示意图；
图14是本申请实施例的IAB节点的集成装置的一示意图；
图15是本申请实施例的IAB节点的集成装置的另一示意图；
图16是本申请实施例的IAB节点的集成装置的另一示意图；
图17是本申请实施例的IAB节点的集成装置的另一示意图；
图18是本申请实施例的IAB节点的集成装置的另一示意图；
图19是本申请实施例的设置装置的一示意图；
图20是本申请实施例的设置装置的另一示意图；
图21是本申请实施例的IAB节点的一示意图；
图22是本申请实施例的IAB-donor节点的一示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A， LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及未来的5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、收发节点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备，也可以称为“终端设备”(TE，Terminal Equipment)。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，还可以是IAB-MT，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type  Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
图1是IAB网络拓扑结构的一个示例的示意图，示出了一个IAB的MT和DU终结到不同的donor-CU的情况。
发明人发现，移动IAB(mobile IAB，mIAB)或者是移动中继在一个较大区域的移动性面临一个挑战，那就是当它在移动过程中，基于网络覆盖的需要和QoS支持的需要，IAB节点的F1终结宿主和非F1终结宿主可能会不同，也就是IAB的MT和DU终结到不同的IAB-donor-CU。
F1终结(F1-terminating)节点指对IAB节点的F1接口进行终结的donor-CU，比如图1所示的donor-CU2，在图1中，IAB-DU1通过F1连接终结到donor-CU2，则donor-CU2是IAB节点1的F1终结节点。F1-terminating donor-CU也可以叫做IAB-DU的donor-CU，因为IAB-DU由该CU配置。
非F1终结(Non-F1-terminating)节点指没有对IAB节点的F1接口进行终结的具有宿主功能的CU，比如图1所示的donor-CU1。因为非F1终结节点和IAB-MT有RRC连接所以非F1终结节点也可以叫做服务IAB-MT的宿主节点，非F1终结宿主CU也叫做IAB-MT的宿主CU，也可以叫做IAB节点的RRC-terminating donor-CU。
在图1中，IAB-MT1单连接到父节点IAB节点2，然后连接到donor-DU1，donor-CU1。IAB-DU1和donor-CU2进行F1连接，但是这个F1连接经过的路径是通过IAB节点2，donor-DU1最终到达donor-CU2的。
由于IAB节点1的RRC接口和F1接口终结到不同的donor-CU，所以IAB节点1为边界(boundary)IAB节点。
发明人发现，在现有的IAB节点集成过程中，IAB节点的MT和DU都终结到同一个donor-CU。这样不能达到移动IAB节点的灵活性，不能快速支持IAB节点的宿主间的拓扑适配。因此，需要定义如何支持IAB节点的MT和DU集成到不同的donor-CU上。也就是支持图1所示的网络集成场景，使边界IAB节点也能进行集成。然而，目前没有对IAB节点的MT和DU连接到不同donor-CU的集成过程进行定义。
在本申请实施例中，以5G多跳IAB网络部署为例，多个UE通过多跳的IAB节点连接到IAB-donor，最后接入5G网络。UE连接的IAB节点可以移动。
图2是本申请实施例的移动IAB节点的集成过程的一示意图，示出了通用的IAB 节点(图2中的IAB节点1)的网络集成的情况。如图2所示，IAB节点1的IAB-MT和IAB-DU集成到不同的IAB-donor。在图2中，IAB-donor 1是RRC终结IAB宿主(RRC-terminating IAB donor)，也就是MT连接的donor；IAB-donor 2是F1终结IAB宿主(F1-terminating IAB donor)，也就是DU连接的donor。
在图2中，IAB节点1的IAB-MT在第一阶段进行了网络接入。在该阶段中，IAB-MT作为普通UE连接至网络，这个过程基本重用普通的UE的初始接入过程。IAB-MT接入的宿主是donor-CU1。在第二阶段，donor-CU1对IAB-MT进行了RRC配置，包括BH RLC信道建立(establishment)等，donor-CU1还对IAB节点1到donor-DU1之间的IAB节点，比如IAB节点2进行路由更新(routing update)，用于支持IAB节点1到donor-DU1的BAP路由。在第三阶段的IAB-DU设置(setup)过程中，IAB节点1的IAB-DU向donor-CU2建立F1连接，也即进行F1建立。
下面结合附图对本申请的各种实施方式进行说明。这些实施方式只是示例性的，不是对本申请的限制。在下面的说明中，“如果…”、“在…的情况下”、“当…时”等说法含义相同，可以互换。
第一方面的实施例
本申请实施例提供一种IAB节点的集成方法，应用于图2所示的场景。
图3是本申请实施例的IAB节点的集成方法的一示意图，从IAB节点的一侧进行说明，该IAB节点例如为图2所示场景下的IAB节点1，包含了MT和DU，该MT也可以称为IAB-MT，该DU可以称为IAB-DU。如图3所示，该方法包括：
301：IAB节点的DU被OAM配置F1终结IAB宿主的CU的基站标识；
302：所述IAB节点的DU根据所述基站标识与所述F1终结IAB宿主的CU进行F1建立。
值得注意的是，以上附图3仅示意性地对本申请实施例进行了说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图3的记载。
在上述实施例中，基站标识可以是gNB ID，Global gNB ID，Global NG-RAN node ID等。
在上述实施例中，在图2的第三阶段的IAB-DU建立(setup)过程中，IAB节点1的DU需要向F1终结IAB宿主的CU进行F1建立，根据本申请实施例，通过OAM(Operation Administration and Maintenance，操作管理和维护)来对IAB-DU进行配置，配置的内容包括了F1终结IAB宿主的CU的基站标识，由此，IAB节点的DU可以根据该基站标识与F1终结IAB宿主的CU进行F1建立，解决了移动IAB节点的MT和DU集成到不同IAB-donor的问题，从而支持IAB节点的配置灵活性，并且支持IAB节点广泛区域的移动，能够为移动IAB节点服务的UE提供高质量的服务。
在本申请实施例中，RRC终结IAB宿主的CU和F1终结IAB宿主的CU不同，例如，如图2所示，RRC终结IAB宿主是IAB-donor 1，则RRC终结IAB宿主的CU是IAB-Donor-CU1，为了方便说明，也称为“CU1”或者“donor-CU1”；F1终结IAB宿主是IAB-donor 2，则F1终结IAB宿主的CU是IAB-donor-CU2，为了方便说明，也称为“CU2”或者“donor-CU2”。
在一些实施例中，在图2所示的第一阶段或第二阶段，donor-CU1通过RRC信令为IAB节点1分配一个或多个IP地址，这些IP地址锚定在IAB-donor-DU1，由此，IAB节点1可以根据该IP地址向F1终结IAB宿主的CU(donor-CU2)发起TNL建立以及F1建立过程。
在一些实施例中，IAB节点仅被配置了上述基站标识，则该IAB节点的DU还可以通过该基站标识发现F1终结宿主的CU(CU2)的TNL地址，并根据上述基站标识和该TNL地址与CU2进行F1建立。
在上述实施例中，如果没有给IAB-DU配置donor-CU2的TNL地址，IAB-DU可以使用和非IAB的gNB-DU使用的相同方法来通过基站标识发现donor-CU2的TNL地址，比如用Xn-C TNL地址发现过程，等等，具体可以参考相关技术。
在一些实施例中，IAB节点既被配置了上述基站标识，又被配置了F1终结宿主的CU(CU2)的TNL地址(也即IP地址)，则IAB节点的DU可以根据该基站标识和该TNL地址与F1终结IAB宿主的CU进行F1建立。
在一些实施例中，IAB节点被配置了多个基站标识，则IAB节点的DU可以根据预定策略从这多个基站标识中选择一个基站标识进行F1建立。
例如，OAM为IAB-DU配置多个CU的基站标识信息，比如包含在一个列表中，表明候选的donor-CU信息。IAB-DU可以自行进行选择其中的某个donor-CU(比如 IAB-donor-CU2)然后进行F1建立。
在一些实施例中，IAB节点还被配置了多个基站标识的优先级，则IAB节点的DU可以选择这多个基站标识中基站标识的优先级最高的基站标识进行F1建立。
例如，上述列表中还可以包含OAM配置的IAB-donor-CU的优先级信息，为IAB-DU进行进一步指示，有助于IAB-DU进行IAB-donor-CU的选择。比如先选择指示为高优先级的IAB-donor-CU，万一F1建立失败，可以选择另外的IAB-donor-CU进行F1建立。
在一些实施例中，IAB节点的DU使用RRC终结IAB宿主的CU(IAB-donor-CU1)为IAB节点分配的IP地址向F1终结IAB宿主的CU(IAB-donor-CU2)发起TNL建立以及F1建立过程。
在上述实施例中，在F1建立请求消息(F1 SETUP REQUEST)中，还可以包含IAB节点的BAP地址。由此，F1终结IAB宿主的CU(IAB-donor-CU2)在收到该F1建立请求消息后，为该IAB节点保存该BAP地址。
在上述实施例中，如果该BAP地址和IAB-donor-CU2的拓扑中的其他节点的BAP地址冲突，IAB-donor-CU2可以将该BAP地址作为IAB节点在IAB-donor-CU1拓扑中使用的BAP地址，IAB-donor-CU2还可以为该IAB节点分配在IAB-donor-CU2的拓扑中的BAP地址。
在上述实施例中，IAB-donor-CU2可以将分配的BAP地址通过F1 SETUP RESPONSE消息发送给IAB-DU。比如可以重用F1 SETUP RESPONSE消息中的BAP Address IE，表明是IAB-donor-CU2为IAB节点分配的BAP地址，本申请不限于此。
在上述实施例中，在IAB-donor-CU2和IAB-DU建立F1连接之后，IAB节点相当于属于两个CU(IAB-donor-CU1和IAB-donor-CU2)的拓扑，被两个CU配置。两个CU需要进行进一步信息交互，从而进行IAB传输迁移管理过程和/或IAB资源协调过程。这些过程在IAB-donor-CU1和IAB-donor-CU2之间的Xn接口进行交互。因为IAB-donor-CU2是IAB节点的F1终结IAB宿主CU，一般由F1终结IAB宿主CU发起这些IAB相关的Xn过程。因此，IAB-donor-CU2需要知道IAB-donor-CU1的基站标识以及IAB节点在IAB-donor-CU1的UE XnAP ID，也就是IAB-donor-CU1为IAB节点生成的NG-RAN node UE XnAP ID，也称为Non F1-terminating IAB-Donor UE XnAP ID。
在本申请实施例中，可以由IAB节点进行相关信息的传递，也可以由IAB-donor-CU1进行相关信息的传递，来使IAB-donor-CU2得到IAB-donor-CU1的基站信息以及IAB-donor-CU1为IAB节点生成的UE XnAP ID。
下面分别进行说明。
在一些实施例中，由IAB节点进行相关信息的传递。
在上述实施例中，IAB节点的MT接收RRC终结IAB宿主的CU(IAB-donor-CU1)发送的第一信息，该第一信息包含IAB节点的标识信息和/或RRC终结IAB宿主的标识信息；IAB节点的DU将与上述第一信息相关的第二信息发送给F1终结IAB宿主。
在上述实施例中，IAB节点的标识信息例如为RRC终结IAB宿主为IAB节点生成的UE XnAP标识；RRC终结IAB宿主的标识信息例如为RRC终结IAB宿主的CU的基站标识信息。这里，基站标识可以是gNB ID，Global gNB ID，Global NG-RAN node ID等。
在上述实施例中，IAB节点的DU可以在与(未来的)F1终结IAB宿主进行F1建立时，通过F1 SETUP REQUEST消息，将上述第二信息发送给F1终结IAB宿主。但本申请不限于此，IAB节点的DU也可以通过F1建立之后的其他F1AP信令来发送上述第二信息。IAB-donor-CU2收到该第二信息，可以得出该IAB节点的MT部分不属于IAB-donor-CU2的拓扑，也就是该IAB节点的MT终结到另外一个donor-CU上，该IAB节点是边界IAB节点。IAB-donor-CU2也可以通过判断收到的F1 SETUP REQUEST消息中IAB节点的BAP地址或者是使用的IP地址不是自己拓扑内的(也即不是IAB-donor-CU2分配的)地址来判断IAB节点的MT终结到另外一个donor-CU。
在上述实施例中，在一个例子中，第一信息包括IAB节点的标识信息和RRC终结IAB宿主的标识信息。在这个例子中，第二信息与第一信息相同，由此，IAB节点的DU直接将IAB节点的MT获取到的上述第一信息发送给F1终结IAB宿主即可。这里的“相同”是指内容相同，也即第一信息和第二信息所包含的信息相同。
在上述实施例中，在另一个例子中，第一信息包括IAB节点的标识信息而不包含RRC终结IAB宿主的标识信息。在这个例子中，第二信息包括IAB节点的MT的服务小区标识NCGI和IAB节点的标识信息。
在上述例子中，因为IAB-MT本身通过IAB-donor-CU1广播的系统信息中得到 小区标识信息(NCGI，NR Cell Global Identifier)，小区标识信息里隐含了基站标识，所以IAB-donor-CU1可以只发IAB节点的UE XnAP ID给IAB-MT，并置的IAB-DU将IAB-MT的服务小区标识NCGI和该UE XnAP ID发送给IAB-donor-CU2。由此，IAB-donor-CU2可以通过某种方法(比如基于OAM配置)确定基站标识的比特长度，然后从NCGI得到基站标识。
在上述实施例中，第一信息可以显式包含在RRC重配置消息中或者包含在RRC重配置消息的一个容器(container)中。例如，该RRC重配置消息中包含第一IE，该第一IE包含上述第一信息；再例如，该RRC重配置消息的bap-Config IE中包含第二IE或者第一字段，该第二IE或者第一字段包含上述第一信息。
在上述实施例中，第二信息可以显式包含在F1AP消息中或者包含在F1AP消息的一个容器(container)中。例如，该F1AP消息中包含第三IE，该第三IE包含上述第二信息。其中，该F1AP消息例如为F1建立请求消息，但本申请不限于此。
图4是IAB节点集成过程中的IAB-DU设置的流程的一个示意图，示出了基于OAM进行IAB-DU配置的情况。如图4所示，该流程包括：
401：IAB-donor-CU1向IAB-MT发送RRC重配置(RRCReconfiguration)消息；
402：IAB-MT向IAB-donor-CU1发送RRC重配置消息完成(RRCReconfigurationComplete)消息；
403：IAB-DU向IAB-donor-CU2发送第二信息；
404：5G核心网对IAB-donor-CU2进行相关配置；
405：IAB-donor-CU2向IAB-DU反馈F1建立响应消息，表明IAB-DU设置结束，IAB节点可以开始为UE提供空口服务；
406：IAB-donor-CU2向IAB-donor-CU1发送“IAB TRANSPORT MIGRATION MANAGEMENT REQUEST”；
407：IAB-donor-CU1向IAB-donor-CU2发送“IAB TRANSPORT MIGRATION MANAGEMENT RESPOSNE”。
上述401和402是IAB-donor-CU1为IAB-MT进行配置的过程。在操作401中，IAB-donor-CU1使用RRCReconfiguration消息进行上述第一信息的配置；
在上述401中，第一信息包含IAB节点的UE XnAP ID以及可选的IAB-donor-CU1的基站标识。该第一信息可以显式包含在RRC重配置消息中，也可以放在RRC重配 置消息中的一个容器(container)中，由IAB-DU直接将该容器放到F1建立请求消息中发送给IAB-donor-CU2，也就是IAB节点不对容器进行解码，直接透明传输。
例如，可以在RRCReconfiguration消息中定义新的IE(第一IE)来指示该第一信息，也可以在RRCReconfiguration消息中的bap-Config IE中定义新的子IE(第二IE)或者字段(第一字段)来指示该第一信息。
上述401和上述402可以发生在图2所示的第三阶段之前的任何阶段，例如从第一阶段到阶段2-2的任何时刻，本申请对此不做限制。
在上述403步骤之前，OAM为IAB-DU进行了配置，包括donor-CU2的基站标识等，用于IAB-DU向该donor-CU2进行F1建立。
在上述403中，IAB-DU可以使用F1 SETUP REQUEST消息发送上述第二信息。第二信息可以包含IAB-donor-CU1的相关标识信息和IAB节点在IAB-donor-CU1的UE XnAP ID(来自第一信息)。IAB-donor-CU1的相关标识信息可以是第一信息中的基站标识，也可以是服务小区的NCGI。该第二信息可以显式包含在F1AP消息中，也可以放在F1AP消息中的一个容器中。例如可以在F1 SETUP REQUEST消息中定义新的IE(第三IE)来指示该第二信息。
上述406和407是IAB-donor-CU2和IAB-donor-CU1之间的IAB相关Xn过程的示例，可以在IAB集成过程之后进行，比如IAB-donor-CU2发起的IAB Transport Migration Management过程。本申请不限于此。
根据上述实施例，IAB-donor-CU2能够从IAB节点获得IAB-donor-CU1的基站信息以及IAB-donor-CU1为IAB节点生成的UE XnAP ID。
在另一些实施例中，由IAB-donor-CU1进行相关信息的传递。
在上述实施例中，OAM为IAB-DU进行了配置。IAB节点的MT向RRC终结IAB宿主的CU(IAB-donor-CU1)发送第一RRC消息，该第一RRC消息包含OAM配置的F1终结IAB宿主的标识信息，以便RRC终结IAB宿主将上述IAB节点的标识信息发送给F1终结IAB宿主。
在上述实施例中，第一RRC消息例如为UEAssistanceInformation消息；该UEAssistanceInformation消息中包含第四IE，该第四IE包含F1终结IAB宿主的标识信息。
在上述实施例中，可选的，IAB节点的MT还可以在IAB节点的DU与F1终结 IAB宿主的F1建立完成之后发起UE辅助信息上报过程。其中，该IAB节点具有提供F1终结IAB宿主的标识信息的能力，并且，该IAB节点被配置了能力上报，并且，该IAB节点处于RRC连接态。也即，如果该IAB节点具有提供F1终结IAB宿主的标识信息的能力，并且，该IAB节点被配置了能力上报，则该IAB在处于RRC连接态时，可以在IAB-DU与CU2的F1建立完成之后发起上述UE辅助信息上报过程。
在上述实施例中，RRC终结IAB宿主的CU可以向F1终结IAB宿主发送第一Xn消息，该第一Xn消息包含RRC终结IAB宿主为IAB节点生成的UE XnAP标识和/或IAB节点的BAP地址。
在上述实施例中，F1终结IAB宿主还可以向RRC终结IAB宿主的CU反馈第二Xn消息，该第二Xn消息包含确认信息。
图5是IAB节点集成过程中的IAB-DU设置的流程的另一个示意图，示出了基于OAM进行IAB-DU配置的情况。如图5所示，该流程包括：
501：IAB-DU与IAB-donor-CU2进行F1建立；
502：5G核心网对IAB-donor-CU2进行相关配置；
503：IAB-donor-CU2向IAB-DU回复F1建立响应；
504：IAB-MT向IAB-donor-CU1发送RRC消息1，在RRC消息1中包含有IAB-donor-CU2的基站标识；
505：IAB-donor-CU1向IAB-donor-CU2发送XnAP消息1，在该XnAP消息1中包含有UE XnAP ID和/或IAB节点的BAP地址；
506：IAB-donor-CU2向IAB-donor-CU1发送XnAP消息2，在该XnAP消息2中包含有确认信息；
507：IAB-donor-CU2向IAB-donor-CU1发送“IAB TRANSPORT MIGRATION MANAGEMENT REQUEST”；
508：IAB-donor-CU1向IAB-donor-CU2发送“IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE”。
上述501～503是IAB-DU到IAB-donor-CU2的常规F1建立过程，具体可以参考相关技术。
在上述504中，由于IAB-donor-CU2的信息是OAM为IAB节点配置的，可以由IAB节点告知IAB-donor-CU1关于IAB-donor-CU2的标识信息，从而 IAB-donor-CU1可以将IAB标识信息发送给IAB-donor-CU2。因此，在504中，IAB节点可以通过上行(UE到网络侧)RRC消息通知IAB-donor-CU1。该RRC消息为第一RRC消息，包含IAB-donor-CU2的基站标识，也就是IAB节点的F1-terminating宿主gNB ID，或者是IAB-MT并置的IAB-DU的CU的gNB ID。
其中，第一RRC消息可以重用UEAssistanceInformation消息，例如在UEAssistanceInformation中增加新的IE(第四IE)，用于包含IAB-donor-CU2的基站标识。
此外，在504中，还可以在RRC层关于UE辅助信息的初始化部分进行增强，例如：一个具有提供F1终结宿主节点信息能力的UE(IAB-MT)如果被配置了需要上报的话，在连接态(RRC_CONNECTED)可以在并置的IAB-DU的F1建立完成之后发起UE辅助信息上报过程。
上述505和506是RAN节点间的XnAP过程，用于IAB-donor-CU1将IAB标识信息发送给IAB-donor-CU2。
在505和506中，可以定义一个新的XnAP过程，例如，可以定义一个UE关联(UE-associated)的class 1IAB过程，该过程由第一Xn消息和第二Xn消息组成。该过程由non-F1-terminating IAB-donor-CU发起。第一Xn消息中包含了IAB-donor-CU1生成的IAB-MT的UE XnAP ID，还可以包含IAB节点的BAP地址，用于IAB-donor-CU2识别该IAB节点。第二Xn消息是IAB-donor-CU2的确认消息。
此外，上述第二Xn消息是可选的，例如，如果是定义class 2的XnAP过程，第二Xn消息可以省略。
此外，上述505和506还可以重用NG-RAN node Configuration Update过程。将IAB标识信息(UE XnAP ID，IAB节点的BAP地址)作为新的IE包含在NG-RAN NODE CONFIGURATION UPDATE消息中。
上述507和508是IAB-donor-CU2和IAB-donor-CU1之间的IAB相关Xn过程的示例，可以在IAB节点的集成过程之后进行，比如IAB-donor-CU2发起的IAB Transport Migration Management过程。本申请不限于此。
根据上述实施例，IAB-donor-CU2能够从IAB-donor-CU1获得IAB-donor-CU1的基站信息以及IAB-donor-CU1为IAB节点生成的UE XnAP ID。
在一些实施例中，IAB节点的MT可以向RRC终结IAB宿主发送RRC建立完 成消息，该RRC建立完成消息包括第三信息，该第三信息指示了IAB节点的移动IAB能力，以便RRC终结IAB宿主选择一个支持移动IAB的AMF。
在上述实施例中，针对图2所示的第一阶段，可以在IAB-MT的设置过程中，IAB-MT通过对IAB-donor-CU1执行RRC连接建立过程，并且向网络进行认证。为了指示自己的移动IAB能力，IAB-MT可以在RRCSetupComplete消息(RRC连接建立完成消息，也叫消息5)中包含了移动IAB节点的指示，用于IAB-donor选择一个支持移动IAB的AMF(Access and Mobility Management Function，接入和移动性管理功能)。
在一些实施例中，IAB节点的MT可以接收RRC终结IAB宿主发送的广播消息，该广播消息指示了支持移动IAB的小区；该IAB节点可以根据该广播消息进行小区选择。具体来说，该广播消息由IAB宿主控制的donor-DU或者IAB-DU发出。
在上述实施例中，针对图2所示的第一阶段，可以在移动IAB-MT的小区选择过程中，选择广播了“支持移动IAB”的小区，也就是选择该小区作为父节点小区。关于支持移动IAB指示的广播消息可以由基站的SIB1(System Information Block 1)消息实现。本申请不限于此。
图6a是本申请实施例的IAB节点的集成方法的另一示意图，图6b是本申请实施例的IAB节点的集成方法的又一示意图，这两个示例都从RRC终结IAB宿主的一侧进行说明，该RRC终结IAB宿主例如为图2所示的IAB-donor 1，包括CU(IAB-donor-CU1)和DU(IAB-donor-DU1)，其中与前面的实施例相同的内容不再重复说明。
如图6a所示，在一个示例中，该方法包括：
601a：RRC终结IAB宿主向IAB节点的MT发送第一信息(步骤401)，所述第一信息包含所述IAB节点的标识信息和/或所述RRC终结IAB宿主的标识信息，以便所述IAB节点的DU将与所述第一信息相关的第二信息发送给F1终结IAB宿主(步骤403)。
在一些实施例中，IAB节点的标识信息可以是RRC终结IAB宿主为IAB节点生成的UE XnAP标识；RRC终结IAB宿主的标识信息可以是RRC终结IAB宿主的CU的基站标识信息。
在上述实施例中，在一个例子中，第一信息包括IAB节点的标识信息和RRC终 结IAB宿主的标识信息，第二信息与第一信息相同；在另一个例子中，第一信息包括IAB节点的标识信息；第二信息包括所述IAB节点的MT的服务小区标识NCGI和所述IAB节点的标识信息。
在上述实施例中，第一信息可以显式包含在RRC重配置消息中或者包含在该RRC重配置消息的一个容器(container)中。
在上述实施例中，在一个例子中，该RRC重配置消息中包含第一IE，该第一IE包含上述第一信息；在另一个例子中，该RRC重配置消息的bap-Config IE中包含第二IE或者第一字段，该第二IE或者第一字段包含上述第一信息。
如图6b所示，在另一个示例中，该方法包括：
601b：RRC终结IAB宿主的CU接收IAB节点的MT发送的第一RRC消息(步骤504)，该第一RRC消息包含上述F1终结IAB宿主的标识信息；RRC终结IAB宿主根据该第一RRC消息，将IAB节点的标识信息发送给F1终结IAB宿主。
在一些实施例中，第一RRC消息可以是UEAssistanceInformation消息；例如，该UEAssistanceInformation消息中包含第四IE，该第四IE包含上述F1终结IAB宿主的标识信息。
在一些实施例中，RRC终结IAB宿主的CU向所述F1终结IAB宿主发送第一Xn消息(步骤505)，该第一Xn消息包含RRC终结IAB宿主为IAB节点生成的UE XnAP标识和/或IAB节点的BAP地址。
在一些实施例中，可选的，RRC终结IAB宿主的CU还可以接收F1终结IAB宿主发送的第二Xn消息(步骤506)，该第二Xn消息包含确认信息。
在上述两个示例中，上述RRC终结IAB宿主的CU(IAB-donor-CU1)和上述F1终结IAB宿主的CU(IAB-donor-CU2)不同。
在上述两个示例中，RRC终结IAB宿主的CU为IAB节点分配一个或多个IP地址，以便该IAB节点使用该IP地址向F1终结IAB宿主的CU发起TNL建立以及F1建立过程。其中，该IP地址可以锚定在RRC终结IAB宿主的DU。
在上述两个示例中，在一些实施方式中，RRC终结IAB宿主还可以接收IAB节点的MT发送的RRC建立完成消息，该RRC建立完成消息包括第三信息，所述第三信息指示了IAB节点的移动IAB能力；该RRC终结IAB宿主根据该第三信息选择支持移动IAB的AMF。
在上述两个示例中，在一些实施方式中，RRC终结IAB宿主还可以发送广播消息，该广播消息指示了支持移动IAB的小区；由此，IAB节点在接收了该广播消息后，可以根据该广播消息进行小区选择。
图7a是本申请实施例的IAB节点的集成方法的又一示意图，图7b是本申请实施例的IAB节点的集成方法的又一示意图，这两个示例都从F1终结IAB宿主的一侧进行说明，该F1终结IAB宿主例如为图2所示的IAB-donor 2，包括CU(IAB-donor-CU2)和DU(IAB-donor-DU2)，其中，图7a的方法对应图6a的方法，图7b的方法对应图6b的方法，与前面的实施例相同的内容不再重复说明。
如图7a所示，在一个示例中，该方法包括：
701a：F1终结IAB宿主接收IAB节点的DU发送的第二信息，所述第二信息与第一信息相关，所述第一信息包含所述IAB节点的标识信息和/或所述RRC终结IAB宿主的标识信息。
在一些实施例中，IAB节点的标识信息为RRC终结IAB宿主为IAB节点生成的UE XnAP标识；RRC终结IAB宿主的标识信息为RRC终结IAB宿主的CU的基站标识信息。
在一些实施例中，在一个例子中，第一信息包括IAB节点的标识信息和RRC终结IAB宿主的标识信息，第二信息与所述第一信息相同；在另一个例子中，第一信息包括IAB节点的标识信息；第二信息包括所述IAB节点的MT的服务小区标识NCGI和所述IAB节点的标识信息。
在一些实施例中，第二信息显式包含在F1AP消息中或者包含在F1AP消息的一个容器(container)中。该F1AP消息可以是F1建立请求消息。此外，该F1AP消息中可以包含第三IE，该第三IE包含上述第二信息。
在一些实施例中，F1终结IAB宿主的CU接收IAB节点的DU发送的F1建立请求消息，该F1建立请求消息包含该IAB节点的BAP地址；F1终结IAB宿主为该IAB节点保存该BAP地址。
如图7b所示，在另一个示例中，该方法包括：
701b：F1终结IAB宿主接收RRC终结IAB宿主的CU发送的第一Xn消息，该第一Xn消息包含RRC终结IAB宿主为IAB节点生成的UE XnAP标识和/或该IAB节点的BAP地址。
在一些实施例中，F1终结IAB宿主还可以向所述RRC终结IAB宿主的CU发送第二Xn消息，该第二Xn消息包含确认信息。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
根据本申请实施例的方法，解决了IAB节点的集成问题，使得IAB-MT和并置的IAB-DU能够集成到不同的donor-CU上，提高了网络配置的灵活性。
第二方面的实施例
本申请实施例提供一种IAB节点的集成方法，应用于图2所示的场景。与第一方面的实施例不同的是，在本申请实施例中，由IAB-donor-CU1来指定IAB节点的F1-terminating donor-CU(也即IAB-donor-CU2)。也即，IAB-donor-CU2的上述相关信息不是由OAM配置给IAB-DU，而是由RRC终结IAB宿主的CU配置给IAB-MT。
图8是本申请实施例的IAB节点的集成方法的一示意图，从RRC终结IAB宿主的一侧进行说明，该RRC终结IAB宿主例如为图2所示的IAB-donor 1，包括CU(IAB-donor-CU1)和DU(IAB-donor-DU1)，其中与第一方面的实施例相同的内容不再重复说明。如图8所示，该方法包括：
801：RRC终结IAB宿主的CU为IAB节点确定F1终结IAB宿主的CU的基站标识；
802：所述RRC终结IAB宿主的CU将所述F1终结IAB宿主的CU的基站标识发送给所述IAB节点的MT，以便所述IAB节点的DU根据所述基站标识与所述F1终结IAB宿主的CU进行F1建立。
值得注意的是，以上附图8仅示意性地对本申请实施例进行了说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图8的记载。
在一些实施例中，RRC终结IAB宿主的CU被OAM配置上述F1终结IAB宿主的基站标识，由此得到F1终结IAB宿主的CU的基站标识。
例如，OAM配置多个IAB-donor-CU的基站标识，RRC终结IAB宿主的CU根 据预定策略从这多个基站标识中选择一个基站标识。
再例如，OAM配置多个IAB-donor-CU的基站标识以及各个基站标识的优先级，RRC终结IAB宿主的CU选择这多个基站标识中，基站标识的优先级最高的基站标识。
在另一些实施例中，RRC终结IAB宿主的CU根据基于ANR(Automatic neighbor relations)功能得到信息(例如邻小区信息)来自己选择F1终结IAB宿主，从而得到F1终结IAB宿主的基站标识。
在一些实施例中，RRC终结IAB宿主的CU通过RRC重配置消息将所述F1终结IAB宿主的基站标识发送给IAB节点的MT。由此，IAB节点得到了F1终结IAB宿主的基站标识。
在上述实施例中，得到了F1终结IAB宿主的基站标识，IAB节点的DU可以根据该基站标识和通过该基站标识发现的F1终结IAB宿主的CU的TNL地址，与该F1终结IAB宿主的CU进行F1建立。具体可以参考第一方面的实施例。
在上述实施例中，可选的，RRC终结IAB宿主的CU还通过RRC重配置消息将F1终结IAB宿主的CU的TNL地址发送给IAB节点的MT。由此，IAB节点的DU根据该基站标识和该TNL地址与F1终结IAB宿主的CU进行F1建立。具体可以参考第一方面的实施例。
在上述实施例中，对RRC重配置消息携带上述基站标识的方式不做限制，例如，可以在该RRC重配置消息中增加新的IE(称为第五IE)或者是在该RRC重配置消息的bap-Config IE中定义新的子IE(称为第六IE)或者字段(称为第二字段)，来指示该F1终结IAB宿主的基站标识和TNL地址(可选)。例如，该第五IE包含上述F1终结IAB宿主的基站标识和TNL地址(可选)；再例如，该第六IE或者第二字段包含上述F1终结IAB宿主的基站标识和TNL地址(可选)。
在一些实施例中，RRC终结IAB宿主的CU为IAB节点分配一个或多个IP地址，并且，该IP地址锚定在RRC终结IAB宿主的DU。由此，IAB节点即可使用分配的IP地址向F1终结IAB宿主的CU发起TNL建立以及F1建立过程。具体可以参考第一方面的实施例。
在一些实施例中，RRC终结IAB宿主的CU(IAB-donor-CU1)还向IAB节点的MT发送第一信息，该第一信息包含IAB节点的标识信息和/或RRC终结IAB宿主的 标识信息；IAB节点的DU将与上述第一信息相关的第二信息发送给F1终结IAB宿主。
IAB节点的标识信息、RRC终结IAB宿主的标识信息、与第一信息相关的内容以及与第二信息相关的内容可以参考第一方面的实施例，此处不再赘述。
其中，第一信息可以通过RRC重配置消息发出。比如，可以和上述F1终结IAB宿主的基站标识一起通过RRC重配置消息发出。具体流程可以参考图4，不同的是，在步骤401中，RRC重配置消息除了包含第一信息，还可以包含F1终结IAB宿主的基站标识。
在一些实施例中，RRC终结IAB宿主的CU向F1终结IAB宿主发送第一Xn消息，该第一Xn消息包含RRC终结IAB宿主为IAB节点生成的UE XnAP标识和/或该IAB节点的BAP地址。具体可以参考第一方面的实施例，例如图5所示的操作505。
在上述实施例中，可选的，RRC终结IAB宿主的CU接收F1终结IAB宿主发送的第二Xn消息，该第二Xn消息包含确认信息。具体可以参考第一方面的实施例，例如图5所示的操作506。
图9是IAB节点集成过程中的IAB-DU设置的流程的又一个示意图，示出了由IAB-donor-CU1指定IAB-donor-CU2的情况。如图9所示，该流程包括：
901：IAB-donor-CU1向IAB-MT发送RRC重配置(RRCReconfiguration)消息，在该RRC重配置消息中，包含IAB-donor-CU2的基站标识和TNL地址(可选)；
902：IAB-MT向IAB-donor-CU1发送RRC重配置完成(RRCReconfigurationComplete)消息；
903：IAB-DU与IAB-donor-CU2进行F1建立；
904：5G核心网对IAB-donor-CU2进行相关配置；
905：IAB-donor-CU2向IAB-DU回复F1建立响应；
906：IAB-donor-CU1向IAB-donor-CU2发送XnAP消息1，在该XnAP消息1中包含有UE XnAP ID和/或IAB节点的BAP地址；
907：IAB-donor-CU2向IAB-donor-CU1发送XnAP消息2，在该XnAP消息2中包含有确认信息；
908：IAB-donor-CU2向IAB-donor-CU1发送“IAB TRANSPORT MIGRATION MANAGEMENT REQUEST”；
909：IAB-donor-CU1向IAB-donor-CU2发送“IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE”。
上述操作906～909与图5的操作505～508相同，具体可以参考第一方面的实施例。
在另一些实施例中，IAB-donor-CU1通过小区广播一个列表，包含一个或多个和IAB-donor-DU1有IP连接的支持mobile IAB的IAB-donor-CU的基站标识，IAB-MT在第一阶段进行接入时就通过接收广播消息来选择IAB-donor-CU2，选择的标准可以基于OAM配置，或者从OAM配置的IAB-donor-CU列表中和广播的IAB-donor-CU列表进行比对，来确定是否进行小区接入，是否需要进行小区重选。
在一些实施例中，与第一方面的实施例类似，RRC终结IAB宿主还可以接收IAB节点的MT发送的RRC建立完成消息，该RRC建立完成消息包括第三信息，该第三信息指示了IAB节点的移动IAB能力；由此，RRC终结IAB宿主可以根据该第三信息选择一个支持移动IAB的AMF。具体可以参考第一方面的实施例。
在一些实施例中，与第一方面的实施例类似，RRC终结IAB宿主的DU还可以发送广播消息，该广播消息指示了支持移动IAB的小区，以便IAB节点根据所述广播消息进行小区选择。具体可以参考第一方面的实施例。
图10是本申请实施例的IAB节点的集成方法的另一示意图，从IAB节点的一侧进行说明。其中与第一方面的实施例和前面实施例相同的内容不再重复说明。如图10所示，该方法包括：
1001：IAB节点的MT被RRC终结IAB宿主的CU配置F1终结IAB宿主的CU的基站标识；
1002：所述IAB节点的DU根据所述基站标识与所述F1终结IAB宿主的CU进行F1建立。
在上述实施例中，可选的，IAB节点的MT还被配置上述F1终结IAB宿主的CU的TNL地址。关于IAB节点的行为与第一方面的实施例中IAB节点的行为相同，此处省略说明。
在一些实施例中，IAB节点的MT还接收来自IAB-donor-CU1的第一信息，并据此向IAB-donor-CU2发送第二信息。具体已经在前面的实施例和第一方面的实施例中做了说明，此处不再赘述。
图11a是本申请实施例的IAB节点的集成方法的另一示意图，图11b是本申请实 施例的IAB节点的集成方法的另一示意图，这两个示例都从F1终结IAB宿主的一侧进行说明。其中与第一方面的实施例和前面实施例相同的内容不再重复说明。
如图11a所示，在一个示例中，该方法包括：
1101a：F1终结IAB宿主接收IAB节点的DU发送的第二信息，所述第二信息与第一信息相关，所述第一信息包含所述IAB节点的标识信息和/或所述RRC终结IAB宿主的标识信息。
上述步骤的实施方式与图7a的701a的实施方式相同，此处不再赘述。
如图11b所示，在另一个示例中，该方法包括：
1101b：F1终结IAB宿主接收RRC终结IAB宿主的CU发送的第一Xn消息，所述第一Xn消息包含所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识和/或所述IAB节点的BAP地址。
在一些实施例中，F1终结IAB宿主还向所述RRC终结IAB宿主的CU发送第二Xn消息，所述第二Xn消息包含确认信息。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
根据本申请实施例的方法，解决了IAB节点的集成问题，使得IAB-MT和并置的IAB-DU能够集成到不同的donor-CU上，提高了网络配置的灵活性。
第三方面的实施例
本申请实施例提供一种设置方法，应用于图2所示的场景，从IAB节点的一侧进行说明，该IAB节点例如为图2所示场景下的IAB节点1，包含了MT和DU，该MT也可以称为IAB-MT，该DU可以称为IAB-DU。
图12是本申请实施例的设置方法的一示意图，如图12所示，该方法包括：
1201：IAB节点的MT向RRC终结IAB宿主发送RRC建立完成消息，所述RRC建立完成消息包括第三信息，所述第三信息指示了所述IAB节点的移动IAB能力，以便所述RRC终结IAB宿主选择一个支持移动IAB的AMF。
在上述实施例中，针对图2所示的第一阶段，可以在IAB-MT的设置过程中，IAB-MT通过对IAB-donor-CU1执行RRC连接建立过程，并且向网络进行认证。为 了指示自己的移动IAB能力，IAB-MT可以在RRCSetupComplete消息(RRC建立完成消息，也叫消息5)中包含了移动IAB节点的指示，用于IAB-donor选择一个支持移动IAB的AMF(Access and Mobility Management Function，接入和移动性管理功能)。
图13是本申请实施例的设置方法的另一示意图，如图13所示，该方法包括：
1301：IAB节点的MT接收RRC终结IAB宿主发送的广播消息，所述广播消息指示了支持移动IAB的小区；
1302：所述IAB节点的MT根据所述广播消息进行小区选择。
在上述实施例中，广播消息例如为SIB消息，本申请不限于此。
在上述实施例中，针对图2所示的第一阶段，可以在移动IAB-MT的小区选择过程中，选择广播了“支持移动IAB”的小区，也就是选择该小区作为父节点小区。关于支持移动IAB指示的广播消息可以由基站的SIB(System Information Block)消息实现。本申请不限于此。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
根据本申请实施例的方法，解决了IAB节点的集成问题，使得IAB-MT和并置的IAB-DU能够集成到不同的donor-CU上，提高了网络配置的灵活性。
第四方面的实施例
本申请实施例提供一种IAB节点的集成装置。
图14是本申请实施例的IAB节点的集成装置的一示意图，该装置例如可以是IAB网络中的IAB节点，也可以是配置于该IAB节点中的某个或某些部件或者组件。该IAB节点对应图2中的IAB节点1，与第一方面的实施例相同的内容不再重复说明。
如图14所示，该装置包括IAB-MT(移动终端)1401和IAB-DU(分布式单元)1402，其中，所述IAB-DU 1402被OAM配置或所述IAB-MT 1401被RRC终结IAB宿主的CU配置F1终结IAB宿主的CU的基站标识；所述IAB-DU 1402根据所述基站标识与所述F1终结IAB宿主的CU进行F1建立。
在一些实施例中，所述RRC终结IAB宿主的CU和所述F1终结IAB宿主的CU 不同。
在一些实施例中，所述IAB-DU 1402通过所述基站标识发现所述F1终结IAB宿主的CU的TNL地址；所述IAB-DU 1402根据所述基站标识和所述TNL地址与所述F1终结IAB宿主的CU进行F1建立。
在一些实施例中，所述IAB-DU 1402还被所述OAM配置所述F1终结IAB宿主的CU的TNL地址；所述IAB-DU 1402根据所述基站标识和所述TNL地址与所述F1终结IAB宿主的CU进行F1建立。
在一些实施例中，所述OAM配置了多个基站标识，所述IAB-DU 1402根据预定策略从所述多个基站标识中选择一个基站标识，进行F1建立。
在上述实施例中，所述OAM还可以配置所述多个基站标识的优先级，所述IAB-DU 1402选择所述多个基站标识中，基站标识的优先级最高的基站标识，进行F1建立。
在一些实施例中，所述IAB-DU 1402使用所述RRC终结IAB宿主的CU为所述IAB节点分配的IP地址向所述F1终结IAB宿主的CU发起TNL建立以及F1建立过程。
在上述实施例中，在F1建立请求消息中，可以包含所述IAB节点的BAP地址；所述F1终结IAB宿主的CU在收到所述F1建立请求消息后，为该IAB节点保存所述BAP地址。
在上述实施例中，所述RRC终结IAB宿主的CU可以为所述IAB节点分配的IP地址的数量为一个或多个，并且，所述IP地址锚定在所述RRC终结IAB宿主的DU。
在一些实施例中，所述IAB-MT 1401接收所述RRC终结IAB宿主的CU发送的第一信息，所述第一信息包含所述IAB节点的标识信息和/或所述RRC终结IAB宿主的标识信息；所述IAB-DU 1402将与所述第一信息相关的第二信息发送给所述F1终结IAB宿主。
在上述实施例中，所述IAB节点的标识信息可以为所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识；所述RRC终结IAB宿主的标识信息可以为所述RRC终结IAB宿主的CU的基站标识信息。
在上述实施例中，所述第一信息可以包括所述IAB节点的标识信息和所述RRC终结IAB宿主的标识信息，所述第二信息与所述第一信息相同；或者，所述第一信 息可以包括所述IAB节点的标识信息；所述第二信息包括所述IAB节点的MT的服务小区标识NCGI和所述IAB节点的标识信息。
在上述实施例中，所述第一信息可以显式包含在RRC重配置消息中或者包含在所述RRC重配置消息的一个容器(container)中。
在上述实施例中，所述RRC重配置消息中可以包含第一IE，所述第一IE包含所述第一信息；或者，所述RRC重配置消息的bap-Config IE中可以包含第二IE或者第一字段，所述第二IE或者第一字段包含所述第一信息。
在上述实施例中，所述第二信息可以显式包含在F1AP消息中或者包含在所述F1AP消息的一个容器(container)中。
在上述实施例中，所述F1AP消息可以为F1建立请求消息。
在上述实施例中，所述F1AP消息中可以包含第三IE，所述第三IE包含所述第二信息。
在一些实施例中，所述IAB-MT 1401向所述RRC终结IAB宿主的CU发送第一RRC消息，所述第一RRC消息包含所述F1终结IAB宿主的标识信息，以便所述RRC终结IAB宿主将所述IAB节点的标识信息发送给所述F1终结IAB宿主。
在上述实施例中，所述第一RRC消息可以为UEAssistanceInformation消息；所述UEAssistanceInformation消息中可以包含第四IE，所述第四IE可以包含所述F1终结IAB宿主的标识信息。
在上述实施例中，所述IAB-MT 1401可以在所述IAB-DU 1402与所述F1终结IAB宿主的F1建立完成之后发起UE辅助信息上报过程；其中，所述IAB节点具有提供F1终结IAB宿主的标识信息的能力，并且，所述IAB节点被配置了能力上报，并且，所述IAB节点处于RRC连接态。
在上述实施例中，所述RRC终结IAB宿主的CU可以向所述F1终结IAB宿主发送第一Xn消息，所述第一Xn消息包含所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识和/或所述IAB节点的BAP地址。
在上述实施例中，所述RRC终结IAB宿主的CU可以接收所述F1终结IAB宿主发送的第二Xn消息，所述第二Xn消息包含确认信息。
在一些实施例中，所述IAB-MT 1401向所述RRC终结IAB宿主发送RRC建立完成消息，所述RRC建立完成消息包括第三信息，所述第三信息指示了所述IAB节 点的移动IAB能力，以便所述RRC终结IAB宿主选择一个支持移动IAB的AMF。
在一些实施例中，所述IAB-MT 1401接收所述RRC终结IAB宿主发送的广播消息，所述广播消息指示了支持移动IAB的小区；所述IAB-MT 1401根据所述广播消息进行小区选择。
图15是本申请实施例的IAB节点的集成装置的另一示意图，该装置例如可以是IAB网络中的IAB宿主，也可以是配置于该IAB宿主中的某个或某些部件或者组件。该IAB宿主对应图2中的RRC终结IAB宿主，也即IAB-donor 1，与第一方面的实施例相同的内容不再重复说明。
如图15所示，该IAB节点的集成装置1500包括：中央单元(IAB-donor-CU1)1501和分布式单元(IAB-donor-DU1)1502。
在一些实施例中，所述IAB-donor-CU1 1501向所述IAB节点的MT发送第一信息，所述第一信息包含所述IAB节点的标识信息和/或所述RRC终结IAB宿主的标识信息，以便所述IAB节点的DU将与所述第一信息相关的第二信息发送给所述F1终结IAB宿主。
在上述实施例中，所述IAB节点的标识信息可以为所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识；所述RRC终结IAB宿主的标识信息可以为所述RRC终结IAB宿主的CU的基站标识信息。
在上述实施例中，所述第一信息可以包括所述IAB节点的标识信息和所述RRC终结IAB宿主的标识信息，所述第二信息与所述第一信息相同；或者，所述第一信息可以包括所述IAB节点的标识信息；所述第二信息包括所述IAB节点的MT的服务小区标识NCGI和所述IAB节点的标识信息。
在上述实施例中，所述第一信息可以显式包含在RRC重配置消息中或者包含在所述RRC重配置消息的一个容器(container)中。
在上述实施例中，所述RRC重配置消息中可以包含第一IE，所述第一IE包含所述第一信息；或者，所述RRC重配置消息的bap-Config IE中可以包含第二IE或者第一字段，所述第二IE或者第一字段包含所述第一信息。
在另一些实施例中，IAB-donor-CU1 1501接收所述IAB节点的MT发送的第一RRC消息，所述第一RRC消息包含所述F1终结IAB宿主的标识信息；所述IAB-donor-CU1 1501根据所述第一RRC消息，将所述IAB节点的标识信息发送给所 述F1终结IAB宿主。
在上述实施例中，所述第一RRC消息可以为UEAssistanceInformation消息；所述UEAssistanceInformation消息中可以包含第四IE，所述第四IE包含所述F1终结IAB宿主的标识信息。
在上述实施例中，所述IAB-donor-CU1 1501可以向所述F1终结IAB宿主发送第一Xn消息，所述第一Xn消息包含所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识和/或所述IAB节点的BAP地址。
在上述实施例中，所述IAB-donor-CU1 1501还可以接收所述F1终结IAB宿主发送的第二Xn消息，所述第二Xn消息包含确认信息。
在一些实施例中，所述RRC终结IAB宿主的CU和所述F1终结IAB宿主的CU不同。
在一些实施例中，所述IAB-donor-CU1 1501为所述IAB节点分配一个或多个IP地址，以便所述IAB节点根据所述IP地址向所述F1终结IAB宿主的CU发起TNL建立以及F1建立过程。
在上述实施例中，所述IP地址锚定在所述RRC终结IAB宿主的DU。
在一些实施例中，所述IAB-donor-CU1 1501接收所述IAB节点的MT发送的RRC建立完成消息，所述RRC建立完成消息包括第三信息，所述第三信息指示了所述IAB节点的移动IAB能力；所述IAB-donor-CU1 1501根据所述第三信息选择支持移动IAB的AMF。
在一些实施例中，所述IAB-donor-CU1 1501发送广播消息，所述广播消息指示了支持移动IAB的小区；以便所述IAB节点在接收了所述广播消息后，根据所述广播消息进行小区选择。
图16是本申请实施例的IAB节点的集成装置的另一示意图，该装置例如可以是IAB网络中的IAB宿主，也可以是配置于该IAB宿主中的某个或某些部件或者组件。该IAB宿主对应图2中的F1终结IAB宿主，也即IAB-donor 2，与第一方面的实施例相同的内容不再重复说明。
如图16所示，该IAB节点的集成装置1600包括：中央单元(IAB-donor-CU2)1601和分布式单元(IAB-donor-DU2)1602。
在一些实施例中，所述IAB-donor-CU2 1601接收IAB节点的DU发送的第二信 息，所述第二信息与第一信息相关，所述第一信息包含所述IAB节点的标识信息和/或所述RRC终结IAB宿主的标识信息。
在上述实施例中，所述IAB节点的标识信息为所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识；所述RRC终结IAB宿主的标识信息为所述RRC终结IAB宿主的CU的基站标识信息。
在上述实施例中，所述第一信息包括所述IAB节点的标识信息和所述RRC终结IAB宿主的标识信息，所述第二信息与所述第一信息相同；或者，所述第一信息包括所述IAB节点的标识信息；所述第二信息包括所述IAB节点的MT的服务小区标识NCGI和所述IAB节点的标识信息。
在上述实施例中，所述第二信息显式包含在F1AP消息中或者包含在所述F1AP消息的一个容器(container)中。
在上述实施例中，所述F1AP消息可以为F1建立请求消息。
在上述实施例中，所述F1AP消息中可以包含第三IE，所述第三IE包含所述第二信息。
在一些实施例中，所述IAB-donor-CU2 1601接收IAB节点的DU发送的F1建立请求消息，所述F1建立请求消息包含所述IAB节点的BAP地址；所述IAB-donor-CU2为该IAB节点保存所述BAP地址。
在一些实施例中，所述IAB-donor-CU2 1601接收所述RRC终结IAB宿主的CU发送的第一Xn消息，所述第一Xn消息包含所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识和/或所述IAB节点的BAP地址。
在上述实施例中，所述IAB-donor-CU2 1601还可以向所述RRC终结IAB宿主的CU发送第二Xn消息，所述第二Xn消息包含确认信息。
图17是本申请实施例的IAB节点的集成装置的另一示意图，该装置例如可以是IAB网络中的IAB宿主，也可以是配置于该IAB宿主中的某个或某些部件或者组件。该IAB宿主对应图2中的RRC终结IAB宿主，也即IAB-donor 1，与第二方面的实施例相同的内容不再重复说明。
如图17所示，该IAB节点的集成装置1700包括：中央单元(IAB-donor-CU1)1701和分布式单元(IAB-donor-DU1)1702。
在本申请实施例中，IAB-donor-CU1 1701确定F1终结IAB宿主的CU的基站标 识；将所述F1终结IAB宿主的CU的基站标识发送给IAB节点的MT，以便所述IAB节点的DU根据所述基站标识与所述F1终结IAB宿主的CU进行F1建立。
在一些实施例中，IAB-donor-CU1 1701确定F1终结IAB宿主的基站标识，包括：
IAB-donor-CU1 1701被OAM配置所述F1终结IAB宿主的基站标识；或者，
IAB-donor-CU1 1701根据基于ANR功能得到信息选择F1终结IAB宿主，从而得到所述F1终结IAB宿主的基站标识。
在上述实施例中，所述OAM可以配置多个基站标识，所述IAB-donor-CU1 1701根据预定策略从所述多个基站标识中选择一个基站标识。
在上述实施例中，所述OAM还可以配置所述多个基站标识的优先级，所述IAB-donor-CU1 1701选择所述多个基站标识中，基站标识的优先级最高的基站标识。
在一些实施例中，所述IAB-donor-CU1 1701通过RRC重配置消息将所述F1终结IAB宿主的基站标识发送给IAB节点的MT。
在上述实施例中，所述IAB节点的DU可以根据所述基站标识和通过所述基站标识发现的所述F1终结IAB宿主的CU的TNL地址，与所述F1终结IAB宿主的CU进行F1建立。
在上述实施例中，所述IAB-donor-CU1 1701还可以通过RRC重配置消息将所述F1终结IAB宿主的CU的TNL地址发送给所述IAB节点的MT；所述IAB节点的DU根据所述基站标识和所述TNL地址与所述F1终结IAB宿主的CU进行F1建立。
在上述实施例中，所述RRC重配置消息中可以包含第五IE，所述第五IE包含所述F1终结IAB宿主的基站标识；或者，所述RRC重配置消息的bap-Config IE中可以包含第六IE或者第二字段，所述第六IE或者第二字段包含所述基站标识。
在一些实施例中，所述IAB-donor-CU1 1701向所述F1终结IAB宿主发送第一Xn消息，所述第一Xn消息包含所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识和/或所述IAB节点的BAP地址。
在上述实施例中，所述IAB-donor-CU1 1701还可以接收所述F1终结IAB宿主发送的第二Xn消息，所述第二Xn消息包含确认信息。
在一些实施例中，所述IAB-donor-CU1 1701为所述IAB节点分配一个或多个IP地址，并且，所述IP地址锚定在所述RRC终结IAB宿主的DU。
在一些实施例中，所述IAB-donor-CU1 1701接收所述IAB节点的MT发送的RRC 建立完成消息，所述RRC建立完成消息包括第三信息，所述第三信息指示了所述IAB节点的移动IAB能力；所述IAB-donor-CU1 1701根据所述第三信息选择一个支持移动IAB的AMF。
在一些实施例中，所述IAB-donor-DU1 1702发送广播消息，所述广播消息指示了支持移动IAB的小区，以便所述IAB节点根据所述广播消息进行小区选择。
图18是本申请实施例的IAB节点的集成装置的另一示意图，该装置例如可以是IAB网络中的IAB宿主，也可以是配置于该IAB宿主中的某个或某些部件或者组件。该IAB宿主对应图2中的F1终结IAB宿主，也即IAB-donor 2，与第二方面的实施例相同的内容不再重复说明。
如图18所示，该IAB节点的集成装置1800包括：中央单元(IAB-donor-CU1)1801和分布式单元(IAB-donor-DU1)1802。
在本申请实施例中，IAB-donor-CU1 1801接收RRC终结IAB宿主的CU发送的第一Xn消息，所述第一Xn消息包含所述RRC终结IAB宿主为IAB节点生成的UE XnAP标识和/或所述IAB节点的BAP地址。
在一些实施例中，IAB-donor-CU1 1801还向所述RRC终结IAB宿主的CU发送第二Xn消息，所述第二Xn消息包含确认信息。
本申请实施例提供一种设置装置。该装置例如可以是IAB网络中的IAB节点，也可以是配置于该IAB节点中的某个或某些部件或者组件。该IAB节点对应图2中的IAB节点1，与第一方面的实施例至第三方面的实施例相同的内容不再重复说明。
图19是本申请实施例的设置装置的一示意图，如图19所示，该装置1900包括：移动终端(IAB-MT)1901和分布式单元(IAB-DU)1902。
在本申请实施例中，IAB-MT 1901向RRC终结IAB宿主发送RRC建立完成消息，所述RRC建立完成消息包括第三信息，所述第三信息指示了所述IAB节点的移动IAB能力，以便所述RRC终结IAB宿主选择一个支持移动IAB的AMF。
图20是本申请实施例的设置装置的另一示意图，如图20所示，该装置2000包括：移动终端(IAB-MT)2001和分布式单元(IAB-DU)2002。
在本申请实施例中，IAB-MT 2001接收RRC终结IAB宿主发送的广播消息，所述广播消息指示了支持移动IAB的小区；所述IAB-MT 2001根据所述广播消息进行小区选择。
在一些实施例中，上述广播消息为SIB消息，本申请不限于此。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的装置1400～2000还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图14至图20中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
根据本申请实施例的装置，解决了IAB节点的集成问题，使得IAB-MT和并置的IAB-DU能够集成到不同的donor-CU上，提高了网络配置的灵活性。
第五方面的实施例
本申请实施例提供一种IAB通信系统，包括IAB节点和IAB-donor节点，该IAB节点被配置为执行第一方面至第三方面中任一方面的实施例中由IAB节点所执行的方法，该IAB-donor节点被配置为执行第一方面至第三方面中任一方面的实施例中由IAB-donor 1或者IAB-donor 2所执行的方法。关于该IAB节点和该IAB-donor节点的具体行为已经在第一方面至第三方面的实施例中做了详细说明，其内容被合并于此，此处不再赘述。
本申请实施例还提供一种IAB节点，该节点包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如第一方面至第三方面中任一方面的实施例中由IAB节点所执行的方法。
图21是本申请实施例的IAB节点的一示意图。如图14所示，该IAB节点2100可以包括处理器2101和存储器2102；存储器2102存储有数据和程序，并耦合到处理器2101。值得注意的是，该图是示例性的；还可以使用其它类型的结构，来补充或代替该结构，以实现电信功能或其它功能。
例如，处理器2101可以被配置为执行程序而实现如第一方面至第三方面中任一方面的实施例中由IAB节点所执行的方法。
如图21所示，该IAB节点2100还可以包括：通信模块2103、输入单元2104、显示器2105、电源2106。其中，上述部件的功能与现有技术类似，此处不再赘述。 值得注意的是，IAB节点2100也并不是必须要包括图21中所示的所有部件，上述部件并不是必需的；此外，IAB节点2100还可以包括图21中没有示出的部件，可以参考现有技术。
本申请实施例还提供了一种IAB-donor节点，该IAB-donor节点包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如第一方面至第三方面中任一方面的实施例中由IAB-donor 1或者IAB-donor 2所执行的方法。
图22是本申请实施例的IAB-donor节点的一示意图。如图22所示，IAB-donor节点2200可以包括：中央处理器(CPU)2201和存储器2202；存储器2202耦合到中央处理器2201。其中该存储器2202可存储各种数据；此外还存储信息处理的程序，并且在中央处理器2201的控制下执行该程序，以接收IAB节点发送的各种信息、并且向IAB节点发送各种信息。
例如，处理器2201可以被配置为执行程序而实现如第一方面至第三方面中任一方面的实施例中由IAB-donor 1或者IAB-donor 2所执行的方法。
此外，如图22所示，IAB-donor节点2200还可以包括：收发机2203和天线2204等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，IAB-donor节点2200也并不是必须要包括图22中所示的所有部件；此外，IAB-donor节点2200还可以包括图22中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机可读程序，其中当在IAB节点中执行所述程序时，所述程序使得计算机在所述IAB节点中执行第一方面至第三方面中任一方面的实施例中由IAB节点所执行的方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在IAB节点中执行第一方面至第三方面中任一方面的实施例中由IAB节点所执行的方法。
本申请实施例还提供一种计算机可读程序，其中当在IAB-donor节点中执行所述程序时，所述程序使得计算机在所述IAB-donor节点中执行第一方面至第三方面中任一方面的实施例中由IAB-donor 1或IAB-donor 2所执行的方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在IAB-donor节点中执行第一方面至第三方面中任一方面的实施 例中由IAB-donor 1或IAB-donor 2所执行的方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。逻辑部件例如现场可编程逻辑部件、微处理器、计算机中使用的处理器等。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围 内。
关于本实施例公开的上述实施方式，还公开了如下的附记：
1.一种IAB节点的集成方法，应用于IAB节点，所述IAB节点包括MT(移动终端)和DU(分布式单元)，其中，所述方法包括：
IAB节点的DU被OAM配置或IAB节点的MT被RRC终结IAB宿主的CU配置F1终结IAB宿主的CU的基站标识；
所述IAB节点的DU根据所述基站标识与所述F1终结IAB宿主的CU进行F1建立。
2.根据附记1所述的方法，其中，
所述RRC终结IAB宿主的CU和所述F1终结IAB宿主的CU不同。
3.根据附记1所述的方法，其中，所述方法还包括：
所述IAB节点的DU通过所述基站标识发现所述F1终结IAB宿主的CU的TNL地址；
所述IAB节点的DU根据所述基站标识和所述TNL地址与所述F1终结IAB宿主的CU进行F1建立。
4.根据附记1所述的方法，其中，
所述IAB节点的DU还被所述OAM配置所述F1终结IAB宿主的CU的TNL地址；
所述IAB节点的DU根据所述基站标识和所述TNL地址与所述F1终结IAB宿主的CU进行F1建立。
5.根据附记1所述的方法，其中，
所述OAM配置了多个基站标识，
所述IAB节点的DU根据预定策略从所述多个基站标识中选择一个基站标识，进行F1建立。
6.根据附记5所述的方法，其中，
所述OAM还配置了所述多个基站标识的优先级，
所述IAB节点的DU选择所述多个基站标识中，基站标识的优先级最高的基站标识，进行F1建立。
7.根据附记1所述的方法，其中，所述方法还包括：
所述IAB节点的DU使用所述RRC终结IAB宿主的CU为所述IAB节点分配的IP地址向所述F1终结IAB宿主的CU发起TNL建立以及F1建立过程。
8.根据附记7所述的方法，其中，
在F1建立请求消息中，包含所述IAB节点的BAP地址；
所述F1终结IAB宿主的CU在收到所述F1建立请求消息后，为所述IAB节点保存所述BAP地址。
9.根据附记7所述的方法，其中，
所述RRC终结IAB宿主的CU为所述IAB节点分配的IP地址的数量为一个或多个，并且，所述IP地址锚定在所述RRC终结IAB宿主的DU。
10.根据附记1-9任一项所述的方法，其中，
所述IAB节点的MT接收所述RRC终结IAB宿主的CU发送的第一信息，所述第一信息包含所述IAB节点的标识信息和/或所述RRC终结IAB宿主的标识信息；
所述IAB节点的DU将与所述第一信息相关的第二信息发送给所述F1终结IAB宿主。
11.根据附记10所述的方法，其中，
所述IAB节点的标识信息为所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识；
所述RRC终结IAB宿主的标识信息为所述RRC终结IAB宿主的CU的基站标识信息。
12.根据附记10所述的方法，其中，
所述第一信息包括所述IAB节点的标识信息和所述RRC终结IAB宿主的标识信息，所述第二信息与所述第一信息相同；或者，
所述第一信息包括所述IAB节点的标识信息；所述第二信息包括所述IAB节点的MT的服务小区标识NCGI和所述IAB节点的标识信息。
13.根据附记10-12任一项所述的方法，其中，
所述第一信息显式包含在RRC重配置消息中或者包含在所述RRC重配置消息的一个容器(container)中。
14.根据附记13所述的方法，其中，
所述RRC重配置消息中包含第一IE，所述第一IE包含所述第一信息；或者，
所述RRC重配置消息的bap-Config IE中包含第二IE或者第一字段，所述第二IE或者第一字段包含所述第一信息。
15.根据附记10-12任一项所述的方法，其中，
所述第二信息显式包含在F1AP消息中或者包含在所述F1AP消息的一个容器(container)中。
16.根据附记15所述的方法，其中，
所述F1AP消息为F1建立请求消息。
17.根据附记15所述的方法，其中，
所述F1AP消息中包含第三IE，所述第三IE包含所述第二信息。
18.根据附记1-9任一项所述的方法，其中，
所述IAB节点的MT向所述RRC终结IAB宿主的CU发送第一RRC消息，所述第一RRC消息包含所述F1终结IAB宿主的标识信息，以便所述RRC终结IAB宿主将所述IAB节点的标识信息发送给所述F1终结IAB宿主。
19.根据附记18所述的方法，其中，
所述第一RRC消息为UEAssistanceInformation消息；
所述UEAssistanceInformation消息中包含第四IE，所述第四IE包含所述F1终结IAB宿主的标识信息。
20.根据附记18所述的方法，其中，所述方法还包括：
所述IAB节点的MT在所述IAB节点的DU与所述F1终结IAB宿主的F1建立完成之后发起UE辅助信息上报过程；
其中，所述IAB节点具有提供F1终结IAB宿主的标识信息的能力，并且，所述IAB节点被配置了能力上报，并且，所述IAB节点处于RRC连接态。
21.根据附记18所述的方法，其中，
所述RRC终结IAB宿主的CU向所述F1终结IAB宿主发送第一Xn消息，所述第一Xn消息包含所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识和/或所述IAB节点的BAP地址。
22.根据附记21所述的方法，其中，
所述RRC终结IAB宿主的CU接收所述F1终结IAB宿主发送的第二Xn消息，所述第二Xn消息包含确认信息。
23.根据附记1-22任一项所述的方法，其中，所述方法还包括：
所述IAB节点的MT向所述RRC终结IAB宿主发送RRC建立完成消息，所述RRC建立完成消息包括第三信息，所述第三信息指示了所述IAB节点的移动IAB能力，以便所述RRC终结IAB宿主选择一个支持移动IAB的AMF。
24.根据附记1-22任一项所述的方法，其中，所述方法还包括：
所述IAB节点的MT接收所述RRC终结IAB宿主发送的广播消息，所述广播消息指示了支持移动IAB的小区；
所述IAB节点根据所述广播消息进行小区选择。
25.一种IAB节点的集成方法，应用于RRC终结IAB宿主，所述RRC终结IAB宿主包括CU和DU，其中，所述方法包括：
所述RRC终结IAB宿主向所述IAB节点的MT发送第一信息，所述第一信息包含所述IAB节点的标识信息和/或所述RRC终结IAB宿主的标识信息，以便所述IAB节点的DU将与所述第一信息相关的第二信息发送给所述F1终结IAB宿主。
26.根据附记25所述的方法，其中，
所述IAB节点的标识信息为所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识；
所述RRC终结IAB宿主的标识信息为所述RRC终结IAB宿主的CU的基站标识信息。
27.根据附记25所述的方法，其中，
所述第一信息包括所述IAB节点的标识信息和所述RRC终结IAB宿主的标识信息，所述第二信息与所述第一信息相同；或者，
所述第一信息包括所述IAB节点的标识信息；所述第二信息包括所述IAB节点的MT的服务小区标识NCGI和所述IAB节点的标识信息。
28.根据附记25-27任一项所述的方法，其中，
所述第一信息显式包含在RRC重配置消息中或者包含在所述RRC重配置消息的一个容器(container)中。
29.根据附记28所述的方法，其中，
所述RRC重配置消息中包含第一IE，所述第一IE包含所述第一信息；或者，
所述RRC重配置消息的bap-Config IE中包含第二IE或者第一字段，所述第二IE 或者第一字段包含所述第一信息。
30.一种IAB节点的集成方法，应用于RRC终结IAB宿主，所述RRC终结IAB宿主包括CU和DU，其中，所述方法还包括：
RRC终结IAB宿主的CU接收IAB节点的MT发送的第一RRC消息，所述第一RRC消息包含所述F1终结IAB宿主的标识信息；
所述RRC终结IAB宿主根据所述第一RRC消息，将所述IAB节点的标识信息发送给所述F1终结IAB宿主。
31.根据附记30所述的方法，其中，
所述第一RRC消息为UEAssistanceInformation消息；
所述UEAssistanceInformation消息中包含第四IE，所述第四IE包含所述F1终结IAB宿主的标识信息。
32.根据附记30或31所述的方法，其中，所述方法还包括：
所述RRC终结IAB宿主的CU向所述F1终结IAB宿主发送第一Xn消息，所述第一Xn消息包含所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识和/或所述IAB节点的BAP地址。
33.根据附记32所述的方法，其中，
所述RRC终结IAB宿主的CU接收所述F1终结IAB宿主发送的第二Xn消息，所述第二Xn消息包含确认信息。
34.根据附记25-33任一项所述的方法，其中，
所述RRC终结IAB宿主的CU和所述F1终结IAB宿主的CU不同。
35.根据附记25-33任一项所述的方法，其中，所述方法还包括：
所述RRC终结IAB宿主的CU为所述IAB节点分配一个或多个IP地址，以便所述IAB节点使用所述IP地址向所述F1终结IAB宿主的CU发起TNL建立以及F1建立过程。
36.根据附记35所述的方法，其中，
所述IP地址锚定在所述RRC终结IAB宿主的DU。
37.根据附记25-36任一项所述的方法，其中，所述方法还包括：
所述RRC终结IAB宿主接收所述IAB节点的MT发送的RRC建立完成消息，所述RRC建立完成消息包括第三信息，所述第三信息指示了所述IAB节点的移动IAB 能力；
所述RRC终结IAB宿主根据所述第三信息选择支持移动IAB的AMF。
38.根据附记25-36任一项所述的方法，其中，所述方法还包括：
所述RRC终结IAB宿主发送广播消息，所述广播消息指示了支持移动IAB的小区；以便所述IAB节点在接收了所述广播消息后，根据所述广播消息进行小区选择。
39.一种IAB节点的集成方法，应用于F1终结IAB宿主，所述F1终结IAB宿主包括CU和DU，其中，所述方法包括：
所述F1终结IAB宿主接收IAB节点的DU发送的第二信息，所述第二信息与第一信息相关，所述第一信息包含所述IAB节点的标识信息和/或所述RRC终结IAB宿主的标识信息。
40.根据附记39所述的方法，其中，
所述IAB节点的标识信息为所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识；
所述RRC终结IAB宿主的标识信息为所述RRC终结IAB宿主的CU的基站标识信息。
41.根据附记39所述的方法，其中，
所述第一信息包括所述IAB节点的标识信息和所述RRC终结IAB宿主的标识信息，所述第二信息与所述第一信息相同；或者，
所述第一信息包括所述IAB节点的标识信息；所述第二信息包括所述IAB节点的MT的服务小区标识NCGI和所述IAB节点的标识信息。
42.根据附记39所述的方法，其中，
所述第二信息显式包含在F1AP消息中或者包含在所述F1AP消息的一个容器(container)中。
43.根据附记42所述的方法，其中，
所述F1AP消息为F1建立请求消息。
44.根据附记42所述的方法，其中，
所述F1AP消息中包含第三IE，所述第三IE包含所述第二信息。
45.根据附记39所述的方法，其中，所述方法还包括：
F1终结IAB宿主的CU接收IAB节点的DU发送的F1建立请求消息，所述F1 建立请求消息包含所述IAB节点的BAP地址；
所述F1终结IAB宿主为所述IAB节点保存所述BAP地址。
46.一种IAB节点的集成方法，应用于RRC终结IAB宿主，所述RRC终结IAB宿主包括CU(中央单元)和DU(分布式单元)，其中，所述方法包括：
RRC终结IAB宿主的CU为IAB节点确定F1终结IAB宿主的CU的基站标识；
所述RRC终结IAB宿主的CU将所述F1终结IAB宿主的CU的基站标识发送给所述IAB节点的MT，以便所述IAB节点的DU根据所述基站标识与所述F1终结IAB宿主的CU进行F1建立。
47.根据附记46所述的方法，其中，RRC终结IAB宿主的CU为IAB节点确定F1终结IAB宿主的基站标识，包括：
所述RRC终结IAB宿主的CU被OAM配置所述F1终结IAB宿主的基站标识；或者，
所述RRC终结IAB宿主的CU根据基于ANR功能得到信息选择F1终结IAB宿主，从而得到所述F1终结IAB宿主的基站标识。
48.根据附记47所述的方法，其中，
所述OAM配置了多个基站标识，
所述RRC终结IAB宿主的CU根据预定策略从所述多个基站标识中选择一个基站标识。
49.根据附记48所述的方法，其中，
所述OAM还配置了所述多个基站标识的优先级，
所述RRC终结IAB宿主的CU选择所述多个基站标识中，基站标识的优先级最高的基站标识。
50.根据附记46所述的方法，其中，
所述RRC终结IAB宿主的CU通过RRC重配置消息将所述F1终结IAB宿主的基站标识发送给IAB节点的MT。
51.根据附记50所述的方法，其中，
所述IAB节点的DU根据所述基站标识和通过所述基站标识发现的所述F1终结IAB宿主的CU的TNL地址，与所述F1终结IAB宿主的CU进行F1建立。
52.根据附记50所述的方法，其中，
所述RRC终结IAB宿主的CU还通过RRC重配置消息将所述F1终结IAB宿主的CU的TNL地址发送给所述IAB节点的MT；
所述IAB节点的DU根据所述基站标识和所述TNL地址与所述F1终结IAB宿主的CU进行F1建立。
53.根据附记50-52任一项所述的方法，其中，
所述RRC重配置消息中包含第五IE，所述第五IE包含所述F1终结IAB宿主的基站标识；或者
所述RRC重配置消息的bap-Config IE中包含第六IE或者第二字段，所述第六IE或者第二字段包含所述基站标识。
53a.根据附记46-53任一项上述的方法，其中，所述方法还包括：
所述RRC终结IAB宿主的CU向所述IAB节点的MT发送第一信息，所述第一信息包含所述IAB节点的标识信息和/或RRC终结IAB宿主的标识信息；以便所述IAB节点的DU将与所述第一信息相关的第二信息发送给F1终结IAB宿主。
53b.根据附记53a所述的方法，其中，
所述IAB节点的标识信息为所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识；
所述RRC终结IAB宿主的标识信息为所述RRC终结IAB宿主的CU的基站标识信息。
53c.根据附记53a所述的方法，其中，
所述第一信息包括所述IAB节点的标识信息和所述RRC终结IAB宿主的标识信息，所述第二信息与所述第一信息相同；或者，
所述第一信息包括所述IAB节点的标识信息；所述第二信息包括所述IAB节点的MT的服务小区标识NCGI和所述IAB节点的标识信息。
53d.根据附记53a-53c任一项所述的方法，其中，
所述第一信息显式包含在RRC重配置消息中或者包含在所述RRC重配置消息的一个容器(container)中。
53e.根据附记53d所述的方法，其中，
所述RRC重配置消息中包含第一IE，所述第一IE包含所述第一信息；或者，
所述RRC重配置消息的bap-Config IE中包含第二IE或者第一字段，所述第二 IE或者第一字段包含所述第一信息。
53f.根据附记53a-53c任一项所述的方法，其中，
所述第二信息显式包含在F1AP消息中或者包含在所述F1AP消息的一个容器(container)中。
53g.根据附记53f所述的方法，其中，
所述F1AP消息为F1建立请求消息。
53h.根据附记53f所述的方法，其中，
所述F1AP消息中包含第三IE，所述第三IE包含所述第二信息。
54.根据附记46-53任一项所述的方法，其中，所述方法还包括：
所述RRC终结IAB宿主的CU向所述F1终结IAB宿主发送第一Xn消息，所述第一Xn消息包含所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识和/或所述IAB节点的BAP地址。
55.根据附记54所述的方法，其中，
所述RRC终结IAB宿主的CU接收所述F1终结IAB宿主发送的第二Xn消息，所述第二Xn消息包含确认信息。
56.根据附记46-55任一项所述的方法，其中，所述方法还包括：
所述RRC终结IAB宿主的CU为所述IAB节点分配一个或多个IP地址，并且，所述IP地址锚定在所述RRC终结IAB宿主的DU。
57.根据附记46-56任一项所述的方法，其中，所述方法还包括：
所述RRC终结IAB宿主接收所述IAB节点的MT发送的RRC建立完成消息，所述RRC建立完成消息包括第三信息，所述第三信息指示了所述IAB节点的移动IAB能力；
所述RRC终结IAB宿主根据所述第三信息选择一个支持移动IAB的AMF。
58.根据附记46-56任一项所述的方法，其中，所述方法还包括：
所述RRC终结IAB宿主的DU发送广播消息，所述广播消息指示了支持移动IAB的小区，以便所述IAB节点根据所述广播消息进行小区选择。
59.一种IAB节点的集成方法，应用于F1终结IAB宿主，所述F1终结IAB宿主包括CU(中央单元)和DU(分布式单元)，其中，所述方法包括：
所述F1终结IAB宿主接收RRC终结IAB宿主的CU发送的第一Xn消息，所述 第一Xn消息包含所述RRC终结IAB宿主为IAB节点生成的UE XnAP标识和/或所述IAB节点的BAP地址。
60.根据附记59所述的方法，其中，所述方法还包括：
所述F1终结IAB宿主向所述RRC终结IAB宿主的CU发送第二Xn消息，所述第二Xn消息包含确认信息。
61.一种设置方法，应用于IAB节点，所述IAB节点包括MT和DU，其中，所述方法包括：
IAB节点的MT向RRC终结IAB宿主发送RRC建立完成消息，所述RRC建立完成消息包括第三信息，所述第三信息指示了所述IAB节点的移动IAB能力，以便所述RRC终结IAB宿主选择一个支持移动IAB的AMF。
62.一种设置方法，应用于IAB节点，所述IAB节点包括MT和DU，其中，所述方法包括：
IAB节点的MT接收RRC终结IAB宿主发送的广播消息，所述广播消息指示了支持移动IAB的小区；
所述IAB节点的MT根据所述广播消息进行小区选择。
63.根据附记62所述的方法，其中，
所述广播消息为SIB消息。
64.一种IAB节点，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记1至24以及61-63任一项所述的方法。
65.一种IAB-donor节点，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记25至60任一项所述的方法。
66.一种IAB通信系统，包括IAB节点和IAB-donor节点，所述IAB节点被配置为执行附记1至24以及61-63任一项所述的方法，所述IAB-donor节点被配置为执行附记25至60任一项所述的方法。

Claims (20)

  1. 一种IAB节点的集成装置，应用于IAB节点，所述装置包括IAB-MT(移动终端)和IAB-DU(分布式单元)，其中，
    所述IAB-DU被OAM配置或所述IAB-MT被RRC终结IAB宿主的CU配置F1终结IAB宿主的CU的基站标识；
    所述IAB-DU根据所述基站标识与所述F1终结IAB宿主的CU进行F1建立。
  2. 根据权利要求1所述的装置，其中，
    所述RRC终结IAB宿主的CU和所述F1终结IAB宿主的CU不同。
  3. 根据权利要求1所述的装置，其中，
    所述IAB-DU还被所述OAM配置所述F1终结IAB宿主的CU的TNL地址；
    所述IAB-DU根据所述基站标识和所述TNL地址与所述F1终结IAB宿主的CU进行F1建立。
  4. 根据权利要求1所述的装置，其中，
    所述IAB-DU使用所述RRC终结IAB宿主的CU为所述IAB节点分配的IP地址向所述F1终结IAB宿主的CU发起TNL建立以及F1建立过程。
  5. 根据权利要求4所述的装置，其中，
    在F1建立请求消息中，包含所述IAB节点的BAP地址；
    所述F1终结IAB宿主的CU在收到所述F1建立请求消息后，为所述IAB节点保存所述BAP地址。
  6. 根据权利要求4所述的装置，其中，
    所述RRC终结IAB宿主的CU为所述IAB节点分配的IP地址的数量为一个或多个，并且，所述IP地址锚定在所述RRC终结IAB宿主的DU。
  7. 根据权利要求1所述的装置，其中，
    所述IAB-MT接收所述RRC终结IAB宿主的CU发送的第一信息，所述第一信息包含所述IAB节点的标识信息和/或所述RRC终结IAB宿主的标识信息；
    所述IAB-DU将与所述第一信息相关的第二信息发送给所述F1终结IAB宿主。
  8. 根据权利要求7所述的装置，其中，
    所述IAB节点的标识信息为所述RRC终结IAB宿主为所述IAB节点生成的UE  XnAP标识；
    所述RRC终结IAB宿主的标识信息为所述RRC终结IAB宿主的CU的基站标识信息。
  9. 根据权利要求7所述的装置，其中，
    所述第一信息包括所述IAB节点的标识信息和所述RRC终结IAB宿主的标识信息，所述第二信息与所述第一信息相同；或者，
    所述第一信息包括所述IAB节点的标识信息；所述第二信息包括所述IAB节点的MT的服务小区标识NCGI和所述IAB节点的标识信息。
  10. 根据权利要求7所述的装置，其中，
    所述第一信息显式包含在RRC重配置消息中或者包含在所述RRC重配置消息的一个容器(container)中。
  11. 根据权利要求7所述的装置，其中，
    所述第二信息显式包含在F1AP消息中或者包含在所述F1AP消息的一个容器(container)中。
  12. 根据权利要求11所述的装置，其中，
    所述F1AP消息为F1建立请求消息。
  13. 根据权利要求1所述的装置，其中，
    所述IAB-MT向所述RRC终结IAB宿主的CU发送第一RRC消息，所述第一RRC消息包含所述F1终结IAB宿主的标识信息，以便所述RRC终结IAB宿主将所述IAB节点的标识信息发送给所述F1终结IAB宿主。
  14. 根据权利要求1所述的装置，其中，所述装置还包括：
    所述IAB-MT向所述RRC终结IAB宿主发送RRC建立完成消息，所述RRC建立完成消息包括第三信息，所述第三信息指示了所述IAB节点的移动IAB能力，以便所述RRC终结IAB宿主选择一个支持移动IAB的AMF。
  15. 根据权利要求1所述的装置，其中，所述装置还包括：
    所述IAB-MT接收所述RRC终结IAB宿主发送的广播消息，所述广播消息指示了支持移动IAB的小区；
    所述IAB-MT根据所述广播消息进行小区选择。
  16. 一种IAB节点的集成装置，应用于RRC终结IAB宿主，所述装置包括 IAB-donor CU和IAB-donor DU，其中，
    IAB-donor CU接收IAB节点的MT发送的第一RRC消息，所述第一RRC消息包含所述F1终结IAB宿主的标识信息；
    所述IAB-donor CU根据所述第一RRC消息，将所述IAB节点的标识信息发送给所述F1终结IAB宿主。
  17. 根据权利要求16所述的装置，其中，
    所述第一RRC消息为UEAssistanceInformation消息；
    所述UEAssistanceInformation消息中包含第四IE，所述第四IE包含所述F1终结IAB宿主的标识信息。
  18. 根据权利要求16所述的装置，其中，所述装置还包括：
    所述IAB-donor CU向所述F1终结IAB宿主发送第一Xn消息，所述第一Xn消息包含所述RRC终结IAB宿主为所述IAB节点生成的UE XnAP标识和/或所述IAB节点的BAP地址。
  19. 根据权利要求18所述的装置，其中，
    所述IAB-donor CU接收所述F1终结IAB宿主发送的第二Xn消息，所述第二Xn消息包含确认信息。
  20. 一种设置装置，应用于IAB节点，所述装置包括IAB-MT和IAB-DU，其中，
    IAB-MT向RRC终结IAB宿主发送RRC建立完成消息，所述RRC建立完成消息包括第三信息，所述第三信息指示了所述IAB节点的移动IAB能力，以便所述RRC终结IAB宿主选择一个支持移动IAB的AMF。
PCT/CN2023/112456 2023-08-11 2023-08-11 接入回传一体化节点的集成方法和装置 Pending WO2025035240A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2023/112456 WO2025035240A1 (zh) 2023-08-11 2023-08-11 接入回传一体化节点的集成方法和装置
CN202380100991.8A CN121693962A (zh) 2023-08-11 2023-08-11 接入回传一体化节点的集成方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/112456 WO2025035240A1 (zh) 2023-08-11 2023-08-11 接入回传一体化节点的集成方法和装置

Publications (1)

Publication Number Publication Date
WO2025035240A1 true WO2025035240A1 (zh) 2025-02-20

Family

ID=94631974

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/112456 Pending WO2025035240A1 (zh) 2023-08-11 2023-08-11 接入回传一体化节点的集成方法和装置

Country Status (2)

Country Link
CN (1) CN121693962A (zh)
WO (1) WO2025035240A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220400427A1 (en) * 2020-02-17 2022-12-15 Zte Corporation Methods and systems for transmitting integrated access and backhaul information
WO2023010367A1 (zh) * 2021-08-04 2023-02-09 富士通株式会社 终端设备的转移方法、装置和系统
WO2023010370A1 (en) * 2021-08-05 2023-02-09 Zte Corporation Systems and methods for configuration information transfer
WO2023011621A1 (zh) * 2021-08-06 2023-02-09 华为技术有限公司 一种通信方法及通信装置
WO2023130231A1 (zh) * 2022-01-04 2023-07-13 富士通株式会社 Iab节点设备、iab宿主设备以及拓扑退行方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220400427A1 (en) * 2020-02-17 2022-12-15 Zte Corporation Methods and systems for transmitting integrated access and backhaul information
WO2023010367A1 (zh) * 2021-08-04 2023-02-09 富士通株式会社 终端设备的转移方法、装置和系统
WO2023010370A1 (en) * 2021-08-05 2023-02-09 Zte Corporation Systems and methods for configuration information transfer
WO2023011621A1 (zh) * 2021-08-06 2023-02-09 华为技术有限公司 一种通信方法及通信装置
WO2023130231A1 (zh) * 2022-01-04 2023-07-13 富士通株式会社 Iab节点设备、iab宿主设备以及拓扑退行方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LENOVO, MOTOROLA MOBILITY: "Discussion on IAB inter-donor topology redundancy", 3GPP DRAFT; R3-212165, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20210517 - 20210528, 7 May 2021 (2021-05-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052002342 *

Also Published As

Publication number Publication date
CN121693962A (zh) 2026-03-17

Similar Documents

Publication Publication Date Title
CN116438835A (zh) 用于施主间移动的方法和装置
JP7639945B2 (ja) 信号の送受信方法、装置及び通信システム
CN116235543A (zh) 群组切换的方法、装置和系统
CN117796000A (zh) 集成的接入和回传的通信装置以及方法
WO2022205326A1 (en) Integrated access and backhaul donor migration methods and systems
US20240349166A1 (en) Iab-node device, iab-donor device and topology revoking method
WO2023150975A1 (zh) Iab宿主设备以及传输迁移回退方法
WO2024026804A1 (zh) 移动节点的配置方法、移动节点和宿主设备
WO2025035240A1 (zh) 接入回传一体化节点的集成方法和装置
CN116724589A (zh) 群组迁移方法、装置和系统
JP2024533856A (ja) 無線ルーティング方法と装置
JP7831633B2 (ja) Ｉａｂノード機器、ｉａｂドナー機器及び伝送アドレス確定方法
JP7806927B2 (ja) 情報を設定する方法と装置及び通信システム
JP7741617B2 (ja) Ｉａｂドナー機器及び伝送移行管理方法
US20240397380A1 (en) Iab-donor device and transport migration management method
CN102647806B (zh) Ip报文处理方法、系统和设备
WO2025091416A1 (zh) 移动iab节点的授权状态的更新方法和装置
WO2024026803A1 (zh) 移动节点的配置方法和宿主设备
WO2025035233A1 (zh) 消息转发方法和装置
JP2026074024A (ja) Ｉａｂドナー機器及び伝送アドレス設定方法
JP2026513333A (ja) 分散ユニット移行の方法、制御装置及び通信システム
WO2023197184A1 (zh) Iab宿主设备以及传输地址配置方法
WO2024164214A1 (zh) 信息处理方法和装置
JP2026513309A (ja) 信号の送受信方法と装置及び通信システム
CN119968888A (zh) 用于iab节点集成的方法及设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23948685

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023948685

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE