WO2023197185A1 - Iab节点设备、iab宿主设备以及传输地址确定方法 - Google Patents

Iab节点设备、iab宿主设备以及传输地址确定方法 Download PDF

Info

Publication number
WO2023197185A1
WO2023197185A1 PCT/CN2022/086455 CN2022086455W WO2023197185A1 WO 2023197185 A1 WO2023197185 A1 WO 2023197185A1 CN 2022086455 W CN2022086455 W CN 2022086455W WO 2023197185 A1 WO2023197185 A1 WO 2023197185A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
reconfiguration message
rrc reconfiguration
address
host
Prior art date
Application number
PCT/CN2022/086455
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/086455 priority Critical patent/WO2023197185A1/zh
Publication of WO2023197185A1 publication Critical patent/WO2023197185A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/06—Reselecting a communication resource in the serving access point

Definitions

  • the embodiments of this application relate to the field of communications.
  • Ultra-dense networks are one of the goals of 5G. Deploying an NR network without wired backhaul is crucial to achieving ultra-dense 5G. Networking is very important. Since 5G millimeter wave reduces cell coverage, the wireless self-backhaul system requires multiple hops to meet deployment requirements. 5G's high bandwidth, massive multiple-input multiple-output (MIMO), and beam systems make it easier than LTE to develop wireless self-backhaul systems for ultra-dense NR cells. In order to develop this multi-hop system with wireless self-backhaul, 3GPP started the research and standardization of the Integrated access and backhaul (IAB) project in Rel-16.
  • IAB Integrated access and backhaul
  • FIG 1 is a schematic diagram of the IAB system.
  • access and backhaul use NR Uu air interface wireless transmission
  • the relay node supports both access and backhaul functions.
  • the relay node multiplexes the access link and the backhaul link in the time domain, frequency domain or air domain.
  • the access link and the backhaul link can use the same or different frequency bands.
  • the relay node refers to the IAB-node (IAB node), which supports both access and backhaul functions.
  • IAB node The last hop access node on the network side is called IAB-donnor (IAB host), which supports gNB function and IAB-node access. All UE data can be transmitted back to the IAB-donor via the IAB-node through one or more hops.
  • IAB-node The function of IAB-node is divided into two parts. One part is the gNB-DU function, called IAB-DU (distribution unit), and the other part is the UE function, called IAB-MT (mobile terminal).
  • IAB-DU implements network side device functions, connects to the downstream child IAB-node (child IAB node or simply child node), provides NR air interface access to UE and downstream child IAB-node and communicates with IAB donor-CU (host centralized An F1 connection is established between units).
  • IAB-MT implements some terminal equipment functions and is connected to the upstream parent IAB-node (parent IAB node or simply parent node) or IAB donor-DU.
  • IAB-MT includes physical layer, layer 2, RRC (Radio Resource Control, wireless Resource Control) and NAS (Non-Access Stratum, non-access layer) layer functions are also indirectly connected to IAB Donor-CU and Core Network (Core Network, CN).
  • IAB-node can access the network through independent networking (SA, Standalone) mode or non-independent networking (EN-DC, E-UTRA-NRDualConnectivity) mode.
  • SA independent networking
  • EN-DC non-independent networking
  • Figure 2 is a schematic diagram of the IAB architecture in SA mode.
  • Figure 3 is a schematic diagram of the IAB architecture in EN-DC mode.
  • FIG 4 is a schematic diagram of an IAB node (IAB-node), parent node (parent IAB-node) and child node (child IAB-node).
  • IAB-node IAB node
  • parent IAB-node parent node
  • child IAB-node child node
  • the IAB-DU of the IAB node is connected to the IAB-MT of the child node as the network side
  • the IAB-MT of the IAB node is connected to the IAB-DU of the parent node as the terminal side.
  • Figure 5 is a schematic diagram of the F1 user plane (F1-U) protocol stack between IAB-DU and IAB donor-CU.
  • Figure 6 is a schematic diagram of the F1 control plane (F1-C) protocol stack between IAB-DU and IAB donor-CU.
  • F1-U and F1-C are built on the transport (IP) layer between IAB-DU and IAB donor-CU. In Figures 5 and 6, they pass through two-hop wireless backhaul. and one-hop wired backhaul.
  • the transport (IP) layer is carried on the backhaul adaptive protocol (BAP) sublayer.
  • BAP adaptive protocol
  • the BAP entity in the IAB-node implements the routing function of the IAB system, and the routing table is provided by the IAB donor-CU.
  • BAP PDU Protocol Data Unit
  • RLC Radio Link Control
  • Multiple RLC channels of the backhaul link can be configured by the IAB-donor to carry different priorities and QoS (Quality of Service). ) service, the BAP entity maps the BAP PDU to different return RLC channels.
  • embodiments of the present application provide an IAB node device, an IAB host device, and a transmission address determination method.
  • an integrated access and backhaul IAB node device includes:
  • a first receiving unit that receives a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
  • an integrated access and backhaul IAB host device is provided, applied to the first IAB host, and the device includes:
  • a first sending unit that sends a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; or, sends at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of the F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain;
  • the F1 connection of the IAB node terminates at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
  • an integrated access and backhaul IAB host device is provided, applied to the second IAB host, and the device includes:
  • the second sending unit sends a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; or sends at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
  • the F1 connection of the IAB node terminates at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
  • the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message.
  • the IAB node can use the IP address of the non-F1 termination point topology domain.
  • the IP address of the F1 termination point topology domain can be used.
  • FIG. 1 is a schematic diagram of the IAB system
  • FIG. 2 is a schematic diagram of the IAB architecture in SA mode
  • Figure 3 is a schematic diagram of the IAB architecture in EN-DC mode
  • Figure 4 is a schematic diagram of the parent node (parent IAB-node) and the child node (child IAB-node);
  • Figure 5 is a schematic diagram of the F1-U protocol stack of the IAB system
  • Figure 6 is a schematic diagram of the F1-C protocol stack of the IAB system
  • Figure 7 is a schematic diagram of IAB system routing
  • Figure 8 is a schematic diagram of network topology adaptation
  • FIG. 9 is a schematic diagram of an IAB device according to an embodiment of the present application.
  • Figure 10 is a schematic diagram of a transmission address determination method according to an embodiment of the present application.
  • Figure 11 is a schematic diagram of the switching scene
  • Figure 12 is a schematic diagram of dual connection scenario one
  • Figure 13 is a schematic diagram of dual connection scenario 2;
  • Figure 14 is a schematic diagram of a transmission address determination method according to an embodiment of the present application.
  • Figure 15 is a schematic diagram of a transmission address determination method according to an embodiment of the present application.
  • FIG. 16 is a schematic diagram of the IAB node device according to the embodiment of the present application.
  • FIG. 17 is a schematic diagram of an IAB host device according to an embodiment of the present application.
  • Figure 18 is a schematic diagram of an IAB host 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
  • the communication between devices in the communication system can be carried out according to the communication protocol at any stage.
  • it can include but is not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and the future. 5G, 6G, 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: base station (BS, Base Station), access point (AP, Access Point), transmission and reception 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.
  • 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 femto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay or low-power node such as femto, 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” refers to a device that accesses a communication network through a network device and receives network services, and may also be called a "Terminal Equipment” (TE, Terminal Equipment).
  • Terminal equipment can be fixed or mobile, and can also be called mobile station (MS, Mobile Station), terminal, user, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), station, etc. wait.
  • 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
  • the signaling radio bearer SRBs include SRB0, SRB1, SRB2, and SRB3. Among them, SRB0, SRB1, and SRB2 are leading to the MN, and SRB3 is leading to the SN.
  • the signaling radio bearer is the radio bearer used to transmit RRC and NAS messages.
  • SRB0 transmits RRC messages using the common control channel (CCCH) logical channel.
  • SRB1 transmits RRC messages (which may include piggybacked NAS messages) and NAS messages before SRB2 is established, using the dedicated control channel (DCCH) logical channel.
  • SRB2 transmits NAS messages and RRC messages containing log measurement messages, using the DCCH logical channel.
  • SRB2 has a lower priority than SRB1 and can be configured by the network after the access stratum (AS) security is activated.
  • SRB3 is used for specific RRC messages when the UE is in (NG)EN-DC or NR-DC, using the DCCH logical channel.
  • the routing function of the IAB system is implemented by the BAP layer.
  • Each IAB-node node saves routing configuration (BH routing configuration) and RLC channel mapping configuration (BH RLC Channel Mapping Configuration).
  • the BAP entity performs routing according to the routing configuration, RLC channel mapping configuration and the routing ID (Routing ID) in the BAP layer data packet header. Routing ID contains the destination BAP address and path identifier.
  • the routing configuration includes the mapping relationship between the Routing ID and the BAP address of the next-hop node.
  • the RLC channel mapping configuration includes the mapping relationship between the BAP address of the previous hop (prior-hop) node, the RLC channel ID of the ingress link, and the BAP address of the next hop node and the RLC channel ID of the egress link.
  • Figure 7 is a schematic diagram of IAB system routing.
  • the next hop node BAP address can be found from the routing configuration through the routing ID in the data packet header.
  • the BAP address of the previous hop node and the RLC channel ID of the ingress link are both known.
  • the egress link RLC channel ID can be found through RLC channel mapping configuration based on the previous hop node BAP address + ingress link RLC channel ID + next hop node BAP address.
  • IAB-donor DU saves routing configuration (BH routing configuration) and downlink RLC channel mapping configuration (Downlink Traffic to BH RLC Channel Mapping Configuration).
  • IAB-donor DU is routed based on the routing configuration, RLC channel mapping configuration, and the Routing ID in the BAP layer packet header.
  • Routing configuration includes the mapping relationship between Routing ID and next hop node address.
  • the downlink RLC channel mapping configuration includes the mapping relationship between the target IP address, DSCP (Differentiated Services Code Point, Differentiated Services Code Point), and next-hop node address and egress link RLC channel ID.
  • IAB-donor DU For each downlink data packet arriving at IAB-donor DU, IAB-donor DU can find the next hop node address from the routing configuration based on the Routing ID in the data packet header. In this way, after the next hop node address is determined, the egress link RLC channel ID is found from the downlink RLC channel mapping configuration based on the IP address and DSCP of the data packet.
  • the access IAB node stores uplink return information (BH information), including the routing ID used by the service, the uplink return RLC channel ID and the next hop node address.
  • the access IAB node configures the routing ID in the BAP layer data packet header of the uplink service based on the uplink BH information and selects the BH RLC channel and next hop node for uplink service transmission.
  • Figure 8 is a schematic diagram of intra-CU topology adaptation.
  • the donor-CU configures the path migration-related configuration for the IAB-node through the RRC reconfiguration message, so that the IAB-node migrates the F1 transmission path. .
  • Configurations related to path migration include updates to the default return RLC channel (default BH RLC channel) for upstream F1-C, F1-U and non-F1 data, updates to the default BAP routing ID (default BAP routing ID), and updates to Update of IP address routed to Donor-DU.
  • the IAB-node When the IAB-node is connected to a new parent node, it starts to apply the above path migration-related configurations. For the child nodes of the IAB-node, the path migration-related configurations are also performed through the same method.
  • 3GPP Rel-17 supports the network topology update and backhaul (BH) wireless link failure (RLF, Radio Link Failure) recovery process when the IAB-node moves under different donor-CU.
  • the IAB-node can start from the source donor-CU (Also known as F1-terminating CU or first donor-CU)
  • the parent node of the service is switched or reestablished to the target donor-CU (Also known as non-F1-terminating CU or second donor-CU)
  • the parent node of the service Node all services of IAB-node (and the services of its sub-nodes) need to be migrated to the non-F1-terminating CU topology.
  • Rel-17 also supports the topology redundancy process when IAB-node and non-F1-terminating CU establish dual connections. The transmission path of some services of IAB-node can be migrated to non-F1-terminating CU topology.
  • IAB-node switches/RLF restores from donor-CU 1 (F1-terminating CU) to donor-CU 2 (non-F1-terminating CU), or after adding an RRC connection with donor-CU 2, only IAB-MT RRC is connected to donor-CU 2, and the F1 interface still terminates at donor-CU 1.
  • IAB-node can also be called boundary node.
  • the RRC connection and F1 interface of the sub-node it serves still belong to donor-CU1, so the routing ID, BH RLC channel and next-hop BAP address of the sub-node service still belong to the F1-terminating topology domain.
  • the routing IDs of all or part of the Boundary node's services will belong to the non-F1-terminating topology domain, that is, the boundary node needs to simultaneously transmit services whose routing IDs belong to the F1-terminating topology domain and services whose routing IDs belong to the non-F1-terminating topology domain. .
  • the boundary node needs to simultaneously transmit services whose routing IDs belong to the F1-terminating topology domain and services whose routing IDs belong to the non-F1-terminating topology domain.
  • the IAB node device includes a migration node or its child node.
  • “resources for serving the services of the IAB node have been established in the topology domain of the donor-CU” may also be referred to as “the services of the IAB node are migrated to the topology domain of the donor-CU", etc. This application is not limited to these expressions. The embodiments of the present application will be further described below.
  • the embodiment of this application provides a method for determining a transmission address, which is explained from the perspective of an IAB node device.
  • Figure 10 is a schematic diagram of a transmission address determination method according to an embodiment of the present application. As shown in Figure 10, the method includes:
  • the IAB node receives the first RRC reconfiguration message.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; the at least one IP address configuration includes the IP address information of the F1 termination point topology domain, Or contain IP address information of non-F1 termination point topological domains.
  • the boundary node Due to the routing ID for the non-F1-terminating topology domain, the boundary node needs to use the IP address of the non-F1-terminating topology domain, that is, the IP address of the donor-DU anchored in the non-F1-terminating topology domain; for F1 -terminating topology domain routing ID, you need to use the IP address of the F1-terminating topology domain, that is, the IP address of the donor-DU anchored in the F1-terminating topology domain.
  • the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message. In this way, the boundary node can separately transmit the routing ID belonging to Services in the F1-terminating topology domain and routing IDs belong to the services in the non-F1-terminating topology domain.
  • the IAB node includes a migration node or its child node.
  • the IAB node when the IAB node is a migration node (also called a border node), the F1 connection of the IAB node terminates at the first IAB host (such as the first IAB donor). -CU), the IAB node has an RRC connection with the second IAB host (for example, the second IAB donor-CU).
  • the IAB-MT of the IAB node maintains an RRC connection with the second IAB host.
  • the first IAB host is also called the F1 termination point host (for example, F1 termination point donor-CU), and the second IAB host is also called the non-F1 termination point host.
  • non-F1 termination point donor-CU where the F1 termination point host refers to the IAB host that terminates the F1 interface of the boundary IAB node and its child IAB node, that is, the first IAB host.
  • Non-F1 termination point hosts refer to hosts with host functions that do not terminate the F1 interface of the boundary IAB node and its child IAB nodes, such as the second IAB host.
  • the IP address refers to the IP address configured for the IAB node and anchored to the donor-DU.
  • At least one IP address configuration in the first RRC reconfiguration message may be the IP address of at least two donor-DUs.
  • the address configuration may also be at least one IP address configuration of a donor-DU.
  • Each IP address configuration may include an IP address index and a corresponding IP address. The embodiments of this application are not limited to this.
  • IP address anchored to IAB donor-DU can be understood as “IP address assigned by donor-DU” or “routable via donor-DU”.
  • Transport Network Layer (TNL) address (TNL address(es) that is(are)routable via the IAB-donor-DU)" the above terms can be replaced with each other, this application is not limited to this, for example, non-F1 configured for the IAB node
  • the IP address of the donor-DU of the termination point topology domain refers to the transport network layer (TNL) address configured for the IAB node that is routable via the donor-DU of the non-F1 termination point topology domain.
  • the method may further include:
  • the IAB node determines that the IP address configuration contains the IP address information of the F1 termination point topology domain or the IP address information of the non-F1 termination point topology domain.
  • the IAB node may determine, based on the host that provides the IP address information, that the IP address configuration includes the F1 termination point topology domain. IP address information or IP address information of a non-F1 termination point topology domain. For example, when the host providing IP address information is an F1 termination point host, make sure the IP address configuration contains the IP address information of the F1 termination point topology domain. When the host providing IP address information is a non-F1 termination point host, make sure the IP address configuration contains non-F1 IP address information of the termination point topology domain.
  • whether the configured IP address belongs to the non-F1 termination point topology domain may be explicitly indicated (for example, explicitly indicated based on the first indication information).
  • the IAB node may determine the IP address based on the first indication information.
  • the address configuration contains the IP address information of the F1 termination point topology domain or the IP address information of the non-F1 termination point topology domain.
  • the first indication information is used to indicate that the IP address configuration includes the IP address information of the non-F1 termination point topology domain.
  • the IAB node determines that the IP address configuration includes the IP address information of the non-F1 termination point topology domain.
  • the IAB node can distinguish whether the configured IP address is a non-F1 termination point topology domain or an F1 termination point topology domain.
  • Figure 11 is a schematic diagram of a switching scenario.
  • the F1 termination point host is the source host of the IAB node switching.
  • the non-F1 termination point host is the target host for the IAB node switching.
  • the first RRC reconfiguration message is a handover command RRC message forwarded by the first IAB host and generated by the second IAB host.
  • the first RRC reconfiguration message is an RRC message sent directly by the second IAB host to the IAB node.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.
  • the at least one IP The address configuration contains the IP address information of the non-F1 termination point topology domain.
  • the IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2.
  • the at least one IP address configuration may be carried by a handover command RRC message, for example, it may be the at least one IP address configuration carried in the RRC reconfiguration information of the reconfigurationWithSync information field in the primary cell group information.
  • the IAB node may determine that at least one IP address configuration configured by the handover command RRC message contains IP address information for a non-F1 termination point topology domain, or the IAB node may determine that at least one IP address configuration in the RRC message sent by the target host contains non-F1 termination IP address information of the point topology domain.
  • the IAB node receives the handover command RRC message. After receiving the message, it can be determined that at least one IP address configuration carried by the switching command RRC message is the IP address information of a non-F1 termination point topology domain.
  • the target host can directly send an RRC message to the IAB node.
  • the IAB node can determine that at least one IP address configuration carried by the RRC message is an IP address in a non-F1 termination point topology domain. information.
  • the target host when the target host generates the handover command RRC message, it can introduce a new information element into it, that is, the first indication information non-F1-terminating. Therefore, the IAB node receives the handover command RRC message. Later, that is, when the handover command RRC message contains the first indication information, it is determined that at least one IP address configuration carried by the handover command RRC message is the IP address information of a non-F1 termination point topology domain.
  • the target host can directly send an RRC message to the IAB node, in which a new information element can be introduced, that is, the first indication information non-F1-terminating-Indication.
  • the IAB node Later, that is, when the handover command RRC message contains the first indication information, it can be determined that at least one IP address configuration carried by the RRC message is the IP address information of a non-F1 termination point topology domain.
  • the first indication information may be included in a new information element of the RRC reconfiguration message, or in an IP address configuration list information element of the RRC reconfiguration message, or in an RRC reconfiguration message.
  • IP address configuration information element or included in the IP address index information element of the RRC reconfiguration message. Examples are given below.
  • the first RRC reconfiguration message can be expressed as: using abstract syntax notation ASN.1 data format:
  • the IP address configuration list information element uses the abstract syntax markup ASN.1 data format and can be expressed as:
  • the IP address configuration information element uses the abstract syntax notation ASN.1 data format and can be expressed as:
  • IP address index information element can be expressed as: using abstract syntax notation ASN.1 data format:
  • the granularity of the indication can be based on each configured IP address information, and the indication method is more flexible.
  • Figure 12 is a schematic diagram of dual connection scenario one.
  • the first IAB host (F1 termination point host) is the main node MN of the IAB node
  • the second The IAB host (non-F1 termination point host) is the secondary node SN of the IAB node.
  • some services of the border node can be migrated to the non-F1 termination point topology domain.
  • Some services are still in the F1 termination point host topology domain.
  • the IP address of the non-F1 termination point topology domain is anchored to donor-DU2. IP address.
  • the IAB node may determine that the at least one IP address configuration in the RRC message received through SRB3 contains IP address information of a non-F1 termination point topology domain, or may determine that the secondary cell group configuration information received through SRB1
  • the at least one IP address configuration contains IP address information of a non-F1 termination point topology domain, or it can be determined that the at least one IP address configuration in the RRC message received through SRB1 contains IP address information of the F1 termination point topology domain.
  • the IAB node may determine that the at least one IP address configuration in the secondary cell group configuration information received through SRB1 contains IP address information of a non-F1 termination point topology domain when receiving the first indication information.
  • the first indication information it is determined that the at least one IP address configuration in the secondary cell group configuration information received through SRB1 contains the IP address information of the F1 termination point topology domain, which will be described in each case below.
  • the IP address of the non-F1 termination point topology domain is configured during the process of adding the secondary cell group.
  • the first RRC reconfiguration message is carried by the secondary cell group configuration (mrdc-SecondaryCellGroupConfig field) of the RRC reconfiguration message.
  • the RRC reconfiguration message is completely generated by the second host and carried by the second RRC reconfiguration message sent by the first IAB host; the IAB node receives the second RRC reconfiguration message sent by the first IAB host through SRB1.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.
  • the at least one IP address configuration includes IP address information of a non-F1 termination point topology domain.
  • the IP address of the non-F1 termination point topology domain refers to the anchor. Set to the IP address of donor-DU2.
  • the ASN.1 structure of the RRC reconfiguration message is as follows, which contains the secondary cell group configuration (mrdc-SecondaryCellGroupConfig field).
  • the SN For example, the SN generates a secondary cell group configuration RRC message and sends it to the MN in the secondary cell group addition response message.
  • the MN After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a second RRC reconfiguration message and adds the secondary cell group configuration RRC message to the MN.
  • the cell group configuration RRC message is placed in the mrdc-SecondaryCellGroupConfig field of the second RRC reconfiguration message and forwarded to the IAB node. Therefore, after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried in it.
  • the IAB node knows that the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field is generated by the SN. (That is, at least one IP address configuration is provided by SN), and SN is a non-F1 termination point. Therefore, the IAB node determines that at least one IP address configuration carried by the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig domain is the IP of a non-F1 termination point topology domain. Address information.
  • the IAB node determines that at least one IP address configuration in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig domain received through SRB1 contains IP address information of a non-F1 termination point topology domain.
  • the SN when the SN generates the secondary cell group configuration RRC message, it can introduce a new information element into it, that is, the first indication information non-F1-terminating, and send it to the MN in the secondary cell group addition response message.
  • a second RRC reconfiguration message is generated, and the secondary cell group configuration RRC message is placed in the mrdc-SecondaryCellGroupConfig field in the second RRC reconfiguration message and forwarded to the IAB node.
  • the IAB node can obtain the RRC reconfiguration message of the mrdc-SecondaryCellGroupConfig domain carried therein and the first indication information contained therein, so the IAB node determines the mrdc-SecondaryCellGroupConfig domain.
  • At least one IP address configuration carried by the RRC reconfiguration message is the IP address information of the non-F1 termination point topology domain.
  • the example of introducing the first indication information into the secondary cell group configuration RRC message is similar to the above-mentioned 1)-4), and will not be described again here.
  • the SN generates a secondary cell group configuration RRC message and sends it to the MN in a secondary cell group addition response message.
  • the MN After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a second RRC reconfiguration message, which can be in the second RRC reconfiguration message.
  • a new information element is introduced into the second RRC reconfiguration message, that is, the first indication information non-F1-terminating, and the secondary cell group configuration RRC message is placed in the second RRC reconfiguration message and forwarded to the IAB node. Therefore, after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message of the mrdc-SecondaryCellGroupConfig domain carried in it and the first indication information.
  • the IAB node determines the RRC reconfiguration message of the mrdc-SecondaryCellGroupConfig domain.
  • At least one IP address configuration carried by the configuration message is IP address information of a non-F1 termination point topology domain.
  • the example in which the second RRC reconfiguration message introduces the first indication information is similar to the above 1), except that when generating the second RRC reconfiguration message, it may not include its own information element iab-IP- configured with the IP address. AddressConfigurationList-r16.
  • the IP address of the non-F1 termination point topology domain may be configured (modified) after the dual connection establishment is completed.
  • the first RRC reconfiguration message is sent directly to the IAB node by the second IAB host; the IAB node receives the first RRC reconfiguration message sent by the second IAB host through SRB3.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.
  • the at least one IP address configuration includes IP address information of a non-F1 termination point topology domain.
  • the IP address of the non-F1 termination point topology domain refers to the anchor. Set to the IP address of donor-DU2.
  • the IAB node receives the first RRC reconfiguration message through SRB3.
  • the IAB node knows that the first RRC reconfiguration message is generated by SN (that is, at least one IP address configuration is provided by SN), and SN is a non-F1 termination point. Therefore, The IAB node determines that at least one IP address configuration carried in the first RRC reconfiguration message is IP address information of a non-F1 termination point topology domain. That is, the IAB node determines that at least one IP address configuration in the first RRC reconfiguration message received through SRB1 contains IP address information of a non-F1 termination point topology domain.
  • the IAB node receives the first RRC reconfiguration message and the first RRC reconfiguration message through SRB3. An indication information, so the IAB node determines that at least one IP address configuration carried in the first RRC reconfiguration message is the IP address information of a non-F1 termination point topology domain.
  • the example in which the first RRC reconfiguration message introduces the first indication information is similar to the above-mentioned 1)-4), and will not be described again here.
  • the IP address of the non-F1 termination point topology domain can be configured (modified) in the process of modifying the secondary cell group.
  • the first RRC reconfiguration message is an RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig domain, and is carried by the second RRC reconfiguration message sent by the first IAB host; the IAB node receives it through SRB1 and is sent by the first IAB host. the second RRC reconfiguration message.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.
  • the at least one IP address configuration includes IP address information of a non-F1 termination point topology domain.
  • the IP address of the non-F1 termination point topology domain refers to the anchor. Set to the IP address of donor-DU2.
  • the SN For example, the SN generates a secondary cell group configuration RRC message and puts it in the secondary cell group modification request message and sends it to the MN.
  • the MN After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a second RRC reconfiguration message and adds the second RRC reconfiguration message to the MN.
  • the secondary cell group configuration RRC message is placed in the mrdc-SecondaryCellGroupConfig field in the second RRC reconfiguration message and forwarded to the IAB node. Therefore, after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried in it.
  • the IAB node knows that the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field is generated by the SN. (That is, at least one IP address configuration is provided by the SN), and the SN is a non-F1 termination point. Therefore, the IAB node determines that at least one IP address configuration carried by the secondary cell group configuration RRC message is the IP address information of the non-F1 termination point topology domain. That is to say, the IAB node determines that at least one IP address configuration in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig domain received through SRB1 contains IP address information of a non-F1 termination point topology domain.
  • the SN when the SN generates a secondary cell group configuration RRC message, it can introduce a new information element into it, that is, the first indication information non-F1-terminating, and put it in the secondary cell group modification request message and send it to the MN.
  • the MN After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a second RRC reconfiguration message, and places the secondary cell group configuration RRC message in the mrdc-SecondaryCellGroupConfig field in the second RRC reconfiguration message and forwards it to the IAB node.
  • the IAB node after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried therein and the first indication information carried therein, so the IAB node determines that the mrdc- At least one IP address configuration carried by the RRC reconfiguration message contained in the SecondaryCellGroupConfig domain is the IP address information of the non-F1 termination point topology domain.
  • the example of introducing the first indication information into the secondary cell group configuration RRC message is similar to the above-mentioned 1)-4), and will not be described again here.
  • the SN For example, the SN generates a secondary cell group configuration RRC message and puts it in the secondary cell group modification request message and sends it to the MN.
  • the MN After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a second RRC reconfiguration message.
  • a new information element is introduced into the second RRC reconfiguration message, that is, the first indication information non-F1-terminating.
  • the secondary cell group configuration RRC message is placed in the mrdc-SecondaryCellGroupConfig field of the second RRC reconfiguration message and forwarded to the IAB node. .
  • the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field and the first indication information. Therefore, the IAB node determines the RRC contained in the mrdc-SecondaryCellGroupConfig field.
  • At least one IP address configuration carried by the reconfiguration message is IP address information of a non-F1 termination point topology domain.
  • the example in which the second RRC reconfiguration message introduces the first indication information is similar to the above 1), except that when generating the second RRC reconfiguration message, it may not include its own information element iab-IP- configured with the IP address. AddressConfigurationList-r16.
  • the IP address of the non-F1 termination point topology domain can be reconfigured during the IAB transmission migration management process and sent by the MN to the IAB node.
  • the first RRC reconfiguration message is an RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field. Since the IAB transmission migration management process does not support the SN to generate a secondary cell group configuration RRC message, the first RRC reconfiguration message is sent by the first RRC reconfiguration message.
  • the IAB host is generated on behalf of the second IAB host and carried by the second RRC reconfiguration message sent by the first IAB host.
  • the IAB node receives the second RRC reconfiguration message sent by the first IAB host through SRB1.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.
  • the at least one IP address configuration includes IP address information of a non-F1 termination point topology domain.
  • the IP address of the non-F1 termination point topology domain refers to the anchor. Set to the IP address of donor-DU2.
  • the SN provides at least one IP address configuration and sends it to the MN in the IAB transmission migration management response message.
  • the MN After receiving the at least one IP address configuration, the MN generates a first RRC reconfiguration message on behalf of the second IAB host, and transfers the first RRC reconfiguration message to the MN.
  • the first RRC reconfiguration message is placed in the second RRC reconfiguration message and forwarded to the IAB node. Therefore, after receiving the second RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried in it.
  • the IAB node knows that at least one of the RRC reconfiguration messages contained in the mrdc-SecondaryCellGroupConfig field An IP address configuration is provided by the SN, and the SN is a non-F1 termination point. Therefore, the IAB node determines that at least one IP address configuration carried by the secondary cell group configuration RRC message is the IP address information of the non-F1 termination point topology domain. That is to say, the IAB node determines that at least one IP address configuration in the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig domain received through SRB1 contains IP address information of a non-F1 termination point topology domain.
  • the SN provides at least one IP address configuration to the MN, and the first RRC reconfiguration message is generated by the MN; the IAB node receives the second RRC reconfiguration message sent by the first IAB host through SRB1.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.
  • the at least one IP address configuration includes IP address information of a non-F1 termination point topology domain.
  • the IP address of the non-F1 termination point topology domain refers to the anchor. Set to the IP address of donor-DU2.
  • the SN provides at least one IP address configuration and sends it to the MN in the IAB transmission migration management response message.
  • the MN After receiving the at least one IP address configuration, the MN generates a first RRC reconfiguration message, in which new information elements can be introduced. , that is, the first indication information non-F1-terminating, sends the first RRC reconfiguration message to the IAB node. Therefore, after receiving the first RRC reconfiguration message through SRB1, the IAB node can obtain at least one of the The IP address information and the first indication information, therefore the IAB node determines that at least one IP address configuration carried in the first RRC reconfiguration message is the IP address information of a non-F1 termination point topology domain.
  • the example in which the first RRC reconfiguration message introduces the first indication information is similar to the above-mentioned 1)-4), and will not be described again here.
  • the IP address of the non-F1 termination point topology domain can be reconfigured during the IAB transmission migration management process.
  • the first RRC reconfiguration message is generated by the SN and is sent by the second IAB host. Directly sent to the IAB node; the IAB node receives the first RRC reconfiguration message sent by the second IAB host through SRB3.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.
  • the at least one IP address configuration includes IP address information of a non-F1 termination point topology domain.
  • the IP address of the non-F1 termination point topology domain refers to the anchor. Set to the IP address of donor-DU2.
  • the IAB node receives the first RRC reconfiguration message through SRB3.
  • the IAB node knows that the first RRC reconfiguration message is generated by SN (that is, at least one IP address configuration is provided by SN), and SN is a non-F1 termination point. Therefore, The IAB node determines that at least one IP address configuration carried in the first RRC reconfiguration message is IP address information of a non-F1 termination point topology domain. That is, the IAB node determines that at least one IP address configuration in the first RRC reconfiguration message received through SRB1 contains IP address information of a non-F1 termination point topology domain.
  • the IAB node receives the first RRC reconfiguration message and the first RRC reconfiguration message through SRB3. An indication information, so the IAB node determines that at least one IP address configuration carried in the first RRC reconfiguration message is the IP address information of a non-F1 termination point topology domain.
  • the first RR example is similar to the aforementioned 1)-4) and will not be described again here.
  • the IP address of the F1 termination point topology domain can be configured (modified) in the process of modifying the secondary cell group.
  • the first RRC reconfiguration message is generated by the MN and sent directly to the IAB node by the first IAB host; the IAB node receives the first RRC reconfiguration message sent by the first IAB host through SRB1.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.
  • the at least one IP address configuration includes IP address information of the F1 termination point topology domain.
  • the IP address of the F1 termination point topology domain refers to the IP address anchored to The IP address of donor-DU1.
  • the IAB node receives the first RRC reconfiguration message through SRB1, and the IAB node knows that the first RRC reconfiguration message is generated by the MN (that is, at least one IP address configuration is provided by the MN), and the MN is the F1 termination point, so The IAB node determines that at least one IP address configuration carried in the first RRC reconfiguration message is the IP address information of the F1 termination point topology domain. That is, the IAB node determines that at least one IP address configuration in the first RRC reconfiguration message received through SRB1 contains IP address information of the F1 termination point topology domain.
  • the MN when the MN generates the first RRC reconfiguration message, it does not need to introduce a new information element, that is, the first indication information non-F1-terminating.
  • the IAB node receives the first RRC reconfiguration message through SRB1. Since there is The first indication information is not included, that is, the IAB node does not receive the first indication information. Therefore, the IAB node determines that at least one IP address configuration carried by the first RRC reconfiguration message is the IP address information of the F1 termination point topology domain.
  • Figure 13 is a schematic diagram of dual connection scenario two.
  • the first IAB host (F1 termination point host) is the main node SN of the IAB node
  • the second IAB The host (the non-F1 termination point host) is the secondary node MN of the IAB node.
  • the IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU1
  • the IP address of the F1 termination point topology domain refers to the IP address anchored to donor-DU2.
  • the IP address of the non-F1 termination point topology domain cannot be configured during the dual connection establishment process. It can only be configured after the dual connection is established. Configure the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain.
  • the IAB node may determine that the at least one IP address configuration in the RRC message received through SRB1 contains IP address information of a non-F1 termination point topology domain, or may determine that the secondary cell group configuration information received through SRB1
  • the at least one IP address configuration includes the IP address information of the F1 termination point topology domain, or it may be determined that the at least one IP address configuration in the RRC message received through SRB3 includes the IP address information of the F1 termination point topology domain.
  • the IAB node may determine that the at least one IP address configuration in the first RRC reconfiguration message contains IP address information of a non-F1 termination point topology domain when receiving the first indication information. When indicating the information, it is determined that the at least one IP address configuration in the first RRC reconfiguration message contains the IP address information of the F1 termination point topology domain, which will be described in each case below.
  • the IP address of the non-F1 termination point topology domain may be configured (modified) after the dual connection establishment is completed.
  • the first RRC reconfiguration message is sent by the second IAB host to the IAB node; the IAB node receives the first RRC reconfiguration message sent by the second IAB host through SRB1.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.
  • the at least one IP address configuration includes IP address information of a non-F1 termination point topology domain.
  • the IP address of the non-F1 termination point topology domain refers to the anchor. Set to the IP address of donor-DU1.
  • the IAB node receives the first RRC reconfiguration message through SRB1.
  • the IAB node knows that the first RRC reconfiguration message is generated by the MN (that is, at least one IP address configuration is provided by the MN), and the MN is a non-F1 termination point. Therefore, The IAB node determines that at least one IP address configuration carried in the first RRC reconfiguration message is IP address information of a non-F1 termination point topology domain. That is, the IAB node determines that at least one IP address configuration in the first RRC reconfiguration message received through SRB1 contains IP address information of a non-F1 termination point topology domain.
  • the MN when the MN generates the first RRC reconfiguration message, it can introduce a new information element into it, that is, the first indication information non-F1-terminating.
  • the IAB node receives the first RRC reconfiguration message and the first RRC reconfiguration message through SRB1.
  • An indication information so the IAB node determines that at least one IP address configuration carried in the first RRC reconfiguration message is the IP address information of a non-F1 termination point topology domain.
  • the example in which the first RRC reconfiguration message introduces the first indication information is similar to the above-mentioned 1)-4), and will not be described again here.
  • the IP address of the F1 termination point topology domain can be configured (modified) in the process of modifying the secondary cell group.
  • the first RRC reconfiguration message is generated by the first IAB host; the IAB node receives the first RRC reconfiguration message sent by the first IAB host through SRB3.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.
  • the at least one IP address configuration includes IP address information of the F1 termination point topology domain.
  • the IP address of the F1 termination point topology domain refers to the IP address anchored to The IP address of donor-DU2.
  • the IAB node receives the first RRC reconfiguration message through SRB3.
  • the IAB node knows that the first RRC reconfiguration message is generated by SN (that is, at least one IP address configuration is provided by SN), and SN is the F1 termination point, so
  • the IAB node determines that at least one IP address configuration carried in the first RRC reconfiguration message is the IP address information of the F1 termination point topology domain. That is, the IAB node determines that at least one IP address configuration in the first RRC reconfiguration message received through SRB3 contains IP address information of the F1 termination point topology domain.
  • the IAB node receives the first RRC reconfiguration message through SRB3. Since the IAB The node does not receive the first indication information, and therefore determines that at least one IP address configuration in the first RRC reconfiguration message received through SRB3 contains IP address information of the F1 termination point topology domain.
  • the IP address of the F1 termination point topology domain can be configured (modified) in the process of modifying the secondary cell group.
  • the first RRC reconfiguration message is an RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field of the RRC reconfiguration message, which is completely generated by the first IAB host and carried by the third RRC reconfiguration message sent by the second IAB host; the IAB The node receives the third RRC reconfiguration message sent by the second IAB host through SRB1.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.
  • the at least one IP address configuration includes IP address information of the F1 termination point topology domain.
  • the IP address of the F1 termination point topology domain refers to the IP address anchored to The IP address of donor-DU2.
  • the SN For example, the SN generates a secondary cell group configuration RRC message and puts it in the secondary cell group modification request message and sends it to the MN.
  • the MN After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a third RRC reconfiguration message and adds the message to the MN.
  • the secondary cell group configuration RRC message is placed in the mrdc-SecondaryCellGroupConfig field in the third RRC reconfiguration message and forwarded to the IAB node. Therefore, after receiving the third RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried in it.
  • the IAB node knows that the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field is generated by the SN. (That is, at least one IP address configuration is provided by SN), and SN is the F1 termination point. Therefore, the IAB node determines that at least one IP address configuration carried by the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig domain is the IP of the F1 termination point topology domain. Address information. That is to say, the IAB node determines that at least one IP address configuration in the secondary cell group configuration RRC message received through SRB1 contains the IP address information of the F1 termination point topology domain.
  • the SN when the SN generates the secondary cell group configuration RRC message, it does not need to introduce a new information element into it, that is, the first indication information non-F1-terminating, and places the secondary cell group configuration RRC message in the secondary cell group modification requirement message. Sent to the MN. After receiving the secondary cell group configuration RRC message sent by the SN, the MN generates a third RRC reconfiguration message and puts the secondary cell group configuration RRC message in the third RRC reconfiguration message and forwards it in the mrdc-SecondaryCellGroupConfig field. to the IAB node.
  • the IAB node after receiving the third RRC reconfiguration message through SRB1, the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried in it, but because the first RRC reconfiguration message and the third RRC reconfiguration message contain None of them contain the first indication information, that is, the IAB node does not receive the first indication information. Therefore, the IAB node determines that at least one IP address configuration carried by the secondary cell group configuration RRC message is the IP address information of the F1 termination point topology domain.
  • the IP address of the non-F1 termination point topology domain can be configured (modified) during the IAB transmission migration management process.
  • the first RRC reconfiguration message is generated by the second IAB host. And sent to the IAB node by the second IAB host.
  • the IAB node receives the first RRC reconfiguration message sent by the second IAB host through SRB1.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.
  • the at least one IP address configuration includes IP address information of a non-F1 termination point topology domain.
  • the IP address of the non-F1 termination point topology domain refers to the anchor. Set to the IP address of donor-DU1.
  • the SN sends an IAB transmission migration management request message to the MN.
  • the MN (the second IAB host, not the F1 termination point host) generates a first RRC reconfiguration message, in which the at least one IP address configuration includes IP address information of the non-F1 termination point topology domain, and sends the first RRC reconfiguration message to the IAB node. Therefore, after receiving the first RRC reconfiguration message through SRB1, the IAB node can obtain at least one IP address configuration carried in it.
  • the IAB node knows that the at least one IP address configuration is provided by the MN, and the MN is a non-F1 termination point.
  • the IAB node determines that at least one IP address configuration carried by the first RRC reconfiguration message is IP address information of a non-F1 termination point topology domain. That is, the IAB node determines that at least one IP address configuration in the first RRC reconfiguration message received through SRB1 contains IP address information of a non-F1 termination point topology domain.
  • the SN sends an IAB transmission migration management request message to the MN.
  • the MN (the second IAB host, not the F1 termination point host) generates the first RRC reconfiguration message, in which new information elements can be introduced. , that is, the first indication information non-F1-terminating, sends the first RRC reconfiguration message to the IAB node. Therefore, after receiving the first RRC reconfiguration message through SRB1, the IAB node can obtain at least one of the The IP address information and the first indication information, therefore the IAB node determines that at least one IP address configuration carried in the first RRC reconfiguration message is the IP address information of a non-F1 termination point topology domain.
  • the example in which the first RRC reconfiguration message introduces the first indication information is similar to the above-mentioned 1)-4), and will not be described again here.
  • the IP address of the F1 termination point topology domain can be configured (modified) during the IAB transmission migration management process, and the first RRC reconfiguration message is replaced by the second IAB host. Generated by the IAB host and sent to the IAB node by the second IAB host. The IAB node receives the first RRC reconfiguration message sent by the second IAB host through SRB1.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node.
  • the at least one IP address configuration includes IP address information of the F1 termination point topology domain.
  • the IP address of the F1 termination point topology domain refers to the IP address anchored to The IP address of donor-DU2.
  • the SN provides at least one IP address configuration (including the IP address information of the F1 termination point topology domain) and sends it to the MN (second IAB host, non-F1 termination point host) in the IAB transmission migration modification request message.
  • the MN second IAB host, non-F1 termination point host
  • the request message After receiving the request message, generate a secondary cell configuration RRC message on behalf of the SN, in which the at least one IP address configuration contains the IP address information of the F1 termination point topology domain, and generate a third RRC reconfiguration message to reconfigure the first RRC
  • the message is placed in the mrdc-SecondaryCellGroupConfig field in the third RRC reconfiguration message and forwarded to the IAB node.
  • the IAB node can obtain the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field carried in it.
  • the IAB node knows that at least one of the RRC reconfiguration messages contained in the mrdc-SecondaryCellGroupConfig field
  • An IP address configuration is provided by the SN, and the SN is the F1 termination point host. Therefore, the IAB node determines that at least one IP address configuration carried in the first RRC reconfiguration message is the IP address information of the F1 termination point topology domain.
  • the IAB node determines that at least one IP address configuration of the RRC reconfiguration message contained in the mrdc-SecondaryCellGroupConfig field in the first RRC reconfiguration message received through SRB1 contains the IP address information of the F1 termination point topology field.
  • the SN provides at least one IP address configuration (including the IP address information of the F1 termination point topology domain), and sends it to the MN (second IAB host, non-F1 termination point host) in the IAB transmission migration modification request message.
  • the MN receives After the request message, a first RRC reconfiguration message is generated, wherein the at least one IP address configuration includes IP address information of the F1 termination point topology domain.
  • the first RRC reconfiguration message does not contain the first indication information, that is, the IAB node does not receive the first indication information, so the IAB node determines the RRC message.
  • At least one IP address configuration carried is the IP address information of the F1 termination point topology domain.
  • the IAB node can know whether the MN or SN is an F1 termination point host or a non-F1 termination point host. For example, the IAB node can know which host provides the received BAP configuration information (bap-config-r16 domain), thereby Determine whether MN or SN is the F1 termination point host.
  • whether the first indication information is received is used as an example to illustrate how to determine whether the configured IP address is a non-F1 termination point topology domain or an F1 termination point topology domain.
  • the first The indication information is used to indicate whether the IP address configuration contains IP address information of a non-F1 termination point topology domain, or the first indication information is used to indicate whether the IP address configuration contains IP address information of a non-F1 termination point topology domain or whether it contains an F1 termination point. IP address information of the topological domain.
  • the IAB when the IAB receives the first indication information, and the value of the first indication information is the first value (true or 1), it determines that the IP address configuration contains IP address information of a non-F1 termination point topology domain, and the first indication information When the value of is the second value (false or 0), it is determined that the IP address configuration includes the IP address information of the F1 termination point topology domain.
  • the specific process is the same as above, and no examples are given here.
  • the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message.
  • the boundary node can separately transmit the routing ID belonging to Services in the F1-terminating topology domain and routing IDs belong to the services in the non-F1-terminating topology domain.
  • the embodiment of the present application provides a transmission address determination method, which is explained from the first IAB host side. The same content as the embodiment of the first aspect will not be described again.
  • Figure 14 is another schematic diagram of a transmission address determination method according to an embodiment of the present application. As shown in Figure 14, the method includes:
  • the first IAB host sends a first RRC reconfiguration message.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; or sends at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of the F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain;
  • the first IAB host may send the first RRC reconfiguration message to the IAB node or the second IAB host, the F1 connection of the IAB node is terminated with the first IAB host, and the IAB node is connected to the second IAB host.
  • the second IAB host has an RRC connection.
  • whether the configured IP address belongs to the non-F1 termination point topology domain may be implicitly indicated, or whether the configured IP address belongs to the non-F1 termination point topology domain may be explicitly indicated.
  • the first IAB host passes The first indication information indicates that the IP address configuration includes IP address information of the F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
  • the IP address configuration contains IP address information for non-F1 termination point topology domains.
  • the first IAB host is the source host of the IAB node switch
  • the second IAB host is the target host of the IAB node switch
  • the first RRC reconfiguration message is a switch command RRC message; the method further It may include: the first IAB host receives the first RRC reconfiguration message sent by the second IAB host. In 1401, the first IAB host forwards the first RRC reconfiguration message generated by the second IAB host to the IAB node. Configuration message.
  • the first IAB host is the primary node MN of the IAB node
  • the second IAB host is the secondary node SN of the IAB node
  • the first RRC reconfiguration message is an RRC reconfiguration message contained in the secondary cell group configuration field in the RRC reconfiguration message and is carried by the second RRC reconfiguration message sent by the first IAB host; the first IAB host passes SRB1 sends the second RRC reconfiguration message to the IAB node.
  • the method also includes: the first IAB host receiving the first RRC reconfiguration message sent by the second IAB host (the first RRC reconfiguration message is generated by the second IAB host). And, in 1401, the first IAB host sends the second RRC reconfiguration message to the IAB node through SRB1 (the second RRC reconfiguration message is generated by the first IAB host), and the second RRC reconfiguration message carries The first RRC reconfiguration message.
  • the method may also include: the first IAB host receiving the IP address configuration provided by the second IAB host, and generating the first RRC reconfiguration message on behalf of the second IAB host, and, in 1401, the first An IAB host sends the second RRC reconfiguration message to the IAB node through SRB1 (the second RRC reconfiguration message is also generated by the first IAB host), and the second RRC reconfiguration message carries the first RRC reconfiguration message.
  • the method may also include: the first IAB host receives the IP address configuration provided by the second IAB host and generates a first RRC reconfiguration message.
  • the first IAB host sends a request to the IAB node through SRB1. Send the first RRC reconfiguration message.
  • the IP address configuration includes the IP address information of the non-F1 termination point topology domain.
  • the first IAB host includes the first RRC reconfiguration message or the second RRC reconfiguration message.
  • the first indication information indicates that the IP address configuration includes IP address information of a non-F1 dead-end topology domain.
  • the first indication information is included in the newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the IP of the first RRC reconfiguration message or the second RRC reconfiguration message.
  • the address configuration list information element is either included in the IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the first RRC reconfiguration message or the second RRC reconfiguration message.
  • the IP address of the message is indexed in the information element.
  • the IP address configuration contains IP address information for the F1 termination point topology domain.
  • the first IAB host is the SN of the IAB node
  • the second IAB host is the MN of the IAB node
  • the first IAB host sends the first RRC reconfiguration message to the IAB node through SRB3.
  • the first IAB host sends the first RRC reconfiguration message to the second IAB host, where the first RRC reconfiguration message is a secondary cell group configuration RRC message.
  • the first IAB host sends the IP address configuration to the second IAB host, and the IP address configuration is carried using the IAB transport migration modification request message.
  • the first IAB host is the primary node MN of the IAB node
  • the second IAB host is the secondary node SN of the IAB node
  • the first IAB host sends the first RRC reconfiguration message to the IAB node through SRB1.
  • the IP address configuration includes the IP address information of the F1 termination point topology domain.
  • the first IAB host indicates that the IP address configuration includes the IP address information of the F1 end-point topology domain by not including the first indication information in the first RRC reconfiguration message.
  • the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message.
  • the boundary node can separately transmit the routing ID belonging to Services in the F1-terminating topology domain and routing IDs belong to the services in the non-F1-terminating topology domain.
  • the embodiment of the present application provides a transmission address determination method, which is explained from the second IAB host side.
  • Figure 15 is a schematic diagram of a transmission address determination method according to an embodiment of the present application. As shown in Figure 15, the method includes:
  • the second IAB host sends a first RRC reconfiguration message.
  • the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; or sends at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of the F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
  • the second IAB host may send the first RRC reconfiguration message to the IAB node or the first IAB host, the F1 connection of the IAB node is terminated with the first IAB host, and the IAB node is connected to the first IAB host.
  • the second IAB host has an RRC connection.
  • whether the configured IP address belongs to the non-F1 termination point topology domain may be implicitly indicated, or whether the configured IP address belongs to the non-F1 termination point topology domain may be explicitly indicated.
  • the second IAB host passes The first indication information indicates that the IP address configuration includes IP address information of the F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
  • the IP address configuration contains IP address information for non-F1 termination point topology domains.
  • the first IAB host is the source host of the IAB node switch
  • the second IAB host is the target host of the IAB node switch
  • the first RRC reconfiguration message is a switch command RRC message
  • the second IAB host sends the first RRC reconfiguration message to the first IAB host.
  • the first IAB host is the primary node MN of the IAB node
  • the second IAB host is the secondary node SN of the IAB node
  • the second IAB host sends a first RRC reconfiguration message to the first IAB host;
  • the second IAB host sends the IP address configuration to the first IAB host.
  • the second IAB host sends the first RRC reconfiguration message to the IAB node through SRB3.
  • the second IAB host is the primary node MN of the IAB node
  • the first IAB host is the secondary node SN of the IAB node
  • the second IAB host sends the first RRC reconfiguration message to the IAB node through SRB1.
  • the IP address configuration includes the IP address information of the non-F1 termination point topology domain.
  • the second IAB host indicates the IP address by including the first indication information in the first RRC reconfiguration message.
  • the address configuration contains IP address information for non-F1 dead-end topology domains.
  • the first indication information is included in the newly added information element of the first RRC reconfiguration message, or is included in the IP address configuration list information element of the first RRC reconfiguration message, or is included in the first RRC reconfiguration message.
  • the IP address configuration information element of the message or is included in the IP address index information element of the first RRC reconfiguration message.
  • the IP address configuration contains IP address information for the F1 termination point topology domain.
  • the first IAB host is the SN of the IAB node
  • the second IAB host is the MN of the IAB node
  • the first RRC reconfiguration message is an RRC reconfiguration message contained in the secondary cell group configuration field in the RRC reconfiguration message, and is carried by the third RRC reconfiguration message sent by the second IAB host; in 1501, the The second IAB host sends the third RRC reconfiguration message to the IAB node through SRB1.
  • the method also includes: the second IAB host receiving the first RRC reconfiguration message sent by the first IAB host.
  • the second IAB host receives the IP address configuration provided by the first IAB host, and generates the first RRC reconfiguration message on behalf of the first IAB host.
  • the method may further include the second IAB host receiving the IP address configuration sent by the first IAB host, and in 1501, the second IAB host sends the first RRC reconfiguration message to the IAB node through SRB1.
  • the IP address configuration includes the IP address information of the F1 termination point topology domain.
  • the first IAB host indicates that the IP address configuration includes the IP address information of the F1 dead-point topology domain by not including the first indication information in the first RRC reconfiguration message or the third RRC reconfiguration message.
  • the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message.
  • the boundary node can separately transmit the routing ID belonging to Services in the F1-terminating topology domain and routing IDs belong to the services in the non-F1-terminating topology domain.
  • the embodiment of the present application provides an IAB node device, and the same content as the embodiment of the first aspect will not be described again.
  • the device may be, for example, an IAB node in the IAB system (such as the boundary node in the embodiment of the first aspect), or may be some or some components or components or modules configured in the IAB node.
  • FIG 16 is a schematic diagram of an IAB node device according to an embodiment of the present application. As shown in Figure 16, IAB node device 1600 includes:
  • the first receiving unit 1601 receives the first RRC reconfiguration message, which includes at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of the F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
  • the IAB node's F1 connection terminates with the first IAB host, and the IAB node has an RRC connection with the second IAB host.
  • the device further includes:
  • the first processing unit 1602 determines that the IP address configuration contains IP address information of the F1 termination point topology domain or IP address information of the non-F1 termination point topology domain.
  • the first processing unit determines according to the first indication information that the IP address configuration includes IP address information of the F1 termination point topology domain or IP address information of the non-F1 termination point topology domain.
  • the first processing unit determines that the IP address configuration includes IP address information of a non-F1-terminating topology domain.
  • the first IAB host is the source host of the IAB node switch
  • the second IAB host is the target host of the IAB node switch
  • the first RRC reconfiguration message is forwarded by the first IAB host.
  • the first IAB host is the primary node MN of the IAB node
  • the second IAB host is the secondary node SN of the IAB node
  • the first RRC reconfiguration message is an RRC reconfiguration message contained in the secondary cell group configuration field in the RRC reconfiguration message, and is carried by the second RRC reconfiguration message sent by the first IAB host; the first receiving unit The second RRC reconfiguration message sent by the first IAB host is received through SRB1.
  • the first RRC reconfiguration message is generated by the first IAB host instead of the second IAB host.
  • the first receiving unit receives the first RRC reconfiguration message sent by the second IAB host through SRB3.
  • the first receiving unit receives the first RRC reconfiguration message sent by the first IAB host through SRB1.
  • the first IAB host is the SN of the IAB node, and the second IAB host is the MN of the IAB node; the first receiving unit receives the first RRC sent by the second IAB host through SRB1 Reconfiguration message.
  • the first processing unit determines that the IP address configuration includes an IP in a non-F1 dead-end topology domain. Address information.
  • the first indication information is included in the newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the IP of the first RRC reconfiguration message or the second RRC reconfiguration message.
  • the address configuration list information element is either included in the IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the first RRC reconfiguration message or the second RRC reconfiguration message.
  • the IP address of the message is indexed in the information element.
  • the first processing unit determines that the IP address configuration includes IP address information of an F1 termination point (F1-terminating) topology domain.
  • the first IAB host is the primary node MN of the IAB node, and the second IAB host is the secondary node SN of the IAB node; the first receiving unit receives the message sent by the first IAB host through SRB1 The first RRC reconfiguration message.
  • the first IAB host is the SN of the IAB node
  • the second IAB host is the MN of the IAB node
  • the first RRC reconfiguration message is an RRC reconfiguration message contained in the secondary cell group configuration field in the RRC reconfiguration message, and is carried by the third RRC reconfiguration message sent by the second IAB host; the first receiving unit The third RRC reconfiguration message sent by the second IAB host is received through SRB1.
  • the first RRC reconfiguration message is generated by the second IAB host instead of the first IAB host.
  • the first receiving unit receives the first RRC reconfiguration message sent by the first IAB host through SRB3.
  • the first receiving unit receives the first RRC reconfiguration message sent by the second IAB host through SRB1.
  • the first processing unit determines that the IP address configuration includes the IP of the F1 dead-end topology domain. Address information.
  • the IAB node device 1600 in this embodiment of the present application may also include other components or modules.
  • the specific content of these components or modules please refer to related technologies.
  • FIG. 16 only illustrates the connection relationships or signal directions between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connections can be used.
  • Each of the above components or modules can be implemented by hardware facilities such as a processor, a memory, a transmitter, a receiver, etc.; the implementation of this application is not limited to this.
  • the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message.
  • the boundary node can separately transmit the routing ID belonging to Services in the F1-terminating topology domain and routing IDs belong to the services in the non-F1-terminating topology domain.
  • the embodiment of the present application provides an IAB host device, and the same content as the embodiment of the second aspect will not be described again.
  • the device may be, for example, an IAB donor-CU in the IAB system (such as the first IAB host in the embodiments of the first, second, and third aspects), or it may be one or more devices configured in the IAB donor-CU. Part or component or module.
  • FIG 17 is a schematic diagram of an IAB host device according to an embodiment of the present application. As shown in Figure 17, IAB host device 1700 includes:
  • the first sending unit 1701 sends a first RRC reconfiguration message, which includes at least one IP address configuration for the IAB node; or, sends at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of the F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain;
  • the F1 connection of the IAB node terminates at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
  • the IAB host device indicates through the first indication information that the IP address configuration contains IP address information of the F1 termination point topology domain, or contains IP address information of a non-F1 termination point topology domain.
  • the IP address configuration contains IP address information for non-F1 termination point topology domains.
  • the first IAB host is the source host of the IAB node switch
  • the second IAB host is the target host of the IAB node switch
  • the first RRC reconfiguration message is a switch command RRC message
  • the device also includes (not shown): a second receiving unit that receives the first RRC reconfiguration message sent by the second IAB host, and the first sending unit forwards the first RRC reconfiguration message sent by the second IAB host to the IAB node.
  • the first RRC reconfiguration message generated.
  • the first IAB host is the primary node MN of the IAB node
  • the second IAB host is the secondary node SN of the IAB node
  • the first RRC reconfiguration message is an RRC reconfiguration message contained in the secondary cell group configuration field in the RRC reconfiguration message, and is carried by the second RRC reconfiguration message sent by the first IAB host;
  • the first sending unit sends the second RRC reconfiguration message to the IAB node through SRB1.
  • the device further includes: (not shown)
  • the third receiving unit receives the first RRC reconfiguration message sent by the second IAB host.
  • the device further includes: (not shown)
  • the fourth receiving unit receives the IP address configuration provided by the second IAB host
  • the second processing part generates the first RRC reconfiguration message on behalf of the second IAB host.
  • the device further includes: (not shown)
  • the fifth receiving part receives the IP address configuration provided by the second IAB host, and the first sending part sends the first RRC reconfiguration message through SRB1.
  • the IAB host device indicates that the IP address configuration includes IP address information of a non-F1 dead-point topology domain by including the first indication information in the first RRC reconfiguration message or the second RRC reconfiguration message.
  • the IP address configuration contains IP address information for the F1 termination point topology domain.
  • the first IAB host is the SN of the IAB node
  • the second IAB host is the MN of the IAB node
  • the first sending unit sends the first RRC reconfiguration message to the IAB node through SRB3.
  • the first sending unit sends the first RRC reconfiguration message to the second IAB host, where the first RRC reconfiguration message is a secondary cell group configuration RRC message; or,
  • the first sending part sends the IP address configuration to the second IAB host.
  • the first IAB host is the primary node MN of the IAB node, and the second IAB host is the secondary node SN of the IAB node; the first sending unit sends the first RRC to the IAB node through SRB1 Reconfiguration message.
  • the IAB host device indicates that the IP address configuration includes the IP address information of the F1 end-point topology domain by not including the first indication information in the first RRC reconfiguration message.
  • the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the first RRC reconfiguration message or the second RRC reconfiguration message.
  • the IP address configuration list information element of the RRC reconfiguration message is either included in the IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the first RRC reconfiguration message or in the IP address index information element of the second RRC reconfiguration message.
  • the IAB host device 1700 in the embodiment of the present application may also include other components or modules.
  • the specific content of these components or modules reference may be made to related technologies.
  • FIG. 17 only illustrates the connection relationships or signal directions between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connections can be used.
  • Each of the above components or modules can be implemented by hardware facilities such as a processor, a memory, a transmitter, a receiver, etc.; the implementation of this application is not limited to this.
  • the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message.
  • the boundary node can separately transmit the routing ID belonging to Services in the F1-terminating topology domain and routing IDs belong to the services in the non-F1-terminating topology domain.
  • the embodiment of the present application provides an IAB host device, and the same content as the embodiment of the third aspect will not be described again.
  • the device may be, for example, the IAB donor-CU in the IAB system (such as the second IAB host in the embodiments of the first, second, and third aspects), or it may be one or more devices configured in the IAB donor-CU. Part or component or module.
  • FIG. 18 is a schematic diagram of an IAB host device according to an embodiment of the present application. As shown in Figure 18, IAB host device 1800 includes:
  • the second sending unit 1801 sends a first RRC reconfiguration message, which includes at least one IP address configuration for the IAB node; or sends at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of the F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
  • the F1 connection of the IAB node terminates at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
  • the IAB host device indicates through the first indication information that the IP address configuration contains IP address information of the F1 termination point topology domain, or contains IP address information of a non-F1 termination point topology domain.
  • the IP address configuration contains IP address information for non-F1 termination point topology domains.
  • the first IAB host is the source host of the IAB node switch
  • the second IAB host is the target host of the IAB node switch
  • the first RRC reconfiguration message is a switch command RRC message
  • the The second sending unit sends the first RRC reconfiguration message to the first IAB host.
  • the first IAB host is the primary node MN of the IAB node
  • the second IAB host is the secondary node SN of the IAB node
  • the second sending unit sends a first RRC reconfiguration message to the first IAB host; or sends the IP address configuration to the first IAB host.
  • the second sending unit sends the first RRC reconfiguration message to the IAB node through SRB3.
  • the first IAB host is the SN of the IAB node
  • the second IAB host is the MN of the IAB node
  • the second sending unit sends the first RRC reconfiguration message to the IAB node through SRB1.
  • the IAB host device indicates that the IP address configuration includes IP address information of a non-F1 end-point topology domain by including the first indication information in the first RRC reconfiguration message.
  • the IP address configuration contains IP address information for the F1 termination point topology domain.
  • the first IAB host is the SN of the IAB node
  • the second IAB host is the MN of the IAB node
  • the first RRC reconfiguration message is an RRC reconfiguration message contained in the secondary cell group configuration field in the RRC reconfiguration message, and is carried by the third RRC reconfiguration message sent by the second IAB host; the second sending part The third RRC reconfiguration message is sent to the IAB node through SRB1.
  • the device further includes: (not shown)
  • the sixth receiving unit receives the first RRC reconfiguration message sent by the first IAB host.
  • the device further includes: (not shown)
  • the seventh receiving unit receives the IP address configuration provided by the first IAB host
  • the second processing part generates the first RRC reconfiguration message on behalf of the first IAB host.
  • the device further includes: (not shown)
  • the eighth receiving unit receives the IP address configuration sent by the first IAB host, and the second sending unit sends the first RRC reconfiguration message to the IAB node through SRB1.
  • the IAB host device indicates that the IP address configuration includes the IP address information of the F1 termination point topology domain by not including the first indication information in the first RRC reconfiguration message or the third RRC reconfiguration message.
  • the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the first RRC reconfiguration message or the second RRC reconfiguration message.
  • the IP address configuration list information element of the RRC reconfiguration message is either included in the IP address configuration information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the first RRC reconfiguration message or in the IP address index information element of the second RRC reconfiguration message.
  • the IAB host device 1800 in the embodiment of the present application may also include other components or modules.
  • the specific content of these components or modules please refer to related technologies.
  • FIG. 18 only illustrates the connection relationships or signal directions between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connections can be used.
  • Each of the above components or modules can be implemented by hardware facilities such as a processor, a memory, a transmitter, a receiver, etc.; the implementation of this application is not limited to this.
  • the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain can be configured to the IAB node through the first RRC reconfiguration message.
  • the boundary node can separately transmit the routing ID belonging to Services in the F1-terminating topology domain and routing IDs belong to the services in the non-F1-terminating topology domain.
  • Embodiments of the present application provide a communication system, including a first IAB host (donor) device of a fourth embodiment, a second IAB host device of a fifth embodiment, and an IAB node (IAB- node) device; for the network architecture of the host (donor) device and IAB node device, you can also refer to related technologies, and the description is omitted here.
  • Embodiments of the present application also provide an IAB device, which may be an IAB host device or an IAB node device (migration node or child node).
  • IAB device which may be an IAB host device or an IAB node device (migration node or child node).
  • FIG. 9 is a schematic diagram of an IAB device according to an embodiment of the present application.
  • the IAB device 900 may include a processor (eg, central processing unit CPU) 901 and a memory 902 ; the memory 902 is coupled to the processor 901 .
  • the memory 902 can store various data; in addition, it also stores an information processing program 905, and the program 905 is executed under the control of the central processor 901.
  • the processor 901 may be configured to execute a program to implement the transmission address determination method as in the embodiment of the first aspect.
  • the processor 901 may be configured to execute a program to implement the transmission address determination method as in the embodiment of the second aspect.
  • the processor 901 may be configured to execute a program to implement the transmission address determination method as in the embodiment of the third aspect.
  • the IAB device 900 may also include: a transceiver 903, an antenna 904, 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 IAB device 900 does not necessarily include all components shown in FIG. 9 ; in addition, the IAB device 900 may also include components not shown in FIG. 9 , and reference may be made to the existing technology.
  • An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in an IAB device, the program causes the computer to execute the transmission address in the embodiments of the first to third aspects in the IAB device. Determine the method.
  • Embodiments of the present application also provide a storage medium storing a computer-readable program, wherein the computer-readable program causes the computer to execute the transmission address determination method in the embodiments of the first to third aspects in the IAB device.
  • 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.
  • Logic components such as field programmable logic components, microprocessors, processors used in computers, etc.
  • 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 transmission address determination method applied to access and backhaul IAB node equipment, characterized in that the method includes:
  • the IAB node receives a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
  • the IAB node determines that the IP address configuration includes IP address information of the F1 termination point topology domain or IP address information of the non-F1 termination point topology domain.
  • the first RRC reconfiguration message is a switching command RRC message generated by the second IAB host and forwarded by the first IAB host.
  • the first RRC reconfiguration message is an RRC reconfiguration message contained in the secondary cell group configuration field in the RRC reconfiguration message and is sent by the first IAB host
  • the second RRC reconfiguration message carries;
  • the IAB node receives the second RRC reconfiguration message sent by the first IAB host through SRB1.
  • the IAB node receives the first RRC reconfiguration message sent by the second IAB host through SRB1.
  • the IAB node receives the first RRC reconfiguration message sent by the first IAB host through SRB1.
  • the IAB node receives the third RRC reconfiguration message sent by the second IAB host through SRB1.
  • the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the The IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or the IP address configuration information contained in the first RRC reconfiguration message or the second RRC reconfiguration message element, or included in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
  • An IAB node (donor) device comprising a memory and a processor, the memory stores a computer program, wherein the processor is configured to execute the computer program to implement any one of appendices 1 to 22 Described transmission address determination method.
  • a transport address determination method applied to the first IAB host, characterized in that the method includes:
  • the first IAB host sends a first RRC reconfiguration message, and the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; or, sends at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of the F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain;
  • the F1 connection of the IAB node terminates at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
  • the method according to appendix 3 wherein the first IAB host is the source host of the IAB node switching, the second IAB host is the target host of the IAB node switching, and the first RRC
  • the reconfiguration message is a handover command RRC message
  • the first IAB host receives the first RRC reconfiguration message sent by the second IAB host, and forwards the first RRC reconfiguration message generated by the second IAB host to the IAB node.
  • the first IAB host sends the second RRC reconfiguration message to the IAB node through SRB1.
  • the first IAB host receives the first RRC reconfiguration message sent by the second IAB host.
  • the first IAB host receives the IP address configuration provided by the second IAB host, and generates the first RRC reconfiguration message on behalf of the second IAB host.
  • the first IAB host receives the IP address configuration provided by the second IAB host, and sends the first RRC reconfiguration message through SRB1.
  • the first IAB host includes the first indication information through the first RRC reconfiguration message or the second RRC reconfiguration message. Indicates that the IP address configuration contains IP address information of a non-F1 end-point topology domain.
  • the first IAB host sends the first RRC reconfiguration message to the IAB node through SRB3.
  • the first IAB host sends the IP address configuration to the second IAB host.
  • the first IAB host sends the first RRC reconfiguration message to the IAB node through SRB1.
  • the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the The IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or the IP address configuration information contained in the first RRC reconfiguration message or the second RRC reconfiguration message element, or included in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
  • An IAB host (donor) device comprising a memory and a processor, the memory storing a computer program, wherein the processor is configured to execute the computer program to implement any one of appendices 1 to 17 Described transmission address determination method.
  • a transport address determination method applied to the second IAB host, characterized in that the method includes:
  • the second IAB host sends a first RRC reconfiguration message, the first RRC reconfiguration message includes at least one IP address configuration for the IAB node; or sends at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
  • the F1 connection of the IAB node terminates at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
  • the method according to appendix 3 wherein the first IAB host is the source host of the IAB node switching, the second IAB host is the target host of the IAB node switching, and the first RRC
  • the reconfiguration message is a handover command RRC message, and,
  • the second IAB host sends the first RRC reconfiguration message to the first IAB host.
  • the second IAB host sends the first RRC reconfiguration message to the IAB node through SRB1.
  • the third RRC reconfiguration message carries;
  • the second IAB host sends the third RRC reconfiguration message to the IAB node through SRB1.
  • the second IAB host receives the first RRC reconfiguration message sent by the first IAB host.
  • the second IAB host receives the IP address configuration sent by the first IAB host, and sends the first RRC reconfiguration message to the IAB node through SRB1.
  • the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the The IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or the IP address configuration information contained in the first RRC reconfiguration message or the second RRC reconfiguration message element, or included in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
  • An IAB host (donor) device comprising a memory and a processor, the memory storing a computer program, wherein the processor is configured to execute the computer program to implement any one of appendices 1 to 17 Described transmission address determination method.
  • An IAB node device characterized in that the device includes:
  • a first receiving unit that receives a first RRC reconfiguration message, where the first RRC reconfiguration message includes at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
  • the first processing part determines that the IP address configuration includes IP address information of the F1 termination point topology domain or IP address information of the non-F1 termination point topology domain.
  • the first processing unit determines that the IP address configuration includes IP address information of the F1 termination point topology domain or an IP address of a non-F1 termination point topology domain according to the first instruction information. information.
  • the first RRC reconfiguration message is a switching command RRC message generated by the second IAB host and forwarded by the first IAB host.
  • the first RRC reconfiguration message is an RRC reconfiguration message contained in the secondary cell group configuration field in the RRC reconfiguration message and is sent by the first IAB host
  • the second RRC reconfiguration message carries;
  • the first receiving unit receives the second RRC reconfiguration message sent by the first IAB host through SRB1.
  • the first receiving unit receives the first RRC reconfiguration message sent by the second IAB host through SRB1.
  • the first processing unit includes the first indication information in the first RRC reconfiguration message or the second RRC reconfiguration message When, it is determined that the IP address configuration contains IP address information of a non-F1 end-point topology domain.
  • the first receiving unit receives the first RRC reconfiguration message sent by the first IAB host through SRB1.
  • the first RRC reconfiguration message is an RRC reconfiguration message contained in the secondary cell configuration field in the RRC reconfiguration message, and is sent by the second IAB host. Three RRC reconfiguration messages are carried;
  • the first receiving unit receives the third RRC reconfiguration message sent by the second IAB host through SRB1.
  • the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the The IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or the IP address configuration information contained in the first RRC reconfiguration message or the second RRC reconfiguration message element, or included in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
  • An IAB host device applied to the first IAB host, characterized in that the device includes:
  • the first sending unit sends a first RRC reconfiguration message, which includes at least one IP address configuration for the IAB node; or, sends at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of the F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain;
  • the F1 connection of the IAB node terminates at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
  • IP address configuration contains IP address information of a non-F1 termination point topology domain.
  • the device is the source host of the IAB node switching, the second IAB host is the target host of the IAB node switching, and the first RRC
  • the reconfiguration message is a handover command RRC message
  • the device further includes: a second receiving unit that receives the first RRC reconfiguration message sent by the second IAB host, and the first sending unit forwards the message sent by the second IAB host to the IAB node.
  • the first RRC reconfiguration message generated.
  • the first sending unit sends the second RRC reconfiguration message to the IAB node through SRB1.
  • the third receiving unit receives the first RRC reconfiguration message sent by the second IAB host.
  • the fourth receiving unit receives the IP address configuration provided by the second IAB host
  • the second processing part generates the first RRC reconfiguration message on behalf of the second IAB host.
  • the fifth receiving part receives the IP address configuration provided by the second IAB host, and the first sending part sends the first RRC reconfiguration message through SRB1.
  • the device includes the first indication information indication through the first RRC reconfiguration message or the second RRC reconfiguration message.
  • the IP address configuration includes IP address information of a non-F1 end-point topology domain.
  • IP address configuration contains IP address information of the F1 termination point topology domain.
  • the first sending unit sends the first RRC reconfiguration message to the IAB node through SRB3.
  • the first sending unit sends the first RRC reconfiguration message to the second IAB host, wherein the first RRC reconfiguration message is a secondary cell configuration RRC message; or,
  • the first sending unit sends the IP address configuration to the second IAB host.
  • the first sending unit sends the first RRC reconfiguration message to the IAB node through SRB1.
  • the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the The IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or the IP address configuration information contained in the first RRC reconfiguration message or the second RRC reconfiguration message element, or included in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.
  • An IAB host device applied to a second IAB host, characterized in that the device includes:
  • the second sending unit sends a first RRC reconfiguration message, which includes at least one IP address configuration for the IAB node; or sends at least one IP address configuration for the IAB node;
  • the at least one IP address configuration includes IP address information of an F1 termination point topology domain, or includes IP address information of a non-F1 termination point topology domain.
  • the F1 connection of the IAB node terminates at the first IAB host, and the IAB node has an RRC connection with the second IAB host.
  • IP address configuration contains IP address information of a non-F1 termination point topology domain.
  • the device is the source host of the IAB node switching, the second IAB host is the target host of the IAB node switching, and the first RRC
  • the reconfiguration message is a handover command RRC message, and,
  • the second sending unit sends the first RRC reconfiguration message to the first IAB host.
  • the second sending unit sends the first RRC reconfiguration message to the IAB node through SRB1.
  • the first RRC reconfiguration message is an RRC reconfiguration message contained in the secondary cell configuration field in the RRC reconfiguration message, and is sent by the second IAB host.
  • Three RRC reconfiguration messages are carried;
  • the second sending unit sends the third RRC reconfiguration message to the IAB node through SRB1.
  • the sixth receiving unit receives the first RRC reconfiguration message sent by the first IAB host.
  • a seventh receiving unit which receives the IP address configuration provided by the first IAB host
  • a third processing unit generates the first RRC reconfiguration message on behalf of the first IAB host.
  • the eighth receiving unit receives the IP address configuration sent by the first IAB host, and the second sending unit sends the first RRC reconfiguration message to the IAB node through SRB1.
  • the first indication information is included in a newly added information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or is included in the The IP address configuration list information element of the first RRC reconfiguration message or the second RRC reconfiguration message, or the IP address configuration information contained in the first RRC reconfiguration message or the second RRC reconfiguration message element, or included in the IP address index information element of the first RRC reconfiguration message or the second RRC reconfiguration message.

Landscapes

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

Abstract

本申请实施例提供了一种IAB节点设备、IAB宿主设备以及传输地址确定方法。该IAB节点设备包括：第一接收部，其接收第一RRC重配置消息，所述第一RRC重配置消息中包括针对所述IAB节点的至少一个IP地址配置；所述至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。

Description

IAB节点设备、IAB宿主设备以及传输地址确定方法 技术领域
本申请实施例涉及通信领域。
背景技术
未来无缝的蜂窝网络部署需要非常灵活和超密集的新无线(NR，new radio)小区部署，超密集网络是5G的目标之一，部署一个无需有线回传的NR网络对于实现5G的超密集网络非常重要。由于5G毫米波使小区覆盖范围缩小，无线自回传系统需要多跳才能满足部署需求。5G的高带宽、大规模多输入多输出(MIMO)和波束系统使5G比LTE更容易开发超密集NR小区的无线自回传系统，为了开发这种带有无线自回传的多跳系统，3GPP在Rel-16开始了集成的接入和回传(IAB，Integrated access and backhaul)项目的研究和标准化。
图1是IAB系统的一示意图，如图1所示，在IAB系统中，接入和回传采用NR的Uu空口无线传输，中继节点同时支持接入(access)和回传(backhaul)功能，中继节点在时域、频域或空域上复用接入链路(access link)和回传链路(backhaul link)，接入链路和回传链路可以使用相同或不同的频段。
在IAB网络架构如下，中继节点指的是IAB-node(IAB节点)，其同时支持接入和回传功能。网络侧最后一跳接入节点称为IAB-donnor(IAB宿主)，其支持gNB功能并支持IAB-node接入。所有的UE数据可以通过一跳或多跳经由IAB-node回传到IAB-donor。
IAB-node的功能分为两部分，一部分是gNB-DU功能，称作IAB-DU(分布单元)，另一部分是UE功能，称作IAB-MT(移动终端)。IAB-DU实现网络侧设备功能，连接到下游的child IAB-node(子IAB节点或简称为子节点)，对UE以及下游child IAB-node提供NR空口接入并与IAB donor-CU(宿主集中单元)之间建立有F1连接。IAB-MT实现部分终端设备功能，连接到上游的parent IAB-node(父IAB节点或简称为父节点)或IAB donor-DU，IAB-MT包括物理层、层二、RRC(Radio Resource Control，无线资源控制)和NAS(Non-Access Stratum，非接入层)层功能，还间接地连接到IAB Donor-CU以及核心网(Core Network，CN)。
在IAB系统中，IAB-node可以通过独立组网(SA，Standalone)模式或非独立 组网(EN-DC，E-UTRA-NRDualConnectivity)模式接入网络。图2是SA模式的IAB架构的示意图。图3是EN-DC模式的IAB架构的示意图。
图4是一个IAB节点(IAB-node)与父节点(parent IAB-node)和子节点(child IAB-node)的示意图。如图4所示，IAB节点的IAB-DU作为网络侧与子节点的IAB-MT连接，IAB节点的IAB-MT作为终端侧与父节点的IAB-DU连接。
图5是IAB-DU和IAB donor-CU之间的F1用户面(F1-U)协议栈的示意图。图6是IAB-DU和IAB donor-CU之间的F1控制面(F1-C)协议栈的示意图。如图5和图6所示，F1-U和F1-C是建立在IAB-DU和IAB donor-CU之间的传输(IP)层之上，图5和图6中经过两跳无线回传和一跳有线回传。
在回传链路上，传输(IP)层承载在回传自适应协议(BAP)子层上，IAB-node中的BAP实体实现IAB系统的路由功能，由IAB donor-CU提供路由表。BAP PDU(协议数据单元)在回传链路的RLC(无线链路控制)信道中传输，回传链路的多个RLC信道可以被IAB-donor配置为承载不同的优先级和QoS(服务质量)的业务，由BAP实体将BAP PDU映射到不同的回传RLC信道上。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的，不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
发明人发现，如果IAB节点的全部业务或者部分业务需要从F1终止点拓扑域迁移或者被配置到非F1终止点拓扑域中，IAB节点的全部或部分业务的routing ID将属于non-F1-terminating拓扑域，也即IAB节点需要同时传输routing ID属于F1-terminating拓扑域的业务和routing ID属于non-F1-terminating拓扑域的业务。但是，如何使IAB节点分别传输routing ID属于F1-terminating拓扑域的业务和routing ID属于non-F1-terminating拓扑域的业务，目前并没有相应的方案。
为了解决上述问题的至少之一，本申请实施例提供一种IAB节点设备、IAB宿主设备以及传输地址确定方法。
根据本申请实施例的一方面，提供一种集成的接入和回传IAB节点设备，所述设备包括：
第一接收部，其接收第一RRC重配置消息，所述第一RRC重配置消息中包括针 对所述IAB节点的至少一个IP地址配置；
所述至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
根据本申请实施例的另一方面，提供一种集成的接入和回传IAB宿主设备，应用于第一IAB宿主，所述设备包括：
第一发送部，其发送第一RRC重配置消息，所述第一RRC重配置消息中包括至少一个针对IAB节点的IP地址配置；或者，发送至少一个所述IAB节点的IP地址配置；
所述至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息；
其中，所述IAB节点的F1连接终止于所述第一IAB宿主，并且IAB节点与第二IAB宿主有RRC连接。
根据本申请实施例的另一方面，提供一种集成的接入和回传IAB宿主设备，应用于第二IAB宿主，所述设备包括：
第二发送部，其发送第一RRC重配置消息，所述第一RRC重配置消息中包括至少一个针对IAB节点的IP地址配置；或者发送至少一个针对IAB节点的IP地址配置；
所述至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
其中，所述IAB节点的F1连接终止于第一IAB宿主，并且所述IAB节点与所述第二IAB宿主有RRC连接。
本申请实施例的有益效果之一在于：可以通过该第一RRC重配置消息向IAB节点配置非F1终止点拓扑域的IP地址或者F1终止点拓扑域的IP地址，这样，针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址，针对F1终止点拓扑域的routing ID，可以使用F1终止点拓扑域的IP地址。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附附记的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的 特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部分，用于例示本申请的实施方式，并与文字描述一起来阐释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。在附图中：
图1是IAB系统的一示意图；
图2是SA模式的IAB架构的一示意图；
图3是EN-DC模式的IAB架构的一示意图；
图4是父节点(parent IAB-node)和子节点(child IAB-node)的一示意图；
图5是IAB系统的F1-U协议栈的一示意图；
图6是IAB系统的F1-C协议栈的一示意图；
图7是IAB系统路由的一示意图；
图8是网络拓扑自适应的一示意图；
图9是本申请实施例的IAB设备的一示意图；
图10是本申请实施例的传输地址确定方法的一示意图；
图11是切换场景示意图；
图12是双连接场景一示意图；
图13是双连接场景二示意图；
图14是本申请实施例的传输地址确定方法的一示意图；
图15是本申请实施例的传输地址确定方法的一示意图；
图16是本申请实施例的IAB节点设备的一示意图；
图17是本申请实施例的IAB宿主设备的一示意图；
图18是本申请实施例的IAB宿主设备的一示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附附记的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如新无线(NR，New Radio)、长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及未来的5G、6G等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备，也可以称为“终端设备”(TE，Terminal Equipment)。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
信令无线承载SRB包括SRB0，SRB1，SRB2，SRB3，其中，SRB0，SRB1，SRB2是通向MN的，SRB3是通向SN的。信令无线承载是用来传输RRC和NAS消息的无线承载。SRB0传输使用公共控制信道(common control channel，CCCH)逻辑信道的RRC消息。SRB1传输RRC消息(可能包含附着(piggybacked)的NAS消息)和SRB2建立之前的NAS消息，使用专用控制信道(dedicated control channel，DCCH)逻辑信道。SRB2传输NAS消息和包含了日志测量消息的RRC消息，使用DCCH逻辑信道。SRB2比SRB1的优先级低，可以在接入层(access stratum，AS)安全激活之后由网络配置。SRB3用于当UE在(NG)EN-DC或NR-DC时的特定RRC消息，使用DCCH逻辑信道。
IAB系统的路由功能由BAP层实现，每个IAB-node节点保存有路由配置(BH routing configuration)和RLC信道映射配置(BH RLC Channel Mapping Configuration)。 BAP实体根据路由配置、RLC信道映射配置和BAP层数据包头中的路由标识(Routing ID)进行路由。Routing ID包含目的BAP地址和路径标识。
路由配置包含Routing ID与下一跳(next-hop)节点BAP地址的映射关系。RLC信道映射配置包含上一跳(prior-hop)节点BAP地址、入口链路RLC信道ID和下一跳节点BAP地址与出口链路RLC信道ID的映射关系。
图7是IAB系统路由的一示意图。如图7所示，对于每个数据包，可以通过数据包头的routing ID从路由配置查找到下一跳节点BAP地址。上一跳节点BAP地址、入口链路RLC信道ID都是已知的。这样，下一跳节点BAP地址确定之后，就可以通过RLC信道映射配置，根据上一跳节点BAP地址+入口链路RLC信道ID+下一跳节点BAP地址查到出口链路RLC信道ID。
IAB-donor DU保存有路由配置(BH routing configuration)和下行RLC信道映射配置(Downlink Traffic to BH RLC Channel Mapping Configuration)。IAB-donor DU根据路由配置、RLC信道映射配置和BAP层数据包头中的Routing ID进行路由。路由配置包含Routing ID与下一跳节点地址的映射关系。下行RLC信道映射配置包含目标IP地址、DSCP(Differentiated Services Code Point，差分服务代码点)和下一跳节点地址与出口链路RLC信道ID的映射关系。
对于每个到达IAB-donor DU的下行数据包，IAB-donor DU可根据数据包头中的Routing ID从路由配置查到下一跳节点地址。这样，下一跳节点地址确定之后，再根据数据包的IP地址和DSCP，从下行RLC信道映射配置查到出口链路RLC信道ID。
接入IAB节点保存有上行回传信息(BH information)，包括业务使用的路由标识(routing ID)、上行回传RLC信道ID和下一跳节点地址。接入IAB节点根据上行BH information配置上行业务的BAP层数据包头中的routing ID并选择上行业务传输的BH RLC信道和下一跳节点。
以上示意性说明了IAB系统的路由和BH RLC信道映射，以下再说明IAB系统的网络拓扑的更新。Rel-16NR已经对IAB-node在同一个donor-CU下移动时拓扑自适应(topology adaptation)过程进行了标准化。
图8是CU内(intra-CU)拓扑自适应的一示意图。IAB-node改变父节点(从IAB-node 1改变为IAB-node 2)时，donor-CU通过RRC重配置消息为IAB-node配置路径迁移相关的配置，使IAB-node进行F1传输路径的迁移。
路径迁移相关的配置包括对上行F1-C、F1-U和非F1数据的默认回传RLC信道 (default BH RLC channel)的更新，对默认BAP路由标识(default BAP routing ID)的更新，以及对路由至Donor-DU的IP地址的更新。IAB-node接入到新的父节点时开始应用上述路径迁移相关的配置，对于IAB-node的子节点，也通过相同的方法进行路径迁移相关的配置。
3GPP Rel-17支持IAB-node在不同donor-CU下移动时的网络拓扑更新和回传(BH)无线链路失败(RLF，Radio Link Failure)的恢复过程，IAB-node可以从源donor-CU(也可称为F1-terminating CU或第一donor-CU)服务的父节点切换或重建立到目标donor-CU(也可称为non-F1-terminating CU或第二donor-CU)服务的父节点，需要将IAB-node的全部业务(以及其子节点的业务)迁移至non-F1-terminating CU的拓扑。Rel-17也支持IAB-node与non-F1-terminating CU建立双连接时的拓扑冗余(topology redundancy)过程，IAB-node的部分业务的传输路径可迁移至non-F1-terminating CU拓扑。
IAB-node从donor-CU 1(F1-terminating CU)切换/RLF恢复到donor-CU 2(non-F1-terminating CU)后，或增加与donor-CU 2的RRC连接后，只是IAB-MT的RRC连接到donor-CU 2，F1接口仍然终止于donor-CU 1，此时IAB-node也可称为boundary node。其服务的子节点的RRC连接和F1接口仍属于donor-CU1，因此子节点业务的routing ID、BH RLC信道以及下一跳BAP地址仍然属于F1-terminating拓扑域。
Boundary node的全部或部分业务的routing ID将属于non-F1-terminating拓扑域，也即boundary node需要同时传输routing ID属于F1-terminating拓扑域的业务和routing ID属于non-F1-terminating拓扑域的业务。但是，如何使boundary node分别传输routing ID属于F1-terminating拓扑域的业务和routing ID属于non-F1-terminating拓扑域的业务，目前并没有相应的方案。
在本申请实施例中，在没有特别说明的情况下，IAB节点设备包括迁移节点或其子节点。此外，“donor-CU的拓扑域中已建立用于服务IAB节点的业务的资源”也可称为“IAB节点的业务迁移到donor-CU的拓扑域中”等，本申请不限于这些表述。以下对本申请实施例进行进一步说明。
第一方面的实施例
本申请实施例提供一种传输地址确定方法，从IAB节点设备进行说明。
图10是本申请实施例的传输地址确定方法的一示意图。如图10所示，该方法包括：
1001，该IAB节点接收第一RRC重配置消息，该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置；该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
值得注意的是，以上附图10仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图10的记载。
由于针对non-F1-terminating拓扑域的routing ID，boundary node需要使用non-F1-terminating拓扑域的IP地址，也即锚定于non-F1-terminating拓扑域的donor-DU的IP地址；针对F1-terminating拓扑域routing ID，需使用F1-terminating拓扑域的IP地址，也即锚定于F1-terminating拓扑域的donor-DU的IP地址。由上述实施例可知，可以通过该第一RRC重配置消息向IAB节点配置非F1终止点拓扑域的IP地址或者F1终止点拓扑域的IP地址，这样，可以使boundary node可以分别传输routing ID属于F1-terminating拓扑域的业务和routing ID属于non-F1-terminating拓扑域的业务。
在一些实施例中，IAB节点包括迁移节点或其子节点，例如，在IAB节点为迁移节点(也称为边界节点)时，IAB节点的F1连接终止于第一IAB宿主(例如第一IAB donor-CU)，该IAB节点与该第二IAB宿主(例如第二IAB donor-CU)有RRC连接。例如IAB节点的IAB-MT与第二IAB宿主保持RRC连接，以下第一IAB宿主也称为F1终止点宿主(例如F1终止点donor-CU)，第二IAB宿主也称为非F1终止点宿主(例如非F1终止点donor-CU)，其中，F1终止点宿主指对边界IAB节点和其子IAB节点的F1接口终止的IAB宿主，即第一IAB宿主。非F1终止点宿主指没有对边界IAB节点和其子IAB节点的F1接口终止的具有宿主功能的宿主，比如第二IAB宿主。
在一些实施例中，该IP地址是指为IAB节点配置的锚定于donor-DU的IP地址，该第一RRC重配置消息中的至少一个IP地址配置可以是至少两个donor-DU的IP地址配置，也可以是一个donor-DU的至少一个IP地址配置，每一个IP地址配置可以包括IP地址索引和对应的IP地址，本申请实施例并不以此作为限制。
在本申请实施例中，“锚定于donor-DU的IP地址(IP address anchored to IAB donor-DU)”可以理解为“由donor-DU分配的IP地址”或者“经由donor-DU可路由的传输网络层(TNL)地址(TNL address(es)that is(are)routable via the IAB-donor-DU)”，以上术语可以相互替换，本申请不限于此，例如针对该IAB节点配置的非F1终止点拓扑域的donor-DU的IP地址，是指针对该IAB节点配置的经由非F1终止点拓扑域的donor-DU可路由的传输网络层(TNL)地址。
在一些实施例中，该方法还可以包括：
1002，该IAB节点确定IP地址配置包含F1终止点拓扑域的IP地址信息或非F1终止点拓扑域的IP地址信息。
在一些实施例中，可以隐式的指示配置的IP地址是否属于非F1终止点拓扑域，在1002中，IAB节点可以根据提供IP地址信息的宿主，确定IP地址配置包含F1终止点拓扑域的IP地址信息或非F1终止点拓扑域的IP地址信息。例如，提供IP地址信息的宿主是F1终止点宿主时，确定IP地址配置包含F1终止点拓扑域的IP地址信息，提供IP地址信息的宿主是非F1终止点宿主时，确定IP地址配置包含非F1终止点拓扑域的IP地址信息。
在一些实施例中，可以显式的指示(例如根据第一指示信息显式指示)配置的IP地址是否属于非F1终止点拓扑域，在1002中，IAB节点可以根据第一指示信息，确定IP地址配置包含F1终止点拓扑域的IP地址信息或非F1终止点拓扑域的IP地址信息。例如，该第一指示信息用于指示IP地址配置包含非F1终止点拓扑域的IP地址信息，该IAB节点在收到该第一指示信息时，确定IP地址配置包含非F1终止点拓扑域的IP地址信息，在没有收到该第一指示信息时，确定IP地址配置包含F1终止点拓扑域的IP地址信息；但本申请实施例并不以此作为限制，该第一指示信息的承载方式以及具体示例将在后述进行说明。由以上实施例可知，通过隐式或显示的指示，IAB节点可以区分配置的IP地址是非F1终止点拓扑域或F1终止点拓扑域。
以下结合不同的场景分别针对隐式和显式的指示进行说明。
(一)针对切换场景
在一些实施例中，图11是切换场景示意图，如图11所示，在切换场景中，边界节点的全部业务迁移至非F1终止点拓扑域，F1终止点宿主是该IAB节点切换的源宿主，该非F1终止点宿主是该IAB节点切换的目标宿主。可以在切换过程中配置非F1终止点拓扑域的IP地址，或者切换完成后配置非F1终止点拓扑域的IP地址。在切 换过程中，该第一RRC重配置消息是第一IAB宿主转发的由第二IAB宿主生成的切换命令RRC消息。在切换过程后，该第一RRC重配置消息是第二IAB宿主直接向IAB节点发送的RRC消息，该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置，该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。该至少一个IP地址配置可以由切换命令RRC消息，例如可以是其中的主小区组信息中reconfigurationWithSync信息域的RRC重配置信息中承载的该至少一个IP地址配置。IAB节点可确定由切换命令RRC消息配置的至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，或者IAB节点可确定目标宿主发送的RRC消息中的至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息。
(i)隐式指示
例如，在切换过程中，由于切换命令RRC消息是目标宿主产生的(即提供IP地址信息的宿主是目标宿主)，而目标宿主是非F1终止点，因此，该IAB节点在收到该切换命令RRC消息后可以确定该切换命令RRC消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。
例如，在切换完成后，目标宿主可以直接向该IAB节点发送RRC消息，该IAB节点在收到该RRC消息后可以确定该RRC消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。
(ii)显式指示
例如，在切换过程中，目标宿主在产生切换命令RRC消息时，可以在其中引入新的信息元，即第一指示信息non-F1-terminating，因此，该IAB节点在收到该切换命令RRC消息后，也即切换命令RRC消息中包含该第一指示信息时，确定该切换命令RRC消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。
例如，在切换完成后，目标宿主可以直接向该IAB节点发送RRC消息，可以在其中引入新的信息元，即第一指示信息non-F1-terminating-Indication，该IAB节点在收到该RRC消息后，也即切换命令RRC消息中包含该第一指示信息时，可以确定该RRC消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。
在一些实施例中，该第一指示信息可以包含在RRC重配置消息的新增的信息元中，或者包含在RRC重配置消息的IP地址配置列表信息元中，或者包含在RRC重配置消息的IP地址配置信息元中，或者包含在RRC重配置消息的IP地址索引信息 元中。以下分别示例说明。
1)在第一RRC重配置消息中增加新的信息元non-F1-terminating-Indication，用于指示该RRC消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息，或者说指示该至少一个IP地址配置是非F1终止点宿主产生的。
该第一RRC重配置消息使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086455-appb-000001
2)在第一RRC重配置消息的IP地址配置列表信息元IAB-IP-AddressConfigurationList中增加新的信息元non-F1-terminating-Indication，用于指示该RRC消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息，或者说指示该至少一个IP地址配置是非F1终止点宿主产生的。
该IP地址配置列表信息元使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086455-appb-000002
Figure PCTCN2022086455-appb-000003
通过上述1)和2)中的指示方式，可以针对所有配置的IP地址信息统一指示其是非F1终止点拓扑域的IP地址信息，节约信息比特。
3)在第一RRC重配置消息的IP地址配置信息元IAB-IP-AddressConfiguration中增加新的信息元non-F1-terminating-Indication，用于指示该RRC消息承载的某个IP地址配置是非F1终止点拓扑域的IP地址信息，或者说指示该IP地址配置是非F1终止点宿主产生的。
该IP地址配置信息元使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086455-appb-000004
4)在第一RRC重配置消息的IP地址索引信息元IAB-IP-AddressIndexInfo中增加新的信息元non-F1-terminating-Indication，用于指示该RRC消息承载的某个IP地址配置是非F1终止点拓扑域的IP地址信息，或者说指示该IP地址配置是非F1终止点宿主产生的。
该IP地址索引信息元使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086455-appb-000005
通过上述3)和4)中的指示方式，指示的粒度可以针对各个配置的IP地址信息，指示方式更加灵活。
(二)针对双连接场景一
在一些实施例中，图12是双连接场景一示意图，如图12所示，在双连接场景一中，第一IAB宿主(F1终止点宿主)是该IAB节点的主节点MN，该第二IAB宿主(非F1终止点宿主)是该IAB节点的辅节点SN。建立双连接后，可将边界节点的 部分业务迁移至非F1终止点拓扑域，部分业务仍然在F1终止点宿主拓扑域，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。可以在双连接建立过程中配置非F1终止点拓扑域的IP地址，或者双连接建立完成后配置非F1终止点拓扑域的IP地址或者F1终止点拓扑域的IP地址。在隐式指示时，IAB节点可确定通过SRB3接收的RRC消息中的该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，或者可确定通过SRB1接收的辅小区组配置信息中的该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，或者可确定通过SRB1接收的RRC消息中的该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息。在显式指示时，IAB节点可以在接收到第一指示信息时确定通过SRB1接收的辅小区组配置信息中的该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，在没有接收到第一指示信息时确定通过SRB1接收的辅小区组配置信息中的该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，以下分情况说明。
在一些实施例中，在添加辅小区组的过程中配置非F1终止点拓扑域的IP地址，该第一RRC重配置消息是RRC重配置消息的辅小区组配置(mrdc-SecondaryCellGroupConfig域)承载的RRC重配置消息，完全由第二宿主产生并并由该第一IAB宿主发送的第二RRC重配置消息携带；该IAB节点通过SRB1接收由所述第一IAB宿主发送的所述第二RRC重配置消息。该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置，该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。
RRC重配置消息的ASN.1结构如下所示，其中包含辅小区组配置(mrdc-SecondaryCellGroupConfig域)。
Figure PCTCN2022086455-appb-000006
Figure PCTCN2022086455-appb-000007
(i)隐式指示
例如，SN产生辅小区组配置RRC消息，并在辅小区组添加响应消息中发送给MN，MN在接收到SN发送的辅小区组配置RRC消息后，生成第二RRC重配置消息，将该辅小区组配置RRC消息放在该第二RRC重配置消息的mrdc-SecondaryCellGroupConfig域中转发至IAB节点。因此，该IAB节点在通过SRB1收到该第二RRC重配置消息后可以获得其中承载的mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息，IAB节点知道mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息是SN产生(即至少一个IP地址配置是SN提供)的，而SN是非F1终止点，因此IAB节点确定该mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。也就是说，IAB节点确定通过SRB1接收的mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息中的至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息。
(ii)显式指示
例如，SN产生辅小区组配置RRC消息时，可以在其中引入新的信息元，即第一指示信息non-F1-terminating，并在辅小区组添加响应消息中发送给MN，MN在接收到SN发送的辅小区组配置RRC消息后，生成第二RRC重配置消息，将该辅小区组配置RRC消息放在该第二RRC重配置消息中的mrdc-SecondaryCellGroupConfig域中转发至IAB节点。因此，该IAB节点在通过SRB1收到该第二RRC重配置消息后可以获得其中承载的mrdc-SecondaryCellGroupConfig域的RRC重配置消息以及其包含的第一指示信息，因此IAB节点确定该mrdc-SecondaryCellGroupConfig域的RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。辅小区组配置RRC消息引入第一指示信息的示例与前述1)-4)类似，此处不再赘述。
例如，SN产生辅小区组配置RRC消息，并在辅小区组添加响应消息中发送给MN，MN在接收到SN发送的辅小区组配置RRC消息后，生成第二RRC重配置消息，可以在第二RRC重配置消息中引入新的信息元，即第一指示信息non-F1-terminating，将该辅小区组配置RRC消息放在该第二RRC重配置消息中转发至IAB节点。因此，该IAB节点在通过SRB1收到该第二RRC重配置消息后可以获得其中承载的mrdc-SecondaryCellGroupConfig域的RRC重配置消息以及第一指示信息，因此IAB节点确定该mrdc-SecondaryCellGroupConfig域的RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。第二RRC重配置消息 引入第一指示信息的示例与前述1)类似，不同之处在生成该第二RRC重配置消息时，可以不包括其自身的与IP地址配置的信息元iab-IP-AddressConfigurationList-r16。
在一些实施例中，可以双连接建立完成后配置(修改)非F1终止点拓扑域的IP地址。该第一RRC重配置消息是由该第二IAB宿主直接发送给IAB节点；该IAB节点通过SRB3接收由所述第二IAB宿主发送的所述第一RRC重配置消息。该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置，该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。
(i)隐式指示
例如，该IAB节点通过SRB3收到该第一RRC重配置消息，IAB节点知道第一RRC重配置消息是SN产生(即至少一个IP地址配置是SN提供)的，而SN是非F1终止点，因此IAB节点确定该第一RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。也就是说，IAB节点确定通过SRB1接收的第一RRC重配置消息中的至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息。
(ii)显式指示
例如，SN产生第一RRC重配置消息时，可以在其中引入新的信息元，即第一指示信息non-F1-terminating，该IAB节点通过SRB3收到该第一RRC重配置消息以及其中的第一指示信息，因此IAB节点确定该第一RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。第一RRC重配置消息引入第一指示信息的示例与前述1)-4)类似，此处不再赘述。
在一些实施例中，可以双连接建立完成后，在修改辅小区组的过程中配置(修改)非F1终止点拓扑域的IP地址。该第一RRC重配置消息是mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息，并由该第一IAB宿主发送的第二RRC重配置消息携带；该IAB节点通过SRB1接收由所述第一IAB宿主发送的所述第二RRC重配置消息。该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置，该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。
(i)隐式指示
例如，SN产生辅小区组配置RRC消息，并放在辅小区组修改请求消息中发送给MN，MN在接收到SN发送的辅小区组配置RRC消息后，生成第二RRC重配置 消息，将该辅小区组配置RRC消息放在该第二RRC重配置消息中的mrdc-SecondaryCellGroupConfig域转发至IAB节点。因此，该IAB节点在通过SRB1收到该第二RRC重配置消息后可以获得其中承载的mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息，IAB节点知道mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息是SN产生(即至少一个IP地址配置是SN提供)的，而SN是非F1终止点，因此IAB节点确定该辅小区组配置RRC消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。也就是说，IAB节点确定通过SRB1接收的mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息中的至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息。
(ii)显式指示
例如，SN产生辅小区组配置RRC消息时，可以在其中引入新的信息元，即第一指示信息non-F1-terminating，并放在辅小区组修改请求消息中发送给MN。MN在接收到SN发送的辅小区组配置RRC消息后，生成第二RRC重配置消息，将该辅小区组配置RRC消息放在该第二RRC重配置消息中的mrdc-SecondaryCellGroupConfig域转发至IAB节点，因此，该IAB节点在通过SRB1收到该第二RRC重配置消息后可以获得其中承载的mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息以及其携带的第一指示信息，因此IAB节点确定该mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。辅小区组配置RRC消息引入第一指示信息的示例与前述1)-4)类似，此处不再赘述。
例如，SN产生辅小区组配置RRC消息，并放在辅小区组修改请求消息中发送给MN，MN在接收到SN发送的辅小区组配置RRC消息后，生成第二RRC重配置消息，可以在第二RRC重配置消息中引入新的信息元，即第一指示信息non-F1-terminating，将该辅小区组配置RRC消息放在该第二RRC重配置消息中mrdc-SecondaryCellGroupConfig域转发至IAB节点。因此，该IAB节点在通过SRB1收到该第二RRC重配置消息后可以获得其中的mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息以及第一指示信息，因此IAB节点确定该mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。第二RRC重配置消息引入第一指示信息的示例与前述1)类似，不同之处在生成该第二RRC重配置消息时，可以不包括其自 身的与IP地址配置的信息元iab-IP-AddressConfigurationList-r16。
在一些实施例中，可以双连接建立完成后，在IAB传输迁移管理过程中重配置非F1终止点拓扑域的IP地址，并由MN发送给IAB节点。
(i)隐式指示
该第一RRC重配置消息是mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息，由于IAB传输迁移管理过程不支持SN产生辅小区组配置RRC消息，因此，该第一RRC重配置消息由所述第一IAB宿主代替该第二IAB宿主生成，并由该第一IAB宿主发送的第二RRC重配置消息携带。该IAB节点通过SRB1接收由所述第一IAB宿主发送的所述第二RRC重配置消息。该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置，该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。
例如，SN提供至少一个IP地址配置，并在IAB传输迁移管理响应消息中发送给MN，MN在接收到至少一个IP地址配置后，代替该第二IAB宿主生成第一RRC重配置消息，将该第一RRC重配置消息放在第二RRC重配置消息中转发至IAB节点。因此，该IAB节点在通过SRB1收到该第二RRC重配置消息后可以获得其中承载的mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息，IAB节点知道mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息中的至少一个IP地址配置是SN提供的，而SN是非F1终止点，因此IAB节点确定该辅小区组配置RRC消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。也就是说，IAB节点确定通过SRB1接收的mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息中的至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息。
(ii)显式指示
SN给MN提供至少一个IP地址配置，该第一RRC重配置消息是MN产生的；该IAB节点通过SRB1接收由所述第一IAB宿主发送的所述第二RRC重配置消息。该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置，该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。
例如，SN提供至少一个IP地址配置，并在IAB传输迁移管理响应消息中发送给MN，MN在接收到至少一个IP地址配置后，生成第一RRC重配置消息，可以在其中引入新的信息元，即第一指示信息non-F1-terminating，将该第一RRC重配置消 息发送至IAB节点，因此，该IAB节点在通过SRB1收到该第一RRC重配置消息后可以获得其中承载的至少一个IP地址信息以及第一指示信息，因此IAB节点确定该第一RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。第一RRC重配置消息引入第一指示信息的示例与前述1)-4)类似，此处不再赘述。
在一些实施例中，可以双连接建立完成后，在IAB传输迁移管理过程中重配置非F1终止点拓扑域的IP地址，该第一RRC重配置消息是SN产生的，由该第二IAB宿主直接发送给该IAB节点；该IAB节点通过SRB3接收由所述第二IAB宿主发送的所述第一RRC重配置消息。该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置，该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。
(i)隐式指示
例如，该IAB节点通过SRB3收到该第一RRC重配置消息，IAB节点知道第一RRC重配置消息是SN产生(即至少一个IP地址配置是SN提供)的，而SN是非F1终止点，因此IAB节点确定该第一RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。也就是说，IAB节点确定通过SRB1接收的第一RRC重配置消息中的至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息。
(ii)显式指示
例如，SN产生第一RRC重配置消息时，可以在其中引入新的信息元，即第一指示信息non-F1-terminating，该IAB节点通过SRB3收到该第一RRC重配置消息以及其中的第一指示信息，因此IAB节点确定该第一RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。第一RR例与前述1)-4)类似，此处不再赘述。
在一些实施例中，可以双连接建立完成后，在修改辅小区组的过程中配置(修改)F1终止点拓扑域的IP地址。该第一RRC重配置消息是MN产生的，由该第一IAB宿主直接发送给该IAB节点；该IAB节点通过SRB1接收由所述第一IAB宿主发送的所述第一RRC重配置消息。该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置，该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，F1终止点拓扑域的IP地址是指锚定于donor-DU1的IP地址。
(i)隐式指示
例如，该IAB节点通过SRB1收到该第一RRC重配置消息，IAB节点知道第一RRC重配置消息是MN产生(即至少一个IP地址配置是MN提供)的，而MN是F1终止点，因此IAB节点确定该第一RRC重配置消息承载的至少一个IP地址配置是F1终止点拓扑域的IP地址信息。也就是说，IAB节点确定通过SRB1接收的第一RRC重配置消息中的至少一个IP地址配置包含F1终止点拓扑域的IP地址信息。
(ii)显式指示
例如，MN产生第一RRC重配置消息时，不需要在其中引入新的信息元，即第一指示信息non-F1-terminating，该IAB节点通过SRB1收到该第一RRC重配置消息，由于其中不包含第一指示信息，即IAB节点没有收到第一指示信息，因此IAB节点确定该第一RRC重配置消息承载的至少一个IP地址配置是F1终止点拓扑域的IP地址信息。
(三)针对双连接场景二
在一些实施例中，图13是双连接场景二示意图，如图13所示，在双连接场景二中，第一IAB宿主(F1终止点宿主)是该IAB节点的主节点SN，第二IAB宿主(该非F1终止点宿主)是该IAB节点的辅节点MN，建立双连接后，可将边界节点的部分业务迁移至非F1终止点拓扑域，部分业务仍然在F1终止点宿主拓扑域。非F1终止点拓扑域的IP地址是指锚定于donor-DU1的IP地址，F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。由于F1连接是在建立双连接后完成的，因此，与双连接场景一不同的是，不可以在双连接建立过程中配置非F1终止点拓扑域的IP地址，仅可以在双连接建立完成后配置非F1终止点拓扑域的IP地址或者F1终止点拓扑域的IP地址。在隐式指示时，IAB节点可确定通过SRB1接收的RRC消息中的该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，或者可确定通过SRB1接收的辅小区组配置信息中的该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者可确定通过SRB3接收的RRC消息中的该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息。在显式指示时，IAB节点可以在接收到第一指示信息时确定第一RRC重配置消息中的该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，在没有接收到第一指示信息时确定第一RRC重配置消息中的该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，以下分情况说明。
在一些实施例中，可以双连接建立完成后配置(修改)非F1终止点拓扑域的IP地址。该第一RRC重配置消息是由该第二IAB宿主发送给IAB节点；该IAB节点 通过SRB1接收由所述第二IAB宿主发送的所述第一RRC重配置消息。该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置，该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，非F1终止点拓扑域的IP地址是指锚定于donor-DU1的IP地址。
(i)隐式指示
例如，该IAB节点通过SRB1收到该第一RRC重配置消息，IAB节点知道第一RRC重配置消息是MN产生(即至少一个IP地址配置是MN提供)的，而MN是非F1终止点，因此IAB节点确定该第一RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。也就是说，IAB节点确定通过SRB1接收的第一RRC重配置消息中的至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息。
(ii)显式指示
例如，MN产生第一RRC重配置消息时，可以在其中引入新的信息元，即第一指示信息non-F1-terminating，该IAB节点通过SRB1收到该第一RRC重配置消息以及其中的第一指示信息，因此IAB节点确定该第一RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。第一RRC重配置消息引入第一指示信息的示例与前述1)-4)类似，此处不再赘述。
在一些实施例中，可以双连接建立完成后，在修改辅小区组的过程中配置(修改)F1终止点拓扑域的IP地址。该第一RRC重配置消息是第一IAB宿主生成的；该IAB节点通过SRB3接收由所述第一IAB宿主发送的所述第一RRC重配置消息。该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置，该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。
(i)隐式指示
例如，该IAB节点通过SRB3收到该第一RRC重配置消息，IAB节点知道第一RRC重配置消息是SN产生(即至少一个IP地址配置是SN提供)的，而SN是F1终止点，因此IAB节点确定该第一RRC重配置消息承载的至少一个IP地址配置是F1终止点拓扑域的IP地址信息。也就是说，IAB节点确定通过SRB3接收的第一RRC重配置消息中的至少一个IP地址配置包含F1终止点拓扑域的IP地址信息。
(ii)显式指示
例如，SN产生第一RRC重配置消息时，不需要在其中引入新的信息元，即第一 指示信息non-F1-terminating，该IAB节点通过SRB3收到该第一RRC重配置消息，由于IAB节点没有接收到第一指示信息，因此确定通过SRB3接收的第一RRC重配置消息中的至少一个IP地址配置包含F1终止点拓扑域的IP地址信息。
在一些实施例中，可以双连接建立完成后，在修改辅小区组的过程中配置(修改)F1终止点拓扑域的IP地址。该第一RRC重配置消息是RRC重配置消息的mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息，完全由第一IAB宿主产生并由该第二IAB宿主发送的第三RRC重配置消息携带；该IAB节点通过SRB1接收由所述第二IAB宿主发送的所述第三RRC重配置消息。该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置，该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。
(i)隐式指示
例如，SN产生辅小区组配置RRC消息，并放在辅小区组修改需求消息中发送给MN，MN在接收到SN发送的辅小区组配置RRC消息后，生成第三RRC重配置消息，将该辅小区组配置RRC消息放在该第三RRC重配置消息中的mrdc-SecondaryCellGroupConfig域转发至IAB节点。因此，该IAB节点在通过SRB1收到该第三RRC重配置消息后可以获得其中承载的mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息，IAB节点知道mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息是SN产生(即至少一个IP地址配置是SN提供)的，而SN是F1终止点，因此IAB节点确定该mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息承载的至少一个IP地址配置是F1终止点拓扑域的IP地址信息。也就是说，IAB节点确定通过SRB1接收的辅小区组配置RRC消息中的至少一个IP地址配置包含F1终止点拓扑域的IP地址信息。
(ii)显式指示
例如，SN产生辅小区组配置RRC消息时，不需要在其中引入新的信息元，即第一指示信息non-F1-terminating，并将辅小区组配置RRC消息放在辅小区组修改需求消息中发送给MN，MN在接收到SN发送的辅小区组配置RRC消息后，生成第三RRC重配置消息，将该辅小区组配置RRC消息放在该第三RRC重配置消息中mrdc-SecondaryCellGroupConfig域转发至IAB节点。因此，该IAB节点在通过SRB1收到该第三RRC重配置消息后可以获得其中承载的mrdc-SecondaryCellGroupConfig 域包含的RRC重配置消息，但由于第一RRC重配置消息和第三RRC重配置消息中都不包含第一指示信息，即IAB节点没有接收到第一指示信息，因此IAB节点确定该辅小区组配置RRC消息承载的至少一个IP地址配置是F1终止点拓扑域的IP地址信息。
在一些实施例中，可以双连接建立完成后，在IAB传输迁移管理过程中配置(修改)非F1终止点拓扑域的IP地址，该第一RRC重配置消息由所述第二IAB宿主生成，并由该第二IAB宿主发送给IAB节点。该IAB节点通过SRB1接收由所述第二IAB宿主发送的所述第一RRC重配置消息。该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置，该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，非F1终止点拓扑域的IP地址是指锚定于donor-DU1的IP地址。
(i)隐式指示
例如，SN向MN发送IAB传输迁移管理请求消息，MN(第二IAB宿主，非F1终止点宿主)在接收到该请求消息后，生成第一RRC重配置消息，其中该至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息，并将该第一RRC重配置消息发送至IAB节点。因此，该IAB节点在通过SRB1收到该第一RRC重配置消息后可以获得其中承载的至少一个IP地址配置，IAB节点知道该至少一个IP地址配置是MN提供的，而MN是非F1终止点，因此IAB节点确定该第一RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。也就是说，IAB节点确定通过SRB1接收的第一RRC重配置消息中的至少一个IP地址配置包含非F1终止点拓扑域的IP地址信息。
(ii)显式指示
例如，SN向MN发送IAB传输迁移管理请求消息，MN(第二IAB宿主，非F1终止点宿主)在接收到该请求消息后，生成第一RRC重配置消息，可以在其中引入新的信息元，即第一指示信息non-F1-terminating，将该第一RRC重配置消息发送至IAB节点，因此，该IAB节点在通过SRB1收到该第一RRC重配置消息后可以获得其中承载的至少一个IP地址信息以及第一指示信息，因此IAB节点确定该第一RRC重配置消息承载的至少一个IP地址配置是非F1终止点拓扑域的IP地址信息。第一RRC重配置消息引入第一指示信息的示例与前述1)-4)类似，此处不再赘述。
在一些实施例中，可以双连接建立完成后，在IAB传输迁移管理过程中配置(修改)F1终止点拓扑域的IP地址，该第一RRC重配置消息由所述第二IAB宿主代替 第一IAB宿主生成，并由该第二IAB宿主发送给IAB节点。该IAB节点通过SRB1接收由所述第二IAB宿主发送的所述第一RRC重配置消息。该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置，该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。
(i)隐式指示
例如，SN提供至少一个IP地址配置(包含F1终止点拓扑域的IP地址信息)，并放在IAB传输迁移修改请求消息中发给MN(第二IAB宿主，非F1终止点宿主)，MN在接收到该请求消息后，代替SN生成辅小区配置RRC消息，其中该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，并生成第三RRC重配置消息，将该第一RRC重配置消息放在该第三RRC重配置消息中的mrdc-SecondaryCellGroupConfig域转发至IAB节点。因此，该IAB节点在通过SRB1收到该第三RRC重配置消息后可以获得其中承载的mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息，IAB节点知道mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息中的至少一个IP地址配置是SN提供的，而SN是F1终止点宿主，因此IAB节点确定第一RRC重配置消息承载的至少一个IP地址配置是F1终止点拓扑域的IP地址信息。也就是说，IAB节点确定通过SRB1接收的第一RRC重配置消息中mrdc-SecondaryCellGroupConfig域包含的RRC重配置消息的至少一个IP地址配置包含F1终止点拓扑域的IP地址信息。
(ii)显式指示
SN提供至少一个IP地址配置(包含F1终止点拓扑域的IP地址信息)，并放在IAB传输迁移修改请求消息中发给MN(第二IAB宿主，非F1终止点宿主)，MN在接收到该请求消息后，生成第一RRC重配置消息，其中该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息。但不需要在第一RRC重配置消息中引入第一指示信息，由于第一RRC重配置消息中不包含第一指示信息，即IAB节点没有接收到第一指示信息，因此IAB节点确定该RRC消息承载的至少一个IP地址配置是F1终止点拓扑域的IP地址信息。
以上对如何非F1终止点拓扑域或F1终止点拓扑域的IP地址进行配置和指示，以及IAB节点如何区分配置的IP地址是非F1终止点拓扑域或F1终止点拓扑域进行了说明。在以上实施例中，IAB节点可以知道MN或者SN是F1终止点宿主还是非 F1终止点宿主，例如IAB节点可以根据接收到的BAP配置信息(bap-config-r16域)由哪个宿主提供，从而确定MN或者SN是F1终止点宿主。
以上显式指示中，以是否接收到第一指示信息为例说明如何确定配置的IP地址是非F1终止点拓扑域或F1终止点拓扑域，但本申请并不以此作为限制，例如该第一指示信息用于指示IP地址配置是否包含非F1终止点拓扑域的IP地址信息，或者说该第一指示信息用于指示IP地址配置包含非F1终止点拓扑域的IP地址信息还是包含F1终止点拓扑域的IP地址信息。例如，该IAB接收到第一指示信息，该第一指示信息的值为第一值(true或1)时，确定IP地址配置包含非F1终止点拓扑域的IP地址信息，该第一指示信息的值为第二值(false或0)时，确定IP地址配置包含F1终止点拓扑域的IP地址信息，具体流程与前述相同，此处不再一一举例。
以上信令过程仅示意性对本申请实施例进行了说明，但本申请不限于此，关于信令的更具体的内容，还可以参考相关技术。此外，例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图10的记载。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，可以通过该第一RRC重配置消息向IAB节点配置非F1终止点拓扑域的IP地址或者F1终止点拓扑域的IP地址，这样，可以使boundary node可以分别传输routing ID属于F1-terminating拓扑域的业务和routing ID属于non-F1-terminating拓扑域的业务。
第二方面的实施例
本申请实施例提供一种传输地址确定方法，从第一IAB宿主侧进行说明。与第一方面的实施例相同的内容不再赘述。
图14是本申请实施例的传输地址确定方法的另一示意图。如图14所示，该方法包括：
1401，该第一IAB宿主发送第一RRC重配置消息，该第一RRC重配置消息中包括至少一个针对IAB节点的IP地址配置；或者发送至少一个针对该IAB节点的IP地址配置；
该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息；
在一些实施例中，该第一IAB宿主可以向该IAB节点或第二IAB宿主发送该第一RRC重配置消息，该IAB节点的F1连接终止于该第一IAB宿主，并且该IAB节点与该第二IAB宿主有RRC连接。
在一些实施例中，可以隐式的指示配置的IP地址是否属于非F1终止点拓扑域，或者可以显式的指示配置的IP地址是否属于非F1终止点拓扑域，例如该第一IAB宿主通过第一指示信息指示该IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
在一些实施例中，该IP地址配置包含非F1终止点拓扑域的IP地址信息。
在一些实施例中，该第一IAB宿主是该IAB节点切换的源宿主，该第二IAB宿主是该IAB节点切换的目标宿主，该第一RRC重配置消息是切换命令RRC消息；该方法还可以包括：该第一IAB宿主接收该第二IAB宿主发送的第一RRC重配置消息，在1401中，该第一IAB宿主向该IAB节点转发由该第二IAB宿主生成的该第一RRC重配置消息。
在一些实施例中，该第一IAB宿主是该IAB节点的主节点MN，该第二IAB宿主是该IAB节点的辅节点SN。
例如，该第一RRC重配置消息是RRC重配置消息中的辅小区组配置域包含的RRC重配置消息并由该第一IAB宿主发送的第二RRC重配置消息携带；该第一IAB宿主通过SRB1向该IAB节点发送该第二RRC重配置消息。
该方法还包括：该第一IAB宿主接收该第二IAB宿主发送的该第一RRC重配置消息(该第一RRC重配置消息由第二IAB宿主生成)。并且，在1401中，该第一IAB宿主通过SRB1向该IAB节点发送该第二RRC重配置消息(该第二RRC重配置消息由第一IAB宿主生成)，该第二RRC重配置消息中承载该第一RRC重配置消息。
或者，该方法还可以包括：该第一IAB宿主接收该第二IAB宿主提供的该IP地址配置，并代替该第二IAB宿主生成该第一RRC重配置消息，并且，在1401中，该第一IAB宿主通过SRB1向该IAB节点发送该第二RRC重配置消息(该第二RRC重配置消息也由第一IAB宿主生成)，该第二RRC重配置消息中承载该第一RRC重配置消息。
例如，该方法还可以包括：该第一IAB宿主接收该第二IAB宿主提供的该IP地址配置，并生成第一RRC重配置消息，在1401中，该第一IAB宿主通过SRB1向该IAB节点发送该第一RRC重配置消息。
在上述实施例中，该IP地址配置包含非F1终止点拓扑域的IP地址信息，在显式指示时，该第一IAB宿主通过该第一RRC重配置消息或该第二RRC重配置消息包含该第一指示信息指示该IP地址配置包含非F1止点拓扑域的IP地址信息。该第一指示信息包含在该第一RRC重配置消息或该第二RRC重配置消息的新增的信息元中，或者包含在该第一RRC重配置消息或该第二RRC重配置消息的IP地址配置列表信息元中，或者包含在该第一RRC重配置消息或该第二RRC重配置消息的IP地址配置信息元中，或者包含在该第一RRC重配置消息或该第二RRC重配置消息的IP地址索引信息元中。
在一些实施例中，该IP地址配置包含F1终止点拓扑域的IP地址信息。
在一些实施例中，该第一IAB宿主是该IAB节点的SN，该第二IAB宿主是该IAB节点的MN。
例如，在1401中，该第一IAB宿主通过SRB3向该IAB节点发送该第一RRC重配置消息。
例如，在1401中，该第一IAB宿主向该第二IAB宿主发送该第一RRC重配置消息，其中，该第一RRC重配置消息为辅小区组配置RRC消息。
例如，在1401中，该第一IAB宿主向该第二IAB宿主发送该IP地址配置，该IP地址配置使用IAB传输迁移修改请求消息承载。
在一些实施例中，该第一IAB宿主是该IAB节点的主节点MN，该第二IAB宿主是该IAB节点的辅节点SN。
例如，该第一IAB宿主通过SRB1向该IAB节点发送该第一RRC重配置消息。
在上述实施例中，该IP地址配置包含F1终止点拓扑域的IP地址信息。在显式指示时，该第一IAB宿主通过该第一RRC重配置消息不包含该第一指示信息指示该IP地址配置包含F1止点拓扑域的IP地址信息。
值得注意的是，以上附图14仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图14的记载。
由上述实施例可知，可以通过该第一RRC重配置消息向IAB节点配置非F1终止点拓扑域的IP地址或者F1终止点拓扑域的IP地址，这样，可以使boundary node可以分别传输routing ID属于F1-terminating拓扑域的业务和routing ID属于non-F1-terminating拓扑域的业务。
第三方面的实施例
本申请实施例提供一种传输地址确定方法，从第二IAB宿主侧进行说明。
图15是本申请实施例的传输地址确定方法的一示意图。如图15所示，该方法包括：
1501，该第二IAB宿主发送第一RRC重配置消息，该第一RRC重配置消息中包括至少一个针对IAB节点的IP地址配置；或者发送至少一个针对IAB节点的IP地址配置；
该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
在一些实施例中，该第二IAB宿主可以向该IAB节点或第一IAB宿主发送该第一RRC重配置消息，该IAB节点的F1连接终止于该第一IAB宿主，并且该IAB节点与该第二IAB宿主有RRC连接。
在一些实施例中，可以隐式的指示配置的IP地址是否属于非F1终止点拓扑域，或者可以显式的指示配置的IP地址是否属于非F1终止点拓扑域，例如该第二IAB宿主通过第一指示信息指示该IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
在一些实施例中，该IP地址配置包含非F1终止点拓扑域的IP地址信息。
在一些实施例中，该第一IAB宿主是该IAB节点切换的源宿主，该第二IAB宿主是该IAB节点切换的目标宿主，该第一RRC重配置消息是切换命令RRC消息，并且，在1501中，该第二IAB宿主向该第一IAB宿主发送该第一RRC重配置消息。
在一些实施例中，该第一IAB宿主是该IAB节点的主节点MN，该第二IAB宿主是该IAB节点的辅节点SN。
例如，在1501中，该第二IAB宿主向该第一IAB宿主发送第一RRC重配置消息；或者，
例如，在1501中，该第二IAB宿主向该第一IAB宿主发送该IP地址配置。
例如，在1501中，该第二IAB宿主通过SRB3向该IAB节点发送该第一RRC重配置消息。
在一些实施例中，该第二IAB宿主是该IAB节点的主节点MN，该第一IAB宿主是该IAB节点的辅节点SN。
例如，在1501中，该第二IAB宿主通过SRB1向该IAB节点发送该第一RRC重配置消息。
在上述实施例中，该IP地址配置包含非F1终止点拓扑域的IP地址信息，在显式指示时，该第二IAB宿主通过该第一RRC重配置消息包含该第一指示信息指示该IP地址配置包含非F1止点拓扑域的IP地址信息。该第一指示信息包含在该第一RRC重配置消息的新增的信息元中，或者包含在该第一RRC重配置消息的IP地址配置列表信息元中，或者包含在该第一RRC重配置消息的IP地址配置信息元中，或者包含在该第一RRC重配置消息的IP地址索引信息元中。
在一些实施例中，该IP地址配置包含F1终止点拓扑域的IP地址信息。
在一些实施例中，该第一IAB宿主是该IAB节点的SN，该第二IAB宿主是该IAB节点的MN。
例如，该第一RRC重配置消息是RRC重配置消息中的辅小区组配置域包含的RRC重配置消息，并由该第二IAB宿主发送的第三RRC重配置消息携带；在1501中，该第二IAB宿主通过SRB1向该IAB节点发送该第三RRC重配置消息。
该方法还包括：该第二IAB宿主接收该第一IAB宿主发送第一RRC重配置消息。
例如，在1501中，该第二IAB宿主接收该第一IAB宿主提供的该IP地址配置，并代替该第一IAB宿主生成该第一RRC重配置消息。
例如，该方法还可以包括，该第二IAB宿主接收该第一IAB宿主发送的该IP地址配置，在1501中，该第二IAB宿主通过SRB1向该IAB节点发送该第一RRC重配置消息。
在上述实施例中，该IP地址配置包含F1终止点拓扑域的IP地址信息。在显式指示时，该第一IAB宿主通过该第一RRC重配置消息或该第三RRC重配置消息不包含该第一指示信息指示该IP地址配置包含F1止点拓扑域的IP地址信息。
值得注意的是，以上附图15仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些 操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图15的记载。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，可以通过该第一RRC重配置消息向IAB节点配置非F1终止点拓扑域的IP地址或者F1终止点拓扑域的IP地址，这样，可以使boundary node可以分别传输routing ID属于F1-terminating拓扑域的业务和routing ID属于non-F1-terminating拓扑域的业务。
第四方面的实施例
本申请实施例提供一种IAB节点设备，与第一方面的实施例相同的内容不再赘述。该设备例如可以是IAB系统中的IAB节点(如第一方面的实施例中的边界节点)，也可以是配置于该IAB节点中的某个或某些部件或者组件或者模块。
图16是本申请实施例的IAB节点设备的一示意图。如图16所示，IAB节点设备1600包括：
第一接收部1601，其接收第一RRC重配置消息，该第一RRC重配置消息中包括针对该IAB节点的至少一个IP地址配置；
该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
在一些实施例中，该IAB节点的F1连接终止于第一IAB宿主，并且该IAB节点与第二IAB宿主有RRC连接。
在一些实施例中，该设备还包括：
第一处理部1602，其确定该IP地址配置包含F1终止点拓扑域的IP地址信息或非F1终止点拓扑域的IP地址信息。
在一些实施例中，该第一处理部根据第一指示信息确定该IP地址配置包含F1终止点拓扑域的IP地址信息或非F1终止点拓扑域的IP地址信息。
在一些实施例中，该第一处理部确定该IP地址配置包含非F1终止点(non-F1-terminating)拓扑域的IP地址信息。
在一些实施例中，该第一IAB宿主是该IAB节点切换的源宿主，该第二IAB宿 主是该IAB节点切换的目标宿主；该第一RRC重配置消息是第一IAB宿主转发的由第二IAB宿主生成的切换命令RRC消息。
在一些实施例中，该第一IAB宿主是该IAB节点的主节点MN，该第二IAB宿主是该IAB节点的辅节点SN。
例如，该第一RRC重配置消息是RRC重配置消息中的辅小区组配置域包含的RRC重配置消息，并由该第一IAB宿主发送的第二RRC重配置消息携带；该第一接收部通过SRB1接收由该第一IAB宿主发送的该第二RRC重配置消息。可选的，该第一RRC重配置消息由该第一IAB宿主代替该第二IAB宿主生成。
例如，该第一接收部通过SRB3接收由该第二IAB宿主发送的该第一RRC重配置消息。
例如，该第一接收部通过SRB1接收由该第一IAB宿主发送的该第一RRC重配置消息。
在一些实施例中，该第一IAB宿主是该IAB节点的SN，该第二IAB宿主是该IAB节点的MN；该第一接收部通过SRB1接收由该第二IAB宿主发送的该第一RRC重配置消息。
在一些实施例中，该第一处理部在该第一RRC重配置消息或该第二RRC重配置消息中包含该第一指示信息时，确定该IP地址配置包含非F1止点拓扑域的IP地址信息。该第一指示信息包含在该第一RRC重配置消息或该第二RRC重配置消息的新增的信息元中，或者包含在该第一RRC重配置消息或该第二RRC重配置消息的IP地址配置列表信息元中，或者包含在该第一RRC重配置消息或该第二RRC重配置消息的IP地址配置信息元中，或者包含在该第一RRC重配置消息或该第二RRC重配置消息的IP地址索引信息元中。
在一些实施例中，该第一处理部确定该IP地址配置包含F1终止点(F1-terminating)拓扑域的IP地址信息。
在一些实施例中，该第一IAB宿主是该IAB节点的主节点MN，该第二IAB宿主是该IAB节点的辅节点SN；该第一接收部通过SRB1接收由该第一IAB宿主发送的该第一RRC重配置消息。
在一些实施例中，该第一IAB宿主是该IAB节点的SN，该第二IAB宿主是该IAB节点的MN。
例如，该第一RRC重配置消息是RRC重配置消息中的辅小区组配置域包含的 RRC重配置消息，并由该第二IAB宿主发送的第三RRC重配置消息携带；该第一接收部通过SRB1接收由该第二IAB宿主发送的该第三RRC重配置消息。可选的，该第一RRC重配置消息由该第二IAB宿主代替该第一IAB宿主生成。
例如，该第一接收部通过SRB3接收由该第一IAB宿主发送的该第一RRC重配置消息。
例如，该第一接收部通过SRB1接收由该第二IAB宿主发送的该第一RRC重配置消息。
在一些实施例中，该第一处理部在该第一RRC重配置消息或该第三RRC重配置消息中不包含该第一指示信息时，确定该IP地址配置包含F1止点拓扑域的IP地址信息。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的IAB节点设备1600还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图16中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，可以通过该第一RRC重配置消息向IAB节点配置非F1终止点拓扑域的IP地址或者F1终止点拓扑域的IP地址，这样，可以使boundary node可以分别传输routing ID属于F1-terminating拓扑域的业务和routing ID属于non-F1-terminating拓扑域的业务。
第五方面的实施例
本申请实施例提供一种IAB宿主设备，与第二方面的实施例相同的内容不再赘述。该设备例如可以是IAB系统中的IAB donor-CU(如第一、二、三方面的实施例中的第一IAB宿主)，也可以是配置于该IAB donor-CU中的某个或某些部件或者组件或者模块。
图17是本申请实施例的IAB宿主设备的一示意图。如图17所示，IAB宿主设备1700包括：
第一发送部1701，其发送第一RRC重配置消息，该第一RRC重配置消息中包括至少一个针对IAB节点的IP地址配置；或者，发送至少一个该IAB节点的IP地址配置；
该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息；
其中，该IAB节点的F1连接终止于该第一IAB宿主，并且IAB节点与第二IAB宿主有RRC连接。
在一些实施例中，该IAB宿主设备通过第一指示信息指示该IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
在一些实施例中，该IP地址配置包含非F1终止点拓扑域的IP地址信息。
在一些实施例中，该第一IAB宿主是该IAB节点切换的源宿主，该第二IAB宿主是该IAB节点切换的目标宿主，该第一RRC重配置消息是切换命令RRC消息；
其中，该设备还包括(未图示)：第二接收部，其接收该第二IAB宿主发送的第一RRC重配置消息，并且该第一发送部向该IAB节点转发由该第二IAB宿主生成的该第一RRC重配置消息。
在一些实施例中，该第一IAB宿主是该IAB节点的主节点MN，该第二IAB宿主是该IAB节点的辅节点SN。
例如，该第一RRC重配置消息是RRC重配置消息中的辅小区组配置域包含的RRC重配置消息，并由该第一IAB宿主发送的第二RRC重配置消息携带；
该第一发送部通过SRB1向该IAB节点发送该第二RRC重配置消息。
在一些实施例中，该设备还包括：(未图示)
第三接收部，其接收该第二IAB宿主发送的该第一RRC重配置消息。
在一些实施例中，该设备还包括：(未图示)
第四接收部，其接收该第二IAB宿主提供的该IP地址配置；
第二处理部，其代替所述第二IAB宿主生成所述第一RRC重配置消息。
在一些实施例中，该设备还包括：(未图示)
第五接收部，其接收该第二IAB宿主提供的该IP地址配置，并且该第一发送部通过SRB1发送该第一RRC重配置消息。
在一些实施例中，该IAB宿主设备通过该第一RRC重配置消息或该第二RRC重配置消息包含该第一指示信息指示该IP地址配置包含非F1止点拓扑域的IP地址信息。
在一些实施例中，该IP地址配置包含F1终止点拓扑域的IP地址信息。
在一些实施例中，该第一IAB宿主是该IAB节点的SN，该第二IAB宿主是该IAB节点的MN。
例如，该第一发送部通过SRB3向该IAB节点发送该第一RRC重配置消息。
例如，该第一发送部向该第二IAB宿主发送该第一RRC重配置消息，其中，该第一RRC重配置消息为辅小区组配置RRC消息；或者，
该第一发送部向该第二IAB宿主发送该IP地址配置。
在一些实施例中，该第一IAB宿主是该IAB节点的主节点MN，该第二IAB宿主是该IAB节点的辅节点SN；该第一发送部通过SRB1向该IAB节点发送该第一RRC重配置消息。
在一些实施例中，该IAB宿主设备通过该第一RRC重配置消息不包含该第一指示信息指示该IP地址配置包含F1止点拓扑域的IP地址信息。
在一些实施例中，该第一指示信息包含在该第一RRC重配置消息或该第二RRC重配置消息的新增的信息元中，或者包含在该第一RRC重配置消息或该第二RRC重配置消息的IP地址配置列表信息元中，或者包含在该第一RRC重配置消息或该第二RRC重配置消息的IP地址配置信息元中，或者包含在该第一RRC重配置消息或该第二RRC重配置消息的IP地址索引信息元中。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的IAB宿主设备1700还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图17中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，可以通过该第一RRC重配置消息向IAB节点配置非F1终止点拓扑域的IP地址或者F1终止点拓扑域的IP地址，这样，可以使boundary node可以分别传输routing ID属于F1-terminating拓扑域的业务和routing ID属于non-F1-terminating拓扑域的业务。
第六方面的实施例
本申请实施例提供一种IAB宿主设备，与第三方面的实施例相同的内容不再赘述。该设备例如可以是IAB系统中的IAB donor-CU(如第一、二、三方面的实施例中的第二IAB宿主)，也可以是配置于该IAB donor-CU中的某个或某些部件或者组件或者模块。
图18是本申请实施例的IAB宿主设备的一示意图。如图18所示，IAB宿主设备1800包括：
第二发送部1801，其发送第一RRC重配置消息，该第一RRC重配置消息中包括至少一个针对IAB节点的IP地址配置；或者发送至少一个针对IAB节点的IP地址配置；
该至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
其中，该IAB节点的F1连接终止于第一IAB宿主，并且该IAB节点与该第二IAB宿主有RRC连接。
在一些实施例中，该IAB宿主设备通过第一指示信息指示该IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
在一些实施例中，该IP地址配置包含非F1终止点拓扑域的IP地址信息。
在一些实施例中，该第一IAB宿主是该IAB节点切换的源宿主，该第二IAB宿主是该IAB节点切换的目标宿主，该第一RRC重配置消息是切换命令RRC消息，并且，该第二发送部向该第一IAB宿主发送该第一RRC重配置消息。
在一些实施例中，该第一IAB宿主是该IAB节点的主节点MN，该第二IAB宿主是该IAB节点的辅节点SN。
例如，该第二发送部向该第一IAB宿主发送第一RRC重配置消息；或者，向该第一IAB宿主发送该IP地址配置。
例如，该第二发送部通过SRB3向该IAB节点发送该第一RRC重配置消息。
在一些实施例中，该第一IAB宿主是该IAB节点的SN，该第二IAB宿主是该IAB节点的MN；该第二发送部通过SRB1向该IAB节点发送该第一RRC重配置消息。
在一些实施例中，该IAB宿主设备通过该第一RRC重配置消息包含该第一指示信息指示该IP地址配置包含非F1止点拓扑域的IP地址信息。
在一些实施例中，该IP地址配置包含F1终止点拓扑域的IP地址信息。
在一些实施例中，该第一IAB宿主是该IAB节点的SN，该第二IAB宿主是该IAB节点的MN。
例如，该第一RRC重配置消息是RRC重配置消息中的辅小区组配置域包含的RRC重配置消息，并由该第二IAB宿主发送的第三RRC重配置消息携带；该第二发送部通过SRB1向该IAB节点发送该第三RRC重配置消息。
在一些实施例中，该设备还包括：(未图示)
第六接收部，其接收该第一IAB宿主发送第一RRC重配置消息。
在一些实施例中，该设备还包括：(未图示)
第七接收部，其接收该第一IAB宿主提供的该IP地址配置；
第二处理部，其代替该第一IAB宿主生成该第一RRC重配置消息。
在一些实施例中，该设备还包括：(未图示)
第八接收部，其接收该第一IAB宿主发送的该IP地址配置，并且，该第二发送部通过SRB1向该IAB节点发送该第一RRC重配置消息。
在一些实施例中，该IAB宿主设备通过该第一RRC重配置消息或该第三RRC重配置消息不包含该第一指示信息指示该IP地址配置包含F1终止点拓扑域的IP地址信息。
在一些实施例中，该第一指示信息包含在该第一RRC重配置消息或该第二RRC重配置消息的新增的信息元中，或者包含在该第一RRC重配置消息或该第二RRC重配置消息的IP地址配置列表信息元中，或者包含在该第一RRC重配置消息或该第二RRC重配置消息的IP地址配置信息元中，或者包含在该第一RRC重配置消息或该第二RRC重配置消息的IP地址索引信息元中。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的IAB宿主设备1800还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图18中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，可以通过该第一RRC重配置消息向IAB节点配置非F1终止点拓扑域的IP地址或者F1终止点拓扑域的IP地址，这样，可以使boundary node可以分别传输routing ID属于F1-terminating拓扑域的业务和routing ID属于non-F1-terminating拓扑域的业务。
第七方面的实施例
本申请实施例提供了一种通信系统，包括第四方面实施例的第一IAB宿主(donor)设备、第五方面实施例的第二IAB宿主设备和第三方面实施例的IAB节点(IAB-node)设备；关于宿主(donor)设备、IAB节点设备的网络架构还可以参考相关技术，此处省略说明。
本申请实施例还提供一种IAB设备，该IAB设备可以是IAB宿主设备，也可以是IAB节点设备(迁移节点或者子节点)。
图9是本申请实施例的IAB设备的示意图。如图9所示，IAB设备900可以包括：处理器(例如中央处理器CPU)901和存储器902；存储器902耦合到处理器901。其中该存储器902可存储各种数据；此外还存储信息处理的程序905，并且在中央处理器901的控制下执行该程序905。
例如，处理器901可以被配置为执行程序而实现如第一方面的实施例中的传输地址确定方法。
再例如，处理器901可以被配置为执行程序而实现如第二方面的实施例中的传输地址确定方法。
再例如，处理器901可以被配置为执行程序而实现如第三方面的实施例中的传输地址确定方法。
此外，如图9所示，IAB设备900还可以包括：收发机903和天线904等；其中， 上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，IAB设备900也并不是必须要包括图9中所示的所有部件；此外，IAB设备900还可以包括图9中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机可读程序，其中当在IAB设备中执行所述程序时，所述程序使得计算机在所述IAB设备中执行第一至第三方面的实施例中的传输地址确定方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在IAB设备中执行第一至第三方面的实施例中的传输地址确定方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。逻辑部件例如现场可编程逻辑部件、微处理器、计算机中使用的处理器等。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立 门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于本实施例公开的上述实施方式，还公开了如下的附记：
边界节点
1.一种传输地址确定方法，应用于接入和回传IAB节点设备，其特征在于，所述方法包括：
所述IAB节点接收第一RRC重配置消息，所述第一RRC重配置消息中包括针对所述IAB节点的至少一个IP地址配置；
所述至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
2.根据附记1所述的方法，其中，所述IAB节点的F1连接终止于第一IAB宿主，并且所述IAB节点与第二IAB宿主有RRC连接。
3.根据附记2所述的方法，其中，所述方法还包括：
所述IAB节点确定所述IP地址配置包含F1终止点拓扑域的IP地址信息或非F1终止点拓扑域的IP地址信息。
4.根据附记3所述的方法，其中，所述IAB节点根据第一指示信息确定所述IP地址配置包含F1终止点拓扑域的IP地址信息或非F1终止点拓扑域的IP地址信息。
5.根据附记3或4所述的方法，其中，所述IAB节点确定所述IP地址配置包含非F1终止点(non-F1-terminating)拓扑域的IP地址信息。
6.根据附记5所述的方法，其中，所述第一IAB宿主是所述IAB节点切换的源宿主，所述第二IAB宿主是所述IAB节点切换的目标宿主；
所述第一RRC重配置消息是第一IAB宿主转发的由第二IAB宿主生成的切换命令RRC消息。
7.根据附记5所述的方法，其中，所述第一IAB宿主是所述IAB节点的主节点 MN，所述第二IAB宿主是所述IAB节点的辅节点SN。
8.根据附记7所述的方法，其中，所述第一RRC重配置消息是RRC重配置消息中的辅小区组配置域包含的RRC重配置消息，并由所述第一IAB宿主发送的第二RRC重配置消息携带；
所述IAB节点通过SRB1接收由所述第一IAB宿主发送的所述第二RRC重配置消息。
9.根据附记8所述的方法，其中，所述第一RRC重配置消息由所述第一IAB宿主代替所述第二IAB宿主生成。
10.根据附记7所述的方法，其中，所述IAB节点通过SRB3接收由所述第二IAB宿主发送的所述第一RRC重配置消息。
11.根据附记7所述的方法，其中，所述IAB节点通过SRB1接收由所述第一IAB宿主发送的所述第一RRC重配置消息。
12.根据附记5所述的方法，其中，所述第一IAB宿主是所述IAB节点的SN，所述第二IAB宿主是所述IAB节点的MN；
所述IAB节点通过SRB1接收由所述第二IAB宿主发送的所述第一RRC重配置消息。
13.根据附记5至12任一项所述的方法，其中，所述IAB节点在所述第一RRC重配置消息或所述第二RRC重配置消息中包含所述第一指示信息时，确定所述IP地址配置包含非F1止点拓扑域的IP地址信息。
14.根据附记3或4所述的方法，其中，所述IAB节点确定所述IP地址配置包含F1终止点(F1-terminating)拓扑域的IP地址信息。
15.根据附记14所述的方法，其中，所述第一IAB宿主是所述IAB节点的主节点MN，所述第二IAB宿主是所述IAB节点的辅节点SN；
所述IAB节点通过SRB1接收由所述第一IAB宿主发送的所述第一RRC重配置消息。
16.根据附记11所述的方法，其中，所述第一IAB宿主是所述IAB节点的SN，所述第二IAB宿主是所述IAB节点的MN。
17.根据附记16所述的方法，其中，所述第一RRC重配置消息是RRC重配置消息中的辅小区配置域包含的RRC重配置消息，并由所述第二IAB宿主发送的第三RRC重配置消息携带；
所述IAB节点通过SRB1接收由所述第二IAB宿主发送的所述第三RRC重配置消息。
18.根据附记17所述的方法，其中，所述第一RRC重配置消息由所述第二IAB宿主代替所述第一IAB宿主生成。
19.根据附记16所述的方法，其中，所述IAB节点通过SRB3接收由所述第一IAB宿主发送的所述第一RRC重配置消息。
20.根据附记16所述的方法，其中，所述IAB节点通过SRB1接收由所述第二IAB宿主发送的所述第一RRC重配置消息。
21.根据附记14至20中任一项所述的方法，其中，所述IAB节点在所述第一RRC重配置消息或所述第三RRC重配置消息中不包含所述第一指示信息时，确定所述IP地址配置包含F1止点拓扑域的IP地址信息。
22.根据附记13所述的方法，其中，所述第一指示信息包含在所述第一RRC重配置消息或所述第二RRC重配置消息的新增的信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置列表信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址索引信息元中。
23.一种IAB节点(donor)设备，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记1至22任一项所述的传输地址确定方法。
第一donor CU节点侧
1.一种传输地址确定方法，应用于第一IAB宿主，其特征在于，所述方法包括：
所述第一IAB宿主发送第一RRC重配置消息，所述第一RRC重配置消息中包括至少一个针对IAB节点的IP地址配置；或者，发送至少一个所述IAB节点的IP地址配置；
所述至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息；
其中，所述IAB节点的F1连接终止于所述第一IAB宿主，并且IAB节点与第二IAB宿主有RRC连接。
2.根据附记1所述的方法，其中，所述第一IAB宿主通过第一指示信息指示所 述IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
3.根据附记1或2所述的方法，其中，所述IP地址配置包含非F1终止点拓扑域的IP地址信息。
4.根据附记3所述的方法，其中，所述第一IAB宿主是所述IAB节点切换的源宿主，所述第二IAB宿主是所述IAB节点切换的目标宿主，所述第一RRC重配置消息是切换命令RRC消息；
其中，所述第一IAB宿主接收所述第二IAB宿主发送的第一RRC重配置消息，并向所述IAB节点转发由所述第二IAB宿主生成的所述第一RRC重配置消息。
5.根据附记3所述的方法，其中，所述第一IAB宿主是所述IAB节点的主节点MN，所述第二IAB宿主是所述IAB节点的辅节点SN。
6.根据附记5所述的方法，其中，所述第一RRC重配置消息是RRC重配置消息中的辅小区组配置域包含的RRC重配置消息并由所述第一IAB宿主发送的第二RRC重配置消息携带；
所述第一IAB宿主通过SRB1向所述IAB节点发送所述第二RRC重配置消息。
7.根据附记6所述的方法，其中，所述方法还包括：
所述第一IAB宿主接收所述第二IAB宿主发送的所述第一RRC重配置消息。
8.根据附记6所述的方法，其中，所述方法还包括：
所述第一IAB宿主接收所述第二IAB宿主提供的所述IP地址配置，并代替所述第二IAB宿主生成所述第一RRC重配置消息。
9.根据附记5所述的方法，其中，所述方法还包括：
所述第一IAB宿主接收所述第二IAB宿主提供的所述IP地址配置，并通过SRB1发送所述第一RRC重配置消息。
10.根据附记3至9中任一项所述的方法，其中，所述第一IAB宿主通过所述第一RRC重配置消息或所述第二RRC重配置消息包含所述第一指示信息指示所述IP地址配置包含非F1止点拓扑域的IP地址信息。
11.根据附记1或2所述的方法，其中，所述IP地址配置包含F1终止点拓扑域的IP地址信息。
12.根据附记11所述的方法，其中，所述第一IAB宿主是所述IAB节点的SN，所述第二IAB宿主是所述IAB节点的MN。
13.根据附记12所述的方法，其中，
所述第一IAB宿主通过SRB3向所述IAB节点发送所述第一RRC重配置消息。
14.根据附记12所述的方法，其中，所述第一IAB宿主向所述第二IAB宿主发送所述第一RRC重配置消息，其中，所述第一RRC重配置消息为辅小区组配置RRC消息；或者，
所述第一IAB宿主向所述第二IAB宿主发送所述IP地址配置。
15.根据附记11所述的方法，其中，所述第一IAB宿主是所述IAB节点的主节点MN，所述第二IAB宿主是所述IAB节点的辅节点SN；
所述第一IAB宿主通过SRB1向所述IAB节点发送所述第一RRC重配置消息。
17.根据附记11至15任一项所述的方法，其中，所述第一IAB宿主通过所述第一RRC重配置消息不包含所述第一指示信息指示所述IP地址配置包含F1止点拓扑域的IP地址信息。
18.根据附记10所述的方法，其中，所述第一指示信息包含在所述第一RRC重配置消息或所述第二RRC重配置消息的新增的信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置列表信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址索引信息元中。
19.一种IAB宿主(donor)设备，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记1至17任一项所述的传输地址确定方法。
第二donor CU节点侧
1.一种传输地址确定方法，应用于第二IAB宿主，其特征在于，所述方法包括：
所述第二IAB宿主发送第一RRC重配置消息，所述第一RRC重配置消息中包括至少一个针对IAB节点的IP地址配置；或者发送至少一个针对IAB节点的IP地址配置；
所述至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
其中，所述IAB节点的F1连接终止于第一IAB宿主，并且所述IAB节点与所述第二IAB宿主有RRC连接。
2.根据附记1所述的方法，其中，所述第二IAB宿主通过第一指示信息指示所述IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
3.根据附记1或2所述的方法，其中，所述IP地址配置包含非F1终止点拓扑域的IP地址信息。
4.根据附记3所述的方法，其中，所述第一IAB宿主是所述IAB节点切换的源宿主，所述第二IAB宿主是所述IAB节点切换的目标宿主，所述第一RRC重配置消息是切换命令RRC消息，并且，
所述第二IAB宿主向所述第一IAB宿主发送所述第一RRC重配置消息。
5.根据附记3所述的方法，其中，所述第一IAB宿主是所述IAB节点的主节点MN，所述第二IAB宿主是所述IAB节点的辅节点SN。
6.根据附记5所述的方法，其中，所述第二IAB宿主向所述第一IAB宿主发送第一RRC重配置消息；或者，
向所述第一IAB宿主发送所述IP地址配置。
7.根据附记5所述的方法，其中，所述第二IAB宿主通过SRB3向所述IAB节点发送所述第一RRC重配置消息。
8.根据附记3所述的方法，其中，所述第一IAB宿主是所述IAB节点的SN，所述第二IAB宿主是所述IAB节点的MN；
所述第二IAB宿主通过SRB1向所述IAB节点发送所述第一RRC重配置消息。
9.根据附记3至8任一项所述的方法，其中，所述第二IAB宿主通过所述第一RRC重配置消息包含所述第一指示信息指示所述IP地址配置包含非F1止点拓扑域的IP地址信息。
10.根据附记1或2所述的方法，其中，所述IP地址配置包含F1终止点拓扑域的IP地址信息。
11.根据附记10所述的方法，其中，所述第一IAB宿主是所述IAB节点的SN，所述第二IAB宿主是所述IAB节点的MN。
12.根据附记11所述的方法，其中，所述第一RRC重配置消息是RRC重配置消息中的辅小区组配置域包含的RRC重配置消息，并由所述第二IAB宿主发送的第三RRC重配置消息携带；
所述第二IAB宿主通过SRB1向所述IAB节点发送所述第三RRC重配置消息。
13.根据附记12所述的方法，其中，所述方法还包括：
所述第二IAB宿主接收所述第一IAB宿主发送第一RRC重配置消息。
14.根据附记12所述的方法，其中，所述第二IAB宿主接收所述第一IAB宿主提供的所述IP地址配置，并代替所述第一IAB宿主生成所述第一RRC重配置消息。
15.根据附记11所述的方法，其中，所述方法还包括：
所述第二IAB宿主接收所述第一IAB宿主发送的所述IP地址配置，并通过SRB1向所述IAB节点发送所述第一RRC重配置消息。
16.根据附记11至15中任一项所述的方法，其中，所述第二IAB宿主通过所述第一RRC重配置消息或所述第三RRC重配置消息不包含所述第一指示信息指示所述IP地址配置包含F1终止点拓扑域的IP地址信息。
17.根据附记9所述的方法，其中，所述第一指示信息包含在所述第一RRC重配置消息或所述第二RRC重配置消息的新增的信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置列表信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址索引信息元中。
18.一种IAB宿主(donor)设备，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记1至17任一项所述的传输地址确定方法。
边界节点
1.一种IAB节点设备，其特征在于，所述设备包括：
第一接收部，其接收第一RRC重配置消息，所述第一RRC重配置消息中包括针对所述IAB节点的至少一个IP地址配置；
所述至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
2.根据附记1所述的设备，其中，所述IAB节点的F1连接终止于第一IAB宿主，并且所述IAB节点与第二IAB宿主有RRC连接。
3.根据附记2所述的设备，其中，所述设备还包括：
第一处理部，其确定所述IP地址配置包含F1终止点拓扑域的IP地址信息或非 F1终止点拓扑域的IP地址信息。
4.根据附记3所述的设备，其中，所述第一处理部根据第一指示信息确定所述IP地址配置包含F1终止点拓扑域的IP地址信息或非F1终止点拓扑域的IP地址信息。
5.根据附记3或4所述的设备，其中，所述第一处理部确定所述IP地址配置包含非F1终止点(non-F1-terminating)拓扑域的IP地址信息。
6.根据附记5所述的设备，其中，所述第一IAB宿主是所述IAB节点切换的源宿主，所述第二IAB宿主是所述IAB节点切换的目标宿主；
所述第一RRC重配置消息是第一IAB宿主转发的由第二IAB宿主生成的切换命令RRC消息。
7.根据附记5所述的设备，其中，所述第一IAB宿主是所述IAB节点的主节点MN，所述第二IAB宿主是所述IAB节点的辅节点SN。
8.根据附记7所述的设备，其中，所述第一RRC重配置消息是RRC重配置消息中的辅小区组配置域包含的RRC重配置消息，并由所述第一IAB宿主发送的第二RRC重配置消息携带；
所述第一接收部通过SRB1接收由所述第一IAB宿主发送的所述第二RRC重配置消息。
9.根据附记8所述的设备，其中，所述第一RRC重配置消息由所述第一IAB宿主代替所述第二IAB宿主生成。
10.根据附记7所述的设备，其中，所述第一接收部通过SRB3接收由所述第二IAB宿主发送的所述第一RRC重配置消息。
11.根据附记7所述的设备，其中，所述第一接收部通过SRB1接收由所述第一IAB宿主发送的所述第一RRC重配置消息。
12.根据附记5所述的设备，其中，所述第一IAB宿主是所述IAB节点的SN，所述第二IAB宿主是所述IAB节点的MN；
所述第一接收部通过SRB1接收由所述第二IAB宿主发送的所述第一RRC重配置消息。
13.根据附记5至12任一项所述的设备，其中，所述第一处理部在所述第一RRC重配置消息或所述第二RRC重配置消息中包含所述第一指示信息时，确定所述IP地址配置包含非F1止点拓扑域的IP地址信息。
14.根据附记3或4所述的设备，其中，所述第一处理部确定所述IP地址配置 包含F1终止点(F1-terminating)拓扑域的IP地址信息。
15.根据附记14所述的设备，其中，所述第一IAB宿主是所述IAB节点的主节点MN，所述第二IAB宿主是所述IAB节点的辅节点SN；
所述第一接收部通过SRB1接收由所述第一IAB宿主发送的所述第一RRC重配置消息。
16.根据附记11所述的设备，其中，所述第一IAB宿主是所述IAB节点的SN，所述第二IAB宿主是所述IAB节点的MN。
17.根据附记16所述的设备，其中，所述第一RRC重配置消息是RRC重配置消息中的辅小区配置域包含的RRC重配置消息，并由所述第二IAB宿主发送的第三RRC重配置消息携带；
所述第一接收部通过SRB1接收由所述第二IAB宿主发送的所述第三RRC重配置消息。
18.根据附记17所述的设备，其中，所述第一RRC重配置消息由所述第二IAB宿主代替所述第一IAB宿主生成。
19.根据附记16所述的设备，其中，所述第一接收部通过SRB3接收由所述第一IAB宿主发送的所述第一RRC重配置消息。
20.根据附记16所述的设备，其中，所述第一接收部通过SRB1接收由所述第二IAB宿主发送的所述第一RRC重配置消息。
21.根据附记14至20中任一项所述的设备，其中，所述第一处理部在所述第一RRC重配置消息或所述第三RRC重配置消息中不包含所述第一指示信息时，确定所述IP地址配置包含F1止点拓扑域的IP地址信息。
22.根据附记13所述的设备，其中，所述第一指示信息包含在所述第一RRC重配置消息或所述第二RRC重配置消息的新增的信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置列表信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址索引信息元中。
第一donor CU节点侧
1.一种IAB宿主设备，应用于第一IAB宿主，其特征在于，所述设备包括：
第一发送部，其发送第一RRC重配置消息，所述第一RRC重配置消息中包括至 少一个针对IAB节点的IP地址配置；或者，发送至少一个所述IAB节点的IP地址配置；
所述至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息；
其中，所述IAB节点的F1连接终止于所述第一IAB宿主，并且IAB节点与第二IAB宿主有RRC连接。
2.根据附记1所述的设备，其中，所述IAB宿主设备通过第一指示信息指示所述IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
3.根据附记1或2所述的设备，其中，所述IP地址配置包含非F1终止点拓扑域的IP地址信息。
4.根据附记3所述的设备，其中，所述第一IAB宿主是所述IAB节点切换的源宿主，所述第二IAB宿主是所述IAB节点切换的目标宿主，所述第一RRC重配置消息是切换命令RRC消息；
其中，所述设备还包括：第二接收部，其接收所述第二IAB宿主发送的第一RRC重配置消息，并且所述第一发送部向所述IAB节点转发由所述第二IAB宿主生成的所述第一RRC重配置消息。
5.根据附记3所述的设备，其中，所述第一IAB宿主是所述IAB节点的主节点MN，所述第二IAB宿主是所述IAB节点的辅节点SN。
6.根据附记5所述的设备，其中，所述第一RRC重配置消息是RRC重配置消息中的辅小区配置域包含的RRC重配置消息，并由所述第一IAB宿主发送的第二RRC重配置消息携带；
所述第一发送部通过SRB1向所述IAB节点发送所述第二RRC重配置消息。
7.根据附记6所述的设备，其中，所述设备还包括：
第三接收部，其接收所述第二IAB宿主发送的所述第一RRC重配置消息。
8.根据附记6所述的设备，其中，所述设备还包括：
第四接收部，其接收所述第二IAB宿主提供的所述IP地址配置；
第二处理部，其代替所述第二IAB宿主生成所述第一RRC重配置消息。
9.根据附记5所述的设备，其中，所述设备还包括：
第五接收部，其接收所述第二IAB宿主提供的所述IP地址配置，并且所述第一 发送部通过SRB1发送所述第一RRC重配置消息。
10.根据附记3至9中任一项所述的设备，其中，所述IAB宿主设备通过所述第一RRC重配置消息或所述第二RRC重配置消息包含所述第一指示信息指示所述IP地址配置包含非F1止点拓扑域的IP地址信息。
11.根据附记1或2所述的设备，其中，所述IP地址配置包含F1终止点拓扑域的IP地址信息。
12.根据附记11所述的设备，其中，所述第一IAB宿主是所述IAB节点的SN，所述第二IAB宿主是所述IAB节点的MN。
13.根据附记12所述的设备，其中，
所述第一发送部通过SRB3向所述IAB节点发送所述第一RRC重配置消息。
14.根据附记12所述的设备，其中，所述第一发送部向所述第二IAB宿主发送所述第一RRC重配置消息，其中，所述第一RRC重配置消息是辅小区配置RRC消息；或者，
所述第一发送部向所述第二IAB宿主发送所述IP地址配置。
15.根据附记11所述的设备，其中，所述第一IAB宿主是所述IAB节点的主节点MN，所述第二IAB宿主是所述IAB节点的辅节点SN；
所述第一发送部通过SRB1向所述IAB节点发送所述第一RRC重配置消息。
17.根据附记11至15任一项所述的设备，其中，所述IAB宿主设备通过所述第一RRC重配置消息不包含所述第一指示信息指示所述IP地址配置包含F1止点拓扑域的IP地址信息。
18.根据附记10所述的设备，其中，所述第一指示信息包含在所述第一RRC重配置消息或所述第二RRC重配置消息的新增的信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置列表信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址索引信息元中。
第二donor CU节点侧
1.一种IAB宿主设备，应用于第二IAB宿主，其特征在于，所述设备包括：
第二发送部，其发送第一RRC重配置消息，所述第一RRC重配置消息中包括至少一个针对IAB节点的IP地址配置；或者发送至少一个针对IAB节点的IP地址配 置；
所述至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
其中，所述IAB节点的F1连接终止于第一IAB宿主，并且所述IAB节点与所述第二IAB宿主有RRC连接。
2.根据附记1所述的设备，其中，所述IAB宿主设备通过第一指示信息指示所述IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
3.根据附记1或2所述的设备，其中，所述IP地址配置包含非F1终止点拓扑域的IP地址信息。
4.根据附记3所述的设备，其中，所述第一IAB宿主是所述IAB节点切换的源宿主，所述第二IAB宿主是所述IAB节点切换的目标宿主，所述第一RRC重配置消息是切换命令RRC消息，并且，
所述第二发送部向所述第一IAB宿主发送所述第一RRC重配置消息。
5.根据附记3所述的设备，其中，所述第一IAB宿主是所述IAB节点的主节点MN，所述第二IAB宿主是所述IAB节点的辅节点SN。
6.根据附记5所述的设备，其中，所述第二发送部向所述第一IAB宿主发送第一RRC重配置消息；或者，
向所述第一IAB宿主发送所述IP地址配置。
7.根据附记5所述的设备，其中，所述第二发送部通过SRB3向所述IAB节点发送所述第一RRC重配置消息。
8.根据附记3所述的设备，其中，所述第一IAB宿主是所述IAB节点的SN，所述第二IAB宿主是所述IAB节点的MN；
所述第二发送部通过SRB1向所述IAB节点发送所述第一RRC重配置消息。
9.根据附记3至8任一项所述的设备，其中，所述IAB宿主设备通过所述第一RRC重配置消息包含所述第一指示信息指示所述IP地址配置包含非F1止点拓扑域的IP地址信息。
10.根据附记1或2所述的设备，其中，所述IP地址配置包含F1终止点拓扑域的IP地址信息。
11.根据附记10所述的设备，其中，所述第一IAB宿主是所述IAB节点的SN， 所述第二IAB宿主是所述IAB节点的MN。
12.根据附记11所述的设备，其中，所述第一RRC重配置消息是RRC重配置消息中的辅小区配置域包含的RRC重配置消息，并由所述第二IAB宿主发送的第三RRC重配置消息携带；
所述第二发送部通过SRB1向所述IAB节点发送所述第三RRC重配置消息。
13.根据附记12所述的设备，其中，所述设备还包括：
第六接收部，其接收所述第一IAB宿主发送第一RRC重配置消息。
14.根据附记12所述的设备，其中，所述设备还包括：
第七接收部，其接收所述第一IAB宿主提供的所述IP地址配置；
第三处理部，其代替所述第一IAB宿主生成所述第一RRC重配置消息。
15.根据附记11所述的设备，其中，所述设备还包括：
第八接收部，其接收所述第一IAB宿主发送的所述IP地址配置，并且，所述第二发送部通过SRB1向所述IAB节点发送所述第一RRC重配置消息。
16.根据附记11至15中任一项所述的设备，其中，所述IAB宿主设备通过所述第一RRC重配置消息或所述第三RRC重配置消息不包含所述第一指示信息指示所述IP地址配置包含F1终止点拓扑域的IP地址信息。
17.根据附记9所述的设备，其中，所述第一指示信息包含在所述第一RRC重配置消息或所述第二RRC重配置消息的新增的信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置列表信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址索引信息元中。

Claims (20)

  1. 一种集成的接入和回传IAB节点设备，其特征在于，所述设备包括：
    第一接收部，其接收第一RRC重配置消息，所述第一RRC重配置消息中包括针对所述IAB节点的至少一个IP地址配置；
    所述至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
  2. 根据权利要求1所述的设备，其中，所述IAB节点的F1连接终止于第一IAB宿主，并且所述IAB节点与第二IAB宿主有RRC连接。
  3. 根据权利要求2所述的设备，其中，所述设备还包括：
    第一处理部，其确定所述IP地址配置包含F1终止点拓扑域的IP地址信息或非F1终止点拓扑域的IP地址信息。
  4. 根据权利要求3所述的设备，其中，所述第一处理部根据第一指示信息确定所述IP地址配置包含F1终止点拓扑域的IP地址信息或非F1终止点拓扑域的IP地址信息。
  5. 根据权利要求3或4所述的设备，其中，所述第一处理部确定所述IP地址配置包含非F1终止点(non-F1-terminating)拓扑域的IP地址信息。
  6. 根据权利要求5所述的设备，其中，所述第一IAB宿主是所述IAB节点的主节点MN，所述第二IAB宿主是所述IAB节点的辅节点SN。
  7. 根据权利要求6所述的设备，其中，所述第一RRC重配置消息是RRC重配置消息中的辅小区组配置域包含的RRC重配置消息，并由所述第一IAB宿主发送的第二RRC重配置消息携带；
    所述第一接收部通过SRB1接收由所述第一IAB宿主发送的所述第二RRC重配置消息。
  8. 根据权利要求5所述的设备，其中，所述第一IAB宿主是所述IAB节点的SN，所述第二IAB宿主是所述IAB节点的MN；
    所述第一接收部通过SRB1接收由所述第二IAB宿主发送的所述第一RRC重配置消息。
  9. 根据权利要求5所述的设备，其中，所述第一处理部在所述第一RRC重配置 消息或所述第二RRC重配置消息中包含所述第一指示信息时，确定所述IP地址配置包含非F1止点拓扑域的IP地址信息。
  10. 根据权利要求3或4所述的设备，其中，所述第一处理部确定所述IP地址配置包含F1终止点(F1-terminating)拓扑域的IP地址信息。
  11. 根据权利要求10所述的设备，其中，所述第一IAB宿主是所述IAB节点的SN，所述第二IAB宿主是所述IAB节点的MN。
  12. 根据权利要求11所述的设备，其中，所述第一RRC重配置消息是RRC重配置消息中的辅小区配置域包含的RRC重配置消息，并由所述第二IAB宿主发送的第三RRC重配置消息携带；
    所述第一接收部通过SRB1接收由所述第二IAB宿主发送的所述第三RRC重配置消息。
  13. 根据权利要求12所述的设备，其中，所述第一处理部在所述第一RRC重配置消息或所述第三RRC重配置消息中不包含所述第一指示信息时，确定所述IP地址配置包含F1止点拓扑域的IP地址信息。
  14. 根据权利要求5所述的设备，其中，所述第一IAB宿主是所述IAB节点切换的源宿主，所述第二IAB宿主是所述IAB节点切换的目标宿主；
    所述第一RRC重配置消息是第一IAB宿主转发的由第二IAB宿主生成的切换命令RRC消息。
  15. 根据权利要求7所述的设备，其中，所述第一RRC重配置消息由所述第一IAB宿主代替所述第二IAB宿主生成。
  16. 根据权利要求12所述的设备，其中，所述第一RRC重配置消息由所述第二IAB宿主代替所述第一IAB宿主生成。
  17. 根据权利要求9所述的设备，其中，所述第一指示信息包含在所述第一RRC重配置消息或所述第二RRC重配置消息的新增的信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置列表信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址配置信息元中，或者包含在所述第一RRC重配置消息或所述第二RRC重配置消息的IP地址索引信息元中。
  18. 根据权利要求10所述的设备，其中，所述第一IAB宿主是所述IAB节点的 主节点MN，所述第二IAB宿主是所述IAB节点的辅节点SN；
    所述第一接收部通过SRB1接收由所述第一IAB宿主发送的所述第一RRC重配置消息。
  19. 一种集成的接入和回传IAB宿主设备，应用于第一IAB宿主，其特征在于，所述设备包括：
    第一发送部，其发送第一RRC重配置消息，所述第一RRC重配置消息中包括至少一个针对IAB节点的IP地址配置；或者，发送至少一个所述IAB节点的IP地址配置；
    所述至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息；
    其中，所述IAB节点的F1连接终止于所述第一IAB宿主。
  20. 一种集成的接入和回传IAB宿主设备，应用于第二IAB宿主，其特征在于，所述设备包括：
    第二发送部，其发送第一RRC重配置消息，所述第一RRC重配置消息中包括至少一个针对IAB节点的IP地址配置；或者发送至少一个针对IAB节点的IP地址配置；
    所述至少一个IP地址配置包含F1终止点拓扑域的IP地址信息，或者包含非F1终止点拓扑域的IP地址信息。
    其中，所述IAB节点的F1连接终止于第一IAB宿主。
PCT/CN2022/086455 2022-04-12 2022-04-12 Iab节点设备、iab宿主设备以及传输地址确定方法 WO2023197185A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/086455 WO2023197185A1 (zh) 2022-04-12 2022-04-12 Iab节点设备、iab宿主设备以及传输地址确定方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/086455 WO2023197185A1 (zh) 2022-04-12 2022-04-12 Iab节点设备、iab宿主设备以及传输地址确定方法

Publications (1)

Publication Number Publication Date
WO2023197185A1 true WO2023197185A1 (zh) 2023-10-19

Family

ID=88328695

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/086455 WO2023197185A1 (zh) 2022-04-12 2022-04-12 Iab节点设备、iab宿主设备以及传输地址确定方法

Country Status (1)

Country Link
WO (1) WO2023197185A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021031000A1 (en) * 2019-08-16 2021-02-25 Nokia Shanghai Bell Co., Ltd. Apparatus, method, and computer program
US20210360439A1 (en) * 2020-05-12 2021-11-18 Qualcomm Incorporated Delayed delivery of reconfiguration message in integrated access and backhaul (iab) network
WO2022015230A1 (en) * 2020-07-17 2022-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Inter-cu migration in iab networkinter-cu migration in iab network
WO2022028593A1 (zh) * 2020-08-07 2022-02-10 大唐移动通信设备有限公司 Iab节点组切换中的信息传输方法、装置及网络设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021031000A1 (en) * 2019-08-16 2021-02-25 Nokia Shanghai Bell Co., Ltd. Apparatus, method, and computer program
US20210360439A1 (en) * 2020-05-12 2021-11-18 Qualcomm Incorporated Delayed delivery of reconfiguration message in integrated access and backhaul (iab) network
WO2022015230A1 (en) * 2020-07-17 2022-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Inter-cu migration in iab networkinter-cu migration in iab network
WO2022028593A1 (zh) * 2020-08-07 2022-02-10 大唐移动通信设备有限公司 Iab节点组切换中的信息传输方法、装置及网络设备

Similar Documents

Publication Publication Date Title
US20210112471A1 (en) Method for establishing a fronthaul interface, method for performing access for a ue, method and apparatus for performing a handover for a ue, data forwarding method, user equipment and base station
WO2018127018A1 (zh) 多链接通信方法、设备和终端
WO2022082518A1 (zh) 信号的接收和发送方法、装置和通信系统
US20230254729A1 (en) Migration method and apparatus for iab-node
US20230308975A1 (en) Group migration method and apparatus and system
WO2024031289A1 (zh) 网络节点的通信方法、移动节点的通信方法、移动节点和宿主设备
CN115136651A (zh) 切换方法和通信装置
WO2023197185A1 (zh) Iab节点设备、iab宿主设备以及传输地址确定方法
WO2023197184A1 (zh) Iab宿主设备以及传输地址配置方法
WO2016119249A1 (zh) 多流聚合方法、装置及系统
WO2024026803A1 (zh) 移动节点的配置方法和宿主设备
WO2023184542A1 (zh) 配置信息的方法、装置和通信系统
WO2024026804A1 (zh) 移动节点的配置方法、移动节点和宿主设备
WO2023197105A1 (zh) 配置信息的方法、装置和通信系统
WO2022205485A1 (zh) 信息收发方法以及装置
WO2023150975A1 (zh) Iab宿主设备以及传输迁移回退方法
WO2023130231A1 (zh) Iab节点设备、iab宿主设备以及拓扑退行方法
WO2023150974A1 (zh) Iab宿主设备以及传输迁移管理方法
WO2022205251A1 (zh) 信息收发方法，数据发送方法以及装置
WO2023130232A1 (zh) Iab节点设备、iab宿主设备以及路径迁移方法
WO2023150976A1 (zh) Iab宿主设备以及传输迁移管理方法
WO2022233008A1 (zh) 消息发送方法、装置和系统
WO2023205941A1 (zh) 信息的发送、接收、配置方法以及装置和通信系统
WO2022236644A1 (zh) 发送和接收信号的方法、装置和通信系统
WO2023130260A1 (zh) Rrc消息的配置方法、装置和系统

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

Country of ref document: EP

Kind code of ref document: A1