WO2022205253A1 - 发送和接收信号的方法、装置和通信系统 - Google Patents

发送和接收信号的方法、装置和通信系统 Download PDF

Info

Publication number
WO2022205253A1
WO2022205253A1 PCT/CN2021/084795 CN2021084795W WO2022205253A1 WO 2022205253 A1 WO2022205253 A1 WO 2022205253A1 CN 2021084795 W CN2021084795 W CN 2021084795W WO 2022205253 A1 WO2022205253 A1 WO 2022205253A1
Authority
WO
WIPO (PCT)
Prior art keywords
path
node
iab
data
destination
Prior art date
Application number
PCT/CN2021/084795
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 CN202180096678.2A priority Critical patent/CN117121559A/zh
Priority to JP2023559859A priority patent/JP2024511815A/ja
Priority to PCT/CN2021/084795 priority patent/WO2022205253A1/zh
Priority to EP21933913.2A priority patent/EP4319314A4/en
Publication of WO2022205253A1 publication Critical patent/WO2022205253A1/zh
Priority to US18/372,189 priority patent/US20240015098A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/083—Reselecting an access point wherein at least one of the access points is a moving node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/22—Performing reselection for specific purposes for handling the traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/28—Connectivity information management, e.g. connectivity discovery or connectivity update for reactive routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • 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
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • the embodiments of the present application relate to the field of communication technologies.
  • IAB Integrated access and backhaul
  • NG-RAN next generation radio access network
  • IAB-node An integrated access and backhaul node
  • NR New Radio
  • IAB-donor represents a network device (eg, gNB) that supports IAB functionality.
  • An IAB-node can connect to an IAB host (IAB-donor) through one or more hops. These multi-hop connections form a Directed Acyclic Graph (DAG) topology with the IAB host as the root node.
  • DAG Directed Acyclic Graph
  • the IAB host is responsible for performing centralized resource management, topology management, and routing management in the IAB network topology.
  • IAB-node supports the function of gNB-DU (distributed unit, distributed unit). IAB-node DU is also called IAB-DU. IAB-DU is the wireless connection to the terminal equipment (UE) and the next hop IAB-node. The endpoint of the incoming (NR access) interface is also the endpoint of the F1 protocol to the gNB-CU (central unit) on the IAB-donor.
  • the IAB-DU can serve normal UEs and IAB sub-nodes.
  • the IAB-DU implements the network side device function, connects to the downstream child IAB-node, provides NR air interface access to the UE and the downstream child IAB-node, and establishes an F1 connection with the IAB donor-CU.
  • IAB-node In addition to the gNB-DU function, the IAB-node also supports a part of UE functions, called IAB-MT (Mobile Termination).
  • IAB-MT includes functions such as physical layer, layer 2, RRC and NAS to connect to another IAB-node Or gNB-DU of IAB-donor, gNB-CU connected to IAB-donor and connected to core network.
  • IAB-MT can support functions such as UE physical layer, access stratum (AS), radio resource control (RRC) layer and non-access stratum (NAS) layer, and can be connected to the IAB parent node.
  • AS access stratum
  • RRC radio resource control
  • NAS non-access stratum
  • FIG. 1 is a schematic diagram of the IAB topology.
  • the IAB-node 100 includes an IAB-MT functional unit 101 and an IAB-DU functional unit 102, and the adjacent nodes on the interface of the IAB-DU functional unit 102 are called child nodes ( child node), the child nodes 201, 202, 203 shown in FIG. 1, the IAB-DU functional unit 102 and the child nodes 201, 202, 203 can communicate through the air interface (Uu); the IAB-MT functional unit
  • the adjacent nodes on the interface of 101 are called parent nodes, such as parent nodes 301 and 302 as shown in FIG. ) to communicate.
  • the direction from the IAB-node 100 to the child nodes 201, 202, 203 is called the downstream direction
  • the direction from the IAB-node 100 to the parent nodes 301, 302 is called the upstream (upstream) direction.
  • the IAB-donor (not shown) performs centralized resource, topology and routing management for the IAB topology 10 .
  • the IAB-node In the process of moving, if the IAB-node disconnects from the original parent IAB-node, it connects to the new parent IAB-node, or, when the IAB-node maintains dual connection, the F1-U transmission path is transferred from a CG side Switching to another CG side will cause network topology changes, which will affect the routing changes of the IAB-node and its downstream sub-nodes.
  • Each uplink data packet is identified by the destination BAP address.
  • the BAP address of the destination DU carried in the Backhaul Adaptation Protocol (BAP) data packet header sent by the IAB-node and sub-nodes is the BAP address of the destination DU after the switch.
  • BAP Backhaul Adaptation Protocol
  • the address of the target Donor-DU, and the path identifier carried in the packet header corresponds to the new path identifier.
  • the IAB-node switches or converts the F1-U transmission path
  • the Donor-DU changes after the IAB-node switches or converts the F1-U path, the upstream data of the original path cannot reach the original Donor-DU.
  • the upstream data of the original path is transmitted through the new path, and will be discarded by the target-side Donor-DU, because the destination BAP address carried is inconsistent with the BAP address of the new Donor-DU.
  • Figure 2 is a schematic diagram of uplink data discarding.
  • IAB-node 3 disconnects from the parent node IAB-node1 and connects to IAB-node2, IAB-node 3, 4, 5
  • There is upstream data on the original path that has not been successfully sent (the target BAP address in the BAP header is 1).
  • the Donor-DU of IAB-node changes (that is, from Donor-DU 1 to Donor-DU 2)
  • IAB-node3 sends these unsuccessful upstream data along the new path, and the upstream data will be replaced by the new Donor -DU (BAP address 2) is discarded so that it cannot reach the Donor-CU.
  • the embodiments of the present application provide a method, device, and communication system for sending and receiving signals.
  • the destination BAP address of the first path of the IAB-node is unreachable, the data of the first path that is not successfully sent or the The route of the received data of the first path is changed, whereby data can be transmitted based on the changed route, and data loss can be avoided.
  • an apparatus for sending and receiving signals is provided, which is applied to an integrated access and backhaul node (IAB-node), and the apparatus includes:
  • a first processing unit configured to perform a routing change on the first path data that was not successfully sent or the first path data received when the destination BAP address of the first path of the IAB-node is unreachable;
  • a first transceiving unit which sends the unsuccessfully sent first path data or the received first path data based on the changed route.
  • an apparatus for sending and receiving signals is provided, which is applied to a sub-node of an integrated access and backhaul node (IAB-node), wherein the apparatus includes:
  • a second processing unit configured to perform a route change on the first path data that was not successfully sent or the first path data received when the destination BAP address of the first path of the IAB-node is unreachable;
  • a second transceiving unit which transmits the unsuccessfully transmitted first path data or the received first path data based on the changed route.
  • an apparatus for sending and receiving signals which is applied to a Donor-CU, and the apparatus includes:
  • the third transceiver unit when the destination BAP address of the first path of the IAB-node is unreachable, sends the path reconfiguration parameter to the IAB-node or the child node of the IAB-node, wherein the path reconfiguration parameter is a
  • the IAB-node or the sub-node performs a route change on the first path data that is not successfully sent or the first path data that is received.
  • a method for transmitting and receiving signals is provided, which is applied to an integrated access and backhaul node (IAB-node), and the method includes:
  • the unsuccessfully sent first path data or the received first path data is sent.
  • a method for sending and receiving signals is provided, which is applied to a sub-node of an integrated access and backhaul node (IAB-node), wherein the method includes:
  • the unsuccessfully sent first path data or the received first path data is sent.
  • a method for sending and receiving signals is provided, which is applied to a Donor-CU, and the method includes:
  • One of the beneficial effects of the embodiments of the present application is: when the destination BAP address of the first path of the IAB-node is unreachable, the route change is performed on the data of the first path that was not successfully sent or the data of the first path received, and the Therefore, data can be transmitted based on the changed route, and data loss can be avoided.
  • Fig. 1 is a schematic diagram of IAB topology
  • Fig. 2 is a schematic diagram of uplink data discarding
  • Fig. 3 is a schematic diagram of the change of network topology caused by the movement of IAB-node
  • FIG. 4 is a schematic diagram of a method for sending and receiving signals according to an embodiment of the first aspect of the present application
  • Fig. 5 is a schematic diagram of IAB-node and its sub-nodes performing routing change
  • Fig. 6 is a schematic diagram of the downstream child node of IAB-node sending end indication
  • Fig. 7 is a schematic diagram of IAB-node and its sub-nodes performing routing change when IAB-node has dual connections;
  • FIG. 8 is a schematic diagram of a method for transmitting and receiving a signal according to an embodiment of the second aspect of the present application.
  • FIG. 9 is a schematic diagram of a method for transmitting and receiving a signal according to an embodiment of the third aspect of the present application.
  • FIG. 10 is a schematic diagram of an apparatus for transmitting and receiving signals according to an embodiment of the fourth aspect of the present application.
  • FIG. 11 is a schematic diagram of an apparatus for transmitting and receiving signals according to an embodiment of the fifth aspect of the present application.
  • FIG. 12 is a schematic diagram of an apparatus for transmitting and receiving signals in an embodiment of the sixth aspect of the present application.
  • FIG. 13 is a schematic diagram of the structure of a network device according to an embodiment of the present application.
  • FIG. 14 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements in terms of numelation, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be referred to by these terms restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed items.
  • the terms “comprising”, “including”, “having”, etc. refer to the presence of stated features, elements, elements or components, but do not preclude 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 conforms to 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
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • High-Speed Packet Access High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to communication protocols at any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G , New Radio (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
  • Network device refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • Network devices may include, but are not limited to, the following devices: Integrated Access and Backhaul Node (IAB-node), Base Station (BS, Base Station), Access Point (AP, Access Point), Transmission Reception Point (TRP, Transmission Reception) Point), broadcast transmitter, Mobile Management Entity (MME, Mobile Management Entity), gateway, server, Radio Network Controller (RNC, Radio Network Controller), Base Station Controller (BSC, Base Station Controller) and so on.
  • IAB-node Integrated Access and Backhaul Node
  • BS Base Station
  • AP Access Point
  • TRP Transmission Reception Point
  • MME Mobile Management Entity
  • gateway server
  • Radio Network Controller Radio Network Controller
  • BSC Base Station Controller
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include a remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low power node (eg femeto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low power node eg femeto, pico, etc.
  • base station may include some or all of their functions, each base station may provide communication coverage for a particular geographic area.
  • the term "cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "User Equipment” (UE, User Equipment) or “Terminal Equipment” (TE, Terminal Equipment or Terminal Device), for example, refers to a device that accesses a communication network through a network device and receives network services.
  • a terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS, Mobile Station), a terminal, a subscriber station (SS, Subscriber Station), an access terminal (AT, Access Terminal), a station, and the like.
  • the terminal device may include but is not limited to the following devices: Cellular Phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • Cellular Phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication device
  • handheld device machine type communication device
  • laptop computer Cordless phones, smartphones, smart watches, digital cameras, and more.
  • the terminal device may also be a machine or device that performs monitoring or measurement, such as but not limited to: Machine Type Communication (MTC, Machine Type Communication) terminals, In-vehicle communication terminals, device-to-device (D2D, Device to Device) terminals, machine-to-machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • network side refers to one side of the network, which may be a certain base station, and may also include one or more network devices as described above.
  • user side or “terminal side” or “terminal device side” refers to the side of a user or terminal, which may be a certain UE, or may include one or more terminal devices as above.
  • the high-level signaling may be, for example, Radio Resource Control (RRC) signaling; for example, it is called an RRC message (RRC message), for example, including MIB, system information (system information), and dedicated RRC message; RRC IE (RRC information element).
  • RRC Radio Resource Control
  • the high-layer signaling may also be, for example, F1-C signaling, or the F1AP protocol.
  • F1-C signaling or the F1AP protocol.
  • the present application is not limited to this.
  • Fig. 3 is a schematic diagram of network topology change caused by IAB-node movement. As shown in Figure 3, after IAB-node5 switches from the cell under IAB-node3 to the cell under IAB-node 4, the route from IAB-node5 and its downstream child node IAB-node 6 to Donor-CU changes.
  • the Donor-CU configures the IAB-node through the RRC reconfiguration message for the uplink F1-C and non- The default return RLC channel (default BH RLC channel) and the default BAP routing ID (default BAP routing ID) of the target path of the F1 data. If the Donor-DU is changed after the switch, the Donor-CU may be configured for the IAB-node and can be routed to IP address of the target Donor-DU, where the default route identifier includes the BAP address and path ID of the target Donor-DU. After the IAB-node switches to the new parent node, the IAB-node starts to apply the above configuration, that is, transfers the transmission path to the target side.
  • Embodiments of the first aspect of the present application provide a method for transmitting and receiving signals.
  • the method is applied to an integrated access and backhaul node (IAB-node).
  • IAB-node integrated access and backhaul node
  • FIG. 4 is a schematic diagram of a method for transmitting and receiving a signal according to an embodiment of the first aspect. As shown in FIG. 4 , the method includes:
  • Operation 401 When the destination BAP address of the first path of the IAB-node is unreachable, perform a route change on the first path data that was not successfully sent or the first path data received;
  • Operation 402 Based on the changed route, send the first path data that was not successfully sent or the first path data that was received.
  • the routing of the data of the first path is changed, so that the data can be sent based on the changed route, and the loss of the data can be avoided.
  • performing a route change on the data of the first path includes: changing the destination BAP address of the first path data to the destination BAP address of the second path; or, changing the destination BAP address of the first path data
  • the destination BAP address of the second path is changed, and the path identifier of the first path data is changed to the path identifier of the second path.
  • the first path data that is not successfully sent that is, the first path data that has been generated or received, but has not been sent in the buffer or has been sent but has not yet received a correct response from the RLC layer. If the destination BAP address of the first path route cannot be reached, the IAB-node can change the route of the first path data to send it based on the changed route of the second path, so that it can reach the Donor-CU.
  • the first path may be an uplink data sending path of the IAB-node before the move, and the path formed after the route change is the second path.
  • sending the first path data may include: sending the first path data to a backhaul RLC channel between the IAB-node and the next hop node of the second path.
  • the IAB-node When the IAB-node changes the route of the first path data, it sends the first path data to the next hop node under the second path. If the Donor-CU has configured the IAB-node with the backhaul RLC channel from the previous hop node and the IAB-node or the access RLC channel to the backhaul RLC channel between the IAB-node and the next hop node of the second path
  • the mapping relationship that is, an appropriate next-hop RLC channel already exists, and the IAB-node can select the backhaul RLC channel for sending the first path data according to the mapping relationship. For example, in the case that the IAB-node has maintained a connection with the next hop node of the second path.
  • the IAB-node can select any backhaul RLC channel to the next-hop node of the second path to send the data of the first path. If the IAB-node is not connected to the next-hop node of the second path , the IAB-node needs to establish a connection with it before sending the first path data.
  • FIG. 5 is a schematic diagram of routing change performed by an IAB-node and its sub-nodes.
  • IAB-node3 transmits the upstream data of the original path (ie, the first path) along the target path (ie, the second path), it will not be discarded by the Donor-DU (BAP address is 2) on the target side.
  • the method may further include:
  • the IAB-node When the IAB-node considers that the first path data has been sent, it stops the routing change for the first path data.
  • the rerouting of the first path data may be stopped under any of the following conditions:
  • the IAB-node triggers the routing change of the data on the first path and starts the timer. After the timer expires, the routing change for the data on the first path is stopped; when the timer expires, it is considered that the IAB-node and child nodes no longer exist.
  • the first path data can stop the route change.
  • Condition 3 When the IAB-node finishes sending the unsuccessfully sent first path data and determines that the downstream child node has sent the unsuccessfully sent first path data, it stops the routing change of the first path data. This condition can be applied to the IAB-node. When the node and child nodes do not perform routing changes at the same time or the child nodes do not perform routing changes, in addition to sending the first path data cached by the IAB-node, it must also ensure that the downstream child nodes have sent the first path data that was not successfully sent. , it is considered that the first path data no longer exists.
  • the IAB-node when the IAB-node receives the end indication sent by the downstream child node of the IAB-node, it determines that the downstream child node has sent the first path data that was not successfully sent.
  • the end indication can be placed in the header of the data PDU of the BAP, or in the control PDU of the BAP.
  • FIG. 6 is a schematic diagram of a downstream child node of an IAB-node sending an end indication.
  • each downstream child node of the IAB-node sends an end indication to the parent node of the downstream child node after sending the unsuccessfully sent first path data buffered by itself. It is worth noting that when the child node receives the end instruction of the downstream child node, it does not directly forward it, but sends its own end instruction to the parent node after sending the first path data cached by itself, or stops sending the first path data. After the route is changed, an end indication is sent to the parent node.
  • the situation that the destination BAP address of the first path of the IAB-node is unreachable includes the following situation 1 or situation 2:
  • Case 2 The destination BAP address of the first path is unreachable after a wireless link failure occurs in the link between the IAB-node and the first parent node.
  • the method further includes:
  • the IAB-node receives the path reconfiguration parameter sent by the Donor-CU.
  • the parameters related to the route change are often not configured. For example, the route of the second path has not been established or even the connection with the next hop node of the second path has not been established. Relevant configuration is obtained so that the IAB-node can perform routing change in operation 401 .
  • the path reconfiguration parameters may include: the destination BAP address and the path identifier of the first path.
  • the path reconfiguration parameter may include: a mapping between the destination BAP address of the first path and the destination BAP address of the second path, or, including the destination BAP address and path identifier of the first path and the second path.
  • the mapping between the destination BAP address of the path and the path identifier enables different first paths to use different second path routes to route to different Donor-DUs, which can meet different QoS requirements of uplink data.
  • the path reconfiguration parameters may include: the destination BAP address of the second path, the path identifier of the second path, and the backhaul RLC channel identifier from the IAB-node to the next hop node of the second path.
  • the destination BAP address of the second path and the path identifier of the second path are used to replace the destination BAP address and path identifier in the BAP header of the first path data, and the return from the IAB-node to the next hop node of the second path
  • the RLC channel is an uplink backhaul RLC channel used to send the data of the first path to the next hop node of the second path.
  • the destination BAP address of the second path is the destination BAP address used for upstream F1-C and non-F1 data
  • the path identifier of the second path is the destination BAP address used for upstream F1-C and non-F1 data path identifier
  • the destination BAP address of the second path is the destination BAP address used for the upstream F1-U data
  • the path identifier of the second path is the path identifier used for the upstream F1-U data.
  • the IAB-node can use the second path route of the F1-C and non-F1 data as the route of the first path data;
  • the IAB-node can use the second path route of the F1-U data as a route for the first path data.
  • the backhaul RLC channel identifier from the IAB-node to the next hop node of the second path is: the backhaul RLC channel identifier for uplink F1-C and non-F1 data; or, for Return RLC channel identifier of uplink F1-U data.
  • the IAB-node can use the backhaul RLC channel for the F1-C and non-F1 data as the channel for sending the first path data
  • the IAB-node can use the channel for the F1-U data as a channel for sending the first path data.
  • the path reconfiguration parameters can be completed by the IAB-node to the new The F1AP message received from the Donor-CU after the switch of the parent node is sent, and when the IAB-node switches to the new parent node, it stops sending the first path data.
  • the IAB-node can stop sending scheduling requests to the parent node. (SR, Schedule Request) or buffer size request (BSR, Buffer Size Request) or stop scheduling the uplink resource grant of the child node.
  • the IAB-node When the IAB-node receives the F1AP message, it can trigger the routing change of the first path data. Because the first path data cannot reach the destination Donor-DU after the IAB-node is switched, stop sending the first path data immediately after the switch to avoid data loss.
  • the path reconfiguration parameters can be obtained through the RRC reconfiguration message received from the Donor-CU after the IAB-node completes the re-establishment to the new parent node or the The F1AP message is sent, and when the link between the IAB-node and the first parent node fails to send the first path data, for example, the IAB-node can stop sending SR and BSR to the parent node or stop scheduling The uplink resource grant of the child node.
  • the IAB-node triggers a routing change to the first path data after receiving the path reconfiguration parameters. Because the first path data cannot reach the destination Donor-DU after the link between the IAB-node and the parent node fails, immediately stopping sending the first path data can avoid data loss.
  • the path reconfiguration parameters can be sent from the IAB-node to the Donor-node
  • the CU sends the F1AP message received from the Donor-CU after reporting the radio link failure information, and stops sending the first path data when the link between the IAB-node and the first parent node fails in the radio link, for example,
  • the IAB-node can stop sending SR and BSR to the parent node or stop scheduling the uplink resource grant of the child node.
  • the IAB-node triggers a routing change to the first path data when receiving the F1AP message.
  • the first path data can also be routed without performing operation 404 .
  • the IAB-node forms a dual connection with the first parent node and the second parent node, wherein the link between the IAB-node and the first parent node fails wirelessly, and the link between the IAB-node and the second parent node fails. No radio link failure has occurred on the link.
  • the routing change of the first path data is triggered, and the destination BAP address in the BAP data packet header of the path passing through the first parent node is replaced is the destination BAP address of the path passing through the link between the IAB-node and the second parent node, or the destination BAP address and the path identifier are respectively replaced with the destination BAP address of the path passing through the link between the IAB-node and the second parent node and path identifiers.
  • the first path is the path passing through the link between the IAB-node and the first parent node
  • the second path is the path passing through the link between the IAB-node and the second parent node.
  • FIG. 7 is a schematic diagram of routing change performed by the IAB-node and its sub-nodes in the case of dual connection of the IAB-node.
  • IAB-node1 and IAB-node2 are the first parent node and the second parent node of IAB-node 3, respectively.
  • RLF occurs on the link between IAB-node 3 and the first parent node IAB-node1
  • no RLF occurs on the link between IAB-node 3 and the second parent node IAB-node2
  • IAB-node3 and its child nodes will One path data is routed to a second path that traverses the link where RLF does not occur.
  • the case where the destination BAP address of the first path of the IAB-node is unreachable is the above case 1 (that is, the destination BAP address of the first path is unreachable after the IAB-node switches to the new parent node).
  • the original Donor-DU is different from the target Donor-DU.
  • the IAB-node or its sub-nodes perform routing changes on the upstream F1 data of the original path (ie, the first path) buffered and received from the downstream node, and replace the BAP address of the original Donor-DU in the BAP header with the target Donor-
  • the BAP address of the DU ie, the destination BAP address of the second path
  • the IAB-node can send the upstream F1 data of the original path to the backhaul RLC channel between the IAB-node and the next hop node of the target side path, so as to send the first path data based on the changed route.
  • the target transmission path parameters for upstream F1-C and non-F1 data are configured by the RRC message sent by the donor-CU through the original path, including the destination Donor-DU address, path identifier and Uplink UL BH RLC channel.
  • the donor-CU can configure the target-side routing for uplink F1-U data through the same RRC message, including the destination Donor-DU address and path identifier and the UL BH RLC channel.
  • the IAB-node can use the destination Donor-DU address of the upstream F1-C and non-F1 data, the target side path identifier and the upstream UL BH RLC channel to transmit the buffered upstream F1-U data of the original path, or it can use the upstream F1-U for upstream F1-U data.
  • the destination path parameter of the data sends the upstream data of the original path.
  • the Donor-CU can configure parameters specifically for the routing change of the upstream data on the original path.
  • the IAB-node can keep the original destination address and path identifier for a period of time after the handover, or the Donor-CU can store the routing identifier (original Donor-DU address and original path identifier) of the uplink data that needs to be rerouted. Configured for IAB-node.
  • uplink data of different original Donor-DUs or original paths may need to be routed to different target Donor-DUs or transmitted using different target paths.
  • the Donor-CU can configure the mapping between the address of the original Donor-DU and the address of the target Donor-DU, or configure the mapping between the BAP address and the original path identifier of the original Donor-DU and the address of the target Donor-DU and the target path identifier.
  • the relevant configuration of the original path data routing change can be sent to the IAB-node through the RRC reconfiguration message during the handover or the F1AP message after the handover is completed.
  • the activation mode for the IAB-node to perform routing change of the original path data (that is, the method for triggering the routing change in operation 401) may include:
  • the IAB-node In the case that the IAB-node has saved the path update configuration, the IAB-node completes random access to the target cell; or, after the IAB-node completes the handover, it receives the original path data routing change related configuration sent by the F1AP message.
  • the deactivation (ie, performing operation 403) of the original path data routing change may include:
  • the IAB-node After the routing change of the original path data is activated, a timer is started, and after the timer expires, the routing change of the original path data is deactivated; or, the IAB-node deactivates the original path data after sending the currently cached original path data that was not successfully sent. or, when the IAB-node determines that all the original path data in the downstream node has been sent and the original path data that has not been sent successfully has been sent, deactivate the routing change of the original path data. For example, deactivate the child node.
  • an end instruction is sent to the parent node. When the IAB-node receives this end instruction, it means that all downstream child nodes have completed the route change by sending the original path data.
  • the uplink data generated after the handover is generated according to the path on the target side, therefore, the uplink data generated after the handover does not need to update the route.
  • the way in which the child node activates the route change of the original path data route change includes: when the child node has saved the path update configuration, after receiving the IAB-node to complete the random access to the target cell, sending When the handover success indication message is received, the original path data routing change is activated; or, after the IAB-node completes the handover, it activates the original path data routing change when it receives the configuration related to the original path data routing change sent by the Donor-CU through the F1AP message.
  • the deactivation method of the route change of the original path data of the child node includes: starting a timer after the child node activates the route change, and deactivates the route change of the original path data after the timer expires; or, the child node deactivates the current cache The original path data that is not successfully sent is deactivated after sending; or, the child node determines that it has sent all the original path data in the downstream node and deactivates the original path data that has not been successfully sent.
  • the case where the destination BAP address of the first path of the IAB-node is unreachable is the above-mentioned case 2 (that is, after the wireless link failure occurs in the link between the IAB-node and the first parent node, the first The destination BAP address of the path is unreachable).
  • the original Donor-DU is different from the new Donor-DU.
  • some uplink data of the original path may not be sent to the original parent node. If these data are sent directly through the new path, they may be discarded by the new Donor-DU.
  • the IAB-node or its sub-nodes change the route of the upstream F1 data of the original path that is buffered and received from the downstream node, and replaces the BAP address of the original Donor-DU in the BAP header with the BAP address of the new Donor-DU, or Replace the BAP address and the original path identifier of the original Donor-DU with the new Donor-DU address and the new path identifier, respectively.
  • the route change is performed on the upstream F1 data of the original path buffered and received from the downstream node.
  • the parameters of the new transmission path for upstream F1-C and non-F1 data are configured by the donor-CU.
  • the donor-CU may configure new transmission path parameters for uplink F1-U data through the same RRC message.
  • IAB-node can use the transmission path parameters of upstream F1-C and non-F1 data, including Donor-DU address, path identifier and upstream UL BH RLC channel to send buffered upstream F1-U data on the original path, and can also be used for F1-U
  • the transmission path parameters of the original path are sent to the uplink data.
  • the Donor-CU can configure parameters specifically for the routing change of the upstream data on the original path.
  • the IAB-node can keep the original destination address and path identifier for a period of time after the re-establishment is successful, or the Donor-CU can configure the original Donor-DU address and original path identifier to be rerouted to the IAB-node .
  • Donor-CU can configure the mapping between the original Donor-DU BAP address and the target Donor-DU BAP address, or configure the mapping between the BAP address and original path ID of the original Donor-DU and the target Donor-DU address and target path ID.
  • the configuration related to the change of the upstream data route of the original path can be sent to the IAB-node through the RRC reconfiguration message after re-establishment or the F1AP message after re-establishment.
  • the IAB-node After the IAB-node completes the access to the new cell, it can stop sending the uplink data of the original path through the new transmission path to prevent it from being discarded by the new Donor-DU.
  • the activation method for the IAB-node to perform data routing change may include: after the IAB-node completes the re-establishment, receiving the original data sent by the RRC message or the F1AP message Configuration related to route data routing changes.
  • Embodiment 1 for the way of deactivating the routing change of the original path data (ie, performing operation 403), and details are not repeated here.
  • the activation mode of the original path data routing change includes: when the child node has saved the path update configuration, for example, in the IAB- When the IAB-node is re-established to the target cell during the node handover, the child node activates the route change when it receives the re-establishment success indication message sent by the IAB-node after completing the random access to the new cell; or, the child node receives the Donor - Route change is activated when the configuration related to the route change of the original path data sent by the CU is changed.
  • Embodiment 2 reference may be made to Embodiment 1 for the deactivation method of the original path data routing change of the child node, which will not be repeated here.
  • the F1 transmission path is converted from one cell group (CG, Cell Group) to another CG, such as the BH chain between the IAB-node and the parent node of a CG Road occurs RLF.
  • RLF occurs on a path of an IAB-node, some uplink data sent through the RLF path may not reach the parent node. If these data are sent directly through another path without RLF, they will be discarded by the Donor-DU of the other path.
  • the IAB-node changes the route of the upstream F1 data buffered and received from the downstream node of the path passing through the RLF link, and replaces the BAP address of the Donor-DU corresponding to the path passing through the RLF link in the BAP header with the BAP address that does not pass through the RLF link.
  • the BAP address of the Donor-DU corresponding to the path of the RLF link, or the path identifier that passes through the RLF link is replaced with the path identifier that does not pass through the RLF link.
  • the IAB-node can send an RLF report to the Donor-CU through an RRC message.
  • SCG Secondary Cell Group
  • SCGFailureInformation secondary cell group error information
  • Donor-CU After Donor-CU receives the RLF report, Donor-CU can configure parameters for uplink data, that is, destination Donor-DU address and path identifier and UL BH RLC channel, and IAB-node can change the parameters according to the route change parameters configured by Donor-CU. Upstream data rerouting over the path where the RLF link occurs. The Donor-CU may also configure the routing identifier of the uplink data to be rerouted to the IAB-node.
  • the Donor-CU can be configured to use different routes for different paths through the RLF link.
  • the activation mode for the IAB-node to change the data route may include: the IAB-node detects that an RLF occurs on a link; or, the IAB-node receives Configuration related to the routing change of uplink data sent by the Donor-CU.
  • Embodiment 1 for the way of deactivating the routing change of the original path data (ie, performing operation 403), and details are not repeated here.
  • the uplink data generated after the F1 transmission path is switched from one CG to another CG does not need to update the route because it is generated according to the new path.
  • Embodiment 3 when the IAB-node detects RLF, it sends an RLF indication to the child node, and the RLF indication includes the route identifier (including the route identifier and the destination BAP address) of the path passing through the RLF link.
  • the child node reroutes the uplink F1 data that was not successfully sent and received from the downstream node through the path of the RLF link.
  • the Donor-CU can be configured to reroute the RLF path related parameters, that is, the destination BAP address and path identifier and the UL BH RLC channel, and the child node reroutes the uplink data of the RLF path according to the parameters.
  • the Donor-CU can also configure the routing identifier (including the destination BAP address and the path identifier) of the uplink F1 data that needs to be rerouted to the child node.
  • the activation method for changing the data route by the child node includes: when the child node receives the RLF instruction sent by the IAB-node, activating the route data route change; or, the child node receives the data sent by the Donor-CU When configuring upstream data rerouting, activate data routing change.
  • Embodiment 3 reference may be made to Embodiment 1 for the deactivation manner of the child node, which will not be repeated here.
  • the route of the data of the first path is changed, so that the data can be sent based on the changed route and data loss can be avoided.
  • the embodiment of the second aspect of the present application provides a method for transmitting and receiving a signal, which corresponds to the method of the embodiment of the first aspect.
  • the method for transmitting and receiving a signal of the embodiment of the second aspect of the present application is applied to a child node of an integrated access and backhaul node (IAB-node).
  • IAB-node integrated access and backhaul node
  • FIG. 8 is a schematic diagram of a method for transmitting and receiving a signal according to an embodiment of the second aspect. As shown in FIG. 8 , the method includes:
  • Operation 802 Based on the changed route, send the first path data that was not successfully sent or the first path data that was received.
  • the route of the data of the first path is changed, so that the data can be sent based on the changed route and data loss can be avoided.
  • routing changes are performed on the first path data, including:
  • sending the first path data includes sending the first path data to a backhaul RLC channel between the child node and a next-hop node of the second path.
  • the child node When the child node changes the route of the first path data, it sends the first path data to the next hop node under the second path. If the Donor-CU has configured the child node with the mapping relationship from the backhaul RLC channel or the access RLC channel between the previous hop node and the child node to the backhaul RLC channel between the child node and the next hop node of the second path , that is, an appropriate next-hop RLC channel already exists, and the sub-node can select the backhaul RLC channel for sending the first path data according to the mapping relationship. For example, when the child node maintains a connection with the next hop node of the second path.
  • the child node can select any backhaul RLC channel to the next hop node of the second path to send the first path data. If the child node is not connected to the next hop node of the second path, then The IAB-node needs to establish a connection with it before sending the first path data.
  • the situation that the destination BAP address of the first path of the IAB-node is unreachable includes the following situation 1 or situation 2:
  • Case 2 The destination BAP address of the first path is unreachable after a wireless link failure occurs in the link between the IAB-node and the first parent node.
  • the method further includes:
  • operation 803 may be performed if any of the following conditions are met:
  • Condition 1 Start the timer after the child node triggers the routing change of the first path data, and stop the routing change of the first path data after the timer expires; when the timer expires, it is considered that the child node and its downstream child nodes no longer exist
  • the first path data can stop the route change.
  • the child node After the child node has sent the first path data that was not successfully sent, it stops changing the route of the first path data; if the child node and its downstream child nodes perform routing changes at the same time, the child node and its downstream child nodes will When the unsuccessfully sent first path data cached by itself has been sent, it is considered that there is no first path data in the child node and its downstream child nodes, and the route change can be stopped.
  • Condition 3 When the child node has sent the first path data that was not successfully sent and it is determined that the downstream child node has sent the first path data that was not successfully sent, the routing change of the first path data is stopped. This condition can be applied to the child node. When a node and its downstream child nodes do not perform routing changes at the same time or their downstream child nodes do not perform routing changes, the child node must not only send the first path data cached by itself, but also ensure that its downstream child nodes have sent the unsuccessfully sent data. When the first path data is detected, it is considered that there is no need to re-route the first path data. For example, the child node may determine that the downstream child node has finished sending the unsuccessfully sent first path data when receiving the end indication sent by the downstream child node of the child node.
  • the method further includes:
  • the child node receives the path reconfiguration parameters sent by the Donor-CU.
  • the child node When the IAB-node leaves the original parent node, the child node is often not configured with parameters related to route change. For example, if the second path route has not been established in the child node, the relevant configuration can be obtained through operation 804.
  • the path reconfiguration parameter includes the destination BAP address and the path identifier of the first path. In this way, if part of the original path data does not require routing change, or the child node does not know which original paths require routing change, the Donor-CU can configure the path that the child node needs to perform routing change.
  • the path reconfiguration parameter includes: a mapping between the destination BAP address of the first path and the destination BAP address of the second path, or includes the destination BAP address and path identifier of the first path and the second path. The mapping between the destination BAP address of the path and the path identifier. Therefore, different first paths can be routed to different Donor-DUs by using different second paths, and different QoS requirements of uplink data can be satisfied.
  • the path reconfiguration parameter includes the destination BAP address of the second path, the path identifier of the second path, and the backhaul RLC channel identifier from the child node to the next hop node of the second path.
  • the destination BAP address of the second path and the path identifier of the second path are used to replace the destination BAP address and path identifier in the BAP header of the first path data, and the return RLC from the child node to the next hop node of the second path
  • the channel is an uplink backhaul RLC channel used to send the data of the first path to the next hop node of the second path.
  • the destination BAP address of the second path is the destination BAP address used for upstream F1-C and non-F1 data
  • the path identifier of the second path is the destination BAP address used for upstream F1-C and non-F1 data path identifier
  • the destination BAP address of the second path is the destination BAP address used for the upstream F1-U data
  • the path identifier of the second path is the path identifier used for the upstream F1-U data.
  • the second path route of F1-C and non-F1 data can be used as the route of the first path data; when the child node If a second path route for uplink F1-U data is also configured, the second path route of the F1-U data can be used as the route of the first path data.
  • the backhaul RLC channel identifier to the next hop node of the second path is: the backhaul RLC channel identifier for uplink F1-C and non-F1 data; or, for uplink F1- Return RLC channel identifier of U data.
  • the backhaul RLC channel for F1-C and non-F1 data can be used as the channel for sending the first path data.
  • a backhaul RLC channel for uplink F1-U data is also configured, and the channel for the F1-U data can be used as a channel for sending the first path data.
  • the path reconfiguration parameters are changed from the IAB-node after the handover is completed.
  • the F1AP message received by the Donor-CU is sent, and when the child node receives the handover success indication sent by the IAB-node after completing the random access to the new parent node, the first path data is stopped, for example, the child node It is possible to stop sending SR and BSR or stop scheduling uplink resource grants of downstream nodes.
  • the child node triggers a routing change to the first path data when receiving the F1AP message. Because the first path data cannot reach the destination Donor-DU after the IAB-node is switched, immediately stop sending the first path data after the IAB-Node is switched to avoid data loss.
  • the child node For sending the first path data, for example, the child node can stop sending the SR and BSR to the parent node or stop scheduling the uplink resource grant of the downstream node. After receiving the path reconfiguration parameter, the child node triggers a routing change to the first path data. Since the first path data cannot reach the destination Donor-DU after the IAB-node is re-established to the new parent node, the child node immediately stops sending the first path data after the IAB-Node is re-established to avoid data loss.
  • the path reconfiguration parameters are sent from the IAB-node to the Donor-CU Send the F1AP message received from the Donor-CU after reporting the radio link failure information, and when the child node receives the RLF indication sent when the link between the IAB-node and the first parent node has a radio link failure, Stop sending the first path data, and when the child node receives the F1AP message, trigger the routing change to the first path data.
  • the first path data can also be rerouted.
  • the IAB-node forms a dual connection with the first parent node and the second parent node, wherein the link between the IAB-node and the first parent node fails wirelessly, and the link between the IAB-node and the second parent node fails. No radio link failure has occurred on the link.
  • the child node when the child node receives the RLF indication sent when a radio link failure (RLF) occurs in the link between the IAB-node and the first parent node, it triggers the routing change of the first path data, which will go through
  • the destination BAP address in the BAP packet header of the link between the IAB-node and the first parent node is replaced with the destination BAP address corresponding to the path passing through the link between the IAB-node and the second parent node, or the destination BAP address and
  • the path identifier is respectively replaced with the destination BAP address and path identifier of the path passing through the link between the IAB-node and the second parent node.
  • the first path is the path passing through the link between the IAB-node and the first parent node
  • the second path is the path passing through the link between the IAB-node and the second parent node.
  • the RLF indication may include the destination BAP address and the path identifier of the first path, so that when an RLF occurs in the IAB-node, the child node can know which paths are affected by the RLF and need to perform a route change.
  • the routing of the data of the first path is changed, so that the child node can send the data based on the changed route to avoid data loss.
  • the embodiment of the third aspect of the present application provides a method for transmitting and receiving a signal, which corresponds to the method of the embodiment of the first aspect.
  • the methods for transmitting and receiving signals according to the embodiments of the third aspect of the present application are applied to a Donor-CU of an integrated access and backhaul node (IAB-node).
  • FIG. 9 is a schematic diagram of a method for transmitting and receiving a signal according to an embodiment of the third aspect. As shown in FIG. 9 , the method includes:
  • Operation 901 When the destination BAP address of the first path of the IAB-node is unreachable, send path reconfiguration parameters to the IAB-node or a child node of the IAB-node.
  • the path reconfiguration parameter is used for the IAB-node or a child node of the IAB-node to perform a routing change for the first path data that was not successfully sent or the first path data that was received.
  • the IAB-node or its sub-nodes can use the path reconfiguration parameters to change the route of the data of the first path, so that the IAB-node or the sub-nodes can send the data based on the changed route. data to avoid data loss.
  • the situation that the destination BAP address of the first path of the IAB-node is unreachable includes:
  • Case 2 The destination BAP address of the first path is unreachable after a wireless link failure occurs in the link between the IAB-node and the first parent node.
  • the path reconfiguration parameter may include the destination BAP address and the path identifier of the first path.
  • the path reconfiguration parameter includes the mapping between the destination BAP address of the first path and the destination BAP address of the second path, or includes the destination BAP address and path identifier of the first path and the difference between the destination BAP address of the first path and the path identifier of the second path. Mapping of destination BAP addresses and path identifiers.
  • the path reconfiguration parameters include: the destination BAP address of the second path, the path identifier of the second path, and the backhaul RLC channel identifier from the IAB-node to the next hop node of the second path.
  • the destination BAP address of the second path is the destination BAP address used for upstream F1-C and non-F1 data
  • the path identifier of the second path is the path identifier used for upstream F1-C and non-F1 data
  • the destination BAP address of the path is the destination BAP address used for the upstream F1-U data
  • the path identifier of the second path is the path identifier used for the upstream F1-U data.
  • the backhaul RLC channel identifier to the next hop node of the second path is: the backhaul RLC channel identifier for uplink F1-C and non-F1 data; or, for uplink F1-C Return RLC channel identifier of U data.
  • the Donor-CU sends the IAB-node or to the child node after the IAB-node completes the re-establishment to the new parent node.
  • the IAB-node or its sub-nodes can use the path reconfiguration parameters to change the route of the data of the first path, so that the IAB-node or the sub-nodes can send the data based on the changed route. data to avoid data loss.
  • Embodiments of the present application provide an apparatus for sending and receiving signals.
  • the apparatus may be, for example, an integrated access and backhaul node, or may be one or some components or components configured in the integrated access and backhaul node.
  • the integrated access and backhaul node is, for example, the one shown in FIG. 5 .
  • the apparatus corresponds to the method of an embodiment of the first aspect.
  • FIG. 10 is a schematic diagram of an apparatus for sending and receiving signals according to an embodiment of the fourth aspect of the present application.
  • the apparatus 1000 for sending and receiving signals includes:
  • a first processing unit 1001 configured to perform a routing change on the first path data that was not successfully sent or the first path data received when the destination BAP address of the first path of the IAB-node is unreachable;
  • the first transceiving unit 1002 which transmits the unsuccessfully sent first path data or the received first path data based on the changed route.
  • performing a routing change on the first path data includes:
  • the destination BAP address of the first path data is changed to the destination BAP address of the second path, and the path identifier of the first path data is changed to the path identifier of the second path.
  • the sending of the first path data includes:
  • the first path data is sent to the backhaul RLC channel between the IAB-node and the next hop node of the second path.
  • the situation that the destination BAP address of the first path of the IAB-node is unreachable includes:
  • the destination BAP address of the first path is unreachable; or, the first path is caused by a radio link failure in the link between the IAB-node and the first parent node.
  • the destination BAP address is unreachable.
  • the first processing unit 1001 further performs the following operations:
  • the first processing unit 1001 determines that the downstream child node has finished sending the unsuccessfully sent first path data.
  • the second path passes through the IAB-node The path of the link with the second parent node, wherein no wireless link failure occurs in the link between the IAB-node and the second parent node.
  • the first processing unit 1001 triggers the IAB-node to process the first path data Routing changes.
  • RLF radio link failure
  • the first transceiver unit 1002 further receives a path reconfiguration parameter sent by the Donor-CU, where the path reconfiguration parameter includes a destination BAP address and a path identifier of the first path.
  • the first transceiver unit 1002 further receives a path reconfiguration parameter sent by the Donor-CU, where the path reconfiguration parameter includes a difference between the destination BAP address of the first path and the destination BAP address of the second path
  • the mapping or, includes the mapping between the destination BAP address and path identifier of the first path and the destination BAP address and path identifier of the second path.
  • the first transceiver unit 1002 further receives a path reconfiguration parameter sent by the Donor-CU, where the path reconfiguration parameter includes the destination BAP address of the second path, the path identifier of the second path, and the IAB -backhaul RLC channel identifier from node to the next hop node of the second path.
  • the destination BAP address of the second path is the destination BAP address used for upstream F1-C and non-F1 data
  • the path identifier of the second path is the destination BAP address used for upstream F1-C and non-F1 data.
  • path identifier; or, the destination BAP address of the second path is the destination BAP address used for the upstream F1-U data
  • the path identifier of the second path is the path identifier used for the upstream F1-U data.
  • the backhaul RLC channel identifier to the next hop node of the second path is:
  • the path reconfiguration parameter is sent by the RRC reconfiguration message for handover sent by the Donor-CU, wherein when the IAB-node completes the random access to the new parent node, the first processing unit 1001 triggers the first processing unit 1001 Routing changes for path data.
  • the path reconfiguration parameters are completed by the IAB-node to the new parent node.
  • the F1AP message received from the Donor-CU after the handover is sent, wherein, when the IAB-node switches to the new parent node, the first transceiver unit 1002 stops sending the first path data, and the IAB-node receives When the F1AP message arrives, the first processing unit 1001 triggers the routing change of the first path data.
  • the path reconfiguration parameter is passed through the IAB - Send the RRC reconfiguration message or F1AP message received from the Donor-CU after the node completes the re-establishment to the new parent node, wherein, when the link between the IAB-node and the first parent node fails, the radio link fails
  • the first transceiver unit 1002 stops sending the first path data
  • the first processing unit 1001 triggers the routing change of the first path data.
  • the path reconfiguration parameter is set by the IAB - Send the F1AP message received from the Donor-CU after the node reports the radio link failure information to the Donor-CU, where:
  • the first transceiver unit 1002 stops sending the first path data, and when the first transceiver unit 1002 receives the F1AP message, the first transceiver unit 1002 A processing unit 1001 triggers a routing change of the first path data.
  • the route of the data of the first path is changed, so that the data can be sent based on the changed route and data loss can be avoided.
  • Embodiments of the present application provide an apparatus for sending and receiving signals.
  • the device may be, for example, a sub-node of the integrated access and backhaul node, or may be one or some components or components configured in the sub-node.
  • the integrated access and backhaul node is, for example, the IAB- node 3.
  • the apparatus corresponds to the method of an embodiment of the second aspect.
  • FIG. 11 is a schematic diagram of an apparatus for sending and receiving signals according to an embodiment of the fifth aspect of the present application. As shown in FIG. 11 , the apparatus 1100 for sending and receiving signals includes:
  • the second processing unit 1101 which, when the destination BAP address of the first path of the IAB-node is unreachable, performs routing change on the first path data that was not successfully sent or the first path data received;
  • the second transceiving unit 1102 sends the unsuccessfully sent first path data or the received first path data based on the changed route.
  • performing a routing change on the first path data includes:
  • the BAP address of the first path data is changed to the BAP address of the second path, and the path identifier of the first path data is changed to the path identifier of the second path.
  • the sending the first path data includes:
  • the first path data is sent to the backhaul RLC channel between the child node and the next hop node of the second path.
  • the situation that the destination BAP address of the first path of the IAB-node is unreachable includes:
  • the destination BAP address of the first path is unreachable; or,
  • the destination BAP address of the first path is unreachable.
  • the second processing unit 1101 further performs the following operations:
  • the routing change of the first path data is stopped.
  • the second processing unit 110 upon receiving an end indication sent by a downstream child node of the child node, determines that the downstream child node has finished sending the unsuccessfully sent first path data.
  • the second path passes through the IAB-node The path of the link with the second parent node, wherein the link between the IAB-node and the second parent node has no wireless link failure.
  • the second processing unit 1101 Trigger the child node to change the route of the first path data.
  • RLF radio link failure
  • the RLF indication includes a destination BAP address and a path identifier of the first path.
  • the second transceiver unit 1102 further receives a path reconfiguration parameter sent by the Donor-CU, where the path reconfiguration parameter includes a destination BAP address and a path identifier of the first path.
  • the second transceiver unit 1102 further receives a path reconfiguration parameter sent by the Donor-CU, where the path reconfiguration parameter includes a difference between the destination BAP address of the first path and the destination BAP address of the second path
  • the mapping or, includes the mapping between the destination BAP address and path identifier of the first path and the destination BAP address and path identifier of the second path.
  • the second transceiver unit 1102 further receives a path reconfiguration parameter sent by the Donor-CU, where the path reconfiguration parameter includes the destination BAP address of the second path, the path identifier of the second path, and the path reconfiguration parameter of the second path. Return the RLC channel identifier from the child node to the next hop node of the second path.
  • the destination BAP address of the second path is the destination BAP address used for upstream F1-C and non-F1 data
  • the path identifier of the second path is the destination BAP address used for upstream F1-C and non-F1 data.
  • path identifier; or, the destination BAP address of the second path is the destination BAP address used for the upstream F1-U data
  • the path identifier of the second path is the path identifier used for the upstream F1-U data.
  • the backhaul RLC channel identifier to the next hop node of the second path is:
  • the path reconfiguration parameters are reconfigured by the RRC before the IAB-node switchover message sending, wherein, when the second transceiver unit 1102 receives the handover success indication sent after the IAB-node completes the random access to the new parent node, the second processing unit 1101 triggers the routing of the first path data change.
  • the path reconfiguration parameters are changed from Donor- The F1AP message received by the CU is sent, where:
  • the second transceiver unit 1102 When the second transceiver unit 1102 receives the handover success indication sent after the IAB-node completes the random access to the new parent node, it stops sending the first path data; and,
  • the second processing unit 1101 triggers a route change of the first path data.
  • the path reconfiguration parameter is set by the IAB - Send the RRC reconfiguration message sent by the Donor-CU before the radio link failure of the node, where:
  • the second processing unit 1101 triggers the routing change of the first path data.
  • the path reconfiguration parameter is set by the IAB - Send an RRC reconfiguration message or F1AP message received from the Donor-CU after the node completes the re-establishment to the new parent node, where:
  • the second transceiver unit 1102 stops sending the first path data when receiving the re-establishment success indication sent by the IAB-node after completing the random access to the new parent node;
  • the second processing unit 1101 triggers a routing change of the first path data.
  • the path reconfiguration parameter is set by the IAB - Send the F1AP message received from the Donor-CU after the node reports the radio link failure information to the Donor-CU, where:
  • the second transceiver unit 1102 When the second transceiver unit 1102 receives the RLF indication sent when the link between the IAB-node and the first parent node fails in the radio link, it stops sending the first path data;
  • the second processing unit 1101 triggers a route change of the first path data.
  • the route of the data of the first path is changed, so that the data can be sent based on the changed route and data loss can be avoided.
  • Embodiments of the present application provide a device for transmitting and receiving signals.
  • the device may be, for example, a host central unit (IAB-donor CU), or may be one or some components or components configured in the host central unit (IAB-donor CU), for example, the host central unit (IAB-donor CU) is The Donor CU of Figure 5.
  • the sending and receiving apparatus corresponds to the method for sending and receiving a signal described in the embodiment of the third aspect.
  • FIG. 12 is a schematic diagram of an apparatus for transmitting and receiving signals in an embodiment of the sixth aspect. As shown in FIG. 12 , the apparatus 1200 includes:
  • the third transceiver unit 1201 when the destination BAP address of the first path of the IAB-node is unreachable, sends the path reconfiguration parameter to the IAB-node or the child node of the IAB-node, wherein the path reconfiguration parameter is used for The IAB-node or the sub-node performs routing change on the first path data that was not successfully sent or the first path data that was received.
  • the path reconfiguration parameter includes a destination BAP address and a path identifier of the first path.
  • the path reconfiguration parameter includes a mapping between the destination BAP address of the first path and the destination BAP address of the second path, or includes the destination BAP address and path identifier of the first path and the first path. The mapping between the destination BAP address of the two paths and the path identifier.
  • the situation that the destination BAP address of the first path of the IAB-node is unreachable includes:
  • the destination BAP address of the first path is unreachable; or,
  • the destination BAP address of the first path is unreachable.
  • the path reconfiguration parameter includes a destination BAP address of the second path, a path identifier of the second path, and a backhaul RLC channel identifier from the IAB-node to the next hop node of the second path .
  • the destination BAP address of the second path is the destination BAP address used for upstream F1-C and non-F1 data
  • the path identifier of the second path is the destination BAP address used for upstream F1-C and non-F1 data.
  • the destination BAP address of the second path is the destination BAP address used for the upstream F1-U data
  • the path identifier of the second path is the path identifier used for the upstream F1-U data.
  • the backhaul RLC channel identifier to the next hop node of the second path is:
  • the third transceiver unit 1201 sends an RRC reconfiguration message including the path reconfiguration parameter to the IAB-node or to the sub-node before the IAB-node handover; or,
  • the third transceiver unit 1201 sends an F1AP message including the path reconfiguration parameter to the IAB-node or to the child node after the IAB-node completes the handover to the new parent node.
  • the third transceiving unit 1201 in the case that the destination BAP address of the first path is unreachable after a wireless link failure occurs in the link between the IAB-node and the first parent node, the third transceiving unit 1201 will After completing the re-establishment to the new parent node, the IAB-node sends an RRC reconfiguration message or an F1AP message including the path reconfiguration parameter to the IAB-node or to the child node.
  • the third transceiver unit 1201 in the case that the destination BAP address of the first path is unreachable after a wireless link failure occurs in the link between the IAB-node and the first parent node, the third transceiver unit 1201 is in the After reporting the radio link failure information to the Donor-CU, the IAB-node sends an RRC reconfiguration message or an F1AP message containing the path reconfiguration parameters to the IAB-node or to the sub-node.
  • the third transceiver unit 1201 in the case that the destination BAP address of the first path is unreachable after a wireless link failure occurs in the link between the IAB-node and the first parent node, the third transceiver unit 1201 is in the Before the radio link failure occurs, the IAB-node sends an RRC reconfiguration message including the path reconfiguration parameter to the sub-node.
  • the IAB-node or its sub-nodes can use the path reconfiguration parameters to change the route of the data of the first path, so that the IAB-node or the sub-nodes can send the data based on the changed route. data to avoid data loss.
  • An embodiment of the present application further provides a communication system, and reference may be made to FIG. 1 , and the same contents as those of the embodiments of the first aspect to the sixth aspect will not be repeated.
  • the communication system may include:
  • IAB-donor CU a host central unit comprising the apparatus 1200 for transmitting and receiving signals as described in the embodiments of the fourth aspect
  • an integrated access and backhaul node comprising the apparatus 1000 for transmitting and receiving signals as described in the embodiments of the fourth aspect.
  • the child node includes the apparatus 1100 for transmitting and receiving signals as described in the embodiment of the fifth aspect.
  • the integrated access and backhaul node may include an IAB-MT functional unit and an IAB-DU functional unit.
  • the IAB-MT functional unit may have the same structure as the terminal equipment.
  • the IAB-DU functional unit and the host central unit (IAB-donor CU) may have the same units as the network equipment.
  • FIG. 13 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • the network device 1300 may include: a processor 1310 (eg, a central processing unit CPU) and a memory 1320 ; the memory 1220 is coupled to the processor 1310 .
  • the memory 1320 can store various data; in addition, the program 1330 for information processing is also stored, and the program 1330 is executed under the control of the processor 1310 .
  • the processor 1310 may be configured to execute a program to implement the method performed by the IAB-DU in the embodiment of the first aspect or the IAB-donor CU in the embodiment of the second aspect.
  • the network device 1300 may further include: a transceiver 1340, an antenna 1350, and the like; wherein, the functions of the above components are similar to those in the prior art, and are not repeated here. It is worth noting that the network device 1300 does not necessarily include all the components shown in FIG. 13 ; in addition, the network device 1300 may also include components not shown in FIG. 13 , and reference may be made to the prior art.
  • FIG. 14 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 1400 may include a processor 1410 and a memory 1420 ; the memory 1420 stores data and programs, and is coupled to the processor 1410 .
  • this figure is exemplary; other types of structures may be used in addition to or in place of this structure to implement telecommunication functions or other functions.
  • the processor 1410 may be configured to execute a program to implement the method performed by the IAB-MT as described in the embodiments of the first aspect.
  • the terminal device 1400 may further include: a communication module 1430 , an input unit 1440 , a display 1450 , and a power supply 1460 .
  • the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the terminal device 1400 does not necessarily include all the components shown in FIG. 14 , and the above components are not required; in addition, the terminal device 1400 may also include components not shown in FIG. 14 . There is technology.
  • the embodiment of the present application further provides a computer program, wherein when the program is executed in the IAB, the program causes the IAB to execute the method for sending and receiving signals according to the embodiment of the first aspect.
  • the embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program causes the IAB to execute the method for sending and receiving a signal according to the embodiment of the first aspect.
  • the embodiment of the present application further provides a computer program, wherein when the program is executed in a child node of an IAB-node, the program causes the child node to execute the method described in the embodiments of the second aspect.
  • the embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program causes a child node of the IAB-node to execute the method described in the embodiment of the second aspect.
  • the embodiment of the present application further provides a computer program, wherein when the program is executed in the Donor-CU, the program causes the Donor-CU to execute the method described in the embodiments of the third aspect.
  • the embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program causes the Donor-CU to execute the method described in the embodiment of the third aspect.
  • the apparatuses and methods above in the present application may be implemented by hardware, or may be implemented by hardware combined with software.
  • the present application relates to a computer-readable program that, when executed by logic components, enables the logic components to implement the above-described apparatus or constituent components, or causes the logic components to implement the above-described various methods or steps.
  • the present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, and the like.
  • the method/apparatus described in conjunction with the embodiments of this application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams shown in the figures and/or one or more combinations of the functional block diagrams may correspond to either software modules or hardware modules of the computer program flow.
  • These software modules may respectively correspond to the various steps shown in the figure.
  • These hardware modules can be implemented by, for example, solidifying these software modules using a Field Programmable Gate Array (FPGA).
  • FPGA Field Programmable Gate Array
  • a software module may reside 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 can be coupled to the processor, such that the processor can read information from, and write information to, the storage medium; or the storage medium can be an integral part of the processor.
  • the processor and storage medium may reside in an ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
  • the functional blocks and/or one or more combinations of the functional blocks described in the figures can be implemented as a general-purpose processor, a digital signal processor (DSP) for performing the functions described in this application ), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof.
  • DSP digital signal processor
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described with respect to the figures can also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, multiple microprocessors processor, one or more microprocessors in communication with the DSP, or any other such configuration.
  • the unsuccessfully sent first path data or the received first path data is sent.
  • routing change to the first path data comprises:
  • the destination BAP address of the first path data is changed to the destination BAP address of the second path, and the path identifier of the first path data is changed to the path identifier of the second path.
  • the destination BAP address of the first path is unreachable; or,
  • the destination BAP address of the first path is unreachable.
  • the IAB-node starts a timer after triggering the routing change of the data of the first path, and stops the routing change of the first path data after the timer expires;
  • the IAB-node finishes sending the unsuccessfully sent first path data and determines that the downstream child node has completed sending the unsuccessfully sent first path data, it stops changing the route of the first path data.
  • the IAB-node When the IAB-node receives the end indication sent by the downstream child node, it is determined that the downstream child node has finished sending the unsuccessfully sent first path data.
  • the second path is a path passing through the link between the IAB-node and the second parent node, wherein no wireless link failure occurs in the link between the IAB-node and the second parent node.
  • RLF radio link failure
  • the IAB-node receives the path reconfiguration parameter sent by the Donor-CU, and the path reconfiguration parameter includes the destination BAP address and the path identifier of the first path.
  • the IAB-node receives the path reconfiguration parameter sent by the Donor-CU, where the path reconfiguration parameter includes the mapping between the destination BAP address of the first path and the destination BAP address of the second path, or includes The mapping between the destination BAP address and the path identifier of the first path and the destination BAP address and path identifier of the second path.
  • the IAB-node receives the path reconfiguration parameters sent by the Donor-CU, where the path reconfiguration parameters include the destination BAP address of the second path, the path identifier of the second path, and the distance from the IAB-node to the Return RLC channel identifier of the next hop node of the second path.
  • the destination BAP address of the second path is the destination BAP address used for upstream F1-C and non-F1 data
  • the path identifier of the second path is the path identifier used for upstream F1-C and non-F1 data
  • the destination BAP address of the second path is the destination BAP address used for the upstream F1-U data
  • the path identifier of the second path is the path identifier used for the upstream F1-U data.
  • the identifier of the backhaul RLC channel to the next hop node of the second path is:
  • the path reconfiguration parameter is sent by an RRC reconfiguration message for handover sent by the Donor-CU, wherein the method further includes: triggering the IAB-node to complete random access to the new parent node The routing of the first path data is changed.
  • the path reconfiguration parameters are sent by the F1AP message received from the Donor-CU after the IAB-node completes the handover to the new parent node, wherein the method further includes:
  • the routing change of the first path data is triggered.
  • the path reconfiguration parameters are sent through the RRC reconfiguration message or the F1AP message received from the Donor-CU after the IAB-node completes the re-establishment to the new parent node, and the method further includes:
  • the IAB-node After receiving the path reconfiguration parameter, the IAB-node triggers a routing change to the first path data.
  • the path reconfiguration parameters are sent by the F1AP message received from the Donor-CU after the IAB-node reports the radio link failure information to the Donor-CU, wherein the method further includes:
  • the routing change of the first path data is triggered.
  • the unsuccessfully sent first path data or the received first path data is sent.
  • routing change to the first path data comprises:
  • the BAP address of the first path data is changed to the BAP address of the second path, and the path identifier of the first path data is changed to the path identifier of the second path.
  • the destination BAP address of the first path is unreachable; or,
  • the destination BAP address of the first path is unreachable.
  • the child node triggers a route change on the first path data and starts a timer, and stops the route change on the first path data after the timer expires;
  • the child node When the child node receives the end indication sent by the downstream child node of the child node, it is determined that the downstream child node has finished sending the unsuccessfully sent first path data.
  • the second path is a path passing through the link between the IAB-node and the second parent node, wherein no wireless link failure occurs in the link between the IAB-node and the second parent node.
  • the child node When the child node receives the RLF indication sent when a radio link failure (RLF) occurs in the link between the IAB-node and the first parent node, it triggers the child node to route the first path data change.
  • RLF radio link failure
  • the child node receives the path reconfiguration parameter sent by the Donor-CU, where the path reconfiguration parameter includes the destination BAP address and the path identifier of the first path.
  • the child node receives the path reconfiguration parameter sent by the Donor-CU, where the path reconfiguration parameter includes the mapping between the destination BAP address of the first path and the destination BAP address of the second path, or includes all The mapping between the destination BAP address and the path identifier of the first path and the destination BAP address and path identifier of the second path.
  • the child node receives the path reconfiguration parameter sent by the Donor-CU, where the path reconfiguration parameter includes the destination BAP address of the second path, the path identifier of the second path, and the path from the child node to the Return RLC channel identifier of the next hop node of the second path.
  • the destination BAP address of the second path is the destination BAP address used for upstream F1-C and non-F1 data
  • the path identifier of the second path is the path identifier used for upstream F1-C and non-F1 data
  • the destination BAP address of the second path is the destination BAP address used for the upstream F1-U data
  • the path identifier of the second path is the path identifier used for the upstream F1-U data.
  • the identifier of the backhaul RLC channel to the next hop node of the second path is:
  • the path reconfiguration parameter is sent by an RRC reconfiguration message before the IAB-node handover, wherein the method further includes: the child node completes random access to a new parent node upon receiving the IAB-node
  • the routing change of the first path data is triggered when the handover success indication is sent later.
  • the path reconfiguration parameters are sent by the F1AP message received from the Donor-CU after the IAB-node completes the handover, wherein the method further includes:
  • the routing change of the first path data is triggered.
  • the path reconfiguration parameter is sent by the RRC reconfiguration message sent by the Donor-CU before the radio link failure of the IAB-node occurs, wherein the method further includes:
  • the routing change of the first path data is triggered.
  • the path reconfiguration parameters are sent by the RRC reconfiguration message or the F1AP message received from the Donor-CU after the IAB-node completes the re-establishment to the new parent node, wherein the method further includes:
  • the child node stops sending the first path data when receiving the re-establishment success indication sent after the IAB-node completes the random access to the new parent node;
  • the child node After receiving the path reconfiguration parameter, the child node triggers a routing change to the first path data.
  • the path reconfiguration parameters are sent by the F1AP message received from the Donor-CU after the IAB-node reports the radio link failure information to the Donor-CU, wherein the method further includes:
  • the child node When the child node receives the RLF indication sent when the link between the IAB-node and the first parent node has a radio link failure, it stops sending the first path data; and,
  • the routing change of the first path data is triggered.
  • the path reconfiguration parameter is used for the IAB-node or the sub-node to change the route of the first path data that was not successfully sent or the first path data that was received.
  • the path reconfiguration parameter includes a destination BAP address and a path identifier of the first path.
  • the path reconfiguration parameter includes the mapping between the destination BAP address of the first path and the destination BAP address of the second path, or includes the destination BAP address and path identifier of the first path and the second path.
  • the mapping of the destination BAP address and path identifier includes the mapping between the destination BAP address of the first path and the destination BAP address of the second path, or includes the destination BAP address and path identifier of the first path and the second path.
  • the destination BAP address of the first path is unreachable; or,
  • the destination BAP address of the first path is unreachable.
  • the path reconfiguration parameter includes the destination BAP address of the second path, the path identifier of the second path, and the backhaul RLC channel identifier from the IAB-node to the next hop node of the second path.
  • the destination BAP address of the second path is the destination BAP address used for upstream F1-C and non-F1 data
  • the path identifier of the second path is the path identifier used for upstream F1-C and non-F1 data
  • the destination BAP address of the second path is the destination BAP address used for the upstream F1-U data
  • the path identifier of the second path is the path identifier used for the upstream F1-U data.
  • the identifier of the backhaul RLC channel to the next hop node of the second path is:
  • the Donor-CU sends an RRC reconfiguration message including the path reconfiguration parameter to the IAB-node or to the child node before the IAB-node is switched; or,
  • the Donor-CU sends an F1AP message including the path reconfiguration parameter to the IAB-node or to the child node after the IAB-node completes the handover to the new parent node.
  • the Donor-CU sends an RRC reconfiguration message or an F1AP message including the path reconfiguration parameters to the IAB-node or to the child node after the IAB-node completes the re-establishment to the new parent node.
  • the Donor-CU sends an RRC reconfiguration message or an F1AP message containing the path reconfiguration parameters to the IAB-node or to the child node after the IAB-node reports the radio link failure information to the Donor-CU .
  • the Donor-CU sends an RRC reconfiguration message including the path reconfiguration parameter to the sub-node before the radio link failure occurs in the IAB-node.

Landscapes

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

Abstract

本申请实施例提供一种发送和接收信号的方法、装置和通信系统，该发送和接收信号的装置应用于集成的接入和回传节点(IAB)节点，该装置包括：第一处理单元，其用于当所述IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的第一路径数据或接收的第一路径数据进行路由变更；以及第一收发单元，其基于变更的路由，发送所述未成功发送的所述第一路径数据或接收的所述第一路径数据。

Description

发送和接收信号的方法、装置和通信系统 技术领域
本申请实施例涉及通信技术领域。
背景技术
集成的接入和回传(Integrated access and backhaul，IAB)在下一代无线接入网络(NG-RAN：next generation radio access network)中实现了无线中继的功能。集成的接入和回传节点(IAB-node)支持通过新无线(New Radio，NR)的接入和回传。NR回传在网络侧中终止点被称为IAB-donor，它表示一个具有支持IAB功能的网络设备(例如，gNB)。
IAB-node可以通过一跳或者多跳来连接到一个IAB宿主(IAB-donor)。这些多跳连接形成了一个以IAB宿主为根节点的有向无环图(DAG，Directed Acyclic Graph)拓扑结构。IAB宿主负责执行IAB网络拓扑中集中式的资源管理、拓扑管理和路由管理。
IAB-node支持gNB-DU(distributed unit，分布式单元)的功能，IAB-node DU也被称为IAB-DU，IAB-DU是到终端设备(UE)和下一跳IAB-node的无线接入(NR access)接口的终点，也是到IAB-donor上的gNB-CU(central unit，中心单元)的F1协议的终点。IAB-DU可以服务普通的UE和IAB子节点。IAB-DU实现网络侧设备功能，连接到下游的child IAB-node，对UE以及下游child IAB-node提供NR空口接入并与IAB donor-CU之间建立有F1连接。
除了gNB-DU功能，IAB-node也支持一部分UE的功能，被称为IAB-MT(Mobile Termination)，IAB-MT包括比如物理层、层2、RRC和NAS功能来连接到另一个IAB-node或IAB-donor的gNB-DU、连接到IAB-donor上的gNB-CU和连接到核心网。IAB-MT可支持如UE物理层、接入(access stratum，AS)、无线资源控制(radio resource control，RRC)层和非接入(non-access stratum，NAS)层功能，可以连接到IAB父节点。
图1是IAB拓扑结构的一个示意图。如图1所示，在IAB拓扑结构10中，IAB-node 100包括IAB-MT功能单元101和IAB-DU功能单元102，IAB-DU功能单元102的 接口上的邻节点被称为子节点(child node)，如图1中所示的子节点201、202、203，IAB-DU功能单元102与子节点201、202、203之间可以通过空中接口(Uu)进行通信；IAB-MT功能单元101的接口上的邻节点被称为父节点(parent node)，如图1中所示的父节点301、302，IAB-MT功能单元101与父节点301、302之间可以通过空中接口(Uu)进行通信。
如图1所示，IAB-node 100到子节点201、202、203的方向被称为下游(downstream)方向，IAB-node 100到父节点301、302的方向被称为上游(upstream)方向。IAB-donor(未图示)为该IAB拓扑结构10执行集中式的资源、拓扑和路由管理。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
本申请的发明人发现：
IAB-node在移动过程中，如果断开了与原来的父IAB-node的连接，连接到新的父IAB-node，或者，IAB-node保持双连接时将F1-U传输路径从一个CG侧转换到另一个CG侧，会引起网络拓扑变化，进而影响IAB-node及其下游子节点的路由变化。每个上行数据包都携带由目的BAP地址标识，在路径转换后IAB-node及子节点发送的回传适配协议(Backhaul Adaptation Protocol，BAP)数据包头中携带的目的DU的BAP地址为切换后目标Donor-DU的地址，包头中携带的路径标识对应新的路径标识。但在IAB-node切换或转换F1-U传输路径时，IAB-node及其子节点中可能有一些未发送成功的数据，即携带原来Donor-DU的BAP地址和原来路径标识的数据包。如果IAB-node切换或转换F1-U路径后Donor-DU发生变化，则原来路径的上行数据不可到达原Donor-DU。而这些原来路径的上行数据通过新的路径传输，会被目标侧Donor-DU丢弃，因为携带的目的BAP地址与新的Donor-DU的BAP地址不一致。
例如，图2是上行数据丢弃的一个示意图，如图2所示，IAB-node 3断开与父节点IAB-node1的连接而连接至到IAB-node2时，IAB-node 3，4，5中有尚未发送成功的的原路径上行数据(BAP包头中目标BAP地址为1)。当IAB-node的Donor-DU发生改变(即，从Donor-DU 1变成Donor-DU 2)，IAB-node3沿新的路径发送这些未 成功发送的上行数据，该上行数据会被新的Donor-DU(BAP地址为2)丢弃，使其无法到达Donor-CU。
针对上述问题，本申请实施例提供一种发送和接收信号的方法、装置和通信系统，当IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的第一路径的数据或接收的第一路径的数据进行路由变更，由此，能够基于变更后的路由来发送数据，避免数据的丢失。
根据本申请实施例的一个方面，提供一种发送和接收信号的装置，应用于集成的接入和回传节点(IAB-node)，该装置包括：
第一处理单元，其用于当所述IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的第一路径数据或接收的第一路径数据进行路由变更；以及
第一收发单元，其基于变更的路由，发送所述未成功发送的所述第一路径数据或接收的所述第一路径数据。
根据本申请实施例的另一个方面，提供一种发送和接收信号的装置，应用于集成的接入和回传节点(IAB-node)的子节点，其中，所述装置包括：
第二处理单元，其当所述IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的所述第一路径数据或接收的所述第一路径数据进行路由变更；以及
第二收发单元，其基于变更的路由，发送所述未成功发送的所述第一路径数据或接收的所述第一路径数据。
根据本申请实施例的另一个方面，提供一种发送和接收信号的装置，应用于宿主中心单元(Donor-CU)，该装置包括：
第三收发单元，其当IAB-node的第一路径的目的BAP地址不可到达时，向IAB-node或所述IAB-node的子节点发送路径重配置参数，其中，所述路径重配置参数用于所述IAB-node或所述子节点对未成功发送的所述第一路径数据或接收的所述第一路径数据进行路由变更。
根据本申请实施例的另一个方面，提供一种发送和接收信号的方法，应用于集成的接入和回传节点(IAB-node)，该方法包括：
当所述IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的第一路径数据或接收的第一路径数据进行路由变更；以及
基于变更的路由，发送所述未成功发送的所述第一路径数据或接收的所述第一路 径数据。
根据本申请实施例的另一个方面，提供一种发送和接收信号的方法，应用于集成的接入和回传节点(IAB-node)的子节点，其中，所述方法包括：
当所述IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的所述第一路径数据或接收的所述第一路径数据进行路由变更；以及
基于变更的路由，发送所述未成功发送的所述第一路径数据或接收的所述第一路径数据。
根据本申请实施例的另一个方面，提供一种发送和接收信号的方法，应用于宿主中心单元(Donor-CU)，该方法包括：
当IAB-node的第一路径的目的BAP地址不可到达时，向IAB-node或所述IAB-node的子节点发送路径重配置参数，其中，所述路径重配置参数用于所述IAB-node或所述子节点对未成功发送的所述第一路径数据或接收的所述第一路径数据进行路由变更。
本申请实施例的有益效果之一在于：当IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的第一路径的数据或接收的第一路径的数据进行路由变更，由此，能够基于变更后的路由来发送数据，避免数据的丢失。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
图1是IAB拓扑结构的一个示意图；
图2是上行数据丢弃的一个示意图；
图3是IAB-node移动导致网络拓扑改变的一个示意图；
图4是本申请第一方面的实施例的发送和接收信号的方法的一个示意图；
图5是IAB-node及其子节点进行路由变更的一个示意图；
图6是IAB-node的下游子节点发送结束指示的一个示意图；
图7是IAB-node有双连接的情况下IAB-node及其子节点进行路由变更的一个示意图；
图8是本申请第二方面的实施例所述的信号的发送和接收信号的方法的一个示意图；
图9是本申请第三方面的实施例的信号的发送和接收信号的方法的一个示意图；
图10是本申请第四方面的实施例的发送和接收信号的装置的一示意图；
图11是本申请第五方面的实施例的发送和接收信号的装置的一示意图；
图12是本申请第六方面的实施例中发送和接收信号的装置的一个示意图；
图13是本申请实施例的网络设备的构成示意图；
图14是本申请实施例的终端设备的示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式 也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如新无线(NR，New Radio)、长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：集成的接入和回传节点(IAB-node)、基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femeto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment或Terminal Device)例如是指通过网络设备接入通信网络并接收网络服务的设备。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人 数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
此外，术语“网络侧”或“网络设备侧”是指网络的一侧，可以是某一基站，也可以包括如上的一个或多个网络设备。术语“用户侧”或“终端侧”或“终端设备侧”是指用户或终端的一侧，可以是某一UE，也可以包括如上的一个或多个终端设备。
在本申请实施例中，高层信令例如可以是无线资源控制(RRC)信令；例如称为RRC消息(RRC message)，例如包括MIB、系统信息(system information)、专用RRC消息；或者称为RRC IE(RRC information element)。高层信令例如还可以是F1-C信令，或者叫F1AP协议。但本申请不限于此。
IAB-node在移动过程中，如果断开了与原来的父IAB-node的连接，连接到新的父IAB-node，则会导致从IAB-node以及IAB-node的子节点到Donor-CU路由的改变，也就是网络拓扑改变。
图3是IAB-node移动导致网络拓扑改变的一个示意图。如图3所示，IAB-node5从IAB-node3下的小区切换到IAB-node 4下的小区之后，IAB-node5及其下游子节点IAB-node 6到Donor-CU的路由都发生改变。
针对IAB-node在同一个donor-CU下的DU中移动时网络拓扑的更新过程而言，IAB-node切换时，Donor-CU通过RRC重配置消息为IAB-node配置用于上行F1-C和非F1数据的目标路径的默认回传RLC信道(default BH RLC channel)、默认BAP路由标识(default BAP routing ID)，如果切换后改变了Donor-DU，Donor-CU可能为IAB-node配置可路由至目标Donor-DU的IP地址，其中，默认路由标识包含了目的Donor-DU的BAP地址和路径ID。当IAB-node切换到新的父节点之后，IAB-node开始应用上述配置，即将传输路径转迁移至目标侧。
第一方面的实施例
本申请第一方面的实施例提供一种发送和接收信号的方法。该方法应用于集成的接入和回传节点(IAB-node)。
图4是第一方面的实施例的发送和接收信号的方法的一个示意图，如图4所示，该方法包括：
操作401、当IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的第一路径数据或接收的第一路径数据进行路由变更；以及
操作402、基于变更的路由，发送未成功发送的第一路径数据或接收的第一路径数据。
根据本申请，对第一路径的数据进行路由变更，由此，能够基于变更后的路由来发送数据，避免数据的丢失。
在本申请的操作401中，对第一路径的数据进行路由变更，包括：将第一路径数据的目的BAP地址变更为第二路径的目的BAP地址；或者，将第一路径数据的目的BAP地址变更为第二路径的目的BAP地址，并且将第一路径数据的路径标识变更为第二路径的路径标识。未成功发送的第一路径数据，即已经产生或已经接收到的第一路径数据，但是在缓存中未发送或已经发送但还未收到RLC层的正确应答。若第一路径路由的目的BAP地址无法到达，IAB-node可以变更第一路径数据的路由，使其基于变更后的第二路径的路由进行发送，可以使其到达Donor-CU。
在本申请中，第一路径可以是IAB-node在移动之前的上行数据发送路径，路由变更后形成的路径是第二路径。
在本申请的操作402中，发送第一路径数据可以包括：将第一路径数据发送到IAB-node与第二路径的下一跳节点之间的回传RLC信道。
IAB-node变更第一路径数据的路由时，将第一路径数据发送到第二路径下的下一跳节点。如果Donor-CU已经为IAB-node配置有从上一跳节点与IAB-node之间的回传RLC信道或接入RLC信道到IAB-node与第二路径的下一跳节点的回传RLC信道的映射关系，即已存在合适的下一跳RLC信道，IAB-node可以据此映射关系选择发送第一路径数据的回传RLC信道。比如在IAB-node已与第二路径的下一跳节点保持有连接的情况下。但是如果不存在上述映射关系，IAB-node可以选择任意一个到第二路径的下一跳节点的回传RLC信道发送第一路径数据，如果IAB-node与第二路径的下一跳节点没有连接，则IAB-node需要在与其建立连接后才能发送第一路径数 据。
图5是IAB-node及其子节点进行路由变更的一个示意图。
如图5所示，例如，IAB-node3离开父节点IAB-node1并连接到IAB-node2时，由于IAB-node 1的Donor-DU发生改变，IAB-node3,4,5将尚未到达IAB-node1的原路径上行数据(BAP包头中目的BAP地址为1,路径标识为1)进行重新路由，即，将BAP包头中目的BAP地址改为新的Donor-DU的地址(BAP地址为2)，发送到与IAB-node 2之间的回传RLC信道。这样当IAB-node3将原路径(即，第一路径)上行数据沿目标路径(即，第二路径)传输时，不会被目标侧Donor-DU(BAP地址为2)丢弃。
在至少一个实施例中，如图4所示，该方法还可以包括：
操作403、停止对第一路径数据的路由变更。
当IAB-node认为已发送完第一路径数据时，停止对第一路径数据的路由变更。在操作403中，可以在如下的任一条件下停止对第一路径数据的路由变更：
条件1、IAB-node触发对第一路径的数据进行路由变更后启动定时器，定时器超时后停止对第一路径数据的路由变更；定时器超时时，认为IAB-node和子节点中已不存在第一路径数据，可以停止路由变更。
条件2、IAB-node把该IAB-node未成功发送的第一路径数据发送完时，停止对第一路径数据的路由变更；如果IAB-node和子节点同时进行路由变更，则IAB-node和子节点将自身缓存的未成功发送的第一路径数据发送完时，认为已不存在第一路径数据，可以停止路由变更。
条件3、IAB-node发送完未成功发送的第一路径数据以及确定下游子节点发送完未成功发送的第一路径数据时，停止对第一路径数据的路由变更，此条件可以应用于IAB-node和子节点不同时进行路由变更或子节点不进行路由变更的情况，IAB-node除了发送完自身缓存的第一路径数据，还要保证下游子节点已发送完未成功发送的第一路径数据时，才认为已不存在第一路径数据。
在条件3中，IAB-node接收到IAB-node的下游子节点发送的结束指示时，确定下游子节点发送完未成功发送的第一路径数据。结束指示可以放在BAP的数据PDU的包头中，或放在BAP的控制PDU中。
图6是IAB-node的下游子节点发送结束指示的一个示意图。如图6所示， IAB-node的各下游子节点在发送完自身缓存的未成功发送的第一路径数据后，发送结束指示给该下游子节点的父节点。值得说明的是，子节点收到下游子节点的结束指示时不是直接转发，而是发送完自身缓存的第一路径数据时再向父节点发送自己的结束指示，或者在停止对第一路径数据的路由变更后向父节点发送结束指示。
在至少一个实施例中，IAB-node的第一路径的目的BAP地址不可到达的情况包括如下的情况1或情况2：
情况1、IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达；
情况2、IAB-node与第一父节点之间的链路发生无线链路失败之后导致第一路径的目的BAP地址不可到达。
至少一个实施例中，如图4所示，该方法还包括：
操作404、IAB-node接收宿主中心单元(Donor-CU)发送的路径重配置参数。
当IAB-node离开原父节点时往往还未配置有路由变更相关的参数，例如，还未建立第二路径路由或者甚至还未与第二路径的下一跳节点建立连接，则通过操作404可以获得相关配置，使得IAB-node能够在操作401中进行路由的变更。
在操作404的实施方式一中，路径重配置参数可以包括：第一路径的目的BAP地址及路径标识。这样，如果部分原路径数据不需要路由变更，或者IAB-node不知道哪些原路径需要路由变更的情况下Donor-CU可以配置IAB-node需要进行路由变更的路径。
在操作404的实施方式二中，路径重配置参数可以包括：第一路径的目的BAP地址与第二路径的目的BAP地址的映射，或者，包括第一路径的目的BAP地址及路径标识与第二路径的目的BAP地址及路径标识的映射，由此，能够使不同的第一路径使用不同的第二路径路由，路由到不同的Donor-DU，可以满足上行数据的不同QoS要求。
在操作404的实施方式三中，路径重配置参数可以包括：第二路径的目的BAP地址、第二路径的路径标识和IAB-node到第二路径的下一跳节点的回传RLC信道标识。其中，第二路径的目的BAP地址、第二路径的路径标识是用来替换第一路径数据BAP包头中的目的BAP地址和路径标识，IAB-node到第二路径的下一跳节点的回传RLC信道是用来向第二路径的下一跳节点发送第一路径数据的上行回传RLC信道。
在操作404的实施方式三中：第二路径的目的BAP地址为用于上行F1-C和非F1数据的目的BAP地址，第二路径的路径标识为用于上行F1-C和非F1数据的路径标识；或者，第二路径的目的BAP地址为用于上行F1-U数据的目的BAP地址，第二路径的路径标识为用于上行F1-U数据的路径标识。这样，如果IAB-node已配置有用于上行F1-C和非F1数据的第二路径路由，IAB-node可以使用该F1-C和非F1数据的第二路径路由作为第一路径数据的路由；当IAB-node还配置有用于上行F1-U数据的第二路径路由，IAB-node可以使用该F1-U数据的第二路径路由作为第一路径数据的路由。
在操作404的实施方式三中，IAB-node到第二路径的下一跳节点的回传RLC信道标识为：用于上行F1-C和非F1数据的回传RLC信道标识；或者，用于上行F1-U数据的回传RLC信道标识。这样，如果IAB-node配置有用于上行F1-C和非F1数据的回传RLC信道，IAB-node可以使用该F1-C和非F1数据的回传RLC信道作为发送第一路径数据的信道，如果IAB-node还配置有用于上行F1-U数据的回传RLC信道，IAB-node可以使用该F1-U数据的信道作为发送第一路径数据的信道。
在操作404的实施方式一至三的第一个例子中，当IAB-node的第一路径的目的BAP地址不可到达的情况为上述的情况1时，即IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达，路径重配置参数可以由Donor-CU发送的用于切换的RRC重配置消息发送，并且，IAB-node在完成到新的父节点的随机接入时触发对第一路径数据的路由变更。
在操作404的实施方式一至三的第二个例子中，当IAB-node的第一路径的目的BAP地址不可到达的情况为上述的情况1时，路径重配置参数可以由IAB-node完成到新的父节点的切换后从Donor-CU收到的F1AP消息发送，并且，当IAB-node切换到新的父节点时停止发送第一路径数据，比如，IAB-node可以停止向父节点发送调度请求(SR，Schedule Request)或缓存大小请求(BSR，Buffer Size Request)或者停止调度子节点的上行资源授权。IAB-node在收到F1AP消息时可以触发对第一路径数据的路由变更。因为IAB-node切换后第一路径数据无法到达目的Donor-DU，所以切换后立即停止发送第一路径数据可避免数据丢失。
在操作404的实施方式一至三的第三个例子中，当IAB-node的第一路径的目的BAP地址不可到达的情况为上述的情况2时，即IAB-node与第一父节点之间的链路 发生无线链路失败之后导致第一路径的目的BAP地址不可到达，路径重配置参数可以通过IAB-node完成到新的父节点的重建立后从Donor-CU接收到的RRC重配置消息或F1AP消息发送，并且，当IAB-node与第一父节点之间的链路发生无线链路失败时停止发送第一路径数据，比如，IAB-node可以停止向父节点发送SR和BSR或者停止调度子节点的上行资源授权。IAB-node在接收到路径重配置参数后触发对第一路径数据的路由变更。因为IAB-node与父节点的链路失败后第一路径数据无法到达目的Donor-DU，所以立即停止发送第一路径数据可避免数据丢失。
在操作404的实施方式一至三的第四个例子中，当IAB-node的第一路径的目的BAP地址不可到达的情况为上述的情况2时，路径重配置参数可以由IAB-node向Donor-CU报告无线链路失败信息后从Donor-CU收到的F1AP消息发送，并且，当IAB-node与第一父节点之间的链路发生无线链路失败时停止发送第一路径数据，比如，IAB-node可以停止向父节点发送SR和BSR或者停止调度子节点的上行资源授权。IAB-node在接收到F1AP消息时触发对第一路径数据的路由变更。
在本申请中，如果IAB-node中已存在第二路径路由，在不执行操作404的情况下，也能对第一路径数据进行路由变更。例如，IAB-node与第一父节点和第二父节点形成双连接，其中，IAB-node与第一父节点之间的链路发生无线链路失败，IAB-node与第二父节点之间的链路未发生无线链路失败。在该情况下，在IAB-node与第一父节点之间的链路发生RLF之后即触发对第一路径数据的路由变更，将经过第一父节点的路径的BAP数据包头中目的BAP地址替换为经过IAB-node与第二父节点之间链路的路径的目的BAP地址，或者目的BAP地址和路径标识分别替换为经过IAB-node与第二父节点之间链路的路径的目的BAP地址和路径标识。那么，第一路径就是经过IAB-node与第一父节点之间链路的路径，第二路径就是经过IAB-node与第二父节点之间链路的路径。
图7是IAB-node双连接的情况下IAB-node及其子节点进行路由变更的一个示意图。如图7所示，IAB-node1和IAB-node2分别是IAB-node 3的第一父节点和第二父节点。IAB-node 3与第一父节点IAB-node1之间的链路发生RLF，IAB-node 3与第二父节点IAB-node2之间的链路没有发生RLF，IAB-node3及其子节点将第一路径数据路由到第二路径，第二路径经过未发生RLF的链路。
下面，结合具体的实施例，对图4的发送和接收信号的方法进行说明。
实施例1、
在实施例1中，IAB-node的第一路径的目的BAP地址不可到达的情况为上述情况1(即，IAB-node切换到新的父节点之后导致第一路径的目的BAP地址不可到达)。
在本实施例中，当IAB-node切换后，原Donor-DU与目标Donor-DU不同。IAB-node或其子节点对缓存的以及从下游节点接收到的原路径(即，第一路径)上行F1数据进行路由变更，将BAP包头中的原Donor-DU的BAP地址替换为目标Donor-DU的BAP地址(即，第二路径的目的BAP地址)，或者将原Donor-DU的BAP地址和原路径标识分别替换为目标Donor-DU地址和目标侧路径(即，第二路径)标识。进而，IAB-node可以将原路径上行F1数据发送到IAB-node与目标侧路径的下一跳节点之间的回传RLC信道，从而基于变更的路由来发送第一路径数据。
IAB-node对缓存的以及从下游节点接收到的原路径上行F1数据进行路由变更的过程说明如下。
IAB-node在切换到新的父节点时，用于上行F1-C和非F1数据的目标传输路径参数由donor-CU通过原路径发送的RRC消息配置，包括目的Donor-DU地址、路径标识和上行UL BH RLC信道。donor-CU可以通过同一条RRC消息配置用于上行F1-U数据的目标侧路由，包括目的Donor-DU地址和路径标识以及UL BH RLC channel。
IAB-node可以利用上行F1-C和非F1数据的目的Donor-DU地址、目标侧路径标识和上行UL BH RLC信道传输缓存的原路径上行F1-U数据，也可以通过用于上行F1-U数据的目标路径参数发送原路径的上行数据。或者，Donor-CU可以专门为原路径上行数据的路由变更配置参数。为了识别原路径上行数据，切换后IAB-node可以将原目的地址和路径标识保留一段时间，或者Donor-CU可以将需要重新路由的上行数据的路由标识(原Donor-DU地址和原路径标识)配置给IAB-node。
为了满足上行数据的不同QoS要求，不同原Donor-DU或原路径的上行数据可能需要路由到不同的目标Donor-DU或使用不同的目标路径进行传输。Donor-CU可以配置原Donor-DU地址与目标Donor-DU地址的映射，或者，配置原Donor-DU的BAP地址和原路径标识与目标Donor-DU地址和目标路径标识的映射。
原路径数据路由变更的相关配置可以通过切换时的RRC重配置消息或切换完成后的F1AP消息发送到IAB-node。
在本实施例中，IAB-node进行原路径数据路由变更的激活方式(即，触发操作 401中的路由变更的方法)可以包括：
在IAB-node已保存有路径更新配置的情况下，IAB-node完成到目标小区的随机接入；或者，IAB-node完成切换后收到通过F1AP消息发送的原路径数据路由变更相关的配置。
在本实施例中，原路径数据路由变更的去激活(即，执行操作403)方式可以包括：
原路径数据的路由变更激活后启动定时器，定时器超时后去激活原路径数据的路由变更；或者，IAB-node把当前缓存的未成功发送的原路径数据发送完，就去激活原路径数据的路由变更；或者，IAB-node确定已经把下游节点中全部的原路径数据发送完并且把当前未成功发送的原路径数据发送完时，去激活原路径数据的路由变更例如，子节点去激活路由变更时向父节点发送一个结束指示，当IAB-node收到这个结束指示，说明所有下游子节点把原路径数据发送完成了路由变更。
此外，在本实施例中，切换后产生的上行数据是按照目标侧路径产生的，因此，切换后产生的上行数据无需更新路由。
此外，在实施例1中，在子节点激活路由变更原路径数据路由变更的方式包括：子节点已保存有路径更新配置的情况下，收到IAB-node完成到目标小区的随机接入后发送的切换成功指示消息时，激活原路径数据路由变更；或者，IAB-node完成切换后收到Donor-CU通过F1AP消息发送的原路径数据路由变更相关的配置时，激活原路径数据路由变更。
在实施例1中，子节点的原路径数据路由变更的去激活方式包括：子节点激活路由变更后启动定时器，定时器超时后去激活原路径数据的路由变更；或者，子节点把当前缓存的未成功发送的原路径数据发送完就去激活；或者，子节点确定已经把下游节点中全部的原路径数据发送完并发送完未成功发送的原路径数据时去激活。
实施例2、
在实施例2中，IAB-node的第一路径的目的BAP地址不可到达的情况为上述情况2(即，IAB-node与第一父节点之间的链路发生无线链路失败之后导致第一路径的目的BAP地址不可到达)。
本实施例2中，当IAB-node完成重建立后，原Donor-DU与新Donor-DU不同。
IAB重建到新小区后，可能有一些原路径的上行数据未发送到原父节点，这些数 据如果直接通过新路径发送可能被新Donor-DU丢弃。
IAB-node或其子节点对缓存的以及从下游节点接收到的原路径上行F1数据进行路由变更，将BAP包头中的原Donor-DU的BAP地址替换为新的Donor-DU的BAP地址，或者将原Donor-DU的BAP地址和原路径标识分别替换为新的Donor-DU地址和新的路径标识。
当IAB-node完成到新小区的重建立时，对缓存的以及从下游节点接收到的原路径上行F1数据进行路由变更。
重建立时，用于上行F1-C和非F1数据的新的传输路径的参数，包括目的Donor-DU地址、目标侧路径标识和上行UL BH RLC信道由donor-CU配置。donor-CU可以通过同一条RRC消息配置用于上行F1-U数据的新的传输路径参数。IAB-node可以用上行F1-C和非F1数据的传输路径参数，包括Donor-DU地址、路径标识和上行UL BH RLC信道发送缓存的原路径上行F1-U数据，也可以用于F1-U的传输路径参数发送原路径上行数据。或者，Donor-CU可以专门为原路径上行数据的路由变更配置参数。为了识别原路径上行数据，重建立成功后IAB-node可以将原目的地址和路径标识保留一段时间，或者Donor-CU可以将需要重新路由的原Donor-DU地址和原路径标识配置给IAB-node。
为了满足上行数据的不同QoS要求，不同上行数据可能需要重新路由到不同的目标Donor-DU或使用不同的目标路径进行传输。Donor-CU可以配置原Donor-DU BAP地址与目标Donor-DU BAP地址的映射，或者，配置原Donor-DU的BAP地址和原路径标识与目标Donor-DU地址和目标路径标识的映射。
原路径上行数据路由变更的相关配置可以通过重建立后的RRC重配置消息或重建立后的F1AP消息发送到IAB-node。
IAB-node完成向新小区的接入后，可以停止通过新的传输路径发送原路径的上行数据，以防止被新的Donor-DU丢弃。
在本实施例中，IAB-node进行数据路由变更的激活方式(即，触发操作401中的路由变更的方法)可以包括：IAB-node完成重建立后收到通过RRC消息或F1AP消息发送的原路径数据路由变更相关的配置。
在本实施例中，原路径数据路由变更的去激活(即，执行操作403)方式可以参考实施例1，此处不再赘述。
此外，在实施例2中，在子节点对原路径的上行数据进行路由变更的过程中，原路径数据路由变更的激活方式包括：子节点已保存有路径更新配置的情况下，比如在IAB-node切换中IAB-node重建立到目标小区的情况下，子节点收到IAB-node完成到新小区的随机接入后发送的重建立成功指示消息时激活路由变更；或者，子节点收到Donor-CU发送的原路径数据路由变更相关的配置时激活路由变更。
在实施例2中，子节点的原路径数据路由变更的去激活方式可以参考实施例1，此处不再赘述。
实施例3、
本实施例3中，IAB-node建立有双连接时，将F1传输路径从一个小区组(CG，Cell Group)转换到另一个CG，比如IAB-node与一个CG的父节点之间的BH链路发生RLF。IAB-node的一条路径发生RLF后，可能有一些经过RLF路径发送的上行数据尚未到达父节点，这些数据如果直接通过另一条未发生RLF的路径发送会被另一条路径的Donor-DU丢弃。
IAB-node对缓存的以及从下游节点接收到的经过RLF链路的路径的上行F1数据进行路由变更，将BAP包头中经过RLF链路的路径对应的Donor-DU的BAP地址替换为不经过发生RLF链路的路径对应的Donor-DU的BAP地址，或者还将经过发生RLF链路的路径标识替换为不经过发生RLF链路的路径标识。
当一条连接发生RLF时，IAB-node可通过RRC消息发送RLF报告给Donor-CU，例如当主小区组(MCG，Master Cell Group)发生RLF时发送主小区组错误信息(MCGfailureInformation)，辅小区组(SCG，Secondary Cell Group)发生RLF时发送辅小区组错误信息(SCGFailureInformation)。
Donor-CU收到RLF报告后，Donor-CU可以配置用于上行数据的参数，即目的Donor-DU地址和路径标识以及UL BH RLC channel，IAB-node可以根据Donor-CU配置的路由变更参数对经过发生RLF链路的路径的上行数据重新路由。Donor-CU还可以将具体需要重新路由的上行数据的路由标识配置给IAB-node。
为了满足上行数据的不同QoS要求，不同上行数据可能需要重新路由到不同的目标Donor-DU或使用不同的目标路径进行传输。Donor-CU可以配置不同的经过发生RLF链路路径的使用不同的路由。
在本实施例中，IAB-node进行数据路由变更的激活方式(即，触发操作401中 的路由变更的方法)可以包括：IAB-node检测到一条链路发生RLF；或者，IAB-node收到Donor-CU发送的上行数据数据路由变更相关的配置。
在本实施例中，原路径数据路由变更的去激活(即，执行操作403)方式可以参考实施例1，此处不再赘述。
此外，F1传输路径从一个CG转换到另一个CG之后产生的上行数据无需更新路由，因为是按照新的路径产生的。
此外，在实施例3中，当IAB-node检测到RLF时，向子节点发送RLF指示，RLF指示包含经过发生RLF链路的路径的路由标识(包括路径标识和目的BAP地址)。子节点对未成功发送的以及从下游节点接收到的经过RLF链路的路径的上行F1数据进行路由变更。
Donor-CU可以配置用于重新路由RLF路径相关参数，即目的BAP地址和路径标识以及UL BH RLC channel，子节点根据参数对发生RLF路径的上行数据重新路由。Donor-CU还可以将需要重新路由的上行F1数据的路由标识(包括目的BAP地址和路径标识)配置给子节点。
此外，在实施例3中，在子节点进行数据路由变更的激活方式包括：子节点收到IAB-node发送的RLF指示时，激活路径数据路由变更；或者，子节点收到Donor-CU发送的上行数据重新路由相关的配置时，激活数据路由变更。
在实施例3中，子节点的的去激活方式可参考实施例1，此处不再赘述。
根据本申请第一方面的实施例，对第一路径的数据进行路由变更，由此，能够基于变更后的路由来发送数据，避免数据的丢失。
第二方面的实施例
至少针对与第一方面的实施例相同的问题，本申请第二方面的实施例提供一种发送和接收信号的方法，与第一方面的实施例的方法对应。本申请第二方面的实施例的发送和接收信号的方法应用于集成的接入和回传节点(IAB-node)的子节点。
图8是第二方面的实施例所述的信号的发送和接收信号的方法的一个示意图，如图8所示，该方法包括：
操作801、当IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的第一路径数据或接收的第一路径数据进行路由变更；以及
操作802、基于变更的路由，发送未成功发送的第一路径数据或接收的第一路径数据。
根据本申请第一方面的实施例，对第一路径的数据进行路由变更，由此，能够基于变更后的路由来发送数据，避免数据的丢失。
在操作801中，对第一路径数据进行路由变更，包括：
将第一路径数据的目的BAP地址变更为第二路径的目的BAP地址；或者，将第一路径数据的目的BAP地址变更为第二路径的目的BAP地址，并且将第一路径数据的路径标识变更为第二路径的路径标识。
在操作802中，发送第一路径数据，包括：将第一路径数据发送到子节点与第二路径的下一跳节点之间的回传RLC信道。
子节点变更第一路径数据的路由时，将第一路径数据发送到第二路径下的下一跳节点。如果Donor-CU已经为子节点配置有从上一跳节点与子节点之间的回传RLC信道或接入RLC信道到子节点与第二路径的下一跳节点的回传RLC信道的映射关系，即已存在合适的下一跳RLC信道，子节点可以据此映射关系选择发送第一路径数据的回传RLC信道。比如，子节点与第二路径的下一跳节点保持有连接的情况下。但是如果不存在上述映射关系，子节点可以选择任意一个到第二路径的下一跳节点的回传RLC信道发送第一路径数据，如果子节点与第二路径的下一跳节点没有连接，则IAB-node需要在与其建立连接后才能发送第一路径数据。
在本实施例中，IAB-node的第一路径的目的BAP地址不可到达的情况包括下述的情况1或情况2：
情况1、IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达；
情况2、IAB-node与第一父节点之间的链路发生无线链路失败之后导致第一路径的目的BAP地址不可到达。
如图8所示，该方法还包括：
操作803、停止对第一路径数据的路由变更。
子节点认为已发送完第一路径数据时，停止第一路径数据的路由变更。在至少一个实施例中，在满足下述任一条件的情况下可以执行操作803：
条件1、子节点触发对第一路径数据进行路由变更后启动定时器，定时器超时后 停止对第一路径数据的路由变更；定时器超时时，认为子节点和其下游子节点中已不存在第一路径数据，可以停止路由变更。
条件2、子节点把未成功发送的第一路径数据发送完之后，停止对第一路径数据的路由变更；如果子节点和其下游子节点同时进行路由变更，则子节点和其下游子节点将自身缓存的未成功发送的第一路径数据发送完时，认为子节点和其下游子节点中已不存在第一路径数据，可以停止路由变更。
条件3、子节点发送完未成功发送的第一路径数据以及确定下游子节点发送完未成功发送的第一路径数据的情况下，停止对第一路径数据的路由变更，此条件可以应用于子节点和其下游子节点不同时进行路由变更或其下游子节点不进行路由变更的情况，子节点除了发送完自身缓存的第一路径数据，还要保证其下游子节点已发送完未成功发送的第一路径数据时，才认为已无需对第一路径数据重新路由。例如，子节点可以在收到该子节点的下游子节点发送的结束指示时，确定该下游子节点发送完该未成功发送的第一路径数据。
如图8所示，该方法还包括：
操作804、子节点接收Donor-CU发送的路径重配置参数。
当IAB-node离开原父节点时子节点往往还未配置有路由变更相关的参数，例如，还子节点中还未建立第二路径路由，则通过操作804可以获得相关配置
在操作804的实施方式一中，该路径重配置参数包括第一路径的目的BAP地址及路径标识。这样，如果部分原路径数据不需要路由变更，或者子节点不知道哪些原路径需要路由变更的情况下Donor-CU可以配置子节点需要进行路由变更的路径。
在操作804的实施方式二中，该路径重配置参数包括：第一路径的目的BAP地址与第二路径的目的BAP地址的映射，或者，包括第一路径的目的BAP地址及路径标识与第二路径的目的BAP地址及路径标识的映射。由此，能够使不同的第一路径使用不同的第二路径路由，路由到不同的Donor-DU，可以满足上行数据的不同QoS要求。
在操作804的实施方式三中，该路径重配置参数包括第二路径的目的BAP地址、第二路径的路径标识和子节点到第二路径的下一跳节点的回传RLC信道标识。其中，第二路径的目的BAP地址、第二路径的路径标识是用来替换第一路径数据BAP包头中的目的BAP地址和路径标识，子节点到第二路径的下一跳节点的回传RLC信道是 用来向第二路径的下一跳节点发送第一路径数据的上行回传RLC信道。
在操作804的实施方式三中：第二路径的目的BAP地址为用于上行F1-C和非F1数据的目的BAP地址，第二路径的路径标识为用于上行F1-C和非F1数据的路径标识；或者，第二路径的目的BAP地址为用于上行F1-U数据的目的BAP地址，第二路径的路径标识为用于上行F1-U数据的路径标识。这样，如果子节点中已配置有用于上行F1-C和非F1数据的第二路径路由，可以使用该F1-C和非F1数据的第二路径路由作为第一路径数据的路由；当子节点还配置有用于上行F1-U数据的第二路径路由，则可以使用该F1-U数据的第二路径路由作为第一路径数据的路由。
在操作804的实施方式三中，到第二路径的下一跳节点的回传RLC信道标识为：用于上行F1-C和非F1数据的回传RLC信道标识；或者，用于上行F1-U数据的回传RLC信道标识。这样，如果子节点中配置有用于上行F1-C和非F1数据的回传RLC信道，可以使用该F1-C和非F1数据的回传RLC信道作为发送第一路径数据的信道，如果子节点还配置有用于上行F1-U数据的回传RLC信道，则可以使用该F1-U数据的信道作为发送第一路径数据的信道。
在操作804的实施方式一至三的第一个例子中，当IAB-node的第一路径的目的BAP地址不可到达的情况为上述的情况1时，即IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达，路径重配置参数由IAB-node切换之前的RRC重配置消息发送，并且，子节点收到IAB-node完成到新的父节点的随机接入后发送的切换成功指示时触发对第一路径数据的路由变更。
在操作804的实施方式一至三的第二个例子中，当IAB-node的第一路径的目的BAP地址不可到达的情况为上述的情况1时，路径重配置参数由IAB-node完成切换后从Donor-CU收到的F1AP消息发送，并且，当子节点收到IAB-node完成到新的父节点的随机接入后发送的切换成功指示时，停止所述第一路径数据，比如，子节点可以停止发送SR和BSR或者停止调度下游节点的上行资源授权。子节点在收到F1AP消息时触发对第一路径数据的路由变更。因为IAB-node切换后第一路径数据无法到达目的Donor-DU，所以当IAB-Node切换后立即停止发送第一路径数据可避免数据丢失。
在操作804的实施方式一至三的第三个例子中，当IAB-node的第一路径的目的BAP地址不可到达的情况为上述的情况2时,即IAB-node与第一父节点之间的链路发 生无线链路失败之后导致第一路径的目的BAP地址不可到达，路径重配置参数由IAB-node发生无线链路失败之前的Donor-CU发送的RRC重配置消息发送，并且，该子节点收到IAB-node完成到新的父节点的随机接入后发送的重建立成功指示时触发对第一路径数据的路由变更。因为IAB-node完成随机接入时子节点已保存有路由变更相关的参数，所以子节点可以立即触发对第一路径数据的路由变更。
在操作804的实施方式一至三的第四个例子中，当IAB-node的第一路径的目的BAP地址不可到达的情况为上述的情况2时，路径重配置参数由IAB-node完成到新的父节点的重建立后从Donor-CU接收到的RRC重配置消息或F1AP消息发送，并且，子节点收到IAB-node完成到新的父节点的随机接入后发送的重建立成功指示时停止发送第一路径数据，比如，子节点可以停止向父节点发送SR和BSR或者停止调度下游节点的上行资源授权。子节点接收到路径重配置参数后触发对第一路径数据的路由变更。因为IAB-node重建立到新的父节点之后，第一路径数据无法到达目的Donor-DU，所以当IAB-Node重建立后子节点立即停止发送第一路径数据可避免数据丢失。
在操作804的实施方式一至三的第五个例子中，当IAB-node的第一路径的目的BAP地址不可到达的情况为上述的情况2时，路径重配置参数由IAB-node向Donor-CU报告无线链路失败信息后从Donor-CU收到的F1AP消息发送，并且，当子节点收到IAB-node与第一父节点之间的链路发生无线链路失败时发送的RLF指示时，停止发送第一路径数据，子节点收到F1AP消息时触发对第一路径数据的路由变更。
此外，在至少一个实施例中，如果子节点中已存在第二路径路由，在执行操作804的情况下，也能对第一路径数据进行路由变更。例如，IAB-node与第一父节点和第二父节点形成双连接，其中，IAB-node与第一父节点之间的链路发生无线链路失败，IAB-node与第二父节点之间的链路未发生无线链路失败。在该情况下，子节点收到IAB-node与第一父节点之间的链路发生无线链路失败(RLF)时发送的RLF指示时，即触发对第一路径数据的路由变更，将经过IAB-node与第一父节点链路的路径的BAP数据包头中的目的BAP地址替换为经过IAB-node与第二父节点之间链路的路径对应的目的BAP地址，或者将目的BAP地址和路径标识分别替换为经过IAB-node与第二父节点之间链路的路径的目的BAP地址和路径标识。那么，第一路径就是经过IAB-node与第一父节点之间链路的路径，第二路径就是经过IAB-node与第二父节点之间链路的路径。此外，RLF指示可以包含第一路径的目的BAP地址和 路径标识，由此，这样在IAB-node发生RLF时，子节点能够知道有哪些路径受到了RLF影响并需要进行路由变更。
在第二方面的实施例中，关于子节点的行为的举例，可以参考第一方面的实施例中关于实施例1～实施例3的说明。
根据本申请第二方面的实施例，对第一路径的数据进行路由变更，由此，子节点能够基于变更后的路由来发送数据，避免数据的丢失。
第三方面的实施例
至少针对与第一方面的实施例相同的问题，本申请第三方面的实施例提供一种发送和接收信号的方法，与第一方面的实施例的方法对应。本申请第三方面的实施例的发送和接收信号的方法应用于集成的接入和回传节点(IAB-node)的宿主中心单元(Donor-CU)。
图9是第三方面的实施例的信号的发送和接收信号的方法的一个示意图，如图9所示，该方法包括：
操作901、当IAB-node的第一路径的目的BAP地址不可到达时，向IAB-node或IAB-node的子节点发送路径重配置参数。
在操作901中，路径重配置参数用于IAB-node或IAB-node的子节点对未成功发送的第一路径数据或接收的第一路径数据进行路由变更。
根据本申请第三方面的实施例，IAB-node或其子节点能够利用路径重配置参数对第一路径的数据进行路由变更，由此，IAB-node或子节点能够基于变更后的路由来发送数据，避免数据的丢失。
在至少一个实施例中，IAB-node的第一路径的目的BAP地址不可到达的情况包括：
情况1、IAB-node切换到新的父节点之后导致第一路径的目的BAP地址不可到达；或者，
情况2、IAB-node与第一父节点之间的链路发生无线链路失败之后导致第一路径的目的BAP地址不可到达。
在操作901的实施方式一中，路径重配置参数可以包括第一路径的目的BAP地址及路径标识。
在操作901的实施方式二中，路径重配置参数包括第一路径的目的BAP地址与第二路径的目的BAP地址的映射，或者，包括第一路径的目的BAP地址及路径标识与第二路径的目的BAP地址及路径标识的映射。
在操作901的实施方式三中，路径重配置参数包括：第二路径的目的BAP地址、第二路径的路径标识和IAB-node到第二路径的下一跳节点的回传RLC信道标识。其中，第二路径的目的BAP地址为用于上行F1-C和非F1数据的目的BAP地址，第二路径的路径标识为用于上行F1-C和非F1数据的路径标识；或者，第二路径的目的BAP地址为用于上行F1-U数据的目的BAP地址，第二路径的路径标识为用于上行F1-U数据的路径标识。
在操作901的实施方式三中，到第二路径的下一跳节点的回传RLC信道标识为：用于上行F1-C和非F1数据的回传RLC信道标识；或者，用于上行F1-U数据的回传RLC信道标识。
在操作901的实施方式一至三的第一个例子中，当IAB-node的第一路径的目的BAP地址不可到达的情况为上述的情况1时(即，IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达)：Donor-CU在IAB-node切换之前向IAB-node或向子节点发送包含路径重配置参数的RRC重配置消息；或者，Donor-CU在IAB-node完成到新的父节点的切换后向IAB-node或向子节点发送包含路径重配置参数的F1AP消息。
在操作901的实施方式一至三的第二个例子中，当IAB-node的第一路径的目的BAP地址不可到达的情况为上述的情况1时，Donor-CU在IAB-node向Donor-CU报告无线链路失败信息后向IAB-node或向子节点发送包含路径重配置参数的RRC重配置消息或F1AP消息。
在操作901的实施方式一至三的第三个例子中，当IAB-node的第一路径的目的BAP地址不可到达的情况为上述的情况2时(即，在IAB-node与第一父节点之间的链路发生无线链路失败之后导致第一路径的目的BAP地址不可到达的情况下)，Donor-CU在IAB-node完成到新的父节点的重建立后向IAB-node或向子节点发送包含路径重配置参数的RRC重配置消息或F1AP消息。
在操作901的实施方式一至三的第四个例子中，当IAB-node的第一路径的目的BAP地址不可到达的情况为上述的情况2时，Donor-CU在IAB-node发生无线链路 失败之前向子节点发送包含路径重配置参数的RRC重配置消息。
在第三方面的实施例中，关于子节点的行为的举例，可以参考第一方面的实施例中关于实施例1～实施例3的说明。
根据本申请第三方面的实施例，IAB-node或其子节点能够利用路径重配置参数对第一路径的数据进行路由变更，由此，IAB-node或子节点能够基于变更后的路由来发送数据，避免数据的丢失。
第四方面的实施例
本申请实施例提供一种发送和接收信号的装置。该装置例如可以是集成的接入和回传节点，也可以是配置于集成的接入和回传节点的某个或某些部件或者组件，集成的接入和回传节点例如是图5的IAB-node 3。该装置对应于第一方面的实施例的方法。
图10是本申请第四方面的实施例的发送和接收信号的装置的一示意图，如图10所示，发送和接收信号的装置1000包括：
第一处理单元1001，其用于当该IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的第一路径数据或接收的第一路径数据进行路由变更；以及
第一收发单元1002，其基于变更的路由，发送该未成功发送的该第一路径数据或接收的该第一路径数据。
在至少一个实施例中，对第一路径数据进行路由变更，包括：
将该第一路径数据的目的BAP地址变更为第二路径的目的BAP地址；或者，
将该第一路径数据的目的BAP地址变更为该第二路径的目的BAP地址，并且将该第一路径数据的路径标识变更为该第二路径的路径标识。
该发送该第一路径数据，包括：
将该第一路径数据发送到该IAB-node与该第二路径的下一跳节点之间的回传RLC信道。
在至少一个实施例中，IAB-node的第一路径的目的BAP地址不可到达的情况包括：
该IAB-node切换到新的父节点之后导致该第一路径的目的BAP地址不可到达；或者，该IAB-node与第一父节点之间的链路发生无线链路失败之后导致该第一路径的目的BAP地址不可到达。
在至少一个实施例中，该第一处理单元1001还进行如下操作：
触发对该第一路径的数据进行路由变更后启动定时器，以及，该定时器超时后停止对该第一路径数据的路由变更；或者
把未成功发送的该第一路径数据发送完时，停止对该第一路径数据的路由变更；或者
发送完未成功发送的该第一路径数据以及确定下游子节点发送完未成功发送的该第一路径数据时，停止对该第一路径数据的路由变更。
在至少一个实施例中，该IAB-node接收到该下游子节点发送的结束指示时，该第一处理单元1001确定该下游子节点发送完该未成功发送的该第一路径数据。
在至少一个实施例中，该IAB-node与第一父节点之间的链路发生无线链路失败之后导致该第一路径的目的BAP地址不可到达的情况下，第二路径是经过IAB-node与第二父节点之间链路的路径，，其中，该IAB-node与第二父节点之间的链路未发生无线链路失败。
在至少一个实施例中，在该IAB-node与第一父节点之间的链路发生无线链路失败(RLF)之后，该第一处理单元1001触发该IAB-node对该第一路径数据的路由变更。
在至少一个实施例中，该第一收发单元1002还接收该Donor-CU发送的路径重配置参数，该路径重配置参数包括该第一路径的目的BAP地址及路径标识。
在至少一个实施例中，该第一收发单元1002还接收该Donor-CU发送的路径重配置参数，该路径重配置参数包括该第一路径的目的BAP地址与该第二路径的目的BAP地址的映射，或者，包括该第一路径的目的BAP地址及路径标识与该第二路径的目的BAP地址及路径标识的映射。
在至少一个实施例中，该第一收发单元1002还接收Donor-CU发送的路径重配置参数，该路径重配置参数包括该第二路径的目的BAP地址、该第二路径的路径标识和该IAB-node到该第二路径的下一跳节点的回传RLC信道标识。
在至少一个实施例中，该第二路径的目的BAP地址为用于上行F1-C和非F1数据的目的BAP地址，该第二路径的路径标识为用于上行F1-C和非F1数据的路径标识；或者，该第二路径的目的BAP地址为用于上行F1-U数据的目的BAP地址，该第二路径的路径标识为用于上行F1-U数据的路径标识。
在至少一个实施例中，该到该第二路径的下一跳节点的回传RLC信道标识为：
用于上行F1-C和非F1数据的回传RLC信道标识；或者，用于上行F1-U数据的回传RLC信道标识。
在至少一个实施例中，在该IAB-node切换到新的父节点之后导致该第一路径的目的BAP地址不可到达的情况下，
该路径重配置参数由Donor-CU发送的用于切换的RRC重配置消息发送，其中，该IAB-node完成到新的父节点的随机接入时，该第一处理单元1001触发对该第一路径数据的路由变更。
在至少一个实施例中，在该IAB-node切换到新的父节点之后导致该第一路径的目的BAP地址不可到达的情况下，该路径重配置参数由该IAB-node完成到新的父节点的切换后从Donor-CU收到的F1AP消息发送，其中，当该IAB-node切换到新的父节点时，该第一收发单元1002停止发送该第一路径数据，以及，该IAB-node收到该F1AP消息时，该第一处理单元1001触发对该第一路径数据的路由变更。
在至少一个实施例中，该IAB-node与第一父节点之间的链路发生无线链路失败之后导致该第一路径的目的BAP地址不可到达的情况下，该路径重配置参数通过该IAB-node完成到新的父节点的重建立后从Donor-CU接收到的RRC重配置消息或F1AP消息发送，其中，当该IAB-node与第一父节点之间的链路发生无线链路失败时该第一收发单元1002停止发送该第一路径数据，该第一收发单元1002接收到该路径重配置参数后，该第一处理单元1001触发对该第一路径数据的路由变更。
在至少一个实施例中，该IAB-node与第一父节点之间的链路发生无线链路失败之后导致该第一路径的目的BAP地址不可到达的情况下，该路径重配置参数由该IAB-node向Donor-CU报告无线链路失败信息后从Donor-CU收到的F1AP消息发送，其中：
当该IAB-node与第一父节点之间的链路发生无线链路失败时该第一收发单元1002停止发送该第一路径数据，该第一收发单元1002收到该F1AP消息时，该第一处理单元1001触发对该第一路径数据的路由变更。
根据本申请第四方面的实施例，对第一路径的数据进行路由变更，由此，能够基于变更后的路由来发送数据，避免数据的丢失。
第五方面的实施例
本申请实施例提供一种发送和接收信号的装置。该装置例如可以是集成的接入和回传节点的子节点，也可以是配置于该子节点的某个或某些部件或者组件，集成的接入和回传节点例如是图5的IAB-node 3。该装置对应于第二方面的实施例的方法。
图11是本申请第五方面的实施例的发送和接收信号的装置的一示意图，如图11所示，发送和接收信号的装置1100包括：
第二处理单元1101，其当该IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的该第一路径数据或接收的该第一路径数据进行路由变更；以及
第二收发单元1102，其基于变更的路由，发送该未成功发送的该第一路径数据或接收的该第一路径数据。
在至少一个实施例中，对该第一路径数据进行路由变更，包括：
将该第一路径数据的目的BAP地址变更为第二路径的目的BAP地址；或者，
将该第一路径数据的BAP地址变更为第二路径的BAP地址，并且将该第一路径数据的路径标识变更为第二路径的路径标识。
在至少一个实施例中，该发送该第一路径数据，包括：
将该第一路径数据发送到该子节点与该第二路径的下一跳节点之间的回传RLC信道。
在至少一个实施例中，IAB-node的第一路径的目的BAP地址不可到达的情况包括：
该IAB-node切换到新的父节点之后导致该第一路径的目的BAP地址不可到达；或者，
该IAB-node与第一父节点之间的链路发生无线链路失败之后导致该第一路径的目的BAP地址不可到达。
在至少一个实施例中，该第二处理单元1101还进行如下操作：
触发对该第一路径数据进行路由变更后启动定时器，该定时器超时后停止对该第一路径数据的路由变更；或者
在未成功发送的该第一路径数据发送完之后，停止对该第一路径数据的路由变更；或者
在未成功发送的该第一路径数据被发送完成以及确定下游子节点发送完未成功 发送的该第一路径数据的情况下，停止对该第一路径数据的路由变更。
在至少一个实施例中，该第二处理单元1101在收到该子节点的下游子节点发送的结束指示时，确定该下游子节点发送完该未成功发送的该第一路径数据。
在至少一个实施例中，该IAB-node与第一父节点之间的链路发生无线链路失败之后导致该第一路径的目的BAP地址不可到达的情况下，第二路径是经过IAB-node与第二父节点之间链路的路径，其中，该IAB-node与第二父节点之间的链路未发生无线链路失败。
在至少一个实施例中，该第二收发单元1102收到该IAB-node与第一父节点之间的链路发生无线链路失败(RLF)时发送的RLF指示时，该第二处理单元1101触发该子节点对该第一路径数据的路由变更。
在至少一个实施例中，该RLF指示包含该第一路径的目的BAP地址和路径标识。
在至少一个实施例中，该第二收发单元1102还接收该Donor-CU发送的路径重配置参数，该路径重配置参数包括该第一路径的目的BAP地址及路径标识。
在至少一个实施例中，该第二收发单元1102还接收该Donor-CU发送的路径重配置参数，该路径重配置参数包括该第一路径的目的BAP地址与该第二路径的目的BAP地址的映射，或者，包括该第一路径的目的BAP地址及路径标识与该第二路径的目的BAP地址及路径标识的映射。
在至少一个实施例中，该第二收发单元1102还接收该Donor-CU发送的路径重配置参数，该路径重配置参数包括该第二路径的目的BAP地址、该第二路径的路径标识和该子节点到该第二路径的下一跳节点的回传RLC信道标识。
在至少一个实施例中，该第二路径的目的BAP地址为用于上行F1-C和非F1数据的目的BAP地址，该第二路径的路径标识为用于上行F1-C和非F1数据的路径标识；或者，该第二路径的目的BAP地址为用于上行F1-U数据的目的BAP地址，该第二路径的路径标识为用于上行F1-U数据的路径标识。
在至少一个实施例中，该到该第二路径的下一跳节点的回传RLC信道标识为：
用于上行F1-C和非F1数据的回传RLC信道标识；或者，用于上行F1-U数据的回传RLC信道标识。
在至少一个实施例中，在该IAB-node切换到新的父节点之后导致该第一路径的目的BAP地址不可到达的情况下，该路径重配置参数由该IAB-node切换之前的RRC 重配置消息发送，其中，该第二收发单元1102收到该IAB-node完成到新的父节点的随机接入后发送的切换成功指示时，该第二处理单元1101触发对该第一路径数据的路由变更。
在至少一个实施例中，在该IAB-node切换到新的父节点之后导致该第一路径的目的BAP地址不可到达的情况下，该路径重配置参数由该IAB-node完成切换后从Donor-CU收到的F1AP消息发送，其中：
当该第二收发单元1102收到该IAB-node完成到新的父节点的随机接入后发送的切换成功指示时，停止发送该第一路径数据；以及，
该第二收发单元1102收到该F1AP消息时，该第二处理单元1101触发对该第一路径数据的路由变更。
在至少一个实施例中，该IAB-node与第一父节点之间的链路发生无线链路失败之后导致该第一路径的目的BAP地址不可到达的情况下，该路径重配置参数由该IAB-node发生无线链路失败之前的Donor-CU发送的RRC重配置消息发送，其中：
该第二收发单元1102收到该IAB-node完成到新的父节点的随机接入后发送的重建立成功指示时，该第二处理单元1101触发对该第一路径数据的路由变更。
在至少一个实施例中，该IAB-node与第一父节点之间的链路发生无线链路失败之后导致该第一路径的目的BAP地址不可到达的情况下，该路径重配置参数由该IAB-node完成到新的父节点的重建立后从Donor-CU接收到的RRC重配置消息或F1AP消息发送，其中：
该第二收发单元1102收到该IAB-node完成到新的父节点的随机接入后发送的重建立成功指示时停止发送该第一路径数据；以及
该第二收发单元1102接收到该路径重配置参数后，该第二处理单元1101触发对该第一路径数据的路由变更。
在至少一个实施例中，该IAB-node与第一父节点之间的链路发生无线链路失败之后导致该第一路径的目的BAP地址不可到达的情况下，该路径重配置参数由该IAB-node向Donor-CU报告无线链路失败信息后从Donor-CU收到的F1AP消息发送，其中：
当该第二收发单元1102收到该IAB-node与第一父节点之间的链路发生无线链路失败时发送的RLF指示时，停止发送该第一路径数据；以及
该第二收发单元1102收到该F1AP消息时，该第二处理单元1101触发对该第一路径数据的路由变更。
根据本申请第五方面的实施例，对第一路径的数据进行路由变更，由此，能够基于变更后的路由来发送数据，避免数据的丢失。
第六方面的实施例
本申请实施例提供一种信号的发送和接收装置。该装置例如可以是宿主中心单元(IAB-donor CU)，也可以是配置于宿主中心单元(IAB-donor CU)的某个或某些部件或者组件，宿主中心单元(IAB-donor CU)例如是图5的Donor CU。该发送和接收装置对应于第三方面的实施例所述的发送和接收信号的方法。
图12是第六方面的实施例中发送和接收信号的装置的一个示意图，如图12所示，该装置1200包括：
第三收发单元1201，其当IAB-node的第一路径的目的BAP地址不可到达时，向IAB-node或该IAB-node的子节点发送路径重配置参数，其中，该路径重配置参数用于该IAB-node或该子节点对未成功发送的该第一路径数据或接收的该第一路径数据进行路由变更。
在至少一个实施例中，该路径重配置参数包括该第一路径的目的BAP地址及路径标识。
在至少一个实施例中，该路径重配置参数包括该第一路径的目的BAP地址与该第二路径的目的BAP地址的映射，或者，包括该第一路径的目的BAP地址及路径标识与该第二路径的目的BAP地址及路径标识的映射。
在至少一个实施例中，IAB-node的第一路径的目的BAP地址不可到达的情况包括：
该IAB-node切换到新的父节点之后导致该第一路径的目的BAP地址不可到达；或者，
该IAB-node与第一父节点之间的链路发生无线链路失败之后导致该第一路径的目的BAP地址不可到达。
在至少一个实施例中，该路径重配置参数包括该第二路径的目的BAP地址、该第二路径的路径标识和该IAB-node到该第二路径的下一跳节点的回传RLC信道标识。
在至少一个实施例中，该第二路径的目的BAP地址为用于上行F1-C和非F1数据的目的BAP地址，该第二路径的路径标识为用于上行F1-C和非F1数据的路径标识；或者
该第二路径的目的BAP地址为用于上行F1-U数据的目的BAP地址，该第二路径的路径标识为用于上行F1-U数据的路径标识。
在至少一个实施例中，该到该第二路径的下一跳节点的回传RLC信道标识为：
用于上行F1-C和非F1数据的回传RLC信道标识；或者，用于上行F1-U数据的回传RLC信道标识。
在至少一个实施例中，在该IAB-node切换到新的父节点之后导致该第一路径的目的BAP地址不可到达的情况下：
该第三收发单元1201在该IAB-node切换之前向该IAB-node或向该子节点发送包含该路径重配置参数的RRC重配置消息；或者，
该第三收发单元1201在该IAB-node完成到新的父节点的切换后向该IAB-node或向该子节点发送包含该路径重配置参数的F1AP消息。
在至少一个实施例中，在该IAB-node与第一父节点之间的链路发生无线链路失败之后导致该第一路径的目的BAP地址不可到达的情况下，该第三收发单元1201在该IAB-node完成到新的父节点的重建立后向该IAB-node或向该子节点发送包含该路径重配置参数的RRC重配置消息或F1AP消息。
在至少一个实施例中，该IAB-node与第一父节点之间的链路发生无线链路失败之后导致该第一路径的目的BAP地址不可到达的情况下，该第三收发单元1201在该IAB-node向该Donor-CU报告无线链路失败信息后向该IAB-node或向该子节点发送包含该路径重配置参数的RRC重配置消息或F1AP消息。
在至少一个实施例中，该IAB-node与第一父节点之间的链路发生无线链路失败后导致该第一路径的目的BAP地址不可到达的情况下，该第三收发单元1201在该IAB-node发生无线链路失败之前向该子节点发送包含该路径重配置参数的RRC重配置消息。
根据本申请第三方面的实施例，IAB-node或其子节点能够利用路径重配置参数对第一路径的数据进行路由变更，由此，IAB-node或子节点能够基于变更后的路由来发送数据，避免数据的丢失。
以上各实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
第七方面的实施例
本申请实施例还提供一种通信系统，可以参考图1，与第一方面至第六方面的实施例相同的内容不再赘述。
在一些实施例中，通信系统可以包括：
宿主中心单元(IAB-donor CU)，其包括如第四方面的实施例所述的发送和接收信号的装置1200；
集成的接入和回传节点，其包括如第四方面的实施例所述的发送和接收信号的装置1000；以及
子节点，其包括如第五方面的实施例所述的发送和接收信号的装置1100。
其中，集成的接入和回传节点(IAB)可以包括IAB-MT功能单元和IAB-DU功能单元。其中，IAB-MT功能单元可以具有与终端设备相同的结构。IAB-DU功能单元和宿主中心单元(IAB-donor CU)可以具有与网络设备相同的单元。
图13是本申请实施例的网络设备的构成示意图。如图13所示，网络设备1300可以包括：处理器1310(例如中央处理器CPU)和存储器1320；存储器1220耦合到处理器1310。其中该存储器1320可存储各种数据；此外还存储信息处理的程序1330，并且在处理器1310的控制下执行该程序1330。
例如，处理器1310可以被配置为执行程序而实现如第一方面的实施例中IAB-DU或第二方面的实施例中IAB-donor CU执行的方法。
此外，如图13所示，网络设备1300还可以包括：收发机1340和天线1350等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1300也并不是必须要包括图13中所示的所有部件；此外，网络设备1300还可以包括图13中没有示出的部件，可以参考现有技术。
图14是本申请实施例的终端设备的示意图。如图14所示，该终端设备1400可以包括处理器1410和存储器1420；存储器1420存储有数据和程序，并耦合到处理器1410。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或 代替该结构，以实现电信功能或其他功能。例如，处理器1410可以被配置为执行程序而实现如第一方面的实施例所述的由IAB-MT执行的方法。
如图14所示，该终端设备1400还可以包括：通信模块1430、输入单元1440、显示器1450、电源1460。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备1400也并不是必须要包括图14中所示的所有部件，上述部件并不是必需的；此外，终端设备1400还可以包括图14中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机程序，其中当在IAB中执行所述程序时，所述程序使得所述IAB执行第一方面的实施例所述的发送和接收信号的方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得IAB执行第一方面的实施例所述的发送和接收信号的方法。
本申请实施例还提供一种计算机程序，其中当在IAB-node的子节点中执行所述程序时，所述程序使得所述子节点执行第二方面的实施例所述的方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得IAB-node的子节点执行第二方面的实施例所述的方法。
本申请实施例还提供一种计算机程序，其中当在Donor-CU中执行所述程序时，所述程序使得所述Donor-CU执行第三方面的实施例所述的方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得Donor-CU执行第三方面的实施例所述的方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM 存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于包括以上实施例的实施方式，还公开下述的附记：
IAB-node侧方法：
1.一种发送和接收信号的方法，应用于集成的接入和回传节点(IAB-node)，该方法包括：
当所述IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的第一路径数据或接收的第一路径数据进行路由变更；以及
基于变更的路由，发送所述未成功发送的所述第一路径数据或接收的所述第一路径数据。
2.如附记1所述的方法，其中，对所述第一路径数据进行路由变更，包括：
将所述第一路径数据的目的BAP地址变更为第二路径的目的BAP地址；或者，
将所述第一路径数据的目的BAP地址变更为所述第二路径的目的BAP地址，并 且将所述第一路径数据的路径标识变更为所述第二路径的路径标识。
3.如附记2所述的方法，其中，所述发送所述第一路径数据，包括：
将所述第一路径数据发送到所述IAB-node与所述第二路径的下一跳节点之间的回传RLC信道。
4.如附记3所述的方法，其中，IAB-node的第一路径的目的BAP地址不可到达的情况包括：
所述IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达；或者，
所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达。
5.如附记4所述的方法，其中，所述方法还包括：
所述IAB-node触发对所述第一路径的数据进行路由变更后启动定时器，以及，所述定时器超时后停止对所述第一路径数据的路由变更；或者
所述IAB-node把未成功发送的所述第一路径数据发送完时，停止对所述第一路径数据的路由变更；或者
所述IAB-node发送完未成功发送的所述第一路径数据以及确定下游子节点发送完未成功发送的所述第一路径数据时，停止对所述第一路径数据的路由变更。
6.如附记5所述的方法，其中，
所述IAB-node接收到所述下游子节点发送的结束指示时，确定所述下游子节点发送完所述未成功发送的所述第一路径数据。
7.如附记4所述的方法，其中，所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达的情况下，
所述第二路径是经过所述IAB-node与第二父节点之间链路的路径，其中，所述IAB-node与第二父节点之间的链路未发生无线链路失败。
8.如附记7所述的方法，其中，
在所述IAB-node与第一父节点之间的链路发生无线链路失败(RLF)之后，
触发所述IAB-node对所述第一路径数据的路由变更。
9.如附记4所述的方法，其中，所述方法还包括：
所述IAB-node接收所述Donor-CU发送的路径重配置参数，所述路径重配置参 数包括所述第一路径的目的BAP地址及路径标识。
10.如附记4所述的方法，其中，所述方法还包括：
所述IAB-node接收所述Donor-CU发送的路径重配置参数，所述路径重配置参数包括所述第一路径的目的BAP地址与所述第二路径的目的BAP地址的映射，或者，包括所述第一路径的目的BAP地址及路径标识与所述第二路径的目的BAP地址及路径标识的映射。
11.如附记4所述的方法，其中，所述方法还包括：
所述IAB-node接收Donor-CU发送的路径重配置参数，所述路径重配置参数包括所述第二路径的目的BAP地址、所述第二路径的路径标识和所述IAB-node到所述第二路径的下一跳节点的回传RLC信道标识。
12.如附记11所述的方法，其中，
所述第二路径的目的BAP地址为用于上行F1-C和非F1数据的目的BAP地址，所述第二路径的路径标识为用于上行F1-C和非F1数据的路径标识；或者
所述第二路径的目的BAP地址为用于上行F1-U数据的目的BAP地址，所述第二路径的路径标识为用于上行F1-U数据的路径标识。
13.如附记11所述的方法，其中，
所述到所述第二路径的下一跳节点的回传RLC信道标识为：
用于上行F1-C和非F1数据的回传RLC信道标识；或者，用于上行F1-U数据的回传RLC信道标识。
14.如附记9-11中任一项所述的方法，其中，在所述IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达的情况下，
所述路径重配置参数由Donor-CU发送的用于切换的RRC重配置消息发送，其中，所述方法还包括：所述IAB-node完成到新的父节点的随机接入时触发对所述第一路径数据的路由变更。
15.如附记9-11中任一项所述的方法，其中，在所述IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达的情况下，
所述路径重配置参数由所述IAB-node完成到新的父节点的切换后从Donor-CU收到的F1AP消息发送，其中，所述方法还包括：
当所述IAB-node切换到新的父节点时停止发送所述第一路径数据；以及，
所述IAB-node收到所述F1AP消息时触发对所述第一路径数据的路由变更。
16.如附记9-11中任一项所述的方法，其中，所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达的情况下，
所述路径重配置参数通过所述IAB-node完成到新的父节点的重建立后从Donor-CU接收到的RRC重配置消息或F1AP消息发送，所述方法还包括：
当所述IAB-node与第一父节点之间的链路发生无线链路失败时停止发送所述第一路径数据；以及
所述IAB-node接收到所述路径重配置参数后触发对所述第一路径数据的路由变更。
17.如附记9-11中任一项所述的方法，其中，所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达的情况下，
所述路径重配置参数由所述IAB-node向Donor-CU报告无线链路失败信息后从Donor-CU收到的F1AP消息发送，其中，所述方法还包括：
当所述IAB-node与第一父节点之间的链路发生无线链路失败时停止发送所述第一路径数据；以及
所述IAB-node收到所述F1AP消息时触发对所述第一路径数据的路由变更。
IAB-node子节点侧的方法：
1.一种发送和接收信号的方法，应用于集成的接入和回传节点(IAB-node)的子节点，其中，所述方法包括：
当所述IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的所述第一路径数据或接收的所述第一路径数据进行路由变更；以及
基于变更的路由，发送所述未成功发送的所述第一路径数据或接收的所述第一路径数据。
2.如附记1所述的方法，其中，对所述第一路径数据进行路由变更，包括：
将所述第一路径数据的目的BAP地址变更为第二路径的目的BAP地址；或者，
将所述第一路径数据的BAP地址变更为第二路径的BAP地址，并且将所述第一路径数据的路径标识变更为第二路径的路径标识。
3.如附记2所述的方法，其中，所述发送所述第一路径数据，包括：
将所述第一路径数据发送到所述子节点与所述第二路径的下一跳节点之间的回传RLC信道。
4.如附记3所述的方法，其中，IAB-node的第一路径的目的BAP地址不可到达的情况包括：
所述IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达；或者，
所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达。
5.如附记4所述的方法，其中，所述方法还包括：
所述子节点触发对所述第一路径数据进行路由变更后启动定时器，所述定时器超时后停止对所述第一路径数据的路由变更；或者
所述子节点把未成功发送的所述第一路径数据发送完之后，停止对所述第一路径数据的路由变更；或者
所述子节点发送完未成功发送的所述第一路径数据以及确定下游子节点发送完未成功发送的所述第一路径数据的情况下，停止对所述第一路径数据的路由变更。
6.如附记5所述的方法，其中，
所述子节点收到所述子节点的下游子节点发送的结束指示时，确定所述下游子节点发送完所述未成功发送的所述第一路径数据。
7.如附记4所述的方法，其中，所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达的情况下，
所述第二路径是经过所述IAB-node与第二父节点之间链路的路径，其中，所述IAB-node与第二父节点之间的链路未发生无线链路失败。
8.如附记7所述的方法，其中，
所述子节点收到所述IAB-node与第一父节点之间的链路发生无线链路失败(RLF)时发送的RLF指示时，触发所述子节点对所述第一路径数据的路由变更。
9.如附记8所述的方法，其中，所述RLF指示包含所述第一路径的目的BAP地址和路径标识。
10.如附记4所述的方法，其中，所述方法还包括：
所述子节点接收所述Donor-CU发送的路径重配置参数，所述路径重配置参数包 括所述第一路径的目的BAP地址及路径标识。
11.如附记4所述的方法，其中，所述方法还包括：
所述子节点接收所述Donor-CU发送的路径重配置参数，所述路径重配置参数包括所述第一路径的目的BAP地址与所述第二路径的目的BAP地址的映射，或者，包括所述第一路径的目的BAP地址及路径标识与所述第二路径的目的BAP地址及路径标识的映射。
12.如附记4所述的方法，其中，所述方法还包括：
所述子节点接收所述Donor-CU发送的路径重配置参数，所述路径重配置参数包括所述第二路径的目的BAP地址、所述第二路径的路径标识和所述子节点到所述第二路径的下一跳节点的回传RLC信道标识。
13.如附记12所述的方法，其中，
所述第二路径的目的BAP地址为用于上行F1-C和非F1数据的目的BAP地址，所述第二路径的路径标识为用于上行F1-C和非F1数据的路径标识；或者
所述第二路径的目的BAP地址为用于上行F1-U数据的目的BAP地址，所述第二路径的路径标识为用于上行F1-U数据的路径标识。
14.如附记12所述的方法，其中，
所述到所述第二路径的下一跳节点的回传RLC信道标识为：
用于上行F1-C和非F1数据的回传RLC信道标识；或者，用于上行F1-U数据的回传RLC信道标识。
15.如附记10-12中任一项所述的方法，其中，在所述IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达的情况下，
所述路径重配置参数由所述IAB-node切换之前的RRC重配置消息发送，其中，所述方法还包括：所述子节点收到所述IAB-node完成到新的父节点的随机接入后发送的切换成功指示时触发对所述第一路径数据的路由变更。
16.如附记10-12中任一项所述的方法，其中，在所述IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达的情况下，
所述路径重配置参数由所述IAB-node完成切换后从Donor-CU收到的F1AP消息发送，其中，所述方法还包括：
当所述子节点收到所述IAB-node完成到新的父节点的随机接入后发送的切换成 功指示时，停止发送所述第一路径数据；以及，
所述子节点收到所述F1AP消息时触发对所述第一路径数据的路由变更。
17.如附记10-12中任一项所述的方法，其中，所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达的情况下，
所述路径重配置参数由所述IAB-node发生无线链路失败之前的Donor-CU发送的RRC重配置消息发送，其中，所述方法还包括：
所述子节点收到所述IAB-node完成到新的父节点的随机接入后发送的重建立成功指示时触发对所述第一路径数据的路由变更。
18.如附记10-12中任一项所述的方法，其中，所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达的情况下，
所述路径重配置参数由所述IAB-node完成到新的父节点的重建立后从Donor-CU接收到的RRC重配置消息或F1AP消息发送，其中，所述方法还包括：
所述子节点收到所述IAB-node完成到新的父节点的随机接入后发送的重建立成功指示时停止发送所述第一路径数据；以及，
所述子节点接收到所述路径重配置参数后触发对所述第一路径数据的路由变更。
19.如附记10-12中任一项所述的方法，其中，所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达的情况下，
所述路径重配置参数由所述IAB-node向Donor-CU报告无线链路失败信息后从Donor-CU收到的F1AP消息发送，其中，所述方法还包括：
当所述子节点收到所述IAB-node与第一父节点之间的链路发生无线链路失败时发送的RLF指示时，停止发送所述第一路径数据；以及，
所述子节点收到所述F1AP消息时触发对所述第一路径数据的路由变更。
Donor-CU侧的方法：
1.一种发送和接收信号的方法，应用于宿主中心单元(Donor-CU)，该方法包括：
当IAB-node的第一路径的目的BAP地址不可到达时，向IAB-node或所述IAB-node的子节点发送路径重配置参数，
其中，
所述路径重配置参数用于所述IAB-node或所述子节点对未成功发送的所述第一 路径数据或接收的所述第一路径数据进行路由变更。
2.如附记1所述的方法，其中，
所述路径重配置参数包括所述第一路径的目的BAP地址及路径标识。
3.如附记1所述的方法，其中，
所述路径重配置参数包括所述第一路径的目的BAP地址与所述第二路径的目的BAP地址的映射，或者，包括所述第一路径的目的BAP地址及路径标识与所述第二路径的目的BAP地址及路径标识的映射。
4.如附记1所述的方法，其中，IAB-node的第一路径的目的BAP地址不可到达的情况包括：
所述IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达；或者，
所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达。
5.如附记4所述的方法，其中，
所述路径重配置参数包括所述第二路径的目的BAP地址、所述第二路径的路径标识和所述IAB-node到所述第二路径的下一跳节点的回传RLC信道标识。
6.如附记5所述的方法，其中，
所述第二路径的目的BAP地址为用于上行F1-C和非F1数据的目的BAP地址，所述第二路径的路径标识为用于上行F1-C和非F1数据的路径标识；或者
所述第二路径的目的BAP地址为用于上行F1-U数据的目的BAP地址，所述第二路径的路径标识为用于上行F1-U数据的路径标识。
7.如附记5所述的方法，其中，
所述到所述第二路径的下一跳节点的回传RLC信道标识为：
用于上行F1-C和非F1数据的回传RLC信道标识；或者，用于上行F1-U数据的回传RLC信道标识。
8.如附记5所述的方法，其中，在所述IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达的情况下：
所述Donor-CU在所述IAB-node切换之前向所述IAB-node或向所述子节点发送包含所述路径重配置参数的RRC重配置消息；或者，
所述Donor-CU在所述IAB-node完成到新的父节点的切换后向所述IAB-node或向所述子节点发送包含所述路径重配置参数的F1AP消息。
9.如附记5所述的方法，其中，在所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达的情况下，
所述Donor-CU在所述IAB-node完成到新的父节点的重建立后向所述IAB-node或向所述子节点发送包含所述路径重配置参数的RRC重配置消息或F1AP消息。
10.如附记5所述的方法，其中，所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达的情况下，
所述Donor-CU在所述IAB-node向Donor-CU报告无线链路失败信息后向所述IAB-node或向所述子节点发送包含所述路径重配置参数的RRC重配置消息或F1AP消息。
11.如附记5所述的方法，其中，所述IAB-node与第一父节点之间的链路发生无线链路失败后导致所述第一路径的目的BAP地址不可到达的情况下，
所述Donor-CU在所述IAB-node发生无线链路失败之前向所述子节点发送包含所述路径重配置参数的RRC重配置消息。

Claims (20)

  1. 一种发送和接收信号的装置，应用于集成的接入和回传节点(IAB-node)，该装置包括：
    第一处理单元，其用于当所述IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的第一路径数据或接收的第一路径数据进行路由变更；以及
    第一收发单元，其基于变更的路由，发送所述未成功发送的所述第一路径数据或接收的所述第一路径数据。
  2. 如权利要求1所述的装置，其中，对所述第一路径数据进行路由变更，包括：
    将所述第一路径数据的目的BAP地址变更为第二路径的目的BAP地址；或者，
    将所述第一路径数据的目的BAP地址变更为所述第二路径的目的BAP地址，并且将所述第一路径数据的路径标识变更为所述第二路径的路径标识。
  3. 如权利要求2所述的装置，其中，所述发送所述第一路径数据，包括：
    将所述第一路径数据发送到所述IAB-node与所述第二路径的下一跳节点之间的回传RLC信道。
  4. 如权利要求3所述的装置，其中，IAB-node的第一路径的目的BAP地址不可到达的情况包括：
    所述IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达；或者，
    所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达。
  5. 如权利要求4所述的装置，其中，所述第一处理单元还进行如下操作：
    触发对所述第一路径的数据进行路由变更后启动定时器，以及，所述定时器超时后停止对所述第一路径数据的路由变更；或者
    把未成功发送的所述第一路径数据发送完时，停止对所述第一路径数据的路由变更；或者
    发送完未成功发送的所述第一路径数据以及确定下游子节点发送完未成功发送的所述第一路径数据时，停止对所述第一路径数据的路由变更。
  6. 如权利要求5所述的装置，其中，
    所述IAB-node接收到所述下游子节点发送的结束指示时，所述第一处理单元确定所述下游子节点发送完所述未成功发送的所述第一路径数据。
  7. 如权利要求4所述的装置，其中，
    所述第一收发单元还接收所述Donor-CU发送的路径重配置参数，所述路径重配置参数包括所述第一路径的目的BAP地址与所述第二路径的目的BAP地址的映射，或者，包括所述第一路径的目的BAP地址及路径标识与所述第二路径的目的BAP地址及路径标识的映射。
  8. 如权利要求4所述的装置，其中，
    所述第一收发单元还接收Donor-CU发送的路径重配置参数，所述路径重配置参数包括所述第二路径的目的BAP地址、所述第二路径的路径标识和所述IAB-node到所述第二路径的下一跳节点的回传RLC信道标识。
  9. 如权利要求8所述的装置，其中，
    所述第二路径的目的BAP地址为用于上行F1-C和非F1数据的目的BAP地址，所述第二路径的路径标识为用于上行F1-C和非F1数据的路径标识；或者
    所述第二路径的目的BAP地址为用于上行F1-U数据的目的BAP地址，所述第二路径的路径标识为用于上行F1-U数据的路径标识。
  10. 如权利要求7所述的装置，其中，所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达的情况下，
    所述路径重配置参数通过所述IAB-node完成到新的父节点的重建立后从Donor-CU接收到的RRC重配置消息或F1AP消息发送，
    其中，
    当所述IAB-node与第一父节点之间的链路发生无线链路失败时停止发送所述第一路径数据；以及
    所述第一收发单元接收到所述路径重配置参数后，所述第一处理单元触发对所述第一路径数据的路由变更。
  11. 一种发送和接收信号的装置，应用于集成的接入和回传节点(IAB-node)的子节点，其中，所述装置包括：
    第二处理单元，其当所述IAB-node的第一路径的目的BAP地址不可到达时，对未成功发送的所述第一路径数据或接收的所述第一路径数据进行路由变更；以及
    第二收发单元，其基于变更的路由，发送所述未成功发送的所述第一路径数据或接收的所述第一路径数据。
  12. 如权利要求11所述的装置，其中，对所述第一路径数据进行路由变更，包括：
    将所述第一路径数据的目的BAP地址变更为第二路径的目的BAP地址；或者，
    将所述第一路径数据的BAP地址变更为第二路径的BAP地址，并且将所述第一路径数据的路径标识变更为第二路径的路径标识。
  13. 如权利要求12所述的装置，其中，所述发送所述第一路径数据，包括：
    将所述第一路径数据发送到所述子节点与所述第二路径的下一跳节点之间的回传RLC信道。
  14. 如权利要求13所述的装置，其中，IAB-node的第一路径的目的BAP地址不可到达的情况包括：
    所述IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达；或者，
    所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达。
  15. 如权利要求14所述的装置，其中，所述第二处理单元还进行如下操作：
    触发对所述第一路径数据进行路由变更后启动定时器，所述定时器超时后停止对所述第一路径数据的路由变更；或者
    在未成功发送的所述第一路径数据发送完之后，停止对所述第一路径数据的路由变更；或者
    在未成功发送的所述第一路径数据被发送完成以及确定下游子节点发送完未成功发送的所述第一路径数据的情况下，停止对所述第一路径数据的路由变更。
  16. 如权利要求14所述的装置，其中，所述IAB-node与第一父节点之间的链路发生无线链路失败之后导致所述第一路径的目的BAP地址不可到达的情况下，
    所述第二路径是经过所述IAB-node与第二父节点之间链路的路径，其中，所述IAB-node与第二父节点之间的链路未发生无线链路失败。
  17. 如权利要求16所述的装置，其中，
    所述第二收发单元收到所述IAB-node与第一父节点之间的链路发生无线链路失败(RLF)时发送的RLF指示时，所述第二处理单元触发所述子节点对所述第一路径 数据的路由变更。
  18. 如权利要求17所述的装置，其中，所述RLF指示包含所述第一路径的目的BAP地址和路径标识。
  19. 如权利要求14所述的装置，其中，
    所述第二收发单元还接收所述Donor-CU发送的路径重配置参数，所述路径重配置参数包括所述第一路径的目的BAP地址及路径标识。
  20. 如权利要求19所述的装置，其中，在所述IAB-node切换到新的父节点之后导致所述第一路径的目的BAP地址不可到达的情况下，
    所述路径重配置参数由所述IAB-node切换之前的RRC重配置消息发送，其中，所述第二收发单元收到所述IAB-node完成到新的父节点的随机接入后发送的切换成功指示时，所述第二处理单元触发对所述第一路径数据的路由变更。
PCT/CN2021/084795 2021-03-31 2021-03-31 发送和接收信号的方法、装置和通信系统 WO2022205253A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN202180096678.2A CN117121559A (zh) 2021-03-31 2021-03-31 发送和接收信号的方法、装置和通信系统
JP2023559859A JP2024511815A (ja) 2021-03-31 2021-03-31 信号を送受信する方法、装置及び通信システム
PCT/CN2021/084795 WO2022205253A1 (zh) 2021-03-31 2021-03-31 发送和接收信号的方法、装置和通信系统
EP21933913.2A EP4319314A4 (en) 2021-03-31 2021-03-31 SIGNAL TRANSMITTING AND RECEIVING METHOD, SIGNAL TRANSMITTING AND RECEIVING APPARATUS AND COMMUNICATION SYSTEM
US18/372,189 US20240015098A1 (en) 2021-03-31 2023-09-25 Method and apparatus for transmitting and receiving signal and communication system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/084795 WO2022205253A1 (zh) 2021-03-31 2021-03-31 发送和接收信号的方法、装置和通信系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/372,189 Continuation US20240015098A1 (en) 2021-03-31 2023-09-25 Method and apparatus for transmitting and receiving signal and communication system

Publications (1)

Publication Number Publication Date
WO2022205253A1 true WO2022205253A1 (zh) 2022-10-06

Family

ID=83457775

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/084795 WO2022205253A1 (zh) 2021-03-31 2021-03-31 发送和接收信号的方法、装置和通信系统

Country Status (5)

Country Link
US (1) US20240015098A1 (zh)
EP (1) EP4319314A4 (zh)
JP (1) JP2024511815A (zh)
CN (1) CN117121559A (zh)
WO (1) WO2022205253A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024164214A1 (zh) * 2023-02-09 2024-08-15 富士通株式会社 信息处理方法和装置
WO2024207363A1 (zh) * 2023-04-06 2024-10-10 富士通株式会社 信号的收发方法、装置和通信系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110636583A (zh) * 2018-06-21 2019-12-31 华为技术有限公司 路径变更方法及装置
WO2021019332A1 (en) * 2019-07-30 2021-02-04 Telefonaktiebolaget Lm Ericsson (Publ) Iab-donor cu aware remapping of bearers in iab network

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110636583A (zh) * 2018-06-21 2019-12-31 华为技术有限公司 路径变更方法及装置
WO2021019332A1 (en) * 2019-07-30 2021-02-04 Telefonaktiebolaget Lm Ericsson (Publ) Iab-donor cu aware remapping of bearers in iab network

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
CATT: "RLF Indication and Local Rerouting", 3GPP DRAFT; R2-2100227, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051973434 *
LENOVO, MOTOROLA MOBILITY: "Discussion on IAB packet rerouting", 3GPP DRAFT; R2-2101142, 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 , XP051974136 *
NOKIA, NOKIA SHANGHAI BELL: "Discussion on Reduction of Service Interruption during Intra-Donor Topology Adaptation", 3GPP DRAFT; R3-210488, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20210125 - 20210204, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051968932 *
QUALCOMM INCORPORATED: "Enhancements to Intra-donor IAB-node Migration", 3GPP DRAFT; R3-204796, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-meeting; 20200817 - 20200828, 6 August 2020 (2020-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911261 *
See also references of EP4319314A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024164214A1 (zh) * 2023-02-09 2024-08-15 富士通株式会社 信息处理方法和装置
WO2024207363A1 (zh) * 2023-04-06 2024-10-10 富士通株式会社 信号的收发方法、装置和通信系统

Also Published As

Publication number Publication date
US20240015098A1 (en) 2024-01-11
EP4319314A1 (en) 2024-02-07
CN117121559A (zh) 2023-11-24
EP4319314A4 (en) 2024-04-17
JP2024511815A (ja) 2024-03-15

Similar Documents

Publication Publication Date Title
US20210168666A1 (en) Communication method and communications apparatus
US11070996B2 (en) Method for controlling wireless link and wireless connection of terminal in wireless communication system, and apparatus supporting same
US20210075864A1 (en) Communication Method and Communications Apparatus
CN109474954B (zh) 一种会话建立方法及装置
US20240015098A1 (en) Method and apparatus for transmitting and receiving signal and communication system
WO2015123948A1 (zh) 保证业务数据连续性的方法、控制器及网关
US20240259776A1 (en) Integrated access and backhaul communication device and method
US12075328B2 (en) Method and apparatus for reporting link assistant information and transmitting data
JP2023551953A (ja) 再ルーティング方法及び装置、通信機器
WO2022082543A1 (zh) Iab节点的移植方法及装置
WO2022082690A1 (zh) 群组切换的方法、装置和系统
WO2022082495A1 (zh) 路由选择方法、装置和系统
EP3618500B1 (en) Path switching method and base station
WO2022205252A1 (zh) 发送和接收信号的方法、装置和通信系统
WO2022151298A1 (zh) 群组迁移方法、装置和系统
WO2017166291A1 (zh) 一种通信方法、终端、基站和移动性管理设备
JP2024517469A (ja) 信号の送受信方法、装置及び通信システム
WO2022233008A1 (zh) 消息发送方法、装置和系统
WO2023205941A1 (zh) 信息的发送、接收、配置方法以及装置和通信系统
WO2023010298A1 (zh) 信息发送方法，信息处理方法以及装置
WO2023150968A1 (zh) 收发信号的方法、装置和通信系统
JP7547629B2 (ja) 通信方法及び関連デバイス
WO2023184542A1 (zh) 配置信息的方法、装置和通信系统
WO2022205485A1 (zh) 信息收发方法以及装置
WO2024164214A1 (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: 21933913

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023559859

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2021933913

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021933913

Country of ref document: EP

Effective date: 20231031

NENP Non-entry into the national phase

Ref country code: DE