WO2024026803A1 - 移动节点的配置方法和宿主设备 - Google Patents

移动节点的配置方法和宿主设备 Download PDF

Info

Publication number
WO2024026803A1
WO2024026803A1 PCT/CN2022/110391 CN2022110391W WO2024026803A1 WO 2024026803 A1 WO2024026803 A1 WO 2024026803A1 CN 2022110391 W CN2022110391 W CN 2022110391W WO 2024026803 A1 WO2024026803 A1 WO 2024026803A1
Authority
WO
WIPO (PCT)
Prior art keywords
donor
mobile node
cell
information
node
Prior art date
Application number
PCT/CN2022/110391
Other languages
English (en)
French (fr)
Inventor
路杨
易粟
Original Assignee
富士通株式会社
路杨
易粟
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, 路杨, 易粟 filed Critical 富士通株式会社
Priority to PCT/CN2022/110391 priority Critical patent/WO2024026803A1/zh
Publication of WO2024026803A1 publication Critical patent/WO2024026803A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections

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 equipment functions, serves one or more cells and is connected to the downstream child IAB-node (sub-IAB node or simply child node), provides NR air interface access to UE and downstream child IAB-node and communicates with An F1 connection is established between IAB donor-CU (host centralized unit).
  • 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,
  • IAB-node can access the network through independent networking (SA, Standalone) mode or non-independent networking (EN-DC, E-UTRA-NRDualConnectivity) mode.
  • SA independent networking
  • EN-DC non-independent networking
  • Figure 2 is a schematic diagram of the IAB architecture in SA mode.
  • Figure 3 is a schematic diagram of the IAB architecture in EN-DC mode.
  • FIG 4 is a schematic diagram of an IAB node (IAB-node), parent node (parent IAB-node) and child node (child IAB-node).
  • IAB-node IAB node
  • parent IAB-node parent node
  • child IAB-node child node
  • the IAB-DU of the IAB node is connected to the IAB-MT of the child node as the network side
  • the IAB-MT of the IAB node is connected to the IAB-DU of the parent node as the terminal side.
  • Figure 5 is a schematic diagram of the F1 user plane (F1-U) protocol stack between IAB-DU and IAB donor-CU.
  • Figure 6 is a schematic diagram of the F1 control plane (F1-C) protocol stack between IAB-DU and IAB donor-CU.
  • F1-U and F1-C are built on the transport (IP) layer between IAB-DU and IAB donor-CU. In Figures 5 and 6, they pass through two-hop wireless backhaul. and one-hop wired backhaul.
  • the transport (IP) layer is carried on the backhaul adaptive protocol (BAP) sublayer.
  • BAP adaptive protocol
  • the BAP entity in the IAB-node implements the routing function of the IAB system, and the routing table is provided by the IAB donor-CU.
  • BAP PDU Protocol Data Unit
  • RLC Radio Link Control
  • Multiple RLC channels of the backhaul link can be configured by the IAB-donor to carry different priorities and QoS (Quality of Service). ) service, the BAP entity maps the BAP PDU to different return RLC channels.
  • embodiments of the present application provide a mobile node configuration method and a host device.
  • a method for configuring a mobile node includes:
  • the first donor-CU reconfigures the distribution unit (DU) of the mobile node with second information related to the first cell based on the first information related to the location of the mobile node;
  • the first donor-CU sends the reconfigured second information related to the first cell to the second donor-CU; wherein the reconfigured second information related to the first cell is used by the second donor-CU.
  • donor-CU sends the DU to the mobile node.
  • a host device including:
  • a configuration part that reconfigures the second information related to the first cell for the distribution unit (DU) of the mobile node according to the first information related to the location of the mobile node;
  • a communication unit that sends the reconfigured second information related to the first cell to the second donor-CU; wherein the reconfigured second information related to the first cell is used by the second donor-CU DU sent to the mobile node.
  • a method for configuring a mobile node includes:
  • the second donor-CU receives the second information related to the first cell of the mobile node's DU sent by the first donor-CU; wherein the second information is provided by the first donor-CU according to the mobile node's
  • the first location-related information is the DU reconfiguration of the mobile node
  • the second donor-CU sends the reconfigured second information related to the first cell to the DU of the mobile node.
  • a host device including:
  • a receiving unit that receives the second information related to the first cell of the DU of the mobile node sent by the first donor-CU; wherein the second information is provided by the first donor-CU according to the location of the mobile node.
  • the relevant first information is the DU reconfiguration of the mobile node;
  • a sending unit that sends the reconfigured second information related to the first cell to the DU of the mobile node.
  • a configuration method of a mobile node is provided.
  • the F1 termination donor-CU of the mobile node is changed from the fourth donor-CU to the fifth donor-CU.
  • the method includes:
  • the fifth donor-CU reconfigures the second information related to the first cell for the DU of the mobile node based on the first information related to the location of the mobile node;
  • the fifth donor-CU sends the reconfigured second information related to the first cell to the DU of the mobile node.
  • a host device is provided, and the F1 termination donor-CU of the mobile node is changed from the fourth donor-CU to the host device, and the host device includes:
  • a configuration part that reconfigures the second information related to the first cell for the DU of the mobile node according to the first information related to the location of the mobile node;
  • the communication unit sends the reconfigured second information related to the first cell to the DU of the mobile node.
  • the first donor-CU reconfigures the second information in the mobility area for the mobile node according to the first information of the mobile node; the second donor-CU receives the first donor-CU The second information sent is the reconfiguration of the mobile node and is sent to the DU of the mobile node.
  • the first donor-CU can dynamically configure the cell information in the mobile area for the mobile node based on the real-time location information of the node; thereby avoiding conflicts between the mobile IAB node and neighboring cells, allowing the network to support multiple mobile nodes. Work simultaneously.
  • 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 a mobility scenario
  • Figure 9 is another schematic diagram of a mobility scenario
  • Figure 10 is a schematic diagram of a mobile node configuration method according to an embodiment of the present application.
  • Figure 11 is an example diagram of a mobile node configuration method according to an embodiment of the present application.
  • Figure 12 is a schematic diagram of a communication method of a mobile node according to an embodiment of the present application.
  • Figure 13 is a signaling flow chart of transmission migration according to the embodiment of the present application.
  • Figure 14 is a schematic diagram of a mobile node configuration method according to an embodiment of the present application.
  • Figure 15 is an example diagram of a mobile node configuration method according to an embodiment of the present application.
  • Figure 16 is a schematic diagram of a host device according to an embodiment of the present application.
  • Figure 17 is another schematic diagram of a host device according to an embodiment of the present application.
  • Figure 18 is a schematic diagram of an IAB 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 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.
  • Rel-17 NR has studied the scenario when the IAB node is stationary.
  • the stationary IAB-node changes the transmission path (or called topology adaptation) between different donor-DUs under the F1-terminating donor-CU.
  • topology adaptation topology adaptation
  • Rel-18NR will be studied for mobility scenarios.
  • FIG 8 is a schematic diagram of a mobility scenario. As shown in Figure 8, for example, an IAB node 801 is mounted on a moving vehicle to serve user equipment on the vehicle. Therefore, there is a need to standardize the process for changing transmission paths when mobile IAB nodes move between multiple different donor-CUs.
  • the physical cell identity (PCI) and physical random access channel (PRACH) resource configuration of its serving cell can be fixed, because the network side can determine the neighboring cells (such as macro cells) of its serving cell based on its fixed location. or the serving cell of other IAB nodes), thereby controlling the PCI or PRACH resources of its serving cell not to conflict with the PCI or PRACH resources of surrounding neighboring cells.
  • PCI physical cell identity
  • PRACH physical random access channel
  • Figure 9 is another schematic diagram of a mobility scenario.
  • the movement trajectory of the mobile IAB node may involve the control areas of multiple different donor-CUs.
  • the fixed PCI and fixed PRACH resource methods are not feasible for the mobile IAB node, because if the PCI or PRACH resource of the mobile IAB node is PRACH resources are fixed, and the network side must ensure that neighboring cells involved in its movement trajectory cannot be configured with the same PCI or PRACH resources.
  • the resources available for other cells will be greatly reduced, making it impossible for the network side to support multiple mobile IAB nodes working at the same time.
  • the location of the UE accessing the cell can be determined by the NR cell global identifier (NCGI, NR cell global Identifier) and tracking area (TA, tracking area) of the serving cell.
  • NCGI NR cell global identifier
  • TA tracking area
  • the core network usually determines the location of the UE based on the NCGI and TA of the UE serving cell.
  • the NCGI and TA of the serving cell are configured by the network side according to the location of the cell.
  • the network side can fixedly configure the NCGI and TA of its serving cell according to its location.
  • the movement trajectory may involve multiple different donor-CU control areas, and the location of its serving cell changes in the network.
  • the method of fixing NCGI and TA is not feasible for mobile IAB nodes, because fixed NCGI and TA cannot reflect the actual location of the mobile IAB node's serving cell, and thus cannot reflect the actual location of the UE accessing the cell, making it impossible for the network side to obtain access information. The actual location of the UE entering the mobile IAB node.
  • the IAB node device includes a migration node or its child node.
  • the second information has been described above using PCI, NCGI, TA and PRACH resources as examples, but the present application is not limited thereto.
  • it may also be other information related to the mobile IAB node.
  • the embodiments of this application are not limited to IAB nodes. For example, they are also applicable to Network-controlled repeaters (NCR, Network-controlled repeater).
  • the embodiment of the present application provides a configuration method of a mobile node.
  • the first donor-CU is the non-F1-terminating donor-CU (non-F1-terminating donor-CU) of the mobile node; the second donor-CU is the mobile node.
  • F1-terminating donor-CU F1-terminating donor-CU.
  • Figure 10 is a schematic diagram of a mobile node configuration method according to an embodiment of the present application. As shown in Figure 10, the method includes:
  • the first donor-CU reconfigures the second information related to the first cell for the distribution unit (DU) of the mobile node based on the first information related to the location of the mobile node;
  • the first donor-CU sends the reconfigured second information related to the first cell to the second donor-CU; wherein the reconfigured second information related to the first cell is used by the second donor-CU.
  • donor-CU sends the DU to the mobile node.
  • the first donor-CU non-F1-terminating donor-CU in the embodiment of the present application can dynamically configure the second donor-CU in the mobile area for the mobile node based on the first information (real-time location information) of the mobile node. information; thereby avoiding conflicts between the mobile node and adjacent cells, allowing the network to support multiple mobile nodes working at the same time.
  • the first donor-CU sends the reconfigured second information to the second donor-CU through an XnAP message
  • the second donor-CU sends the reconfigured second information through the first F1AP message.
  • the second information is sent to the DU of the mobile node.
  • the first F1AP message includes an F1 establishment response message or a gNB CU configuration update message.
  • the second information includes at least one of the following: physical cell identity (PCI), NR cell global identity (NCGI), tracking area code (TAC), physical random access channel (PRACH) resource configuration.
  • PCI physical cell identity
  • NCGI NR cell global identity
  • TAC tracking area code
  • PRACH physical random access channel
  • the first information includes: second information related to the second cell detected and reported by the mobile terminal (MT), and/or the location information of the mobile node or the cell accessed by the MT. information.
  • non-F1-terminating donor-CU can configure PCI, NCGI, TAC and PRACH resources for the DU of the mobile IAB node; non-F1-terminating donor-CU can configure the configured This information is sent to F1-terminating donor-CU, which sends these configuration information to the DU of the mobile IAB node using F1AP messages.
  • the PCI and PRACH resources of the mobile IAB node do not conflict with neighboring cells, and the NCGI and TAC of the mobile IAB node are changed according to its actual geographical location, and the network can obtain the actual location information of the UE accessing the mobile IAB node.
  • a mobile terminal accessing the non-F1-terminating donor-CU can detect the PCI, NCGI, TAC and PRACH configuration, and report these configurations to non-F1-terminating donor-CU. Based on this information, non-F1-terminating donor-CU can configure PCI, NCGI, TAC and PRACH resources for the DU of the mobile IAB node; non-F1-terminating donor-CU can send the configured information to F1-terminating donor- CU, the F1-terminating donor-CU sends these configuration information to the DU of the mobile IaB node using F1AP messages.
  • the PCI and PRACH resources of the mobile IAB node do not conflict with neighboring cells, and the NCGI and TAC of the mobile IAB node are changed according to its actual geographical location, and the network can obtain the actual location information of the UE accessing the mobile IAB node.
  • the first donor-CU receives the second information sent by the second donor-CU before the first donor-CU reconfigures the second information related to the first cell for the DU of the mobile node. second information related to the first cell currently configured in the DU of the mobile node.
  • the first donor-CU determines that the second information related to the first cell needs to be reconfigured based on the first information and the currently configured second information related to the first cell. .
  • the mobile node's non-F1 terminating donor-CU changes from the first donor-CU to a third donor-CU.
  • the physical cell identity (PCI) reconfigured for the first cell of the DU of the mobile node does not conflict with the PCI of the neighboring cell
  • the NR reconfigured for the first cell of the DU of the mobile node does not conflict with the PCI of the adjacent cell.
  • the cell global identity (NCGI) is related to the NCGI of the adjacent cell
  • the tracking area code (TAC) reconfigured for the first cell of the DU of the mobile node is the same as or related to the TAC of the adjacent cell
  • the PRACH resources reconfigured by the first cell of the DU do not conflict with the PRACH resources of the neighboring cells.
  • FIG 11 is an example diagram of a mobile node configuration method according to an embodiment of the present application. As shown in Figure 11, the IAB node establishes an F1 connection with donor-CU1, and does not change the F1-terminating CU within a certain area.
  • Donor-CU2 indicates the configuration to donor-CU1 through the XnAP message, and donor-CU1 uses the F1AP message (GNB-CU CONFIGURATION UPDATE) to send the configuration to the IAB node.
  • the PCI of the serving cell of the parent node is 1 and the PCI of the serving cell of the IAB node is 2, which are different. This prevents the PCI of the mobile IAB node from conflicting with neighboring cells.
  • the PCI of the serving cell of the parent node is 2 and the PCI of the serving cell of the IAB node is 1. They are different. This prevents the PCI of the mobile IAB node from conflicting with neighboring cells.
  • the first donor-CU reconfigures the second information in the mobile area for the mobile node according to the first information of the mobile node; the second donor-CU receives the information sent by the first donor-CU.
  • the second information of mobile node reconfiguration is sent to the DU of the mobile node.
  • the first donor-CU can dynamically configure the cell information in the mobile area for the mobile node based on the real-time location information of the node; thereby avoiding conflicts between the mobile IAB node and neighboring cells, allowing the network to support multiple mobile nodes. Work simultaneously.
  • the embodiment of the present application provides a communication method for a mobile node, which can be combined with the embodiment of the first aspect or implemented separately. The same content as the embodiment of the first aspect will not be described again.
  • Rel-17 supports the process of changing the transmission path between IAB nodes F1-terminating donor-CU and non-F1-terminating donor-CU.
  • the mobile node does not change the F1-terminating CU during the movement. It may continuously change the non-F1-terminating donor-CU according to its moving position, and migrate the transmission path to the donor-under the latest non-F1-terminating donor-CU. DU, the embodiments of this application illustrate this.
  • the first donor-CU is the non-F1 terminated donor-CU of the mobile node before migration or radio link failure (RLF) recovery
  • the second donor-CU is the F1-terminated donor of the mobile node.
  • the third donor-CU is a non-F1 terminated donor-CU after migration of the mobile node or recovery from radio link failure (RLF).
  • Figure 12 is a schematic diagram of a communication method of a mobile node according to an embodiment of the present application. As shown in Figure 12, after the RRC connection of the MT of the mobile node is migrated from the first donor-CU to the third donor-CU , the method includes:
  • the second donor-CU receives a transmission migration modification request sent by the first donor-CU, where the transmission migration modification request is used to request the release of transmission resources of the service;
  • the second donor-CU sends a transmission migration modification response to the first donor-CU.
  • the mobile node receives the IP address and BAP layer address assigned by the third donor-CU; the IP address and BAP layer address assigned by the third donor-CU are carried by an RRC reconfiguration message; and The DU of the mobile node reports the IP address selected from the IP addresses allocated by the third donor-CU to the second donor-CU through a gNB DU configuration update message.
  • the second donor-CU determines the third donor-CU based on the IP address reported by the mobile node, and sends a transmission migration management request to the third donor-CU.
  • the transmission migration management request is used to request transmission resources for establishing a service; and the second donor-CU receives the transmission migration management response sent by the third donor-CU.
  • the transmission migration modification request sent by the first donor-CU received by the second donor-CU and the transmission sent by the second donor-CU to the third donor-CU The migration management request includes the Xn interface identifier allocated by the third donor-CU to the mobile node. In this way, the third donor-CU can identify the mobile IAB node through the Xn interface identifier when receiving the transmission migration management request.
  • the DU of the mobile node reports the BAP layer address allocated by the third donor-CU to the mobile node to the second donor-CU through the gNB DU configuration update message; and,
  • the transmission migration management request sent by the second donor-CU to the third donor-CU includes the BAP layer address.
  • the third donor-CU can identify the mobile IAB node through the BAP layer address when receiving the transmission migration management request.
  • the transmission migration process in the embodiment of the present application will be further exemplified below through signaling interaction.
  • Figure 13 is a signaling flow chart of transmission migration according to an embodiment of the present application.
  • F1donor-CU is the second donor-CU mentioned above
  • the original non-F1donor-CU in the source path is the first donor-CU mentioned above
  • the new non-F1donor-CU in the target path is the third donor-CU mentioned above. donor-CU.
  • the process includes:
  • IAB-MT switches from the original non-F1-terminating CU to the new non-F1-terminating CU like the UE.
  • the new non-F1-terminating CU will allocate the UE XnAP ID to IAB-IMT, and allocate the IP address for transmitting non-UP services on the target path to IAB-DU through RRC messages.
  • the original non-F1-terminating CU releases the BH RLC channel and BAP sublayer routing on the original path.
  • the original non-F1-terminating CU sends an IAB TRANSPORT MIGRATION MODIFICATION REQUEST message to the F1-terminating CU to request the release of services on the original path.
  • the released service information includes the release of all service instructions (full release indication) and indicates the new Non-F1-Terminating donor UE XnAP ID.
  • the new Non-F1-Terminating donor UE XnAP ID is the UE identity assigned to the IAB node by the new non-F1-terminating CU side in 1301. In this way, when the F1-terminating CU in 1307 sends a message to the new non-F1-terminating CU, New non-F1-terminatig CU can index to related IAB-MT.
  • F1-terminating CU sends IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message to confirm the request to release all services.
  • the new non-F1-terminating CU configures the BH RLC channel and BAP sublayer routing for the nodes on the target path, as well as the configuration of DL mapping for the donor-DU. These configurations are to support F1-C transmission on the target path.
  • F1-C connects to the IP address assigned in application 1301, and IAB-DU reports the actually used IP address to F1-terminating CU through the gNB-DU CONFIGURATION UPDATE message.
  • F1-terminating CU determines the new non-F1-terminating CU through the IP address reported by IAB-DU, and sends the IAB TRANSPORT MIGRATION MANAGEMENT REQUST message to the new non-F1-terminating CU, including the context information of the business requesting migration, and also It may include DL TNL information used by the new non-F1-terminating donor-CU to configure downstream mapping for the donor-DU.
  • the new non-F1-terminating donor-CU configures or modifies the BH RLC channel and BAP sublayer routing for the nodes on the target path, as well as the configuration of the DL mapping of the donor-DU. These configurations are to support the transmission of F1-U and non-UP services on the target path.
  • the new non-F1-terminating CU sends the IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message to the F1-terminating CU, including the layer 2 information (routing ID, BH RLC channel, The next hop BAP address) may also include the DSCP/IPv6 flow label used to transmit downlink non-UP services.
  • F1-U starts using the IP address assigned by the new non-F1-terminating CU.
  • F1-terminating CU configures updated UL BH information to IAB-DU based on the Layer 2 information of the service received in 1309.
  • the mobile node does not change the F1-terminating CU during the movement process, but can continuously change the non-F1-terminating donor-CU according to its moving position, and migrate the transmission path to the latest non-F1-terminating donor-CU. Donor-DU. As a result, it can better support mobile scenarios and further improve the service stability of mobile IAB nodes.
  • the embodiment of the present application provides a configuration method of a mobile node.
  • the F1 termination donor-CU of the mobile node is changed from the fourth donor-CU to the fifth donor-CU.
  • Figure 14 is a schematic diagram of a mobile node configuration method according to an embodiment of the present application. As shown in Figure 14, the method includes:
  • the fifth donor-CU reconfigures the second information related to the first cell for the DU of the mobile node based on the first information related to the location of the mobile node;
  • the fifth donor-CU sends the reconfigured second information related to the first cell to the DU of the mobile node.
  • the fifth donor-CU (F1-terminating donor-CU) in the embodiment of the present application can dynamically configure the cell information in the mobile area for the mobile node according to the real-time location information of the mobile node; thus, the mobile node can be avoided Conflicts with neighboring cells enable the network to support multiple mobile nodes working simultaneously.
  • the fifth donor-CU sends the reconfigured second information related to the first cell to the DU of the mobile node through a second F1AP message.
  • the second F1AP message includes an F1 establishment response message or a gNB CU configuration update message.
  • the second information includes at least one of the following: physical cell identity (PCI), NR cell global identity (NCGI), tracking area code (TAC), and physical random access channel (PRACH) resource configuration.
  • PCI physical cell identity
  • NCGI NR cell global identity
  • TAC tracking area code
  • PRACH physical random access channel
  • the first information includes: second information related to the second cell detected and reported by the mobile terminal (MT), and/or, the location information of the mobile node or the location information currently accessed by the MT. Community information.
  • the F1-terminating donor-CU can configure PCI, NCGI and TA for the mobile IAB node. ; and send these configuration information to the mobile IaB node using F1AP messages.
  • the PCI of the mobile IAB node does not conflict with neighboring cells, and the NCGI and TA of the mobile IAB node are changed according to its actual geographical location, and the network can obtain the actual location information of the UE accessing the mobile IAB node.
  • the MT of the IAB node or the MT served by the DU of the IAB node can detect the PCI configuration of the neighboring cell (for example, the serving cell accessed by the MT of the IAB node), and report these PCI configurations to the F1-terminating donor-CU. Based on this information, F1-terminating donor-CU can configure PCI, NCGI and TA for the mobile IAB node; and send these configuration information to the mobile IaB node using F1AP messages.
  • the PCI of the mobile IAB node does not conflict with neighboring cells, and the NCGI and TA of the mobile IAB node are changed according to its actual geographical location, and the network can obtain the actual location information of the UE accessing the mobile IAB node.
  • the fifth donor-CU before the fifth donor-CU reconfigures the second information related to the first cell for the DU of the mobile node, the fifth donor-CU receives the DU of the mobile node through the third Three F1AP messages send second information of the currently configured first cell.
  • the third F1AP message includes an F1 establishment request message or a gNB DU configuration update message.
  • the fifth donor-CU determines that the second information related to the first cell needs to be reconfigured based on the first information and the currently configured second information related to the first cell. .
  • the physical cell identity (PCI) reconfigured for the first cell of the DU of the mobile node does not conflict with the PCI of the neighboring cell
  • the NR reconfigured for the first cell of the DU of the mobile node does not conflict with the PCI of the adjacent cell.
  • the cell global identity (NCGI) is related to the NCGI of the adjacent cell
  • the tracking area code (TAC) reconfigured for the first cell of the DU of the mobile node is the same as or related to the TAC of the adjacent cell
  • the PRACH resources reconfigured by the first cell of the DU do not conflict with the PRACH resources of the neighboring cells.
  • Figure 15 is an example diagram of a mobile node configuration method according to an embodiment of the present application.
  • the IAB node initially establishes an F1 connection with donor-CU1, and the F1 transmission path passes through donor-DU1.
  • the PCI of the serving cell of the parent node is 1 and the PCI of the serving cell of the IAB node is 2, which are different. This prevents the PCI of the mobile IAB node from conflicting with neighboring cells.
  • the IAB node MT moves to the donor-DU2 serving cell
  • the IAB-MT switches to donor-CU2
  • the F1 transmission path migrates to donor-DU2.
  • the IAB node establishes an F1 connection with donor-CU2.
  • the PCI of the serving cell of the parent node is 2 and the PCI of the serving cell of the IAB node is 1. They are different. This prevents the PCI of the mobile IAB node from conflicting with neighboring cells.
  • the fifth donor-CU (F1-terminating donor-CU) configures the second information in the mobility area for the mobile node according to the first information of the mobile node, and sends the configured information to the mobile node. DU of the mobile node.
  • the fifth donor-CU can dynamically configure the cell information in the mobile area for the mobile node based on the real-time location information of the mobile node; thereby avoiding conflicts between the mobile node and neighboring cells and allowing the network to support multiple mobile nodes. Work simultaneously.
  • An embodiment of the present application provides a host device, and the same content as the embodiments of the first to third aspects will not be described again.
  • the device may be, for example, an IAB donor-CU in the IAB system (such as the first donor-CU in the first and second embodiments), or may be configured in the IAB donor-CU.
  • IAB donor-CU in the IAB system
  • the IAB donor-CU may be configured in the IAB donor-CU.
  • One or more parts or components or modules may be configured in the IAB donor-CU.
  • FIG 16 is a schematic diagram of a host device according to an embodiment of the present application. As shown in Figure 16, host device 1600 includes:
  • Configuration part 1601 which reconfigures the second information related to the first cell for the distribution unit (DU) of the mobile node according to the first information related to the location of the mobile node;
  • the communication unit 1602 sends the reconfigured second information related to the first cell to the second donor-CU; wherein the reconfigured second information related to the first cell is used by the second donor-CU.
  • DU sent by the CU to the mobile node.
  • the host device is a non-F1-terminating donor-CU (non-F1-terminating donor-CU) of the mobile node; the second donor-CU is an F1-terminating donor-CU of the mobile node.
  • CU F1-terminating donor-CU
  • the communication unit 1602 sends the reconfigured second information to the second donor-CU through an XnAP message, and the second donor-CU sends the reconfigured second information through a first F1AP message.
  • the second information is sent to the DU of the mobile node.
  • the first F1AP message includes an F1 setup response message or a gNB CU configuration update message.
  • the second information includes at least one of the following: physical cell identity (PCI), NR cell global identity (NCGI), tracking area code (TAC), and physical random access channel (PRACH) resource configuration.
  • PCI physical cell identity
  • NCGI NR cell global identity
  • TAC tracking area code
  • PRACH physical random access channel
  • the first information includes: second information related to the second cell detected and reported by the mobile terminal (MT), and/or, the location information of the mobile node or the cell accessed by the MT. Community information.
  • the communication unit 1602 receives the mobile unit sent by the second donor-CU. Second information related to the first cell currently configured in the node's DU.
  • the configuration part 1601 determines that the second information related to the first cell needs to be reconfigured based on the first information and the currently configured second information related to the first cell.
  • the mobile node's non-F1 terminated donor-CU changes from the first donor-CU to a third donor-CU;
  • the communication unit 1602 After the RRC connection of the MT of the mobile node is migrated from the first donor-CU to the third donor-CU, the communication unit 1602 sends a transmission migration modification request to the second donor-CU, wherein, The transmission migration modification request is used to request the release of transmission resources of the service; and receives the transmission migration modification response sent by the second donor-CU.
  • the physical cell identity (PCI) reconfigured for the first cell of the DU of the mobile node does not conflict with the PCI of the neighboring cell
  • the NR reconfigured for the first cell of the DU of the mobile node does not conflict with the PCI of the adjacent cell.
  • the cell global identity (NCGI) is related to the NCGI of the adjacent cell
  • the tracking area code (TAC) reconfigured for the first cell of the DU of the mobile node is the same as or related to the TAC of the adjacent cell
  • the PRACH resources reconfigured by the first cell of the DU do not conflict with the PRACH resources of the neighboring cells.
  • the device may be, for example, an IAB donor-CU in the IAB system (such as the second donor-CU in the first and second embodiments), or may be configured in the IAB donor-CU.
  • IAB donor-CU in the IAB system
  • the second donor-CU in the first and second embodiments
  • the IAB donor-CU may be configured in the IAB donor-CU.
  • One or more parts or components or modules may be configured in the IAB donor-CU.
  • FIG 17 is a schematic diagram of a host device according to an embodiment of the present application. As shown in Figure 17, host device 1700 includes:
  • the receiving unit 1701 receives the second information related to the first cell of the mobile node's DU sent by the first donor-CU; wherein the second information is generated by the first donor-CU according to the mobile node's
  • the first location-related information is the DU reconfiguration of the mobile node
  • the sending unit 1702 sends the reconfigured second information related to the first cell to the DU of the mobile node.
  • the first donor-CU is a non-F1-terminating donor-CU of the mobile node; the host device is an F1-terminating donor-CU of the mobile node.
  • CU F1-terminating donor-CU
  • the mobile node's non-F1 terminated donor-CU changes from the first donor-CU to a third donor-CU;
  • the receiving unit 1701 receives the reconfigured first cell information for the mobile node DU sent by the third donor-CU; and the sending unit 1702 sends the reconfigured first cell information to the mobile node DU. DU of the node.
  • the receiving unit 1701 receives the transmission migration modification sent by the first donor-CU. request; wherein, the transmission migration modification request is used to request the release of transmission resources of the service; the sending unit 1702 sends a transmission migration modification response to the first donor-CU.
  • the receiving unit 1701 receives the IP address selected from the IP addresses allocated by the third donor-CU reported by the DU of the mobile node through the gNB DU configuration update message; wherein, the The mobile node receives the IP address and BAP layer address allocated by the third donor-CU, and the IP address and BAP layer address allocated by the third donor-CU are carried by the RRC reconfiguration message.
  • the sending unit 1702 determines the third donor-CU according to the IP address reported by the mobile node, and sends a transmission migration management request to the third donor-CU, wherein: The transmission migration management request is used to request the establishment of transmission resources for the service; and the receiving unit 1701 receives the transmission migration management response sent by the third donor-CU.
  • the device may be, for example, an IAB donor-CU in the IAB system (such as the fifth donor-CU in the embodiment of the third aspect), or may be a certain device configured in the IAB donor-CU. or certain parts or components or modules.
  • the structure of the host device can be shown in Figure 16.
  • the F1 terminating donor-CU of the mobile node is changed from the fourth donor-CU to the host device, and the configuration part 1601 configures the mobile node for the mobile node based on the first location-related information of the mobile node.
  • the DU reconfigures the second information related to the first cell; and the communication unit 1602 sends the reconfigured second information related to the first cell to the DU of the mobile node.
  • the communication part 1602 sends the reconfigured second information related to the first cell to the DU of the mobile node through a second F1AP message;
  • the second F1AP message includes an F1 establishment response message or a gNB CU configuration update message.
  • the communication part 1602 receives the DU of the mobile node and sends it through a third F1AP message.
  • the third F1AP message includes an F1 establishment request message or a gNB DU configuration update message.
  • the configuration part 1601 determines that the second information related to the first cell needs to be reconfigured based on the first information and the currently configured second information related to the first cell.
  • the host device 1600 or 1700 in the embodiment of the present application may also include other components or modules.
  • the specific content of these components or modules please refer to related technologies.
  • FIG. 16 or 17 only illustrates the connection relationships or signal directions between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connections can be used.
  • Each of the above components or modules can be implemented by hardware facilities such as a processor, a memory, a transmitter, a receiver, etc.; the implementation of this application is not limited to this.
  • the host device configures the second information in the mobility area for the mobile node according to the first information of the mobile node, and sends the configured information to the DU of the mobile node.
  • the host device can dynamically configure cell information for the mobile node in the mobile area based on the real-time location information of the mobile node. This can avoid conflicts between the mobile node and neighboring cells and enable the network to support multiple mobile nodes working at the same time.
  • the embodiment of the present application provides a communication system, including a host (donor) device and a mobile node (such as an IAB-node); for the network architecture and specific content of the host (donor device) and IAB node, you can also refer to related technologies, here Omit description.
  • the IAB system includes: a first donor-CU and a second donor-CU; the first donor-CU is a non-F1-terminating donor-CU of the mobile node. ); the second donor-CU is the F1-terminating donor-CU (F1-terminating donor-CU) of the mobile node.
  • the first donor-CU reconfigures the distribution unit (DU) of the mobile node with second information related to the first cell based on the first information related to the location of the mobile node;
  • the first donor-CU sends the reconfigured second information related to the first cell to the second donor-CU; wherein the reconfigured second information related to the first cell is used by the second donor-CU.
  • the IAB-DU sent by the donor-CU to the mobile IAB node.
  • the IAB system includes: a fourth donor-CU and a fifth donor-CU; the F1 terminating donor-CU of the mobile node changes from the fourth donor-CU to the fifth donor-CU.
  • the fifth donor-CU reconfigures the second information related to the first cell for the DU of the mobile node based on the first information related to the location of the mobile node;
  • the fifth donor-CU sends the reconfigured second information related to the first cell to the DU of the mobile node.
  • Embodiments of the present application also provide an IAB device, which may be an IAB host device or an IAB node device (migration node or child node).
  • IAB device which may be an IAB host device or an IAB node device (migration node or child node).
  • FIG 18 is a schematic diagram of an IAB device according to an embodiment of the present application.
  • IAB device 1800 may include: a processor (eg, central processing unit CPU) 1801 and memory 1802; memory 1802 is coupled to processor 1801.
  • the memory 1802 can store various data; in addition, it also stores an information processing program 1805, and the program 1805 is executed under the control of the central processor 1801.
  • the processor 1801 may be configured to execute a program to implement the configuration method of a mobile node as in the embodiment of the first aspect.
  • the processor 1801 may be configured to perform the following control: reconfigure the distribution unit (DU) of the mobile node with second information related to the first cell according to the first information related to the location of the mobile node; and Send the reconfigured second information related to the first cell to the second donor-CU; wherein the reconfigured second information related to the first cell is sent to the second donor-CU by the second donor-CU.
  • IAB-DU of the mobile IAB node may be configured to execute a program to implement the configuration method of a mobile node as in the embodiment of the first aspect.
  • the processor 1801 may be configured to perform the following control: reconfigure the distribution unit (DU) of the mobile node with second information related to the first cell according to the first information related to the location of the mobile node; and Send the reconfigured second information related to the first cell to the second donor-CU; wherein the reconfigured second information related to the first cell
  • the processor 1801 may be configured to execute a program to implement the communication method of the mobile node as in the embodiment of the second aspect.
  • the processor 1801 may be configured to perform the following control: after the RRC connection of the MT of the mobile node is migrated from the first donor-CU to the third donor-CU, receive the A transmission migration modification request, wherein the transmission migration modification request is used to request the release of transmission resources of the service; and a transmission migration modification response is sent to the first donor-CU.
  • the processor 1801 may be configured to execute a program to implement the configuration method of a mobile node as in the embodiment of the third aspect.
  • the processor 1801 may be configured to perform the following control: the F1 terminating donor-CU of the mobile node is changed from the fourth donor-CU to the fifth donor-CU, according to the first location-related information of the mobile node, Reconfiguring second information related to the first cell for the DU of the mobile node; and sending the reconfigured second information related to the first cell to the DU of the mobile node.
  • the IAB device 1800 may also include: a transceiver 1803, an antenna 1804, 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 1800 does not necessarily include all components shown in FIG. 18 ; in addition, the IAB device 1800 may also include components not shown in FIG. 18 , and reference may be made to the prior art.
  • Embodiments of the present application also provide a computer-readable program, wherein when the program is executed in an IAB device, the program causes the computer to execute the mobile node in the embodiment of the first or third aspect in the IAB device.
  • the configuration method, or the communication method of the mobile node in the embodiment of the second aspect are examples of the configuration method, or the communication method of the mobile node in the embodiment of the second aspect.
  • Embodiments of the present application also provide a storage medium storing a computer-readable program, wherein the computer-readable program causes the computer to execute the configuration method of the mobile node in the embodiment of the first or third aspect in the IAB device, or The communication method of the mobile node in the embodiment of the second aspect.
  • 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 configuration method for a mobile node comprising:
  • the first donor-CU reconfigures the distribution unit (DU) of the mobile node with second information related to the first cell based on the first information related to the location of the mobile node;
  • the first donor-CU sends the reconfigured second information related to the first cell to the second donor-CU; wherein the reconfigured second information related to the first cell is used by the second donor-CU.
  • donor-CU sends the DU to the mobile node.
  • the first donor-CU is a non-F1-terminating donor-CU (non-F1-terminating donor-CU) of the mobile node; the second donor-CU F1-terminating donor-CU (F1-terminating donor-CU) for the mobile node.
  • the second information includes at least one of the following: physical cell identity (PCI), NR cell global identity (NCGI), tracking area code (TAC) , Physical Random Access Channel (PRACH) resource configuration.
  • PCI physical cell identity
  • NCGI NR cell global identity
  • TAC tracking area code
  • PRACH Physical Random Access Channel
  • the first information includes: second information related to the second cell detected and reported by the mobile terminal (MT), and/or, the The location information of the mobile node or the cell information accessed by the MT.
  • the first donor-CU receives the second information related to the first cell currently configured in the DU of the mobile node sent by the second donor-CU.
  • the first donor-CU determines that the second information related to the first cell needs to be reconfigured based on the first information and the currently configured second information related to the first cell.
  • the physical cell identity (PCI) reconfigured for the first cell of the DU of the mobile node does not conflict with the PCI of the adjacent cell.
  • the NR Cell Global Identity (NCGI) of the first cell reconfiguration of the mobile node's DU is related to the NCGI of the neighboring cell
  • the Tracking Area Code (TAC) of the first cell reconfiguration of the DU of the mobile node is related to the neighboring cell.
  • the TACs are the same or related, and the PRACH resources reconfigured for the first cell of the DU of the mobile node do not conflict with the PRACH resources of adjacent cells.
  • the first donor-CU sends a transmission migration modification request to the second donor-CU; wherein the transmission migration modification request is used to request the release of transmission resources of the service;
  • the first donor-CU receives the transmission migration modification response sent by the second donor-CU.
  • the mobile node receives the IP address and BAP layer address allocated by the third donor-CU; wherein the IP address and BAP layer address allocated by the third donor-CU are carried by an RRC reconfiguration message; and,
  • the DU of the mobile node reports the IP address selected from the IP addresses allocated by the third donor-CU to the second donor-CU through a gNB DU configuration update message.
  • a method for configuring a mobile node comprising:
  • the second donor-CU receives the second information related to the first cell of the mobile node's DU sent by the first donor-CU; wherein the second information is provided by the first donor-CU according to the mobile node's
  • the first location-related information is the DU reconfiguration of the mobile node
  • the second donor-CU sends the reconfigured second information related to the first cell to the DU of the mobile node.
  • the first donor-CU is a non-F1-terminating donor-CU (non-F1-terminating donor-CU) of the mobile node; the second donor-CU F1-terminating donor-CU (F1-terminating donor-CU) for the mobile node.
  • the first F1AP message includes an F1 establishment response message or a gNB CU configuration update message.
  • the second information includes at least one of the following: physical cell identity (PCI), NR cell global identity (NCGI), tracking area code (TAC) , Physical Random Access Channel (PRACH) resource configuration.
  • PCI physical cell identity
  • NCGI NR cell global identity
  • TAC tracking area code
  • PRACH Physical Random Access Channel
  • the first information includes: second information related to the second cell detected and reported by the MT, and/or the mobile node's Location information or cell information accessed by the MT.
  • the second donor-CU sends the second information related to the first cell currently configured in the DU of the mobile node to the first donor-CU.
  • the second donor-CU receives the first cell information for DU reconfiguration of the mobile node sent by the third donor-CU;
  • the second donor-CU sends the reconfigured first cell information to the DU of the mobile node.
  • the second donor-CU receives the transmission migration modification request sent by the first donor-CU, wherein the transmission migration modification request is used to request the release of transmission resources of the service;
  • the second donor-CU sends a transmission migration modification response to the first donor-CU.
  • the second donor-CU receives the DU of the mobile node reported through the gNB DU configuration update message and selects an IP address to be used from the IP addresses allocated by the third donor-CU;
  • the mobile node receives the IP address and BAP layer address allocated by the third donor-CU, and the IP address and BAP layer address allocated by the third donor-CU are carried by an RRC reconfiguration message.
  • the second donor-CU determines the third donor-CU according to the IP address reported by the mobile node, and sends a transmission migration management request to the third donor-CU, wherein the transmission migration management request Transport resources used to request the establishment of services;
  • the second donor-CU receives the transmission migration management response sent by the third donor-CU.
  • the fifth donor-CU reconfigures the second information related to the first cell for the DU of the mobile node based on the first information related to the location of the mobile node;
  • the fifth donor-CU sends the reconfigured second information related to the first cell to the DU of the mobile node.
  • the second information includes at least one of the following: physical cell identity (PCI), NR cell global identity (NCGI), tracking area code (TAC) , Physical Random Access Channel (PRACH) resource configuration.
  • PCI physical cell identity
  • NCGI NR cell global identity
  • TAC tracking area code
  • PRACH Physical Random Access Channel
  • the first information includes: second information related to the second cell detected and reported by the mobile terminal, and/or the mobile node location information or cell information currently accessed by the MT.
  • the fifth donor-CU receives the second information of the currently configured first cell sent by the DU of the mobile node through a third F1AP message.
  • the fifth donor-CU determines that the second information related to the first cell needs to be reconfigured based on the first information and the currently configured second information related to the first cell.
  • a communication method for a mobile node wherein the first donor-CU is a non-F1 terminated donor-CU before migration or radio link failure (RLF) recovery of the mobile node, and the second donor-CU is the mobile node.
  • the method After the RRC connection of the MT of the mobile node is migrated from the first donor-CU to the third donor-CU, the method includes:
  • the second donor-CU receives the transmission migration modification request sent by the first donor-CU, wherein the transmission migration modification request is used to request the release of transmission resources of the service;
  • the second donor-CU sends a transmission migration modification response to the first donor-CU.
  • the DU of the mobile node reports the IP address selected from the IP addresses allocated by the third donor-CU to the second donor-CU through a gNB DU configuration update message.
  • the second donor-CU determines the third donor-CU according to the IP address reported by the mobile IAB node, and sends a transmission migration management request to the third donor-CU, wherein the transmission migration management Requesting transport resources for requesting the establishment of services;
  • the second donor-CU receives the transmission migration management response sent by the third donor-CU.
  • the transmission migration management request sent by the third donor-CU includes the Xn interface identifier assigned by the third donor-CU to the mobile node.
  • An IAB host (donor) device comprising a memory and a processor, the memory storing a computer program, wherein the processor is configured to execute the computer program to implement any one of appendices 1 to 36

Abstract

本申请实施例提供了一种移动节点的配置方法和宿主设备。所述方法包括：第一donor-CU根据移动节点的第一信息，为所述移动节点重配置移动区域内的第二信息；第二donor-CU接收第一donor-CU发送的为所述移动节点重配置的第二信息，并发送给所述移动节点的DU。

Description

移动节点的配置方法和宿主设备 技术领域
本申请实施例涉及通信领域。
背景技术
未来无缝的蜂窝网络部署需要非常灵活和超密集的新无线(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节点的标识与其位置相关，但是在移动场景下移动节点的小区信息可能与相邻小区冲突，从而使得网络无法支持多个移动节点同时工作。
为了解决上述问题的至少之一，本申请实施例提供一种移动节点的配置方法和宿主设备。
根据本申请实施例的一方面，提供一种移动节点的配置方法，所述方法包括：
第一donor-CU根据移动节点的与位置相关的第一信息，为所述移动节点的分布单元(DU)重配置与第一小区相关的第二信息；以及
所述第一donor-CU向第二donor-CU发送所述重配置的与第一小区相关的第二信息；其中，所述重配置的与第一小区相关的第二信息被所述第二donor-CU发送给所述移动节点的DU。
根据本申请实施例的另一方面，提供一种宿主设备，包括：
配置部，其根据移动节点的与位置相关的第一信息，为所述移动节点的分布单元(DU)重配置与第一小区相关的第二信息；以及
通信部，其向第二donor-CU发送所述重配置的与第一小区相关的第二信息；其中，所述重配置的与第一小区相关的第二信息被所述第二donor-CU发送给所述移动节点的DU。
根据本申请实施例的另一方面，提供一种移动节点的配置方法，所述方法包括：
第二donor-CU接收第一donor-CU发送的与移动节点的DU的第一小区相关的第二信息；其中，所述第二信息由所述第一donor-CU根据所述移动节点的与位置相关的第一信息，为所述移动节点的DU重配置；以及
所述第二donor-CU将所述重配置的与第一小区相关的第二信息发送给所述移动节点的DU。
根据本申请实施例的另一方面，提供一种宿主设备，包括：
接收部，其接收第一donor-CU发送的与移动节点的DU的第一小区相关的第二信息；其中，所述第二信息由所述第一donor-CU根据所述移动节点的与位置相关的第一信息，为所述移动节点的DU重配置；以及
发送部，其将所述重配置的与第一小区相关的第二信息发送给所述移动节点的DU。
根据本申请实施例的另一方面，提供一种移动节点的配置方法，所述移动节点的F1终止donor-CU从第四donor-CU改变到第五donor-CU，所述方法包括：
所述第五donor-CU根据所述移动节点的与位置相关的第一信息，为所述移动节点的DU重配置与第一小区相关的第二信息；以及
所述第五donor-CU将重配置的所述与第一小区相关的第二信息发送给所述移动节点的DU。
根据本申请实施例的另一方面，提供一种宿主设备，移动节点的F1终止donor-CU从第四donor-CU改变到所述宿主设备，所述宿主设备包括：
配置部，其根据所述移动节点的与位置相关的第一信息，为所述移动节点的DU重配置与第一小区相关的第二信息；以及
通信部，将重配置的所述与第一小区相关的第二信息发送给所述移动节点的DU。
本申请实施例的有益效果之一在于：第一donor-CU根据移动节点的第一信息，为所述移动节点重配置移动区域内的第二信息；第二donor-CU接收第一donor-CU发 送的为所述移动节点重配置的第二信息，并发送给所述移动节点的DU。由此，第一donor-CU能够根据节点的实时位置信息，动态地为移动节点配置在移动区域内的小区信息；从而可以避免该移动IAB节点与相邻小区冲突，使得网络支持多个移动节点同时工作。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附附记的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部分，用于例示本申请的实施方式，并与文字描述一起来阐释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。在附图中：
图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是移动性场景的另一示意图；
图10是本申请实施例的移动节点的配置方法的一示意图；
图11是本申请实施例的移动节点的配置方法的一示例图；
图12是本申请实施例的移动节点的通信方法的一示意图；
图13是本申请实施例的传输迁移的一信令流程图；
图14是本申请实施例的移动节点的配置方法的一示意图；
图15是本申请实施例的移动节点的配置方法的一示例图；
图16是本申请实施例的宿主设备的一示意图；
图17是本申请实施例的宿主设备的另一示意图；
图18是本申请实施例的IAB设备的一示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附附记的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如新无线(NR，New Radio)、长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及未来的5G、6G等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备，也可以称为“终端设备”(TE，Terminal Equipment)。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
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信道映射。
Rel-17 NR已经对IAB节点静止时的场景进行了研究，对静止IAB-node在F1终止(F1-terminating)donor-CU下的不同donor-DU之间改变传输路径(或称为拓扑自适应，topology adaptation)过程，以及在F1-terminating donor-CU和non-F1-terminating donor-CU之间改变传输路径的流程进行了标准化。Rel-18NR将针对移动性场景进行研究。
图8是移动性场景的一示意图。如图8所示，例如，在移动的车辆上装载IAB节 点801用于服务车上用户设备。因此，需要对移动IAB节点在多个不同donor-CU之间移动时改变传输路径的流程进行标准化。
对于静止IAB节点，其服务小区的物理小区标识(PCI)和物理随机接入信道(PRACH)资源配置可以固定不变，因为网络侧能够根据其固定位置确定其服务小区的邻小区(例如宏小区或其他IAB节点的服务小区)，从而控制其服务小区的PCI或PRACH资源和周围邻小区的PCI或PRACH资源不冲突。
图9是移动性场景的另一示意图。如图9所示，移动IAB节点因为移动性，运动轨迹可能涉及多个不同donor-CU的控制区域，固定PCI、固定PRACH资源的方式对移动IAB节点不可行，因为如果移动IAB节点的PCI或PRACH资源固定，网络侧必须保证其移动轨迹涉及的邻小区不能配置有相同的PCI或PRACH资源。在较多移动IAB节点的情况下，可供其他小区使用的资源将大大减少，使得网络侧无法支持多个移动IAB节点同时工作。
因此，可行的解决方案是网络侧根据IAB节点的移动位置动态配置其服务小区的PCI或PRACH资源，以避免与其所在位置的邻小区资源发生冲突。但是，目前没有技术支持针对IAB节点的动态的PCI或PRACH资源配置。
另一方面，接入小区的UE的位置可以由服务小区的NR小区全局标识(NCGI，NR cell global Identifier)和跟踪区域(TA，tracking area)决定，核心网通常根据UE服务小区的NCGI和TA定位UE，因此，服务小区的NCGI和TA由网络侧根据小区所在的位置配置。
对于静止IAB节点，网络侧可以根据其位置固定配置其服务小区的NCGI和TA。但移动IAB节点因为移动性，运动轨迹可能涉及多个不同donor-CU控制区域，其服务小区的位置在网络中是变化的。固定NCGI和TA的方式对移动IAB节点不可行，因为固定的NCGI和TA不能反映出移动IAB节点的服务小区的实际位置，从而不能反映接入小区的UE的实际位置，使网络侧无法获取接入移动IAB节点的UE的实际位置。
因此，可行的解决方案是网络侧根据IAB节点的移动位置动态配置其服务小区的NCGI和TA，以反映接入小区的UE的实际位置。但是，目前没有技术支持动态的NCGI配置和/或TA配置。
在本申请实施例中，在没有特别说明的情况下，IAB节点设备包括迁移节点或其子节点。此外，以上以PCI、NCGI、TA和PRACH资源为例对第二信息进行了说明， 但本申请不限于此，例如还可以是与移动IAB节点相关的其他信息。本申请实施例也不限于IAB节点，例如针对网络控制转发器(NCR，Network-controlled repeater)同样适用。
以下对本申请实施例进行进一步说明。
第一方面的实施例
本申请实施例提供一种移动节点的配置方法，第一donor-CU是该移动节点的非F1终止dornor-CU(non-F1-terminating donor-CU)；第二donor-CU为所述移动节点的F1终止dornor-CU(F1-terminating donor-CU)。
图10是本申请实施例的移动节点的配置方法的一示意图，如图10所示，该方法包括：
1001，第一donor-CU根据移动节点的与位置相关的第一信息，为所述移动节点的分布单元(DU)重配置与第一小区相关的第二信息；
1002，第一donor-CU向第二donor-CU发送所述重配置的与第一小区相关的第二信息；其中，所述重配置的与第一小区相关的第二信息被所述第二donor-CU发送给所述移动节点的DU。
由此，本申请实施例的第一donor-CU(non-F1-terminating donor-CU)能够根据移动节点的第一信息(实时位置信息)，动态地为移动节点配置在移动区域内的第二信息；从而可以避免该移动节点与相邻小区冲突，从而使得网络支持多个移动节点同时工作。
值得注意的是，以上附图10仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图10的记载。
在一些实施例中，所述第一donor-CU通过XnAP消息向所述第二donor-CU发送重配置的所述第二信息，所述第二donor-CU通过第一F1AP消息将重配置的所述第二信息发送给所述移动节点的DU。
例如，所述第一F1AP消息包括F1建立响应消息或gNB CU配置更新消息。
在一些实施例中，所述第二信息包括如下至少之一：物理小区标识(PCI)、NR小区全局标识(NCGI)、跟踪区域码(TAC)、物理随机接入信道(PRACH)资源配 置。本申请不限于此，例如可以包括以上信息的一个或多个，也可以包括其他的信息。
在一些实施例中，所述第一信息包括：移动终端(MT)检测并上报的与第二小区相关的第二信息，和/或，所述移动节点的位置信息或MT所接入的小区信息。
例如，根据IAB节点的MT接入的服务小区，non-F1-terminating donor-CU可以为移动IAB节点的DU配置PCI、NCGI、TAC和PRACH资源；non-F1-terminating donor-CU可以将配置的这些信息发送给F1-terminating donor-CU，由F1-terminating donor-CU将这些配置信息使用F1AP消息发送给移动IAB节点的DU。这样，可使移动IAB节点的PCI和PRACH资源与邻小区不冲突，以及使移动IAB节点的NCGI和TAC根据其实际地理位置改变，网络能够获取接入移动IAB节点的UE的实际位置信息。
再例如，接入non-F1-terminating donor-CU的移动终端(包括移动IAB节点的MT)可以检测移动IAB节点的DU的邻小区(例如移动IAB节点的MT接入的服务小区)的PCI、NCGI、TAC和PRACH配置，并将这些配置上报给non-F1-terminating donor-CU。根据这些信息，non-F1-terminating donor-CU可以为移动IAB节点的DU配置PCI、NCGI、TAC和PRACH资源；non-F1-terminating donor-CU可以将配置的这些信息发送给F1-terminating donor-CU，由F1-terminating donor-CU将这些配置信息使用F1AP消息发送给移动IaB节点的DU。这样，可使移动IAB节点的PCI和PRACH资源与邻小区不冲突，以及使移动IAB节点的NCGI和TAC根据其实际地理位置改变，网络能够获取接入移动IAB节点的UE的实际位置信息。
在一些实施例中，在所述第一donor-CU为所述移动节点的DU重配置与第一小区相关的第二信息之前，所述第一donor-CU接收所述第二donor-CU发送的所述移动节点的DU当前配置的与第一小区相关的第二信息。
在一些实施例中，所述第一donor-CU根据所述第一信息和所述当前配置的与第一小区相关的第二信息，确定需要重配置所述与第一小区相关的第二信息。
在一些实施例中，所述移动节点的非F1终止donor-CU从所述第一donor-CU改变到第三donor-CU。
在一些实施例中，为所述移动节点的DU的第一小区重配置的物理小区标识(PCI)与相邻小区的PCI不冲突，为所述移动节点的DU的第一小区重配置的NR小区全局标识(NCGI)与相邻小区的NCGI相关，为所述移动节点的DU的第一小区重配置的跟踪区域码(TAC)与相邻小区的TAC相同或相关，为所述移动节点的DU的第 一小区重配置的PRACH资源与相邻小区的PRACH资源不冲突。
图11是本申请实施例的移动节点的配置方法的一示例图。如图11所示，IAB节点与donor-CU1建立有F1连接，并且在一定区域范围内不改变F1-terminating CU。
当IAB节点的MT移动到donor-DU2服务小区时，IAB-MT切换到donor-CU2，F1传输路径迁移到donor-DU2，donor-CU2成为non-F1-terminating donor-CU。此时，donor-CU2根据IAB节点的位置(父节点的服务小区PCI＝1，TAC＝A，NCGI＝k)，或者，根据IAB节点检测并通过RRC上报的PCI(邻小区PCI＝1)，为IAB节点的服务小区配置的PCI为2，TAC为A，NCGI＝k+1。donor-CU2通过XnAP消息将该配置指示给donor-CU1，donor-CU1使用F1AP消息(GNB-CU CONFIGURATION UPDATE)该配置发送给IAB节点。
由此，父节点的服务小区PCI＝1而IAB节点的服务小区的PCI为2，二者之间不同，这可使移动IAB节点的PCI与邻小区不冲突。父节点的服务小区TAC＝A且NCGI＝k，IAB节点的服务小区的TAC＝A且NCGI＝k+1，二者之间相同或相关，网络能够获取接入移动IAB节点的UE的实际位置信息。
当IAB节点MT移动到donor-DU3服务小区时，IAB-MT切换到donor-CU3，F1传输路径迁移到donor-DU3，donor-CU3变成non-F1-terminating CU。此时，donor-CU3根据IAB节点的位置(父节点的服务小区PCI＝2，TAC＝B，NCGI＝m)，为IAB节点的服务小区配置的PCI为1，TAC为B，NCGI＝m+1，并通过XnAP消息将该配置指示给donor-CU1，donor-CU1使用F1AP消息(GNB-CU CONFIGURATION UPDATE)将该配置发送给IAB节点。
由此，父节点的服务小区PCI＝2而IAB节点的服务小区的PCI为1，二者之间不同，这可使移动IAB节点的PCI与邻小区不冲突。父节点的服务小区TAC＝B且NCGI＝m，IAB节点的服务小区的TAC＝B且NCGI＝m+1，二者之间相同或相关，网络能够获取接入移动IAB节点的UE的实际位置信息。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，第一donor-CU根据移动节点的第一信息，为所述移动节点重配置移动区域内的第二信息；第二donor-CU接收第一donor-CU发送的为所述移动节点重配置的第二信息，并发送给所述移动节点的DU。由此，第一donor-CU能 够根据节点的实时位置信息，动态地为移动节点配置在移动区域内的小区信息；从而可以避免该移动IAB节点与相邻小区冲突，使得网络支持多个移动节点同时工作。
第二方面的实施例
本申请实施例提供一种移动节点的通信方法，可以与第一方面的实施例结合起来，也可以单独地实施，与第一方面的实施例相同的内容不再赘述。
Rel-17支持IAB节点F1-terminating donor-CU和non-F1-terminating donor-CU之间改变传输路径的流程。但是，移动节点在移动过程中不改变F1-terminating CU，根据其移动位置可能会不断改变non-F1-terminating donor-CU，将传输路径迁移到最新non-F1-terminating donor-CU下的donor-DU，本申请实施例对此进行说明。
在本申请实施例中，第一donor-CU为所述移动节点迁移或者无线链路失败(RLF)恢复前的非F1终止dornor-CU，第二donor-CU为所述移动节点的F1终止dornor-CU，第三donor-CU为所述移动节点迁移或者无线链路失败(RLF)恢复后的非F1终止dornor-CU。
图12是本申请实施例的移动节点的通信方法的一示意图，如图12所示，所述移动节点的MT的RRC连接由所述第一donor-CU迁移到所述第三donor-CU后，该方法包括：
1201，第二donor-CU接收第一donor-CU发送的传输迁移修改请求，其中，所述传输迁移修改请求用于请求释放业务的传输资源；
1202，所述第二donor-CU向所述第一donor-CU发送传输迁移修改响应。
值得注意的是，以上附图12仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图12的记载。
在一些实施例中，所述移动节点接收所述第三donor-CU分配的IP地址和BAP层地址；所述第三donor-CU分配的IP地址和BAP层地址由RRC重配置消息承载；以及所述移动节点的DU通过gNB DU配置更新消息向所述第二donor-CU上报从由所述第三donor-CU分配的IP地址中选择使用的IP地址。
在一些实施例中，所述第二donor-CU根据所述移动节点上报的所述IP地址确定所述第三donor-CU，并向所述第三donor-CU发送传输迁移管理请求，所述传输迁移 管理请求用于请求建立业务的传输资源；以及所述第二donor-CU接收所述第三donor-CU发送的传输迁移管理响应。
在一些实施例中，所述第二donor-CU接收的由所述第一donor-CU发送的传输迁移修改请求和所述第二donor-CU向所述第三donor-CU发送的所述传输迁移管理请求中包括所述第三donor-CU为所述移动节点分配的Xn接口标识。这样，所述第三donor-CU收到所述传输迁移管理请求时能通过Xn接口标识识别所述移动IAB节点。
在一些实施例中，所述移动节点的DU通过所述gNB DU配置更新消息向所述第二donor-CU上报由所述第三donor-CU为所述移动节点分配的BAP层地址；以及，所述第二donor-CU向所述第三donor-CU发送的所述传输迁移管理请求中包括所述BAP层地址。这样，所述第三donor-CU收到所述传输迁移管理请求时能通过BAP层地址识别所述移动IAB节点。
以下再通过信令交互进一步示例性说明本申请实施例的传输迁移过程。
图13是本申请实施例的传输迁移的一信令流程图。在图13中，F1donor-CU为上述的第二donor-CU，源路径的原non-F1donor-CU为上述的第一donor-CU，目标路径下的新non-F1donor-CU为上述的第三donor-CU。
如图13所示，该流程包括：
1301，IAB-MT和UE一样从原non-F1-terminating CU切换到新non-F1-terminating CU。这个过程中新non-F1-terminating CU会为IAB-IMT分配UE XnAP ID，以及通过RRC消息为IAB-DU分配在目标路径上传输non-UP业务的IP地址。
1302，在完成IAB-MT切换后，原non-F1-terminating CU释放原路径上的BH RLC信道和BAP子层的路由。
1303，原non-F1-terminating CU发送IAB TRANSPORT MIGRATION MODIFICATION REQUEST消息给F1-terminating CU，以请求业务在原路径上的释放。
其中，释放的业务信息中包含释放所有的业务指示(full release indication)，并指示新Non-F1-Terminating donor UE XnAP ID。新的Non-F1-Terminating donor UE XnAP ID是1301中新non-F1-terminating CU侧为IAB节点分配的UE标识，这样，1307中F1-terminating CU向新non-F1-terminating CU发送消息时，新non-F1-terminatig CU可以索引到相关的IAB-MT。
1304，F1-terminating CU发送IAB TRANSPORT MIGRATION MODIFICATION RESPONSE消息确认对释放所有业务的请求。
1305，新non-F1-terminating CU为目标路径上的节点配置BH RLC信道和BAP子层路由，以及对donor-DU的DL mapping的配置。这些配置是为了支持F1-C在目标路径上的传输。
1306，F1-C连接应用1301中分配的IP地址，IAB-DU通过gNB-DU CONFIGURATION UPDATE消息向F1-terminating CU上报实际使用的IP地址。
1307，F1-terminating CU通过IAB-DU上报的IP地址确定新non-F1-terminating CU，并向新non-F1-terminating CU发送IAB TRANSPORT MIGRATION MANAGEMENT REQUST消息，包含请求迁移的业务的上下文信息，也可能包括新non-F1-terminating donor-CU用来给donor-DU配置下行mapping的DL TNL信息。
1308，新non-F1-terminating donor-CU为目标路径上的节点配置或修改BH RLC信道和BAP子层路由，以及对donor-DU的DL mapping的配置。这些配置是为了支持F1-U和non-UP业务在目标路径上的传输。
1309，新non-F1-terminating CU向F1-terminating CU发送IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE消息，包含1307中请求的业务在新non-F1-terminating拓扑域中的层2信息(routing ID,BH RLC channel，下一跳BAP地址)，可能还包含用于传输下行non-UP业务的DSCP/IPv6 flow label。
1310，F1-U开始使用新non-F1-terminating CU分配的IP地址。F1-terminating CU根据1309中收到的业务的层二信息向IAB-DU配置更新的UL BH信息。
1311，重复1307至1310。
以上信令过程仅示意性对本申请实施例进行了说明，但本申请不限于此，关于信令的更具体的内容，还可以参考相关技术。此外，例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图13的记载。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，移动节点在移动过程中不改变F1-terminating CU，根据其移动位置可以不断改变non-F1-terminating donor-CU，将传输路径迁移到最新non-F1- terminating donor-CU下的donor-DU。由此，能够更好地支持移动场景，并进一步提升移动IAB节点的服务稳定性。
第三方面的实施例
本申请实施例提供一种移动节点的配置方法，移动节点的F1终止donor-CU从第四donor-CU改变到第五donor-CU。
图14是本申请实施例的移动节点的配置方法的一示意图，如图14所示，该方法包括：
1401，第五donor-CU根据所述移动节点的与位置相关的第一信息，为所述移动节点的DU重配置与第一小区相关的第二信息；
1402，所述第五donor-CU将重配置的所述与第一小区相关的第二信息发送给所述移动节点的DU。
由此，本申请实施例的第五donor-CU(F1-terminating donor-CU)能够根据移动节点的实时位置信息，动态地为移动节点配置在移动区域内的小区信息；从而可以避免该移动节点与相邻小区冲突，使得网络支持多个移动节点同时工作。
值得注意的是，以上附图14仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图14的记载。
在一些实施例中，所述第五donor-CU通过第二F1AP消息将重配置的所述与第一小区相关的第二信息发送给所述移动节点的DU。
例如，所述第二F1AP消息包括F1建立响应消息或gNB CU配置更新消息。
在一些实施例中，所述第二信息包括如下至少之一：物理小区标识(PCI)、NR小区全局标识(NCGI)、跟踪区域码(TAC)、物理随机接入信道(PRACH)资源配置。本申请不限于此，例如可以包括以上信息的一个或多个，也可以包括其他的信息。
在一些实施例中，所述第一信息包括：由移动终端(MT)检测并上报的与第二小区相关的第二信息，和/或，所述移动节点的位置信息或MT当前接入的小区信息。
例如，根据由当前移动IAB节点的MT接入的服务小区，或者根据移动IAB节点在核心网注册的位置信息或网络定位信息，F1-terminating donor-CU可以为移动IAB节点配置PCI、NCGI和TA；并将这些配置信息使用F1AP消息发送给移动IaB 节点。这样，可使移动IAB节点的PCI与邻小区不冲突，以及使移动IAB节点的NCGI和TA根据其实际地理位置改变，网络能够获取接入移动IAB节点的UE的实际位置信息。
再例如，IAB节点的MT或IAB节点的DU服务的MT可以检测邻小区(例如IAB节点的MT接入的服务小区)的PCI配置，并将这些PCI配置上报给F1-terminating donor-CU。根据这些信息，F1-terminating donor-CU可以为移动IAB节点配置PCI、NCGI和TA；并将这些配置信息使用F1AP消息发送给移动IaB节点。这样，可使移动IAB节点的PCI与邻小区不冲突，以及使移动IAB节点的NCGI和TA根据其实际地理位置改变，网络能够获取接入移动IAB节点的UE的实际位置信息。
在一些实施例中，在所述第五donor-CU为所述移动节点的DU重配置与第一小区相关的第二信息之前，所述第五donor-CU接收所述移动节点的DU通过第三F1AP消息发送的当前配置的所述第一小区的第二信息。
例如，所述第三F1AP消息包括F1建立请求消息或gNB DU配置更新消息。
在一些实施例中，所述第五donor-CU根据所述第一信息和所述当前配置的与第一小区相关的第二信息，确定需要重配置所述与第一小区相关的第二信息。
在一些实施例中，为所述移动节点的DU的第一小区重配置的物理小区标识(PCI)与相邻小区的PCI不冲突，为所述移动节点的DU的第一小区重配置的NR小区全局标识(NCGI)与相邻小区的NCGI相关，为所述移动节点的DU的第一小区重配置的跟踪区域码(TAC)与相邻小区的TAC相同或相关，为所述移动节点的DU的第一小区重配置的PRACH资源与相邻小区的PRACH资源不冲突。
图15是本申请实施例的移动节点的配置方法的一示例图。如图15所示，假设IAB节点一开始与donor-CU1建立有F1连接，F1传输路径经过donor-DU1。此时，donor-CU1根据IAB节点的位置(父节点的服务小区PCI＝1，TAC＝A，NCGI＝k)，为IAB节点的服务小区配置的PCI为2，TAC为A，NCGI＝k+1，并用F1AP消息配置给IAB节点。
由此，父节点的服务小区PCI＝1而IAB节点的服务小区的PCI为2，二者之间不同，这可使移动IAB节点的PCI与邻小区不冲突。父节点的服务小区TAC＝A且NCGI＝k，IAB节点的服务小区的TAC＝A且NCGI＝k+1，二者之间相同或相关，网络能够获取接入移动IAB节点的UE的实际位置信息。
当IAB节点MT移动到donor-DU2服务小区时，IAB-MT切换到donor-CU2，F1 传输路径迁移到donor-DU2。此时，IAB节点与donor-CU2建立F1连接。IAB节点可以通过F1连接建立请求F1AP消息向donor-CU2上报当前的PCI＝2，donor-CU2根据IAB节点当前接入的父节点(父节点的服务小区PCI＝2)确定其实时位置并确定其PCI与父节点的服务小区冲突，然后donor-CU2可以通过F1连接建立响应F1AP消息为IAB节点重配置PCI＝1。
此外，donor-CU2根据IAB节点当前接入的父节点(父节点的服务小区配置，TAC为B，NCGI＝m+1)，为IAB节点的服务小区配置TAC为B，NCGI＝m+1，并用F1连接建立响应F1AP消息配置给IAB节点。
由此，父节点的服务小区PCI＝2而IAB节点的服务小区的PCI为1，二者之间不同，这可使移动IAB节点的PCI与邻小区不冲突。父节点的服务小区TAC＝B且NCGI＝m，IAB节点的服务小区的TAC＝B且NCGI＝m+1，二者之间相同或相关，网络能够获取接入移动IAB节点的UE的实际位置信息。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，第五donor-CU(F1-terminating donor-CU)根据移动节点的第一信息，为所述移动节点配置移动区域内的第二信息，并将配置的信息发送给所述移动节点的DU。由此，第五donor-CU能够根据移动节点的实时位置信息，动态地为移动节点配置在移动区域内的小区信息；从而可以避免该移动节点与相邻小区冲突，使得网络支持多个移动节点同时工作。
第四方面的实施例
本申请实施例提供一种宿主设备，与第一至三方面的实施例相同的内容不再赘述。
在一些实施例中，该设备例如可以是IAB系统中的IAB donor-CU(如第一、二方面的实施例中的第一donor-CU)，也可以是配置于该IAB donor-CU中的某个或某些部件或者组件或者模块。
图16是本申请实施例的宿主设备的一示意图。如图16所示，宿主设备1600包括：
配置部1601，其根据移动节点的与位置相关的第一信息，为所述移动节点的分布单元(DU)重配置与第一小区相关的第二信息；以及
通信部1602，其向第二donor-CU发送所述重配置的与第一小区相关的第二信息；其中，所述重配置的与第一小区相关的第二信息被所述第二donor-CU发送给所述移动节点的DU。
在一些实施例中，所述宿主设备为所述移动节点的非F1终止dornor-CU(non-F1-terminating donor-CU)；所述第二donor-CU为所述移动节点的F1终止dornor-CU(F1-terminating donor-CU)。
在一些实施例中，所述通信部1602通过XnAP消息向所述第二donor-CU发送重配置的所述第二信息，所述第二donor-CU通过第一F1AP消息将重配置的所述第二信息发送给所述移动节点的DU。
在一些实施例中，所述第一F1AP消息包括F1建立响应消息或gNB CU配置更新消息。
在一些实施例中，所述第二信息包括如下至少之一：物理小区标识(PCI)、NR小区全局标识(NCGI)、跟踪区域码(TAC)、物理随机接入信道(PRACH)资源配置。
在一些实施例中，所述第一信息包括：由移动终端(MT)检测并上报的与第二小区相关的第二信息，和/或，所述移动节点的位置信息或MT所接入的小区信息。
在一些实施例中，在所述配置部1601为所述移动节点的DU重配置与第一小区相关的第二信息之前，所述通信部1602接收所述第二donor-CU发送的所述移动节点的DU当前配置的与第一小区相关的第二信息。
在一些实施例中，所述配置部1601根据所述第一信息和所述当前配置的与第一小区相关的第二信息，确定需要重配置所述与第一小区相关的第二信息。
在一些实施例中，所述移动节点的非F1终止donor-CU从所述第一donor-CU改变到第三donor-CU；
在所述移动节点的MT的RRC连接由所述第一donor-CU迁移到所述第三donor-CU后，所述通信部1602向所述第二donor-CU发送传输迁移修改请求，其中，所述传输迁移修改请求用于请求释放业务的传输资源；并接收所述第二donor-CU发送的传输迁移修改响应。
在一些实施例中，为所述移动节点的DU的第一小区重配置的物理小区标识(PCI)与相邻小区的PCI不冲突，为所述移动节点的DU的第一小区重配置的NR小区全局标识(NCGI)与相邻小区的NCGI相关，为所述移动节点的DU的第一小区重配置 的跟踪区域码(TAC)与相邻小区的TAC相同或相关，为所述移动节点的DU的第一小区重配置的PRACH资源与相邻小区的PRACH资源不冲突。
在一些实施例中，该设备例如可以是IAB系统中的IAB donor-CU(如第一、二方面的实施例中的第二donor-CU)，也可以是配置于该IAB donor-CU中的某个或某些部件或者组件或者模块。
图17是本申请实施例的宿主设备的一示意图。如图17所示，宿主设备1700包括：
接收部1701，其接收第一donor-CU发送的与移动节点的DU的第一小区相关的第二信息；其中，所述第二信息由所述第一donor-CU根据所述移动节点的与位置相关的第一信息，为所述移动节点的DU重配置；以及
发送部1702，其将所述重配置的与第一小区相关的第二信息发送给所述移动节点的DU。
在一些实施例中，所述第一donor-CU为所述移动节点的非F1终止dornor-CU(non-F1-terminating donor-CU)；所述宿主设备为所述移动节点的F1终止dornor-CU(F1-terminating donor-CU)。
在一些实施例中，所述移动节点的非F1终止donor-CU从所述第一donor-CU改变到第三donor-CU；
所述接收部1701接收所述第三donor-CU发送的为所述移动节点DU重配置的第一小区信息；以及所述发送部1702将重配置的所述第一小区信息发送给所述移动节点的DU。
在一些实施例中，在所述移动节点MT的RRC连接由所述第一donor-CU迁移到第三donor-CU后，所述接收部1701接收所述第一donor-CU发送的传输迁移修改请求；其中，所述传输迁移修改请求用于请求释放业务的传输资源；所述发送部1702向所述第一donor-CU发送传输迁移修改响应。
在一些实施例中，所述接收部1701接收所述移动节点的DU通过gNB DU配置更新消息上报的从由所述第三donor-CU分配的IP地址中选择使用的IP地址；其中，所述移动节点接收所述第三donor-CU分配的IP地址和BAP层地址，所述第三donor-CU分配的IP地址和BAP层地址由RRC重配置消息承载。
在一些实施例中，所述发送部1702根据所述移动节点上报的所述IP地址确定所述第三donor-CU，并向所述第三donor-CU发送传输迁移管理请求，其中，所述传输 迁移管理请求用于请求建立业务的传输资源；以及所述接收部1701接收所述第三donor-CU发送的传输迁移管理响应。
在一些实施例中，该设备例如可以是IAB系统中的IAB donor-CU(如第三方面的实施例中的第五donor-CU)，也可以是配置于该IAB donor-CU中的某个或某些部件或者组件或者模块。该宿主设备的结构可如图16所示。
在一些实施例中，移动节点的F1终止donor-CU从第四donor-CU改变到所述宿主设备，配置部1601根据所述移动节点的与位置相关的第一信息，为所述移动节点的DU重配置与第一小区相关的第二信息；以及通信部1602将重配置的所述与第一小区相关的第二信息发送给所述移动节点的DU。
在一些实施例中，所述通信部1602通过第二F1AP消息将重配置的所述与第一小区相关的第二信息发送给所述移动节点的DU；
所述第二F1AP消息包括F1建立响应消息或gNB CU配置更新消息。
在一些实施例中，在所述配置部1601为所述移动节点的DU重配置与第一小区相关的第二信息之前，所述通信部1602接收所述移动节点的DU通过第三F1AP消息发送的当前配置的所述第一小区的第二信息；
所述第三F1AP消息包括F1建立请求消息或gNB DU配置更新消息。
在一些实施例中，所述配置部1601根据所述第一信息和所述当前配置的与第一小区相关的第二信息，确定需要重配置所述与第一小区相关的第二信息。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的宿主设备1600或1700还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图16或17中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，宿主设备根据移动节点的第一信息，为所述移动节点配置移动区域内的第二信息，并将配置的信息发送给所述移动节点的DU。由此，宿主设备 能够根据移动节点的实时位置信息，动态地为移动节点配置在移动区域内的小区信息；从而可以避免该移动节点与相邻小区冲突，使得网络支持多个移动节点同时工作。
第五方面的实施例
本申请实施例提供了一种通信系统，包括宿主(donor)设备和移动节点(例如IAB-node)；关于宿主(donor)设备、IAB节点的网络架构和具体内容还可以参考相关技术，此处省略说明。
在一些实施例中，IAB系统包括：第一donor-CU和第二donor-CU；所述第一donor-CU为所述移动节点的非F1终止dornor-CU(non-F1-terminating donor-CU)；所述第二donor-CU为所述移动节点的F1终止dornor-CU(F1-terminating donor-CU)。
第一donor-CU根据移动节点的与位置相关的第一信息，为所述移动节点的分布单元(DU)重配置与第一小区相关的第二信息；以及
所述第一donor-CU向第二donor-CU发送所述重配置的与第一小区相关的第二信息；其中，所述重配置的与第一小区相关的第二信息被所述第二donor-CU发送给所述移动IAB节点的IAB-DU。
在一些实施例中，IAB系统包括：第四donor-CU和第五donor-CU；所述移动节点的F1终止donor-CU从第四donor-CU改变到第五donor-CU。
第五donor-CU根据所述移动节点的与位置相关的第一信息，为所述移动节点的DU重配置与第一小区相关的第二信息；以及
所述第五donor-CU将重配置的所述与第一小区相关的第二信息发送给所述移动节点的DU。
本申请实施例还提供一种IAB设备，该IAB设备可以是IAB宿主设备，也可以是IAB节点设备(迁移节点或者子节点)。
图18是本申请实施例的IAB设备的示意图。如图18所示，IAB设备1800可以包括：处理器(例如中央处理器CPU)1801和存储器1802；存储器1802耦合到处理器1801。其中该存储器1802可存储各种数据；此外还存储信息处理的程序1805，并且在中央处理器1801的控制下执行该程序1805。
例如，处理器1801可以被配置为执行程序而实现如第一方面的实施例中的移动节点的配置方法。例如，处理器1801可以被配置为进行如下的控制：根据移动节点的与位置相关的第一信息，为所述移动节点的分布单元(DU)重配置与第一小区相 关的第二信息；以及向第二donor-CU发送所述重配置的与第一小区相关的第二信息；其中，所述重配置的与第一小区相关的第二信息被所述第二donor-CU发送给所述移动IAB节点的IAB-DU。
再例如，处理器1801可以被配置为执行程序而实现如第二方面的实施例中的移动节点的通信方法。例如，处理器1801可以被配置为进行如下的控制：移动节点的MT的RRC连接由所述第一donor-CU迁移到所述第三donor-CU后，接收所述第一donor-CU发送的传输迁移修改请求，其中，所述传输迁移修改请求用于请求释放业务的传输资源；向所述第一donor-CU发送传输迁移修改响应。
再例如，处理器1801可以被配置为执行程序而实现如第三方面的实施例中的移动节点的配置方法。例如，处理器1801可以被配置为进行如下的控制：移动节点的F1终止donor-CU从第四donor-CU改变到第五donor-CU，根据所述移动节点的与位置相关的第一信息，为所述移动节点的DU重配置与第一小区相关的第二信息；以及将重配置的所述与第一小区相关的第二信息发送给所述移动节点的DU。
此外，如图18所示，IAB设备1800还可以包括：收发机1803和天线1804等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，IAB设备1800也并不是必须要包括图18中所示的所有部件；此外，IAB设备1800还可以包括图18中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机可读程序，其中当在IAB设备中执行所述程序时，所述程序使得计算机在所述IAB设备中执行第一或第三方面的实施例中的移动节点的配置方法，或者第二方面的实施例中的移动节点的通信方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在IAB设备中执行第一或第三方面的实施例中的移动节点的配置方法，或者第二方面的实施例中的移动节点的通信方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。逻辑部件例如现场可编程逻辑部件、微处理器、计算机中使用的处理器等。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或 多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于本实施例公开的上述实施方式，还公开了如下的附记：
1.一种移动节点的配置方法，所述方法包括：
第一donor-CU根据移动节点的与位置相关的第一信息，为所述移动节点的分布单元(DU)重配置与第一小区相关的第二信息；以及
所述第一donor-CU向第二donor-CU发送所述重配置的与第一小区相关的第二信息；其中，所述重配置的与第一小区相关的第二信息被所述第二donor-CU发送给所述移动节点的DU。
2.根据附记1所述的方法，其中，所述第一donor-CU为所述移动节点的非F1 终止dornor-CU(non-F1-terminating donor-CU)；所述第二donor-CU为所述移动节点的F1终止dornor-CU(F1-terminating donor-CU)。
3.根据附记1或2所述的方法，其中，所述第一donor-CU通过XnAP消息向所述第二donor-CU发送重配置的所述第二信息，所述第二donor-CU通过第一F1AP消息将重配置的所述第二信息发送给所述移动节点的DU。
4.根据附记3所述的方法，其中，所述第一F1AP消息包括F1建立响应消息或gNB CU配置更新消息。
5.根据附记1至4任一项所述的方法，其中，所述第二信息包括如下至少之一：物理小区标识(PCI)、NR小区全局标识(NCGI)、跟踪区域码(TAC)、物理随机接入信道(PRACH)资源配置。
6.根据附记1至5任一项所述的方法，其中，所述第一信息包括：由移动终端(MT)检测并上报的与第二小区相关的第二信息，和/或，所述移动节点的位置信息或MT所接入的小区信息。
7.根据附记1至6任一项所述的方法，其中，在所述第一donor-CU为所述移动节点的DU重配置与第一小区相关的第二信息之前，所述方法还包括：
所述第一donor-CU接收所述第二donor-CU发送的所述移动节点的DU当前配置的与第一小区相关的第二信息。
8.根据附记7所述的方法，其中，所述方法还包括：
所述第一donor-CU根据所述第一信息和所述当前配置的与第一小区相关的第二信息，确定需要重配置所述与第一小区相关的第二信息。
9.根据附记1至8任一项所述的方法，其中，所述移动节点的非F1终止donor-CU从所述第一donor-CU改变到第三donor-CU。
10.根据附记1至9任一项所述的方法，其中，为所述移动节点的DU的第一小区重配置的物理小区标识(PCI)与相邻小区的PCI不冲突，为所述移动节点的DU的第一小区重配置的NR小区全局标识(NCGI)与相邻小区的NCGI相关，为所述移动节点的DU的第一小区重配置的跟踪区域码(TAC)与相邻小区的TAC相同或相关，为所述移动节点的DU的第一小区重配置的PRACH资源与相邻小区的PRACH资源不冲突。
11.根据附记9或10所述的方法，其中，在所述移动节点的MT的RRC连接由所述第一donor-CU迁移到所述第三donor-CU后，所述方法还包括：
所述第一donor-CU向所述第二donor-CU发送传输迁移修改请求；其中，所述传输迁移修改请求用于请求释放业务的传输资源；
所述第一donor-CU接收所述第二donor-CU发送的传输迁移修改响应。
12.根据附记11所述的方法，其中，
所述移动节点接收所述第三donor-CU分配的IP地址和BAP层地址；其中，所述第三donor-CU分配的IP地址和BAP层地址由RRC重配置消息承载；以及，
所述移动节点的DU通过gNB DU配置更新消息向所述第二donor-CU上报从由所述第三donor-CU分配的IP地址中选择使用的IP地址。
13.一种移动节点的配置方法，所述方法包括：
第二donor-CU接收第一donor-CU发送的与移动节点的DU的第一小区相关的第二信息；其中，所述第二信息由所述第一donor-CU根据所述移动节点的与位置相关的第一信息，为所述移动节点的DU重配置；以及
所述第二donor-CU将所述重配置的与第一小区相关的第二信息发送给所述移动节点的DU。
14.根据附记13所述的方法，其中，所述第一donor-CU为所述移动节点的非F1终止dornor-CU(non-F1-terminating donor-CU)；所述第二donor-CU为所述移动节点的F1终止dornor-CU(F1-terminating donor-CU)。
15.根据附记13或14所述的方法，其中，所述第一donor-CU通过XnAP消息向所述第二donor-CU发送重配置的所述第二信息，所述第二donor-CU通过第一F1AP消息将重配置的所述第二信息发送给所述移动节点的DU。
16.根据附记15所述的方法，其中，所述第一F1AP消息包括F1建立响应消息或gNB CU配置更新消息。
17.根据附记13至16任一项所述的方法，其中，所述第二信息包括如下至少之一：物理小区标识(PCI)、NR小区全局标识(NCGI)、跟踪区域码(TAC)、物理随机接入信道(PRACH)资源配置。
18.根据附记13至17任一项所述的方法，其中，所述第一信息包括：由MT检测并上报的与第二小区相关的第二信息，和/或，所述移动节点的位置信息或MT所接入的小区信息。
19.根据附记13至18任一项所述的方法，其中，在所述第一donor-CU为所述移动节点的DU重配置与第一小区相关的第二信息之前，所述方法还包括：
所述第二donor-CU向所述第一donor-CU发送所述移动节点的DU当前配置的与第一小区相关的第二信息。
20.根据附记13至19任一项所述的方法，其中，所述移动节点的非F1终止donor-CU从所述第一donor-CU改变到第三donor-CU。
21.根据附记20所述的方法，其中，所述方法还包括：
所述第二donor-CU接收所述第三donor-CU发送的为所述移动节点的DU重配置的第一小区信息；以及
所述第二donor-CU将重配置的所述第一小区信息发送给所述移动节点的DU。
22.根据附记13至21任一项所述的方法，其中，为所述移动节点的DU的第一小区重配置的物理小区标识(PCI)与相邻小区的PCI不冲突，为所述移动节点的DU的第一小区重配置的NR小区全局标识(NCGI)与相邻小区的NCGI相关，为所述移动节点的DU的第一小区重配置的跟踪区域码(TAC)与相邻小区的TAC相同或相关，为所述移动节点的DU的第一小区重配置的PRACH资源与相邻小区的PRACH资源不冲突。
23.根据附记20至22任一项所述的方法，其中，在所述移动节点MT的RRC连接由所述第一donor-CU迁移到所述第三donor-CU后，所述方法还包括：
所述第二donor-CU接收所述第一donor-CU发送的传输迁移修改请求，其中，所述传输迁移修改请求用于请求释放业务的传输资源；
所述第二donor-CU向所述第一donor-CU发送传输迁移修改响应。
24.根据附记23所述的方法，其中，所述方法还包括：
所述第二donor-CU接收所述移动节点的DU通过gNB DU配置更新消息上报的从由所述第三donor-CU分配的IP地址中选择使用的IP地址；
其中，所述移动节点接收所述第三donor-CU分配的IP地址和BAP层地址，所述第三donor-CU分配的IP地址和BAP层地址由RRC重配置消息承载。
25.根据附记24所述的方法，其中，所述方法还包括：
所述第二donor-CU根据所述移动节点上报的所述IP地址确定所述第三donor-CU，并向所述第三donor-CU发送传输迁移管理请求，其中，所述传输迁移管理请求用于请求建立业务的传输资源；以及
所述第二donor-CU接收所述第三donor-CU发送的传输迁移管理响应。
26.根据附记25所述的方法，其中，所述第二donor-CU接收的由所述第一donor- CU发送的传输迁移修改请求和所述第二donor-CU向所述第三donor-CU发送的所述传输迁移管理请求中包括所述第三donor-CU为所述移动节点分配的Xn接口标识。
27.根据附记25所述的方法，其中，所述移动节点的DU通过所述gNB DU配置更新消息向所述第二donor-CU上报由所述第三donor-CU为所述移动节点分配的BAP层地址；以及，所述第二donor-CU向所述第三donor-CU发送的所述传输迁移管理请求中包括所述BAP层地址。
28.一种移动节点的配置方法，所述移动节点的F1终止donor-CU从第四donor-CU改变到第五donor-CU，所述方法包括：
所述第五donor-CU根据所述移动节点的与位置相关的第一信息，为所述移动节点的DU重配置与第一小区相关的第二信息；以及
所述第五donor-CU将重配置的所述与第一小区相关的第二信息发送给所述移动节点的DU。
29.根据附记28所述的方法，其中，所述第五donor-CU通过第二F1AP消息将重配置的所述与第一小区相关的第二信息发送给所述移动节点的DU。
30.根据附记29所述的方法，其中，所述第二F1AP消息包括F1建立响应消息或gNB CU配置更新消息。
31.根据附记28至30任一项所述的方法，其中，所述第二信息包括如下至少之一：物理小区标识(PCI)、NR小区全局标识(NCGI)、跟踪区域码(TAC)、物理随机接入信道(PRACH)资源配置。
32.根据附记28至31任一项所述的方法，其中，所述第一信息包括：由移动终端检测并上报的与第二小区相关的第二信息，和/或，所述移动节点的位置信息或MT当前接入的小区信息。
33.根据附记28至32任一项所述的方法，其中，在所述第五donor-CU为所述移动节点的DU重配置与第一小区相关的第二信息之前，所述方法还包括：
所述第五donor-CU接收所述移动节点的DU通过第三F1AP消息发送的当前配置的所述第一小区的第二信息。
34.根据附记33所述的方法，其中，所述第三F1AP消息包括F1建立请求消息或gNB DU配置更新消息。
35.根据附记33所述的方法，其中，所述方法还包括：
所述第五donor-CU根据所述第一信息和所述当前配置的与第一小区相关的第二 信息，确定需要重配置所述与第一小区相关的第二信息。
36.根据附记28至35任一项所述的方法，其中，为所述移动节点的DU的第一小区重配置的物理小区标识(PCI)与相邻小区的PCI不冲突，为所述移动节点的DU的第一小区重配置的NR小区全局标识(NCGI)与相邻小区的NCGI相关，为所述移动节点的DU的第一小区重配置的跟踪区域码(TAC)与相邻小区的TAC相同或相关，为所述移动节点的DU的第一小区重配置的PRACH资源与相邻小区的PRACH资源不冲突。
37.一种移动节点的通信方法，其中，第一donor-CU为所述移动节点迁移或者无线链路失败(RLF)恢复前的非F1终止dornor-CU，第二donor-CU为所述移动节点的F1终止dornor-CU，第三donor-CU为所述移动节点迁移或者无线链路失败(RLF)恢复后的非F1终止dornor-CU；
在所述移动节点的MT的RRC连接由所述第一donor-CU迁移到所述第三donor-CU后，所述方法包括：
所述第二donor-CU接收所述第一donor-CU发送的传输迁移修改请求，其中，所述传输迁移修改请求用于请求释放业务的传输资源；
所述第二donor-CU向所述第一donor-CU发送传输迁移修改响应。
38.根据附记37所述的方法，其中，所述移动节点接收所述第三donor-CU分配的IP地址和BAP层地址；所述第三donor-CU分配的IP地址和BAP层地址由RRC重配置消息承载；以及，
所述移动节点的DU通过gNB DU配置更新消息向所述第二donor-CU上报从由所述第三donor-CU分配的IP地址中选择使用的IP地址。
39.根据附记38所述的方法，其中，所述方法还包括：
所述第二donor-CU根据所述移动IAB节点上报的所述IP地址确定所述第三donor-CU，并向所述第三donor-CU发送传输迁移管理请求，其中，所述传输迁移管理请求用于请求建立业务的传输资源；以及
所述第二donor-CU接收所述第三donor-CU发送的传输迁移管理响应。
40.根据附记39所述的方法，其中，所述第二donor-CU接收的由所述第一donor-CU发送的所述传输迁移修改请求和所述第二donor-CU向所述第三donor-CU发送的所述传输迁移管理请求中包括所述第三donor-CU为所述移动节点分配的Xn接口标识。
41.根据附记39所述的方法，其中，所述移动节点的DU通过所述gNB DU配置更新消息向所述第二donor-CU上报由所述第三donor-CU为所述移动节点分配的BAP层地址；以及，所述第二donor-CU向所述第三donor-CU发送的所述传输迁移管理请求中包括所述BAP层地址。
42.一种IAB宿主(donor)设备，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记1至36任一项所述的移动节点的配置方法，或者如附记37至41任一项所述的移动节点的通信方法。

Claims (20)

  1. 一种宿主设备，包括：
    配置部，其根据移动节点的与位置相关的第一信息，为所述移动节点的分布单元重配置与第一小区相关的第二信息；以及
    通信部，其向第二donor-CU发送所述重配置的与第一小区相关的第二信息；其中，所述重配置的与第一小区相关的第二信息被所述第二donor-CU发送给所述移动节点的分布单元。
  2. 根据权利要求1所述的设备，其中，所述宿主设备为所述移动节点的非F1终止dornor-CU；所述第二donor-CU为所述移动节点的F1终止dornor-CU。
  3. 根据权利要求1所述的设备，其中，所述通信部通过XnAP消息向所述第二donor-CU发送重配置的所述第二信息，所述第二donor-CU通过第一F1AP消息将重配置的所述第二信息发送给所述移动节点的分布单元。
  4. 根据权利要求3所述的设备，其中，所述第一F1AP消息包括F1建立响应消息或gNB CU配置更新消息。
  5. 根据权利要求1所述的设备，其中，所述第二信息包括如下至少之一：物理小区标识、NR小区全局标识、跟踪区域码、物理随机接入信道资源配置。
  6. 根据权利要求1所述的设备，其中，所述第一信息包括：由移动终端检测并上报的与第二小区相关的第二信息，和/或，所述移动节点的位置信息或移动终端所接入的小区信息。
  7. 根据权利要求1所述的设备，其中，在所述配置部为所述移动节点的分布单元重配置与第一小区相关的第二信息之前，所述通信部接收所述第二donor-CU发送的所述移动节点的分布单元当前配置的与第一小区相关的第二信息。
  8. 根据权利要求7所述的设备，其中，所述配置部根据所述第一信息和所述当前配置的与第一小区相关的第二信息，确定需要重配置所述与第一小区相关的第二信息。
  9. 根据权利要求1所述的设备，其中，所述移动节点的非F1终止donor-CU从第一donor-CU改变到第三donor-CU；
    在所述移动节点的移动终端的无线资源控制连接由所述第一donor-CU迁移到所述第三donor-CU后，所述通信部向所述第二donor-CU发送传输迁移修改请求，其 中，所述传输迁移修改请求用于指示释放业务的传输资源；并接收所述第二donor-CU发送的传输迁移修改响应。
  10. 根据权利要求1所述的设备，其中，为所述移动节点的分布单元的第一小区重配置的物理小区标识与相邻小区的物理小区标识不冲突，为所述移动节点的分布单元的第一小区重配置的NR小区全局标识与相邻小区的NR小区全局标识相关，为所述移动节点的分布单元的第一小区重配置的跟踪区域码与相邻小区的跟踪区域码相同或相关，为所述移动节点的分布单元的第一小区重配置的物理随机接入信道资源与相邻小区的物理随机接入信道资源不冲突。
  11. 一种宿主设备，包括：
    接收部，其接收第一donor-CU发送的与移动节点的分布单元的第一小区相关的第二信息；其中，所述第二信息由所述第一donor-CU根据所述移动节点的与位置相关的第一信息，为所述移动节点的分布单元重配置；以及
    发送部，其将所述重配置的与第一小区相关的第二信息发送给所述移动节点的分布单元。
  12. 根据权利要求11所述的设备，其中，所述第一donor-CU为所述移动节点的非F1终止dornor-CU；所述宿主设备为所述移动节点的F1终止dornor-CU。
  13. 根据权利要求11所述的设备，其中，所述移动节点的非F1终止donor-CU从所述第一donor-CU改变到第三donor-CU；
    所述接收部接收所述第三donor-CU发送的为所述移动节点分布单元重配置的第一小区信息；以及所述发送部将重配置的所述第一小区信息发送给所述移动节点的分布单元。
  14. 根据权利要求11所述的设备，其中，在所述移动节点的移动终端的无线资源控制连接由所述第一donor-CU迁移到第三donor-CU后，所述接收部接收所述第一donor-CU发送的传输迁移修改请求，其中，所述传输迁移修改请求用于请求释放业务的传输资源；
    所述发送部向所述第一donor-CU发送传输迁移修改响应。
  15. 根据权利要求14所述的设备，其中，所述接收部接收所述移动节点的分布单元通过gNB DU配置更新消息上报的从由所述第三donor-CU分配的IP地址中选择使用的IP地址；
    其中，所述移动节点接收所述第三donor-CU分配的IP地址和BAP层地址，所述第三donor-CU分配的IP地址和BAP层地址由无线资源控制重配置消息承载。
  16. 根据权利要求15所述的设备，其中，所述发送部根据所述移动节点上报的所述IP地址确定所述第三donor-CU，并向所述第三donor-CU发送传输迁移管理请求，其中，所述传输迁移管理请求用于请求建立业务的传输资源；以及
    所述接收部接收所述第三donor-CU发送的传输迁移管理响应。
  17. 根据权利要求16所述的设备，其中，所述接收部接收的由所述第一donor-CU发送的传输迁移修改请求和所述发送部向所述第三donor-CU发送的所述传输迁移管理请求中包括所述第三donor-CU为所述移动节点分配的Xn接口标识。
  18. 根据权利要求16所述的设备，其中，所述接收部接收由所述移动节点的分布单元通过所述gNB DU配置更新消息上报的由所述第三donor-CU为所述移动节点分配的BAP层地址；以及，所述发送部向所述第三donor-CU发送的所述传输迁移管理请求中包括所述BAP层地址。
  19. 一种宿主设备，移动节点的F1终止donor-CU从第四donor-CU改变到所述宿主设备，所述宿主设备包括：
    配置部，其根据所述移动节点的与位置相关的第一信息，为所述移动节点的分布单元重配置与第一小区相关的第二信息；以及
    通信部，将重配置的所述与第一小区相关的第二信息发送给所述移动节点的分布单元。
  20. 根据权利要求19所述的设备，其中，所述配置部根据所述第一信息和当前配置的与第一小区相关的第二信息，确定需要重配置所述与第一小区相关的第二信息。
PCT/CN2022/110391 2022-08-04 2022-08-04 移动节点的配置方法和宿主设备 WO2024026803A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/110391 WO2024026803A1 (zh) 2022-08-04 2022-08-04 移动节点的配置方法和宿主设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/110391 WO2024026803A1 (zh) 2022-08-04 2022-08-04 移动节点的配置方法和宿主设备

Publications (1)

Publication Number Publication Date
WO2024026803A1 true WO2024026803A1 (zh) 2024-02-08

Family

ID=89848194

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/110391 WO2024026803A1 (zh) 2022-08-04 2022-08-04 移动节点的配置方法和宿主设备

Country Status (1)

Country Link
WO (1) WO2024026803A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220086718A1 (en) * 2020-09-14 2022-03-17 Qualcomm Incorporated Migration of an integrated access and backhaul node
WO2022061780A1 (en) * 2020-09-25 2022-03-31 Nokia Shanghai Bell Co., Ltd. Methods, apparatuses and computer readable media for integrated access and backhaul communication
WO2022082518A1 (zh) * 2020-10-21 2022-04-28 富士通株式会社 信号的接收和发送方法、装置和通信系统
WO2022152089A1 (zh) * 2021-01-15 2022-07-21 大唐移动通信设备有限公司 一种信息传输方法及其装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220086718A1 (en) * 2020-09-14 2022-03-17 Qualcomm Incorporated Migration of an integrated access and backhaul node
WO2022061780A1 (en) * 2020-09-25 2022-03-31 Nokia Shanghai Bell Co., Ltd. Methods, apparatuses and computer readable media for integrated access and backhaul communication
WO2022082518A1 (zh) * 2020-10-21 2022-04-28 富士通株式会社 信号的接收和发送方法、装置和通信系统
WO2022152089A1 (zh) * 2021-01-15 2022-07-21 大唐移动通信设备有限公司 一种信息传输方法及其装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Inter-CU topology redundancy", 3GPP DRAFT; R3-212415, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20210517 - 20210527, 7 May 2021 (2021-05-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052002459 *
ZTE: "Discussion on inter-donor migration in IAB", 3GPP DRAFT; R3-213205, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20210816 - 20210826, 6 August 2021 (2021-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052035183 *

Similar Documents

Publication Publication Date Title
WO2019128947A1 (zh) 通信方法和通信设备
US10143019B2 (en) Method and apparatus for signaling between eNBs in a wireless communication system supporting dual connectivity
WO2018029933A1 (ja) 無線アクセスネットワークノード、無線端末、コアネットワークノード、及びこれらの方法
US20220408317A1 (en) Handover method and communication apparatus
US11533769B2 (en) Multi-hop data transmission method and apparatus
US20230254729A1 (en) Migration method and apparatus for iab-node
WO2024026803A1 (zh) 移动节点的配置方法和宿主设备
WO2024026804A1 (zh) 移动节点的配置方法、移动节点和宿主设备
WO2023197184A1 (zh) Iab宿主设备以及传输地址配置方法
WO2023197185A1 (zh) Iab节点设备、iab宿主设备以及传输地址确定方法
WO2023130232A1 (zh) Iab节点设备、iab宿主设备以及路径迁移方法
WO2023150974A1 (zh) Iab宿主设备以及传输迁移管理方法
WO2023184542A1 (zh) 配置信息的方法、装置和通信系统
WO2022082690A1 (zh) 群组切换的方法、装置和系统
WO2023130231A1 (zh) Iab节点设备、iab宿主设备以及拓扑退行方法
WO2023150975A1 (zh) Iab宿主设备以及传输迁移回退方法
WO2023150976A1 (zh) Iab宿主设备以及传输迁移管理方法
WO2024031289A1 (zh) 网络节点的通信方法、移动节点的通信方法、移动节点和宿主设备
WO2023010364A1 (zh) 集成的接入和回传的通信装置以及方法
WO2023010367A1 (zh) 终端设备的转移方法、装置和系统
WO2022236644A1 (zh) 发送和接收信号的方法、装置和通信系统
WO2022233008A1 (zh) 消息发送方法、装置和系统
WO2022205252A1 (zh) 发送和接收信号的方法、装置和通信系统
US20230345326A1 (en) Group migrating method and apparatus and system
WO2022205251A1 (zh) 信息收发方法，数据发送方法以及装置

Legal Events

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

Ref document number: 22953612

Country of ref document: EP

Kind code of ref document: A1