[go: up one dir, main page]

WO2023197184A1 - Iab宿主设备以及传输地址配置方法 - Google Patents

Iab宿主设备以及传输地址配置方法 Download PDF

Info

Publication number
WO2023197184A1
WO2023197184A1 PCT/CN2022/086454 CN2022086454W WO2023197184A1 WO 2023197184 A1 WO2023197184 A1 WO 2023197184A1 CN 2022086454 W CN2022086454 W CN 2022086454W WO 2023197184 A1 WO2023197184 A1 WO 2023197184A1
Authority
WO
WIPO (PCT)
Prior art keywords
termination point
node
host
iab
address
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/086454
Other languages
English (en)
French (fr)
Inventor
路杨
易粟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to EP22936838.6A priority Critical patent/EP4510703A4/en
Priority to PCT/CN2022/086454 priority patent/WO2023197184A1/zh
Priority to CN202280094508.5A priority patent/CN118975317A/zh
Priority to JP2024557897A priority patent/JP2025511113A/ja
Publication of WO2023197184A1 publication Critical patent/WO2023197184A1/zh
Priority to US18/903,595 priority patent/US20250081274A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/06—Reselecting a communication resource in the serving access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices

Definitions

  • the 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.
  • the IAB node For the routing ID of the F1-terminating topology domain, the IAB node needs to use the IP address of the F1-terminating topology domain.
  • the network needs to configure the IAB node with an IP address anchored to the donor-DU in the non-F1-terminating topology domain, or an IP address anchored to the donor-DU in the F1-terminating topology domain.
  • embodiments of the present application provide an IAB host device and a transport address configuration method.
  • a transport address configuration method is provided, which is applied to the F1 termination point host device of the IAB node.
  • the method includes:
  • the F1 termination point host sends IP address request information for the non-F1 termination point topological domain of the IAB node to the non-F1 termination point host; and/or,
  • the F1 termination point host receives the IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node sent by the non-F1 termination point host; and/or,
  • the F1 termination point host sends the IP address configuration information for the F1 termination point topology domain allocated by the IAB node to the non-F1 termination point host.
  • a transport address configuration method is provided, which is applied to the non-F1 termination point host device of the IAB node.
  • the method includes:
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; and/or,
  • the non-F1 termination point host sends the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node to the F1 termination point host; and/or,
  • the non-F1 termination point host receives the IP address configuration information for the F1 termination point topology domain allocated by the IAB node sent by the F1 termination point host.
  • an IAB host device is provided.
  • the IAB host device is the F1 termination point host device of the IAB node.
  • the device includes:
  • the first receiving unit receives the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node sent by the non-F1 termination point host.
  • an IAB host device is provided.
  • the IAB host device is a non-F1 termination point host device of an IAB node.
  • the device includes:
  • the second receiving unit receives the IP address request information for the non-F1 termination point topological domain of the IAB node sent by the F1 termination point host; and/or,
  • the second sending unit is configured to send IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node to the F1 termination point host.
  • a communication system includes: the IAB host device described in the foregoing aspect.
  • the F1 termination point host can request the non-F1 termination point host to allocate the IP address of the non-F1 termination point topological domain, or further receive the non-F1 IP address allocated by the non-F1 termination point host for the IAB node. IP address configuration information of the termination point topology domain, so that the F1 termination point host can request the IP address of the non-F1 termination point topology domain, or further send the IP address of the non-F1 termination point topology domain to the IAB node, for example, when it is not F1 When the termination point host cannot send messages to the IAB node.
  • the F1 termination point host can receive the IP address configuration information of the non-F1 termination point topology domain actively sent by the non-F1 termination point host, so as to send the IP address of the non-F1 termination point topology domain to the IAB node. For example, when the non-F1 termination point host cannot When sending a message to the IAB node.
  • the F1 termination point host can send the IP address configuration information of the F1 termination point topology domain to the non-F1 termination point host, so that the non-F1 termination point host can send the IP address of the F1 termination point topology domain to the IAB node. For example, when F1 When the termination point host cannot send messages to the IAB node.
  • the IAB node can use the IP address of the non-F1 termination point topology domain, and for the routing ID of the 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 host device according to an embodiment of the present application.
  • Figure 10 is a schematic diagram of a transmission address configuration 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 a transmission address configuration method according to an embodiment of the present application.
  • Figure 13 is a schematic diagram of dual connection scenario one
  • Figure 14 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application.
  • Figure 15 is a schematic diagram of the transmission address configuration method according to the embodiment of the present application.
  • Figure 16 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application.
  • Figure 17 is a schematic diagram of dual connection scenario 2;
  • Figure 18 is a schematic diagram of the transmission address configuration method according to the embodiment of the present application.
  • Figure 19 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application.
  • Figure 20 is a schematic diagram of RLF recovery scenario
  • Figure 21 is a schematic diagram of the transmission address configuration method according to the embodiment of the present application.
  • Figure 22 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application.
  • Figure 23 is a schematic diagram of the transmission address configuration method according to the embodiment of the present application.
  • Figure 24 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application.
  • Figure 25 is a schematic diagram of the transmission address configuration method according to the embodiment of the present application.
  • Figure 26 is a schematic diagram of the transmission address configuration method according to the embodiment of the present application.
  • Figure 27 is a schematic diagram of the transmission address configuration method according to the embodiment of the present application.
  • Figure 28 is a schematic diagram of the transmission address configuration method according to the embodiment of the present application.
  • Figure 29 is a schematic diagram of an IAB host device according to an embodiment of the present application.
  • Figure 30 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 network topology update and backhaul (BH) wireless link failure (RLF, Radio Link Failure) recovery process when IAB-node moves under different donor-CU.
  • IAB-node can be downloaded from the source host (also The parent node of the service, which can be called F1-terminating CU or first donor-CU) is switched or reestablished to the parent node of the target host (also called non-F1-terminating CU or second donor-CU) service.
  • You need to All services of IAB-node (and the services of its sub-nodes) are 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 donor-CU1 topology domain.
  • All routing IDs of the boundary node will belong to the non-F1-terminating topology domain, or the boundary node will simultaneously transmit services whose routing IDs belong to the F1-terminating topology domain and routing IDs which belong to the non-F1-terminating topology domain.
  • the boundary node For the routing ID of the non-F1-terminating topology domain, the boundary node needs to use the IP address of the non-F1-terminating topology domain.
  • the boundary node needs to use the IP address of the F1-terminating topology domain.
  • the network needs to configure the boundary node with an IP address anchored to the donor-DU in the non-F1-terminating topology domain, or an IP address anchored to the donor-DU in the F1-terminating topology domain.
  • IP address anchored to the donor-DU in the non-F1-terminating topology domain or an IP address anchored to the donor-DU in the F1-terminating topology domain.
  • the IAB node device includes a migration 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 transport address configuration method, which is explained from the host device side of the F1 termination point of the IAB node.
  • Figure 10 is a schematic diagram of a transmission address configuration method according to an embodiment of the present application. As shown in Figure 10, the method includes:
  • the F1 termination point host sends the IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; and/or,
  • the F1 termination point host receives the IP address configuration information for the non-F1 termination point topology domain assigned by the IAB node sent by the non-F1 termination point host; and/or,
  • the F1 termination point host sends the IP address configuration information for the F1 termination point topology domain allocated by the IAB node to the non-F1 termination point host.
  • the F1 termination point host can request the non-F1 termination point host to allocate the IP address of the non-F1 termination point topology domain, or further receive the IP address of the non-F1 termination point topology domain allocated by the non-F1 termination point host for the IAB node. IP address configuration information, so that the F1 termination point host can request the IP address of the non-F1 termination point topology domain, or further send the IP address of the non-F1 termination point topology domain for the IAB node, for example, when the non-F1 termination point host cannot provide When the IAB node sends a message.
  • the F1 termination point host can receive the IP address configuration information of the non-F1 termination point topology domain actively sent by the non-F1 termination point host, so as to send the IP address of the non-F1 termination point topology domain to the IAB node. For example, when the non-F1 termination point host cannot When sending a message to the IAB node.
  • the F1 termination point host can send the IP address configuration information of the F1 termination point topology domain to the non-F1 termination point host, so that the non-F1 termination point host can send the IP address of the F1 termination point topology domain to the IAB node. For example, when F1 When the termination point host cannot send messages to the IAB node.
  • the IAB node can use the IP address of the non-F1 termination point topology domain, and for the routing ID of the F1 termination point topology domain, the IP address of the F1 termination point topology domain can be used.
  • the IAB node includes a migration node (also called a border node) whose F1 connection terminates at the F1 termination point host and which has an RRC connection with the non-F1 termination point host.
  • the F1 termination point host device can be the first IAB donor-CU (host centralized unit), and the non-F1 termination point host device can be the second IAB donor.
  • -CU host centralized unit
  • the F1 termination point host device refers to the donor-CU that terminates the F1 interface of the border IAB node and its child IAB node, such as the first IAB donor-CU.
  • Non-F1 termination point host device refers to a CU with host function that does not terminate the F1 interface of the border IAB node and its child IAB node, such as the second IAB donor-CU.
  • the requested and/or configured IP address refers to the IP address configured for the IAB node (or for the IAB node) anchored to the donor-DU.
  • the IP address configuration information may include anchor IP address configurations anchored to at least two donor-DUs may also include at least one IP address configuration anchored to one donor-DU.
  • Each IP address configuration may include an IP address index and a corresponding IP address.
  • 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 above-mentioned IP address request information and/or IP address configuration information can be carried by the RRC container, or can also be carried by the IAB transmission migration management request/response or by the IAB transmission migration modification request, which will be described separately below.
  • IP address request information and/or IP address configuration information are carried by the RRC container
  • the IP address request information is carried by the first RRC container.
  • the IP address request information is carried by other IAB information messages (cell structure IABOtherInformation) or RRC reconfiguration messages contained in the first RRC container.
  • the first RRC container includes the IP address configuration information of the IAB node in the F1 termination point topology domain.
  • the IABOtherInformation message is an RRC message used by the IAB node to request an IP address from the network and report the IP address actually used or allocated by the network to the IAB node.
  • the F1 termination point host simulates the IAB node to generate an IABOtherInformation message, and includes it in the first RRC container and sends it to the non-F1 termination point host to replace the IAB node in requesting the IP address of the non-F1 topology domain.
  • the RRC reconfiguration message is an RRC message in which the network configures an IP address to the IAB node.
  • the RRC reconfiguration message is generated by the F1 termination point host, and is included in the first RRC container and sent to the non-F1 termination point host to request the IP address of the non-F1 topology domain.
  • the IP address configuration information is carried by the second RRC container.
  • the IP address configuration information is carried by the RRC reconfiguration message (RRCReconfiguration) contained in the second RRC container.
  • the existing RRC message (such as IABOtherInformation) is an RRC message used by the IAB node to request an IP address from the host
  • the RRC reconfiguration message (RRCReconfiguration) message is an RRC message used to configure an IP address for the IAB node
  • RRC can be reused.
  • Messages (such as IABOtherInformation) carry IP address request information for border nodes
  • reused RRC reconfiguration messages (RRCReconfiguration) carry IP address configuration information for border nodes, making IP address request and configuration simpler and more flexible.
  • existing Xn procedures (which may be carried by Xn Interface Application Protocol (XnAP) signaling), such as handover preparation, dual connection establishment or modification procedures, UE context acquisition procedures, etc., may be used to request and/or configure the above IP address.
  • the first RRC container is carried by at least one of the following messages: a handover request message; a secondary node addition request message; a secondary node modification request message; a secondary node modification requirement message; and a UE context acquisition response message.
  • the second RRC container is carried by at least one of the following messages: a handover request response message; a secondary node addition response message; a secondary node modification response message; a secondary node modification requirement message.
  • these Xn processes are processes for border nodes, they can be naturally distinguished from IP address requests and configuration information for child nodes, so that the host can use the RRC connection with the border node to send IP address configuration to the border node.
  • Figure 11 is a schematic diagram of a switching scenario. As shown in Figure 11, in the switching scenario, all services of the border node are migrated to the non-F1 termination point topology domain, and the F1 termination point host is the source host of the IAB node switching. , the non-F1 termination point host is the target host of the IAB node switching, and the IP address of the non-F1 termination point topological domain refers to the IP address anchored to donor-DU2.
  • Figure 12 is a schematic diagram of the transmission address configuration method in this switching scenario. As shown in Figure 12, the method includes:
  • the F1 termination point host sends the IP address request information for the non-F1 termination point topological domain of the IAB node to the non-F1 termination point host;
  • the F1 termination point host receives the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node sent by the non-F1 termination point host;
  • the IP address request information is carried by a first RRC container
  • the IP address configuration information is carried by a second RRC container
  • the first RRC container is carried by a handover request message
  • the second RRC container responds by a handover request Message bearer. Therefore, the F1 termination point host sends a handover request message (HANDOVER REQUEST) to the non-F1 termination point host.
  • the handover request message contains the RRC message HandoverPreparationInformation.
  • the entire RRC message IABOtherInformation generated by the F1 termination point host can be introduced in HandoverPreparationInformation.
  • IABOtherInformation carries the IP address request information (IAB-TNLAddressInfo domain) of the non-F1 termination point topology domain.
  • the IABOtherInformation can also include the IP address configuration information of the border node in the F1 termination point topology domain.
  • the non-F1 termination point host replies to the F1 termination point host with a handover request response (HANDOVER REQUEST ACKNOWLEDGE).
  • the handover request response contains the RRC message HandoverCommand.
  • the HandoverCommand carries the entire RRC message RRCReconfiguration generated by the non-F1 termination point host. RRCReconfiguration is used as
  • the second RRC container carries the IP address configuration information of the non-F1 termination point topology domain (iab-IP-AddressConfigurationList-r16 domain).
  • the HandoverPreparationInformation uses abstract syntax notation ASN.1 data format can be expressed as:
  • the IABOtherInformation uses abstract syntax notation ASN.1 data format can be expressed as:
  • IABOtherInformation can also carry the number of IP addresses requested for various services or the IP addresses actually used by various services.
  • the HandoverCommand uses abstract syntax to markup the ASN.1 data format and can be expressed as:
  • the RRCReconfiguration uses abstract syntax notation ASN.1 data format can be expressed as:
  • the RRCReconfiguration carries the IP address configuration information IAB-IP-AddressConfigurationList-r16 of the non-F1 termination point topology domain, including an IP address addition and modification list and an IP address release list, each list including at least one IP address configuration IAB-IP-AddressConfiguration-r16, each IP address configuration can include the IP address index and the corresponding IP address.
  • IP address request information is carried by the IABOtherInformatio contained in the first RRC container.
  • IP address request information can also be carried by the RRC reconfiguration message contained in the first RRC container. This embodiment of the present invention is not limited. .
  • the method may further include:
  • the F1 termination point host sends the received IP address configuration information to the IAB node; for example, the F1 termination point host forwards the HandoverCommand generated by the non-F1 termination point host, and the HandoverCommand carries the entire command generated by the non-F1 termination point host.
  • RRC message RRCReconfiguration, RRCReconfiguration carries the IP address configuration information of the non-F1 termination point topology domain.
  • the F1 termination point host can request the non-F1 termination point host to allocate the IP address of the non-F1 termination point topology domain, or further receive the IP address of the non-F1 termination point topology domain allocated by the non-F1 termination point host for the IAB node. IP address configuration information, so that the F1 termination point host can request the IP address of the non-F1 termination point topology domain, or further send the non-F1 termination point topology to the IAB node when the non-F1 termination point host cannot send a message to the IAB node.
  • the IP address of the domain In this way, for the routing ID of the non-F1 termination point topology domain, the IAB node can use the IP address of the non-F1 termination point topology domain.
  • Figure 13 is a schematic diagram of dual connection scenario one.
  • the F1 termination point host is the primary node MN of the IAB node
  • the non-F1 termination point host is the IAB
  • 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 refers to the anchor Set to the IP address of donor-DU2.
  • Figure 14 is a schematic diagram of a method for configuring a transmission address in the dual connection scenario. As shown in Figure 14, the method includes:
  • the F1 termination point host sends the IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;
  • the F1 termination point host receives the IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node sent by the non-F1 termination point host.
  • the IP address of the non-F1 termination point topology domain is requested, the IP address request information is carried by the first RRC container, and the IP address configuration information is carried by the second RRC container.
  • the first RRC container is carried by a secondary node add request message, and the second RRC container is carried by a secondary node add response message.
  • the F1 termination point host sends a secondary node add request message (S-node AdditionRequest) to the non-F1 termination point host. For example, the entire RRC generated by the F1 termination point host is introduced into the RRC message CG-ConfigInfo contained therein.
  • IABOtherInformation which serves as the first RRC container to carry the IP address request information (IAB-TNLAddressInfo field) of the non-F1 termination point topology domain.
  • the non-F1 termination point host replies to the F1 termination point host with the secondary node addition response message (S-node Addition Response).
  • the secondary cell group configuration information field scg-CellGroupConfig in the RRC message CG-Config contained in it carries the non-F1 termination point host.
  • the entire RRC message generated is RRCReconfiguration.
  • RRCReconfiguration serves as the second RRC container to carry the IP address configuration information of the non-F1 termination point topology domain (iab-IP-AddressConfigurationList-r16 area).
  • Figure 15 is a schematic diagram of a method for configuring a transmission address in the dual connection scenario. As shown in Figure 15, the method includes:
  • the F1 termination point host sends the IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;
  • the F1 termination point host receives the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node sent by the non-F1 termination point host.
  • the IP address of the non-F1 termination point topology domain is requested in the process of modifying the secondary cell group.
  • the IP address request information is carried by the first RRC container, and the IP address configuration information is carried by The second RRC container is carried, the first RRC container is carried by the secondary node modification request message, and the second RRC container is carried by the secondary node modification response message.
  • the F1 termination point host sends a secondary node modification request message (S-node Modification Request) to the non-F1 termination point host.
  • S-node Modification Request secondary node modification request message
  • the entire F1 termination point host generated by the RRC message CG-ConfigInfo is introduced in it.
  • RRC message IABOtherInformation is introduced in it.
  • the IABOtherInformation serves as the first RRC container to carry the IP address request information (IAB-TNLAddressInfo domain) of the non-F1 termination point topology domain.
  • the non-F1 termination point host replies to the F1 termination point host with a secondary node modification response message (S-node Modification Response), the secondary cell group configuration information (scg-CellGroupConfig field) contained in the RRC message CG-Config carries the entire RRC message RRCReconfiguration generated by the non-F1 termination point host.
  • RRCReconfiguration serves as the second RRC container to carry the IP address configuration information of the non-F1 termination point topology domain (iab-IP-AddressConfigurationList-r16 domain).
  • the CG-ConfigInfo uses abstract syntax markup ASN.1 data format can be expressed as:
  • the CG-Config uses abstract syntax markup ASN.1 data format can be expressed as:
  • the RRCReconfiguration uses an abstract syntax to mark the representation of the ASN.1 data format as described previously and will not be repeated here.
  • the address configuration information element carries the IP address of the non-F1 termination point topological domain configured for the border node.
  • IP address request information is carried by the IABOtherInformatio contained in the first RRC container.
  • IP address request information can also be carried by the RRC reconfiguration message contained in the first RRC container. This embodiment of the present invention is not limited. .
  • the method may also include:
  • the F1 termination point host sends the received IP address configuration information to the IAB node; for example, the F1 termination point host forwards the RRCReconfiguration in the CG-Config generated by the non-F1 termination point host, and the RRCReconfiguration carries the non-F1 termination IP address configuration information of the point topology domain.
  • the non-F1 termination point host can also send the IP address configuration information to the IAB node. This is not a limitation in the embodiment of the present application.
  • the F1 termination point host can request the non-F1 termination point host to allocate the IP address of the non-F1 termination point topology domain, or further receive the IP address of the non-F1 termination point topology domain allocated by the non-F1 termination point host for the IAB node. IP address configuration information, so that the F1 termination point host can request the IP address of the non-F1 termination point topology domain, or further send the non-F1 termination point topology to the IAB node when the non-F1 termination point host cannot send a message to the IAB node.
  • the IP address of the domain In this way, for the routing ID of the non-F1 termination point topology domain, the IAB node can use the IP address of the non-F1 termination point topology domain.
  • Figure 16 is a schematic diagram of another method of configuring the transmission address in the dual connection scenario. As shown in Figure 16, the method includes:
  • the F1 termination point host receives the IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node sent by the non-F1 termination point host.
  • the second RRC container is carried by the secondary node modification request message.
  • the difference from Figure 15 is that after the dual connection establishment is completed and the SN does not establish SRB3, the F1 termination point host is not required to actively request the IP address of the non-F1 termination point topology domain. , the non-F1 termination point host can actively initiate IP address reconfiguration for the non-F1 termination point topology domain.
  • the IP address configuration information is carried by the second RRC container, and the second RRC container is carried by the secondary node modification request message.
  • the non-F1 termination point host sends the secondary node modification requirement message (S-node Modification Required) to the F1 termination point host, such as the secondary cell group in the RRC message CG-Config contained therein.
  • the configuration information (scg-CellGroupConfig domain) carries the entire RRC message RRCReconfiguration generated by the non-F1 termination point host.
  • RRCReconfiguration serves as the second RRC container to carry the IP address configuration information of the non-F1 termination point topology domain, also called IP address reconfiguration information.
  • the IP address of the non-F1 termination point topology domain for border node reconfiguration can be carried through the IP address configuration information element contained in the RRC container RRCReconfiguration in the secondary node modification requirement message.
  • the method may also include:
  • the F1 termination point host forwards the received IP address configuration information to the IAB node; for example, the F1 termination point host forwards the RRCReconfiguration in the CG-Config generated by the non-F1 termination point host, and the RRCReconfiguration carries the non-F1 termination point topology. Domain IP address configuration information.
  • the F1 termination point host can receive the IP address configuration information of the non-F1 termination point topology domain actively sent by the non-F1 termination point host, so that when the non-F1 termination point host cannot send a message to the IAB node, the IAB The node sends the IP address of the non-F1 termination point topological domain. In this way, for the routing ID of the non-F1 termination point topology domain, the IAB node can use the IP address of the non-F1 termination point topology domain.
  • Figure 17 is a schematic diagram of dual connection scenario two.
  • the F1 termination point host is the primary node SN CU of the IAB node
  • the non-F1 termination point host is the The secondary node MN CU of the IAB node, after establishing dual connectivity, can migrate some services of the border node 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 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 requested during the dual connection establishment process. It can only be requested after the dual connection establishment is completed. Request/configure the IP address of the non-F1 termination point topology domain or the IP address of the F1 termination point topology domain, as explained below.
  • Figure 18 is a schematic diagram of a method for configuring the transmission address in the dual connection scenario. As shown in Figure 18, the method includes:
  • the F1 termination point host sends the IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;
  • the IP address of the non-F1 termination point topology domain is requested in the process of modifying the secondary cell group.
  • the IP address request information is carried by the first RRC container, and the first RRC container is The secondary node modification requirement message is carried.
  • the F1 termination point host sends a secondary node modification requirement message to the non-F1 termination point host.
  • the IP address request information (IAB-TNLAddressInfo field) is introduced into the RRC message CG-Config contained therein to carry the entire RRC message IABOtherInformation generated by the F1 termination point host.
  • the IABOtherInformation serves as the first RRC container to carry the IP address request information of the non-F1 termination point topology domain.
  • the non-F1 termination point host Since the IP address configured by the non-F1 termination point host can be directly sent by the non-F1 termination point host to the border node through SRB1, the non-F1 termination point host does not need to reply to the F1 termination point host with the IP address configuration information. In other words, The F1 termination point host will not receive IP address configuration information sent by non-F1 termination point hosts.
  • the CG-Config uses abstract syntax markup ASN.1 data format can be expressed as:
  • a new RRC container IABOtherInformation can be introduced in the secondary node modification request message to request the IP address of the non-F1 termination point topology domain.
  • IP address request information is carried by the IABOtherInformatio contained in the first RRC container.
  • IP address request information can also be carried by the RRC reconfiguration message contained in the first RRC container. This embodiment of the present invention is not limited. .
  • the method may further include:
  • the non-F1 termination point host sends IP address configuration information to the IAB node; for example, the non-F1 termination point host generates an RRCReconfiguration, which carries the IP address configuration information of the non-F1 termination point topology domain.
  • the F1 termination point host can request the non-F1 termination point host to allocate the IP address of the non-F1 termination point topology domain, so that the F1 termination point host requests the IP address of the non-F1 termination point topology domain and receives the IP address from the non-F1 termination point.
  • the host sends the IP address of the non-F1 termination point topology domain to the IAB node.
  • the IAB node can use the IP address of the non-F1 termination point topology domain.
  • Figure 19 is a schematic diagram of another method for configuring the transmission address in the second dual connection scenario. As shown in Figure 19, the method includes:
  • the F1 termination point host sends the IP address configuration information for the F1 termination point topology domain allocated by the IAB node to the non-F1 termination point host.
  • the second RRC container is carried by the secondary node modification request message.
  • the F1 termination point host can actively initiate IP address reconfiguration for the F1 termination point topology domain, and the IP address configuration information is provided by the second
  • the second RRC container is carried by the RRC container, and the second RRC container is carried by the secondary node modification requirement message.
  • the F1 termination point host sends the secondary node modification requirement message (S-node Modification Required) to the non-F1 termination point host, such as the secondary cell configuration in the RRC message CG-Config contained therein.
  • the information (scg-CellGroupConfig domain) carries the entire RRC message RRCReconfiguration generated by the F1 termination point host.
  • RRCReconfiguration serves as the second RRC container to carry the IP address configuration information of the F1 termination point topology domain, also called IP address reconfiguration information.
  • the CG-Config uses abstract syntax markup ASN.1 data format can be expressed as:
  • the IP address of the F1 termination point topology domain for the border node reconfiguration may be indicated by the existing IP address configuration information element in the secondary node modification requirement message.
  • the method may also include:
  • the non-F1 termination point host forwards the received IP address configuration information of the F1 termination point topology domain to the IAB node; for example, the non-F1 termination point host forwards the RRCReconfiguration in the CG-Config generated by the F1 termination point host.
  • the RRCReconfiguration Carrying the IP address configuration information of the F1 termination point topology domain.
  • the F1 termination point host can send the IP address configuration information of the F1 termination point topology domain to the non-F1 termination point host, so that when the F1 termination point host cannot send a message to the IAB node, the non-F1 termination point host can The IP address of the F1 termination point topology domain can be sent to the IAB node.
  • the IAB node can use the IP address of the F1 termination point topology domain.
  • Figure 20 is a schematic diagram of the RLF recovery scenario.
  • the F1 termination point host is the host (old host CU) of the IAB node after RLF recovery
  • the non-F1 termination point The point host is the host (new host CU) of the IAB node before RLF recovery.
  • the IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2.
  • Figure 21 is a schematic diagram of the transmission address configuration method in this switch scenario. , as shown in Figure 21, the method includes:
  • the F1 termination point host sends the IP address request information for the non-F1 termination point topological domain of the IAB node to the non-F1 termination point host;
  • the non-F1 termination point host sends a UE context acquisition request message (RETRIEVE UE CONTEXT REQUEST) to the F1 termination point host, and the F1 termination point host replies a UE context acquisition response message (RETRIEVE UE CONTEXT RESPONSE) to the non-F1 termination point host.
  • RETRIEVE UE CONTEXT REQUEST UE context acquisition request message
  • RETRIEVE UE CONTEXT RESPONSE UE context acquisition response message
  • the UE context acquisition response message contains the RRC message HandoverPreparationInformation.
  • the entire RRC message IABOtherInformation generated by the F1 termination point host can be introduced into the HandoverPreparationInformation.
  • the IABOtherInformation serves as the first RRC container to carry the IP address request information (IAB- TNLAddressInfo field), the IABOtherInformation may also include the IP address configuration information of the border node in the F1 termination point topology field. Since the border node is reestablished to the non-F1 termination point host, the IP address configuration information can only be sent by the non-F1 termination point host, so the non-F1 termination point host does not need to reply to the F1 termination point host with the IP address configuration information. In other words , the F1 termination point host will not receive the IP address configuration information sent by non-F1 termination point hosts.
  • a new RRC container IABOtherInformation can be introduced in the UE context acquisition response message to request the IP address of the non-F1 termination point topology domain.
  • IP address request information is carried by the IABOtherInformatio contained in the first RRC container.
  • IP address request information can also be carried by the RRC reconfiguration message contained in the first RRC container. This embodiment of the present invention is not limited. .
  • the method may further include:
  • the non-F1 termination point host sends IP address configuration information to the IAB node; for example, the non-F1 termination point host generates an RRCReconfiguration, which carries the IP address configuration information of the non-F1 termination point topology domain.
  • the F1 termination point host can request the non-F1 termination point host to allocate the IP address of the non-F1 termination point topology domain, so that the F1 termination point host requests the IP address of the non-F1 termination point topology domain and receives the IP address from the non-F1 termination point.
  • the host sends the IP address of the non-F1 termination point topological domain to the IAB node.
  • the IAB node can use the IP address of the non-F1 termination point topology domain.
  • IP address request information and/or IP address configuration information is carried by the IAB transfer migration management request/response or by the IAB transfer migration modification request.
  • the IP address request information is carried by the IAB transmission migration management request message, and the IP address request information also includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node, that is, to indicate that the IAB node is a border node.
  • the IP address request information of the border node; the IP address configuration information is carried by the IAB transmission migration management response message or the IAB transmission migration modification request message.
  • the IP address configuration information contains the border node identification; the border node identification is used to indicate the IAB node It is a border node, that is to say, it indicates the IP address configuration information configured for the border node.
  • the migration management request/response transmitted by the IAB or the migration modification request transmitted by the IAB is exclusive to the IAB node and does not involve the configuration of the AS layer, therefore, the migration management request/response transmitted by the IAB or the migration modification request and the configuration are not transmitted by the IAB.
  • the IP address of the F1 termination point topology domain can make the request and configuration of the IP address simpler and more flexible.
  • FIG. 11 in the handover scenario, all services of the border node are migrated to the non-F1 termination point topological domain, the F1 termination point host is the source host of the IAB node switch, and the non-F1 termination point host is the target host for the IAB node switching.
  • the IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2.
  • Figure 22 is a schematic diagram of the transmission address configuration method in this switching scenario. As shown in Figure 22, the Methods include:
  • the F1 termination point host sends the IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;
  • the IP address request information is carried by an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST. Therefore, after handover preparation, the F1 termination point host sends an IAB transmission migration management request message to the non-F1 termination point host.
  • the IAB transmission migration management request message can carry the IP address request information of the non-F1 termination point topology domain IAB TNL ADDRESS REQUEST, the IP address request information also contains the border node identifier; the border node identifier is used to indicate that the IAB node is a border node, that is, it indicates that the IP address request information is for the IP of the non-F1 termination point topology domain of the border node Address request information.
  • the IAB TNL ADDRESS REQUEST uses abstract syntax notation ASN.1 data format can be expressed as:
  • IAB TNL ADDRESS REQUEST contains request information for IPv4 or IPv6 addresses IAB TNL Addresses Requested field and boundary node identification Boundary Node field.
  • IAB TNL Addresses Requested includes requests for the number of IP addresses for various services.
  • the non-F1 termination point host Since the RRC message can only be sent by the target host to the border node after the switch, the non-F1 termination point host does not need to reply to the F1 termination point host with the IP address configuration information of the non-F1 termination point topology domain.
  • the new information element IAB TNL ADDRESS REQUEST can be introduced in the IAB transport migration management request message to request the IP address of the non-F1 termination point topology domain for the border node.
  • the method may further include:
  • the non-F1 termination point host sends IP address configuration information to the IAB node; for example, the non-F1 termination point host generates the entire RRC message RRCReconfiguration.
  • RRCReconfiguration carries the IP address configuration information of the non-F1 termination point topology domain and sends it to the border node.
  • RRCReconfiguration uses abstract syntax to mark the representation of ASN.1 data format as mentioned before and will not be repeated here.
  • the RRCReconfiguration carries the IP address configuration information IAB-IP-AddressConfigurationList-r16 of the non-F1 termination point topology domain, including at least one IP address configuration IAB-IP-AddressConfiguration-r16, and each IP address configuration may include an IP address. Index and corresponding IP address.
  • the F1 termination point host can request the non-F1 termination point host to allocate the IP address of the non-F1 termination point topology domain, so that the F1 termination point host requests the IP address of the non-F1 termination point topology domain and receives the IP address from the non-F1 termination point.
  • the host sends the IP address of the non-F1 termination point topological domain to the IAB node.
  • the IAB node can use the IP address of the non-F1 termination point topology domain.
  • the F1 termination point host is the primary node MN of the IAB node
  • the 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, and some services are still in the F1 termination point host topology domain.
  • the IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2.
  • Figure 23 is a schematic diagram of a method for configuring a transmission address in this dual connection scenario. As shown in Figure 23, the method includes:
  • the F1 termination point host sends the IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host;
  • the F1 termination point host receives the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node sent by the non-F1 termination point host.
  • the IP address request information is carried by the IAB transmission migration management request message, and the IP address configuration information is responded by the IAB transmission migration management Message bearer.
  • the IP address request information IAB TNL ADDRESS REQUEST of the non-F1 termination point topology domain is introduced in the IAB transmission migration management request message.
  • the IP address request information also contains the boundary node identifier; the boundary node identifier is used to indicate that the IAB node is the boundary node, that is, the IP address request information indicates that the IP address request information is for the non-F1 termination point topological domain of the border node.
  • the non-F1 termination point host When the SN does not establish SRB3, the non-F1 termination point host replies IAB transfer migration to the F1 termination point host.
  • Management response message for example, it carries the IP address configuration information (cell structure IAB TNL Address Response) of the non-F1 termination point topology domain.
  • the IP address configuration information can also contain a border node identifier; the border node identifier is used to indicate the The IAB node is a border node, which means that the IP address configuration information is for the non-F1 termination point topological domain of the border node.
  • the IAB TNL Address Response uses abstract syntax notation ASN.1 data format can be expressed as:
  • Each IP address configuration includes the specific IP address IAB TNL Address and the corresponding donor-DU. AddressAssociated Donor DU Address.
  • IAB TNL ADDRESS REQUEST can be introduced in the transmission migration management request message to request the IP address of the non-F1 termination point topology domain, and the information element in the IAB transmission migration management response message can be used IAB TNL Address Response indicates the IP address of the non-F1 termination point topological domain configured for the border node (not the child node).
  • the method may also include:
  • the F1 termination point host sends the received IP address configuration information to the IAB node; for example, the non-F1 termination point host generates the entire RRC message RRCReconfiguration.
  • RRCReconfiguration carries the IP address configuration information of the non-F1 termination point topology domain and sends it to Boundary node.
  • RRCReconfiguration uses abstract syntax to mark the representation of ASN.1 data format as mentioned before and will not be repeated here.
  • the non-F1 termination point host can also send the IP address configuration information to the IAB node.
  • the F1 termination point host needs to request an IP address from the non-F1 termination point host.
  • the non-F1 termination point host configures and replies to the F1 termination point host for the request with the IP address of the non-F1 termination point topological domain.
  • F1 The termination point host forwards it to the border node, so that for the routing ID of the non-F1 termination point topology domain, the IAB node can use the IP address of the non-F1 termination point topology domain.
  • Figure 24 is a schematic diagram of a method for configuring a transmission address in the dual connection scenario. As shown in Figure 24, the method includes:
  • the F1 termination point host receives the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node sent by the non-F1 termination point host.
  • the difference from Figure 23 is that when the SN does not establish SRB3, the F1 termination point host is not required to actively request the IP address of the non-F1 termination point topological domain.
  • the non-F1 termination point host You can proactively initiate IP address reconfiguration for non-F1 termination point topology domains.
  • the IP address configuration information is carried by the IAB TRANSPORT MODIFIATION REQUEST message.
  • the non-F1 termination point host sends an IAB transport migration modification request message to the F1 termination point host, such as carrying the IP address configuration of the non-F1 termination point topology domain in it.
  • Information cell structure IAB TNL Address Response, the specific data format is as mentioned above and will not be repeated here
  • IP address reconfiguration information also contains the border node identifier; the border node identifier It is used to indicate that the IAB node is a border node, that is, it indicates that the IP address configuration information is IP address reconfiguration information for the non-F1 termination point topological domain of the border node. Therefore, the IP address of the non-F1 termination point topological domain reconfigured for the border node (not the child node) can be indicated by the information element IAB TNL Address Response in the IAB Transport Migration Modification Request message.
  • the method may also include
  • the F1 termination point host forwards the received IP address configuration information to the IAB node; for example, the F1 termination point host forwards the RRCReconfiguration generated by the non-F1 termination point host, and the RRCReconfiguration carries the IP address configuration of the non-F1 termination point topology domain. information.
  • the F1 termination point host can receive the IP address configuration information of the non-F1 termination point topology domain actively sent by the non-F1 termination point host, so that when the non-F1 termination point host cannot send a message to the IAB node, the IAB The node sends the IP address of the non-F1 termination point topological domain. In this way, for the routing ID of the non-F1 termination point topology domain, the IAB node can use the IP address of the non-F1 termination point topology domain.
  • the F1 termination point host is the primary node SN CU of the IAB node
  • the non-F1 termination point host is the secondary node MN CU of the IAB node.
  • some services of the border node can be migrated to the non-F1 termination point topology domain, and some services are still in the F1 termination point host topology domain.
  • the IP address of the non-F1 termination point topology domain refers to the IP anchored to donor-DU1 Address
  • the IP address of the F1 termination point topology domain refers to the IP address anchored to donor-DU2.
  • Figure 25 is a schematic diagram of a method for configuring the transmission address in the dual connection scenario. As shown in Figure 25, the method includes:
  • the F1 termination point host sends the IP address request information for the non-F1 termination point topological domain of the IAB node to the non-F1 termination point host;
  • the IP address of the non-F1 termination point topology domain is requested, and the IP address request information is carried by the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST.
  • the F1 termination point host sends an IAB transmission migration management request message to the non-F1 termination point host, for example, introducing the IP address request information of the non-F1 termination point topology domain IAB TNL ADDRESS REQUEST (the specific data format is as mentioned above and will not be repeated here.
  • the IP address request information also contains a border node identifier; the border node identifier is used to indicate that the IAB node is a border node, that is, to indicate that the IP address request information is for the IP of the non-F1 termination point topology domain of the border node.
  • Address request information Since the IP address configured by the non-F1 termination point host can be directly sent by the non-F1 termination point host to the border node through SRB1, the non-F1 termination point host does not need to reply to the F1 termination point host.
  • the IP address configuration information In other words, the F1 termination point host will not receive IP address configuration information sent by non-F1 termination point hosts.
  • the new information element IAB TNL ADDRESS REQUEST can be introduced in the IAB transmission migration management request message to request the IP address of the non-F1 termination point topology domain.
  • the method may further include:
  • the non-F1 termination point host sends IP address configuration information to the IAB node; for example, the non-F1 termination point host generates RRCReconfiguration, which carries the IP address configuration information of the non-F1 termination point topology domain IAB TNL ADDRESS, and the IP address configuration information It also contains a border node identifier; the border node identifier is used to indicate that the IAB node is a border node, that is, to indicate that the IP address configuration information is the IP address configuration information for the non-F1 termination point topological domain of the border node.
  • the F1 termination point host can request the non-F1 termination point host to allocate the IP address of the non-F1 termination point topology domain, so that the F1 termination point host requests the IP address of the non-F1 termination point topology domain and receives the IP address from the non-F1 termination point.
  • the host sends the IP address of the non-F1 termination point topological domain to the IAB node.
  • the IAB node can use the IP address of the non-F1 termination point topology domain.
  • Figure 26 is a schematic diagram of another method for configuring the transmission address in the dual connection scenario. As shown in Figure 26, the method includes:
  • the F1 termination point host sends the IP address configuration information for the F1 termination point topology domain allocated by the IAB node to the non-F1 termination point host.
  • the F1 termination point host does not need to request the IP address of the non-F1 termination point topology domain.
  • the F1 termination point host can actively initiate F1 termination. IP address reconfiguration in a point topology domain.
  • the IP address configuration information is carried by the IAB transmission migration management request message.
  • the IP address configuration information also contains the border node identifier; the border node identifier is used to indicate that the IAB node is a border node, and also This indicates that the IP address configuration information is for the non-F1 termination point topological domain of the border node.
  • the F1 termination point host sends an IAB transmission migration management request message to a non-F1 termination point host, for example, it carries the IP address configuration information (cell structure IAB TNL Address Response) of the F1 termination point topology domain.
  • IP address configuration information cell structure IAB TNL Address Response
  • the border node identifier is used to indicate that the IAB node is a border node, that is, to indicate that the IP address configuration information is the IP address configuration information for the non-F1 termination point topological domain of the border node, also called an IP address. Reconfiguration information.
  • the abstract syntax example used by IAB TNL Address Response is as mentioned above and will not be repeated here.
  • the IP address of the F1 termination point topology domain reconfigured for the border node (not the child node) can be indicated by introducing a new information element IAB TNL Address Response in the IAB Transport Migration Management Request message.
  • the method may also include:
  • the non-F1 termination point host forwards the received IP address configuration information of the F1 termination point topology domain to the IAB node; for example, the non-F1 termination point host generates RRCReconfiguration, which carries the IP address configuration information of the F1 termination point topology domain. .
  • the F1 termination point host can send the IP address configuration information of the F1 termination point topology domain to the non-F1 termination point host, so that when the F1 termination point host cannot send a message to the IAB node, the non-F1 termination point host can The IP address of the F1 termination point topology domain can be sent to the IAB node.
  • the IAB node can use the IP address of the F1 termination point topology domain.
  • the F1 termination point host is the host of the IAB node after RLF recovery (old host CU), and the non-F1 termination point host is the IAB before RLF recovery.
  • the host of the node (new host CU), the IP address of the non-F1 termination point topology domain refers to the IP address anchored to donor-DU2.
  • Figure 27 is a schematic diagram of the transmission address configuration method in this switching scenario. As shown in Figure 27, the Methods include:
  • the F1 termination point host sends the IP address request information for the non-F1 termination point topological domain of the IAB node to the non-F1 termination point host;
  • the F1 termination point host sends an IAB transport migration management request message to the non-F1 termination point host, for example, introducing the IP address request information IAB TNL ADDRESS REQUEST of the non-F1 termination point topology domain, and the IP address request information also contains the boundary Node identifier; the border node identifier is used to indicate that the IAB node is a border node, that is, to indicate that the IP address request information is for the non-F1 termination point topological domain of the border node.
  • the IP address configuration information can only be sent by the non-F1 termination point host. Therefore, the non-F1 termination point host does not need to reply to the F1 termination point host with the IP of the non-F1 termination point topology domain. Address configuration information, in other words, the F1 termination point host will not receive the IP address configuration information sent by non-F1 termination point hosts.
  • the new information element IAB TNL ADDRESS REQUEST can be introduced in the IAB transmission migration management request message to request the IP address of the non-F1 termination point topology domain.
  • the method may further include:
  • the non-F1 termination point host sends IP address configuration information to the IAB node; for example, the non-F1 termination point host generates an RRCReconfiguration, and the RRCReconfiguration carries the IP address configuration information of the non-F1 termination point topology domain.
  • the F1 termination point host can request the non-F1 termination point host to allocate the IP address of the non-F1 termination point topology domain, so that the F1 termination point host requests the IP address of the non-F1 termination point topology domain and receives the IP address from the non-F1 termination point.
  • the host sends the IP address of the non-F1 termination point topological domain to the IAB node.
  • the IAB node can use the IP address of the non-F1 termination point topology domain.
  • the F1 termination point host can request the non-F1 termination point host to allocate the IP address of the non-F1 termination point topology domain, or further receive the IP address of the non-F1 termination point topology domain allocated by the non-F1 termination point host for the IAB node. IP address configuration information, so that the F1 termination point host can request the IP address of the non-F1 termination point topology domain, or further send the IP address of the non-F1 termination point topology domain for the IAB node, for example, when the non-F1 termination point host cannot provide When the IAB node sends a message.
  • the F1 termination point host can receive the IP address configuration information of the non-F1 termination point topology domain actively sent by the non-F1 termination point host, so as to send the IP address of the non-F1 termination point topology domain to the IAB node. For example, when the non-F1 termination point host cannot When sending a message to the IAB node.
  • the F1 termination point host can send the IP address configuration information of the F1 termination point topology domain to the non-F1 termination point host, so that the non-F1 termination point host can send the IP address of the F1 termination point topology domain to the IAB node. For example, when F1 When the termination point host cannot send messages to the IAB node.
  • the IAB node can use the IP address of the non-F1 termination point topology domain, and for the routing ID of the F1 termination point topology domain, the IP address of the F1 termination point topology domain can be used.
  • the embodiment of this application provides a transport address configuration method, which is explained from the non-F1 termination point host side. The same content as the embodiment of the first aspect will not be described again.
  • Figure 28 is another schematic diagram of the transmission address configuration method according to the embodiment of the present application. As shown in Figure 28, the method includes:
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topological domain of the IAB node sent by the F1 termination point host; and/or,
  • the non-F1 termination point host sends the IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node to the F1 termination point host; and/or,
  • the non-F1 termination point host receives the IP address configuration information for the F1 termination point topology domain assigned by the IAB node sent by the F1 termination point host.
  • the method may further include: (not shown)
  • the non-F1 termination point host sends the IP address configuration information to the IAB node.
  • the IP address request information is carried by a first RRC container.
  • the first RRC container also includes the IP address configuration information of the IAB node in the F1 termination point topology domain.
  • the IP address request information It is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.
  • the first RRC container is carried by at least one of the following messages:
  • the IP address configuration information is carried by the second RRC container.
  • the IP address configuration information is carried by the RRC reconfiguration message (RRCReconfiguration) contained in the second RRC container.
  • the second RRC container is carried by at least one of the following messages:
  • the secondary node adds a response message
  • the F1 termination point host is the source host of the IAB node switching
  • the non-F1 termination point host is the target host of the IAB node switching.
  • the method includes:
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, and the non-F1 termination point host sends the IP address allocated for the IAB node to the F1 termination point host.
  • the IP address configuration information of the non-F1 termination point topology domain, the first RRC container is carried by the handover request message, and the second RRC container is carried by the handover request response message.
  • the F1 termination point host is the primary node MN of the IAB node, and the non-F1 termination point host is the secondary node SN of the IAB node.
  • the method includes:
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, and the first RRC container is carried by a secondary node add request message or a secondary node modification request message, Further, the non-F1 termination point host sends the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node to the F1 termination point host, and the second RRC container is added by a secondary node response message or a secondary node modification response message. carry. Optionally, the non-F1 termination point host also sends the IP address configuration information to the IAB node.
  • the F1 termination point host is the primary node MN of the IAB node, and the non-F1 termination point host is the secondary node SN of the IAB node.
  • the method includes:
  • the non-F1 termination point host sends the IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node to the F1 termination point host, and the second RRC container is carried by the secondary node modification request message.
  • the non-F1 termination point host is the primary node MN of the IAB node, and the F1 termination point host is the secondary node SN of the IAB node.
  • the method includes:
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, and the first RRC container is carried by the secondary node modification request message.
  • the non-F1 termination point host also sends the IP address configuration information to the IAB node.
  • the non-F1 termination point host is the primary node MN of the IAB node, and the F1 termination point host is the secondary node SN of the IAB node.
  • the method includes:
  • the non-F1 termination point host receives the IP address configuration information for the F1 termination point topology domain allocated by the border node sent by the F1 termination point host, and the second RRC container is carried by the secondary node modification request message.
  • the non-F1 termination point host also sends the IP address configuration information to the IAB node.
  • the F1 termination point host is the host of the IAB node after RLF recovery
  • the non-F1 termination point host is the host of the IAB node before RLF recovery.
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, and the first RRC container is carried by the UE context acquisition response message.
  • the non-F1 termination point host also sends the IP address configuration information to the IAB node.
  • the IP address request information is carried by an IAB transport migration management request message.
  • the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • the IP address configuration information is carried by an IAB transmission migration management response message or an IAB transmission migration modification request message, and the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • the F1 termination point host is the source host of the IAB node switching
  • the non-F1 termination point host is the target host of the IAB node switching.
  • the method includes:
  • the non-F1 termination point host receives the IP address request information sent by the F1 termination point host for the non-F1 termination point topology domain of the IAB node.
  • the IP address request information is carried by the IAB transmission migration management request message.
  • the non-F1 termination point host also sends the IP address configuration information to the IAB node.
  • the method includes:
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host.
  • the IP address request information is carried by the IAB transmission migration management request message.
  • the non-F1 The termination point host sends the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node to the F1 termination point host.
  • the IP address configuration information is carried by the IAB transmission migration management response message.
  • the non-F1 termination point host also sends the IP address configuration information to the IAB node.
  • the F1 termination point host is the primary node MN of the IAB node, and the non-F1 termination point host is the secondary node SN of the IAB node.
  • the method includes:
  • the non-F1 termination point host sends the IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node to the F1 termination point host.
  • the IP address configuration information is carried by the IAB transmission migration modification request message.
  • the non-F1 termination point host is the primary node MN of the IAB node, and the F1 termination point host is the secondary node SN of the IAB node.
  • the method includes:
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host.
  • the IP address request information is carried by the IAB transmission migration management request message.
  • the non-F1 termination point host also sends the IP address configuration information to the IAB node.
  • the non-F1 termination point host is the primary node MN of the IAB node, and the F1 termination point host is the secondary node SN of the IAB node.
  • the method includes:
  • the non-F1 termination point host receives the IP address configuration information for the F1 termination point topology domain allocated by the border node sent by the F1 termination point host.
  • the IP address configuration information is carried by the IAB transmission migration management request message.
  • the non-F1 termination point host also sends the IP address configuration information to the IAB node.
  • the F1 termination point host is the host of the IAB node after RLF recovery
  • the non-F1 termination point host is the host of the IAB node before RLF recovery.
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host.
  • the IP address request information is carried by the IAB transmission migration management request message.
  • the non-F1 termination point host also sends the IP address configuration information to the IAB node.
  • the F1 termination point host can request the non-F1 termination point host to allocate the IP address of the non-F1 termination point topology domain, or further receive the IP address of the non-F1 termination point topology domain allocated by the non-F1 termination point host for the IAB node. IP address configuration information, so that the F1 termination point host can request the IP address of the non-F1 termination point topology domain, or further send the IP address of the non-F1 termination point topology domain for the IAB node, for example, when the non-F1 termination point host cannot provide When the IAB node sends a message.
  • the F1 termination point host can receive the IP address configuration information of the non-F1 termination point topology domain actively sent by the non-F1 termination point host, so as to send the IP address of the non-F1 termination point topology domain to the IAB node. For example, when the non-F1 termination point host cannot When sending a message to the IAB node.
  • the F1 termination point host can send the IP address configuration information of the F1 termination point topology domain to the non-F1 termination point host, so that the non-F1 termination point host can send the IP address of the F1 termination point topology domain to the IAB node. For example, when F1 When the termination point host cannot send messages to the IAB node.
  • the IAB node can use the IP address of the non-F1 termination point topology domain, and for the routing ID of the F1 termination point topology domain, the IP address of the F1 termination point topology domain can be used.
  • the embodiment of the present application provides an IAB host device, and the same content as the embodiment of the first aspect will not be described again.
  • the device may be, for example, the IAB donor-CU in the IAB system (such as the first donor-CU or the F1 termination point host in the first and second embodiments), or it may be configured on the IAB donor-CU or the F1 termination point. Click on one or some parts or components or modules in the host.
  • FIG 29 is a schematic diagram of an IAB host device according to an embodiment of the present application. As shown in Figure 29, IAB host device 2900 includes:
  • the first sending part 2901 sends IP address request information for the non-F1 termination point topological domain of the IAB node to the non-F1 termination point host; and/or,
  • the first receiving unit 2902 receives the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node sent by the non-F1 termination point host.
  • the IP address request information is carried by the first RRC container.
  • the first RRC container further includes the IP address configuration information of the IAB node in the F1 termination point topology domain.
  • the IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.
  • IAB information messages IABOtherInformation
  • RRCReconfiguration RRC reconfiguration messages
  • the first RRC container is carried by at least one of the following messages:
  • the IP address configuration information is carried by the second RRC container.
  • the IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) contained in the second RRC container.
  • RRCReconfiguration RRC reconfiguration message
  • the second RRC container is carried by at least one of the following messages:
  • the secondary node adds a response message
  • the F1 termination point host is the source host of the IAB node switch
  • the non-F1 termination point host is the target host of the IAB node switch
  • the first sending unit sends a message to the non-F1 termination point host for the IAB node switch.
  • the first receiving unit receives the IP address configuration information of the non-F1 termination point topology domain assigned by the IAB node and is sent by the non-F1 termination point host.
  • the RRC container is carried by the handover request message
  • the second RRC container is carried by the handover request response message.
  • the first sending unit also sends the IP address configuration information to the IAB node.
  • the F1 termination point host is the primary node MN of the IAB node
  • the non-F1 termination point host is the secondary node SN of the IAB node
  • the first sending unit sends a message for the non-F1 termination point host to the non-F1 termination point host.
  • the first RRC container is carried by a secondary node add request message or a secondary node modification request message for the IP address request information of the non-F1 termination point topology domain of the IAB node; further, the first receiving unit receives the IP address request information sent by the non-F1 termination point host.
  • the second RRC container is carried by a secondary node adding response message or a secondary node modifying response message.
  • the first sending unit also sends the IP address configuration information to the IAB node.
  • the F1 termination point host is the primary node MN of the IAB node
  • the non-F1 termination point host is the secondary node SN of the IAB node
  • the first receiving unit receives the message sent by the non-F1 termination point host.
  • the IP address configuration information of the non-F1 termination point topology domain allocated by the IAB node is carried by the secondary node modification request message in the second RRC container.
  • the first sending unit also sends the IP address configuration information to the IAB node.
  • the non-F1 termination point host is the primary node MN of the IAB node
  • the F1 termination point host is the secondary node SN of the IAB node
  • the first sending unit sends a message for the non-F1 termination point host to the non-F1 termination point host.
  • the IP address request information of the non-F1 termination point topology domain of the IAB node, and the first RRC container is carried by the secondary node modification request message.
  • the non-F1 termination point host is the primary node MN of the IAB node
  • the F1 termination point host is the secondary node SN of the IAB node
  • the first sending part sends a message for the boundary to the non-F1 termination point host.
  • the IP address configuration information of the F1 termination point topology domain assigned by the node, and the second RRC container is carried by the secondary node modification request message.
  • the F1 termination point host is the host of the IAB node after the RLF is restored
  • the non-F1 termination point host is the host of the IAB node before the RLF is restored
  • the first sending part sends to the non-F1 termination point host
  • the first RRC container is carried by the UE context acquisition response message.
  • the IP address request information is carried by an IAB transport migration management request message.
  • the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • the IP address configuration information is carried by an IAB transport migration management response message or an IAB transport migration modification request message.
  • the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • the F1 termination point host is the source host of the IAB node switch
  • the non-F1 termination point host is the target host of the IAB node switch
  • the sending is sent to the non-F1 termination point host for the IAB node.
  • IP address request information for the non-F1 termination point topology domain is carried by the IAB transmission migration management request message.
  • the F1 termination point host is the primary node MN of the IAB node
  • the non-F1 termination point host is the secondary node SN of the IAB node
  • the first sending unit sends a message for the non-F1 termination point host to the non-F1 termination point host.
  • the IP address request information is carried by the IAB transmission migration management request message.
  • the first receiving unit receives the allocation for the IAB node sent by the non-F1 termination point host.
  • the IP address configuration information of the non-F1 termination point topology domain is carried by the IAB transport migration management response message.
  • the first sending unit also sends the IP address configuration information to the IAB node.
  • the F1 termination point host is the primary node MN of the IAB node
  • the non-F1 termination point host is the secondary node SN of the IAB node
  • the first receiving unit receives the message sent by the non-F1 termination point host.
  • the IP address configuration information is carried by the IAB transmission migration modification request message.
  • the first sending unit also sends the IP address configuration information to the IAB node.
  • the non-F1 termination point host is the primary node MN of the IAB node
  • the F1 termination point host is the secondary node SN of the IAB node
  • the first sending unit sends a message for the non-F1 termination point host to the non-F1 termination point host.
  • the non-F1 termination point host is the primary node MN of the IAB node
  • the F1 termination point host is the secondary node SN of the IAB node
  • the first sending part sends a message to the non-F1 termination point host for the border node.
  • the F1 termination point host is the host of the IAB node after the RLF is restored
  • the non-F1 termination point host is the host of the IAB node before the RLF is restored
  • the first sending part sends to the non-F1 termination point host
  • the IP address request information for the non-F1 termination point topology domain of the IAB node is carried by the IAB transmission migration management request message.
  • the IAB host device 2900 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. 29 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 processors, memories, transmitters, receivers, etc.; the implementation of this application is not limited to this.
  • the F1 termination point host can request the non-F1 termination point host to allocate the IP address of the non-F1 termination point topology domain, or further receive the IP address of the non-F1 termination point topology domain allocated by the non-F1 termination point host for the IAB node. IP address configuration information, so that the F1 termination point host can request the IP address of the non-F1 termination point topology domain, or further send the IP address of the non-F1 termination point topology domain for the IAB node, for example, when the non-F1 termination point host cannot provide When the IAB node sends a message.
  • the F1 termination point host can receive the IP address configuration information of the non-F1 termination point topology domain actively sent by the non-F1 termination point host, so as to send the IP address of the non-F1 termination point topology domain to the IAB node. For example, when the non-F1 termination point host cannot When sending a message to the IAB node.
  • the F1 termination point host can send the IP address configuration information of the F1 termination point topology domain to the non-F1 termination point host, so that the non-F1 termination point host can send the IP address of the F1 termination point topology domain to the IAB node. For example, when F1 When the termination point host cannot send messages to the IAB node.
  • the IAB node can use the IP address of the non-F1 termination point topology domain, and for the routing ID of the F1 termination point topology domain, the IP address of the F1 termination point topology domain can be used.
  • 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, the IAB donor-CU in the IAB system (such as the second donor-CU or the non-F1 termination point host in the first and second embodiments), or may be configured in the IAB donor-CU or non-F1 termination point host.
  • F1 termination point is one or more components or components or modules in the host.
  • FIG 30 is a schematic diagram of an IAB host device according to an embodiment of the present application. As shown in Figure 30, IAB host device 3000 includes:
  • the second receiving unit 3001 receives the IP address request information for the non-F1 termination point topological domain of the IAB node sent by the F1 termination point host; and/or,
  • the second sending unit 3002 is configured to send IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node to the F1 termination point host.
  • the IP address request information is carried by the first RRC container.
  • the first RRC container further includes the IP address configuration information of the IAB node in the F1 termination point topology domain.
  • the IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.
  • IAB information messages IABOtherInformation
  • RRCReconfiguration RRC reconfiguration messages
  • the first RRC container is carried by at least one of the following messages:
  • the IP address configuration information is carried by the second RRC container.
  • the IP address configuration information is carried by an RRC reconfiguration message (RRCReconfiguration) contained in the second RRC container.
  • RRCReconfiguration RRC reconfiguration message
  • the second RRC container is carried by at least one of the following messages:
  • the secondary node adds a response message
  • the F1 termination point host is the source host of the IAB node switch
  • the non-F1 termination point host is the target host of the IAB node switch
  • the second receiving unit receives the message sent by the F1 termination point host for the IAB node switch.
  • the second sending unit sends IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node to the F1 termination point host, and the first RRC container It is carried by the handover request message, and the second RRC container is carried by the handover request response message.
  • the F1 termination point host is the primary node MN of the IAB node
  • the non-F1 termination point host is the secondary node SN of the IAB node
  • the second receiving unit receives the message sent by the F1 termination point host for the
  • the first RRC container is carried by a secondary node add request message or a secondary node modification request message for the IP address request information of the non-F1 termination point topology domain of the IAB node.
  • the second sending unit sends the request information for the F1 termination point host to the F1 termination point host.
  • the IP address configuration information of the non-F1 termination point topology domain allocated by the IAB node, and the second RRC container is carried by the secondary node add response message or the secondary node modification response message.
  • the second sending unit also sends the IP address configuration information to the IAB node.
  • the F1 termination point host is the primary node MN of the IAB node
  • the non-F1 termination point host is the secondary node SN of the IAB node
  • the second sending unit sends a message to the F1 termination point host for the IAB.
  • the second RRC container is carried by the secondary node modification request message.
  • the non-F1 termination point host is the primary node MN of the IAB node
  • the F1 termination point host is the secondary node SN of the IAB node
  • the second receiving unit receives the message sent by the F1 termination point host for the The IP address request information of the non-F1 termination point topology domain of the IAB node, and the first RRC container is carried by the secondary node modification request message.
  • the second sending unit also sends the IP address configuration information to the IAB node.
  • the non-F1 termination point host is the primary node MN of the IAB node
  • the F1 termination point host is the secondary node SN of the IAB node
  • the second receiving unit receives the border-specific message sent by the F1 termination point host.
  • the IP address configuration information of the F1 termination point topology domain assigned by the node, and the second RRC container is carried by the secondary node modification request message.
  • the second sending unit also sends the IP address configuration information to the IAB node.
  • the F1 termination point host is the host of the IAB node after the RLF is restored
  • the non-F1 termination point host is the host of the IAB node before the RLF is restored
  • the second receiving unit receives the message sent by the F1 termination point host.
  • the first RRC container is carried by the UE context acquisition response message.
  • the second sending unit also sends the IP address configuration information to the IAB node.
  • the IP address request information is carried by an IAB transport migration management request message.
  • the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • the IP address configuration information is carried by an IAB transport migration management response message or an IAB transport migration modification request message.
  • the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • the F1 termination point host is the source host of the IAB node switch
  • the non-F1 termination point host is the target host of the IAB node switch
  • the second receiving unit receives the F1 termination point host sent for the IAB IP address request information of the node's non-F1 termination point topology domain.
  • the IP address request information is carried by the IAB transmission migration management request message.
  • the second sending unit also sends the IP address configuration information to the IAB node.
  • the F1 termination point host is the primary node MN of the IAB node
  • the non-F1 termination point host is the secondary node SN of the IAB node
  • the second receiving unit receives the message sent by the F1 termination point host for the
  • the IP address request information of the non-F1 termination point topology domain of the IAB node is carried by the IAB transmission migration management request message.
  • the second sending unit sends the non-F1 termination point host allocated for the IAB node to the F1 termination point host.
  • the IP address configuration information of the F1 termination point topology domain is carried by the IAB transmission migration management response message.
  • the second sending unit also sends the IP address configuration information to the IAB node.
  • the F1 termination point host is the primary node MN of the IAB node
  • the non-F1 termination point host is the secondary node SN of the IAB node
  • the second sending unit sends a message to the F1 termination point host for the IAB.
  • the IP address configuration information is carried by the IAB transmission migration modification request message.
  • the non-F1 termination point host is the primary node MN of the IAB node
  • the F1 termination point host is the secondary node SN of the IAB node
  • the second receiving unit receives the message sent by the F1 termination point host for the IP address request information for the non-F1 termination point topology domain of the IAB node.
  • the IP address request information is carried by the IAB transmission migration management request message.
  • the second sending unit also sends the IP address configuration information to the IAB node.
  • the non-F1 termination point host is the primary node MN of the IAB node
  • the F1 termination point host is the secondary node SN of the IAB node
  • the second receiving unit receives the border-specific message sent by the F1 termination point host.
  • the IP address configuration information is carried by the IAB transmission migration management request message.
  • the second sending unit also sends the IP address configuration information to the IAB node.
  • the F1 termination point host is the host of the IAB node after the RLF is restored
  • the non-F1 termination point host is the host of the IAB node before the RLF is restored
  • the second receiving unit receives the message sent by the F1 termination point host.
  • the IP address request information for the non-F1 termination point topology domain of the IAB node is carried by the IAB transmission migration management request message.
  • the second sending unit also sends the IP address configuration information to the IAB node.
  • the IAB host device 3000 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.
  • Figure 30 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 F1 termination point host can request the non-F1 termination point host to allocate the IP address of the non-F1 termination point topology domain, or further receive the IP address of the non-F1 termination point topology domain allocated by the non-F1 termination point host for the IAB node. IP address configuration information, so that the F1 termination point host can request the IP address of the non-F1 termination point topology domain, or further send the IP address of the non-F1 termination point topology domain for the IAB node, for example, when the non-F1 termination point host cannot provide When the IAB node sends a message.
  • the F1 termination point host can receive the IP address configuration information of the non-F1 termination point topology domain actively sent by the non-F1 termination point host, so as to send the IP address of the non-F1 termination point topology domain to the IAB node. For example, when the non-F1 termination point host cannot When sending a message to the IAB node.
  • the F1 termination point host can send the IP address configuration information of the F1 termination point topology domain to the non-F1 termination point host, so that the non-F1 termination point host can send the IP address of the F1 termination point topology domain to the IAB node. For example, when F1 When the termination point host cannot send messages to the IAB node.
  • the IAB node can use the IP address of the non-F1 termination point topology domain, and for the routing ID of the F1 termination point topology domain, the IP address of the F1 termination point topology domain can be used.
  • the embodiment of the present application provides a communication system.
  • the IAB system includes: the IAB host device 2900 of the third embodiment and/or the IAB host device 3000 of the fourth embodiment, and also includes an IAB node (border node), Regarding the network architecture of the host (donor) device and IAB node, you can also refer to related technologies, and the description is omitted here.
  • An embodiment of the present application also provides an IAB host device.
  • FIG. 9 is a schematic diagram of an IAB host 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 configuration method as in the embodiment of the first aspect.
  • the processor 901 may be configured to execute a program to implement the transmission address configuration method in the embodiment of the second aspect.
  • the IAB host 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.
  • Embodiments of the present application also provide a computer-readable program, wherein when the program is executed in an IAB host device, the program causes the computer to execute the embodiments of the first to second aspects in the IAB host device.
  • Transport address configuration method when the program is executed in an IAB host device, the program causes the computer to execute the embodiments of the first to second aspects in the IAB host device.
  • An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes the computer to execute the transmission address configuration method in the embodiments of the first to second aspects in the IAB host 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 transport address configuration method applied to the F1 termination point host device of an IAB node, characterized in that the method includes:
  • the F1 termination point host sends IP address request information for the non-F1 termination point topological domain of the IAB node to the non-F1 termination point host; and/or,
  • the F1 termination point host receives the IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node sent by the non-F1 termination point host; and/or,
  • the F1 termination point host sends the IP address configuration information for the F1 termination point topology domain allocated by the IAB node to the non-F1 termination point host.
  • IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.
  • IAB information messages IABOtherInformation
  • RRCReconfiguration RRC reconfiguration messages
  • the secondary node adds a response message
  • the F1 termination point host sends IP address request information for the non-F1 termination point topological domain of the IAB node to the non-F1 termination point host, and the F1 termination point host receives the IP address request information sent by the non-F1 termination point host.
  • the F1 termination point host sends the IP address configuration information to the IAB node.
  • the F1 termination point host sends IP address request information for the non-F1 termination point topological domain of the IAB node to the non-F1 termination point host; wherein the first RRC container is added by a secondary node request message or a secondary node Modify the request message bearer.
  • the F1 termination point host receives the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node sent by the non-F1 termination point host, and the second RRC container is added by a secondary node response message or a secondary node Modify the response message bearer.
  • the F1 termination point host sends the IP address configuration information to the IAB node.
  • the F1 termination point host receives the IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node sent by the non-F1 termination point host; wherein the second RRC container is carried by a secondary node modification requirement message. .
  • the F1 termination point host sends the IP address configuration information to the IAB node.
  • the F1 termination point host sends IP address request information for the non-F1 termination point topological domain of the IAB node to the non-F1 termination point host; wherein the first RRC container is carried by a secondary node modification requirement message.
  • the F1 termination point host sends the IP address configuration information for the F1 termination point topology domain allocated by the IAB node to the non-F1 termination point host; wherein the second RRC container is carried by a secondary node modification requirement message.
  • the methods include:
  • the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the first RRC container is carried by a UE context acquisition response message.
  • the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.
  • the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.
  • the F1 termination point host receives the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node sent by the non-F1 termination point host; wherein the IP address configuration information is transmitted by the IAB migration management response message carry.
  • the F1 termination point host sends the IP address configuration information to the IAB node.
  • the F1 termination point host receives the IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node sent by the non-F1 termination point host; wherein the IP address configuration information is transmitted by the IAB in a migration modification request message carry.
  • the F1 termination point host sends the IP address configuration information to the IAB node.
  • the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.
  • the F1 termination point host sends the IP address configuration information for the F1 termination point topology domain allocated by the IAB node to the non-F1 termination point host; wherein the IP address configuration information is carried by an IAB transmission migration management request message.
  • the methods include:
  • the F1 termination point host sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.
  • An IAB host (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 25
  • the transport address configuration method comprising
  • a transport address configuration method applied to the non-F1 termination point host device of the IAB node, characterized in that the method includes:
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; and/or,
  • the non-F1 termination point host sends the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node to the F1 termination point host; and/or,
  • the non-F1 termination point host receives the IP address configuration information for the F1 termination point topology domain allocated by the IAB node sent by the F1 termination point host.
  • IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.
  • IAB information messages IABOtherInformation
  • RRCReconfiguration RRC reconfiguration messages
  • the secondary node adds a response message
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topological domain of the IAB node sent by the F1 termination point host, and the non-F1 termination point host sends a request for the F1 termination point host to the F1 termination point host.
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the first RRC container is added by a secondary node request message or secondary node. Node modification request message bearer.
  • the non-F1 termination point host sends the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node to the F1 termination point host; wherein the second RRC container is added by a secondary node response message or secondary node. Node modification response message bearer.
  • the non-F1 termination point host sends the IP address configuration information to the IAB node.
  • the non-F1 termination point host sends IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node to the F1 termination point host; wherein the second RRC container is carried by a secondary node modification requirement message.
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the first RRC container is carried by a secondary node modification requirement message.
  • the non-F1 termination point host sends the IP address configuration information to the IAB node.
  • the non-F1 termination point host receives the IP address configuration information for the F1 termination point topology domain allocated by the IAB node sent by the F1 termination point host; wherein the second RRC container is carried by a secondary node modification requirement message.
  • the non-F1 termination point host sends the IP address configuration information to the IAB node.
  • the methods include:
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the first RRC container is carried by a UE context acquisition response message.
  • the non-F1 termination point host sends the IP address configuration information to the IAB node.
  • the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • the non-F1 termination point host receives the IP address request information sent by the F1 termination point host for the non-F1 termination point topology domain of the IAB node; wherein the IP address request information is carried by an IAB transmission migration management request message.
  • the non-F1 termination point host sends the IP address configuration information to the IAB node.
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the IP address request information is carried by the IAB transmission migration management request message. .
  • the non-F1 termination point host sends the IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node to the F1 termination point host; wherein the IP address configuration information is carried by the IAB transmission migration management response message .
  • the non-F1 termination point host sends the IP address configuration information to the IAB node.
  • the non-F1 termination point host sends the IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node to the F1 termination point host; wherein the IP address configuration information is carried by the IAB transmission migration modification request message .
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the IP address request information is carried by the IAB transmission migration management request message. .
  • the non-F1 termination point host sends the IP address configuration information to the IAB node.
  • the non-F1 termination point host receives the IP address configuration information for the F1 termination point topology domain assigned by the IAB node sent by the F1 termination point host; wherein the IP address configuration information is carried by the IAB transmission migration management request message .
  • the non-F1 termination point host sends the IP address configuration information to the IAB node.
  • the methods include:
  • the non-F1 termination point host receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the IP address request information is carried by the IAB transmission migration management request message. .
  • the non-F1 termination point host sends the IP address configuration information to the IAB node.
  • An IAB host (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 25
  • the transport address configuration method comprising
  • An IAB host device is the F1 termination point host device of the IAB node, characterized in that the device includes:
  • the first sending part sends IP address request information for the non-F1 termination point topological domain of the IAB node to the non-F1 termination point host; and/or,
  • the first receiving unit receives the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node sent by the non-F1 termination point host.
  • IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.
  • IAB information messages IABOtherInformation
  • RRCReconfiguration RRC reconfiguration messages
  • the secondary node adds a response message
  • the device is the source host of the IAB node switching, the non-F1 termination point host is the target host of the IAB node switching, and the The first sending unit sends IP address request information for the non-F1 termination point topological domain of the IAB node to the non-F1 termination point host, and the first receiving unit receives the IP address request information sent by the non-F1 termination point host for the IAB node.
  • the device 10 or 8 wherein the F1 termination point host is the primary node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the The first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the first RRC container is configured by a secondary node addition request message or a secondary node modification request. Message bearer.
  • the first receiving unit also receives the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node sent by the non-F1 termination point host; wherein , the second RRC container is carried by a secondary node adding response message or a secondary node modifying response message.
  • the device 11 or 8 wherein the F1 termination point host is the primary node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the The first receiving unit receives the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node sent by the non-F1 termination point host; wherein the second RRC container is carried by a secondary node modification requirement message.
  • the device wherein the non-F1 termination point host is the primary node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the The first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the first RRC container is carried by a secondary node modification requirement message.
  • the device wherein the non-F1 termination point host is the primary node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the The first sending part sends the IP address configuration information for the F1 termination point topology domain allocated by the IAB node to the non-F1 termination point host; wherein the second RRC container is carried by a secondary node modification requirement message.
  • the device 14
  • the device 14 or 8 wherein the F1 termination point host is the host of the IAB node after RLF recovery, and the non-F1 termination point host is the host of the IAB node before RLF recovery
  • the first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the first RRC container is carried by a UE context acquisition response message.
  • the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • IP address configuration information is carried by an IAB transmission migration management response message or an IAB transmission migration modification request message.
  • the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • the F1 termination point host is the source host of the IAB node switching
  • the non-F1 termination point host is the target host of the IAB node switching
  • the Send IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.
  • the device 20.
  • the F1 termination point host is the primary node MN of the IAB node
  • the non-F1 termination point host is the secondary node SN of the IAB node
  • the The first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.
  • the first receiving unit also receives the IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node sent by the non-F1 termination point host; wherein , the IP address configuration information is carried by the IAB transmission migration management response message.
  • the device according to appendix 15 or 17, wherein the F1 termination point host is the primary node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the The first receiving unit receives the IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node sent by the non-F1 termination point host; wherein the IP address configuration information is carried by the IAB transmission migration modification request message.
  • the device 22.
  • the non-F1 termination point host is the primary node MN of the IAB node
  • the F1 termination point host is the secondary node SN of the IAB node
  • the The first sending unit sends IP address request information for the non-F1 termination point topological domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.
  • the device according to appendix 15 or 17, wherein the non-F1 termination point host is the primary node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the The first sending unit sends IP address configuration information for the F1 termination point topology domain allocated by the IAB node to the non-F1 termination point host; wherein the IP address configuration information is carried by an IAB transmission migration management request message.
  • the first sending unit sends IP address request information for the non-F1 termination point topology domain of the IAB node to the non-F1 termination point host; wherein the IP address request information is carried by an IAB transmission migration management request message.
  • An IAB host device is a non-F1 termination point host device of an IAB node, characterized in that the device includes:
  • the second receiving unit receives the IP address request information for the non-F1 termination point topological domain of the IAB node sent by the F1 termination point host; and/or,
  • the second sending unit is configured to send IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node to the F1 termination point host.
  • IP address request information is carried by other IAB information messages (IABOtherInformation) or RRC reconfiguration messages (RRCReconfiguration) contained in the first RRC container.
  • IAB information messages IABOtherInformation
  • RRCReconfiguration RRC reconfiguration messages
  • the secondary node adds a response message
  • the device is the source host of the IAB node switching, the non-F1 termination point host is the target host of the IAB node switching, and the The second receiving unit receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host, and the second sending unit sends the IP address request information for the IAB node to the F1 termination point host.
  • IP address configuration information of the assigned non-F1 termination point topology domain wherein the first RRC container is carried by a handover request message, and the second RRC container is carried by a handover request response message.
  • the F1 termination point host is the primary node MN of the IAB node
  • the non-F1 termination point host is the secondary node SN of the IAB node
  • the The second receiving part receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the first RRC container is configured by a secondary node add request message or a secondary node modification request. Message bearer.
  • the second sending unit also sends IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node to the F1 termination point host, and the second RRC
  • the container is carried by a secondary node adding response message or a secondary node modifying response message.
  • the device 11 or 8 wherein the F1 termination point host is the primary node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the The second sending unit sends IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node to the F1 termination point host; wherein the second RRC container is carried by a secondary node modification requirement message.
  • the device wherein the non-F1 termination point host is the primary node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the The second receiving unit receives the IP address request information for the non-F1 termination point topological domain of the IAB node sent by the F1 termination point host; wherein the first RRC container is carried by a secondary node modification requirement message.
  • the device wherein the non-F1 termination point host is the primary node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the The second receiving unit receives the IP address configuration information for the F1 termination point topology domain allocated by the IAB node sent by the F1 termination point host; wherein the second RRC container is carried by a secondary node modification requirement message.
  • the second receiving unit receives the IP address request information for the non-F1 termination point topology domain of the IAB node sent by the F1 termination point host; wherein the first RRC container is carried by a UE context acquisition response message.
  • the IP address request information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • IP address configuration information is carried by an IAB transmission migration management response message or an IAB transmission migration modification request message.
  • the IP address configuration information includes a border node identifier; the border node identifier is used to indicate that the IAB node is a border node.
  • the device 19 The device according to appendix 15 or 17, wherein the F1 termination point host is the source host of the IAB node switching, the non-F1 termination point host is the target host of the IAB node switching, and the The second receiving unit receives the IP address request information sent by the F1 termination point host for the non-F1 termination point topology domain of the IAB node; wherein the IP address request information is carried by an IAB transmission migration management request message.
  • the device 20.
  • the F1 termination point host is the primary node MN of the IAB node
  • the non-F1 termination point host is the secondary node SN of the IAB node
  • the The second receiving unit receives the IP address request information sent by the F1 termination point host for the non-F1 termination point topology domain of the IAB node; wherein the IP address request information is carried by the IAB transmission migration management request message.
  • the second sending unit also sends IP address configuration information for the non-F1 termination point topology domain allocated by the IAB node to the F1 termination point host; wherein, the The above IP address configuration information is carried by the IAB transmission migration management response message.
  • the device according to appendix 15 or 17, wherein the F1 termination point host is the primary node MN of the IAB node, the non-F1 termination point host is the secondary node SN of the IAB node, and the The second sending unit sends the IP address configuration information for the non-F1 termination point topological domain allocated by the IAB node to the F1 termination point host; wherein the IP address configuration information is carried by the IAB transmission migration modification request message.
  • the device 22.
  • the non-F1 termination point host is the primary node MN of the IAB node
  • the F1 termination point host is the secondary node SN of the IAB node
  • the The second receiving unit receives the IP address request information sent by the F1 termination point host for the non-F1 termination point topology domain of the IAB node; wherein the IP address request information is carried by the IAB transmission migration management request message.
  • the device according to appendix 15 or 17, wherein the non-F1 termination point host is the primary node MN of the IAB node, the F1 termination point host is the secondary node SN of the IAB node, and the The second receiving unit receives the IP address configuration information for the F1 termination point topology domain allocated by the IAB node sent by the F1 termination point host; wherein the IP address configuration information is carried by the IAB transmission migration management request message.
  • the second receiving unit receives the IP address request information sent by the F1 termination point host for the non-F1 termination point topology domain of the IAB node; wherein the IP address request information is carried by an IAB transmission migration management request message.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供了一种IAB宿主设备以及传输地址配置方法。该IAB宿主设备包括：第一发送部，其向非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，向非F1终止点宿主发送针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；和/或，第一接收部，其接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息。

Description

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拓扑域的业务。针对non-F1-terminating拓扑域的routing ID，IAB节点需要使用non-F1-terminating拓扑域的IP地址，针对F1-terminating拓扑域的routing ID，IAB节点需要使用F1-terminating拓扑域的IP地址。网络需要给IAB节点配置锚定于non-F1-terminating拓扑域的donor-DU的IP地址，或锚定于F1-terminating拓扑域donor-DU的IP地址。但是，如何对非F1终止点拓扑域的IP地址进行请求，或如何对F1终止域和非F1终止域的IP地址进行配置，目前并没有相应的方案。
为了解决上述问题的至少之一，本申请实施例提供一种IAB宿主设备以及传输 地址配置方法。
根据本申请实施例的一方面，提供一种传输地址配置方法，应用于IAB节点的F1终止点宿主设备，所述方法包括：
所述F1终止点宿主向非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
所述F1终止点宿主接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；和/或，
所述F1终止点宿主向非F1终止点宿主发送针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息。
根据本申请实施例的另一方面，提供一种传输地址配置方法，应用于IAB节点的非F1终止点宿主设备，所述方法包括：
所述非F1终止点宿主接收F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
所述非F1终止点宿主向F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；和/或，
所述非F1终止点宿主接收F1终止点宿主发送的针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息。
根据本申请实施例的另一方面，提供一种IAB宿主设备，所述IAB宿主设备是IAB节点的F1终止点宿主设备，所述设备包括：
第一发送部，其向非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
向非F1终止点宿主发送针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；和/或，
第一接收部，其接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息。
根据本申请实施例的另一方面，提供一种IAB宿主设备，所述IAB宿主设备是IAB节点的非F1终止点宿主设备，所述设备包括：
第二接收部，其接收F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
接收F1终止点宿主发送的针对所述IAB节点分配的F1终止点拓扑域的IP地址 配置信息；和/或，
第二发送部，其向F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息。
根据本申请实施例的另一方面，提供一种种通信系统，所述系统包括：前述方面所述的IAB宿主设备。
本申请实施例的有益效果之一在于：F1终止点宿主可以请求非F1终止点宿主分配非F1终止点拓扑域的IP地址，或进一步的接收非F1终止点宿主针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，从而使F1终止点宿主可以请求非F1终止点拓扑域的IP地址，或进一步的为IAB节点发送非F1终止点拓扑域的IP地址，例如，当非F1终止点宿主无法给IAB节点发送消息的情况下。F1终止点宿主可以接收非F1终止点宿主主动发送的非F1终止点拓扑域的IP地址配置信息，以便为IAB节点发送非F1终止点拓扑域的IP地址，例如，当非F1终止点宿主无法向IAB节点发送消息的情况下。另外，F1终止点宿主可以向非F1终止点宿主发送F1终止点拓扑域的IP地址配置信息，从而使非F1终止点宿主可以向IAB节点发送F1终止点拓扑域的IP地址，例如，当F1终止点宿主无法向IAB节点发送消息的情况下。这样，针对非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是本申请实施例的传输地址配置方法的一示意图；
图17是双连接场景二示意图；
图18是本申请实施例的传输地址配置方法的一示意图；
图19是本申请实施例的传输地址配置方法的一示意图；
图20是RLF恢复场景示意图；
图21是本申请实施例的传输地址配置方法的一示意图；
图22是本申请实施例的传输地址配置方法的一示意图；
图23是本申请实施例的传输地址配置方法的一示意图；
图24是本申请实施例的传输地址配置方法的一示意图；
图25是本申请实施例的传输地址配置方法的一示意图；
图26是本申请实施例的传输地址配置方法的一示意图；
图27是本申请实施例的传输地址配置方法的一示意图；
图28是本申请实施例的传输地址配置方法的一示意图；
图29是本申请实施例的IAB宿主设备的一示意图；
图30是本申请实施例的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可以从源宿主(也可称为F1-terminating 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地址仍然属于donor-CU1拓扑域。
Boundary node的全部routing ID将属于non-F1-terminating拓扑域，或者，boundary node同时传输routing ID属于F1-terminating拓扑域和routing ID属于non-F1-terminating拓扑域的业务。针对non-F1-terminating拓扑域的routing ID，boundary node需要使用non-F1-terminating拓扑域的IP地址，针对F1-terminating拓扑域的routing ID，boundary node需要使用F1-terminating拓扑域的IP地址。网络需要给boundary node配置锚定于non-F1-terminating拓扑域的donor-DU的IP地址，或锚定于F1-terminating拓扑域donor-DU的IP地址。但是，如何对非F1终止点拓扑域的IP地址进行请求，或如何对F1终止域和非F1终止域的IP地址进行配置，目前并 没有相应的方案。
在本申请实施例中，在没有特别说明的情况下，IAB节点设备包括迁移节点。此外，“donor-CU的拓扑域中已建立用于服务IAB节点的业务的资源”也可称为“IAB节点的业务迁移到donor-CU的拓扑域中”等，本申请不限于这些表述。以下对本申请实施例进行进一步说明。
第一方面的实施例
本申请实施例提供一种传输地址配置方法，从IAB节点的F1终止点宿主设备侧进行说明。
图10是本申请实施例的传输地址配置方法的一示意图。如图10所示，该方法包括：
1001，该F1终止点宿主向非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
该F1终止点宿主接收该非F1终止点宿主发送的针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息；和/或，
该F1终止点宿主向非F1终止点宿主发送针对该IAB节点分配的F1终止点拓扑域的IP地址配置信息。
值得注意的是，以上附图10仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图10的记载。
由上述实施例可知，F1终止点宿主可以请求非F1终止点宿主分配非F1终止点拓扑域的IP地址，或进一步的接收非F1终止点宿主针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，从而使F1终止点宿主可以请求非F1终止点拓扑域的IP地址，或进一步的为IAB节点发送非F1终止点拓扑域的IP地址，例如，当非F1终止点宿主无法给IAB节点发送消息的情况下。F1终止点宿主可以接收非F1终止点宿主主动发送的非F1终止点拓扑域的IP地址配置信息，以便为IAB节点发送非F1终止点拓扑域的IP地址，例如，当非F1终止点宿主无法向IAB节点发送消息的情况下。另外，F1终止点宿主可以向非F1终止点宿主发送F1终止点拓扑域的IP地址配置信息，从而使非F1终止点宿主可以向IAB节点发送F1终止点拓扑域的IP 地址，例如，当F1终止点宿主无法向IAB节点发送消息的情况下。这样，针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址，针对F1终止点拓扑域的routing ID，可以使用F1终止点拓扑域的IP地址。
在一些实施例中，IAB节点包括迁移节点(也称为边界节点)，该IAB节点的F1连接终止于F1终止点宿主，该IAB节点与该非F1终止点宿主有RRC连接。例如IAB节点的IAB-MT与非F1终止点宿主保持RRC连接，该F1终止点宿主设备可以是第一IAB donor-CU(宿主集中单元)，该非F1终止点宿主设备可以是第二IAB donor-CU(宿主集中单元)，F1终止点宿主设备指对边界IAB节点和其子IAB节点的F1接口终止的donor-CU，比如第一IAB donor-CU。非F1终止点宿主设备指没有对边界IAB节点和其子IAB节点的F1接口终止的具有宿主功能的CU，比如第二IAB donor-CU。
在一些实施例中，该请求和/或配置的IP地址是指为该IAB节点配置的(或者说针对该IAB节点的)锚定于donor-DU的IP地址，该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)地址。
在一些实施例中，上述IP地址请求信息和/或IP地址配置信息可以由RRC容器承载，或者也可以由IAB传输迁移管理请求/响应或者由IAB传输迁移修改请求承载，以下分别进行说明。
(一)IP地址请求信息和/或IP地址配置信息由RRC容器承载
在一些实施例中，IP地址请求信息由第一RRC容器承载，例如所述IP地址请求信息由所述第一RRC容器中包含的其他IAB信息消息(信元结构IABOtherInformation)或RRC重配置消息承载，该第一RRC容器包括该IAB节点在F1终止点拓扑域中的IP地址配置信息。该IABOtherInformation消息是IAB节点用 于向网络请求IP地址，以及汇报实际使用或网络已为IAB节点分配的IP地址的RRC消息。在本实施例中，由F1终止点宿主模拟IAB节点产生IABOtherInformation消息，并将其包含在第一RRC容器中发送给非F1终止点宿主，以代替IAB节点请求非F1拓扑域的IP地址。该RRC重配置消息是网络向IAB节点配置IP地址的RRC消息。在本实施例中，由F1终止点宿主产生RRC重配置消息，并将其包含在第一RRC容器中发送给非F1终止点宿主，以请求非F1拓扑域的IP地址。
在一些实施例中，IP地址配置信息由第二RRC容器承载，例如所述IP地址配置信息由所述第二RRC容器中包含的RRC重配置消息(RRCReconfiguration)承载。
由于现有的RRC消息(例如IABOtherInformation)是IAB节点用来向宿主请求IP地址的RRC消息，RRC重配置消息(RRCReconfiguration)消息是用来为IAB节点配置IP地址的RRC消息，因此，可以重用RRC消息(例如IABOtherInformation)承载针对边界节点的IP地址请求信息，以及重用RRC重配置消息(RRCReconfiguration)承载针对边界节点的IP地址配置信息，使得IP地址的请求和配置更加简单和灵活。
在一些实施例中，可以使用现有Xn过程(可以由Xn接口应用协议(XnAP)信令承载)，例如切换准备、双连接建立或修改过程、UE上下文获取过程等请求和/或配置上述IP地址。例如第一RRC容器由以下至少一种消息承载：切换请求消息；辅节点添加请求消息；辅节点修改请求消息；辅节点修改需求消息；UE上下文获取响应消息。所述第二RRC容器由以下至少一种消息承载：切换请求响应消息；辅节点添加响应消息；辅节点修改响应消息；辅节点修改需求消息。以下结合不同的场景进行说明。另外，由于这些Xn过程是针对边界节点的过程，因此能自然与针对子节点的IP地址请求、配置信息区分开，使得宿主可以使用与边界节点的RRC连接为边界节点发送IP地址配置。
I.针对切换场景
在一些实施例中，图11是切换场景示意图，如图11所示，在切换场景中，边界节点的全部业务迁移至非F1终止点拓扑域，F1终止点宿主是该IAB节点切换的源宿主，该非F1终止点宿主是该IAB节点切换的目标宿主，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址，图12是该切换场景下传输地址配置方法示意图，如图12所示，该方法包括：
1201，该F1终止点宿主向该非F1终止点宿主发送针对该IAB节点的非F1终止 点拓扑域的IP地址请求信息；
1202，该F1终止点宿主接收该非F1终止点宿主发送的针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息；
在一些实施例中，该IP地址请求信息由第一RRC容器承载，该IP地址配置信息由第二RRC容器承载，该第一RRC容器由切换请求消息承载，该第二RRC容器由切换请求响应消息承载。因此，F1终止点宿主向非F1终止点宿主发送切换请求消息(HANDOVER REQUEST)，例如，该切换请求消息中包含RRC消息HandoverPreparationInformation，可以在HandoverPreparationInformation中引入F1终止点宿主产生的整个RRC消息IABOtherInformation，该IABOtherInformation作为第一RRC容器承载非F1终止点拓扑域的IP地址请求信息(IAB-TNLAddressInfo域)，该IABOtherInformation还可以包括边界节点在F1终止点拓扑域中的IP地址配置信息。非F1终止点宿主向F1终止点宿主回复切换请求响应(HANDOVER REQUEST ACKNOWLEDGE)，例如该切换请求响应中包含RRC消息HandoverCommand，该HandoverCommand里承载由非F1终止点宿主产生的整个RRC消息RRCReconfiguration,RRCReconfiguration作为第二RRC容器承载非F1终止点拓扑域的IP地址配置信息(iab-IP-AddressConfigurationList-r16域)。
该HandoverPreparationInformation使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086454-appb-000001
该IABOtherInformation使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086454-appb-000002
Figure PCTCN2022086454-appb-000003
IABOtherInformation还可以承载对各种业务请求的IP地址个数或各种业务实际采用的IP地址。
该HandoverCommand使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086454-appb-000004
该RRCReconfiguration使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086454-appb-000005
在一些实施例中，该RRCReconfiguration承载非F1终止点拓扑域的IP地址配置信息IAB-IP-AddressConfigurationList-r16，包括IP地址增加和修改列表以及IP地址 释放列表，每个列表包括至少一个IP地址配置IAB-IP-AddressConfiguration-r16，每一个IP地址配置可以包括IP地址索引以及对应的IP地址。
因此，可以通过在切换请求消息中引入新的RRC容器IABOtherInformation，用于请求非F1终止点拓扑域的IP地址，并利用切换请求响应消息中的RRC容器RRCReconfiguration包含的IP地址配置信息元承载针对边界节点的非F1终止点拓扑域的IP地址。
以上是对IP地址请求信息由第一RRC容器包含的IABOtherInformatio承载的示例，除此之外，IP地址请求信息还可以由第一RRC容器包含的RRC重配置消息承载，本发明实施例不做限制。
在一些实施例中，该方法还可以包括：
1203，该F1终止点宿主向该IAB节点发送接收到的该IP地址配置信息；例如该F1终止点宿主转发非F1终止点宿主产生的HandoverCommand，该HandoverCommand里承载由非F1终止点宿主产生的整个RRC消息RRCReconfiguration,RRCReconfiguration承载非F1终止点拓扑域的IP地址配置信息。
由上述实施例可知，F1终止点宿主可以请求非F1终止点宿主分配非F1终止点拓扑域的IP地址，或进一步的接收非F1终止点宿主针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，从而使F1终止点宿主可以请求非F1终止点拓扑域的IP地址，或当非F1终止点宿主无法给IAB节点发送消息的情况下进一步的为IAB节点发送非F1终止点拓扑域的IP地址。这样针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址。
II.针对双连接场景一
在一些实施例中，图13是双连接场景一示意图，如图13所示，在双连接场景一中，F1终止点宿主是该IAB节点的主节点MN，该非F1终止点宿主是该IAB节点的辅节点SN，建立双连接后，可将边界节点的部分业务迁移至非F1终止点拓扑域，部分业务仍然在F1终止点宿主拓扑域，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。可以在双连接建立过程中请求非F1终止点拓扑域的IP地址，或者双连接建立完成后请求/配置非F1终止点拓扑域的IP地址或者F1终止点拓扑域的IP地址，以下分别说明。
图14是该双连接场景一下传输地址配置一种方法示意图，如图14所示，该方法包括：
1401，该F1终止点宿主向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息；
1402，该F1终止点宿主接收该非F1终止点宿主发送的针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息。
在一些实施例中，在添加辅小区组的过程中请求非F1终止点拓扑域的IP地址，该IP地址请求信息由第一RRC容器承载，该IP地址配置信息由第二RRC容器承载，该第一RRC容器由辅节点添加请求消息承载，该第二RRC容器由辅节点添加响应消息承载。增加Secondary Cell Group过程中，F1终止点宿主向非F1终止点宿主发送辅节点添加请求消息(S-node AdditionRequest)，例如在其中包含的RRC消息CG-ConfigInfo中引入F1终止点宿主产生的整个RRC消息IABOtherInformation，该IABOtherInformation作为第一RRC容器承载非F1终止点拓扑域的IP地址请求信息(IAB-TNLAddressInfo域)。非F1终止点宿主向F1终止点宿主回复辅节点添加响应消息(S-node Addition Response)，在其中包含的RRC消息CG-Config中的辅小区组配置信息域scg-CellGroupConfig承载非F1终止点宿主产生的整个RRC消息RRCReconfiguration。在SN没有建立SRB3的情况下(这种情况下SN无法直接向IAB节点发送RRC消息)，RRCReconfiguration作为第二RRC容器承载非F1终止点拓扑域的IP地址配置信息(iab-IP-AddressConfigurationList-r16域)。
图15是该双连接场景一下传输地址配置一种方法示意图，如图15所示，该方法包括：
1501，该F1终止点宿主向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息；
1502，该F1终止点宿主接收该非F1终止点宿主发送的针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息。
在一些实施例中，在双连接建立完成后，在修改辅小区组的过程中请求非F1终止点拓扑域的IP地址，该IP地址请求信息由第一RRC容器承载，该IP地址配置信息由第二RRC容器承载，该第一RRC容器由辅节点修改请求消息承载，该第二RRC容器由辅节点修改响应消息承载。修改Secondary Cell Group过程中，F1终止点宿主向非F1终止点宿主发送辅节点修改请求消息(S-node Modification Request)，例如在其中包含的RRC消息CG-ConfigInfo中引入F1终止点宿主产生的整个RRC消息IABOtherInformation，该IABOtherInformation作为第一RRC容器承载非F1终止点拓 扑域的IP地址请求信息(IAB-TNLAddressInfo域)，非F1终止点宿主向F1终止点宿主回复辅节点修改响应消息(S-node Modification Response)，在其中包含的RRC消息CG-Config中的辅小区组配置信息(scg-CellGroupConfig域)承载非F1终止点宿主产生的整个RRC消息RRCReconfiguration。在SN没有建立SRB3的情况下，RRCReconfiguration作为第二RRC容器承载非F1终止点拓扑域的IP地址配置信息(iab-IP-AddressConfigurationList-r16域)。
该CG-ConfigInfo使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086454-appb-000006
该CG-Config使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086454-appb-000007
该RRCReconfiguration使用抽象语法标记ASN.1数据格式的表示如前所述，此处不再重复。
因此，可以通过在辅节点添加/修改请求消息中引入新的RRC容器IABOtherInformation，用于请求非F1终止点拓扑域的IP地址，并利用辅节点添加/修改响应消息中的RRC容器RRCReonfiguration包含的IP地址配置信息元承载针对边界节点配置的非F1终止点拓扑域的IP地址。
以上是对IP地址请求信息由第一RRC容器包含的IABOtherInformatio承载的示例，除此之外，IP地址请求信息还可以由第一RRC容器包含的RRC重配置消息承载，本发明实施例不做限制。
在一些实施例中，在SN没有建立SRB3的情况下，该方法还可以包括：
1403/1503，该F1终止点宿主向该IAB节点发送接收到的该IP地址配置信息；例如该F1终止点宿主转发非F1终止点宿主产生的CG-Config中的RRCReconfiguration，该RRCReconfiguration承载非F1终止点拓扑域的IP地址配置信息。
在1503中，可选的，SN建立SRB3的情况下，还可以由非F1终止点宿主向该IAB节点发送该IP地址配置信息，本申请实施例并不以此作为限制。
由上述实施例可知，F1终止点宿主可以请求非F1终止点宿主分配非F1终止点拓扑域的IP地址，或进一步的接收非F1终止点宿主针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，从而使F1终止点宿主可以请求非F1终止点拓扑域的IP地址，或当非F1终止点宿主无法给IAB节点发送消息的情况下进一步的为IAB节点发送非F1终止点拓扑域的IP地址。这样针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址。
图16是该双连接场景一下传输地址配置又一种方法示意图，如图16所示，该方法包括：
1601，该F1终止点宿主接收该非F1终止点宿主发送的针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该第二RRC容器由辅节点修改需求消息承载。
在一些实施例中，与附图15中的不同之处在于，在双连接建立完成后，在SN没有建立SRB3的情况下，不需要F1终止点宿主主动请求非F1终止点拓扑域的IP地址，该非F1终止点宿主可以主动发起针对非F1终止点拓扑域的IP地址重配置，该IP地址配置信息由第二RRC容器承载，该第二RRC容器由辅节点修改需求消息承载。
例如，在修改辅小区组的过程中，非F1终止点宿主向F1终止点宿主发送辅节点修改需求消息(S-node Modification Required)，例如在其中包含的RRC消息CG-Config中的辅小区组配置信息(scg-CellGroupConfig域)承载非F1终止点宿主产生的整个RRC消息RRCReconfiguration,RRCReconfiguration作为第二RRC容器承载非F1终止点拓扑域的IP地址配置信息，也称作IP地址重配置信息。
因此，可以通过在辅节点修改需求消息中的RRC容器RRCReconfiguration包含的IP地址配置信息元承载针对边界节点重配置的非F1终止点拓扑域的IP地址。
在一些实施例中，在SN没有建立SRB3的情况下，该方法还可以包括：
1602，该F1终止点宿主向该IAB节点转发接收到的该IP地址配置信息；例如该F1终止点宿主转发非F1终止点宿主产生的CG-Config中的RRCReconfiguration，该RRCReconfiguration承载非F1终止点拓扑域的IP地址配置信息。
由上述实施例可知，F1终止点宿主可以接收非F1终止点宿主主动发送的非F1终止点拓扑域的IP地址配置信息，以便当非F1终止点宿主无法给IAB节点发送消息的情况下为IAB节点发送非F1终止点拓扑域的IP地址。这样针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址。
III.针对双连接场景二
在一些实施例中，图17是双连接场景二示意图，如图17所示，在双连接场景二中，F1终止点宿主是该IAB节点的主节点SN CU，该非F1终止点宿主是该IAB节点的辅节点MN CU，建立双连接后，可将边界节点的部分业务迁移至非F1终止点拓扑域，部分业务仍然在F1终止点宿主拓扑域，非F1终止点拓扑域的IP地址是指锚定于donor-DU1的IP地址，F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。由于F1连接是在建立双连接后完成的，因此，与双连接场景一不同的是，不可以在双连接建立过程中请求非F1终止点拓扑域的IP地址，仅可以在双连接建立完成后请求/配置非F1终止点拓扑域的IP地址或者F1终止点拓扑域的IP地址，以下分别说明。
图18是该双连接场景二下传输地址配置一种方法示意图，如图18所示，该方法包括：
1801，该F1终止点宿主向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息；
在一些实施例中，在双连接建立完成后，在修改辅小区组的过程中请求非F1终 止点拓扑域的IP地址，该IP地址请求信息由第一RRC容器承载，该第一RRC容器由辅节点修改需求消息承载。F1终止点宿主向非F1终止点宿主发送辅节点修改需求消息，例如在其中包含的RRC消息CG-Config中引入IP地址请求信息(IAB-TNLAddressInfo域)承载F1终止点宿主产生的整个RRC消息IABOtherInformation，该IABOtherInformation作为第一RRC容器承载非F1终止点拓扑域的IP地址请求信息。由于非F1终止点宿主配置的IP地址可以直接由非F1终止点宿主通过SRB1发送给边界节点，因此，非F1终止点宿主不需要向F1终止点宿主回复该IP地址配置信息，换句话说，F1终止点宿主不会接收到非F1终止点宿主发送的IP地址配置信息。
该CG-Config使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086454-appb-000008
因此，可以通过在辅节点修改需求消息中引入新的RRC容器IABOtherInformation，用于请求非F1终止点拓扑域的IP地址。
以上是对IP地址请求信息由第一RRC容器包含的IABOtherInformatio承载的示例，除此之外，IP地址请求信息还可以由第一RRC容器包含的RRC重配置消息承载，本发明实施例不做限制。
在一些实施例中，该方法还可以包括：
1802，该非F1终止点宿主向该IAB节点发送IP地址配置信息；例如非F1终止点宿主产生RRCReconfiguration，该RRCReconfiguration承载非F1终止点拓扑域的IP地址配置信息。
由上述实施例可知，F1终止点宿主可以请求非F1终止点宿主分配非F1终止点拓扑域的IP地址，从而使F1终止点宿主请求非F1终止点拓扑域的IP地址并由非F1终止点宿主将非F1终止点拓扑域的IP地址发送给IAB节点。这样针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址。
图19是该双连接场景二下传输地址配置又一种方法示意图，如图19所示，该方 法包括：
1901，该F1终止点宿主向该非F1终止点宿主发送针对该IAB节点分配的F1终止点拓扑域的IP地址配置信息，该第二RRC容器由辅节点修改需求消息承载。
在一些实施例中，在双连接建立完成后，在SN没有建立SRB3的情况下，该F1终止点宿主可以主动发起针对F1终止点拓扑域的IP地址重配置，该IP地址配置信息由第二RRC容器承载，该第二RRC容器由辅节点修改需求消息承载。
例如，在修改辅小区组的过程中，F1终止点宿主向非F1终止点宿主发送辅节点修改需求消息(S-node Modification Required)，例如在其中包含的RRC消息CG-Config中的辅小区配置信息(scg-CellGroupConfig域)承载F1终止点宿主产生的整个RRC消息RRCReconfiguration,RRCReconfiguration作为第二RRC容器承载F1终止点拓扑域的IP地址配置信息，也称作IP地址重配置信息。
该CG-Config使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086454-appb-000009
因此，可以通过在辅节点修改需求消息中现有的IP地址配置信息元指示针对边界节点重配置的F1终止点拓扑域的IP地址。
在一些实施例中，在SN没有建立SRB3的情况下，该方法还可以包括：
1902，该非F1终止点宿主向该IAB节点转发接收到的F1终止点拓扑域的IP地址配置信息；例如该非F1终止点宿主转发F1终止点宿主产生的CG-Config中的RRCReconfiguration，该RRCReconfiguration承载F1终止点拓扑域的IP地址配置信息。
由上述实施例可知，F1终止点宿主可以向非F1终止点宿主发送F1终止点拓扑域的IP地址配置信息，从而当F1终止点宿主无法向IAB节点发送消息的情况下使 非F1终止点宿主可以向IAB节点发送F1终止点拓扑域的IP地址。这样针对F1终止点拓扑域的routing ID，IAB节点可以使用F1终止点拓扑域的IP地址。
IV.针对RLF恢复场景
在一些实施例中，图20是RLF恢复场景示意图，如图20所示，在RLF恢复场景中，该F1终止点宿主是RLF恢复后该IAB节点的宿主(旧宿主CU)，该非F1终止点宿主是RLF恢复前该IAB节点的宿主(新宿主CU)，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址，图21是该切换场景下传输地址配置方法示意图，如图21所示，该方法包括：
2101，该F1终止点宿主向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息；
在一些实施例中，在UE上下文获取过程中请求非F1终止点拓扑域的IP地址，该IP地址请求信息由第一RRC容器承载，该第一RRC容器由UE上下文获取响应消息承载。因此，非F1终止点宿主向F1终止点宿主发UE上下文获取请求消息(RETRIEVE UE CONTEXT REQUEST)，F1终止点宿主向非F1终止点宿主回复UE上下文获取响应消息(RETRIEVE UE CONTEXT RESPONSE)，例如，该UE上下文获取响应消息中包含RRC消息HandoverPreparationInformation，可以在HandoverPreparationInformation中引入F1终止点宿主产生的整个RRC消息IABOtherInformation，该IABOtherInformation作为第一RRC容器承载非F1终止点拓扑域的IP地址请求信息(IAB-TNLAddressInfo域)，该IABOtherInformation还可以包括边界节点在F1终止点拓扑域中的IP地址配置信息。由于边界节点重建立到非F1终止点宿主之后，IP地址配置信息只能由非F1终止点宿主发送，因此非F1终止点宿主不需要向F1终止点宿主回复该IP地址配置信息，换句话说，F1终止点宿主不会接收到非F1终止点宿主发送的IP地址配置信息。
因此，可以通过在UE上下文获取响应消息中引入新的RRC容器IABOtherInformation，用于请求非F1终止点拓扑域的IP地址。
以上是对IP地址请求信息由第一RRC容器包含的IABOtherInformatio承载的示例，除此之外，IP地址请求信息还可以由第一RRC容器包含的RRC重配置消息承载，本发明实施例不做限制。
在一些实施例中，该方法还可以包括：
2102，该非F1终止点宿主向该IAB节点发送IP地址配置信息；例如非F1终止 点宿主产生RRCReconfiguration，该RRCReconfiguration承载非F1终止点拓扑域的IP地址配置信息。
由上述实施例可知，F1终止点宿主可以请求非F1终止点宿主分配非F1终止点拓扑域的IP地址，从而使F1终止点宿主请求非F1终止点拓扑域的IP地址并由非F1终止点宿主将非F1终止点拓扑域的IP地址发送给IAB节点。这样针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址。
(二)IP地址请求信息和/或IP地址配置信息由IAB传输迁移管理请求/响应或者由IAB传输迁移修改请求承载
在一些实施例中，IP地址请求信息由IAB传输迁移管理请求消息承载，该IP地址请求信息中还包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点，也就是说指示针对边界节点的IP地址请求信息；该IP地址配置信息由IAB传输迁移管理响应消息或IAB传输迁移修改请求消息承载，该IP地址配置信息中包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点，也就是说指示针对边界节点配置的IP地址配置信息。
由于IAB传输迁移管理请求/响应或者由IAB传输迁移修改请求是IAB节点专用的，不涉及AS层的配置，由此，通过IAB传输迁移管理请求/响应或者由IAB传输迁移修改请求请求以及配置非F1终止点拓扑域的IP地址，可以使得IP地址的请求和配置更加简单和灵活。
I.针对切换场景
在一些实施例中，如图11所示，在切换场景中，边界节点的全部业务迁移至非F1终止点拓扑域，F1终止点宿主是该IAB节点切换的源宿主，该非F1终止点宿主是该IAB节点切换的目标宿主，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址，图22是该切换场景下传输地址配置方法示意图，如图22所示，该方法包括：
2201，该F1终止点宿主向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息；
在一些实施例中，该IP地址请求信息由IAB传输迁移管理请求消息(IAB TRANSPORT MIGRATION MANAGEMENT REQUEST)承载。因此，在切换准备后，F1终止点宿主向非F1终止点宿主发送IAB传输迁移管理请求消息，例如，可以在IAB传输迁移管理请求消息中承载非F1终止点拓扑域的IP地址请求信息IAB TNL  ADDRESS REQUEST，该IP地址请求信息中还包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点，也就是指示该IP地址请求信息是针对边界节点的非F1终止点拓扑域的IP地址请求信息。
该IAB TNL ADDRESS REQUEST使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086454-appb-000010
其中，IAB TNL ADDRESS REQUEST包含针对IPv4或IPv6地址的请求信息IAB TNL Addresses Requested域和边界节点标识Boundary Node域。
IAB TNL Addresses Requested的数据格式可以表示为：
Figure PCTCN2022086454-appb-000011
其中，IAB TNL Addresses Requested包含对各种业务的IP地址个数的请求。
由于切换后RRC消息只能由目标宿主发送给边界节点，因此，非F1终止点宿主不需要回复F1终止点宿主该非F1终止点拓扑域的IP地址配置信息。
因此，可以通过在IAB传输迁移管理请求消息中引入新的信息元IAB TNL ADDRESS REQUEST，用于请求针对边界节点的非F1终止点拓扑域的IP地址。
在一些实施例中，该方法还可以包括：
2202，该非F1终止点宿主向该IAB节点发送IP地址配置信息；例如非F1终止点宿主产生整个RRC消息RRCReconfiguration,RRCReconfiguration承载非F1终止点拓扑域的IP地址配置信息，并发送给边界节点。RRCReconfiguration使用抽象语法标记ASN.1数据格式的表示如前所述，此处不再重复。
在一些实施例中，该RRCReconfiguration承载非F1终止点拓扑域的IP地址配置信息IAB-IP-AddressConfigurationList-r16包括至少一个IP地址配置IAB-IP-AddressConfiguration-r16，每一个IP地址配置可以包括IP地址索引以及对应的IP地址。
由上述实施例可知，F1终止点宿主可以请求非F1终止点宿主分配非F1终止点拓扑域的IP地址，从而使F1终止点宿主请求非F1终止点拓扑域的IP地址并由非F1终止点宿主将非F1终止点拓扑域的IP地址发送给IAB节点。这样针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址。
II.针对双连接场景一
在一些实施例中如图13所示，在双连接场景一中，F1终止点宿主是该IAB节点的主节点MN，该非F1终止点宿主是该IAB节点的辅节点SN，建立双连接后，可将边界节点的部分业务迁移至非F1终止点拓扑域，部分业务仍然在F1终止点宿主拓扑域，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。
图23是该双连接场景一下传输地址配置一种方法示意图，如图23所示，该方法包括：
2301，该F1终止点宿主向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息；
2302，该F1终止点宿主接收该非F1终止点宿主发送的针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息。
在一些实施例中，在添加辅小区组的过程后请求非F1终止点拓扑域的IP地址，该IP地址请求信息由IAB传输迁移管理请求消息承载，该IP地址配置信息由IAB传输迁移管理响应消息承载。例如在IAB传输迁移管理请求消息中引入非F1终止点拓扑域的IP地址请求信息IAB TNL ADDRESS REQUEST，该IP地址请求信息中还包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点，也就是指示该IP地址请求信息是针对边界节点的非F1终止点拓扑域的IP地址请求信息，在SN没有建立SRB3的情况下，非F1终止点宿主向F1终止点宿主回复IAB传输迁移管 理响应消息，例如在其中承载非F1终止点拓扑域的IP地址配置信息(信元结构IAB TNL Address Response)，该IP地址配置信息中还可以包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点，也就是指示该IP地址配置信息是针对边界节点的非F1终止点拓扑域的IP地址配置信息。
该IAB TNL Address Response使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2022086454-appb-000012
其中，包含分配的至少一个非F1终止点拓扑域的IP地址配置IAB Allocated TNL Address List域和边界节点标识Boundary Node域，每个IP地址配置包括具体的IP地址IAB TNL Address以及相应的donor-DU地址Associated Donor DU Address。
因此，可以通过在传输迁移管理请求消息中引入新的信息元IP地址请求信息IAB TNL ADDRESS REQUEST，用于请求非F1终止点拓扑域的IP地址，并利用IAB传输迁移管理响应消息中的信息元IAB TNL Address Response指示针对边界节点(而非子节点)配置的非F1终止点拓扑域的IP地址。
在一些实施例中，在SN没有建立SRB3的情况下，该方法还可以包括：
2303，该F1终止点宿主向该IAB节点发送接收到的该IP地址配置信息；例如非F1终止点宿主产生整个RRC消息RRCReconfiguration,RRCReconfiguration承载非F1终止点拓扑域的IP地址配置信息，并发送给边界节点。RRCReconfiguration使用抽象语法标记ASN.1数据格式的表示如前所述，此处不再重复。
在2303中，可选的，在SN建立SRB3的情况下，还可以由非F1终止点宿主向该IAB节点发送该IP地址配置信息，本申请实施例并不以此作为限制。由上述实施例可知，F1终止点宿主需要向非F1终止点宿主请求IP地址，非F1终止点宿主针对该请求配置并回复F1终止点宿主该非F1终止点拓扑域的IP地址，再由F1终止点宿主转发给边界节点，这样针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址。
图24是该双连接场景一下传输地址配置一种方法示意图，如图24所示，该方法包括：
2401，该F1终止点宿主接收该非F1终止点宿主发送的针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息。
在一些实施例中，与附图23中的不同之处在于，在SN没有建立SRB3的情况下，不需要F1终止点宿主主动请求非F1终止点拓扑域的IP地址，该非F1终止点宿主可以主动发起针对非F1终止点拓扑域的IP地址重配置，该IP地址配置信息由IAB传输迁移修改请求消息(IAB TRANSPORT MODIFIATION REQUEST)承载。
例如，在辅节点添加过程之后，在SN没有建立SRB3的情况下，非F1终止点宿主向F1终止点宿主发送IAB传输迁移修改请求消息，例如在其中承载非F1终止点拓扑域的IP地址配置信息(信元结构IAB TNL Address Response，具体数据格式如前所述，此处不再赘述)，也称作IP地址重配置信息，该IP地址配置信息中还包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点，也就是指示该IP地址配置信息是针对边界节点的非F1终止点拓扑域的IP地址重配置信息。因此，可以通过在IAB传输迁移修改请求消息中的信息元IAB TNL Address Response指示针对边界节点(而非子节点)重配置的非F1终止点拓扑域的IP地址。
在一些实施例中，在SN没有建立SRB3的情况下，该方法还可以包括
2402，该F1终止点宿主向该IAB节点转发接收到的该IP地址配置信息；例如该F1终止点宿主转发非F1终止点宿主产生的RRCReconfiguration，该RRCReconfiguration承载非F1终止点拓扑域的IP地址配置信息。
由上述实施例可知，F1终止点宿主可以接收非F1终止点宿主主动发送的非F1终止点拓扑域的IP地址配置信息，以便当非F1终止点宿主无法给IAB节点发送消息的情况下为IAB节点发送非F1终止点拓扑域的IP地址。这样针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址。
III.针对双连接场景二
在一些实施例中，如图17所示，在双连接场景二中，F1终止点宿主是该IAB节点的主节点SN CU，该非F1终止点宿主是该IAB节点的辅节点MN CU，建立双连接后，可将边界节点的部分业务迁移至非F1终止点拓扑域，部分业务仍然在F1终止点宿主拓扑域，非F1终止点拓扑域的IP地址是指锚定于donor-DU1的IP地址，F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址。可以在双连接建立完成后 请求/配置非F1终止点拓扑域的IP地址或者F1终止点拓扑域的IP地址，以下分别说明。
图25是该双连接场景二下传输地址配置一种方法示意图，如图25所示，该方法包括：
2501，该F1终止点宿主向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息；
在一些实施例中，在双连接建立完成后请求非F1终止点拓扑域的IP地址，该IP地址请求信息由IAB传输迁移管理请求消息(IAB TRANSPORT MIGRATION MANAGEMENT REQUEST)承载。F1终止点宿主向非F1终止点宿主发送IAB传输迁移管理请求消息，例如在其中引入非F1终止点拓扑域的IP地址请求信息IAB TNL ADDRESS REQUEST(具体数据格式如前所述，此处不再赘述)，该IP地址请求信息中还包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点，也就是指示该IP地址请求信息是针对边界节点的非F1终止点拓扑域的IP地址请求信息，由于非F1终止点宿主配置的IP地址可以直接由非F1终止点宿主通过SRB1发送给边界节点，因此，非F1终止点宿主不需要向F1终止点宿主回复该IP地址配置信息，换句话说，F1终止点宿主不会接收到非F1终止点宿主发送的IP地址配置信息。
因此，可以通过在IAB传输迁移管理请求消息中引入新的信息元IAB TNL ADDRESS REQUEST，用于请求非F1终止点拓扑域的IP地址。
在一些实施例中，该方法还可以包括：
2502，该非F1终止点宿主向该IAB节点发送IP地址配置信息；例如非F1终止点宿主产生RRCReconfiguration，该RRCReconfiguration承载非F1终止点拓扑域的IP地址配置信息IAB TNL ADDRESS，该IP地址配置信息中还包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点，也就是指示该IP地址配置信息是针对边界节点的非F1终止点拓扑域的IP地址配置信息。
由上述实施例可知，F1终止点宿主可以请求非F1终止点宿主分配非F1终止点拓扑域的IP地址，从而使F1终止点宿主请求非F1终止点拓扑域的IP地址并由非F1终止点宿主将非F1终止点拓扑域的IP地址发送给IAB节点。这样针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址。
图26是该双连接场景二下传输地址配置又一种方法示意图，如图26所示，该方法包括：
2601，该F1终止点宿主向该非F1终止点宿主发送针对该IAB节点分配的F1终止点拓扑域的IP地址配置信息。
在一些实施例中，在双连接建立完成后，在SN没有建立SRB3的情况下，F1终止点宿主不需要请求非F1终止点拓扑域的IP地址，该F1终止点宿主可以主动发起针对F1终止点拓扑域的IP地址重配置，该IP地址配置信息由IAB传输迁移管理请求消息承载，该IP地址配置信息中还包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点，也就是指示该IP地址配置信息是针对边界节点的非F1终止点拓扑域的IP地址配置信息。
例如，F1终止点宿主向非F1终止点宿主发送IAB传输迁移管理请求消息，例如在其中承载F1终止点拓扑域的IP地址配置信息(信元结构IAB TNL Address Response)，该IP地址配置信息中还包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点，也就是指示该IP地址配置信息是针对边界节点的非F1终止点拓扑域的IP地址配置信息，也称作IP地址重配置信息。IAB TNL Address Response使用的抽象语法示例如上所述，此处不再赘述。
因此，可以通过在IAB传输迁移管理请求消息中引入新的信息元IAB TNL Address Response指示针对边界节点(而非子节点)重配置的F1终止点拓扑域的IP地址。
在一些实施例中，在SN没有建立SRB3的情况下，该方法还可以包括：
2602，该非F1终止点宿主向该IAB节点转发接收到的F1终止点拓扑域的IP地址配置信息；例如该非F1终止点宿主产生RRCReconfiguration，该RRCReconfiguration承载F1终止点拓扑域的IP地址配置信息。
由上述实施例可知，F1终止点宿主可以向非F1终止点宿主发送F1终止点拓扑域的IP地址配置信息，从而当F1终止点宿主无法向IAB节点发送消息的情况下使非F1终止点宿主可以向IAB节点发送F1终止点拓扑域的IP地址。这样针对F1终止点拓扑域的routing ID，IAB节点可以使用F1终止点拓扑域的IP地址。
IV.针对RLF恢复场景
在一些实施例中，如图20所示，在RLF恢复场景中，该F1终止点宿主是RLF恢复后该IAB节点的宿主(旧宿主CU)，该非F1终止点宿主是RLF恢复前该IAB节点的宿主(新宿主CU)，非F1终止点拓扑域的IP地址是指锚定于donor-DU2的IP地址，图27是该切换场景下传输地址配置方法示意图，如图27所示，该方法包 括：
2701，该F1终止点宿主向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息；
在一些实施例中，在UE上下文获取响应消息发送后，请求非F1终止点拓扑域的IP地址，该IP地址请求信息由IAB传输迁移管理请求消息承载。因此，F1终止点宿主向非F1终止点宿主发送IAB传输迁移管理请求消息，例如，在其中引入非F1终止点拓扑域的IP地址请求信息IAB TNL ADDRESS REQUEST，该IP地址请求信息中还包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点，也就是指示该IP地址请求信息是针对边界节点的非F1终止点拓扑域的IP地址请求信息。由于边界节点重建立到非F1终止点宿主之后，IP地址配置信息只能由非F1终止点宿主发送，因此非F1终止点宿主不需要向F1终止点宿主回复该非F1终止点拓扑域的IP地址配置信息，换句话说，F1终止点宿主不会接收到非F1终止点宿主发送的该IP地址配置信息。
因此，可以通过在IAB传输迁移管理请求消息中引入新的信息元IAB TNL ADDRESS REQUEST，用于请求非F1终止点拓扑域的IP地址。
在一些实施例中，该方法还可以包括：
2702，该非F1终止点宿主向该IAB节点发送IP地址配置信息；例如非F1终止点宿主产生RRCReconfiguration，该RRCReconfiguration承载非F1终止点拓扑域的IP地址配置信息。
由上述实施例可知，F1终止点宿主可以请求非F1终止点宿主分配非F1终止点拓扑域的IP地址，从而使F1终止点宿主请求非F1终止点拓扑域的IP地址并由非F1终止点宿主将非F1终止点拓扑域的IP地址发送给IAB节点。这样针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址。
以上信令过程仅示意性对本申请实施例进行了说明，但本申请不限于此，关于信令的更具体的内容，还可以参考相关技术。此外，例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图12,14-16,18-19,21的记载。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例， 也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，F1终止点宿主可以请求非F1终止点宿主分配非F1终止点拓扑域的IP地址，或进一步的接收非F1终止点宿主针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，从而使F1终止点宿主可以请求非F1终止点拓扑域的IP地址，或进一步的为IAB节点发送非F1终止点拓扑域的IP地址，例如，当非F1终止点宿主无法给IAB节点发送消息的情况下。F1终止点宿主可以接收非F1终止点宿主主动发送的非F1终止点拓扑域的IP地址配置信息，以便为IAB节点发送非F1终止点拓扑域的IP地址，例如，当非F1终止点宿主无法向IAB节点发送消息的情况下。另外，F1终止点宿主可以向非F1终止点宿主发送F1终止点拓扑域的IP地址配置信息，从而使非F1终止点宿主可以向IAB节点发送F1终止点拓扑域的IP地址，例如，当F1终止点宿主无法向IAB节点发送消息的情况下。这样，针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址，针对F1终止点拓扑域的routing ID，可以使用F1终止点拓扑域的IP地址。
第二方面的实施例
本申请实施例提供一种传输地址配置方法，从非F1终止点宿主侧进行说明。与第一方面的实施例相同的内容不再赘述。
图28是本申请实施例的传输地址配置方法的另一示意图。如图28所示，该方法包括：
2801，该非F1终止点宿主接收F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
该非F1终止点宿主向F1终止点宿主发送针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息；和/或，
该非F1终止点宿主接收F1终止点宿主发送的针对该IAB节点分配的F1终止点拓扑域的IP地址配置信息。
在一些实施例中，该方法还可以包括：(未图示)
该非F1终止点宿主向该IAB节点发送该IP地址配置信息。
在一些实施例中，该IP地址请求信息由第一RRC容器承载，该第一RRC容器还包括该IAB节点在该F1终止点拓扑域中的IP地址配置信息，例如，所述IP地址 请求信息由所述第一RRC容器中包含的其他IAB信息消息(IABOtherInformation)或RRC重配置消息(RRCReconfiguration)承载。
在一些实施例中，该第一RRC容器由以下至少一种消息承载：
切换请求消息；
辅节点添加请求消息；
辅节点修改请求消息；
辅节点修改需求消息；
UE上下文获取响应消息。
在一些实施例中，该IP地址配置信息由第二RRC容器承载，例如所述IP地址配置信息由所述第二RRC容器中包含的RRC重配置消息(RRCReconfiguration)承载。
在一些实施例中，该第二RRC容器由以下至少一种消息承载：
切换请求响应消息；
辅节点添加响应消息；
辅节点修改响应消息；
辅节点修改需求消息。
在一些实施例中，该F1终止点宿主是该IAB节点切换的源宿主，该非F1终止点宿主是该IAB节点切换的目标宿主，该方法包括：
该非F1终止点宿主接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该非F1终止点宿主向该F1终止点宿主发送针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该第一RRC容器由切换请求消息承载，该第二RRC容器由切换请求响应消息承载。
在一些实施例中，该F1终止点宿主是该IAB节点的主节点MN，该非F1终止点宿主是该IAB节点的辅节点SN，该方法包括：
该非F1终止点宿主接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该第一RRC容器由辅节点添加请求消息或辅节点修改请求消息承载，进一步，该非F1终止点宿主向该F1终止点宿主发送针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该第二RRC容器由辅节点添加响应消息或辅节点修改响应消息承载。可选的，该非F1终止点宿主还向所述IAB节点发送所述IP地址配置信息。
在一些实施例中，该F1终止点宿主是该IAB节点的主节点MN，该非F1终止点宿主是该IAB节点的辅节点SN，该方法包括：
该非F1终止点宿主向该F1终止点宿主发送针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该第二RRC容器由辅节点修改需求消息承载。
在一些实施例中，该非F1终止点宿主是该IAB节点的主节点MN，该F1终止点宿主是该IAB节点的辅节点SN，该方法包括：
该非F1终止点宿主接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该第一RRC容器由辅节点修改需求消息承载。可选的，该非F1终止点宿主还向所述IAB节点发送所述IP地址配置信息。
在一些实施例中，该非F1终止点宿主是该IAB节点的主节点MN，该F1终止点宿主是该IAB节点的辅节点SN，该方法包括：
该非F1终止点宿主接收该F1终止点宿主发送的针对边界节点分配的F1终止点拓扑域的IP地址配置信息，该第二RRC容器由辅节点修改需求消息承载。可选的，该非F1终止点宿主还向所述IAB节点发送所述IP地址配置信息。
在一些实施例中，该F1终止点宿主是RLF恢复后该IAB节点的宿主，该非F1终止点宿主是RLF恢复前该IAB节点的宿主，该方法包括：
该非F1终止点宿主接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该第一RRC容器由UE上下文获取响应消息承载。可选的，该非F1终止点宿主还向所述IAB节点发送所述IP地址配置信息。
在一些实施例中，该IP地址请求信息由IAB传输迁移管理请求消息承载。其中，该IP地址请求信息中包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点。
在一些实施例中，该IP地址配置信息由IAB传输迁移管理响应消息或IAB传输迁移修改请求消息承载，该IP地址配置信息中包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点。
在一些实施例中，该F1终止点宿主是该IAB节点切换的源宿主，该非F1终止点宿主是该IAB节点切换的目标宿主，该方法包括：
该非F1终止点宿主接收该F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该IP地址请求信息由IAB传输迁移管理请求消息承载。可选的，该非F1终止点宿主还向所述IAB节点发送所述IP地址配置信息。
在一些实施例中，其中，该F1终止点宿主是该IAB节点的主节点MN，该非F1终止点宿主是该IAB节点的辅节点SN，该方法包括：
该非F1终止点宿主接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该IP地址请求信息由IAB传输迁移管理请求消息承载，进一步，该非F1终止点宿主向该F1终止点宿主发送针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该IP地址配置信息由IAB传输迁移管理响应消息承载。可选的，该非F1终止点宿主还向所述IAB节点发送所述IP地址配置信息。
在一些实施例中，该F1终止点宿主是该IAB节点的主节点MN，该非F1终止点宿主是该IAB节点的辅节点SN，该方法包括：
该非F1终止点宿主向该F1终止点宿主发送针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该IP地址配置信息由IAB传输迁移修改请求消息承载。
在一些实施例中，该非F1终止点宿主是该IAB节点的主节点MN，该F1终止点宿主是该IAB节点的辅节点SN，该方法包括：
该非F1终止点宿主接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该IP地址请求信息由IAB传输迁移管理请求消息承载。可选的，该非F1终止点宿主还向所述IAB节点发送所述IP地址配置信息。
在一些实施例中，该非F1终止点宿主是该IAB节点的主节点MN，该F1终止点宿主是该IAB节点的辅节点SN，该方法包括：
该非F1终止点宿主接收该F1终止点宿主发送的针对边界节点分配的F1终止点拓扑域的IP地址配置信息，该IP地址配置信息由IAB传输迁移管理请求消息承载。可选的，该非F1终止点宿主还向所述IAB节点发送所述IP地址配置信息。
在一些实施例中，该F1终止点宿主是RLF恢复后该IAB节点的宿主，该非F1终止点宿主是RLF恢复前该IAB节点的宿主，该方法包括：
该非F1终止点宿主接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该IP地址请求信息由IAB传输迁移管理请求消息承载。可选的，该非F1终止点宿主还向所述IAB节点发送所述IP地址配置信息。
以上信令过程仅示意性对本申请实施例进行了说明，但本申请不限于此，关于信令的更具体的内容，还可以参考相关技术。此外，例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，具体信令过程与第一方面实施例中附图 12,14-16,18-19,21的记载对应，此处不再一一赘述。
由上述实施例可知，F1终止点宿主可以请求非F1终止点宿主分配非F1终止点拓扑域的IP地址，或进一步的接收非F1终止点宿主针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，从而使F1终止点宿主可以请求非F1终止点拓扑域的IP地址，或进一步的为IAB节点发送非F1终止点拓扑域的IP地址，例如，当非F1终止点宿主无法给IAB节点发送消息的情况下。F1终止点宿主可以接收非F1终止点宿主主动发送的非F1终止点拓扑域的IP地址配置信息，以便为IAB节点发送非F1终止点拓扑域的IP地址，例如，当非F1终止点宿主无法向IAB节点发送消息的情况下。另外，F1终止点宿主可以向非F1终止点宿主发送F1终止点拓扑域的IP地址配置信息，从而使非F1终止点宿主可以向IAB节点发送F1终止点拓扑域的IP地址，例如，当F1终止点宿主无法向IAB节点发送消息的情况下。这样，针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址，针对F1终止点拓扑域的routing ID，可以使用F1终止点拓扑域的IP地址。
第三方面的实施例
本申请实施例提供一种IAB宿主设备，与第一方面的实施例相同的内容不再赘述。该设备例如可以是IAB系统中的IAB donor-CU(如第一、二方面的实施例中的第一donor-CU或F1终止点宿主)，也可以是配置于该IAB donor-CU或F1终止点宿主中的某个或某些部件或者组件或者模块。
图29是本申请实施例的IAB宿主设备的一示意图。如图29所示，IAB宿主设备2900包括：
第一发送部2901，其向非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
向非F1终止点宿主发送针对该IAB节点分配的F1终止点拓扑域的IP地址配置信息；和/或，
第一接收部2902，其接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息。
在一些实施例中，该IP地址请求信息由第一RRC容器承载。
在一些实施例中，该第一RRC容器还包括该IAB节点在该F1终止点拓扑域中的IP地址配置信息。
在一些实施例中，所述IP地址请求信息由所述第一RRC容器中包含的其他IAB信息消息(IABOtherInformation)或RRC重配置消息(RRCReconfiguration)承载。
在一些实施例中，该第一RRC容器由以下至少一种消息承载：
切换请求消息；
辅节点添加请求消息；
辅节点修改请求消息；
辅节点修改需求消息；
UE上下文获取响应消息。
在一些实施例中，该IP地址配置信息由第二RRC容器承载。
在一些实施例中，所述IP地址配置信息由所述第二RRC容器中包含的RRC重配置消息(RRCReconfiguration)承载。
在一些实施例中，该第二RRC容器由以下至少一种消息承载：
切换请求响应消息；
辅节点添加响应消息；
辅节点修改响应消息；
辅节点修改需求消息。
在一些实施例中，该F1终止点宿主是该IAB节点切换的源宿主，该非F1终止点宿主是该IAB节点切换的目标宿主，该第一发送部向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该第一接收部接收该非F1终止点宿主发送的针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该第一RRC容器由切换请求消息承载，该第二RRC容器由切换请求响应消息承载。可选的，该第一发送部还向该IAB节点发送该IP地址配置信息。
在一些实施例中，该F1终止点宿主是该IAB节点的主节点MN，该非F1终止点宿主是该IAB节点的辅节点SN，该第一发送部向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该第一RRC容器由辅节点添加请求消息或辅节点修改请求消息承载；进一步，该第一接收部接收该非F1终止点宿主发送的针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该第二RRC容器由辅节点添加响应消息或辅节点修改响应消息承载。可选的，该第一发送部还向该IAB节点发送该IP地址配置信息。
在一些实施例中，该F1终止点宿主是该IAB节点的主节点MN，该非F1终止 点宿主是该IAB节点的辅节点SN，该第一接收部接收该非F1终止点宿主发送的针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该第二RRC容器由辅节点修改需求消息承载。可选的，该第一发送部还向该IAB节点发送该IP地址配置信息。
在一些实施例中，该非F1终止点宿主是该IAB节点的主节点MN，该F1终止点宿主是该IAB节点的辅节点SN，该第一发送部向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该第一RRC容器由辅节点修改需求消息承载。
在一些实施例中，该非F1终止点宿主是该IAB节点的主节点MN，该F1终止点宿主是该IAB节点的辅节点SN，该第一发送部向该非F1终止点宿主发送针对边界节点分配的F1终止点拓扑域的IP地址配置信息，该第二RRC容器由辅节点修改需求消息承载。
在一些实施例中，该F1终止点宿主是RLF恢复后该IAB节点的宿主，该非F1终止点宿主是RLF恢复前该IAB节点的宿主，该第一发送部向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该第一RRC容器由UE上下文获取响应消息承载。
在一些实施例中，该IP地址请求信息由IAB传输迁移管理请求消息承载。
在一些实施例中，该IP地址请求信息中包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点。
在一些实施例中，该IP地址配置信息由IAB传输迁移管理响应消息或IAB传输迁移修改请求消息承载。
在一些实施例中，该IP地址配置信息中包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点。
在一些实施例中，该F1终止点宿主是该IAB节点切换的源宿主，该非F1终止点宿主是该IAB节点切换的目标宿主，该发送向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该IP地址请求信息由IAB传输迁移管理请求消息承载。
在一些实施例中，该F1终止点宿主是该IAB节点的主节点MN，该非F1终止点宿主是该IAB节点的辅节点SN，该第一发送部向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该IP地址请求信息由IAB传输 迁移管理请求消息承载，进一步，该第一接收部接收该非F1终止点宿主发送的针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息该IP地址配置信息由IAB传输迁移管理响应消息承载。可选的，该第一发送部还向该IAB节点发送该IP地址配置信息。
在一些实施例中，该F1终止点宿主是该IAB节点的主节点MN，该非F1终止点宿主是该IAB节点的辅节点SN，该第一接收部接收该非F1终止点宿主发送的针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该IP地址配置信息由IAB传输迁移修改请求消息承载。可选的，该第一发送部还向该IAB节点发送该IP地址配置信息。
在一些实施例中，该非F1终止点宿主是该IAB节点的主节点MN，该F1终止点宿主是该IAB节点的辅节点SN，该第一发送部向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该IP地址请求信息由IAB传输迁移管理请求消息承载。
在一些实施例中，该非F1终止点宿主是该IAB节点的主节点MN，该F1终止点宿主是该IAB节点的辅节点SN，该第一发送部向非F1终止点宿主发送针对边界节点分配的F1终止点拓扑域的IP地址配置信息，该IP地址配置信息由IAB传输迁移管理请求消息承载。
在一些实施例中，该F1终止点宿主是RLF恢复后该IAB节点的宿主，该非F1终止点宿主是RLF恢复前该IAB节点的宿主，该第一发送部向该非F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该IP地址请求信息由IAB传输迁移管理请求消息承载。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的IAB宿主设备2900还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图29中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实 现；本申请实施并不对此进行限制。
由上述实施例可知，F1终止点宿主可以请求非F1终止点宿主分配非F1终止点拓扑域的IP地址，或进一步的接收非F1终止点宿主针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，从而使F1终止点宿主可以请求非F1终止点拓扑域的IP地址，或进一步的为IAB节点发送非F1终止点拓扑域的IP地址，例如，当非F1终止点宿主无法给IAB节点发送消息的情况下。F1终止点宿主可以接收非F1终止点宿主主动发送的非F1终止点拓扑域的IP地址配置信息，以便为IAB节点发送非F1终止点拓扑域的IP地址，例如，当非F1终止点宿主无法向IAB节点发送消息的情况下。另外，F1终止点宿主可以向非F1终止点宿主发送F1终止点拓扑域的IP地址配置信息，从而使非F1终止点宿主可以向IAB节点发送F1终止点拓扑域的IP地址，例如，当F1终止点宿主无法向IAB节点发送消息的情况下。这样，针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址，针对F1终止点拓扑域的routing ID，可以使用F1终止点拓扑域的IP地址。
第四方面的实施例
本申请实施例提供一种IAB宿主设备，与第二方面的实施例相同的内容不再赘述。该设备例如可以是IAB系统中的IAB donor-CU(如第一、二方面的实施例中的第二donor-CU或非F1终止点宿主)，也可以是配置于该IAB donor-CU或非F1终止点宿主中的某个或某些部件或者组件或者模块。
图30是本申请实施例的IAB宿主设备的一示意图。如图30所示，IAB宿主设备3000包括：
第二接收部3001，其接收F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
接收F1终止点宿主发送的针对该IAB节点分配的F1终止点拓扑域的IP地址配置信息；和/或，
第二发送部3002，其向F1终止点宿主发送针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息。
在一些实施例中，该IP地址请求信息由第一RRC容器承载。
在一些实施例中，该第一RRC容器还包括该IAB节点在该F1终止点拓扑域中的IP地址配置信息。
在一些实施例中，所述IP地址请求信息由所述第一RRC容器中包含的其他IAB信息消息(IABOtherInformation)或RRC重配置消息(RRCReconfiguration)承载。
在一些实施例中，该第一RRC容器由以下至少一种消息承载：
切换请求消息；
辅节点添加请求消息；
辅节点修改请求消息；
辅节点修改需求消息；
UE上下文获取响应消息。
在一些实施例中，该IP地址配置信息由第二RRC容器承载。
在一些实施例中，所述IP地址配置信息由所述第二RRC容器中包含的RRC重配置消息(RRCReconfiguration)承载。
在一些实施例中，该第二RRC容器由以下至少一种消息承载：
切换请求响应消息；
辅节点添加响应消息；
辅节点修改响应消息；
辅节点修改需求消息。
在一些实施例中，该F1终止点宿主是该IAB节点切换的源宿主，该非F1终止点宿主是该IAB节点切换的目标宿主，该第二接收部接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该第二发送部向该F1终止点宿主发送针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该第一RRC容器由切换请求消息承载，该第二RRC容器由切换请求响应消息承载。
在一些实施例中，该F1终止点宿主是该IAB节点的主节点MN，该非F1终止点宿主是该IAB节点的辅节点SN，该第二接收部接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该第一RRC容器由辅节点添加请求消息或辅节点修改请求消息承载，进一步，该第二发送部向该F1终止点宿主发送针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该第二RRC容器由辅节点添加响应消息或辅节点修改响应消息承载。可选的，该第二发送部还向该IAB节点发送该IP地址配置信息。
在一些实施例中，该F1终止点宿主是该IAB节点的主节点MN，该非F1终止点宿主是该IAB节点的辅节点SN，该第二发送部向该F1终止点宿主发送针对该IAB 节点分配的非F1终止点拓扑域的IP地址配置信息，该第二RRC容器由辅节点修改需求消息承载。
在一些实施例中，该非F1终止点宿主是该IAB节点的主节点MN，该F1终止点宿主是该IAB节点的辅节点SN，该第二接收部接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该第一RRC容器由辅节点修改需求消息承载。可选的，该第二发送部还向该IAB节点发送该IP地址配置信息。
在一些实施例中，该非F1终止点宿主是该IAB节点的主节点MN，该F1终止点宿主是该IAB节点的辅节点SN，该第二接收部接收该F1终止点宿主发送的针对边界节点分配的F1终止点拓扑域的IP地址配置信息，该第二RRC容器由辅节点修改需求消息承载。可选的，该第二发送部还向该IAB节点发送该IP地址配置信息。
在一些实施例中，该F1终止点宿主是RLF恢复后该IAB节点的宿主，该非F1终止点宿主是RLF恢复前该IAB节点的宿主，该第二接收部接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该第一RRC容器由UE上下文获取响应消息承载。可选的，该第二发送部还向该IAB节点发送该IP地址配置信息。
在一些实施例中，该IP地址请求信息由IAB传输迁移管理请求消息承载。
在一些实施例中，该IP地址请求信息中包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点。
在一些实施例中，该IP地址配置信息由IAB传输迁移管理响应消息或IAB传输迁移修改请求消息承载。
在一些实施例中，该IP地址配置信息中包含边界节点标识；该边界节点标识用于指示该IAB节点为边界节点。
在一些实施例中，该F1终止点宿主是该IAB节点切换的源宿主，该非F1终止点宿主是该IAB节点切换的目标宿主，该第二接收部接收该F1终止点宿主发送针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该IP地址请求信息由IAB传输迁移管理请求消息承载。可选的，该第二发送部还向该IAB节点发送该IP地址配置信息。
在一些实施例中，该F1终止点宿主是该IAB节点的主节点MN，该非F1终止点宿主是该IAB节点的辅节点SN，该第二接收部接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该IP地址请求信息由IAB传 输迁移管理请求消息承载，进一步，该第二发送部向该F1终止点宿主发送针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该IP地址配置信息由IAB传输迁移管理响应消息承载。可选的，该第二发送部还向该IAB节点发送该IP地址配置信息。
在一些实施例中，该F1终止点宿主是该IAB节点的主节点MN，该非F1终止点宿主是该IAB节点的辅节点SN，该第二发送部向该F1终止点宿主发送针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，该IP地址配置信息由IAB传输迁移修改请求消息承载。
在一些实施例中，该非F1终止点宿主是该IAB节点的主节点MN，该F1终止点宿主是该IAB节点的辅节点SN，该第二接收部接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该IP地址请求信息由IAB传输迁移管理请求消息承载。可选的，该第二发送部还向该IAB节点发送该IP地址配置信息。
在一些实施例中，该非F1终止点宿主是该IAB节点的主节点MN，该F1终止点宿主是该IAB节点的辅节点SN，该第二接收部接收该F1终止点宿主发送的针对边界节点分配的F1终止点拓扑域的IP地址配置信息，该IP地址配置信息由IAB传输迁移管理请求消息承载。可选的，该第二发送部还向该IAB节点发送该IP地址配置信息。
在一些实施例中，该F1终止点宿主是RLF恢复后该IAB节点的宿主，该非F1终止点宿主是RLF恢复前该IAB节点的宿主，该第二接收部接收该F1终止点宿主发送的针对该IAB节点的非F1终止点拓扑域的IP地址请求信息，该IP地址请求信息由IAB传输迁移管理请求消息承载。可选的，该第二发送部还向该IAB节点发送该IP地址配置信息。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的IAB宿主设备3000还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图30中仅示例性示出了各个部件或模块之间的连接关系 或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，F1终止点宿主可以请求非F1终止点宿主分配非F1终止点拓扑域的IP地址，或进一步的接收非F1终止点宿主针对该IAB节点分配的非F1终止点拓扑域的IP地址配置信息，从而使F1终止点宿主可以请求非F1终止点拓扑域的IP地址，或进一步的为IAB节点发送非F1终止点拓扑域的IP地址，例如，当非F1终止点宿主无法给IAB节点发送消息的情况下。F1终止点宿主可以接收非F1终止点宿主主动发送的非F1终止点拓扑域的IP地址配置信息，以便为IAB节点发送非F1终止点拓扑域的IP地址，例如，当非F1终止点宿主无法向IAB节点发送消息的情况下。另外，F1终止点宿主可以向非F1终止点宿主发送F1终止点拓扑域的IP地址配置信息，从而使非F1终止点宿主可以向IAB节点发送F1终止点拓扑域的IP地址，例如，当F1终止点宿主无法向IAB节点发送消息的情况下。这样，针对非F1终止点拓扑域的routing ID，IAB节点可以使用非F1终止点拓扑域的IP地址，针对F1终止点拓扑域的routing ID，可以使用F1终止点拓扑域的IP地址。
第五方面的实施例
本申请实施例提供了一种通信系统，该IAB系统包括：第三方面实施例的IAB宿主设备2900和/或第四方面实施例的IAB宿主设备3000，另外还包括IAB节点(边界节点)，关于宿主(donor)设备、IAB节点的网络架构还可以参考相关技术，此处省略说明。
本申请实施例还提供一种IAB宿主设备。
图9是本申请实施例的IAB宿主设备的示意图。如图9所示，IAB设备900可以包括：处理器(例如中央处理器CPU)901和存储器902；存储器902耦合到处理器901。其中该存储器902可存储各种数据；此外还存储信息处理的程序905，并且在中央处理器901的控制下执行该程序905。
例如，处理器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通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于本实施例公开的上述实施方式，还公开了如下的附记：
F1
1.一种传输地址配置方法，应用于IAB节点的F1终止点宿主设备，其特征在于，所述方法包括：
所述F1终止点宿主向非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
所述F1终止点宿主接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；和/或，
所述F1终止点宿主向非F1终止点宿主发送针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息。
2.根据附记1所述的方法，其中，所述IP地址请求信息由第一RRC容器承载。
3.根据附记2所述的方法，其中，所述第一RRC容器还包括所述IAB节点在所述F1终止点拓扑域中的IP地址配置信息。
4.根据附记2或3所述的方法，其中，所述IP地址请求信息由所述第一RRC容器中包含的其他IAB信息消息(IABOtherInformation)或RRC重配置消息(RRCReconfiguration)承载。
5.根据附记2至4任一项所述的方法，其中，所述第一RRC容器由以下至少一种消息承载：
切换请求消息；
辅节点添加请求消息；
辅节点修改请求消息；
辅节点修改需求消息；
UE上下文获取响应消息。
6.根据附记1所述的方法，其中，所述IP地址配置信息由第二RRC容器承载。
7.根据附记6所述的方法，其中，所述IP地址配置信息由所述第二RRC容器中包含的RRC重配置消息(RRCReconfiguration)承载。
8.根据附记6或7所述的方法，其中，所述第二RRC容器由以下至少一种消息承载：
切换请求响应消息；
辅节点添加响应消息；
辅节点修改响应消息；
辅节点修改需求消息。
9.根据附记5或8所述的方法，其中，所述F1终止点宿主是所述IAB节点切换的源宿主，所述非F1终止点宿主是所述IAB节点切换的目标宿主，所述方法包括：
所述F1终止点宿主向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息，所述F1终止点宿主接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述第一RRC容器由切换请求消息承载，所述第二RRC容器由切换请求响应消息承载。
9.1.根据附记9所述的方法，其中，所述方法还包括：
所述F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
10.根据附记5或8所述的方法，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述F1终止点宿主向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述第一RRC容器由辅节点添加请求消息或辅节点修改请求消息承载。
10.1.根据附记10所述的方法，其中，所述方法还包括：
所述F1终止点宿主接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息，所述第二RRC容器由辅节点添加响应消息或辅节点修改响应消息承载。
10.2.根据附记10或10.1所述的方法，其中，所述方法还包括：
所述F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
11.根据附记5或8所述的方法，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述F1终止点宿主接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述第二RRC容器由辅节点修改需求消息承载。
11.1.根据附记11所述的方法，其中，所述方法还包括：
所述F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
12.根据附记5或8所述的方法，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述F1终止点宿主向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述第一RRC容器由辅节点修改需求消息承载。
13.根据附记5或8所述的方法，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述F1终止点宿主向所述非F1终止点宿主发送针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；其中，所述第二RRC容器由辅节点修改需求消息承载。
14.根据附记5或8所述的方法，其中，所述F1终止点宿主是RLF恢复后所述IAB节点的宿主，所述非F1终止点宿主是RLF恢复前所述IAB节点的宿主，所述方法包括：
所述F1终止点宿主向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述第一RRC容器由UE上下文获取响应消息承载。
15.根据附记1所述的方法，其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
16.根据附记15所述的方法，其中，所述IP地址请求信息中包含边界节点标识；所述边界节点标识用于指示所述IAB节点为边界节点。
17.根据附记1所述的方法，其中，所述IP地址配置信息由IAB传输迁移管理响应消息或IAB传输迁移修改请求消息承载。
18.根据附记17所述的方法，其中，所述IP地址配置信息中包含边界节点标识；所述边界节点标识用于指示所述IAB节点为边界节点。
19.根据附记15或17所述的方法，其中，所述F1终止点宿主是所述IAB节点切换的源宿主，所述非F1终止点宿主是所述IAB节点切换的目标宿主，所述方法包括：
所述F1终止点宿主向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
20.根据附记15或17所述的方法，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述F1终止点宿主向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
20.1.根据附记20所述的方法，其中，所述方法还包括：
所述F1终止点宿主接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移管理响应消息承载。
20.2.根据附记20.1所述的方法，其中，所述方法还包括：
所述F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
21.根据附记15或17所述的方法，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述F1终止点宿主接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移修改请求消息承载。
21.1.根据附记21所述的方法，其中，所述方法还包括：
所述F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
22.根据附记15或17所述的方法，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述F1终止点宿主向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
23.根据附记15或17所述的方法，其中，所述非F1终止点宿主是所述IAB节 点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述F1终止点宿主向所述非F1终止点宿主发送针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移管理请求消息承载。
24.根据附记15或17所述的方法，其中，所述F1终止点宿主是RLF恢复后所述IAB节点的宿主，所述非F1终止点宿主是RLF恢复前所述IAB节点的宿主，所述方法包括：
所述F1终止点宿主向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
25.一种IAB宿主(donor)设备，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记1至25任一项所述的传输地址配置方法。
非F1
1.一种传输地址配置方法，应用于IAB节点的非F1终止点宿主设备，其特征在于，所述方法包括：
所述非F1终止点宿主接收F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
所述非F1终止点宿主向F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；和/或，
所述非F1终止点宿主接收F1终止点宿主发送的针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息。
2.根据附记1所述的方法，其中，所述IP地址请求信息由第一RRC容器承载。
3.根据附记2所述的方法，其中，所述第一RRC容器还包括所述IAB节点在所述F1终止点拓扑域中的IP地址配置信息。
4.根据附记2或3所述的方法，其中，所述IP地址请求信息由所述第一RRC容器中包含的其他IAB信息消息(IABOtherInformation)或RRC重配置消息(RRCReconfiguration)承载。
5.根据附记2至4任一项所述的方法，其中，所述第一RRC容器由以下至少一 种消息承载：
切换请求消息；
辅节点添加请求消息；
辅节点修改请求消息；
辅节点修改需求消息；
UE上下文获取响应消息。
6.根据附记1所述的方法，其中，所述IP地址配置信息由第二RRC容器承载。
7.根据附记6所述的方法，其中，所述IP地址配置信息由所述第二RRC容器中包含的RRC重配置消息(RRCReconfiguration)承载。
8.根据附记6或7所述的方法，其中，所述第二RRC容器由以下至少一种消息承载：
切换请求响应消息；
辅节点添加响应消息；
辅节点修改响应消息；
辅节点修改需求消息。
9.根据附记5或8所述的方法，其中，所述F1终止点宿主是所述IAB节点切换的源宿主，所述非F1终止点宿主是所述IAB节点切换的目标宿主，所述方法包括：
所述非F1终止点宿主接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息，所述非F1终止点宿主向所述F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述第一RRC容器由切换请求消息承载，所述第二RRC容器由切换请求响应消息承载。
10.根据附记5或8所述的方法，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述非F1终止点宿主接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述第一RRC容器由辅节点添加请求消息或辅节点修改请求消息承载。
10.1.根据附记10所述的方法，其中，所述方法还包括：
所述非F1终止点宿主向所述F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述第二RRC容器由辅节点添加响应消息或辅节点修改响应消息承载。
10.2.根据附记10或10.1所述的方法，其中，所述方法还包括：
所述非F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
11.根据附记5或8所述的方法，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述非F1终止点宿主向所述F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述第二RRC容器由辅节点修改需求消息承载。
12.根据附记5或8所述的方法，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述非F1终止点宿主接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述第一RRC容器由辅节点修改需求消息承载。
12.1.根据附记12所述的方法，其中，所述方法还包括：
所述非F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
13.根据附记5或8所述的方法，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述非F1终止点宿主接收所述F1终止点宿主发送的针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；其中，所述第二RRC容器由辅节点修改需求消息承载。
13.1.根据附记13所述的方法，其中，所述方法还包括：
所述非F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
14.根据附记5或8所述的方法，其中，所述F1终止点宿主是RLF恢复后所述IAB节点的宿主，所述非F1终止点宿主是RLF恢复前所述IAB节点的宿主，所述方法包括：
所述非F1终止点宿主接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述第一RRC容器由UE上下文获取响应消息承载。
14.1.根据附记14所述的方法，其中，所述方法还包括：
所述非F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
15.根据附记1所述的方法，其中，所述IP地址请求信息由IAB传输迁移管理 请求消息承载。
16.根据附记15所述的方法，其中，所述IP地址请求信息中包含边界节点标识；所述边界节点标识用于指示所述IAB节点为边界节点。
17.根据附记1所述的方法，其中，所述IP地址配置信息由IAB传输迁移管理响应消息或IAB传输迁移修改请求消息承载。
18.根据附记17所述的方法，其中，所述IP地址配置信息中包含边界节点标识；所述边界节点标识用于指示所述IAB节点为边界节点。
19.根据附记15或17所述的方法，其中，所述F1终止点宿主是所述IAB节点切换的源宿主，所述非F1终止点宿主是所述IAB节点切换的目标宿主，所述方法包括：
所述非F1终止点宿主接收所述F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
19.1.根据附记19所述的方法，其中，所述方法还包括：
所述非F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
20.根据附记15或17所述的方法，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述非F1终止点宿主接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
20.1.根据附记20所述的方法，其中，所述方法还包括：
所述非F1终止点宿主向所述F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移管理响应消息承载。
20.2.根据附记20或20.1所述的方法，其中，所述方法还包括：
所述非F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
21.根据附记15或17所述的方法，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述非F1终止点宿主向所述F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移修改 请求消息承载。
22.根据附记15或17所述的方法，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述非F1终止点宿主接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
22.1.根据附记22所述的方法，其中，所述方法还包括：
所述非F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
23.根据附记15或17所述的方法，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述方法包括：
所述非F1终止点宿主接收所述F1终止点宿主发送的针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移管理请求消息承载。
23.1.根据附记23所述的方法，其中，所述方法还包括：
所述非F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
24.根据附记15或17所述的方法，其中，所述F1终止点宿主是RLF恢复后所述IAB节点的宿主，所述非F1终止点宿主是RLF恢复前所述IAB节点的宿主，所述方法包括：
所述非F1终止点宿主接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
24.1.根据附记24所述的方法，其中，所述方法还包括：
所述非F1终止点宿主向所述IAB节点发送所述IP地址配置信息。
25.一种IAB宿主(donor)设备，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记1至25任一项所述的传输地址配置方法。
F1
1.一种IAB宿主设备，所述IAB宿主设备是IAB节点的F1终止点宿主设备，其特征在于，所述设备包括：
第一发送部，其向非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
向非F1终止点宿主发送针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；和/或，
第一接收部，其接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息。
2.根据附记1所述的设备，其中，所述IP地址请求信息由第一RRC容器承载。
3.根据附记2所述的设备，其中，所述第一RRC容器还包括所述IAB节点在所述F1终止点拓扑域中的IP地址配置信息。
4.根据附记2或3所述的设备，其中，所述IP地址请求信息由所述第一RRC容器中包含的其他IAB信息消息(IABOtherInformation)或RRC重配置消息(RRCReconfiguration)承载。
5.根据附记2至4任一项所述的设备，其中，所述第一RRC容器由以下至少一种消息承载：
切换请求消息；
辅节点添加请求消息；
辅节点修改请求消息；
辅节点修改需求消息；
UE上下文获取响应消息。
6.根据附记1所述的设备，其中，所述IP地址配置信息由第二RRC容器承载。
7.根据附记6所述的设备，其中，所述IP地址配置信息由所述第二RRC容器中包含的RRC重配置消息(RRCReconfiguration)承载。
8.根据附记6或7所述的设备，其中，所述第二RRC容器由以下至少一种消息承载：
切换请求响应消息；
辅节点添加响应消息；
辅节点修改响应消息；
辅节点修改需求消息。
9.根据附记5或8所述的设备，其中，所述F1终止点宿主是所述IAB节点切换的源宿主，所述非F1终止点宿主是所述IAB节点切换的目标宿主，所述第一发送部 向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息，所述第一接收部接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述第一RRC容器由切换请求消息承载，所述第二RRC容器由切换请求响应消息承载。
10.根据附记5或8所述的设备，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述第一RRC容器由辅节点添加请求消息或辅节点修改请求消息承载。
10.1.根据附记10所述的设备，其中，所述第一接收部还接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述第二RRC容器由辅节点添加响应消息或辅节点修改响应消息承载。
11.根据附记5或8所述的设备，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述第一接收部接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述第二RRC容器由辅节点修改需求消息承载。
12.根据附记5或8所述的设备，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述第一RRC容器由辅节点修改需求消息承载。
13.根据附记5或8所述的设备，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；其中，所述第二RRC容器由辅节点修改需求消息承载。
14.根据附记5或8所述的设备，其中，所述F1终止点宿主是RLF恢复后所述IAB节点的宿主，所述非F1终止点宿主是RLF恢复前所述IAB节点的宿主，所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述第一RRC容器由UE上下文获取响应消息承载。
15.根据附记1所述的设备，其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
16.根据附记15所述的设备，其中，所述IP地址请求信息中包含边界节点标识； 所述边界节点标识用于指示所述IAB节点为边界节点。
17.根据附记1所述的设备，其中，所述IP地址配置信息由IAB传输迁移管理响应消息或IAB传输迁移修改请求消息承载。
18.根据附记17所述的设备，其中，所述IP地址配置信息中包含边界节点标识；所述边界节点标识用于指示所述IAB节点为边界节点。
19.根据附记15或17所述的设备，其中，所述F1终止点宿主是所述IAB节点切换的源宿主，所述非F1终止点宿主是所述IAB节点切换的目标宿主，所述发送向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
20.根据附记15或17所述的设备，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
20.1.根据附记20所述的设备，其中，所述第一接收部还接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移管理响应消息承载。
21.根据附记15或17所述的设备，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述第一接收部接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移修改请求消息承载。
22.根据附记15或17所述的设备，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
23.根据附记15或17所述的设备，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移管理请求消息承载。
24.根据附记15或17所述的设备，其中，所述F1终止点宿主是RLF恢复后所述IAB节点的宿主，所述非F1终止点宿主是RLF恢复前所述IAB节点的宿主，所 述第一发送部向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
25.根据附记9或10或10.1或11或20或20.1或21所述的设备，其中，所述第一发送部还向所述IAB节点发送所述IP地址配置信息。
非F1
1.一种IAB宿主设备，所述IAB宿主设备是IAB节点的非F1终止点宿主设备，其特征在于，所述设备包括：
第二接收部，其接收F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
接收F1终止点宿主发送的针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；和/或，
第二发送部，其向F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息。
2.根据附记1所述的设备，其中，所述IP地址请求信息由第一RRC容器承载。
3.根据附记2所述的设备，其中，所述第一RRC容器还包括所述IAB节点在所述F1终止点拓扑域中的IP地址配置信息。
4.根据附记2或3所述的设备，其中，所述IP地址请求信息由所述第一RRC容器中包含的其他IAB信息消息(IABOtherInformation)或RRC重配置消息(RRCReconfiguration)承载。
5.根据附记2至4任一项所述的设备，其中，所述第一RRC容器由以下至少一种消息承载：
切换请求消息；
辅节点添加请求消息；
辅节点修改请求消息；
辅节点修改需求消息；
UE上下文获取响应消息。
6.根据附记1所述的设备，其中，所述IP地址配置信息由第二RRC容器承载。
7.根据附记6所述的设备，其中，所述IP地址配置信息由所述第二RRC容器中包含的RRC重配置消息(RRCReconfiguration)承载。
8.根据附记6或7所述的设备，其中，所述第二RRC容器由以下至少一种消息承载：
切换请求响应消息；
辅节点添加响应消息；
辅节点修改响应消息；
辅节点修改需求消息。
9.根据附记5或8所述的设备，其中，所述F1终止点宿主是所述IAB节点切换的源宿主，所述非F1终止点宿主是所述IAB节点切换的目标宿主，所述第二接收部接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息，所述第二发送部向所述F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述第一RRC容器由切换请求消息承载，所述第二RRC容器由切换请求响应消息承载。
10.根据附记5或8所述的设备，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述第二接收部接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述第一RRC容器由辅节点添加请求消息或辅节点修改请求消息承载。
10.1.根据附记10所述的设备，所述第二发送部还向所述F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息，所述第二RRC容器由辅节点添加响应消息或辅节点修改响应消息承载。
11.根据附记5或8所述的设备，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述第二发送部向所述F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述第二RRC容器由辅节点修改需求消息承载。
12.根据附记5或8所述的设备，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述第二接收部接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述第一RRC容器由辅节点修改需求消息承载。
13.根据附记5或8所述的设备，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述第二接收部 接收所述F1终止点宿主发送的针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；其中，所述第二RRC容器由辅节点修改需求消息承载。
14.根据附记5或8所述的设备，其中，所述F1终止点宿主是RLF恢复后所述IAB节点的宿主，所述非F1终止点宿主是RLF恢复前所述IAB节点的宿主，所述第二接收部接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述第一RRC容器由UE上下文获取响应消息承载。
15.根据附记1所述的设备，其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
16.根据附记15所述的设备，其中，所述IP地址请求信息中包含边界节点标识；所述边界节点标识用于指示所述IAB节点为边界节点。
17.根据附记1所述的设备，其中，所述IP地址配置信息由IAB传输迁移管理响应消息或IAB传输迁移修改请求消息承载。
18.根据附记17所述的设备，其中，所述IP地址配置信息中包含边界节点标识；所述边界节点标识用于指示所述IAB节点为边界节点。
19.根据附记15或17所述的设备，其中，所述F1终止点宿主是所述IAB节点切换的源宿主，所述非F1终止点宿主是所述IAB节点切换的目标宿主，所述第二接收部接收所述F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
20.根据附记15或17所述的设备，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述第二接收部接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
20.1.根据附记20所述的设备，其中，所述第二发送部还向所述F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移管理响应消息承载。
21.根据附记15或17所述的设备，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，所述第二发送部向所述F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移修改请求消息承载。
22.根据附记15或17所述的设备，其中，所述非F1终止点宿主是所述IAB节 点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述第二接收部接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
23.根据附记15或17所述的设备，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，所述第二接收部接收所述F1终止点宿主发送的针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移管理请求消息承载。
24.根据附记15或17所述的设备，其中，所述F1终止点宿主是RLF恢复后所述IAB节点的宿主，所述非F1终止点宿主是RLF恢复前所述IAB节点的宿主，所述第二接收部接收所述F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
25.根据附记10或10.1或12或13或4或19或20或20.1或22或23或24所述的设备，其中，所述第二发送部还向所述IAB节点发送所述IP地址配置信息。

Claims (20)

  1. 一种集成的接入和回传IAB宿主设备，所述IAB宿主设备是IAB节点的F1终止点宿主设备，其特征在于，所述设备包括：
    第一发送部，其向非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
    向非F1终止点宿主发送针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；和/或，
    第一接收部，其接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息。
  2. 根据权利要求1所述的设备，其中，所述IP地址请求信息由第一RRC容器承载。
  3. 根据权利要求2所述的设备，其中，所述第一RRC容器还包括所述IAB节点在所述F1终止点拓扑域中的IP地址配置信息。
  4. 根据权利要求2或3所述的设备，其中，所述IP地址请求信息由所述第一RRC容器中包含的其他IAB信息消息(IABOtherInformation)或RRC重配置消息(RRCReconfiguration)承载。
  5. 根据权利要求1所述的设备，其中，所述IP地址配置信息由第二RRC容器承载。
  6. 根据权利要求5所述的设备，其中，所述IP地址配置信息由所述第二RRC容器中包含的RRC重配置消息(RRCReconfiguration)承载。
  7. 根据权利要3或6所述的设备，其中，所述第一RRC容器由以下至少一种消息承载：
    切换请求消息；
    辅节点添加请求消息；
    辅节点修改请求消息；
    辅节点修改需求消息；
    UE上下文获取响应消息。
    其中，所述第二RRC容器由以下至少一种消息承载：
    切换请求响应消息；
    辅节点添加响应消息；
    辅节点修改响应消息；
    辅节点修改需求消息。
  8. 根据权利要求7所述的设备，其中，所述F1终止点宿主是所述IAB节点切换的源宿主，所述非F1终止点宿主是所述IAB节点切换的目标宿主；
    所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息，所述第一接收部接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；
    其中，所述第一RRC容器由切换请求消息承载，所述第二RRC容器由切换请求响应消息承载。
  9. 根据权利要求7所述的设备，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，
    所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息，其中，所述第一RRC容器由辅节点添加请求消息或辅节点修改请求消息承载，或者，
    所述第一接收部接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述第二RRC容器由辅节点添加响应消息或辅节点修改响应消息承载；或者，
    所述第一接收部接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述第二RRC容器由辅节点修改需求消息承载。
  10. 根据权利要求7所述的设备，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，
    所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息，所述第一RRC容器由辅节点修改需求消息承载，或者，
    所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；其中，所述第二RRC容器由辅节点修改需求消息承载。
  11. 根据权利要求7所述的设备，其中，所述F1终止点宿主是RLF恢复后所述 IAB节点的宿主，所述非F1终止点宿主是RLF恢复前所述IAB节点的宿主；
    所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述第一RRC容器由UE上下文获取响应消息承载。
  12. 根据权利要求1所述的设备，其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载，所述IP地址配置信息由IAB传输迁移管理响应消息或IAB传输迁移修改请求消息承载。
  13. 根据权利要求12所述的设备，其中，所述IP地址请求信息中包含边界节点标识，所述边界节点标识用于指示所述IAB节点为边界节点；或者，所述IP地址配置信息中包含边界节点标识，所述边界节点标识用于指示所述IAB节点为边界节点。
  14. 根据权利要求12所述的设备，其中，所述F1终止点宿主是所述IAB节点切换的源宿主，所述非F1终止点宿主是所述IAB节点切换的目标宿主；
    所述发送向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
  15. 根据权利要求12所述的设备，其中，所述F1终止点宿主是所述IAB节点的主节点MN，所述非F1终止点宿主是所述IAB节点的辅节点SN，
    所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载；或者，
    所述第一接收部接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移管理响应消息承载；或者，
    所述第一接收部接收所述非F1终止点宿主发送的针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移修改请求消息承载。
  16. 根据权利要求12所述的设备，其中，所述非F1终止点宿主是所述IAB节点的主节点MN，所述F1终止点宿主是所述IAB节点的辅节点SN，
    所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消 息承载，或者，
    所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；其中，所述IP地址配置信息由IAB传输迁移管理请求消息承载。
  17. 根据权利要求12所述的设备，其中，所述F1终止点宿主是RLF恢复后所述IAB节点的宿主，所述非F1终止点宿主是RLF恢复前所述IAB节点的宿主；
    所述第一发送部向所述非F1终止点宿主发送针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；其中，所述IP地址请求信息由IAB传输迁移管理请求消息承载。
  18. 根据权利要求1所述的设备，其中，所述第一发送部还向所述IAB节点发送所述IP地址配置信息。
  19. 一种集成的接入和回传IAB宿主设备，所述IAB宿主设备是IAB节点的非F1终止点宿主设备，其特征在于，所述设备包括：
    第二接收部，其接收F1终止点宿主发送的针对所述IAB节点的非F1终止点拓扑域的IP地址请求信息；和/或，
    接收F1终止点宿主发送的针对所述IAB节点分配的F1终止点拓扑域的IP地址配置信息；和/或，
    第二发送部，其向F1终止点宿主发送针对所述IAB节点分配的非F1终止点拓扑域的IP地址配置信息。
  20. 一种通信系统，所述系统包括：权利要求1所述的设备和/或权利要求19所述的设备。
PCT/CN2022/086454 2022-04-12 2022-04-12 Iab宿主设备以及传输地址配置方法 Ceased WO2023197184A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP22936838.6A EP4510703A4 (en) 2022-04-12 2022-04-12 IAB DONOR DEVICE AND TRANSFER ADDRESS CONFIGURATION PROCEDURE
PCT/CN2022/086454 WO2023197184A1 (zh) 2022-04-12 2022-04-12 Iab宿主设备以及传输地址配置方法
CN202280094508.5A CN118975317A (zh) 2022-04-12 2022-04-12 Iab宿主设备以及传输地址配置方法
JP2024557897A JP2025511113A (ja) 2022-04-12 2022-04-12 Ｉａｂドナー機器及び伝送アドレス設定方法
US18/903,595 US20250081274A1 (en) 2022-04-12 2024-10-01 Iab-donor device and transport address configuration method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/086454 WO2023197184A1 (zh) 2022-04-12 2022-04-12 Iab宿主设备以及传输地址配置方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/903,595 Continuation US20250081274A1 (en) 2022-04-12 2024-10-01 Iab-donor device and transport address configuration method

Publications (1)

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

Family

ID=88328727

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/086454 Ceased WO2023197184A1 (zh) 2022-04-12 2022-04-12 Iab宿主设备以及传输地址配置方法

Country Status (5)

Country Link
US (1) US20250081274A1 (zh)
EP (1) EP4510703A4 (zh)
JP (1) JP2025511113A (zh)
CN (1) CN118975317A (zh)
WO (1) WO2023197184A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021187933A1 (ko) * 2020-03-20 2021-09-23 주식회사 케이티 릴레이 노드를 제어하는 방법 및 그 장치
WO2021229997A1 (ja) * 2020-05-11 2021-11-18 京セラ株式会社 通信制御方法
WO2022015230A1 (en) * 2020-07-17 2022-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Inter-cu migration in iab networkinter-cu migration in iab network

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4169291A1 (en) * 2020-06-18 2023-04-26 Telefonaktiebolaget LM Ericsson (publ) Handling communication
CN113873587B (zh) * 2020-06-30 2023-09-22 华为技术有限公司 一种用于iab网络通信的方法及相关设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021187933A1 (ko) * 2020-03-20 2021-09-23 주식회사 케이티 릴레이 노드를 제어하는 방법 및 그 장치
WO2021229997A1 (ja) * 2020-05-11 2021-11-18 京セラ株式会社 通信制御方法
WO2022015230A1 (en) * 2020-07-17 2022-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Inter-cu migration in iab networkinter-cu migration in iab network

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Inter-donor topology adaptation procedures", 3GPP TSG RAN WG3 MEETING #113-E, R3-213256, 5 August 2021 (2021-08-05), XP052032654 *
See also references of EP4510703A4 *

Also Published As

Publication number Publication date
US20250081274A1 (en) 2025-03-06
CN118975317A (zh) 2024-11-15
EP4510703A1 (en) 2025-02-19
EP4510703A4 (en) 2025-06-11
JP2025511113A (ja) 2025-04-15

Similar Documents

Publication Publication Date Title
ES2841848T3 (es) Procedimiento para establecer una interfaz de enlace de recorrido frontal y estación base
US12483956B2 (en) Group migration method and apparatus and system
CN117796000A (zh) 集成的接入和回传的通信装置以及方法
US20240349166A1 (en) Iab-node device, iab-donor device and topology revoking method
WO2022233008A1 (zh) 消息发送方法、装置和系统
WO2022205251A1 (zh) 信息收发方法，数据发送方法以及装置
WO2022236644A1 (zh) 发送和接收信号的方法、装置和通信系统
WO2023150975A1 (zh) Iab宿主设备以及传输迁移回退方法
WO2024026804A1 (zh) 移动节点的配置方法、移动节点和宿主设备
WO2023197184A1 (zh) Iab宿主设备以及传输地址配置方法
JP7741617B2 (ja) Ｉａｂドナー機器及び伝送移行管理方法
CN116724589A (zh) 群组迁移方法、装置和系统
JP7758880B2 (ja) Ｉａｂノード装置、ｉａｂドナー装置及び経路移行方法
WO2023197185A1 (zh) Iab节点设备、iab宿主设备以及传输地址确定方法
WO2024026803A1 (zh) 移动节点的配置方法和宿主设备
US20240397380A1 (en) Iab-donor device and transport migration management method
WO2023184542A1 (zh) 配置信息的方法、装置和通信系统
WO2024207363A1 (zh) 信号的收发方法、装置和通信系统
JP2025528050A (ja) ネットワークノードの通信方法、移動ノードの通信方法、移動ノード及びドナー機器

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024557897

Country of ref document: JP

Ref document number: 202280094508.5

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2022936838

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022936838

Country of ref document: EP

Effective date: 20241112