WO2023184542A1 - 配置信息的方法、装置和通信系统 - Google Patents

配置信息的方法、装置和通信系统 Download PDF

Info

Publication number
WO2023184542A1
WO2023184542A1 PCT/CN2022/085090 CN2022085090W WO2023184542A1 WO 2023184542 A1 WO2023184542 A1 WO 2023184542A1 CN 2022085090 W CN2022085090 W CN 2022085090W WO 2023184542 A1 WO2023184542 A1 WO 2023184542A1
Authority
WO
WIPO (PCT)
Prior art keywords
bap
iab
topology
default
donor
Prior art date
Application number
PCT/CN2022/085090
Other languages
English (en)
French (fr)
Inventor
易粟
路杨
贾美艺
李国荣
Original Assignee
富士通株式会社
易粟
路杨
贾美艺
李国荣
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, 易粟, 路杨, 贾美艺, 李国荣 filed Critical 富士通株式会社
Priority to PCT/CN2022/085090 priority Critical patent/WO2023184542A1/zh
Publication of WO2023184542A1 publication Critical patent/WO2023184542A1/zh

Links

Images

Classifications

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

Definitions

  • the embodiments of this application relate to the field of communication technology.
  • IAB Integrated access and backhaul
  • NG-RAN next generation radio access network
  • IAB-node The integrated access and backhaul node
  • NR New Radio
  • IAB-donor represents a network device (for example, gNB) that supports IAB functionality.
  • IAB-node can connect to an IAB host (IAB-donor) through one or multiple hops. These multi-hop connections form a directed acyclic graph (DAG) topology with the IAB host as the root node.
  • DAG directed acyclic graph
  • the IAB host is responsible for performing centralized resource management, topology management and routing management in the IAB network topology.
  • IAB-node supports the function of gNB-DU (distributed unit, distributed unit). IAB-node DU is also called IAB-DU. IAB-DU is the wireless interface to the terminal equipment (UE) and the next hop IAB-node. The end point of the NR access interface is also the end point of the F1 protocol to the gNB-CU (central unit, central unit) on the IAB-donor. IAB-DU can serve ordinary UEs and IAB sub-nodes. IAB-DU implements network-side device functions, connects to the downstream child IAB-node, provides NR air interface access to the UE and the downstream child IAB-node, and establishes an F1 connection with the IAB donor-CU.
  • IAB-node In addition to the gNB-DU function, IAB-node also supports some UE functions, called IAB-MT (Mobile Termination). IAB-MT includes physical layer, layer 2, RRC and NAS functions to connect to another IAB-node. Or gNB-DU of IAB-donor, connected to gNB-CU on IAB-donor and connected to the core network. IAB-MT can support UE physical layer, access stratum (AS), radio resource control (RRC) layer and non-access stratum (NAS) layer functions, and can be connected to the IAB parent node.
  • AS access stratum
  • RRC radio resource control
  • NAS non-access stratum
  • IAB-donor is the terminal node on the network side. IAB-donor provides network access for IAB-MT or UE through backhaul or access links. 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. In the independent networking scenario, gNB and IAB-donor-CU are connected through the Xn interface.
  • BAP Backhaul Adaptation Protocol
  • RLC Radio Link Control
  • FIG 1 is a schematic diagram of the relationship between IAB parent and child nodes.
  • IAB-node 100 includes IAB-MT functional unit 101 and IAB-DU functional unit 102.
  • the neighboring nodes on the interface of IAB-DU functional unit 102 are called children.
  • Node (child node), the child nodes 201, 202, 203 shown in Figure 1, the IAB-DU functional unit 102 and the child nodes 201, 202, 203 can communicate through the air interface (Uu);
  • IAB-MT The neighboring nodes on the interface of the functional unit 101 are called parent nodes, such as the parent nodes 301 and 302 shown in Figure 1.
  • the IAB-MT functional unit 101 and the parent nodes 301 and 302 can be connected through the air interface. (Uu) communicate.
  • the direction from IAB-node 100 to child nodes 201, 202, and 203 is called the downstream direction, and the direction from IAB-node 100 to parent nodes 301 and 302 is called the upstream direction.
  • the IAB-donor (not shown) performs centralized resource, topology and routing management for the IAB topology 10 .
  • the IAB node In a multi-hop scenario, in order to realize the relay and forwarding of data packets, the IAB node needs to determine the target node where the data packet arrives, and then determine the next-hop node corresponding to the target node according to the routing table and send it.
  • the donor-CU configures the IAB node through F1AP (F1 application protocol) signaling for each uplink F1-U Tunnel, non-UE associated (Non-UE associated) F1AP message, and user equipment associated (UE) initiated from the IAB node.
  • F1AP F1 application protocol
  • UE user equipment associated
  • the IAB node determines the BAP routing identifiers corresponding to different types of upstream IP packets initiated from the IAB node based on the routing identifier mapping information, and encapsulates the BAP subheaders containing the BAP routing identifier information for these upstream IP packets.
  • Donor-CU configures the mapping of different types of downlink data packets to BAP routing identifiers for donor-DU through F1AP signaling.
  • Donor-DU determines the BAP routing identifier corresponding to the received downstream IP packets based on the routing identifier mapping information, and encapsulates the BAP subheader containing the BAP routing identifier downstream for these downstream IP packets.
  • the BAP routing identifier includes the destination BAP address and the path identity from the IAB node to the donor-DU.
  • the BAP address is also called DESTINATION in the BAP header.
  • Each IAB node and donor-DU are configured with a BAP address.
  • RRC can be configured with a default BH RLC channel and a default BAP route identifier for non-F1-U traffic. These configurations can be updated in topology adaptation scenarios.
  • IAB nodes can have redundant paths to different IAB-donor-CUs.
  • NR-DC can be used to allow the IAB-MT and two parent nodes to have backhaul links at the same time, thereby achieving backhaul route redundancy.
  • Two parent nodes can be connected to different IAB-donor-CUs, and these IAB-donor-CUs can control the establishment and release of redundant routes through the two parent nodes.
  • the gNB-DU function of the parent node and the corresponding IAB-donor-CU acquire the roles of the master node (MN) and/or the secondary node (SN) of the IAB-MT.
  • MN master node
  • SN secondary node
  • the NR-DC framework (such as MCG/SCG related processes) is used to configure dual wireless connections from the IAB node to the parent node.
  • Figure 2 is a schematic diagram of the inter-host topology redundancy (inter-donor topology redundancy, or inter-CU topology redundancy) network structure.
  • Figure 3 is a schematic diagram of partial migration between hosts.
  • node 3 is called the boundary IAB node.
  • a border IAB node refers to one of its RRC interfaces and F1 interfaces that terminate to different IAB-donor-CUs. Border IAB nodes are suitable for partial migration, inter-host topology redundancy and inter-host RLF (radio link failure, wireless link failure) recovery.
  • the DU of node 3 terminates to CU1
  • the MT of node 3 has interfaces to both CU1 and CU2, so it meets the definition of a border IAB node.
  • Descendant IAB nodes refer to nodes that are connected to the network through the border IAB node, and each node is single-connected to its own parent node.
  • IAB node 4 is a descendant node.
  • the F1-terminating host node refers to the donor-CU that terminates the F1 interfaces of the border IAB nodes and descendant nodes.
  • donor-CU1 is the F1 terminating node, that is, IAB-DU3 and IAB-DU4 in Figure 2
  • the F1 interface terminates to donor-CU1.
  • Non-F1-terminating host node refers to a CU that does not terminate the F1 interface of the boundary IAB node and descendant node and has the host function, such as donor-CU2 in Figure 2.
  • the boundary node ie, node 3
  • the IAB-MT of the border IAB node i.e., IAB-MT3
  • IAB-MT3 can be migrated to a parent node under a different IAB-donor-CU (for example, to the parent node under Donor-CU2).
  • the collocated IAB-DU i.e., IAB-DU3
  • the IAB-DU of the descendant node e.g., IAB-DU4
  • This migration is called inter-donor partial migration.
  • the IAB-DU of the border IAB node and the F1 traffic of the descendant node are routed via the BAP layer of the IAB topology to which the IAB-MT of the border IAB node migrates.
  • SA mode can support partial migration between hosts.
  • an IAB node in SA mode When an IAB node in SA mode declares a backhaul link RLF, it can perform RLF recovery on the parent node under a different IAB-donor-CU. Like partial migration between hosts, the collocated IAB-DU and the IAB-DU of the descendant node can maintain the F1 connection with the original IAB-donor-CU.
  • IAB node 3 is the boundary IAB node, and IAB-MT3 changes from a single connection to the parent node IAB node 1 to a single connection to the parent node IAB node 2.
  • IAB-DU3 and its child node IAB node 4 still have F1 connections with donor-CU1, but the path taken by this F1 connection is through IAB node 2 and finally reaches donor-CU1.
  • the boundary node (node 3) is the migration node.
  • the scenario of partial migration between hosts is also applicable to partial RLF recovery.
  • the border IAB node belongs to two IAB topologies.
  • the existing technology does not indicate which topology it is, for example:
  • the situation that SN serves as the F1 termination host is not considered.
  • the BAP address of the corresponding donor-DU is not considered to be a pseudo address.
  • Embodiments of the present application provide a method, device and communication system for configuring information, indicating through the RRC reconfiguration message the correlation of the topology to which the default uplink BH RLC channel configured for the IAB node and/or the default uplink BAP route ID belongs. information. From this, it is possible to indicate which topology the default upstream BAP route ID and/or the default upstream BH RLC channel configured for the IAB node belongs to.
  • a device for configuring information is provided, which is applied to an IAB node.
  • the device includes:
  • a first receiving unit that receives an RRC reconfiguration message, wherein the RRC reconfiguration message indicates relevant information about the topology to which the default uplink BAP route ID configured for the IAB node belongs.
  • a device for configuring information is provided, which is applied to an IAB node.
  • the device includes:
  • the second receiving unit receives an RRC reconfiguration message, wherein the RRC reconfiguration message indicates relevant information about the topology to which the default uplink BH RLC channel configured for the IAB node belongs.
  • a device for configuring information is provided, which is applied to an IAB node.
  • the device includes:
  • the third receiving unit receives the RRC reconfiguration message, wherein the RRC reconfiguration message configures a first donor-DU BAP address for the IAB node, and the first donor-DU BAP address points to the host under the second topology.
  • Distributed unit (DU2) DU2
  • the beneficial effect of the embodiment of the present application is that it can indicate which topology the default upstream BAP route ID and/or the default upstream BH RLC channel configured for the IAB node belongs to.
  • Figure 1 is a schematic diagram of the relationship between IAB parent and child nodes
  • Figure 2 is a schematic diagram of the topological redundant network structure between hosts
  • Figure 3 is a schematic diagram of partial migration between hosts
  • Figure 4 is a schematic diagram of a method for configuring information according to the embodiment of the first aspect
  • Figure 5 is a schematic diagram of a method for configuring information according to the embodiment of the second aspect
  • Figure 6 is a schematic diagram of a method for configuring information according to the embodiment of the third aspect
  • Figure 7 is a schematic diagram of a method for configuring information according to the embodiment of the fourth aspect.
  • Figure 8 is a schematic diagram of a method for configuring information according to the embodiment of the fifth aspect
  • Figure 9 is a schematic diagram of a method for configuring information according to the embodiment of the sixth aspect.
  • Figure 10 is a schematic diagram of a device for configuring information according to the embodiment of the seventh aspect
  • Figure 11 is a schematic diagram of a device for configuring information according to the embodiment of the eighth aspect.
  • Figure 12 is a schematic diagram of a device for configuring information according to the embodiment of the ninth aspect
  • Figure 13 is a schematic diagram of a device for configuring information according to the embodiment of the tenth aspect
  • Figure 14 is a schematic diagram of a device for configuring information according to the embodiment of the eleventh aspect
  • Figure 15 is a schematic diagram of a method for configuring information according to the embodiment of the twelfth aspect
  • Figure 16 is a schematic diagram of the composition of an electronic device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be used by these terms. restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the terms “comprises,” “includes,” “having” and the like refer to the presence of stated features, elements, elements or components but do not exclude the presence or addition of one or more other features, elements, elements or components.
  • the term “communication network” or “wireless communication network” may refer to a network that complies with any of the following communication standards, such as New Radio (NR, New Radio), Long Term Evolution (LTE, Long Term Evolution), Enhanced Long-term evolution (LTE-A, LTE-Advanced), wideband code division multiple access (WCDMA, Wideband Code Division Multiple Access), high-speed packet access (HSPA, High-Speed Packet Access), etc.
  • NR New Radio
  • LTE Long Term Evolution
  • LTE-A Long-term evolution
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • communication between devices in the communication system can be carried out according to any stage of communication protocols, which may include but are not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G. , New Wireless (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
  • Network device refers to a device in a communication system that connects a terminal device to a communication network and provides services to the terminal device.
  • Network equipment may include but is not limited to the following equipment: integrated access and backhaul node (IAB-node), relay (relay), base station (BS, Base Station), access point (AP, Access Point), sending and receiving Point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, wireless network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller) etc.
  • IAB-node integrated access and backhaul node
  • relay relay
  • base station BS, Base Station
  • AP Access Point
  • TRP Transmission Reception Point
  • broadcast transmitter mobile management entity
  • MME Mobile Management Entity
  • gateway server
  • wireless network controller RNC, Radio Network Controller
  • BSC Base Station Controller
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB) and 5G base station (gNB), etc.
  • it may also include remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay or low-power node (such as femeto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay or low-power node such as femeto, pico, etc.
  • base station may include some or all of their functions, each of which may provide communications coverage to a specific geographic area.
  • the term "cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "user equipment” (UE, User Equipment) or “terminal equipment” (TE, Terminal Equipment or Terminal Device) refers to a device that accesses a communication network through a network device and receives network services.
  • Terminal equipment can be fixed or mobile, and can also be called mobile station (MS, Mobile Station), terminal, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), mobile terminal (MT, mobile termination), stations, etc.
  • the terminal equipment may include but is not limited to the following equipment: cellular phone (Cellular Phone), personal digital assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication equipment, handheld device, machine-type communication equipment, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • cellular phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication equipment
  • handheld device machine-type communication equipment
  • laptop computer Cordless phones
  • Cordless phones smartphones, smart watches, digital cameras, and more.
  • the terminal device can also be a machine or device for monitoring or measuring.
  • the terminal device can include but is not limited to: Machine Type Communication (MTC) terminals, Vehicle communication terminals, device-to-device (D2D, Device to Device) terminals, machine-to-machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • network side refers to one side of the network, which may be a certain base station or may include one or more network devices as above.
  • user side or “terminal side” or “terminal device side” refers to the side of the user or terminal, which may be a certain UE or may include one or more terminal devices as above.
  • the high-level signaling may be, for example, radio resource control (RRC) signaling; for example, it is called an RRC message (RRC message), and includes, for example, MIB, system information (system information), and dedicated RRC message; or Called RRC IE (RRC information element).
  • RRC radio resource control
  • the high-level signaling may also be F1-C signaling, or F1AP protocol, for example.
  • F1-C signaling F1AP protocol
  • a multi-hop IAB network deployment scenario is taken as an example to describe each embodiment, in which multiple terminal devices (for example, UE) are connected to the IAB-donor through multi-hop IAB nodes, and finally access the network.
  • the network is, for example, a 5G network. It should be noted that the embodiments of the present application may not be limited to the above scenarios.
  • the IAB topology refers to the combination of all IAB nodes and IAB-donor-DUs interconnected through backhaul links and F1 interfaces and/or RRC terminated to the same IAB-donor-CU.
  • Donor-DU1, IAB node 1, IAB node 3 and IAB node 4 are nodes managed by Donor-CU1, and the IAB topology network composed of them and Donor-CU1 is called the first topology;
  • Donor-DU2, IAB node 2, and IAB node 3 are nodes managed by Donor-CU2.
  • the IAB topology network composed of them and Donor-CU2 is called the second topology.
  • the boundary node ie, IAB node 3 belongs to both the first and second topologies.
  • the border nodes are connected to different IAB topologies.
  • the upstream BAP route identifiers used by the border nodes may lead to two IAB topologies (that is, to two different IAB topologies).
  • BAP routing identifier of donor-DU below donor-CU Because BAP routing identifiers of different IAB topologies are configured and managed by their respective donor-CUs, BAP routing identifiers belonging to different IAB topologies may conflict. Therefore, the default upstream BAP route ID is ambiguous, and further topology-related information needs to be specified.
  • an embodiment of the first aspect of the present application provides a method of configuring information. This method applies to IAB nodes.
  • Figure 4 is a schematic diagram of a method for configuring information according to the embodiment of the first aspect. As shown in Figure 4, the method includes:
  • Operation 401 Receive an RRC reconfiguration message, where the RRC reconfiguration message indicates relevant information about the topology to which the default upstream BAP route ID configured for the IAB node belongs.
  • the IAB node may be a boundary IAB node, for example, IAB node 3 shown in FIG. 2 or FIG. 3 .
  • the IAB node of this application is not limited to this, and the IAB node can also be of other types.
  • the topology-related information may refer to: topology information and/or cell group (CG, cell group) information.
  • the topology includes F1 termination topology or non-F1 termination topology.
  • the cell group information includes primary cell group/secondary cell group (MCG/SCG) information.
  • the RRC reconfiguration message may have first indication information, the first indication information being used to indicate the topology to which the default uplink BAP route ID belongs.
  • the first indication information is used to indicate whether the topology to which the default upstream BAP route ID belongs belongs to an F1 terminated topology or a non-F1 terminated topology.
  • the first indication information may be necessary only for the border IAB node.
  • the default uplink BAP routing ID (defaultUL-BAP-RoutingID) field may be configured or the backhaul adaptation protocol configuration (bap- Config)'s donor central unit (donor-CU) indicates the topology to which the default upstream BAP route ID belongs. Therefore, it is possible to implicitly indicate which topology the default upstream BAP route ID belongs to.
  • the default upstream BAP route ID field is configured by the F1 termination host or the bap-Config containing the default upstream BAP route ID field is configured, then the default upstream BAP route ID belongs to the F1 termination topology; if it is configured by a non-F1 If the termination host configures the default upstream BAP route ID field or configures bap-Config containing the default upstream BAP route ID field, then the default upstream BAP route ID belongs to a non-F1 termination topology.
  • the RRC standard can be enhanced in TS 38.331.
  • the defaultUL-BAP-RoutingID field in the bap-Config IE of the RRC reconfiguration information can be modified to the form shown in Table 3 below.
  • the configuration of the F1 termination host or the non-F1 termination host can be determined by whether the MN or SN is the F1 termination host.
  • the default upstream BAP route ID field or bap-Config containing the default upstream BAP route ID field is configured.
  • the IAB node selects the MN or SN as the F1 termination host.
  • the default upstream BAP route ID field or bap-Config is included in the RRC reconfiguration message transmitted through SRB3, or the default uplink BAP route ID field or bap-Config is included in the multi-radio access technology dual connectivity secondary cell group Information element (mrdc-SecondaryCellGroup IE), then the default upstream BAP route ID field or bap-Config is configured by the secondary node (SN). If the default upstream BAP route ID field or bap-Config is included in the RRC reconfiguration message transmitted through SRB1 and is not included in the mrdc-SecondaryCellGroup IE, then the default upstream BAP route ID field or bap-Config is configured by the master node (MN) configuration.
  • MN master node
  • the RRC reconfiguration message will configure the default upstream BH RLC for the F1-C and non-F1 traffic of the IAB node.
  • Channel (defaultUL-BH-RLC-Channel). This default upstream BH RLC channel can be configured or reconfigured when the IP address corresponding to the F1-C related traffic of the IAB node changes, and when the new IP address is anchored in a different IAB-donor-DU.
  • the link of the BH RLC channel needs to be specified, which is the uplink parent node link, which is also equivalent to the cell group.
  • the default uplink BH RLC channel points to the RLC channel on the SCG (secondary cell group, secondary cell group), otherwise, points to the MCG (master cell group, RLC (radio link control) channel on the primary cell group).
  • the parent node of an IAB node can belong to different IAB-donor-CUs, that is, the boundary IAB node can have two IAB-donor-CUs. Both MN (master node) and SN (secondary node) can be used as F1 termination host nodes. If the IAB node establishes the NR-DC before the F1-C connection is established, the IAB node can implicitly derive that the MN or SN is the F1 termination host, for example based on the entity providing the default BAP configuration. In this case, the Rel-16 designation method does not apply, because in the Rel-17 NR-DC scenario, the default uplink BH RLC channel can also point to the SCG. That is, if IAB-MT works in addition to the EN-DC scenario, the default uplink BH RLC channel can point to the RLC channel of MCG or SCG.
  • the configuration of the defaultUL-BH-RLC-Channel must be based on the configuration. Channel to select the egress link. Therefore, the ambiguity of the default uplink BH RLC channel leads to ambiguity in egress link selection, and further specification of topology information or cell group information is required.
  • an embodiment of the second aspect of the present application provides a method of configuring information. This method applies to IAB nodes.
  • Figure 5 is a schematic diagram of a method for configuring information according to the embodiment of the second aspect. As shown in Figure 5, the method includes:
  • Operation 501 Receive an RRC reconfiguration message, where the RRC reconfiguration message indicates relevant information about the topology to which the default uplink BH RLC channel configured for the IAB node belongs.
  • the IAB node does not operate in EN-DC.
  • the IAB node may be a boundary IAB node, for example, IAB node 3 shown in Figure 2 or Figure 3 .
  • the IAB node of this application is not limited to this, and the IAB node can also be of other types.
  • the topology-related information may refer to: topology information and/or cell group information.
  • the topology includes F1 termination topology or non-F1 termination topology.
  • the cell group information includes primary cell group/secondary cell group (MCG/SCG) information.
  • the RRC reconfiguration message may have second indication information, the second indication information is used to indicate that the topology to which the default uplink BH RLC channel belongs is an F1 terminated topology or a non-F1 terminated topology, or, The second indication information is used to indicate that the default uplink BH RLC channel points to the RLC channel on the primary cell group (MCG) or the RLC channel on the secondary cell group (SCG).
  • the second indication information may be necessary for a dual-connection node, an NR-DC node, or a border IAB node.
  • the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) may point to the RLC channel of the MCG or point to the RLC channel of the SCG.
  • the default uplink BH RLC channel may be configured by field (defaultUL-BH-RLC-Channel) or the host central unit (donor-CU) configured with bap-Config containing the default uplink BH RLC channel field indicates the cell group pointed to by the default uplink BH RLC channel. Therefore, relevant information about the topology to which the default uplink BH RLC channel belongs can be indicated implicitly.
  • the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) is configured by the MN or a bap-Config containing the default uplink BH RLC channel field is configured, then the default The uplink BH RLC channel points to the RLC channel on the MCG; if the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) is configured by the SN or the bap-Config containing the default uplink BH RLC channel field is configured, then The default upstream BH RLC channel points to the RLC channel on the SCG. That is to say, for an IAB node (for example, a border IAB node), the default upstream BH RLC channel points to the RLC channel on the backhaul link configured by the donor-CU configuring this field.
  • IAB node for example, a border IAB node
  • the RRC standard can be enhanced in TS 38.331.
  • the enhancements shown in Table 4 can be made in the defaultUL-BH-RLC-Channel field in the bap-Config IE of the RRC reconfiguration information.
  • the default upstream BH RLC channel field or bap-Config is included in the RRC reconfiguration message transmitted through SRB1 and is not included in the multi-radio access technology dual connectivity secondary cell group information element ( mrdc-SecondaryCellGroup IE), then the default upstream BH RLC channel field or bap-Config is configured by the master node (MN); if the default upstream BH RLC channel field or bap-Config is included in the RRC reconfiguration transmitted through SRB3 message, or the default upstream BH RLC channel field or bap-Config is included in the mrdc-SecondaryCellGroup IE, then the default upstream BH RLC channel field or bap-Config is configured by the secondary node (SN).
  • MN master node
  • the default upstream BH RLC channel field or bap-Config is included in the RRC reconfiguration transmitted through SRB3 message, or the default upstream BH RLC channel field or bap-Config is included in the
  • the IAB node when routing at the BAP sublayer, if the return route configuration is not configured or reconfigured by the F1 Application Protocol (F1AP) after the default upstream BH RLC channel was last configured or reconfigured by RRC , then, the IAB node selects the egress link based on the cell group corresponding to the default uplink BH RLC channel.
  • F1AP F1 Application Protocol
  • the relevant information of the topology to which the default uplink BH RLC channel configured for the IAB node belongs can be indicated.
  • the descendant nodes of the border node can use the same inter-host (or inter-CU) topology adaptation process. For example, after the IAB-MT of the border node is migrated to donor-CU2, or after an RRC is established with donor-CU2, the IAB-DU of the border node still maintains an F1 connection with donor-CU1, and the descendant node (such as IAB node 4) still maintains an F1 connection. The RRC connection and F1 connection are maintained with donor-CU1.
  • donor-CU2 Since the descendant node of the border node needs to migrate the transport path of the F1 connection to a non-F1 termination topology, donor-CU2 needs to provide the descendant node with a new TNL (transport network layer) address, which is an IP address, according to the request of donor-CU1. These one or more new TNL addresses are anchored to the donor-DU in the topology of donor-CU2, such as donor-DU2. Donor-CU2 sends these new TNL addresses to donor-CU1 through XnAP messages, such as IAB Transport Migration Management Response messages. Donor-CU2 also provides layer 2 information under the topology to donor-CU1, such as the upstream BAP routing identifier, which contains the donor-DU in the topology, such as the BAP address of donor-DU2.
  • TNL transport network layer
  • Donor-CU1 configures the IP address of the descendant node through the RRCReconfiguration message.
  • the IP address is configured using the IAB-IP-AddressConfiguration IE in RRC reconfiguration, which includes the IP address, the purpose of the IP address, and the BAP address of the donor-DU corresponding to the IP address (iab-donor-DU-BAP-Address) fields.
  • the descendant node transmits uplink data from itself, it obtains the BAP address contained in the routing ID through the BAP routing ID configured for the data traffic.
  • This address is the BAP address of the destination donor-DU, and then in the IAB-IP- Find the IP address corresponding to the BAP address of the donor-DU in the AddressConfiguration configuration, and select this IP address as the IP address used for the traffic for uplink transmission.
  • the embodiment of the third aspect provides a method of configuring information, which method is applied to the IAB node.
  • Figure 6 is a schematic diagram of a method of configuring information according to the embodiment of the third aspect. As shown in Figure 6, the method includes:
  • Operation 601 Receive an RRC reconfiguration message, where the RRC reconfiguration message configures a first donor-DU BAP address for the IAB node, and the first donor-DU BAP address points to the host distributed unit (donor-DU2) under the second topology. ).
  • the IAB node may be a descendant node of the boundary IAB node, for example, the IAB node 4 shown in FIG. 2 or FIG. 3 .
  • the IAB node of this application is not limited to this, and the IAB node can also be of other types.
  • the second topology refers to a different topology than the topology to which the IAB node belongs.
  • the IAB node belongs to the F1-terminated topology of the border node, that is, the first topology, and the second topology is the non-F1-terminated topology of the border node.
  • the IP address configuration of the RRC reconfiguration message may include the first donor-DU BAP address.
  • the IAB node is configured with an upstream BAP routing ID, and the upstream BAP routing ID includes the first donor-DU BAP address.
  • the method further includes:
  • the IAB node selects an IP address based on the first donor-DU BAP address
  • Operation 603 The IAB node uses the selected IP address to perform uplink transmission via the second topology.
  • CU1 can allocate the first donor-DU BAP address to donor-DU2 within the topology of CU1.
  • the first donor-DU BAP address can be called pseudo (pseudo) )BAP address, or alias address.
  • CU1 can configure the upstream BAP route ID for the descendant node, including the first donor-DU BAP address indicating donor-DU2.
  • the BAP address for donor-DU2 in the IAB-IP-AddressConfiguration is also the first donor-DU2.
  • DU BAP address not the actual BAP address of donor-DU2 in the CU2 topology.
  • the BAP address of the IAB-donor-DU in the IP address configuration can be the first donor-DU BAP address, which points to the non-F1 termination of the border IAB node.
  • a certain IAB-donor-DU under the host CU for example, donor-DU2 in Figures 2 and 3).
  • the RRC standard can be enhanced in TS 38.331.
  • the iab-donor-DU-BAP-Address field in the IAB-IP-AddressConfiguration IE of the RRC reconfiguration information can be enhanced as shown in Table 5.
  • the IAB node when the IAB node receives the IAB IP address addition/modification list (iab-IP-AddressToAddModList) contained in the RRC reconfiguration message, it saves the IP address in the list and the IP address corresponding to the IP address.
  • the IP address can be an IPv4 or IPv6 address.
  • the purpose of the IP address can be F1-C, F1-U, non-F1 traffic, etc.
  • the embodiment of the third aspect when configuring an IP address for a border IAB node or a descendant node, it is possible to cope with the situation where the BAP address of the donor-DU is a pseudo address.
  • An embodiment of the fourth aspect of the present application provides a method of configuring information, which corresponds to the method of configuring information of the embodiment of the first aspect. This method is applied to the host central unit (CU), for example, donor-CU1 or donor-CU2 of Figure 2 or Figure 3.
  • CU host central unit
  • Figure 7 is a schematic diagram of a method for configuring information according to the embodiment of the fourth aspect. As shown in Figure 7, the method includes:
  • Operation 701 Send an RRC reconfiguration message, where the RRC reconfiguration message indicates relevant information about the topology to which the default upstream BAP route ID configured for the IAB node belongs.
  • the IAB node may be a boundary IAB node, for example, IAB node 3 shown in FIG. 2 or FIG. 3 .
  • the IAB node of this application is not limited to this, and the IAB node can also be of other types.
  • the topology-related information may refer to: topology information and/or cell group information.
  • the topology includes F1 termination topology or non-F1 termination topology.
  • the cell group information includes primary cell group/secondary cell group (MCG/SCG) information.
  • the RRC reconfiguration message may have first indication information, the first indication information being used to indicate the topology to which the default uplink BAP route ID belongs.
  • the first indication information is used to indicate whether the topology to which the default upstream BAP route ID belongs belongs to an F1 terminated topology or a non-F1 terminated topology.
  • the first indication information may be necessary only for the border IAB node.
  • the default uplink BAP routing ID (defaultUL-BAP-RoutingID) field may be configured or the backhaul adaptation protocol configuration (bap- Config)'s donor central unit (donor-CU) indicates the topology to which the default upstream BAP route ID belongs. Therefore, it is possible to implicitly indicate which topology the default upstream BAP route ID belongs to.
  • the default upstream BAP route ID field is configured by the F1 termination host or the bap-Config containing the default upstream BAP route ID field is configured, then the default upstream BAP route ID belongs to the F1 termination topology; if it is configured by a non-F1 If the termination host configures the default upstream BAP route ID field or configures bap-Config containing the default upstream BAP route ID field, then the default upstream BAP route ID belongs to a non-F1 termination topology.
  • An embodiment of the fifth aspect of the present application provides a method of configuring information, which corresponds to the method of configuring information of the embodiment of the second aspect. This method is applied to the host central unit (CU), for example, donor-CU1 or donor-CU2 shown in Figure 2 or Figure 3.
  • CU host central unit
  • Figure 8 is a schematic diagram of a method for configuring information according to the embodiment of the fifth aspect. As shown in Figure 8, the method includes:
  • Operation 801 Send an RRC reconfiguration message, where the RRC reconfiguration message indicates relevant information about the topology to which the default uplink BH RLC channel configured for the IAB node belongs.
  • the IAB node does not operate in EN-DC.
  • the IAB node may be a boundary IAB node, for example, IAB node 3 shown in Figure 2 or Figure 3 .
  • the IAB node of this application is not limited to this, and the IAB node can also be of other types.
  • the topology-related information may refer to: topology information and/or cell group information.
  • the topology includes F1 termination topology or non-F1 termination topology.
  • the cell group information includes primary cell group/secondary cell group (MCG/SCG) information.
  • the RRC reconfiguration message may have second indication information, the second indication information is used to indicate that the topology to which the default uplink BH RLC channel belongs is an F1 terminated topology or a non-F1 terminated topology, or, The second indication information is used to indicate that the default uplink BH RLC channel points to the RLC channel on the primary cell group (MCG) or the RLC channel on the secondary cell group (SCG).
  • the second indication information may be necessary for a dual-connection node, an NR-DC node, or a border IAB node.
  • the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) may point to the RLC channel of the MCG or point to the RLC channel of the SCG.
  • the default uplink BH RLC channel may be configured by field (defaultUL-BH-RLC-Channel) or the host central unit (donor-CU) configured with bap-Config containing the default uplink BH RLC channel field indicates the cell group pointed to by the default uplink BH RLC channel. Therefore, relevant information about the topology to which the default uplink BH RLC channel belongs can be indicated implicitly.
  • the host of configuring the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configuring the bap-Config containing the default uplink BH RLC channel field is the MN, then the The default uplink BH RLC channel points to the RLC channel on the MCG; if the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) is configured or the host of bap-Config that contains the default uplink BH RLC channel field is configured is SN, then the default upstream BH RLC channel points to the RLC channel on the SCG. That is to say, for an IAB node (for example, a border IAB node), the default upstream BH RLC channel points to the RLC channel on the backhaul link configured by the donor-CU configuring this field.
  • the default upstream BH RLC channel points to the RLC channel on the backhaul link configured by the donor-CU configuring this field.
  • the IAB node when routing at the BAP sublayer, if the return route configuration is not configured or reconfigured by the F1 Application Protocol (F1AP) after the default upstream BH RLC channel was last configured or reconfigured by RRC , then, the IAB node selects the egress link based on the cell group corresponding to the default uplink BH RLC channel.
  • F1AP F1 Application Protocol
  • the relevant information of the topology to which the default uplink BH RLC channel configured for the IAB node belongs can be indicated.
  • An embodiment of the sixth aspect provides a method of configuring information, which corresponds to the method of configuring information of the embodiment of the third aspect. This method is applied to a host central unit (CU), for example, donor-CU1 shown in Figure 2 or Figure 3.
  • CU host central unit
  • Figure 9 is a schematic diagram of a method of configuring information according to the embodiment of the sixth aspect. As shown in Figure 9, the method includes:
  • Operation 901 Send an RRC reconfiguration message, where the RRC reconfiguration message configures a first donor-DU BAP address for the IAB node, and the first donor-DU BAP address points to the host distributed unit (donor-DU2) under the second topology. ).
  • the IAB node may be a descendant node of the boundary IAB node, for example, the IAB node 4 shown in FIG. 2 or FIG. 3 .
  • the IAB node of this application is not limited to this, and the IAB node can also be of other types.
  • the second topology refers to a different topology than the topology to which the IAB node belongs.
  • the IAB node belongs to the F1-terminated topology of the border node
  • the second topology is the non-F1-terminated topology of the border node.
  • the IP address configuration of the RRC reconfiguration message may include the first donor-DU BAP address.
  • the CU may be configured with an upstream BAP routing ID for the IAB node, and the upstream BAP routing ID includes the first donor-DU BAP address.
  • donor-CU1 can allocate the first donor-DU BAP address to donor-DU2 within the topology of CU1.
  • the first donor-DU BAP address can be called a pseudo (pseudo) BAP address, or alias address.
  • CU1 can configure the upstream BAP route ID for the descendant node, including the first donor-DU BAP address indicating donor-DU2.
  • the BAP address for donor-DU2 in the IAB-IP-AddressConfiguration is also the first donor-DU2.
  • DU BAP address not the actual BAP address of donor-DU2 in the CU2 topology.
  • the BAP address of the IAB-donor-DU in the IP address configuration can be the first donor-DU BAP address, which points to the non-F1 termination of the border IAB node.
  • a certain IAB-donor-DU under the host CU for example, donor-DU2 in Figures 2 and 3).
  • the RRC reconfiguration message sent by the CU may include an IAB IP address addition/modification list (iab-IP-AddressToAddModList), which includes the IP address and the first donor-DU BAP corresponding to the IP address. address.
  • the IP address can be an IPv4 or IPv6 address.
  • the purpose of the IP address can be F1-C, F1-U, non-F1 traffic, etc.
  • An embodiment of the seventh aspect of the present application provides an apparatus for configuring information, which corresponds to the method of configuring information described in the embodiment of the first aspect. This device applies to IAB nodes.
  • Figure 10 is a schematic diagram of a device for configuring information according to the embodiment of the seventh aspect.
  • the device 1000 for configuring information includes:
  • the first receiving unit 1001 receives an RRC reconfiguration message, where the RRC reconfiguration message indicates relevant information about the topology to which the default uplink BAP route ID configured for the IAB node belongs.
  • the IAB node may be a boundary IAB node, for example, IAB node 3 shown in FIG. 2 or FIG. 3 .
  • the IAB node of this application is not limited to this, and the IAB node can also be of other types.
  • Topology-related information may refer to: topology information and/or cell group information.
  • the topology includes F1 termination topology or non-F1 termination topology.
  • the cell group information includes primary cell group/secondary cell group (MCG/SCG) information.
  • the RRC reconfiguration message may have first indication information, and the first indication information is used to indicate the topology to which the default uplink BAP route ID belongs.
  • the first indication information is used to indicate whether the topology to which the default upstream BAP route ID belongs belongs to an F1 terminated topology or a non-F1 terminated topology.
  • the first indication information may be necessary only for the border IAB node.
  • the home center may configure a default upstream BAP routing ID (defaultUL-BAP-RoutingID) field or configure a backhaul adaptation protocol configuration (bap-Config) containing the default upstream BAP routing ID field.
  • the unit indicates the topology to which the default upstream BAP route ID belongs. Therefore, it is possible to implicitly indicate which topology the default upstream BAP route ID belongs to.
  • the default upstream BAP route ID field is configured by the F1 termination host or the bap-Config containing the default upstream BAP route ID field is configured, then the default upstream BAP route ID belongs to the F1 termination topology; if it is configured by a non-F1 If the termination host configures the default upstream BAP route ID field or configures bap-Config containing the default upstream BAP route ID field, then the default upstream BAP route ID belongs to a non-F1 termination topology.
  • the configuration of the F1 termination host or the non-F1 termination host can be determined by whether the MN or SN is the F1 termination host.
  • the default upstream BAP route ID field or bap-Config containing the default upstream BAP route ID field is configured.
  • the IAB node selects the MN or SN as the F1 termination host.
  • the default upstream BAP route ID field or bap-Config is included in the RRC reconfiguration message transmitted through SRB3, or the default uplink BAP route ID field or bap-Config is included in the multi-radio access technology dual connectivity secondary cell group Information element (mrdc-SecondaryCellGroup IE), then the default upstream BAP route ID field or bap-Config is configured by the secondary node (SN). If the default upstream BAP route ID field or bap-Config is included in the RRC reconfiguration message transmitted through SRB1 and is not included in the mrdc-SecondaryCellGroup IE, then the default upstream BAP route ID field or bap-Config is configured by the master node (MN) configuration.
  • MN master node
  • An embodiment of the eighth aspect of the present application provides an apparatus for configuring information, which corresponds to the method of configuring information of the embodiment of the second aspect. This device applies to IAB nodes.
  • Figure 11 is a schematic diagram of a device for configuring information according to the embodiment of the eighth aspect. As shown in Figure 11, the device 1100 for configuring information includes:
  • the second receiving unit 1101 receives an RRC reconfiguration message, wherein the RRC reconfiguration message indicates relevant information about the topology to which the default uplink BH RLC channel configured for the IAB node belongs.
  • the IAB node does not operate in EN-DC.
  • the IAB node may be a boundary IAB node, for example, IAB node 3 shown in Figure 2 or Figure 3 .
  • the IAB node of this application is not limited to this, and the IAB node can also be of other types.
  • Topology-related information may refer to: topology information and/or cell group information.
  • the topology includes F1 termination topology or non-F1 termination topology.
  • the cell group information includes primary cell group/secondary cell group (MCG/SCG) information.
  • the RRC reconfiguration message may have second indication information, the second indication information is used to indicate that the topology to which the default uplink BH RLC channel belongs is an F1 terminated topology or a non-F1 terminated topology, or, the second indication The information is used to indicate that the default uplink BH RLC channel points to the RLC channel on the primary cell group (MCG) or the RLC channel on the secondary cell group (SCG).
  • the second indication information may be necessary for a dual-connection node, an NR-DC node, or a border IAB node.
  • the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) can point to the RLC channel of the MCG or the RLC channel of the SCG, and can be configured by configuring the default uplink BH RLC channel field (defaultUL -BH-RLC-Channel) or the donor central unit (donor-CU) configured with bap-Config containing the default uplink BH RLC channel field indicates the cell group pointed to by the default uplink BH RLC channel. Therefore, relevant information about the topology to which the default uplink BH RLC channel belongs can be indicated implicitly.
  • the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) is configured by the MN or a bap-Config containing the default uplink BH RLC channel field is configured, then the default The uplink BH RLC channel points to the RLC channel on the MCG; if the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) is configured by the SN or the bap-Config containing the default uplink BH RLC channel field is configured, then The default upstream BH RLC channel points to the RLC channel on the SCG. That is to say, for an IAB node (for example, a border IAB node), the default upstream BH RLC channel points to the RLC channel on the backhaul link configured by the donor-CU configuring this field.
  • IAB node for example, a border IAB node
  • the default BH RLC channel field or bap-Config is included in the RRC reconfiguration message transmitted through SRB1 and is not included in the multi-radio access technology dual connectivity secondary cell group information element (mrdc -SecondaryCellGroup IE), then the default BH RLC channel field or bap-Config is configured by the master node (MN); if the default upstream BH RLC channel field or bap-Config is included in the RRC reconfiguration message transmitted through SRB3 , or the default upstream BH RLC channel field or bap-Config is included in the mrdc-SecondaryCellGroup IE, then the default upstream BH RLC channel field or bap-Config is configured by the secondary node (SN).
  • MN master node
  • the default upstream BH RLC channel field or bap-Config is included in the RRC reconfiguration message transmitted through SRB3 , or the default upstream BH RLC channel field or bap-Config is included in the m
  • the IAB node when routing at the BAP sublayer, if the return route configuration is not configured or reconfigured by the F1 Application Protocol (F1AP) after the default upstream BH RLC channel was last configured or reconfigured by RRC , then, the IAB node selects the egress link based on the cell group corresponding to the default uplink BH RLC channel.
  • F1AP F1 Application Protocol
  • the relevant information of the topology to which the default uplink BH RLC channel configured for the IAB node belongs can be indicated.
  • An embodiment of the ninth aspect provides an apparatus for configuring information, which corresponds to the method of configuring information of the embodiment of the third aspect. This device applies to IAB nodes.
  • Figure 12 is a schematic diagram of a device for configuring information according to the embodiment of the ninth aspect. As shown in Figure 12, the device for configuring information includes:
  • the third receiving unit 1201 receives the RRC reconfiguration message, wherein the RRC reconfiguration message configures the first donor-DU BAP address for the IAB node, and the first donor-DU BAP address points to the host distributed unit under the second topology. (donor-DU2).
  • the IAB node may be a descendant node of the boundary IAB node, for example, the IAB node 4 shown in FIG. 2 or FIG. 3 .
  • the IAB node of this application is not limited to this, and the IAB node can also be of other types.
  • the second topology refers to a different topology than the topology to which the IAB node belongs.
  • the IAB node belongs to the F1-terminated topology of the border node
  • the second topology is the non-F1-terminated topology of the border node.
  • the IP address configuration of the RRC reconfiguration message may include the first donor-DU BAP address.
  • the IAB node is configured with an upstream BAP routing ID, and the upstream BAP routing ID contains the first donor-DU BAP address.
  • the third receiving unit 1201 also performs the following operations:
  • the selected IP address is used for upstream transmission via the second topology.
  • CU1 can allocate the first donor-DU BAP address to donor-DU2 within the topology of CU1.
  • the first donor-DU BAP address can be called pseudo (pseudo) )BAP address, or alias address.
  • CU1 can configure the upstream BAP route ID for the descendant node, including the first donor-DU BAP address indicating donor-DU2.
  • the BAP address for donor-DU2 in the IAB-IP-AddressConfiguration is also the first donor-DU2.
  • DU BAP address not the actual BAP address of donor-DU2 in the CU2 topology.
  • the BAP address of the IAB-donor-DU in the IP address configuration can be the first donor-DU BAP address, which points to the non-F1 termination of the border IAB node.
  • a certain IAB-donor-DU under the host CU for example, donor-DU2 in Figures 2 and 3).
  • the IAB node when the IAB node receives the IAB IP address addition/modification list (iab-IP-AddressToAddModList) contained in the RRC reconfiguration message, it saves the IP address in the list and the IP address corresponding to the IP address.
  • the IP address can be an IPv4 or IPv6 address.
  • the purpose of the IP address can be F1-C, F1-U, non-F1 traffic, etc.
  • the embodiment of the ninth aspect when configuring an IP address for a border IAB node or a descendant node, it is possible to cope with the situation where the BAP address of the donor-DU is a pseudo address.
  • An embodiment of the tenth aspect of the present application provides a method of configuring information, which corresponds to the method of configuring information of the embodiment of the fourth aspect. This method is applied to the host central unit (CU), for example, donor-CU1 or donor-CU2 of Figure 2 or Figure 3.
  • CU host central unit
  • Figure 13 is a schematic diagram of a device for configuring information according to the embodiment of the tenth aspect. As shown in Figure 13, the device 1300 includes:
  • the first sending unit 1301 sends an RRC reconfiguration message, where the RRC reconfiguration message indicates relevant information about the topology to which the default uplink BAP route ID configured for the IAB node belongs.
  • the IAB node may be a boundary IAB node, for example, IAB node 3 shown in FIG. 2 or FIG. 3 .
  • the IAB node of this application is not limited to this, and the IAB node can also be of other types.
  • Topology-related information may refer to: topology information and/or cell group information.
  • the topology includes F1 termination topology or non-F1 termination topology.
  • the cell group information includes primary cell group/secondary cell group (MCG/SCG) information.
  • the RRC reconfiguration message may have first indication information, and the first indication information is used to indicate the topology to which the default uplink BAP route ID belongs.
  • the first indication information is used to indicate whether the topology to which the default upstream BAP route ID belongs belongs to an F1 terminated topology or a non-F1 terminated topology.
  • the first indication information may be necessary only for the border IAB node.
  • the home center may configure a default upstream BAP routing ID (defaultUL-BAP-RoutingID) field or configure a backhaul adaptation protocol configuration (bap-Config) containing the default upstream BAP routing ID field.
  • the unit indicates the topology to which the default upstream BAP route ID belongs. Therefore, it is possible to implicitly indicate which topology the default upstream BAP route ID belongs to.
  • the default upstream BAP route ID field is configured by the F1 termination host or the bap-Config containing the default upstream BAP route ID field is configured, then the default upstream BAP route ID belongs to the F1 termination topology; if it is configured by a non-F1 If the termination host configures the default upstream BAP route ID field or configures bap-Config containing the default upstream BAP route ID field, then the default upstream BAP route ID belongs to a non-F1 termination topology.
  • An embodiment of the eleventh aspect of the present application provides an apparatus for configuring information, which corresponds to the method of configuring information of the embodiment of the fifth aspect.
  • This method is applied to the host central unit (CU), for example, donor-CU1 or donor-CU2 shown in Figure 2 or Figure 3.
  • CU host central unit
  • Figure 14 is a schematic diagram of a device for configuring information according to the embodiment of the eleventh aspect. As shown in Figure 14, the device 1400 includes:
  • the second sending unit 1401 sends an RRC reconfiguration message, where the RRC reconfiguration message indicates relevant information about the topology to which the default uplink BH RLC channel configured for the IAB node belongs.
  • the IAB node does not operate in EN-DC.
  • the IAB node may be a boundary IAB node, for example, IAB node 3 shown in Figure 2 or Figure 3 .
  • the IAB node of this application is not limited to this, and the IAB node can also be of other types.
  • Topology-related information may refer to: topology information and/or cell group information.
  • the topology includes F1 termination topology or non-F1 termination topology.
  • the cell group information includes primary cell group/secondary cell group (MCG/SCG) information.
  • the RRC reconfiguration message may have second indication information, the second indication information is used to indicate that the topology to which the default uplink BH RLC channel belongs is an F1 terminated topology or a non-F1 terminated topology, or, the second indication The information is used to indicate that the default uplink BH RLC channel points to the RLC channel on the primary cell group (MCG) or the RLC channel on the secondary cell group (SCG).
  • the second indication information may be necessary for a dual-connection node, an NR-DC node, or a border IAB node.
  • the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) can point to the RLC channel of the MCG or the RLC channel of the SCG, and can be configured by configuring the default uplink BH RLC channel field (defaultUL -BH-RLC-Channel) or the donor central unit (donor-CU) configured with bap-Config containing the default uplink BH RLC channel field indicates the cell group pointed to by the default uplink BH RLC channel. Therefore, relevant information about the topology to which the default uplink BH RLC channel belongs can be indicated implicitly.
  • the host of configuring the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configuring the bap-Config containing the default uplink BH RLC channel field is the MN, then the The default uplink BH RLC channel points to the RLC channel on the MCG; if the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) is configured or the host of bap-Config that contains the default uplink BH RLC channel field is configured is SN, then the default upstream BH RLC channel points to the RLC channel on the SCG. That is to say, for an IAB node (for example, a border IAB node), the default upstream BH RLC channel points to the RLC channel on the backhaul link configured by the donor-CU configuring this field.
  • the default upstream BH RLC channel points to the RLC channel on the backhaul link configured by the donor-CU configuring this field.
  • the IAB node when routing at the BAP sublayer, if the return route configuration is not configured or reconfigured by the F1 Application Protocol (F1AP) after the default upstream BH RLC channel was last configured or reconfigured by RRC , then, the IAB node selects the egress link based on the cell group corresponding to the default uplink BH RLC channel.
  • F1AP F1 Application Protocol
  • the relevant information of the topology to which the default uplink BH RLC channel configured for the IAB node belongs can be indicated.
  • An embodiment of the twelfth aspect provides an apparatus for configuring information, which corresponds to the method of configuring information of the embodiment of the sixth aspect.
  • the device is applied to a host central unit (CU), for example, donor-CU1 shown in Figure 2 or Figure 3.
  • CU host central unit
  • Figure 15 is a schematic diagram of a method of configuring information according to the embodiment of the twelfth aspect. As shown in Figure 15, the device 1500 includes:
  • the third sending unit 1501 sends an RRC reconfiguration message, where the RRC reconfiguration message configures the first donor-DU BAP address for the IAB node, and the first donor-DU BAP address points to the host distributed unit under the second topology. (donor-DU2).
  • the IAB node may be a descendant node of the boundary IAB node, for example, the IAB node 4 shown in FIG. 2 or FIG. 3 .
  • the IAB node of this application is not limited to this, and the IAB node can also be of other types.
  • the second topology refers to a different topology than the topology to which the IAB node belongs.
  • the IAB node belongs to the F1-terminated topology of the border node
  • the second topology is the non-F1-terminated topology of the border node.
  • the IP address configuration of the RRC reconfiguration message may include the first donor-DU BAP address.
  • the CU may be configured with an upstream BAP routing ID for the IAB node, and the upstream BAP routing ID includes the first donor-DU BAP address.
  • donor-CU1 can allocate the first donor-DU BAP address to donor-DU2 within the topology of CU1.
  • the first donor-DU BAP address can be called Pseudo BAP address, or alias address.
  • CU1 can configure the upstream BAP route ID for the descendant node, including the first donor-DU BAP address indicating donor-DU2.
  • the BAP address for donor-DU2 in the IAB-IP-AddressConfiguration is also the first donor-DU2.
  • DU BAP address not the actual BAP address of donor-DU2 in the CU2 topology.
  • the BAP address of the IAB-donor-DU in the IP address configuration can be the first donor-DU BAP address, which points to the non-F1 termination of the border IAB node.
  • a certain IAB-donor-DU under the host CU for example, donor-DU2 in Figures 2 and 3).
  • the RRC reconfiguration message sent by the CU may include an IAB IP address addition/modification list (iab-IP-AddressToAddModList), which includes the IP address and the first donor-DU BAP corresponding to the IP address. address.
  • the IP address can be an IPv4 or IPv6 address.
  • the purpose of the IP address can be F1-C, F1-U, non-F1 traffic, etc.
  • the embodiment of the present application also provides a communication system, which may include an IAB node and a base station CU. At least one of the MT of the IAB node, the DU of the IAB node, and the base station CU may have the composition of the electronic device shown in FIG. 16 .
  • Figure 16 is a schematic diagram of the composition of an electronic device according to an embodiment of the present application.
  • the electronic device 1600 may include a processor 1610 (eg, a central processing unit CPU) and a memory 1620 ; the memory 1620 is coupled to the processor 1610 .
  • the memory 1620 can store various data; in addition, it also stores an information processing program 1630, and the program 1630 is executed under the control of the processor 1610.
  • the processor 1610 may be configured to execute a program to implement the methods in the embodiments of the first to sixth aspects.
  • the electronic device 1600 may also include: a transceiver 1640, an antenna 1650, etc.; the functions of the above components are similar to those of the existing technology, and will not be described again here. It is worth noting that the electronic device 1600 does not necessarily include all components shown in FIG. 16 ; in addition, the electronic device 1600 may also include components not shown in FIG. 16 , and reference may be made to the prior art.
  • An embodiment of the present application also provides a computer program, wherein when the program is executed in an IAB node, the program causes the IAB node to execute the method described in the embodiments of the first to third aspects.
  • An embodiment of the present application also provides a computer program, wherein when the program is executed in a CU node, the program causes the CU to execute the method described in the embodiments of the fourth to sixth aspects.
  • Embodiments of the present application also provide a storage medium storing a computer program, wherein the computer program causes an electronic device to perform the method described in the embodiments of the first to sixth aspects.
  • the above devices and methods of this application can be implemented by hardware, or can be implemented by hardware combined with software.
  • the present application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or component described above, or enables the logic component to implement the various methods described above or steps.
  • This application also involves storage media used to store the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memories, etc.
  • the methods/devices described in connection with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of both.
  • one or more of the functional block diagrams and/or one or more combinations of the functional block diagrams shown in the figure may correspond to each software module of the computer program flow, or may correspond to each hardware module.
  • These software modules can respectively correspond to the various steps shown in the figure.
  • These hardware modules can be implemented by solidifying these software modules using a field programmable gate array (FPGA), for example.
  • FPGA field programmable gate array
  • the software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
  • a storage medium may be coupled to the processor such 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 storage media may be located in an ASIC.
  • the software module can be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or the large-capacity flash memory device.
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described in the accompanying drawings may be implemented as a general-purpose processor or a digital signal processor (DSP) for performing the functions described in this application. ), 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.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, or multiple microprocessors. processor, one or more microprocessors combined with DSP communications, or any other such configuration.
  • a method of configuring information, applied to IAB nodes, the method includes:
  • RRC reconfiguration message indicates relevant information about the topology to which the default upstream BAP route ID configured for the IAB node belongs.
  • the topology includes an F1 terminated topology or a non-F1 terminated topology.
  • the RRC reconfiguration message has first indication information, and the first indication information is used to indicate the topology to which the default uplink BAP route ID belongs.
  • the host central unit that configures the default upstream BAP routing ID field (defaultUL-BAP-RoutingID) or configures the bap-Config containing the default upstream BAP routing ID field indicates that the default upstream BAP routing ID belongs to topology.
  • the F1 termination host configures the default upstream BAP route ID field or configures bap-Config containing the default upstream BAP route ID field, then the default upstream BAP route ID belongs to the F1 termination topology.
  • the default upstream BAP route ID field is configured by a non-F1 termination host or a bap-Config containing the default upstream BAP route ID field is configured, then the default upstream BAP route ID belongs to the non-F1 termination topology.
  • the default upstream BAP route ID field configured as the F1 termination host or the non-F1 termination host is determined by whether the MN or the SN is the F1 termination host or the bap-Config containing the default upstream BAP route ID field is configured.
  • the MN is the F1 termination host; if the IAB node establishes the NR-DC before establishing the F1-C, then the IAB node selects the MN or SN as the F1 termination host. Host.
  • the default upstream BAP route ID field or bap-Config is included in the RRC reconfiguration message transmitted through SRB3, or the default upstream BAP route ID field or bap-Config is included in the mrdc-SecondaryCellGroup IE, then the The above default upstream BAP route ID field or bap-Config is configured by the secondary node (SN).
  • the default upstream BAP route ID field or bap-Config is included in the RRC reconfiguration message transmitted through SRB1 and is not included in the mrdc-SecondaryCellGroup IE, then the default upstream BAP route ID field or bap-Config Configured by the master node (MN).
  • the IAB node is a boundary IAB node.
  • a method of configuring information, applied to IAB nodes, the method includes:
  • RRC reconfiguration message indicates relevant information about the topology to which the default uplink BH RLC channel configured for the IAB node belongs.
  • the RRC reconfiguration message has second indication information
  • the second indication information is used to indicate that the topology to which the default uplink BH RLC channel belongs is an F1 terminated topology or a non-F1 terminated topology, or the second indication information is used to indicate that the default uplink BH RLC channel Points to the RLC channel on the primary cell group or the RLC channel on the secondary cell group.
  • the configured default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) points to the RLC channel of the MCG or the RLC channel of the SCG.
  • the default uplink BH RLC is indicated by the host central unit (donor-CU) that configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures the bap-Config containing the default uplink BH RLC channel field.
  • default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) is configured by the MN or the bap-Config containing the default uplink BH RLC channel field is configured, then the default uplink BH RLC channel points to the MCG RLC channel.
  • default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) is configured by the SN or the bap-Config containing the default uplink BH RLC channel field is configured, then the default uplink BH RLC channel points to the SCG RLC channel.
  • the default upstream BH RLC channel field or bap-Config is included in the RRC reconfiguration message transmitted through SRB3, or the default upstream BH RLC channel field or bap-Config is included in the mrdc-SecondaryCellGroup IE, then the The default upstream BH RLC channel field or bap-Config is configured by the secondary node (SN).
  • the default BH RLC channel field or bap-Config is included in the RRC reconfiguration message transmitted through SRB1 and is not included in the mrdc-SecondaryCellGroup IE, then the default BH RLC channel field or bap-Config is determined by the master Node (MN) configuration.
  • MN master Node
  • the IAB node does not work on EN-DC.
  • the IAB node is a boundary IAB node.
  • a method of configuring information, applied to IAB nodes, the method includes:
  • RRC reconfiguration message configures a first donor-DU BAP address for the IAB node, and the first donor-DU BAP address points to the host distributed unit (DU2) under the second topology.
  • the IP address configuration of the RRC reconfiguration message includes the first donor-DU BAP address.
  • the IAB node When the IAB node receives the IAB IP address addition/modification list (iab-IP-AddressToAddModList) contained in the RRC reconfiguration message, it saves the IP addresses in the list and all the IP addresses corresponding to the IP addresses. Describe the first donor-DU BAP address.
  • the IAB node is configured with an upstream BAP routing ID, and the upstream BAP routing ID includes the first donor-DU BAP address.
  • the IAB node selects an IP address based on the first donor-DU BAP address
  • the selected IP address is used for upstream transmission via the second topology.
  • the IAB node is a descendant node of the boundary IAB node.
  • the second topology is the non-F1 terminated topology of the border IAB node.
  • a method of configuring information, applied to a host central unit (CU), the method includes:
  • RRC reconfiguration message indicates relevant information about the topology to which the default upstream BAP route ID configured for the IAB node belongs.
  • the topology includes an F1 terminated topology or a non-F1 terminated topology.
  • the RRC reconfiguration message has first indication information, and the first indication information is used to indicate the topology to which the default uplink BAP route ID belongs.
  • the host central unit that configures the default upstream BAP routing ID field (defaultUL-BAP-RoutingID) or configures the bap-Config containing the default upstream BAP routing ID field indicates that the default upstream BAP routing ID belongs to topology.
  • the default upstream BAP route ID field is configured by the CU serving as the F1 termination host or the bap-Config containing the default upstream BAP route ID field is configured, then the default upstream BAP route ID belongs to the F1 termination topology.
  • the default upstream BAP route ID field is configured by the CU as the non-F1 termination host or the bap-Config containing the default upstream BAP route ID field is configured, then the default upstream BAP route ID belongs to the non-F1 termination topology. .
  • the IAB node is a boundary IAB node.
  • RRC reconfiguration message indicates relevant information about the topology to which the default uplink BH RLC channel configured for the IAB node belongs.
  • the RRC reconfiguration message has second indication information
  • the second indication information is used to indicate that the topology to which the default uplink BH RLC channel belongs is an F1 terminated topology or a non-F1 terminated topology, or the second indication information is used to indicate that the default uplink BH RLC channel Points to the RLC channel on the primary cell group or the RLC channel on the secondary cell group.
  • the configured default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) points to the RLC channel of the MCG or the RLC channel of the SCG.
  • the default uplink BH RLC is indicated by the host central unit (donor-CU) that configures the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) or configures the bap-Config containing the default uplink BH RLC channel field.
  • the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) is configured by the CU as the MN or the bap-Config containing the default uplink BH RLC channel field is configured, then the default uplink BH RLC The channel points to the RLC channel on the MCG.
  • the default uplink BH RLC channel field (defaultUL-BH-RLC-Channel) is configured by the CU as the SN or the bap-Config containing the default uplink BH RLC channel field is configured, then the default uplink BH RLC The channel points to the RLC channel on the SCG.
  • the IAB node does not work on EN-DC.
  • the return routing configuration is configured based on the missing Save the cell group corresponding to the uplink BH RLC channel to select the egress link.
  • the IAB node is a boundary IAB node.
  • RRC reconfiguration message configures a first donor-DU BAP address for the IAB node, and the first donor-DU BAP address points to the host distributed unit (DU2) under the second topology.
  • the IP address configuration of the RRC reconfiguration message includes the first donor-DU BAP address.
  • the CU sends an IAB IP address addition/modification list (iab-IP-AddressToAddModList), which includes an IP address and the first donor-DU BAP address corresponding to the IP address.
  • IAB IP address addition/modification list (iab-IP-AddressToAddModList), which includes an IP address and the first donor-DU BAP address corresponding to the IP address.
  • the CU configures an upstream BAP routing ID for the IAB node, and the upstream BAP routing ID includes the first donor-DU BAP address.
  • the IAB node is a descendant node of the boundary IAB node.
  • the second topology is the non-F1 terminated topology of the border IAB node.

Landscapes

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

Abstract

本申请实施例提供一种配置信息的方法、装置和通信系统，该配置信息的装置应用于IAB节点，该装置包括：第一接收单元，其接收RRC重配置消息，该RRC重配置消息指示为所述IAB节点配置的缺省上行BAP路由ID所属于的拓扑的相关信息。

Description

配置信息的方法、装置和通信系统 技术领域
本申请实施例涉及通信技术领域。
背景技术
集成的接入和回传(Integrated access and backhaul，IAB)又称接入回传一体化在下一代无线接入网络(NG-RAN：next generation radio access network)中实现了无线中继的功能。集成的接入和回传节点(IAB-node)支持通过新无线(New Radio，NR)的接入和回传。NR回传在网络侧中终止点被称为IAB-donor，它表示一个具有支持IAB功能的网络设备(例如，gNB)。
IAB-node可以通过一跳或者多跳来连接到一个IAB宿主(IAB-donor)。这些多跳连接形成了一个以IAB宿主为根节点的有向无环图(DAG，Directed Acyclic Graph)拓扑结构。IAB宿主负责执行IAB网络拓扑中集中式的资源管理、拓扑管理和路由管理。
IAB-node支持gNB-DU(distributed unit，分布式单元)的功能，IAB-node DU也被称为IAB-DU，IAB-DU是到终端设备(UE)和下一跳IAB-node的无线接入(NR access)接口的终点，也是到IAB-donor上的gNB-CU(central unit，中心单元)的F1协议的终点。IAB-DU可以服务普通的UE和IAB子节点。IAB-DU实现网络侧设备功能，连接到下游的child IAB-node，对UE以及下游child IAB-node提供NR空口接入并与IAB donor-CU之间建立有F1连接。
除了gNB-DU功能，IAB-node也支持一部分UE的功能，被称为IAB-MT(Mobile Termination)，IAB-MT包括比如物理层、层2、RRC和NAS功能来连接到另一个IAB-node或IAB-donor的gNB-DU、连接到IAB-donor上的gNB-CU和连接到核心网。IAB-MT可支持如UE物理层、接入(access stratum，AS)、无线资源控制(radio resource control，RRC)层和非接入(non-access stratum，NAS)层功能，可以连接到IAB父节点。
IAB-donor是网络侧的终结节点，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引入了回传适配协议(Backhaul Adaptation Protocol，BAP)子层。BAP子层位于无线链路控制(RLC)子层之上、IP层之下，支持数据包目的节点及路径选择、数据包路由转发、承载映射、流控反馈、回传链路失败通知等功能。
图1是IAB父子节点关系的一个示意图。如图1所示，在IAB父子节点关系结构10中，IAB-node 100包括IAB-MT功能单元101和IAB-DU功能单元102，IAB-DU功能单元102的接口上的邻节点被称为子节点(child node)，如图1中所示的子节点201、202、203，IAB-DU功能单元102与子节点201、202、203之间可以通过空中接口(Uu)进行通信；IAB-MT功能单元101的接口上的邻节点被称为父节点(parent node)，如图1中所示的父节点301、302，IAB-MT功能单元101与父节点301、302之间可以通过空中接口(Uu)进行通信。
如图1所示，IAB-node 100到子节点201、202、203的方向被称为下游(downstream)方向，IAB-node 100到父节点301、302的方向被称为上游(upstream)方向。IAB-donor(未图示)为该IAB拓扑结构10执行集中式的资源、拓扑和路由管理。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
在多跳场景下，为了实现数据包的中继转发，IAB节点需要确定数据包到达的目标节点，然后根据路由表确定到达目标节点对应的下一跳节点并发送。由donor-CU通过F1AP(F1 application protocol)信令为IAB节点配置从IAB节点发起的上行每个F1-U Tunnel、非用户设备关联的(Non-UE associated)F1AP消息、用户设备关联的(UE-associated)F1AP消息、非F1流量(Non-F1 Traffic)到BAP路由标识的映射。
IAB节点根据路由标识映射信息确定从IAB节点发起的不同类型上行IP包对应的BAP路由标识，并为这些上行IP包封装包含BAP路由标识信息的BAP子头。 Donor-CU通过F1AP信令为donor-DU配置不同类型的下行数据包到BAP路由标识的映射。Donor-DU根据路由标识映射信息确定收到的下行IP包对应的BAP路由标识，并为这些下行IP包封装包含BAP路由标识下行的BAP子头。
BAP路由标识包括目的BAP地址和从IAB节点到donor-DU之间的路径标识(path identity)。BAP地址在BAP报头中也被称为DESTINATION(目的地)。每个IAB节点及donor-DU都被配置了一个BAP地址。
在IAB节点启动(integration)时，RRC可以配置用于非F1-U流量的一个缺省的BH RLC信道和一个缺省的BAP路由标识。这些配置可以在拓扑适配(topology adaptation)的场景进行更新。
IAB节点可以有冗余的路径到不同IAB-donor-CU。对于在独立组网(Stand Alone，SA)模式下工作的IAB节点，可以通过NR-DC来允许IAB-MT和两个父节点同时具有回传链路，从而实现回传的路线冗余。两个父节点可以连接到不同的IAB-donor-CU，这些IAB-donor-CU可以控制经过该两个父节点的冗余路线的建立和释放。父节点的gNB-DU功能和对应的IAB-donor-CU一起获得了IAB-MT的主节点(MN)和/或辅节点(SN)的角色。NR-DC的框架(比如MCG/SCG相关的过程)被用来配置IAB节点到父节点的双无线连接。
图2是宿主间拓扑冗余(inter-donor topology redundancy，或者是inter-CU topology redundancy)网络结构的一个示意图。图3是宿主间部分迁移的一个示意图。
如图2所示，节点3被称为边界(boundary)IAB节点。边界IAB节点指其某个RRC接口和F1接口终结到不同的IAB-donor-CU。边界IAB节点适用于部分迁移、宿主间拓扑冗余和宿主间RLF(radio link failure，无线链路失败)恢复。如图2所示，节点3的DU终结到CU1，节点3的MT对CU1和CU2都有接口，因此符合边界IAB节点的定义。后裔(descendant)IAB节点指通过边界IAB节点接入到网络的节点，而且每个节点都是单连接到自己的父节点，比如IAB节点4是后裔节点。F1终结(F1-terminating)宿主节点指对边界IAB节点和后裔节点的F1接口进行终结的donor-CU，比如donor-CU1为F1终结节点，即，图2中的IAB-DU3和IAB-DU4的F1接口终结到donor-CU1。非F1终结(Non-F1-terminating)宿主节点指没有对边界IAB节点和后裔节点的F1接口进行终结、且具有宿主功能的CU，比如图2的donor-CU2。在图2所示的拓扑冗余场景中，边界节点(即，节点3)是双连接节点。 在宿主间拓扑冗余的场景，边界IAB节点(即，IAB节点3)以及后裔节点可以分别通过第一路径(First path)和第二路径(Second path)与CU1通信。
在图3中，边界IAB节点的IAB-MT(即，IAB-MT3)可以迁移到一个不同的IAB-donor-CU下面的父节点下(例如，迁移到Donor-CU2下面的父节点下)。在这种情况下，并置的IAB-DU(即，IAB-DU3)以及后裔节点的IAB-DU(例如，IAB-DU4)保持了和原来IAB-donor-CU(例如，Donor-CU1)的F1连接。这种迁移叫做宿主间部分迁移(inter-donor partial migration)。在宿主间部分迁移之后，边界IAB节点的IAB-DU和后裔节点的F1流量经由边界IAB节点的IAB-MT迁移到的IAB拓扑的BAP层进行路由。SA模式能够支持宿主间部分迁移。
当SA模式的IAB节点声明回传链路RLF时，其可以在不同IAB-donor-CU下面的父节点进行RLF恢复。和宿主间部分迁移一样，并置的IAB-DU以及后裔节点的IAB-DU可以保持和原来IAB-donor-CU的F1连接。
IAB节点3是边界IAB节点，IAB-MT3从单连接到父节点IAB节点1改变为单连接到父节点IAB节点2。IAB-DU3和其子节点IAB节点4都仍然和donor-CU1进行F1连接，但是这个F1连接经过的路径是通过IAB节点2最终到达donor-CU1的。在图3所示的宿主间部分迁移的场景中，边界节点(节点3)是迁移节点。宿主间部分迁移的场景也同样适用于部分RLF恢复。
本申请的发明人发现，边界IAB节点属于两个IAB拓扑，现有技术在为边界IAB节点配置缺省上行BAP路由ID和/或缺省上行BH RLC信道时，没有表明是哪个拓扑，例如：在配置缺省上行BH RLC信道时，没有考虑SN作为F1终结宿主的情况。此外，在为边界IAB节点或者其后裔节点配置IP地址时，也没有考虑对应的donor-DU的BAP地址为伪地址的情况。
本申请的实施例提供一种配置信息的方法、装置和通信系统，通过RRC重配置消息指示为IAB节点配置的缺省上行BH RLC信道和/或缺省上行BAP路由ID所属于的拓扑的相关信息。由此，能够表明为IAB节点配置的缺省上行BAP路由ID和/或缺省上行BH RLC信道属于哪个拓扑。
根据本申请实施例的一个方面，提供一种配置信息的装置，应用于IAB节点，该装置包括：
第一接收单元，其接收RRC重配置消息，其中，所述RRC重配置消息指示为所 述IAB节点配置的缺省上行BAP路由ID所属于的拓扑的相关信息。
根据本申请实施例的另一个方面，提供一种配置信息的装置，应用于IAB节点，该装置包括：
第二接收单元，其接收RRC重配置消息，其中，所述RRC重配置消息指示为所述IAB节点配置的缺省上行BH RLC信道所属于的拓扑的相关信息。
根据本申请实施例的另一个方面，提供一种配置信息的装置，应用于IAB节点，该装置包括：
第三接收单元，其接收RRC重配置消息，其中，所述RRC重配置消息为所述IAB节点配置第一donor-DU BAP地址，所述第一donor-DU BAP地址指向第二拓扑下的宿主分布式单元(DU2)。
本申请实施例的有益效果在于：能够表明为IAB节点配置的缺省上行BAP路由ID和/或缺省上行BH RLC信道属于哪个拓扑。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
图1是IAB父子节点关系的一个示意图；
图2是宿主间拓扑冗余网络结构的一个示意图；
图3是宿主间部分迁移的一个示意图；
图4是第一方面的实施例的配置信息的方法的一个示意图；
图5是第二方面的实施例的配置信息的方法的一个示意图；
图6是第三方面的实施例的配置信息的方法的一个示意图；
图7是第四方面的实施例的配置信息的方法的一个示意图；
图8是第五方面的实施例的配置信息的方法的一个示意图；
图9是第六方面的实施例的配置信息的方法的一个示意图；
图10是第七方面的实施例的配置信息的装置的一个示意图；
图11是第八方面的实施例的配置信息的装置的一个示意图；
图12是第九方面的实施例的配置信息的装置的一个示意图；
图13是第十方面的实施例的配置信息的装置的一个示意图；
图14是第十一方面的实施例的配置信息的装置的一个示意图；
图15是第十二方面的实施例的配置信息的方法的一个示意图；
图16是本申请实施例的电子设备的组成的一个示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如新无线(NR，New Radio)、长期演进(LTE，Long Term Evolution)、 增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：集成的接入和回传节点(IAB-node)、中继(relay)、基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femeto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment或Terminal Device)例如是指通过网络设备接入通信网络并接收网络服务的设备。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、移动终端(MT，mobile termination)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行 监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
此外，术语“网络侧”或“网络设备侧”是指网络的一侧，可以是某一基站，也可以包括如上的一个或多个网络设备。术语“用户侧”或“终端侧”或“终端设备侧”是指用户或终端的一侧，可以是某一UE，也可以包括如上的一个或多个终端设备。
在现有技术(例如TS38.331)中，RRC重配置消息中的关于配置缺省BAP路由ID和BH RLC信道的字段描述如表1所示。
表1
Figure PCTCN2022085090-appb-000001
在现有技术(例如TS38.331)中，RRC重配置消息中的IAB-IP-AddressConfiguration字段内容以及其中的iab-donor-DU-BAP-Address字段描述如表2所示。
表2
Figure PCTCN2022085090-appb-000002
Figure PCTCN2022085090-appb-000003
在本申请的各实施例中，高层信令例如可以是无线资源控制(RRC)信令；例如称为RRC消息(RRC message)，例如包括MIB、系统信息(system information)、专用RRC消息；或者称为RRC IE(RRC information element)。高层信令例如还可以是F1-C信令，或者叫F1AP协议。但本申请不限于此。
在本申请中，以多跳IAB网络部署场景为例，对各实施例进行说明，其中，多个终端设备(例如，UE)通过多跳的IAB节点，连接到IAB-donor，最后接入网络，该网络例如是5G网络。需要说明的是，本申请的各实施例可以不限于上述场景。
在本申请的各实施例中，IAB拓扑指通过回传链路进行互连以及F1接口和/或RRC终结到同一个IAB-donor-CU的所有IAB节点和IAB-donor-DU的组合。例如，在图2和图3中：Donor-DU1、IAB节点1、IAB节点3以及IAB节点4是由Donor-CU1管理的节点，它们与Donor-CU1组成的IAB拓扑网络称为第一拓扑；Donor-DU2、IAB节点2以及IAB节点3是由Donor-CU2管理的节点，它们与Donor-CU2组成的IAB拓扑网络称为第二拓扑。边界节点(即，IAB节点3)既属于第一拓扑也属于第二拓扑。
第一方面的实施例
在IAB节点的引导过程，迁移过程，或者是IAB-MT的RRC恢复以及IAB-MT的RRC重建过程中，RRC重配置消息会为IAB节点的F1-C以及非F1流量配置缺省的上行BAP路由ID(defaultUL-BAP-RoutingID)。这个缺省的上行BAP路由ID可以在IAB节点的F1-C相关流量对应的IP地址改变的时候进行配置或者重配置。
然而，在图2和图3的场景中，边界节点连接了不同IAB拓扑，在边界节点所用到的上行BAP路由标识中，可能会有分别通向两个IAB拓扑(也就是通向两个不同donor-CU下面的donor-DU)的BAP路由标识。因为不同IAB拓扑的BAP路由标识分别由各自的donor-CU来配置和管理，所以属于不同IAB拓扑的BAP路由标识可能会冲突。因此缺省的上行BAP路由ID具有模糊性，需要进一步指明拓扑的相关信息。
为了解决上述问题或类似问题，本申请第一方面的实施例提供一种配置信息的方法。该方法应用于IAB节点。
图4是第一方面的实施例的配置信息的方法的一个示意图，如图4所示，该方法包括：
操作401、接收RRC重配置消息，其中，该RRC重配置消息指示为IAB节点配置的缺省上行BAP路由ID所属于的拓扑的相关信息。
在第一方面的实施例中，该IAB节点可以是边界IAB节点，例如，图2或图3所示的IAB节点3。此外，本申请的IAB节点并不限于此，IAB节点也可以是其它的类型。
在操作401中，拓扑的相关信息可以指：拓扑的信息，和/或小区组(CG,cell group)的信息。其中，拓扑包括F1终结拓扑或非F1终结拓扑。小区组的信息包括主小区组/辅小区组(MCG/SCG)信息。
在至少一些实施例中，在操作401中，RRC重配置消息可以具有第一指示信息，该第一指示信息用于指示缺省上行BAP路由ID所属于的拓扑。例如，该第一指示信息用于指示缺省上行BAP路由ID所属于的拓扑是属于F1终结拓扑或非F1终结拓扑。该第一指示信息可以只对于边界IAB节点才是必须的。
在至少另一些实施例中，在操作401中，可以由配置缺省上行BAP路由ID(defaultUL-BAP-RoutingID)字段或者配置包含该缺省上行BAP路由ID字段的回传适应协议配置(bap-Config)的宿主中心单元(donor-CU)指示该缺省上行BAP路由ID所属于的拓扑。由此，能够通过隐式的方法指示该缺省上行BAP路由ID属于哪个拓扑。
其中，如果由F1终结宿主配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于F1终结拓扑；如果由非F1终结宿主配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于非F1终结拓扑。
例如，可以在TS 38.331中对RRC标准进行增强。具体地，RRC重配置信息的bap-Config IE中的defaultUL-BAP-RoutingID字段可以被修改为如下的表3所示的形式。
表3
Figure PCTCN2022085090-appb-000004
对于通过隐式的方法指示该缺省上行BAP路由ID属于哪个拓扑的方案，在一个具体的实施方式中，可以通过是MN还是SN是F1终结宿主来确定F1终结宿主还是非F1终结宿主配置的所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config。
例如，如果IAB节点在建立F1连接之后建立NR-DC，那么MN是F1终结宿主；如果IAB节点在建立F1-C之前建立了NR-DC，那么由IAB节点选择MN或者SN作为F1终结宿主。
如果缺省上行BAP路由ID字段或bap-Config包含在通过SRB3传输的RRC重配置消息中，或者所述缺省上行BAP路由ID字段或bap-Config包含在多无线电接入技术双连接辅小区组信息元素(mrdc-SecondaryCellGroup IE)中，那么该缺省上行BAP路由ID字段或bap-Config是由辅节点(SN)配置的。如果缺省上行BAP路由ID字段或bap-Config包含在通过SRB1传输的RRC重配置消息中，且不是包含在mrdc-SecondaryCellGroup IE中，那么该缺省上行BAP路由ID字段或bap-Config由主节点(MN)配置。
通过第一方面的实施例，能够指示为IAB节点配置的缺省上行BAP路由ID属于哪个拓扑。
第二方面的实施例
在IAB节点的引导过程，迁移过程，或者是IAB-MT的RRC恢复以及IAB-MT的RRC重建过程中，RRC重配置消息会为IAB节点的F1-C以及非F1流量配置缺省上行BH RLC信道(defaultUL-BH-RLC-Channel)。这个缺省上行BH RLC信道可以在IAB节点的F1-C相关流量对应的IP地址改变的时候，以及新的IP地址锚定在不同的IAB-donor-DU时进行配置或者重配置。因为BH RLC信道标识只在每条链路上 唯一，所以在双连接情况下，还需指定该BH RLC信道的链路，也就是上行父节点链路，也等同于小区组。在Rel-16的情况，如果IAB-MT工作在EN-DC场景，缺省的上行BH RLC信道指向SCG(secondary cell group，辅小区组)上的RLC信道，否则，指向MCG(master cell group，主小区组)上的RLC(无线链路控制)信道。
在Rel-17的NR-DC场景，IAB节点的父节点可以属于不同IAB-donor-CU，也就是边界IAB节点可以有两个IAB-donor-CU。MN(master node，主节点)和SN(secondary node，辅节点)都可以作为F1终结宿主节点。如果IAB节点在F1-C连接建立之前建立NR-DC，IAB节点可以通过例如基于提供缺省BAP配置的实体来隐式得出MN或者SN是F1终结宿主。在这种情况下，Rel-16的指定方法不适用，因为Rel-17的NR-DC场景，缺省的上行BH RLC信道也可以指向SCG。也就是，如果IAB-MT除了工作在EN-DC场景之外，缺省的上行BH RLC信道可以指向MCG或者SCG的RLC信道。
在BAP子层做路由时，如果在最近一次由RRC配置或者重新配置了defaultUL-BH-RLC-Channel之后，没有由F1AP配置或重新配置回传路由配置，需根据配置的defaultUL-BH-RLC-Channel来选择出口链路。因此缺省的上行BH RLC信道具有模糊性导致出口链路选择具有模糊性，需要进一步指明拓扑的信息或者小区组信息。
为了解决上述问题或类似问题，本申请第二方面的实施例提供一种配置信息的方法。该方法应用于IAB节点。
图5是第二方面的实施例的配置信息的方法的一个示意图，如图5所示，该方法包括：
操作501、接收RRC重配置消息，其中，该RRC重配置消息指示为IAB节点配置的缺省上行BH RLC信道所属于的拓扑的相关信息。
在第二方面的实施例中，该IAB节点不工作在EN-DC。该IAB节点可以是边界IAB节点，例如，图2或图3所示的IAB节点3。此外，本申请的IAB节点并不限于此，IAB节点也可以是其它的类型。
在操作501中，拓扑的相关信息可以指：拓扑的信息和/或小区组信息。其中，拓扑包括F1终结拓扑或非F1终结拓扑。小区组信息包括主小区组/辅小区组(MCG/SCG)信息。
在操作501的一些实施例中，RRC重配置消息可以具有第二指示信息，该第二指示信息用于指示缺省上行BH RLC信道所属于的拓扑是F1终结拓扑或非F1终结拓扑，或者，第二指示信息用于指示该缺省上行BH RLC信道指向主小区组(MCG)上的RLC信道或辅小区组(SCG)上的RLC信道。该第二指示信息可以针对双连接节点，或者NR-DC的节点，或者是边界IAB节点是必须的。
在操作501的至少另一些实施例中，该缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)可以指向MCG的RLC信道或者指向SCG的RLC信道，可以由配置缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config的宿主中心单元(donor-CU)指示该缺省上行BH RLC信道所指向的小区组。由此，能够通过隐式的方法指示该缺省上行BH RLC信道所属于的拓扑的相关信息。
在该至少另一些实施例中：如果由MN配置该缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config，那么该缺省上行BH RLC信道指向MCG上的RLC信道；如果由SN配置所述缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config，那么该缺省上行BH RLC信道指向SCG上的RLC信道。也就是说，对于IAB节点(例如，边界IAB节点)，该缺省的上行BH RLC信道指向配置该字段的donor-CU所配置的回传链路上的RLC信道。
例如，可以在TS 38.331中对RRC标准进行增强。可以在RRC重配置信息的bap-Config IE中的defaultUL-BH-RLC-Channel字段进行如表4所示的增强。
表4
Figure PCTCN2022085090-appb-000005
在该至少另一些实施例中：如果缺省上行BH RLC信道字段或bap-Config包含在 通过SRB1传输的RRC重配置消息中，且不是包含在多无线电接入技术双连接辅小区组信息元素(mrdc-SecondaryCellGroup IE)中，那么该缺省上行BH RLC信道字段或bap-Config由主节点(MN)配置；如果该缺省上行BH RLC信道字段或bap-Config包含在通过SRB3传输的RRC重配置消息中，或者该缺省上行BH RLC信道字段或bap-Config包含在mrdc-SecondaryCellGroup IE中，那么该缺省上行BH RLC信道字段或bap-Config由辅节点(SN)配置。
在BAP子层做路由时，如果在最近一次由RRC配置或者重新配置了缺省上行BH RLC信道之后，没有由F1AP配置或重新配置回传路由配置，那么，根据缺省上行BH RLC信道对应的小区组来选择出口链路。
在至少一个实施例中，在BAP子层做路由时，如果在最近一次由RRC配置或者重新配置了缺省上行BH RLC信道之后，没有由F1应用协议(F1AP)配置或重新配置回传路由配置，那么，IAB节点根据缺省上行BH RLC信道对应的小区组来选择出口链路。
通过第二方面的实施例，能够指示为IAB节点配置的缺省上行BH RLC信道所属于的拓扑的相关信息。
第三方面的实施例
在图2和图3所示的宿主间路由的情况下，边界节点的后裔节点可以使用相同的宿主间(或CU间，inter-CU)拓扑适配过程。例如，当边界节点的IAB-MT迁移到donor-CU2之后，或者是和donor-CU2建立RRC之后，边界节点的IAB-DU仍然和donor-CU1保持F1连接，后裔节点(如IAB节点4)仍然和donor-CU1保持了RRC连接和F1连接。
由于边界节点的后裔节点需要将F1连接的运输路径迁移到非-F1终结拓扑，donor-CU2需根据donor-CU1的请求，为后裔节点提供新的TNL(transport network layer)地址也就是IP地址。这些一个或多个新的TNL地址锚定在donor-CU2的拓扑中的donor-DU，比如donor-DU2上。Donor-CU2通过XnAP消息，比如IAB Transport Migration Management Response消息将这些新的TNL地址发送给donor-CU1。Donor-CU2还提供该拓扑下的层2信息给donor-CU1，比如上行BAP路由标识，其中包含了该拓扑中的donor-DU，比如donor-DU2的BAP地址。Donor-CU1通过 RRCReconfiguration消息来对后裔节点进行IP地址配置。IP地址的配置使用RRC重配置中的IAB-IP-AddressConfiguration IE，其中包含IP地址、IP地址的用途，以及该IP地址对应的donor-DU的BAP地址(iab-donor-DU-BAP-Address)等字段。后裔节点在进行来源于自身的上行数据传输时，通过为该数据流量配置的BAP路由ID得到路由ID里包含的BAP地址，这个地址就是目的地donor-DU的BAP地址，然后在IAB-IP-AddressConfiguration配置中查找与该donor-DU的BAP地址对应的IP地址，选择该IP地址作为该流量使用的IP地址进行上行传输。
由于donor-DU2的BAP地址是CU2的拓扑中的，和CU1的拓扑中的BAP地址可能冲突。
为了解决上述问题，第三方面的实施例提供一种配置信息的方法，该方法应用于IAB节点。
图6是第三方面的实施例的配置信息的方法的一个示意图。如图6所示，该方法包括：
操作601、接收RRC重配置消息，其中，该RRC重配置消息为IAB节点配置第一donor-DU BAP地址，该第一donor-DU BAP地址指向第二拓扑下的宿主分布式单元(donor-DU2)。
在第三方面的实施例中，该IAB节点可以是边界IAB节点的后裔节点，例如，图2或图3所示的IAB节点4。此外，本申请的IAB节点并不限于此，IAB节点也可以是其它的类型。
在至少一个实施例中，第二拓扑指和该IAB节点所属于的拓扑不同的拓扑。例如，该IAB节点属于边界节点的F1终结拓扑，也就是第一拓扑，该第二拓扑为边界节点的非F1终结拓扑。
在操作601的至少一个实施例中，该RRC重配置消息的IP地址配置中可以包括该第一donor-DU BAP地址。
在至少一个实施例中，IAB节点被配置上行BAP路由ID，该上行BAP路由ID中包含该第一donor-DU BAP地址。
在至少一个实施例中，如图6所示，该方法还包括：
操作602、该IAB节点根据第一donor-DU BAP地址选择IP地址；以及
操作603、该IAB节点使用选择的IP地址经由第二拓扑进行上行传输。
结合图2、图3可知，在第三方面的实施例中，CU1可以给donor-DU2在CU1的拓扑内分配第一donor-DU BAP地址，该第一donor-DU BAP地址可以叫做伪(pseudo)BAP地址，或者叫别名(alias)地址。CU1可以为后裔节点配置上行BAP路由ID，包含指示donor-DU2的第一donor-DU BAP地址。
由于后裔节点在选择IP地址时是根据上行BAP路由ID中的donor-DU BAP地址来进行相应选择，所以IAB-IP-AddressConfiguration中的针对donor-DU2的BAP地址也是donor-DU2的第一donor-DU BAP地址，而不是donor-DU2在CU2拓扑中的实际BAP地址。具体地，对于边界IAB节点的后裔节点，IP地址配置中的IAB-donor-DU的BAP地址可以是第一donor-DU BAP地址，该第一donor-DU BAP地址指向边界IAB节点的非F1终结宿主CU下面的某个IAB-donor-DU(例如，图2、图3的donor-DU2)。
例如，可以在TS 38.331中对RRC标准进行增强。可以在RRC重配置信息的IAB-IP-AddressConfiguration IE中的iab-donor-DU-BAP-Address字段进行如表5所示的增强。
表5
Figure PCTCN2022085090-appb-000006
在至少一个实施例中，IAB节点在收到RRC重配置消息中包含的IAB IP地址增加/修改列表(iab-IP-AddressToAddModList)的情况下，保存该列表中的IP地址和该IP地址对应的第一donor-DU BAP地址。该IP地址可以是IPv4，也可以是IPv6地址。IP地址的用途可以是F1-C，F1-U，非F1流量等。
根据第三方面的实施例，在为边界IAB节点或者后裔节点配置IP地址时，能够应对donor-DU的BAP地址为伪地址的情况。
第四方面的实施例
本申请第四方面的实施例提供一种配置信息的方法，与第一方面的实施例的配置信息的方法对应。该方法应用于宿主中心单元(CU)，例如，图2或图3的donor-CU1或donor-CU2。
图7是第四方面的实施例的配置信息的方法的一个示意图，如图7所示，该方法包括：
操作701、发送RRC重配置消息，其中，该RRC重配置消息指示为IAB节点配置的缺省上行BAP路由ID所属于的拓扑的相关信息。
在第四方面的实施例中，该IAB节点可以是边界IAB节点，例如，图2或图3所示的IAB节点3。此外，本申请的IAB节点并不限于此，IAB节点也可以是其它的类型。
在操作701中，拓扑的相关信息可以指：拓扑的信息，和/或小区组的信息。其中，拓扑包括F1终结拓扑或非F1终结拓扑。小区组的信息包括主小区组/辅小区组(MCG/SCG)信息。
在至少一些实施例中，在操作701中，RRC重配置消息可以具有第一指示信息，该第一指示信息用于指示缺省上行BAP路由ID所属于的拓扑。例如，该第一指示信息用于指示缺省上行BAP路由ID所属于的拓扑是属于F1终结拓扑或非F1终结拓扑。该第一指示信息可以只对于边界IAB节点才是必须的。
在至少另一些实施例中，在操作701中，可以由配置缺省上行BAP路由ID(defaultUL-BAP-RoutingID)字段或者配置包含该缺省上行BAP路由ID字段的回传适应协议配置(bap-Config)的宿主中心单元(donor-CU)指示该缺省上行BAP路由ID所属于的拓扑。由此，能够通过隐式的方法指示该缺省上行BAP路由ID属于哪个拓扑。
其中，如果由F1终结宿主配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于F1终结拓扑；如果由非F1终结宿主配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于非F1终结拓扑。
通过第四方面的实施例，能够指示为IAB节点配置的缺省上行BAP路由ID属于哪个拓扑。
第五方面的实施例
本申请第五方面的实施例提供一种配置信息的方法，与第二方面的实施例的配置信息的方法对应。该方法应用于宿主中心单元(CU)，例如，图2或图3所示的donor-CU1或donor-CU2。
图8是第五方面的实施例的配置信息的方法的一个示意图，如图8所示，该方法包括：
操作801、发送RRC重配置消息，其中，该RRC重配置消息指示为IAB节点配置的缺省上行BH RLC信道所属于的拓扑的相关信息。
在第五方面的实施例中，该IAB节点不工作在EN-DC。该IAB节点可以是边界IAB节点，例如，图2或图3所示的IAB节点3。此外，本申请的IAB节点并不限于此，IAB节点也可以是其它的类型。
在操作801中，拓扑的相关信息可以指：拓扑的信息和/或小区组信息。其中，拓扑包括F1终结拓扑或非F1终结拓扑。小区组信息包括主小区组/辅小区组(MCG/SCG)信息。
在操作801的一些实施例中，RRC重配置消息可以具有第二指示信息，该第二指示信息用于指示缺省上行BH RLC信道所属于的拓扑是F1终结拓扑或非F1终结拓扑，或者，第二指示信息用于指示该缺省上行BH RLC信道指向主小区组(MCG)上的RLC信道或辅小区组(SCG)上的RLC信道。该第二指示信息可以针对双连接节点，或者NR-DC的节点，或者是边界IAB节点是必须的。
在操作801的至少另一些实施例中，该缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)可以指向MCG的RLC信道或者指向SCG的RLC信道，可以由配置缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config的宿主中心单元(donor-CU)指示该缺省上行BH RLC信道所指向的小区组。由此，能够通过隐式的方法指示该缺省上行BH RLC信道所属于的拓扑的相关信息。
在该至少另一些实施例中：如果配置该缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config的宿主是MN，那么该缺省上行BH RLC信道指向MCG上的RLC信道；如果配置所述缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config的宿主是SN，那么该缺省上行BH RLC 信道指向SCG上的RLC信道。也就是说，对于IAB节点(例如，边界IAB节点)，该缺省的上行BH RLC信道指向配置该字段的donor-CU所配置的回传链路上的RLC信道。
在至少一个实施例中，在BAP子层做路由时，如果在最近一次由RRC配置或者重新配置了缺省上行BH RLC信道之后，没有由F1应用协议(F1AP)配置或重新配置回传路由配置，那么，IAB节点根据缺省上行BH RLC信道对应的小区组来选择出口链路。
通过第五方面的实施例，能够指示为IAB节点配置的缺省上行BH RLC信道所属于的拓扑的相关信息。
第六方面的实施例
第六方面的实施例提供一种配置信息的方法，与第三方面的实施例的配置信息的方法对应。该方法应用于宿主中心单元(CU)，例如，图2或图3所示的donor-CU1。
图9是第六方面的实施例的配置信息的方法的一个示意图。如图9所示，该方法包括：
操作901、发送RRC重配置消息，其中，该RRC重配置消息为IAB节点配置第一donor-DU BAP地址，该第一donor-DU BAP地址指向第二拓扑下的宿主分布式单元(donor-DU2)。
在第六方面的实施例中，该IAB节点可以是边界IAB节点的后裔节点，例如，图2或图3所示的IAB节点4。此外，本申请的IAB节点并不限于此，IAB节点也可以是其它的类型。
在至少一个实施例中，第二拓扑指和该IAB节点所属于的拓扑不同的拓扑。例如，该IAB节点属于边界节点的F1终结拓扑，该第二拓扑为边界节点的非F1终结拓扑。
在操作901的至少一个实施例中，该RRC重配置消息的IP地址配置中可以包括该第一donor-DU BAP地址。
在至少一个实施例中，CU可以为IAB节点被配置上行BAP路由ID，该上行BAP路由ID中包含该第一donor-DU BAP地址。
结合图2、图3可知，在第三方面的实施例中，donor-CU1可以给donor-DU2在 CU1的拓扑内分配第一donor-DU BAP地址，该第一donor-DU BAP地址可以叫做伪(pseudo)BAP地址，或者叫别名(alias)地址。CU1可以为后裔节点配置上行BAP路由ID，包含指示donor-DU2的第一donor-DU BAP地址。
由于后裔节点在选择IP地址时是根据上行BAP路由ID中的donor-DU BAP地址来进行相应选择，所以IAB-IP-AddressConfiguration中的针对donor-DU2的BAP地址也是donor-DU2的第一donor-DU BAP地址，而不是donor-DU2在CU2拓扑中的实际BAP地址。具体地，对于边界IAB节点的后裔节点，IP地址配置中的IAB-donor-DU的BAP地址可以是第一donor-DU BAP地址，该第一donor-DU BAP地址指向边界IAB节点的非F1终结宿主CU下面的某个IAB-donor-DU(例如，图2、图3的donor-DU2)。
在至少一个实施例中，CU发送的RRC重配置消息中可以包含IAB IP地址增加/修改列表(iab-IP-AddressToAddModList)，该列表中包括IP地址和该IP地址对应的第一donor-DU BAP地址。该IP地址可以是IPv4，也可以是IPv6地址。IP地址的用途可以是F1-C，F1-U，非F1流量等。
根据第六方面的实施例，在为边界IAB节点或者后裔节点配置IP地址时，能够应对donor-DU的BAP地址为伪地址的情况。
第七方面的实施例
本申请第七方面的实施例提供一种配置信息的装置，与第一方面的实施例所述的配置信息的方法对应。该装置应用于IAB节点。
图10是第七方面的实施例的配置信息的装置的一个示意图，如图10所示，配置信息的装置1000包括：
第一接收单元1001，其接收RRC重配置消息，其中，该RRC重配置消息指示为IAB节点配置的缺省上行BAP路由ID所属于的拓扑的相关信息。
在第七方面的实施例中，该IAB节点可以是边界IAB节点，例如，图2或图3所示的IAB节点3。此外，本申请的IAB节点并不限于此，IAB节点也可以是其它的类型。
拓扑的相关信息可以指：拓扑的信息，和/或小区组的信息。其中，拓扑包括F1终结拓扑或非F1终结拓扑。小区组的信息包括主小区组/辅小区组(MCG/SCG)信 息。
在至少一些实施例中，RRC重配置消息可以具有第一指示信息，该第一指示信息用于指示缺省上行BAP路由ID所属于的拓扑。例如，该第一指示信息用于指示缺省上行BAP路由ID所属于的拓扑是属于F1终结拓扑或非F1终结拓扑。该第一指示信息可以只对于边界IAB节点才是必须的。
在至少另一些实施例中，可以由配置缺省上行BAP路由ID(defaultUL-BAP-RoutingID)字段或者配置包含该缺省上行BAP路由ID字段的回传适应协议配置(bap-Config)的宿主中心单元(donor-CU)指示该缺省上行BAP路由ID所属于的拓扑。由此，能够通过隐式的方法指示该缺省上行BAP路由ID属于哪个拓扑。
其中，如果由F1终结宿主配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于F1终结拓扑；如果由非F1终结宿主配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于非F1终结拓扑。
对于通过隐式的方法指示该缺省上行BAP路由ID属于哪个拓扑的方案，在一个具体的实施方式中，可以通过是MN还是SN是F1终结宿主来确定F1终结宿主还是非F1终结宿主配置的所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config。
例如，如果IAB节点在建立F1连接之后建立NR-DC，那么MN是F1终结宿主；如果IAB节点在建立F1-C之前建立了NR-DC，那么由IAB节点选择MN或者SN作为F1终结宿主。
如果缺省上行BAP路由ID字段或bap-Config包含在通过SRB3传输的RRC重配置消息中，或者所述缺省上行BAP路由ID字段或bap-Config包含在多无线电接入技术双连接辅小区组信息元素(mrdc-SecondaryCellGroup IE)中，那么该缺省上行BAP路由ID字段或bap-Config是由辅节点(SN)配置的。如果缺省上行BAP路由ID字段或bap-Config包含在通过SRB1传输的RRC重配置消息中，且不是包含在mrdc-SecondaryCellGroup IE中，那么该缺省上行BAP路由ID字段或bap-Config由主节点(MN)配置。
通过第七方面的实施例，能够指示为IAB节点配置的缺省上行BAP路由ID属于哪个拓扑。
第八方面的实施例
本申请第八方面的实施例提供一种配置信息的装置，与第二方面的实施例的配置信息的方法对应。该装置应用于IAB节点。
图11是第八方面的实施例的配置信息的装置的一个示意图，如图11所示，该配置信息的装置1100包括：
第二接收单元1101，其接收RRC重配置消息，其中，该RRC重配置消息指示为IAB节点配置的缺省上行BH RLC信道所属于的拓扑的相关信息。
在第八方面的实施例中，该IAB节点不工作在EN-DC。该IAB节点可以是边界IAB节点，例如，图2或图3所示的IAB节点3。此外，本申请的IAB节点并不限于此，IAB节点也可以是其它的类型。
拓扑的相关信息可以指：拓扑的信息和/或小区组信息。其中，拓扑包括F1终结拓扑或非F1终结拓扑。小区组信息包括主小区组/辅小区组(MCG/SCG)信息。
在一些实施例中，RRC重配置消息可以具有第二指示信息，该第二指示信息用于指示缺省上行BH RLC信道所属于的拓扑是F1终结拓扑或非F1终结拓扑，或者，第二指示信息用于指示该缺省上行BH RLC信道指向主小区组(MCG)上的RLC信道或辅小区组(SCG)上的RLC信道。该第二指示信息可以针对双连接节点，或者NR-DC的节点，或者是边界IAB节点是必须的。
在至少另一些实施例中，该缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)可以指向MCG的RLC信道或者指向SCG的RLC信道，可以由配置缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config的宿主中心单元(donor-CU)指示该缺省上行BH RLC信道所指向的小区组。由此，能够通过隐式的方法指示该缺省上行BH RLC信道所属于的拓扑的相关信息。
在该至少另一些实施例中：如果由MN配置该缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config，那么该缺省上行BH RLC信道指向MCG上的RLC信道；如果由SN配 置所述缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config，那么该缺省上行BH RLC信道指向SCG上的RLC信道。也就是说，对于IAB节点(例如，边界IAB节点)，该缺省的上行BH RLC信道指向配置该字段的donor-CU所配置的回传链路上的RLC信道。
在该至少另一些实施例中：如果缺省BH RLC信道字段或bap-Config包含在通过SRB1传输的RRC重配置消息中，且不是包含在多无线电接入技术双连接辅小区组信息元素(mrdc-SecondaryCellGroup IE)中，那么该缺省BH RLC信道字段或bap-Config由主节点(MN)配置；如果该缺省上行BH RLC信道字段或bap-Config包含在通过SRB3传输的RRC重配置消息中，或者该缺省上行BH RLC信道字段或bap-Config包含在mrdc-SecondaryCellGroup IE中，那么该缺省上行BH RLC信道字段或bap-Config由辅节点(SN)配置。
在BAP子层做路由时，如果在最近一次由RRC配置或者重新配置了缺省上行BH RLC信道之后，没有由F1AP配置或重新配置回传路由配置，那么，根据缺省上行BH RLC信道对应的小区组来选择出口链路。
在至少一个实施例中，在BAP子层做路由时，如果在最近一次由RRC配置或者重新配置了缺省上行BH RLC信道之后，没有由F1应用协议(F1AP)配置或重新配置回传路由配置，那么，IAB节点根据缺省上行BH RLC信道对应的小区组来选择出口链路。
通过第八方面的实施例，能够指示为IAB节点配置的缺省上行BH RLC信道所属于的拓扑的相关信息。
第九方面的实施例
第九方面的实施例提供一种配置信息的装置，与第三方面的实施例的配置信息的方法对应。该装置应用于IAB节点。
图12是第九方面的实施例的配置信息的装置的一个示意图。如图12所示，该配置信息的装置包括：
第三接收单元1201，其接收RRC重配置消息，其中，该RRC重配置消息为IAB节点配置第一donor-DU BAP地址，该第一donor-DU BAP地址指向第二拓扑下的宿主分布式单元(donor-DU2)。
在第九方面的实施例中，该IAB节点可以是边界IAB节点的后裔节点，例如，图2或图3所示的IAB节点4。此外，本申请的IAB节点并不限于此，IAB节点也可以是其它的类型。
在至少一个实施例中，第二拓扑指和该IAB节点所属于的拓扑不同的拓扑。例如，该IAB节点属于边界节点的F1终结拓扑，该第二拓扑为边界节点的非F1终结拓扑。
在至少一个实施例中，该RRC重配置消息的IP地址配置中可以包括该第一donor-DU BAP地址。
在至少一个实施例中，IAB节点被配置上行BAP路由ID，该上行BAP路由ID中包含该第一donor-DU BAP地址。
在至少一个实施例中，第三接收单元1201还进行如下操作：
根据第一donor-DU BAP地址选择IP地址；以及
使用选择的IP地址经由第二拓扑进行上行传输。
结合图2、图3可知，在第九方面的实施例中，CU1可以给donor-DU2在CU1的拓扑内分配第一donor-DU BAP地址，该第一donor-DU BAP地址可以叫做伪(pseudo)BAP地址，或者叫别名(alias)地址。CU1可以为后裔节点配置上行BAP路由ID，包含指示donor-DU2的第一donor-DU BAP地址。
由于后裔节点在选择IP地址时是根据上行BAP路由ID中的donor-DU BAP地址来进行相应选择，所以IAB-IP-AddressConfiguration中的针对donor-DU2的BAP地址也是donor-DU2的第一donor-DU BAP地址，而不是donor-DU2在CU2拓扑中的实际BAP地址。具体地，对于边界IAB节点的后裔节点，IP地址配置中的IAB-donor-DU的BAP地址可以是第一donor-DU BAP地址，该第一donor-DU BAP地址指向边界IAB节点的非F1终结宿主CU下面的某个IAB-donor-DU(例如，图2、图3的donor-DU2)。
在至少一个实施例中，IAB节点在收到RRC重配置消息中包含的IAB IP地址增加/修改列表(iab-IP-AddressToAddModList)的情况下，保存该列表中的IP地址和该IP地址对应的第一donor-DU BAP地址。该IP地址可以是IPv4，也可以是IPv6地址。IP地址的用途可以是F1-C，F1-U，非F1流量等。
根据第九方面的实施例，在为边界IAB节点或者后裔节点配置IP地址时，能够 应对donor-DU的BAP地址为伪地址的情况。
第十方面的实施例
本申请第十方面的实施例提供一种配置信息的方法，与第四方面的实施例的配置信息的方法对应。该方法应用于宿主中心单元(CU)，例如，图2或图3的donor-CU1或donor-CU2。
图13是第十方面的实施例的配置信息的装置的一个示意图，如图13所示，该装置1300包括：
第一发送单元1301，其发送RRC重配置消息，其中，该RRC重配置消息指示为IAB节点配置的缺省上行BAP路由ID所属于的拓扑的相关信息。
在第十方面的实施例中，该IAB节点可以是边界IAB节点，例如，图2或图3所示的IAB节点3。此外，本申请的IAB节点并不限于此，IAB节点也可以是其它的类型。
拓扑的相关信息可以指：拓扑的信息，和/或小区组的信息。其中，拓扑包括F1终结拓扑或非F1终结拓扑。小区组的信息包括主小区组/辅小区组(MCG/SCG)信息。
在至少一些实施例中，RRC重配置消息可以具有第一指示信息，该第一指示信息用于指示缺省上行BAP路由ID所属于的拓扑。例如，该第一指示信息用于指示缺省上行BAP路由ID所属于的拓扑是属于F1终结拓扑或非F1终结拓扑。该第一指示信息可以只对于边界IAB节点才是必须的。
在至少另一些实施例中，可以由配置缺省上行BAP路由ID(defaultUL-BAP-RoutingID)字段或者配置包含该缺省上行BAP路由ID字段的回传适应协议配置(bap-Config)的宿主中心单元(donor-CU)指示该缺省上行BAP路由ID所属于的拓扑。由此，能够通过隐式的方法指示该缺省上行BAP路由ID属于哪个拓扑。
其中，如果由F1终结宿主配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于F1终结拓扑；如果由非F1终结宿主配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于非F1 终结拓扑。
通过第十方面的实施例，能够指示为IAB节点配置的缺省上行BAP路由ID属于哪个拓扑。
第十一方面的实施例
本申请第十一方面的实施例提供一种配置信息的装置，与第五方面的实施例的配置信息的方法对应。该方法应用于宿主中心单元(CU)，例如，图2或图3所示的donor-CU1或donor-CU2。
图14是第十一方面的实施例的配置信息的装置的一个示意图，如图14所示，该装置1400包括：
第二发送单元1401，其发送RRC重配置消息，其中，该RRC重配置消息指示为IAB节点配置的缺省上行BH RLC信道所属于的拓扑的相关信息。
在第十一方面的实施例中，该IAB节点不工作在EN-DC。该IAB节点可以是边界IAB节点，例如，图2或图3所示的IAB节点3。此外，本申请的IAB节点并不限于此，IAB节点也可以是其它的类型。
拓扑的相关信息可以指：拓扑的信息和/或小区组信息。其中，拓扑包括F1终结拓扑或非F1终结拓扑。小区组信息包括主小区组/辅小区组(MCG/SCG)信息。
在一些实施例中，RRC重配置消息可以具有第二指示信息，该第二指示信息用于指示缺省上行BH RLC信道所属于的拓扑是F1终结拓扑或非F1终结拓扑，或者，第二指示信息用于指示该缺省上行BH RLC信道指向主小区组(MCG)上的RLC信道或辅小区组(SCG)上的RLC信道。该第二指示信息可以针对双连接节点，或者NR-DC的节点，或者是边界IAB节点是必须的。
在至少另一些实施例中，该缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)可以指向MCG的RLC信道或者指向SCG的RLC信道，可以由配置缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config的宿主中心单元(donor-CU)指示该缺省上行BH RLC信道所指向的小区组。由此，能够通过隐式的方法指示该缺省上行BH RLC信道所属于的拓扑的相关信息。
在该至少另一些实施例中：如果配置该缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config的宿主是MN，那么该缺省上行BH RLC信道指向MCG上的RLC信道；如果配置所述缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config的宿主是SN，那么该缺省上行BH RLC信道指向SCG上的RLC信道。也就是说，对于IAB节点(例如，边界IAB节点)，该缺省的上行BH RLC信道指向配置该字段的donor-CU所配置的回传链路上的RLC信道。
在至少一个实施例中，在BAP子层做路由时，如果在最近一次由RRC配置或者重新配置了缺省上行BH RLC信道之后，没有由F1应用协议(F1AP)配置或重新配置回传路由配置，那么，IAB节点根据缺省上行BH RLC信道对应的小区组来选择出口链路。
通过第十一方面的实施例，能够指示为IAB节点配置的缺省上行BH RLC信道所属于的拓扑的相关信息。
第十二方面的实施例
第十二方面的实施例提供一种配置信息的装置，与第六方面的实施例的配置信息的方法对应。该装置应用于宿主中心单元(CU)，例如，图2或图3所示的donor-CU1。
图15是第十二方面的实施例的配置信息的方法的一个示意图。如图15所示，该装置1500包括：
第三发送单元1501，其发送RRC重配置消息，其中，该RRC重配置消息为IAB节点配置第一donor-DU BAP地址，该第一donor-DU BAP地址指向第二拓扑下的宿主分布式单元(donor-DU2)。
在第十二方面的实施例中，该IAB节点可以是边界IAB节点的后裔节点，例如，图2或图3所示的IAB节点4。此外，本申请的IAB节点并不限于此，IAB节点也可以是其它的类型。
在至少一个实施例中，第二拓扑指和该IAB节点所属于的拓扑不同的拓扑。例如，该IAB节点属于边界节点的F1终结拓扑，该第二拓扑为边界节点的非F1终结拓扑。
在至少一个实施例中，该RRC重配置消息的IP地址配置中可以包括该第一donor-DU BAP地址。
在至少一个实施例中，CU可以为IAB节点被配置上行BAP路由ID，该上行BAP路由ID中包含该第一donor-DU BAP地址。
结合图2、图3可知，在第十二方面的实施例中，donor-CU1可以给donor-DU2在CU1的拓扑内分配第一donor-DU BAP地址，该第一donor-DU BAP地址可以叫做伪(pseudo)BAP地址，或者叫别名(alias)地址。CU1可以为后裔节点配置上行BAP路由ID，包含指示donor-DU2的第一donor-DU BAP地址。
由于后裔节点在选择IP地址时是根据上行BAP路由ID中的donor-DU BAP地址来进行相应选择，所以IAB-IP-AddressConfiguration中的针对donor-DU2的BAP地址也是donor-DU2的第一donor-DU BAP地址，而不是donor-DU2在CU2拓扑中的实际BAP地址。具体地，对于边界IAB节点的后裔节点，IP地址配置中的IAB-donor-DU的BAP地址可以是第一donor-DU BAP地址，该第一donor-DU BAP地址指向边界IAB节点的非F1终结宿主CU下面的某个IAB-donor-DU(例如，图2、图3的donor-DU2)。
在至少一个实施例中，CU发送的RRC重配置消息中可以包含IAB IP地址增加/修改列表(iab-IP-AddressToAddModList)，该列表中包括IP地址和该IP地址对应的第一donor-DU BAP地址。该IP地址可以是IPv4，也可以是IPv6地址。IP地址的用途可以是F1-C，F1-U，非F1流量等。
根据第十二方面的实施例，在为边界IAB节点或者后裔节点配置IP地址时，能够应对donor-DU的BAP地址为伪地址的情况。
第十三方面的实施例
本申请实施例还提供一种通信系统，该通信系统可以包括IAB节点和基站CU。该IAB节点的MT、该IAB节点的DU以及该基站CU中的至少一者可以具有图16所示的电子设备的组成。
图16是本申请实施例的电子设备的组成的一个示意图。如图16所示，电子设备1600可以包括：处理器1610(例如中央处理器CPU)和存储器1620；存储器1620耦合到处理器1610。其中该存储器1620可存储各种数据；此外还存储信息处理的程 序1630，并且在处理器1610的控制下执行该程序1630。
例如，处理器1610可以被配置为执行程序而实现如第一方面的实施例至第六方面的实施例中的方法。
此外，如图16所示，电子设备1600还可以包括：收发机1640和天线1650等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，电子设备1600也并不是必须要包括图16中所示的所有部件；此外，电子设备1600还可以包括图16中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机程序，其中当在IAB节点中执行所述程序时，所述程序使得所述IAB节点执行第一方面至第三方面的实施例所述的方法。
本申请实施例还提供一种计算机程序，其中当在CU节点中执行所述程序时，所述程序使得所述CU执行第四方面至第六方面的实施例所述的方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得电子设备执行第一方面至第六方面的实施例所述的方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或 者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于包括以上实施例的实施方式，还公开下述的附记：
(IAB节点侧的方法：)
1.一种配置信息的方法，应用于IAB节点，该方法包括：
接收RRC重配置消息，其中，所述RRC重配置消息指示为所述IAB节点配置的缺省上行BAP路由ID所属于的拓扑的相关信息。
2.如附记1所述的方法，其中，
所述拓扑包括F1终结拓扑或非F1终结拓扑。
3.如附记1所述的方法，其中，
所述RRC重配置消息具有第一指示信息，所述第一指示信息用于指示所述缺省上行BAP路由ID所属于的拓扑。
4.如附记1所述的方法，其中，
由配置缺省上行BAP路由ID字段(defaultUL-BAP-RoutingID)或者配置包含该缺省上行BAP路由ID字段的bap-Config的宿主中心单元(donor-CU)指示该缺省上行BAP路由ID所属于的拓扑。
5.如附记4所述的方法，其中，
如果由F1终结宿主配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于F1终结拓扑。
6.如附记4所述的方法，其中，
如果由非F1终结宿主配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于非F1终结拓扑。
7.如附记5或6所述的方法，其中，
通过是MN还是SN是F1终结宿主来确定F1终结宿主还是非F1终结宿主配置的所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config。
8.如附记7所述的方法，其中，
如果所述IAB节点在建立F1连接之后建立NR-DC，那么MN是F1终结宿主；如果IAB节点在建立F1-C之前建立了NR-DC，那么由所述IAB节点选择MN或者SN作为F1终结宿主。
9.如附记7所述的方法，其中，
如果所述缺省上行BAP路由ID字段或bap-Config包含在通过SRB3传输的RRC重配置消息中，或者所述缺省上行BAP路由ID字段或bap-Config包含在mrdc-SecondaryCellGroup IE中，那么所述缺省上行BAP路由ID字段或bap-Config由辅节点(SN)配置。
10.如附记7所述的方法，其中，
如果所述缺省上行BAP路由ID字段或bap-Config包含在通过SRB1传输的RRC重配置消息中，且不是包含在mrdc-SecondaryCellGroup IE中，那么所述缺省上行BAP路由ID字段或bap-Config由主节点(MN)配置。
11.如附记1所述的方法，其中，
所述IAB节点是边界IAB节点。
12.一种配置信息的方法，应用于IAB节点，该方法包括：
接收RRC重配置消息，其中，所述RRC重配置消息指示为所述IAB节点配置的缺省上行BH RLC信道所属于的拓扑的相关信息。
13.如附记12所述的方法，其中，
所述RRC重配置消息具有第二指示信息，
所述第二指示信息用于指示所述缺省上行BH RLC信道所属于的拓扑是F1终结 拓扑或非F1终结拓扑，或者，所述第二指示信息用于指示所述缺省上行BH RLC信道指向主小区组上的RLC信道或辅小区组上的RLC信道。
14.如附记12所述的方法，其中，
配置的所述缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)指向MCG的RLC信道或者SCG的RLC信道。
15.如附记14所述的方法，其中，
由配置缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config的宿主中心单元(donor-CU)指示所述缺省上行BH RLC信道所指向的小区组。
16.如附记15所述的方法，其中，
如果由MN配置所述缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config，那么该缺省上行BH RLC信道指向MCG上的RLC信道。
17.如附记15所述的方法，其中，
如果由SN配置所述缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config，那么该缺省上行BH RLC信道指向SCG上的RLC信道。
18.如附记17所述的方法，其中，
如果所述缺省上行BH RLC信道字段或bap-Config包含在通过SRB3传输的RRC重配置消息中，或者所述缺省上行BH RLC信道字段或bap-Config包含在mrdc-SecondaryCellGroup IE中，那么所述缺省上行BH RLC信道字段或bap-Config由辅节点(SN)配置。
19.如附记16所述的方法，其中，
如果所述缺省BH RLC信道字段或bap-Config包含在通过SRB1传输的RRC重配置消息中，且不是包含在mrdc-SecondaryCellGroup IE中，那么所述缺省BH RLC信道字段或bap-Config由主节点(MN)配置。
20.如附记12-19中任一项所述的方法，其中，
所述IAB节点不工作在EN-DC。
21.如附记12所述的方法，其中，
在BAP子层做路由时，如果在最近一次由RRC配置或者重新配置了缺省上行BH RLC信道之后，没有由F1AP配置或重新配置回传路由配置，那么，根据缺省上行BH RLC信道对应的小区组来选择出口链路。
22.如附记12所述的方法，其中，
所述IAB节点是边界IAB节点。
23.一种配置信息的方法，应用于IAB节点，该方法包括：
接收RRC重配置消息，其中，所述RRC重配置消息为所述IAB节点配置第一donor-DU BAP地址，所述第一donor-DU BAP地址指向第二拓扑下的宿主分布式单元(DU2)。
24.如附记23所述的方法，其中，
所述RRC重配置消息的IP地址配置中包括所述第一donor-DU BAP地址。
25.如附记23所述的方法，其中，
所述IAB节点在收到所述RRC重配置消息中包含的IAB IP地址增加/修改列表(iab-IP-AddressToAddModList)的情况下，保存所述列表中的IP地址和所述IP地址对应的所述第一donor-DU BAP地址。
26.如附记23所述的方法，其中，
所述IAB节点被配置上行BAP路由ID，所述上行BAP路由ID中包含所述第一donor-DU BAP地址。
27.如附记24所述的方法，其中，所述方法还包括：
所述IAB节点根据所述第一donor-DU BAP地址选择IP地址；以及
使用所述选择的IP地址经由第二拓扑进行上行传输。
28.如附记23所述的方法，其中，
所述IAB节点是边界IAB节点的后裔节点。
29.如附记28所述的方法，其中，
所述第二拓扑是所述边界IAB节点的非F1终结拓扑。
(CU侧的方法：)
30.一种配置信息的方法，应用于宿主中心单元(CU)，该方法包括：
发送RRC重配置消息，其中，所述RRC重配置消息指示为IAB节点配置的缺 省上行BAP路由ID所属于的拓扑的相关信息。
31.如附记30所述的方法，其中，
所述拓扑包括F1终结拓扑或非F1终结拓扑。
32.如附记30所述的方法，其中，
所述RRC重配置消息具有第一指示信息，所述第一指示信息用于指示所述缺省上行BAP路由ID所属于的拓扑。
33.如附记30所述的方法，其中，
由配置缺省上行BAP路由ID字段(defaultUL-BAP-RoutingID)或者配置包含该缺省上行BAP路由ID字段的bap-Config的宿主中心单元(donor-CU)指示该缺省上行BAP路由ID所属于的拓扑。
34.如附记33所述的方法，其中，
如果由作为F1终结宿主的所述CU配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于F1终结拓扑。
35.如附记33所述的方法，其中，
如果由作为非F1终结宿主的所述CU配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于非F1终结拓扑。
36.如附记30所述的方法，其中，
所述IAB节点是边界IAB节点。
37.一种配置信息的方法，应用于宿主中心单元(CU)，该方法包括：
发送RRC重配置消息，其中，所述RRC重配置消息指示为IAB节点配置的缺省上行BH RLC信道所属于的拓扑的相关信息。
38.如附记37所述的方法，其中，
所述RRC重配置消息具有第二指示信息，
所述第二指示信息用于指示所述缺省上行BH RLC信道所属于的拓扑是F1终结拓扑或非F1终结拓扑，或者，所述第二指示信息用于指示所述缺省上行BH RLC信道指向主小区组上的RLC信道或辅小区组上的RLC信道。
39.如附记37所述的方法，其中，
配置的所述缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)指向MCG的RLC信道或者SCG的RLC信道。
40.如附记39所述的方法，其中，
由配置缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config的宿主中心单元(donor-CU)指示所述缺省上行BH RLC信道所指向的小区组。
41.如附记40所述的方法，其中，
如果由作为MN的所述CU配置所述缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config，那么该缺省上行BH RLC信道指向MCG上的RLC信道。
42.如附记40所述的方法，其中，
如果由作为SN的所述CU配置所述缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config，那么该缺省上行BH RLC信道指向SCG上的RLC信道。
43.如附记37-42中任一项所述的方法，其中，
所述IAB节点不工作在EN-DC。
44.如附记37所述的方法，其中，
在所述IAB节点的BAP子层做路由时，如果在最近一次由所述RRC配置或者重新配置了缺省上行BH RLC信道之后，没有由F1AP配置或重新配置回传路由配置，那么，根据缺省上行BH RLC信道对应的小区组来选择出口链路。
45.如附记37所述的方法，其中，
所述IAB节点是边界IAB节点。
46.一种配置信息的方法，应用于宿主中心单元(CU)，该方法包括：
发送RRC重配置消息，其中，所述RRC重配置消息为IAB节点配置第一donor-DU BAP地址，所述第一donor-DU BAP地址指向第二拓扑下的宿主分布式单元(DU2)。
47.如附记46所述的方法，其中，
所述RRC重配置消息的IP地址配置中包括所述第一donor-DU BAP地址。
48.如附记46所述的方法，其中，所述方法还包括：
所述CU发送IAB IP地址增加/修改列表(iab-IP-AddressToAddModList)，所述列表中包括IP地址和所述IP地址对应的所述第一donor-DU BAP地址。
49.如附记46所述的方法，其中，所述方法还包括：
所述CU为所述IAB节点配置上行BAP路由ID，所述上行BAP路由ID中包含所述第一donor-DU BAP地址。
50.如附记46所述的方法，其中，
所述IAB节点是边界IAB节点的后裔节点。
51.如附记50所述的方法，其中，
所述第二拓扑是所述边界IAB节点的非F1终结拓扑。

Claims (20)

  1. 一种配置信息的装置，应用于IAB节点，该装置包括：
    第一接收单元，其接收RRC重配置消息，其中，所述RRC重配置消息指示为所述IAB节点配置的缺省上行BAP路由ID所属于的拓扑的相关信息。
  2. 如权利要求1所述的装置，其中，
    所述拓扑包括F1终结拓扑或非F1终结拓扑。
  3. 如权利要求1所述的装置，其中，
    由配置缺省上行BAP路由ID字段(defaultUL-BAP-RoutingID)或者配置包含该缺省上行BAP路由ID字段的bap-Config的宿主中心单元(donor-CU)指示该缺省上行BAP路由ID所属于的拓扑。
  4. 如权利要求3所述的装置，其中，
    如果由F1终结宿主配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于F1终结拓扑。
  5. 如权利要求3所述的装置，其中，
    如果由非F1终结宿主配置所述缺省上行BAP路由ID字段或者配置包含该缺省上行BAP路由ID字段的bap-Config，那么该缺省上行BAP路由ID属于非F1终结拓扑。
  6. 如权利要求1所述的装置，其中，
    所述IAB节点是边界IAB节点。
  7. 一种配置信息的装置，应用于IAB节点，该装置包括：
    第二接收单元，其接收RRC重配置消息，其中，所述RRC重配置消息指示为所述IAB节点配置的缺省上行BH RLC信道所属于的拓扑的相关信息。
  8. 如权利要求7所述的装置，其中，
    配置的所述缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)指向MCG的RLC信道或者SCG的RLC信道。
  9. 如权利要求8所述的装置，其中，
    由配置缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config的宿主中心单元(donor-CU)指示所述缺省上行BH RLC信道所指向的小区组。
  10. 如权利要求9所述的装置，其中，
    如果由MN配置所述缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config，那么该缺省上行BH RLC信道指向MCG上的RLC信道。
  11. 如权利要求9所述的装置，其中，
    如果由SN配置所述缺省上行BH RLC信道字段(defaultUL-BH-RLC-Channel)或者配置包含该缺省上行BH RLC信道字段的bap-Config，那么该缺省上行BH RLC信道指向SCG上的RLC信道。
  12. 如权利要求7所述的装置，其中，
    所述IAB节点不工作在EN-DC。
  13. 如权利要求7所述的装置，其中，
    在BAP子层做路由时，如果在最近一次由RRC配置或者重新配置了缺省上行BH RLC信道之后，没有由F1AP配置或重新配置回传路由配置，那么，根据缺省上行BH RLC信道对应的小区组来选择出口链路。
  14. 如权利要求7所述的装置，其中，
    所述IAB节点是边界IAB节点。
  15. 一种配置信息的装置，应用于IAB节点，该装置包括：
    第三接收单元，其接收RRC重配置消息，其中，所述RRC重配置消息为所述IAB节点配置第一donor-DU BAP地址，所述第一donor-DU BAP地址指向第二拓扑下的宿主分布式单元(DU2)。
  16. 如权利要求15所述的装置，其中，
    所述RRC重配置消息的IP地址配置中包括所述第一donor-DU BAP地址。
  17. 如权利要求15所述的装置，其中，
    所述IAB节点在收到所述RRC重配置消息中包含的IAB IP地址增加/修改列表(iab-IP-AddressToAddModList)的情况下，保存所述列表中的IP地址和所述IP地址对应的所述第一donor-DU BAP地址。
  18. 如权利要求16所述的装置，其中，所述第三接收单元还：
    根据所述第一donor-DU BAP地址选择IP地址；以及
    使用所述选择的IP地址经由第二拓扑进行上行传输。
  19. 如权利要求15所述的装置，其中，
    所述IAB节点是边界IAB节点的后裔节点。
  20. 如权利要求19所述的装置，其中，
    所述第二拓扑是所述边界IAB节点的非F1终结拓扑。
PCT/CN2022/085090 2022-04-02 2022-04-02 配置信息的方法、装置和通信系统 WO2023184542A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/085090 WO2023184542A1 (zh) 2022-04-02 2022-04-02 配置信息的方法、装置和通信系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/085090 WO2023184542A1 (zh) 2022-04-02 2022-04-02 配置信息的方法、装置和通信系统

Publications (1)

Publication Number Publication Date
WO2023184542A1 true WO2023184542A1 (zh) 2023-10-05

Family

ID=88198878

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/085090 WO2023184542A1 (zh) 2022-04-02 2022-04-02 配置信息的方法、装置和通信系统

Country Status (1)

Country Link
WO (1) WO2023184542A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190394084A1 (en) * 2018-06-20 2019-12-26 Industrial Technology Research Institute Network link topology adaptation method for intergrated access and backhaul node and intergrated access and backhaul node using the same
CN111526543A (zh) * 2019-02-02 2020-08-11 索尼公司 电子设备、通信方法和存储介质
CN113630815A (zh) * 2020-05-06 2021-11-09 索尼公司 电子设备、无线通信方法和计算机可读存储介质
CN114071617A (zh) * 2020-08-07 2022-02-18 大唐移动通信设备有限公司 Iab节点组切换中的信息传输方法、装置、网络设备及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190394084A1 (en) * 2018-06-20 2019-12-26 Industrial Technology Research Institute Network link topology adaptation method for intergrated access and backhaul node and intergrated access and backhaul node using the same
CN111526543A (zh) * 2019-02-02 2020-08-11 索尼公司 电子设备、通信方法和存储介质
CN113630815A (zh) * 2020-05-06 2021-11-09 索尼公司 电子设备、无线通信方法和计算机可读存储介质
WO2021223666A1 (zh) * 2020-05-06 2021-11-11 索尼集团公司 电子设备、无线通信方法和计算机可读存储介质
CN114071617A (zh) * 2020-08-07 2022-02-18 大唐移动通信设备有限公司 Iab节点组切换中的信息传输方法、装置、网络设备及系统

Similar Documents

Publication Publication Date Title
US11510131B2 (en) Configuration method, data transmission method, and apparatus
JP7516578B2 (ja) Ｉａｂネットワーク通信方法及び関連デバイス
WO2022082690A1 (zh) 群组切换的方法、装置和系统
WO2022236644A1 (zh) 发送和接收信号的方法、装置和通信系统
WO2023010364A1 (zh) 集成的接入和回传的通信装置以及方法
WO2023184542A1 (zh) 配置信息的方法、装置和通信系统
WO2022167611A1 (en) Handover technique for time-sensitive networking
WO2023197105A1 (zh) 配置信息的方法、装置和通信系统
WO2023197185A1 (zh) Iab节点设备、iab宿主设备以及传输地址确定方法
WO2023197184A1 (zh) Iab宿主设备以及传输地址配置方法
WO2024026804A1 (zh) 移动节点的配置方法、移动节点和宿主设备
WO2024026803A1 (zh) 移动节点的配置方法和宿主设备
WO2024164214A1 (zh) 信息处理方法和装置
WO2024207363A1 (zh) 信号的收发方法、装置和通信系统
WO2022205251A1 (zh) 信息收发方法，数据发送方法以及装置
WO2023150975A1 (zh) Iab宿主设备以及传输迁移回退方法
WO2023150974A1 (zh) Iab宿主设备以及传输迁移管理方法
WO2023150968A1 (zh) 收发信号的方法、装置和通信系统
WO2022205485A1 (zh) 信息收发方法以及装置
WO2023150976A1 (zh) Iab宿主设备以及传输迁移管理方法
WO2023130232A1 (zh) Iab节点设备、iab宿主设备以及路径迁移方法
US20240349166A1 (en) Iab-node device, iab-donor device and topology revoking method
WO2023205941A1 (zh) 信息的发送、接收、配置方法以及装置和通信系统
WO2022205326A1 (en) Integrated access and backhaul donor migration methods and systems
WO2024207361A1 (zh) 分布式单元迁移的方法、控制装置和通信系统

Legal Events

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

Ref document number: 22934369

Country of ref document: EP

Kind code of ref document: A1