WO2023246746A1 - Procédé de communication et dispositif associé - Google Patents

Procédé de communication et dispositif associé Download PDF

Info

Publication number
WO2023246746A1
WO2023246746A1 PCT/CN2023/101289 CN2023101289W WO2023246746A1 WO 2023246746 A1 WO2023246746 A1 WO 2023246746A1 CN 2023101289 W CN2023101289 W CN 2023101289W WO 2023246746 A1 WO2023246746 A1 WO 2023246746A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
interface
donor
iab node
new
Prior art date
Application number
PCT/CN2023/101289
Other languages
English (en)
Chinese (zh)
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 华为技术有限公司
Publication of WO2023246746A1 publication Critical patent/WO2023246746A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point

Definitions

  • the present application relates to the field of communication technology, and more specifically, to a communication method and related equipment.
  • the fifth generation mobile communication system (5th-generation, 5G) introduces integrated access and backhaul (IAB) network technology.
  • the access link and backhaul link in the IAB network (backhaul link) all adopt wireless transmission solutions, which reduces fiber deployment, thereby reducing deployment costs and improving deployment flexibility.
  • IAB network it includes IAB node (IAB node) and IAB host (IAB donor).
  • IAB node is composed of the mobile terminal (MT) part and the distributed unit (DU) part
  • the IAB donor is composed of the centralized unit (centralized unit, CU) part and the distributed unit (distributed unit).
  • DU distributed unit
  • the IAB node can choose to switch between different IAB hosts.
  • the F1 interface between the IAB node and the target IAB host in topology 1
  • the source IAB host in topology 2.
  • This problem arises through the establishment of F1 interfaces across IAB hosts or across topologies.
  • This application provides a communication method that can establish a cross-topology F1 interface to facilitate the cross-host switching process of an IAB node and ensure communication between the IAB node and its downstream nodes.
  • the first aspect provides the first implementation method, including: Donor CU1 determines that the first IAB node needs to switch from Donor CU1 to Donor CU2.
  • the Donor CU1 determines at least one new IP address of the first IAB node for the second F1 interface control plane, where the second F1 interface is an interface between the first IAB node and the Donor CU2.
  • the Donor CU1 sends configuration information to the Donor DU1 based on at least one new IP address used for the second F1 interface control plane, and the configuration information is used to configure the transmission resources of the second F1 interface control plane message.
  • exemplary beneficial effects include: during the cross-host handover process of the IAB node, the host base station can configure relevant transmission resources for the cross-host handover of the IAB node, so as to support subsequent cross-topology F1 Establishment of interface control plane. If Donor CU1 determines at least one new IP address of the first IAB node for the second F1 interface control plane by itself, then through the first implementation manner, exemplary beneficial effects include: it can make the cross-interface of the IAB node During the host switching process, the cross-topology F1 interface is established as soon as possible to facilitate the cross-host switching process of the IAB node and ensure communication between the IAB node and its downstream nodes.
  • the method further includes: The Donor CU1 receives the first message from the Donor CU2. The first message is used to request the second F1 interface of the first IAB node. At least one new IP address for the control plane.
  • exemplary beneficial effects include: the cross-host switching process on the IAB node can be triggered by Donor CU2 (that is, the F1-terminating CU of the cross-topology F1 interface) to establish the cross-topology F1 interface. In order to implement the appropriate cross-host switching process of the IAB node and ensure the communication between the IAB node and its downstream nodes.
  • the Donor CU1 sends a first RRC message to the first IAB node, and the first RRC message includes at least one of the following: the At least one new IP address for the second F1 interface control plane; or, the default BAP configuration of the first IAB node for transmitting the second F1 interface control plane message, the default BAP configuration including the default BAP routing ID, and/or, the default BH RLC CH ID; or, the IP address of the Donor CU2.
  • exemplary beneficial effects include: during the cross-host switching process of the IAB node, the IAB node can obtain the necessary information for establishing the cross-topology F1 interface control plane, thereby establishing the cross-topology F1 interface.
  • the control plane is used to facilitate the cross-host switching process of the IAB node and ensure the communication between the IAB node and its downstream nodes.
  • the first RRC message further includes the first IAB node's third IP address corresponding to the at least one new IP address used for the second F1 interface control plane.
  • Identification information of two distributed units DU wherein the first IAB node at least includes a first DU and a second DU, a first F1 interface exists between the first DU and the Donor CU1, and the second F1 interface is the first DU. The interface between the second DU and the Donor CU2.
  • the Donor CU1 sends a second message to the Donor CU2, the second message includes the second F1 interface for At least one new IP address of the control plane, and/or a quality of service QoS attribute value corresponding to the at least one new IP address used for the second F1 interface control plane.
  • exemplary beneficial effects include: during the cross-host switching process of the IAB node, the target IAB host can obtain the necessary information for establishing a cross-topology F1 interface control plane, thereby establishing a cross-topology F1 interface.
  • the interface control plane facilitates the cross-host switching process of IAB nodes and ensures communication between IAB nodes and their downstream nodes.
  • the Donor CU1 determines at least one new IP address of the first IAB node for the second F1 interface control plane, including : The Donor CU1 determines the same new IP address for the first IAB node to be used for all traffic on the second F1 interface control plane.
  • the method before the Donor CU1 sends the second message to the Donor CU2, the method further includes: the Donor CU1 receives the message for the third message from the first IAB node.
  • Two F1 interfaces have new IP addresses for different traffic on the control plane.
  • the configuration information is used to configure the transmission resources of the second F1 interface control plane message, including: the configuration information is specifically used to indicate the Donor DU1 only determines at least one of the BAP routing ID, Next Hop BAP Address and BH RLC CH ID of the second F1 interface control plane message based on the destination IP address of the second F1 interface control plane message.
  • the method further includes: the Donor CU1 determines the new flow rate of the first IAB node for the first traffic of the second F1 interface user plane. IP address.
  • exemplary beneficial effects include: during the cross-host switching process of the IAB node, Donor CU1 can obtain the new first flow of the first IAB node for the second F1 interface user plane. IP address to support the subsequent establishment of the F1 interface user plane across topologies. If Donor CU1 determines the new IP address of the first IAB node for the first traffic of the second F1 interface user plane by itself, then through the first implementation manner, exemplary beneficial effects include: it can make the IAB node Cross-host switching process, establish a cross-topology F1 interface as soon as possible to facilitate the cross-host switching process of IAB nodes and ensure communication between IAB nodes and their downstream nodes.
  • the The method before the Donor CU1 determines the new IP address of the first IAB node for the first traffic of the second F1 interface user plane, the The method also includes: the Donor CU1 receives a third message from the Donor CU2, the third message is used to request at least one new IP address of the first IAB node for the second F1 interface user plane.
  • exemplary beneficial effects include: the cross-host switching process on the IAB node can be triggered by Donor CU2 (that is, the F1-terminating CU of the cross-topology F1 interface) to establish the cross-topology F1 interface. In order to implement the appropriate cross-host switching process of the IAB node and ensure the communication between the IAB node and its downstream nodes.
  • the Donor CU1 determines the new IP of the first IAB node for the first traffic of the second F1 interface user plane. Address, including: the Donor CU1 selects the new IP address for the first flow of the second F1 interface user plane from at least one new IP address of the first IAB node for the second F1 interface user plane ; Alternatively, the Donor CU1 sends a second RRC message to the first IAB node, where the second RRC message includes at least one new IP address of the first IAB node for the second F1 interface user plane. The Donor CU1 receives a new IP address from the first IAB node for the first traffic of the second F1 interface user plane.
  • the method includes: the Donor CU1 sends a third RRC message to the first IAB node, and the third RRC message includes the third RRC message.
  • the third RRC message also includes a new IP address corresponding to the first IAB node for the first traffic of the second F1 interface user plane.
  • the identification information of the second DU of the first IAB node is not limited to the third RRC message.
  • the Donor CU1 sends a fourth message to the Donor CU2, the fourth message includes the message for the second The new IP address of the first traffic on the F1 interface user plane.
  • exemplary beneficial effects include: during the cross-host switching process of the IAB node, the target IAB host can obtain the necessary information for establishing the cross-topology F1 interface user plane, thereby establishing the cross-topology F1 interface. Interface user plane to facilitate the cross-host switching process of IAB nodes and ensure communication between IAB nodes and their downstream nodes.
  • the first IAB node determines the first IP address based on the at least one new IP address, including: if the at least one new IP address includes The second F1 interface controls multiple new IP addresses, and the first IAB node selects the first IP address from the multiple new IP addresses.
  • the first IP address is used for the second F1 interface.
  • the first IAB node determines the first IP address based on the at least one new IP address, including: if the at least one new IP address The IP address includes a new IP address corresponding to the old IP address used for the first traffic of the first F1 interface user plane, then the first IAB node determines that the first IP address used for the first F1 interface user plane
  • the new IP address corresponding to the old IP address of a flow is the first IP address
  • the first IP address corresponds to the first flow used for the user plane of the second F1 interface, where the first F1 interface is the first flow.
  • the first IAB node determines the first IP address based on the at least one new IP address, including: if the at least one new IP address The IP address includes multiple new IP addresses for the second F1 interface user plane, then the first IAB node selects the first IP address from the multiple new IP addresses, and the first IP address is the same as First traffic mapping for the user plane of the second F1 interface.
  • the first IAB node sends the first IP address to the Donor CU1 through an RRC message or a first F1 interface message.
  • the fourth aspect provides a first implementation method, including: the second host centralized unit Donor CU2 receives at least one new IP address from the first host centralized unit Donor CU1 for the second F1 interface user plane, wherein, The second F1 interface is the interface between the first access backhaul integrated IAB node and the Donor CU2.
  • the Donor CU2 sends at least one new IP address for the second F1 interface user plane to the first IAB node through a second F1 interface message.
  • the Donor CU2 sends at least one new IP address for the second F1 interface user plane to the first IAB node through the second F1 interface message, Including: the Donor CU2 sends the old IP address used for the first flow of the first F1 interface user plane to the first IAB node through the second F1 interface message, and the old IP address used for the first F1 interface user plane.
  • the old IP address of a flow corresponds to a new IP address used for the first flow of the user plane of the second F1 interface, where the second F1 interface is the interface between the first IAB node and the Donor CU1.
  • the present application provides a communication device, which includes methods for performing the first to fourth aspects. and modules for any method in any of its designs.
  • the present application provides a communication device, including a processor and a memory.
  • the processor is coupled to the memory.
  • the processor is used to implement the methods of the first to fourth aspects and any one of their designs. method.
  • the present application provides a communication device, including at least one processor and an interface circuit.
  • the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or from the processor.
  • the signal of the processor is sent to other communication devices other than the communication device, and the processor is used to implement the methods of the first to fourth aspects and any method in any design thereof through logic circuits or executing code instructions.
  • the device may be a chip or an integrated circuit in a node in any of the methods of the first to fourth aspects and any of the designs thereof.
  • the communication device may also include at least one memory, which stores related program instructions.
  • the present application provides a communication device, which has functions or operations to implement any one of the methods of the first to fourth aspects and methods in any of its designs, and the functions or operations are It can be implemented through hardware, or corresponding software can be implemented through hardware.
  • the hardware or software includes one or more units (modules) corresponding to the above functions or operations, such as a transceiver unit and a processing unit.
  • this application provides a computer program product.
  • the computer program product includes related program instructions.
  • the related program instructions When the related program instructions are executed, the methods of the first to fourth aspects and any of the designs thereof are implemented. any method.
  • the present application also provides a chip, which is used to implement the methods of the first to fourth aspects and any method in any design thereof.
  • the present application provides a communication system, which includes at least one communication device in the fifth aspect to the eighth aspect and any one of the designs thereof.
  • FIG. 1 is a schematic diagram of an IAB network communication system
  • FIG. 2 is a schematic diagram of the control plane protocol stack in an IAB network
  • Figure 4 is a schematic diagram of an applicable scenario provided by the embodiment of the present application.
  • Figure 5 is a schematic flow chart of a method provided by an embodiment of the present application.
  • Figure 6 is a schematic flow chart of a method provided by an embodiment of the present application.
  • Figure 7 is a schematic flow chart of a method provided by an embodiment of the present application.
  • Figure 8 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • FIG 1 is a schematic diagram of an IAB network communication system provided by this application.
  • the communication system includes terminals, IAB nodes, and host base stations.
  • IAB network is just an example and can be replaced by "wireless backhaul network” or “relay network”.
  • IAB node is just an example and can be replaced with “wireless backhaul device” or “relay node”.
  • the donor base station can serve as the host node of the IAB node.
  • the host base station may include but is not limited to: next-generation base station (generation nodeB, gNB), evolved node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B) B, NB), base station controller (BSC), base transceiver station (BTS), home base station (home evolved Node B or home Node B), transmission point (transmission and reception point or transmission point ), road side unit (RSU) with base station function, baseband unit (baseband unit, BBU), radio frequency remote unit (Remote Radio Unit, RRU), active antenna unit (active antenna unit, AAU), One or a group of antenna panels, or nodes with base station functions in subsequent evolution systems.
  • generation nodeB generation nodeB, gNB
  • evolved node B evolved Node B
  • RNC radio network controller
  • Node B Node B
  • BSC base station controller
  • BTS base
  • the host base station can be an entity, and can also include a centralized unit (CU) entity plus at least one distributed unit (DU) entity.
  • the interface between CU and DU can be called the F1 interface.
  • the two ends of the F1 interface are CU and DU respectively.
  • the opposite end of CU's F1 interface is DU, and the opposite end of DU's F1 interface is CU.
  • the F1 interface can further include an F1 interface control plane (F1-C) and an F1 interface user plane (F1-U).
  • F1-C F1 interface control plane
  • F1-U F1 interface user plane
  • the CU of the host base station may be referred to as Donor CU
  • the DU of the host base station may be referred to as Donor DU.
  • the terminal is sometimes also called user equipment (UE), mobile station, terminal equipment, etc.
  • Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), Internet of Things (internet) of things, IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc.
  • Terminals can be mobile phones, tablets, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.
  • the terminal may include but is not limited to: user equipment UE, mobile station, mobile device, terminal device, user agent, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop, WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device, other processing device connected to a wireless modem, vehicle-mounted device, wearable device (such as smart watch, smart bracelet, Smart glasses, etc.), smart furniture or home appliances, vehicle equipment in the Internet of Vehicles (vehicle to everything, V2X), terminal equipment with relay functions, customer premises equipment (CPE), IAB nodes (specifically IAB MT of the node or IAB node as the terminal role), etc.
  • This application does not limit the specific name and implementation form of the terminal.
  • the MT function or MT entity that provides the terminal role for the IAB node.
  • the child nodes can be other IAB nodes or terminals
  • it can serve as a network device, that is, the network device role of the IAB node.
  • the DU function or DU entity that provides the network device role for the IAB node.
  • the MT of the IAB node may be referred to as IAB-MT
  • the DU of the IAB node may be referred to as IAB-DU.
  • the IAB node can access the host base station or pass Connect to the host base station through other IAB nodes.
  • the IAB network supports multi-hop networking and multi-connection networking to ensure the reliability of service transmission.
  • the IAB node regards the IAB node that provides the backhaul service as a parent node, and accordingly, the IAB node can be regarded as a child node of its parent node.
  • the terminal can also regard the IAB node connected to itself as a parent node.
  • the IAB node can also regard the terminal connected to itself as a child node.
  • the IAB node can regard the host base station connected to itself as a parent node.
  • the host base station can also regard the IAB node connected to itself as a child node.
  • the parent node of IAB node 1 includes the host base station.
  • IAB node 1 is the parent node of IAB node 2 or IAB node 3.
  • the parent node of terminal 1 includes IAB node 4.
  • the child nodes of IAB node 4 include terminal 1 or terminal 2.
  • the IAB node that the terminal directly accesses can be called an access IAB node.
  • IAB node 4 in Figure 1 is the access IAB node for terminal 1 and terminal 2.
  • IAB node 5 is the access IAB node of terminal 2.
  • the nodes on the uplink transmission path from the IAB node to the host base station can be called the upstream node of the IAB node.
  • Upstream nodes can include parent nodes, parent nodes of parent nodes (or grandparent nodes), etc.
  • IAB node 1 and IAB node 2 in Figure 1 can be called the upstream nodes of IAB node 5.
  • the nodes on the downlink transmission path from the IAB node to the terminal can be called the downstream node (downstream node) or descendant node (descendant node) of the IAB node.
  • Downstream nodes or descendant nodes may include child nodes (or called next-hop nodes), child nodes of child nodes (or called grandchild nodes), or terminals, etc.
  • terminal 1, terminal 2, IAB node 2, IAB node 3, IAB node 4 or IAB node 5 in Figure 1 can be called downstream nodes or descendant nodes of IAB node 1.
  • IAB node 4 and IAB node 5 in Figure 1 can be called downstream nodes or descendant nodes of IAB node 2.
  • Terminal 1 in Figure 1 can be called a downstream node or descendant node of IAB node 4.
  • Each IAB node needs to maintain a backhaul link (BL) facing the parent node. If the child node of the IAB node is a terminal, the IAB node also needs to maintain an access link (AL) with the terminal.
  • the link between IAB node 4 and terminal 1 or terminal 2 includes AL.
  • a BL is included between IAB node 4 and IAB node 2 or IAB node 3.
  • transmission path 1 is “host base station-IAB node 1-IAB node 2-IAB node 5-terminal 2
  • transmission path 2 is “host base station-IAB node 1-IAB node 2-IAB node 5-terminal 2”.
  • transmission path 3 is "host base station-IAB node 1-IAB node 3-IAB node 4-terminal 2".
  • adaptation protocol routing identity (bakhaul adaptation protocol routing identity, BAP routing ID).
  • IAB nodes on the path can have BAP addresses (BAP addresses) and Internet Protocol (internet protocol, IP) addresses.
  • FIGS 2 and 3 are respectively a schematic diagram of the control plane protocol stack and a schematic diagram of the user plane protocol stack in the IAB network provided by the embodiment of the present application.
  • the host base station in Figure 2 and Figure 3 may include host CU and host DU functions (in this case, the host base station is one entity), or may include a host CU entity and a host DU entity (in this case, the host base station is divided into two entities).
  • the equivalent protocol layers between the host DU and the host CU include the IP layer, layer 2 (layer 2, L2), and layer 1 (layer 1, L1).
  • L1 and L2 may refer to the protocol stack layer in the wired transmission (such as optical fiber transmission) network.
  • L1 can be the physical layer
  • L2 can be the data link layer
  • Backhaul links (BL) are established between IAB node 4 and IAB node 3, between IAB node 3 and IAB node 1, and between IAB node 1 and the host DU.
  • the peer-to-peer protocol stacks at both ends of the BL can include the backhaul adaptation protocol (BAP) layer, radio link control (RLC), media access control (medium access control, MAC) layer, and Physical (PHY) layer.
  • BAP backhaul adaptation protocol
  • RLC radio link control
  • MAC media access control
  • PHY Physical
  • the F1 interface There is an interface between the DU of the IAB node that the terminal accesses (ie, IAB node 4 in Figure 2) and the host base station, for example, it is called the F1 interface.
  • One end of the F1 interface is located at IAB node 4, and the other end is located at the host base station.
  • the opposite end of the F1 interface of the host base station (for example, it can be the host CU) is the IAB node (specifically, it can be the DU of the IAB node), and the opposite end of the F1 interface of the IAB node (specifically, it can be the DU of the IAB node) is the host base station (specifically, it can be the DU of the IAB node).
  • the peer-to-peer user plane protocol layers at both ends of the F1 interface between the DU of IAB node 4 and the host base station include the general packet radio service tunneling protocol for the user plane (GTP-U) layer.
  • Datagram protocol user datagram protocol, UDP
  • IP layer optionally including IPsec layer.
  • the host base station may include a host CU entity and a host DU entity.
  • the user plane protocol stack of the F1 interface on the host base station side can be located in the host CU.
  • the host CU includes a GTP-U layer, a UDP layer and an IP layer, and optionally includes an IPsec layer.
  • the user plane protocol stack of the F1 interface at the host base station can also be located in the host CU and the host DU respectively.
  • the host CU includes the GTP-U layer and the UDP layer, optionally including the IPsec layer
  • the host DU includes the IP layer.
  • an IAB node may have one or more roles in the IAB network.
  • the IAB node can act as a terminal, an access IAB node (the protocol stack of IAB node 4 in Figures 2 and 3), or an intermediate IAB node (the IAB in Figures 2 and 3). node 1 or IAB node 3 protocol stack).
  • the IAB node can use protocol stacks corresponding to different roles for different roles.
  • the IAB node When the IAB node has multiple roles in the IAB network, it can have multiple sets of protocol stacks at the same time. Each set of protocol stacks can share some of the same protocol layers, such as sharing the same RLC layer, MAC layer, and PHY layer.
  • multiple IAB nodes can be included between IAB node 1 and IAB donor 1, or IAB node 3 can also be directly connected to IAB donor 1, that is, IAB node 1 in Figure 4 does not need to exist.
  • Multiple IAB nodes may also be included between IAB node 2 and IAB donor 2, or IAB node 3 may be directly connected to IAB donor 2, that is, IAB node 2 in Figure 4 may not exist.
  • other upstream nodes of IAB node 3 may also be included between IAB node 3 and IAB node 1, or between IAB node 3 and IAB node 2.
  • downstream nodes or descendant nodes of IAB node 3 may also be included.
  • the third possible cross-host switching process includes: initial stage -> final stage, that is, without passing through the intermediate stage.
  • IAB node 3 establishes an F1 interface control plane (F1-C) with host base station 2, and the MT of IAB node 3 also maintains the Uu interface with host base station 1.
  • F1 interface communication including only control plane communication
  • the F1 interface may or may not exist between the IAB node 3 and the host base station 1.
  • IAB node 3 in Figure 4 includes DU1 and DU2, then during the handover process across donor CUs, IAB node 3 can maintain the F1 connection between DU1 and IAB donor CU1 while establishing DU2 and DU2. IAB donor CU2 between F1-C.
  • the F1 interface control plane communication between the IAB node and host base station 2 needs to pass through Donor DU1.
  • the F1 interface user plane (F1-U) is established between IAB node 3 and host base station 2. If there was an F1 interface between IAB node 3 and host base station 1 before, in this case, the F1 interface between IAB node 3 and host base station 1 can be disconnected. In this case, the IAB node enters the final stage. In the final stage, the F1 interface communication (including user plane and control plane communication) between IAB node 3 and host base station 2 needs to pass through Donor DU2.
  • the CU of the opposite host base station of the F1 interface of IAB node 3 can also be called F1 endpoint CU (F1-terminating CU), and the CU of another host base station can be called non-F1 endpoint CU (non-F1-terminating donor). CU).
  • IAB node 3 in Figure 4 can also be called a boundary IAB node or a switching IAB node.
  • Figure 5 provides a schematic diagram of a communication method 100.
  • the first host centralized unit determines that the first IAB node needs to switch from Donor CU1 to the second host centralized unit (Donor CU2).
  • Donor CU1 can send a switching request to Donor CU2, requesting to switch the first IAB node (or the MT of the first IAB node) to Donor CU2.
  • Donor CU2 can send a switching response to Donor CU1, and the switching response can carry the IP address of Donor CU2.
  • Donor CU1 determines at least one new IP address of the first IAB node for the second F1 interface control plane, which may include: Donor CU1 requests F1 interface control from Donor DU1 noodle At least one new IP address, Donor CU1 receives at least one new IP address from the F1 interface control plane of Donor DU1, so that Donor CU1 determines at least one new IP of the first IAB node for the second F1 interface control plane address.
  • the transmission resources of the second F1 interface control plane message may include at least one of a next hop node, a transmission path, and a transmission channel.
  • Donor DU1 can determine at least one of the BAP routing ID of the second F1 interface control plane message, the BAP Address of the next hop (Next Hop), and the BH RLC CH ID.
  • the configuration information can be specifically used to instruct Donor DU1 to determine the BAP routing ID, Next Hop BAP Address and BH of the second F1 interface control plane message only based on the destination IP address of the second F1 interface control plane message. At least one of the RLC CH IDs.
  • the configuration information can be specifically used to indicate that Donor DU1 does not need to determine the BAP routing ID of the second F1 interface control plane message based on the quality of service (QoS) attribute value of the second F1 interface control plane message. At least one of Next Hop BAP Address and BH RLC CH ID. Through this configuration information, Donor CU1 does not need to send the QoS attribute value mapping rules of the F1 interface control plane message to Donor CU2.
  • Donor CU2 can still determine the QoS attribute value for the F1 interface control plane message sent to Donor DU1 based on the QoS attribute value mapping rules of its own F1 interface control plane message.
  • This implementation is optional, on the one hand, because the QoS attribute values corresponding to the F1 interface control plane messages can be specified in the 3rd Generation Partnership Project (3GPP) protocol or standard, that is to say, any A Donor CU that complies with 3GPP standards will carry unified QoS attribute values in the F1 interface control plane message. In this way, even if Donor CU1 does not make special configurations for Donor DU1 in this implementation, Donor DU1 can still reasonably transmit the second F1 interface control plane message.
  • 3GPP 3rd Generation Partnership Project
  • the communication method 100 includes the second implementation of S106, that is, Donor CU1 sends the second message to Donor CU2, then Donor CU1 does not need to do any special implementation of this implementation to Donor DU1.
  • Configuration in other words, Donor DU1 can reuse the configuration used to transmit the first F1 interface control plane message to transmit the second F1 interface control plane message.
  • the QoS attribute value may include a differentiated services code point (DSCP) and/or a flow label.
  • the QoS attribute value mapping rules of the control plane message may include the corresponding relationship between the QoS attribute value and the control plane message type, or the corresponding relationship between the QoS attribute value and the destination IP address of the control plane message.
  • the host base station can configure relevant transmission resources for the cross-host handover of the IAB node during the cross-host handover process of the IAB node, so as to support the subsequent establishment of the F1 interface control plane across topologies.
  • Donor CU1 sends the first RRC message to the first IAB node.
  • the first RRC message may include at least one of the following: at least one new IP address of the first IAB node for the second F1 interface control plane; or, the first IAB node for transmitting the second F1 interface control plane.
  • the default BAP configuration of the above message, the default BAP configuration includes the default BAP routing identifier routing ID, and/or, the default return wireless link control channel identifier BH RLC CH ID; or, the IP address of the Donor CU2.
  • the first IAB node may send the second F1 according to the first RRC message.
  • Interface control plane messages such as F1 interface establishment request information (such as F1 SETUP REQUEST message, please refer to the definition in 3GPP TS 38.473 V17.0.0 for specific understanding).
  • the first IAB node determines the routing ID of the second F1 interface control plane message according to the default BAP configuration, and/or the BH RLC CH used to transmit the second F1 interface control plane message.
  • the first IAB node determines the first IP address based on the at least one new IP address used for the second F1 interface control plane, and uses the first IP address as the source IP address of the second F1 interface control plane message. If the at least one new IP address includes the same new IP address for all traffic on the second F1 interface control plane (that is, Donor CU1 determines only one for all traffic on the second F1 interface control plane) IP address), the first IAB node determines that the same new IP address used for all traffic on the second F1 interface control plane is the first IP address.
  • the The first IAB node needs to select corresponding IP addresses from the multiple new IP addresses for different traffic on the second F1 interface control plane. For example, the first IAB node selects a first IP address corresponding to the first traffic for the second F1 interface control plane from the plurality of new IP addresses.
  • the second F1 interface control plane message belongs to the first traffic of the second F1 interface control plane.
  • the first IAB node uses the IP address of Donor CU2 as the destination IP address of the second F1 interface control plane message.
  • the IP address of Donor CU2 can be obtained by Donor CU1 from Donor CU2.
  • Donor CU1 obtains the IP address of Donor CU2 through the switching response mentioned in S101.
  • the first RRC message may also include information related to the user. Identification information of the second DU of the first IAB node corresponding to at least one new IP address of the second F1 interface control plane.
  • the identification information of DU may include IAB-DU identification (ID), IAB-DU name (name), serving cell information of a cell served by the IAB node (served cell information of a cell served by the IAB node), The system information configuration sent by the DU of the IAB node (such as synchronization signal and PBCH block (synchronization signal and physical broadcast channel block, SSB) related configuration), the RRC version supported by the DU of the IAB node, the transmission of the DU of the IAB node Layer address information
  • the IAB node can obtain the necessary information for establishing the cross-topology F1 interface control plane, thereby establishing the cross-topology F1 interface control plane, so as to facilitate the implementation of the IAB node
  • the cross-host switching process ensures communication between the IAB node and its downstream nodes.
  • Donor CU1 sends the second message to Donor CU2.
  • the second message includes at least one new IP address of the first IAB node used for the second F1 interface control plane.
  • the at least one new IP address includes multiple new IP addresses for the second F1 interface control plane (that is, Donor CU1 determines multiple IP addresses for the second F1 interface control plane)
  • communication method 100 Also included is Donor CU1 receiving a new IP address from the first IAB node for different traffic on the second F1 interface control plane.
  • the second message specifically includes a plurality of new IP addresses respectively corresponding to different traffic used for the second F1 interface control plane.
  • the first IAB node can send the new traffic information for different traffic of the second F1 interface control plane to Donor CU1 through the Uu interface (for example, through RRC messages) or the F1 interface (for example, through F1AP messages) with Donor CU1.
  • IP address In this embodiment of the present application, the second message specifically includes multiple new IP addresses respectively corresponding to different traffic used for the second F1 interface control plane. It can be understood that the second message includes the second F1 interface control plane. Identifiers of different flows, and multiple new IP addresses respectively corresponding to the identifiers of different flows on the control plane of the second F1 interface.
  • the identification of the traffic may include the traffic index (traffic index) of the traffic, the QoS parameter of the traffic (5QI or priority level or priority), the QoS attribute value of the traffic (DSCP or flow label), and the usage type of the traffic (usage type). at least one.
  • the second message or S106 is required.
  • the second message may be an IAB node traffic migration management request.
  • Response IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE
  • the above-mentioned first message does not exist or the above-mentioned first message is a newly defined interface (such as XN port) message between Donor CU1 and Donor CU2, then S106 is optional, that is, Donor CU1 may not A second message needs to be sent to Donor CU2.
  • the source address of the F1 interface establishment request information (such as the F1 SETUP REQUEST message) sent by the IAB node when establishing the cross-topology F1-C is at least one new address of the first IAB node for the second F1 interface control plane. IP address.
  • the function to be implemented by S106 can be implemented instead through the establishment request information of the F1 interface.
  • a new IP address used for the first flow of the second F1 interface control plane and a QoS attribute value corresponding to the new IP address used for the first flow of the second F1 interface control plane.
  • the traffic index or QoS parameter of the first traffic on the second F1 interface control plane, and the QoS attribute value corresponding to the traffic index or QoS parameter of the first traffic on the second F1 interface control plane are examples of the traffic index or QoS parameter of the first traffic on the second F1 interface control plane.
  • the traffic index of the first traffic on the second F1 interface control plane, the QoS parameters corresponding to the traffic index, and the QoS attribute values corresponding to the traffic index and/or QoS parameters of the first traffic on the second F1 interface control plane is any traffic in the second F1 interface control plane traffic.
  • the second message in this implementation may also include similar information about other traffic on the second F1 interface control plane. Different traffic types can be distinguished by the type of traffic or the QoS parameters of the traffic.
  • Figure 6 provides a schematic diagram of a communication method 200.
  • Donor CU1 determines the new IP address of the first IAB node for the first traffic of the user plane of the second F1 interface, where the second F1 interface is the interface between the first IAB node and Donor CU2.
  • Donor CU1 can determine the new IP address of the first IAB node for the first traffic of the second F1 interface user plane by itself. In other words, after S201, Donor CU1 can determine to execute S202 on its own without waiting for the trigger of any external message (such as a message from Donor CU2).
  • the cross-topology F1 interface can be established as soon as possible during the cross-host switching process of the IAB node, so as to facilitate the cross-host switching process of the IAB node and ensure the communication between the IAB node and its downstream nodes.
  • Donor CU1 determines on its own that it needs to perform cross-host switching of the first IAB node through at least one of the above-mentioned first to third possible cross-host switching processes.
  • the Donor CU1 determines the new IP address of the first IAB node for the first traffic of the second F1 interface user plane, which may include: the Donor CU1 sends the second IP address to the first IAB node.
  • RRC message the second RRC message includes at least one new IP address of the first IAB node for the second F1 interface user plane.
  • the first IAB node can communicate with Donor CU1 through the Uu interface (for example, through RRC messages) or the F1 interface (for example For example, sending a new IP address for the first traffic of the second F1 interface user plane to Donor CU1 through an F1AP message.
  • the first IAB node can also send a new IP address related to the first IAB node to Donor CU1 at the same time.
  • the new IP address used for the first flow of the second F1 interface user plane corresponds to the old IP address of the first IAB node used for the first flow of the first F1 interface user plane.
  • Donor CU1 stores the old IP address used for the first flow of the first F1 interface user plane
  • Donor CU1 receives the old IP address used for the first flow of the first F1 interface user plane and the user After the new IP address of the first traffic of the second F1 interface user plane, it can be accurately identified that the traffic corresponding to the new IP address is the first traffic of the first F1 interface user plane.
  • the Donor CU1 needs to first determine the IP address of the first IAB node. At least one new IP address for the user plane of the second F1 interface. Donor CU1 determines at least one new IP address of the first IAB node for the second F1 interface user plane, which may include: Donor CU1 requests at least one new IP address of the F1 interface user plane from Donor DU1, and Donor CU1 receives the request from Donor DU1.
  • Donor CU1 can be the first step in self-determined execution. In other words, after S201, Donor CU1 can determine to execute the first step of the above three implementation methods by itself without waiting for the trigger of any external message (such as a message from Donor CU2). In the above three implementation methods, Donor CU1 may also need to wait for the trigger of an external message (for example, the third message from Donor CU2), that is, S203, before deciding to execute the first step of the above three implementation methods.
  • an external message for example, the third message from Donor CU2
  • the third message and the first message may be the same message.
  • one message can realize the functions of S103 and S203 at the same time.
  • the above communication method 200 may also include:
  • the above communication method 200 may also include:
  • the fourth message may also include any of the following: (1) QoS attribute value corresponding to the new IP address used for the first traffic of the second F1 interface user plane, wherein the QoS attribute value may be Including DSCP or flow label. (2) QoS attributes corresponding to the traffic index (traffic index) or QoS parameters of the first traffic on the second F1 interface user plane value, where the QoS parameters may include: fifth generation mobile communication system QoS parameter indicator (5th Generation QoS indicator, 5QI) value, priority level value (priority level) or priority (priority).
  • 5QI fifth generation mobile communication system QoS parameter indicator
  • the transmission resources of the first traffic of the second F1 interface user plane may include at least one of a next hop node, a transmission path, and a transmission channel.
  • Donor DU1 can determine at least one of the BAP routing ID of the first flow of the second F1 interface user plane, the BAP Address of the next hop (Next Hop), and the BH RLC CH ID.
  • the target IAB host can obtain the necessary information for establishing the cross-topology F1 interface user plane, thereby establishing the cross-topology F1 interface user plane, so as to facilitate the implementation of the IAB node
  • the cross-host switching process ensures communication between the IAB node and its downstream nodes.
  • the communication method 100 and the communication method 200 can be executed before or after, or at the same time, or only the communication method 200 can be executed without executing the communication method 100, or only the communication method 100 can be executed without executing the communication method 200, which is not limited by this application.
  • Each operation in the communication method 100 and the communication method 200 can be combined with each other to form a new independent embodiment, and this application is not limited in this regard.
  • Donor CU2 obtains at least one new IP address of the first IAB node for the user plane of the second F1 interface.
  • the Donor CU2 can obtain at least one new IP address for the second F1 interface user plane through the existing IAB TRANSPORT MIGRATION MANAGEMENT process.
  • Donor CU2 sends at least one new IP address for the second F1 interface user plane to the first IAB node.
  • the Donor CU2 can send at least one message for the second F1 interface user plane to the first IAB node through the second F1 interface control plane (the second F1-C) that has been previously established (for example, established through the communication method 100).
  • New IP address For example, the Donor CU2 may send a second F1 interface control plane message (such as an F1AP message) to the first IAB node.
  • the second F1 interface control plane message includes at least the first IAB node's user plane for the second F1 interface. A new IP address.
  • the second F1 interface control plane message may also include the new IP address of the first IAB node used for the first traffic of the second F1 interface user plane.
  • the old IP address of the first IAB node used for the first traffic of the first F1 interface user plane is used for the first traffic of the first F1 interface user plane.
  • the second F1 interface control plane message only includes the first IAB corresponding to the new IP address of the first IAB node used for the first traffic of the second F1 interface user plane.
  • the second F1 interface control plane message may also include other information of the first IAB node used for the second F1 interface user plane.
  • the new IP address of the traffic, and the first IAB node used for the The new IP address of other traffic on the second F1 interface user plane corresponds to the old IP address of the first IAB node used for other traffic on the first F1 interface user plane.
  • the second F1 interface control plane message may also include the first IAB node corresponding to the new IP address of the first IAB node used for the first traffic of the second F1 interface user plane.
  • Donor CU2 can obtain the old IP address for the first flow of the first F1 interface user plane from the switch request mentioned in S101 or S201 before through other processes (for example, Donor CU2 can also Obtain the old IP address used for the first flow of the first F1 interface user plane by initiating an IAB TRANSPORT MIGRATION MANAGEMENT process (such as S301). Obtain the old IP address used for the first flow of the first F1 interface user plane.
  • Donor CU2 when Donor CU2 receives the old IP address used for the first flow of the first F1 interface user plane and the new IP address used for the first flow of the second F1 interface user plane, it can accurately identify the The traffic corresponding to the new IP address is the first traffic of the user plane of the first F1 interface.
  • the second F1 interface control plane message that the Donor CU2 can send to the first IAB node may only include at least one new IP of the first IAB node for the second F1 interface user plane. address, or does not include at least one old IP of the first IAB node used for the first F1 interface user plane corresponding to at least one new IP address of the first IAB node used for the second F1 interface user plane address.
  • Donor CU2 F1-terminating CU
  • Donor CU2 can obtain the new IP address of the first IAB node for the first traffic of the second F1 interface user plane, thereby utilizing the existing IAB TRANSPORT MIGRATION MANAGEMENT process.
  • the communication device can be the first node, the second node, the third node or the host in any possible design solution in the foregoing embodiment method.
  • the communication device includes: in the communication method provided by the previous embodiment, at least one corresponding unit for executing the method steps, operations or behaviors performed by the first node, the second node, the third node or the host node.
  • the setting of the at least one unit may have a one-to-one correspondence with the method steps, operations or behaviors performed by the first node, the second node, the third node or the host node.
  • These units can be implemented by computer programs, hardware circuits, or a combination of computer programs and hardware circuits.
  • the communication device provided by the present application will be described below with reference to FIG. 8 .
  • the communication device 800 can be applied to the second node.
  • the structure and functions of the communication device 800 will be divided into different designs to be described in detail below. Although the module names between different designs are the same, the structures and functions can be different.
  • the communication device 800 may include a processing module 801 and a sending module 802 .
  • the processing module 801 determines that the first IAB node needs to switch from Donor CU1 to Donor CU2.
  • the processing module 801 determines the first IAB node for the second At least one new IP address of the F1 interface control plane, where the second F1 interface is the interface between the first IAB node and the Donor CU2.
  • the processing module 801 causes the sending module 802 to send configuration information to Donor DU1, where the configuration information is used to configure the transmission resources of the second F1 interface control plane message.
  • the communication device 800 also includes a receiving module 803.
  • the receiving module 803 receives a first message from the Donor CU2.
  • the first message is used to request the first IAB node for the second F1 interface control plane. At least a new IP address.
  • the sending module 802 sends a first RRC message to the first IAB node, where the first RRC message includes at least one of the following: at least one new IP address used for the second F1 interface control plane.
  • the default BAP configuration of the first IAB node for transmitting the second F1 interface control plane message the default BAP configuration includes a default routing ID, and/or, a default BH RLC CH ID.
  • the first RRC message also includes identification information of the second distributed unit DU of the first IAB node corresponding to the at least one new IP address used for the second F1 interface control plane, wherein the first An IAB node at least includes a first DU and a second DU.
  • a first F1 interface exists between the first DU and the Donor CU1, and the second F1 interface is an interface between the second DU and the Donor CU2.
  • the sending module 802 sends a second message to the Donor CU2.
  • the second message includes at least one new IP address for the second F1 interface control plane, and/or, and the second message for the second F1 interface.
  • Quality of Service QoS attribute value corresponding to at least one new IP address on the interface control plane.
  • the processing module 801 determines at least one new IP address of the first IAB node for the second F1 interface control plane, including: the Donor CU1 determines the first IAB node for the second F1 interface control plane. All traffic to the same new IP address.
  • the receiving module 803 receives a new IP address from the first IAB node for different traffic of the second F1 interface control plane.
  • the configuration information is specifically used to instruct the Donor DU1 to determine the BAP routing ID, Next Hop BAP Address and BH RLC CH ID of the second F1 interface control plane message only based on the destination IP address of the second F1 interface control plane message. at least one of them.
  • the processing module 801 determines a new IP address of the first IAB node used for the first traffic of the second F1 interface user plane.
  • the receiving module 803 receives a third message from the Donor CU2, the third message is used to request at least one new IP address of the first IAB node for the second F1 interface user plane.
  • the sending module 802 sends a second RRC message to the first IAB node, where the second RRC message includes at least one new IP address of the first IAB node for the second F1 interface user plane.
  • the receiving module 803 receives a new IP address from the first IAB node for the first traffic of the second F1 interface user plane.
  • the sending module 802 sends a third RRC message to the first IAB node, where the third RRC message includes the new IP address of the first IAB node used for the first traffic of the second F1 interface user plane.
  • the third RRC message also includes identification information of the second DU of the first IAB node corresponding to the new IP address of the first IAB node used for the first traffic of the second F1 interface user plane. .
  • the third RRC message also includes the first flow for the second F1 interface user plane with the first IAB node.
  • the new IP address corresponds to the old IP address of the first IAB node used for the first traffic of the first F1 interface user plane.
  • the sending module 802 sends a fourth message to the Donor CU2, where the fourth message includes the new IP address used for the first traffic of the second F1 interface user plane.
  • the fourth message also includes a quality of service QoS attribute value corresponding to the new IP address used for the first traffic of the second F1 interface user plane.
  • the processing module 801 sends configuration information to the Donor DU1 based on the new IP address used for the first traffic of the second F1 interface user plane, and the configuration information is used to configure the third flow of the second F1 interface user plane.
  • a traffic transmission resource
  • the above-mentioned second RRC message and/or the above-mentioned third RRC message are the same RRC message as the above-mentioned first RRC message.
  • the communication device 900 includes one or more processors 901 and, optionally, an interface 902 .
  • the device 900 can be caused to implement the communication method provided by any of the foregoing embodiments and any possible design thereof.
  • the processor 901 is used to implement the communication method provided by any of the foregoing embodiments and any possible design thereof through logic circuits or execution of code instructions.
  • the interface 902 can be used to receive program instructions and transmit them to the processor, or the interface 902 can be used for the device 900 to communicate and interact with other communication devices, such as interactive control signaling and/or service data.
  • the interface 902 may be used to receive signals from other devices other than the device 900 and transmit them to the processor 901 or to send signals from the processor 901 to other communication devices other than the device 900 .
  • the interface 902 may be a code and/or data reading and writing interface circuit, or the interface 902 may be a signal transmission interface circuit between a communication processor and a transceiver, or a pin of a chip.
  • the communication device 900 may also include at least one memory 903, which may be used to store required related program instructions and/or data.
  • the device 900 may also include a power supply circuit 904.
  • the power supply circuit 904 may be used to power the processor 901.
  • the processor in this application can be a central processing unit (CPU).
  • the processor can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (Application Specific Integrated Circuits). specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, etc.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • ASIC application Specific Integrated Circuit
  • FPGA off-the-shelf programmable gate array
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc.
  • memory in this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM Synchronously connect dynamic random access memory
  • direct rambus RAM direct rambus RAM, DR RAM
  • the power supply circuit described in the embodiment of the present application includes but is not limited to at least one of the following: a power supply line, a power supply electronic system, a power management chip, a power consumption management processor, or a power consumption management control circuit.
  • the transceiver device, interface, or transceiver described in the embodiments of the present application may include a separate transmitter and/or a separate receiver, or the transmitter and receiver may be integrated.
  • the transceiver device, interface, or transceiver can operate under the instructions of the corresponding processor.
  • the transmitter can correspond to the transmitter in the physical device
  • the receiver can correspond to the receiver in the physical device.
  • the disclosed system, device and method can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of modules or units is only a logical function division.
  • there may be other division methods for example, multiple units or components may be combined. Either it can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • “implemented by software” may refer to the processor reading and executing program instructions stored in the memory to implement the functions corresponding to the above modules or units, where the processor refers to a processing circuit with the function of executing program instructions, Including but not limited to at least one of the following: central processing unit (CPU), microprocessor, digital signal processing (DSP), microcontroller unit (MCU), or artificial intelligence processing Various types of processing circuits that can run program instructions, such as processors. In other embodiments, the processor may also include circuits for other processing functions (such as hardware circuits, buses and interfaces for hardware acceleration, etc.).
  • the processor can be presented in the form of an integrated chip, for example, in the form of an integrated chip whose processing function only includes the function of executing software instructions, or it can also be presented in the form of a system on a chip (SoC), that is, on a chip , in addition to processing circuits (often called “cores") that can run program instructions, it also includes other hardware circuits used to implement specific functions (of course, these hardware circuits can also be implemented separately based on ASIC or FPGA).
  • SoC system on a chip
  • cores processing circuits
  • the processing function can also include various hardware acceleration functions (such as AI calculation, encoding and decoding, compression and decompression, etc.).
  • the hardware processing circuit can be composed of discrete hardware components, or it can be an integrated circuit. In order to reduce power consumption and size, it is usually implemented in the form of integrated circuits.
  • the hardware processing circuit may include ASIC, or programmable logic device (PLD); PLD may include FPGA, complex programmable logic device (CPLD), etc.
  • PLD programmable logic device
  • CPLD complex programmable logic device
  • These hardware processing circuits can be a separately packaged semiconductor chip (such as packaged into an ASIC); they can also be integrated with other circuits (such as CPU, DSP) and packaged into a semiconductor chip. For example, they can be formed on a silicon base.
  • SoC system on a programmable chip
  • each embodiment is described with its own emphasis.
  • parts that are not described in detail in a certain embodiment please refer to the relevant descriptions of other embodiments.
  • the embodiments of the present application can be combined, and some technical features in the embodiments can also be decoupled from specific embodiments.
  • the technical problems involved in the embodiments of the present application can be solved by combining with existing technologies.
  • the units described as separate components may or may not be physically separated.
  • the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Superior. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present application.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the above integrated units can be implemented in the form of hardware or software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage
  • the medium may include several instructions to cause a computer device, such as a personal computer, a server, a network device, etc., or a processor to perform all or part of the operations of the methods described in various embodiments of the present application.
  • the aforementioned storage media can include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, etc., which can store program code. media or computer-readable storage media.
  • transmission may include the following three situations: sending of data, receiving of data, or sending of data and receiving of data.
  • data may include service data and/or signaling data.
  • the number of nouns means “singular noun or plural noun", that is, “one or more”, unless otherwise specified. "At least one” means one or more. "Including at least one of the following: A, B, C.” means it can include A, or B, or C, or A and B, or A and C, or B and C, Or include A, B and C. Among them, A, B, and C can be single or multiple.

Landscapes

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

Abstract

La présente invention concerne un procédé et un appareil de communication, ainsi qu'un support de stockage. Une première unité centralisée donneuse (CU1 donneuse) détermine qu'un premier nœud à accès et liaison intégrés (IAB) doit commuter de la CU1 donneuse à une CU2 donneuse. La CU1 donneuse détermine au moins une nouvelle adresse de protocole Internet (IP) du premier nœud IAB utilisé pour un deuxième plan de commande d'interface F1, la deuxième interface F1 étant une interface entre le premier nœud IAB et la CU2 donneuse. La CU1 donneuse envoie des informations de configuration à une DU1 donneuse sur la base de la ou des nouvelles adresses IP utilisées pour le deuxième plan de commande d'interface F1, les informations de configuration étant utilisées pour configurer une ressource de transmission d'un deuxième message de plan de commande d'interface F1.
PCT/CN2023/101289 2022-06-20 2023-06-20 Procédé de communication et dispositif associé WO2023246746A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210695852.1 2022-06-20
CN202210695852.1A CN117320084A (zh) 2022-06-20 2022-06-20 一种通信方法及相关设备

Publications (1)

Publication Number Publication Date
WO2023246746A1 true WO2023246746A1 (fr) 2023-12-28

Family

ID=89287119

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/101289 WO2023246746A1 (fr) 2022-06-20 2023-06-20 Procédé de communication et dispositif associé

Country Status (2)

Country Link
CN (1) CN117320084A (fr)
WO (1) WO2023246746A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021147107A1 (fr) * 2020-01-23 2021-07-29 华为技术有限公司 Procédé et appareil de communication
WO2022082679A1 (fr) * 2020-10-22 2022-04-28 华为技术有限公司 Procédé de communication et dispositif associé
CN114600508A (zh) * 2019-11-08 2022-06-07 华为技术有限公司 Iab节点双连接建立的方法和通信装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114600508A (zh) * 2019-11-08 2022-06-07 华为技术有限公司 Iab节点双连接建立的方法和通信装置
WO2021147107A1 (fr) * 2020-01-23 2021-07-29 华为技术有限公司 Procédé et appareil de communication
WO2022082679A1 (fr) * 2020-10-22 2022-04-28 华为技术有限公司 Procédé de communication et dispositif associé

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Consideration of topology adaptation enhancement for R17 IAB", 3GPP DRAFT; R2-2101071, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051974076 *

Also Published As

Publication number Publication date
CN117320084A (zh) 2023-12-29

Similar Documents

Publication Publication Date Title
US20190166526A1 (en) Method for establishing a fronthaul interface, method for performing access for a ue, method and apparatus for performing a handover for a ue, data forwarding method, user equipment and base station
WO2020192783A1 (fr) Procédé, appareil et système de configuration de porteuse radio
WO2016173078A1 (fr) Procédé et système de transfert de données et ue doté d'une fonction de relais
WO2019242749A1 (fr) Procédé et dispositif de transfert intercellulaire
WO2020164615A1 (fr) Procédé de communication et dispositif associé
WO2022082679A1 (fr) Procédé de communication et dispositif associé
CN113556794A (zh) 通信方法、装置及系统
WO2020098747A1 (fr) Procédé et appareil de configuration de trajet de transmission
US20230254922A1 (en) Multipath transmission method and communication apparatus
WO2023011245A1 (fr) Procédé de communication et appareil de communication
WO2021238882A1 (fr) Procédé et dispositif d'implémentation de continuité de service
WO2021062803A1 (fr) Procédé et dispositif de transmission de paquets de données
WO2022205234A1 (fr) Procédé et appareil de communication
WO2021097858A1 (fr) Procédé et appareil de communication
US20240172084A1 (en) Data transmission method and apparatus
WO2022067818A1 (fr) Procédé et appareil de transmission de données
JP2023531787A (ja) Ｉａｂネットワーク通信方法及び関連デバイス
WO2021026706A1 (fr) Procédé et appareil de gestion d'interface f1
CN115699816A (zh) 用于在双连接下进行侧行链路中继通信的方法
WO2022001738A1 (fr) Procédé de traitement d'informatique à la frontière mobile, et dispositif associé
CN109691066B (zh) 数据复制下的处理方法及相关设备
EP3534662B1 (fr) Procédé de configuration de porteuse et produit associé
WO2022033543A1 (fr) Procédé de communication de relais, et appareil de communication
WO2021238318A1 (fr) Procédé et appareil de communication
WO2023246746A1 (fr) Procédé de communication et dispositif associé

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

Country of ref document: EP

Kind code of ref document: A1