WO2022068164A1 - 一种通信方法及相关设备 - Google Patents
一种通信方法及相关设备 Download PDFInfo
- Publication number
- WO2022068164A1 WO2022068164A1 PCT/CN2021/085137 CN2021085137W WO2022068164A1 WO 2022068164 A1 WO2022068164 A1 WO 2022068164A1 CN 2021085137 W CN2021085137 W CN 2021085137W WO 2022068164 A1 WO2022068164 A1 WO 2022068164A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- node
- indication information
- path
- message
- destination
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 114
- 238000004891 communication Methods 0.000 title claims abstract description 103
- 238000011084 recovery Methods 0.000 claims abstract description 49
- 238000012545 processing Methods 0.000 claims description 35
- 230000006978 adaptation Effects 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 7
- 238000012546 transfer Methods 0.000 claims description 2
- 230000011664 signaling Effects 0.000 abstract description 8
- 230000005540 biological transmission Effects 0.000 description 59
- 238000013461 design Methods 0.000 description 59
- 230000006870 function Effects 0.000 description 57
- 230000001960 triggered effect Effects 0.000 description 42
- 238000010586 diagram Methods 0.000 description 27
- 238000011144 upstream manufacturing Methods 0.000 description 14
- 230000006855 networking Effects 0.000 description 11
- 230000008569 process Effects 0.000 description 10
- 230000009286 beneficial effect Effects 0.000 description 9
- 230000009977 dual effect Effects 0.000 description 5
- 238000010295 mobile communication Methods 0.000 description 5
- 230000001360 synchronised effect Effects 0.000 description 5
- 230000002159 abnormal effect Effects 0.000 description 4
- 239000013256 coordination polymer Substances 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 239000002699 waste material Substances 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000007774 longterm Effects 0.000 description 3
- 238000005259 measurement Methods 0.000 description 3
- XUIMIQQOPSSXEZ-UHFFFAOYSA-N Silicon Chemical compound [Si] XUIMIQQOPSSXEZ-UHFFFAOYSA-N 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 229910052710 silicon Inorganic materials 0.000 description 2
- 239000010703 silicon Substances 0.000 description 2
- 239000000758 substrate Substances 0.000 description 2
- 102100022734 Acyl carrier protein, mitochondrial Human genes 0.000 description 1
- 101000678845 Homo sapiens Acyl carrier protein, mitochondrial Proteins 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000002238 attenuated effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000012508 change request Methods 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000000670 limiting effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000002829 reductive effect Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 230000008054 signal transmission Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000005641 tunneling Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/24—Reselection being triggered by specific parameters
- H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
- H04W36/305—Handover due to radio link failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- 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
- 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/74—Address processing for routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real 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/12—Communication route or path selection, e.g. power-based or shortest path routing based on transmission quality or channel quality
-
- 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/248—Connectivity information update
-
- 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
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
- H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/14—Direct-mode setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/18—Interfaces between hierarchically similar devices between terminal devices
Definitions
- the present application relates to the field of communication technologies, and more particularly, to a communication method and related equipment.
- a radio link failure may occur in the radio link between the relay node and the parent node.
- RLF radio link failure
- the relay node will first try to restore the link.
- the relay node will send RLF indication information to its child nodes. It is used to indicate the occurrence of RLF to the child node, so that the child node can trigger the rerouting operation and transmit the data to be transmitted through other relay nodes.
- the original relay node succeeds in rerouting by itself, it will still send RLF indication information to its child nodes to trigger the child nodes to perform rerouting, which will cause unnecessary waste of link resources and overhead of air interface resources.
- the present application provides a communication method and related equipment, which can realize reasonable rerouting in the case of RLF.
- the present application provides a communication method, the method may include: when the first node determines that RLF occurs in the wireless link between the first node and the second node and there is no other available path between the first node and the destination node, the The first node will send the first indication information to the third node.
- the first indication information is used to indicate that the RLF is or is attempting link recovery.
- the second node is a parent node of the first node, and the third node is a child node of the first node; or, the second node is a child node of the first node, and the third node is the first node The parent node of the first node or the host node to which the first node is connected.
- exemplary beneficial effects include: the rerouting function of the relay node can be fully utilized, the stability of the data relay can be increased, and unnecessary waste of link resources and air interface signaling overhead can be avoided.
- the first node when the second node is the parent node of the first node and the third node is the child node of the first node, the first node is determining the wireless link between the first node and the second node.
- the first indication information is sent to the third node under the condition that RLF occurs on the path and the radio link recovery is attempted and it is determined that there is no other available path with the destination node.
- the first indication information is used to indicate that link recovery is being attempted.
- exemplary beneficial effects include: the rerouting function and link recovery function of the relay node can be fully utilized, the stability of data relay can be increased, and unnecessary waste of link resources and air interface signaling overhead can be avoided.
- the first node further sends second indication information to the third node, where the second indication information is used to indicate that the path from the first node to the destination node is unavailable.
- exemplary beneficial effects include: enabling the third node to obtain more accurate information about the RLF, thereby realizing more efficient and accurate rerouting.
- the second indication information includes a backhaul adaptation (Bakhaul Adaptation Protocol, BAP) layer address of the destination node.
- BAP Backhaul adaptation
- exemplary beneficial effects include: it can be indicated to the third node that all paths from the first node to the destination node are unavailable, so that the third node can achieve more efficient and accurate rerouting.
- the second indication information includes a routing identity (routing identity, routing ID) corresponding to the path from the first node to the destination node.
- the second indication information includes a path identity (path identity, path ID) corresponding to the path from the first node to the destination node.
- the second indication information is used to indicate that the path from the first node to the destination node is unavailable, including: the second indication information is used to indicate all paths from the first node to the destination node. are not available; or, the second indication information is used to indicate that in all the paths from the first node to the destination node, the paths whose corresponding path IDs are equal to the path IDs included in the second indication information are unavailable; or, the first The second indication information is used to indicate that in all the paths that pass through the first node to the destination node, the corresponding routing ID is equal to the routing ID included in the second indication information. The path is unavailable.
- exemplary beneficial effects include: indicating to the third node which paths between the first node and the destination node are unavailable, thereby enabling the third node to achieve more efficient and accurate rerouting.
- the second indication information includes the identifier of the second node.
- the second indication information is used to indicate that the path from the first node to the destination node is unavailable, including: the second indication information is used to indicate all paths from the first node to the destination node. , the path including the direct wireless link between the first node and the second node is unavailable.
- exemplary beneficial effects include: the host node (that is, the third node) receiving the identifier of the second node from the first node can accurately determine the occurrence of RLF, so that the third node can accurately determine the occurrence of RLF. Achieve more efficient and accurate rerouting.
- the present application provides a communication method, the method may include: receiving, at a third node, second indication information from a first node, where the second indication information is used to indicate a path to a destination node through the first node In the case of being unavailable, the third node determines to route the data to the destination node through other paths.
- the third node further receives first indication information from the first node, where the first indication information is used to indicate RLF or is attempting link recovery.
- the second indication information includes the BAP address of the destination node, or the routing ID corresponding to the path from the first node to the destination node, or the route ID from the first node to the destination node.
- the path identifier path identity, path ID
- the other path does not include the first node, or the routing ID of the other path is not equal to the routing ID included in the second indication information, or the Path ID of the other path is not equal to the second Path ID included in the indication.
- the second indication information includes an identifier of a second node, wherein the second node is a child node of the first node, and the wireless link between the first node and the second node has occurred. RLF.
- the routing ID of the other path is not equal to the routing ID corresponding to the path from the first node to the destination node that includes the direct wireless link between the first node and the second node.
- the third node when the third node receives third indication information from the first node, where the third indication information is used to indicate that the wireless link is successfully recovered, the third node stops using the method through rerouting. route data to the destination node through other paths.
- exemplary beneficial effects include: the third node can be made to stop rerouting in time, and the source path used before being notified of the RLF can be resumed to route data (or, in other words, the original routing configuration information can be resumed to route data. ), which can reduce the processing complexity of the upstream or downstream node of the third node.
- the present application provides a communication method, the method may include: a first node receives a first message from a master base station of a fourth node, where the first message is used to request to add the first node as the fourth node's Secondary base station.
- the first message includes: the physical cell identifier PCI of the cell of the second node accessed by the fourth node and the temporary radio network identifier C-RNTI of the cell of the fourth node in the cell of the second node, or, The identity of the third node and the identity of the fourth node on the interface between the third node and the first node.
- the third node is the source secondary base station of the fourth node, and the fourth node is the downstream node of the second node.
- the first node further acquires context information of the fourth node.
- exemplary beneficial effects include: since the context information of the fourth node is already cached on the first node, it can be avoided that the message sent by the primary base station to the first node further carries the context information of the fourth node, Thus, the air interface overhead is reduced.
- the C-RNTI enables the first node to obtain the context information of the fourth node according to the identity of the fourth node in the first message, and then makes itself a new secondary base station of the fourth node to provide services for the fourth node , to avoid data interruption of the fourth node.
- the method before receiving the first message, further includes: the first node receives a second message from the second node, where the second message is used for requesting to establish or re-establish a communication with the second node The radio resource control RRC connection. Afterwards, the first node sends a third message to the third node, where the third message is used to request to acquire context information related to the second node. Then, the first node receives a fourth message from the third node, the fourth message including contextual information related to the second node. The third node sends a fifth message to the second node, where the fifth message is used to establish or re-establish an RRC connection with the second node.
- the fifth message includes information for updating the cell served by the second node.
- the information for updating the cell served by the second node includes: when the second node is connected to the first node, the global cell identity CGI and/or cell identity of the cell of the second node cell identity.
- the context information related to the second node includes at least one of the following: context information of the second node, topology information between the second node and the fourth node, and information of the fourth node.
- the context information is indication information indicating whether the second node is a wireless backhaul device, or indication information indicating whether the fourth node is a wireless backhaul device.
- the context information of the fourth node includes the PCI and the C-RNTI.
- the context information of the fourth node includes an identifier of the third node and an identifier of the fourth node on the interface between the third node and the first node.
- the present application provides a communication method, the method may include: the master base station of the fourth node receives a sixth message from the third node, where the sixth message is used to request the first node as the fourth node's A target secondary base station, wherein the third node is the source secondary base station of the fourth node.
- the primary base station sends a first message to the first node, where the first message is used to request to add a secondary base station whose first node is the fourth node, wherein the first message includes the information accessed by the fourth node.
- the physical cell identifier PCI of the cell of the second node and the cell temporary radio network identifier C-RNTI of the fourth node in the cell of the second node, or the first message includes the identifier of the third node and the fourth node The identification of the node on the interface between the third node and the first node.
- exemplary beneficial effects include: the second node can be re-established from the source secondary base station to the destination secondary base station, thereby reducing the impact on the downstream node (fourth node) of the second node, ensuring that the second node The normal operation of downstream nodes.
- the present application provides a communication method, the method may include: the first node determines the first information. The first node determines whether to trigger rerouting according to the first information.
- the first node determines the first information by itself.
- the first information includes a first threshold value, and when the number of data packet transmission/retransmission times of the first node reaches/exceeds the first threshold value, the first node triggers rerouting.
- the first information includes the configuration of the timer, and the configuration of the timer includes the duration of the timer, then when the timer expires and the data packet of the first node has not been successfully sent, the first node triggers rerouting .
- the first node receives the first information from the third node.
- the first information includes a first threshold, and the first information is used to indicate that rerouting is triggered when the number of times of data packet transmission/retransmission of the first node reaches/exceeds the first threshold; or, the first
- the information includes the configuration of the timer, and the first information is used to indicate that when the timer expires and the data packet of the first node has not been successfully sent, rerouting is triggered.
- the first node determines whether to trigger uplink rerouting according to the first information, and the data packet of the first node is an uplink data packet.
- the third node may be a host node or an upstream node to which the first node is connected.
- the first node determines whether to trigger downlink rerouting according to the first information, and the data packet of the first node is a downlink data packet.
- the third node may be a host node connected to the first node.
- the data packets of the first node may be BAP layer/RLC layer/MAC layer/PHY layer data packets.
- the first threshold value needs to be smaller than the maximum retransmission threshold value of the RLC layer.
- the duration of the timer needs to satisfy: before the timer expires, the transmission/replay of the RLC layer data packet of the first node The number of transmissions is less than the maximum retransmission threshold of the RLC layer.
- the maximum retransmission threshold of the RLC layer can be used by the first node to judge whether a radio link failure occurs.
- the maximum retransmission threshold value of the RLC layer may be configured by the host node to the first node through an RRC message.
- the present application provides a communication method, the method may include: when the first node determines that the wireless link with all the second nodes is unavailable, the first node sends the first node to the third node. Instructions.
- the first indication information is used to indicate that the RLF is or is attempting link recovery.
- the second node is a child node of the first node, and the third node is a parent node of the first node or a host node connected to the first node; or, the second node is a parent node of the first node, The third node is a child node of the first node.
- the first node sends first indication information to the third node when it is determined that the wireless links with all the second nodes are unavailable, and in the case of attempting link recovery.
- the first indication information is used to indicate that link recovery is being attempted.
- the first node will also send second indication information to the third node, where the second indication information is used to indicate that the first node is unavailable, or is used to indicate that the first node communicates with all the third nodes. The channel between the two nodes is unavailable.
- the second indication information includes a backhaul adaptation protocol (Bakhaul Adaptation Protocol, BAP) address of the first node.
- BAP Backhaul adaptation protocol
- the second indication information includes an identifier of the second backhaul RLC channel, and the second backhaul RLC channel has a corresponding relationship with the first backhaul RLC channel.
- the first backhaul RLC channel is all backhaul RLC channels between the first node and the second node
- the second backhaul RLC channel is all backhaul RLC channels between the first node and the third node channel.
- the first node maps data from the first backhaul RLC channel to the second backhaul according to the correspondence between the second backhaul RLC channel and the first backhaul RLC channel RLC channel, or the first node maps data from the second backhaul RLC channel to the first backhaul RLC channel according to the corresponding relationship.
- the DU of the first node sends third indication information to the MT of the first node when RLF occurs in the radio link with all the second nodes, the third indication information Instructing the MT of the first node to send the first indication information to the third node.
- the first indication information is carried in the BAP control PDU or in the MAC CE.
- the present application provides a communication method.
- the method may include: when the first node determines that the first backhaul RLC channel with the second node is unavailable, the first node sends a message to the third node.
- first indication information is used to indicate that the second backhaul RLC channel between the first node and the third node is unavailable or that the backhaul RLC channel recovery is being attempted. There is a corresponding relationship between the second backhaul RLC channel and the first backhaul RLC channel.
- the second node is a child node of the first node
- the third node is a parent node of the first node or a host node connected to the first node; or, the second node is a parent node of the first node,
- the third node is a child node of the first node.
- the first node when the first node determines that the first backhaul RLC channel with the second node is unavailable and attempts to recover the backhaul RLC channel, the first node sends the first indication information to the third node .
- the first indication information is used to indicate that the RLC channel recovery is being attempted to be transmitted back.
- the first indication information includes the identifier of the second backhaul RLC channel
- the first node maps data from the first backhaul RLC channel to the second backhaul according to the correspondence between the second backhaul RLC channel and the first backhaul RLC channel RLC channel, or the first node maps data from the second backhaul RLC channel to the first backhaul RLC channel according to the corresponding relationship.
- the second node is located between the first node and the primary base station/host node of the first node, or between the first node and the secondary host node of the first node, or The second node is the primary base station/primary host node of the first node, or the second node is the secondary host node of the first node.
- the present application provides a communication device, the device comprising a module for performing any one of the methods of the first to seventh aspects and any design thereof.
- the present application provides a communication device, comprising a processor and a memory, the processor is coupled to the memory, and the processor is used to implement any one of the methods of the first to seventh aspects and any design thereof method.
- the present application provides a communication device, comprising at least one processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices other than the communication device and transmit to the processor or transfer signals from the processor
- the signal of the processor is sent to other communication devices other than the communication device, and the processor is used to implement any one of the methods of the first aspect to the seventh aspect and any one of its designs through a logic circuit or executing code instructions.
- the apparatus may be a chip or an integrated circuit in a node in any of the methods of the first to seventh aspects and any design thereof.
- the communication device may further include at least one memory, and the memory stores the related program instructions.
- the present application provides a communication device, the device having the function or operation of implementing any one of the methods of the above-mentioned first to seventh aspects and any of the methods in any design thereof, the function or The operations may be implemented by hardware, or by hardware executing corresponding software.
- the hardware or software includes one or more units (modules) corresponding to the above functions or operations, such as a transceiver unit and a processing unit.
- the present application provides a computer-readable storage medium, in which related program instructions are stored, and when the related program instructions are executed, the communication apparatus implements the first aspect to the The method of the seventh aspect and any method in any design thereof.
- the present application provides a computer program product, the computer program product includes related program instructions, when the related program instructions are executed, to implement the methods of the first to seventh aspects and any design thereof any of the methods.
- the present application further provides a chip for implementing any one of the methods of the first to seventh aspects and any design thereof.
- the present application provides a communication system, which includes at least one communication device in any of the eighth to eleventh aspects and any designs thereof.
- FIG. 1 is a schematic diagram of a possible communication system of the present application.
- FIG. 2 is a schematic diagram of an IAB host provided by an embodiment of the present application.
- FIG. 3 is a schematic diagram of a control plane protocol stack in an IAB network provided by an embodiment of the present application.
- FIG. 4 is a schematic diagram of a user plane protocol stack in an IAB network provided by an embodiment of the present application.
- FIG. 5 is a schematic diagram of an IAB node networking provided by an embodiment of the present application.
- 6A is a schematic diagram of a communication method provided by an embodiment of the present application.
- 6B is a schematic diagram of a communication method provided by an embodiment of the present application.
- 6C is a schematic diagram of a communication method provided by an embodiment of the present application.
- 6D is a schematic diagram of a communication method provided by an embodiment of the present application.
- 6E is a schematic diagram of a communication method provided by an embodiment of the present application.
- 6F is a schematic diagram of a communication method provided by an embodiment of the present application.
- FIG. 7 is a schematic diagram of a communication method provided by an embodiment of the present application.
- FIG. 8 is a schematic diagram of a communication method provided by an embodiment of the present application.
- FIG. 9 is a schematic block diagram of a communication device provided by an embodiment of the present application.
- FIG. 10 is a schematic block diagram of a communication device provided by an embodiment of the present application.
- FIG. 11 is a schematic block diagram of a communication device provided by an embodiment of the present application.
- FIG. 12 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application.
- FIG. 13 is a schematic block diagram of an apparatus provided by an embodiment of the present application.
- the fifth generation mobile communication (5G) or new radio (NR) system has put forward all the performance indicators of the network. More stringent requirements. For example, the capacity index has been increased by 1000 times, wider coverage requirements, ultra-high reliability and ultra-low latency, etc.
- the use of high-frequency small stations to form a network is becoming more and more popular. High-frequency carriers have poor propagation characteristics, are severely attenuated by occlusion, and have limited coverage, so a large number of small stations need to be densely deployed.
- the wireless backhaul device provides an idea for solving the above two problems: both the access link and the backhaul link use a wireless transmission scheme to avoid fiber deployment.
- the wireless backhaul device may be a relay node (Relay Node, RN), an integrated access backhaul (Integrated Access Backhaul, IAB) node, or other devices that provide wireless backhaul functions. This application does not limited.
- an IAB node as a wireless backhaul device, can provide wireless access services for user equipment (UE), and the service data of the UE is connected to the IAB node through a wireless backhaul link.
- the host node or the host base station transmits.
- Using an IAB node can share antennas for access and backhaul, reducing the number of antennas at the base station.
- the user equipment in FIG. 1 may be an access terminal equipment, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal equipment, a mobile equipment, a user terminal equipment, a wireless terminal equipment, a user agent, or a user equipment, etc. .
- It can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication capable Handheld devices, computing devices, other processing devices connected to wireless modems, in-vehicle devices, wearable devices (such as smart watches, smart bracelets, etc.), smart furniture or home appliances, terminal devices in 5G networks, future evolution Terminal equipment in public land mobile network (PLMN), or vehicle equipment in vehicle to everything (V2X), customer premises equipment (CPE), etc.
- PLMN public land mobile network
- V2X vehicle equipment in vehicle to everything
- CPE customer premises equipment
- the IAB node in Figure 1 may be composed of a mobile terminal (MT) and a distributed unit (DU), wherein, when the IAB node faces its parent node, it can be regarded as a terminal device, that is, an MT When an IAB node faces its subordinate device (the subordinate device may be another IAB sub-node, or a normal UE), it can be regarded as a network device, that is, it acts as a DU. It should be understood that each node in FIG. 1 only takes an IAB node as an example, and each of the IAB nodes can be replaced by a general relay node (relay node, RN).
- relay node relay node
- the IAB donor (IAB donor) in Figure 1 can be the donor base station, and the IAB donor can be referred to as DgNB (ie, donor gNodeB) for short in the 5G network.
- the IAB host can be a complete entity, or can be a centralized unit (CU) (referred to as Donor-CU or gNB-CU in this application) and a distributed unit (DU) (in this application) It exists in the form of separation of Donor-DU or gNB-DU for short.
- the IAB host can be a gNB located in a 5G radio access network (5G radio access network, 5G RAN).
- the IAB host may be composed of gNB-CU and gNB-DU.
- the gNB-CU and the gNB-DU are connected through an F1 interface, and the F1 interface may further include a control plane interface (F1-C) and a user plane interface (F1-U).
- the CU and the core network are connected through a next generation (NG) interface.
- the gNB-CU or Donor-CU may also be a user plane (UP) (referred to as CU-UP in this application) and a control plane (CP) (referred to as CU-CP in this application)
- UP user plane
- CP control plane
- CU-CP control plane
- One gNB-CU may include one gNB-CU-CP and at least one gNB-CU-UP.
- one Donor-CU may include one Donor-CU-CP and at least one Donor-CU-UP.
- the IAB node is connected to the core network via the IAB host.
- the IAB node is connected to the 5GC via the IAB host.
- the IAB node Under the dual connectivity (DC) or multi-connectivity (MC) 5G architecture (for example, non-standalone (NSA) or NR-NR DC scenarios, etc.), on the main path,
- the IAB node can be connected to an evolved packet core (EPC) via an evolved base station (evolved NodeB, eNB), or can be connected to a 5G core network via an IAB host.
- EPC evolved packet core
- eNB evolved NodeB
- the IAB network supports the networking of multi-hop IAB nodes and multi-connection IAB nodes. Therefore, there may be multiple transmission paths between the terminal and the IAB host.
- On a path there is a definite hierarchical relationship between the IAB nodes and between the IAB nodes and the IAB hosts connected to the IAB nodes, and each IAB node regards the node that provides backhaul services for it as a parent node. Accordingly, each IAB node can be regarded as a child node of its parent node.
- the parent node of IAB node 1 is the IAB host
- IAB node 1 is the parent node of IAB node 2 and IAB node 3
- both IAB node 2 and IAB node 3 are the parent nodes of IAB node 4
- the parent node of IAB node 5 is IAB node 2.
- the uplink data packets of the terminal may be transmitted to the IAB host via one or more IAB nodes, and the downlink data packets will be sent to the terminal by the IAB host via one or more IAB nodes.
- terminal 1 and IAB host There are two available paths for data packet transmission between terminal 1 and IAB host, namely: terminal 1 ⁇ IAB node 4 ⁇ IAB node 3 ⁇ IAB node 1 ⁇ IAB host, terminal 1 ⁇ IAB node 4 ⁇ IAB node 2 ⁇ IAB node 1 ⁇ IAB host.
- terminal 2 ⁇ IAB node 4 ⁇ IAB node 3 ⁇ IAB node 1 ⁇ IAB host terminal 2 ⁇ IAB node 4 ⁇ IAB node 2 ⁇ IAB Node 1 ⁇ IAB host, terminal 2 ⁇ IAB node 5 ⁇ IAB node 2 ⁇ IAB node 1 ⁇ IAB host.
- the IAB host In order to ensure the normal transmission of data between the terminal and the IAB host, the IAB host needs to configure a routing table for each IAB node, that is, configure next-hop nodes corresponding to different paths. At the same time, the IAB host needs to determine the transmission path corresponding to the data transmission. That is to say, a transmission path will be determined before data transmission. This transmission path can be called the main path. Data is routed between the terminal and the IAB host through this main path, and other paths can be regarded as Backup path. The backup path is used for re-routing only when the primary path is unavailable, eg, an RLF occurs on a link on the primary path.
- the main data transmission path of the IAB host configuration terminal 2 is: terminal 2 ⁇ IAB node 4 ⁇ IAB node 2 ⁇ IAB node 1 ⁇ IAB host, when IAB node 2 detects the connection between IAB node 1 and IAB node 1 When RLF occurs and the link cannot be recovered, the IAB node 2 sends an RLF indication message to the IAB node 4.
- the IAB node 4 can trigger data re-routing, and the uplink data received from the terminal 2 Temporarily transmit through the backup path, namely: terminal 2 ⁇ IAB node 4 ⁇ IAB node 3 ⁇ IAB node 1 ⁇ IAB host.
- a wireless link recovery (recovery) mechanism is introduced, that is, when an RLF occurs between two nodes, an attempt can be made to restore the wireless link between the two nodes.
- the IAB node 5 may attempt to perform radio link recovery, such as performing RRC re-establishment in other cells of the IAB node 2, etc., to restore the wireless link between IAB Node 5 and IAB Node 2.
- the intermediate IAB nodes on the upstream path from the IAB node to the IAB host can be called the upstream node of the IAB node.
- the IAB node 1 and IAB node 2 in Figure 1 can be called the upstream node of the IAB node 5.
- the intermediate IAB nodes on the downlink path from the IAB node to the terminal can be called the downstream nodes of the IAB node.
- IAB node 2, IAB node 3, IAB node 4 and IAB node 5 in FIG. 1 can be called IAB node 1.
- the downstream node includes child nodes, child nodes (or grandchild nodes) of child nodes, etc., where the downstream node can be other IAB nodes or terminals.
- the terminal 1 in FIG. 1 may be referred to as the downstream node of the IAB node 4, the IAB node 4 and the IAB node 5 may be referred to as the downstream nodes of the IAB node 1, and the terminal 1 and the terminal 2 may be referred to as the downstream nodes of the IAB node 1. downstream node.
- a transmission path between a terminal and an IAB host may include one or more IAB nodes.
- Each IAB node needs to maintain the wireless backhaul link facing the parent node, and also needs to maintain the wireless link with the child nodes. If the child node of the IAB node is a terminal, there is a wireless access link between the IAB node and the child node (ie, the terminal). If the child nodes of the IAB node are other IAB nodes, there is a wireless backhaul link between the IAB node and the child nodes (ie, other IAB nodes). Exemplarily, referring to FIG.
- terminal 1 accesses IAB node 4 through a wireless access link
- IAB node 4 accesses IAB node 4 through wireless
- the backhaul link is connected to the IAB node 3
- the IAB node 3 is connected to the IAB node 1 through the wireless backhaul link
- the IAB node 1 is connected to the IAB host through the wireless backhaul link.
- the above IAB networking scenario is just an example.
- the IAB host and the IAB nodes under another IAB host are composed Dual connections are terminal services, etc., which will not be listed here.
- the access IAB node in the embodiment of the present application refers to the IAB node accessed by the terminal, and the intermediate IAB node refers to the IAB node that provides wireless backhaul service for the terminal or the IAB node.
- IAB node 4 is the access IAB node
- IAB node 3 and IAB node 1 are intermediate IAB nodes.
- an IAB node is an access IAB node for a terminal that accesses the IAB node.
- IAB node 3 and IAB node 1 are intermediate IAB nodes.
- an IAB node is an access IAB node for a terminal that accesses the IAB node.
- an intermediate IAB node For a terminal that accesses other IAB nodes, it is an intermediate IAB node. Therefore, an IAB node is specifically an access IAB node.
- the node or the intermediate IAB node is not fixed and needs to be determined according to the specific application scenario.
- FIG. 3 and FIG. 4 are respectively a schematic diagram of a control plane protocol stack and a schematic diagram of a user plane protocol stack in an IAB network provided by an embodiment of the present application, which will be described below with reference to FIG. 3 and FIG. 4 .
- a Uu interface is established between the terminal 1 and the IAB2-DU, and the peer-to-peer protocol layers include the RLC layer, the MAC layer, and the PHY layer.
- the IAB2-DU and the IAB donor CU1 establish an F1-C interface, and the peer-to-peer protocol layers include the F1 application protocol (F1AP) layer and the stream control transmission protocol (SCTP) layer.
- the IAB donor DU 1 and the IAB donor CU 1 are connected by wire, and the peer-to-peer protocol layers include the Internet Protocol (IP) layer, L2 and L1.
- IP Internet Protocol
- BL is established between IAB node 2 and IAB node 3, between IAB node 3 and IAB node 1, and between IAB node 1 and IAB donor DU 1, and the peer-to-peer protocol layer includes the backhaul adaptation protocol (Bakhaul Adaptation). Protocol, BAP) layer, RLC layer, MAC layer and PHY layer.
- BAP backhaul adaptation protocol
- RLC backhaul adaptation protocol
- MAC media access control
- PHY PHY
- a peer-to-peer RRC layer and a PDCP layer are established between the terminal 1 and the IAB donor CU 1, and a peer-to-peer IP layer is established between the IAB2-DU and the IAB donor DU 1.
- control plane protocol stack of the IAB network is compared with the control plane protocol stack of the single air interface.
- the DU connected to the IAB node realizes the function of the gNB-DU of the single air interface (that is, establishing a peer RLC layer, MAC layer with the terminal). and the functions of the PHY layer, as well as the functions of the F1AP layer and SCTP layer that establish peering with the CU).
- the DU connected to the IAB node in the IAB network realizes the function of the single air interface gNB-DU; the IAB donor CU realizes the function of the single air interface gNB-CU.
- RRC messages are encapsulated and transmitted in F1AP messages between the access IAB node and the IAB donor CU.
- the terminal 1 encapsulates the RRC message in the PDCP protocol data unit (protocol data unit, PDU), and sends it to the IAB2-DU after being processed by the RLC layer, the MAC layer and the PHY layer in sequence.
- PDU protocol data unit
- IAB2-DU obtains PDCP PDU after processing by PHY layer, MAC layer and RLC layer in turn, encapsulates PDCP PDU in F1AP message, and obtains IP packet after processing by SCTP layer and IP layer in sequence
- IAB2-MT separates IP packet It is sent to IAB3-DU after being processed by BAP layer, RLC layer, MAC layer and PHY layer.
- the IAB3-DU is processed by the PHY layer, the MAC layer, the RLC layer and the BAP layer to obtain an IP packet, and then the IAB3-MT adopts an operation similar to the IAB2-MT to send the IP packet to the IAB1-DU.
- IAB1 -MT sends the IP packet to IAB donor DU 1.
- the IP packet is sent to the IAB donor CU 1, and the IAB donor CU 1 sequentially processes the IP packet through the SCTP layer, the F1AP layer and the PDCP layer to obtain the RRC message.
- the downstream direction is similar and will not be described here.
- a Uu interface is established between the terminal 1 and the IAB2-DU, and the peer-to-peer protocol layers include the RLC layer, the MAC layer, and the PHY layer.
- IAB2-DU and IAB donor CU 1 establish an F1-U interface, and the peer-to-peer protocol layers include the GPRS tunneling protocol for the user plane (GTP-U) layer, the user datagram protocol (user datagram protocol, UDP) layer.
- GTP-U GPRS tunneling protocol for the user plane
- UDP user datagram protocol
- the IAB donor DU 1 and the IAB donor CU 1 are connected through a wired connection, and the equivalent protocol layers include the IP layer, L2 and L1.
- BL is established between IAB node 2 and IAB node 3, between IAB node 3 and IAB node 1, and between IAB node 1 and IAB donor DU 1, and the peer-to-peer protocol layers include BAP layer, RLC layer, and MAC layer. and the PHY layer.
- a peer-to-peer SDAP layer and a PDCP layer are established between the terminal 1 and the IAB donor CU 1, and a peer-to-peer IP layer is established between the IAB2-DU and the IAB donor DU 1.
- the user plane protocol stack of the IAB network is compared with the user plane protocol stack of the single air interface.
- the DU of the IAB access node realizes the function of the single air interface gNB-DU; the IAB donor CU realizes the function of the single air interface gNB-CU.
- PDCP packets are encapsulated and transmitted in the GTP-U tunnel between the access IAB node and the IAB donor CU.
- the GTP-U tunnel is established on the F1-U interface.
- FIG. 3 and FIG. 4 describe the protocol stack in the IAB scenario shown in FIG. 1 as an example.
- an IAB node may have one or more roles, and the IAB node may have protocol stacks of the one or more roles; or, the IAB node may have a set of protocol stacks, and the protocol stack may Different roles are processed using the protocol layers corresponding to different roles.
- the following is an example of the protocol stack in which the IAB node has the one or more roles:
- the MT of the IAB node has the protocol stack of a common terminal, such as the protocol stack of the terminal 1 in FIG. 3 and FIG. 4 , that is, the RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer.
- the RRC message of the IAB node is encapsulated in the F1AP message between the parent node of the IAB node and the IAB donor CU; on the user plane, the PDCP data packet of the IAB node is encapsulated between the parent node of the IAB node and the IAB donor CU. transmitted in the GTP-U tunnel.
- the IAB node can still act as a common terminal, for example, transmit its own uplink and/or downlink data packets (such as OAM data packets) with the IAB donor, and perform measurement through the RRC layer and many more.
- uplink and/or downlink data packets such as OAM data packets
- the IAB node After the IAB node accesses the IAB network, the IAB node can provide access services for the terminal, thereby acting as an access IAB node. At this time, the IAB node has the protocol stack for accessing the IAB node, such as Figure 3 and Figure 3 The protocol stack of IAB node 2 in 4.
- the interface of the IAB node facing its parent node can have two sets of protocol stacks, one set is the protocol stack of the common terminal, and the other set is the protocol stack that provides backhaul services for the terminal (ie: access The protocol stack of the IAB node).
- the same protocol layer of the two sets of protocol stacks may be shared, for example, the two sets of protocol stacks correspond to the same RLC layer, MAC layer, PHY layer, or BAP layer.
- the IAB node After the IAB node accesses the IAB network, the IAB node can play the role of an intermediate IAB node. At this time, the IAB node has the protocol stack of the intermediate IAB node, such as IAB node 3 or IAB node 1 in Figure 3 and Figure 4 the protocol stack.
- the interface of the IAB node facing its parent node can have two sets of protocol stacks, one set is the protocol stack of the common terminal, and the other set is the protocol stack that provides the return service for the child IAB node (ie: The protocol stack of the intermediate IAB node).
- the same protocol layer of the two sets of protocol stacks may be shared, for example, the two sets of protocol stacks correspond to the same RLC layer, MAC layer, PHY layer, or BAP layer.
- the IAB node can assume the roles of the access IAB node and the intermediate IAB node at the same time.
- the IAB node can be the access IAB node for some terminals, and the intermediate IAB node for other terminals.
- the IAB node There may be three sets of protocol stacks, one set is the protocol stack of the above-mentioned common terminal, the other set is the protocol stack of the access IAB node, and the other set is the protocol stack of the intermediate IAB node.
- the same protocol layer of the three sets of protocol stacks may be shared, for example, the three sets of protocol stacks all correspond to the same RLC layer, MAC layer, PHY layer, or BAP layer.
- Figures 3 and 4 take the IAB network as an example.
- the contents of Figures 3 and 4 are also applicable to other types of relay networks other than the IAB network.
- the control plane protocol stack architecture of the relay network can be Referring to FIG. 3 , reference may be made to FIG. 4 for the user plane protocol stack architecture of the relay network.
- the IAB nodes in Figures 3 and 4 can be replaced by relays, for example, IAB node 2 can be replaced by relay node 2, IAB node 3 can be replaced by relay node 3, and IAB node 1 can be replaced by relay nodes 1.
- the IAB donor 1 can be replaced by the host node 1.
- the host node has CU and DU protocol stacks. The rest of the content is the same as that described in Figures 3 and 4. For details, please refer to the descriptions in Figures 3 and 4, which will not be repeated here. Repeat.
- the IAB network shown in FIG. 1 can be considered as a schematic diagram of an IAB independent networking, and the IAB network also supports a non-standalone (non-standalone, NSA) networking.
- Figure 5 shows a schematic diagram of the IAB non-independent networking.
- the IAB node supports dual connections of 4G and 5G networks, namely EN-DC (E-UTRAN NR dual connectivity), in which the LTE base station eNB is the master base station (master eNB, MeNB). ), provide LTE air interface (LTE Uu) connection for IAB node, and establish S1 interface with 4G core network evolved packet core (EPC) for user plane and control plane transmission.
- EN-DC E-UTRAN NR dual connectivity
- LTE base station eNB is the master base station (master eNB, MeNB).
- LTE Uu LTE air interface
- EPC 4G core network evolved packet core
- the IAB-donor is the secondary base station/secondary host node, which provides the NR air interface (NR Uu) connection for the IAB node, and establishes an S1 interface with the core network EPC for user plane transmission.
- the UE also supports EN-DC.
- the UE connects to the primary base station eNB through the LTE Uu interface, uses the NR Uu interface to access the IAB node, and connects to the secondary base station/secondary host node IAB donor through the IAB node.
- the IAB non-independent networking scenario in this application may also be referred to as the EN-DC networking scenario of the IAB.
- the secondary base station/secondary host node before the change can be called the source secondary base station/source secondary host node, and the changed secondary base station/secondary host node can be called as is the target secondary base station/target secondary host node.
- Figure 5 is only an example of networking, and the NSA scenario of the IAB network also supports multi-hop IAB networking.
- the UE in Figure 5 can be another IAB node, that is, the IAB node can use a multi-hop wireless backhaul link. Connect to the IAB donor, which is not limited in this application.
- the NSA scenario of the IAB network also supports NR-NR DC.
- the main base station eNB can also be the main host node IAB-donor, that is, the IAB node can also support 5G and 5G network dual connections.
- the MT of the IAB node may be abbreviated as IAB-MT
- the DU of the IAB node may be abbreviated as IAB-DU
- the CU of the IAB host may be abbreviated as Donor-CU
- the DU of the IAB host may be abbreviated as Donor-DU.
- the IAB host connected to the IAB node may be referred to as the IAB host of the IAB node for short.
- the IAB node may directly access the IAB host, or the IAB node may be connected to the IAB host through other IAB nodes.
- FIG. 6A shows a communication method 600A according to an embodiment of the present application.
- the first node may be a child node of the second node, and the first node is a parent node of the third node, and the destination node may be a host node.
- the first node may be the parent node of the second node, and the first node may be the child node of the third node, and the destination node may be the access node of the terminal device (also referred to as node to which the terminal device is connected).
- the terminal device also referred to as node to which the terminal device is connected.
- the second node may be located between the first node and the primary base station/host node of the first node, or between the first node and the secondary host node of the first node, or the The second node is the primary base station/primary host node of the first node, or the second node is the secondary host node of the first node.
- the primary base station/primary host node or the secondary host node can be understood with reference to the embodiment corresponding to FIG. 5 .
- At least one relay node may be included between the second node and the destination node, or the second node may also be directly connected to the destination node.
- the communication method 600A includes:
- S601A The first node sends the first indication information to the third node.
- the first indication information may be used to indicate that the wireless link is abnormal, for example, the first indication information may be used to indicate that the wireless link fails, or the first indication information may be used to indicate that link recovery is being attempted.
- the first node may send the first indication information to the third node when it is determined that RLF occurs in the wireless link with the second node.
- the first indication information may be used to indicate that the radio link fails.
- the first node may send the first indication information to the third node when it is determined that the radio link between the first node and the second node occurs RLF, and in the case of attempting radio link recovery (recovery) .
- the first indication information may be used to indicate that link recovery is being attempted.
- the first node may send the first indication to the third node when it is determined that RLF occurs on the wireless link with the second node and no other available paths exist between the first node and the destination node information.
- the first indication information may be used to indicate that the radio link fails.
- the first node may determine that RLF occurs on the wireless link between the first node and the second node, and try to recover the wireless link, and there is no other available path between the first node and the destination node. , and send the first indication information to the third node. At this time, the first indication information may be used to indicate that link recovery is being attempted.
- the first indication information may be carried in a backhaul adaptation protocol layer (backhaul adaptation protocol, BAP) control protocol data unit (control protocol data unit, control PDU) and sent.
- BAP backhaul adaptation protocol
- control protocol data unit control protocol data unit
- the third node after receiving the first indication information, performs re-routing (re-routing) on the data packet to be sent to the destination node.
- Rerouting the data packets to be sent to the destination node refers to routing data to the destination node through other paths.
- the other path may also be referred to as a backup path, that is, different from the original path through which the third node routed data to the destination node through the first node before the occurrence of RLF.
- the third node can trigger the rerouting function of the data packet after receiving the first indication information, and the data to be sent to the destination node.
- the packet is rerouted to route the data packet to the destination node through other available paths.
- the third node can receive the The first indication information can then trigger the rerouting operation of the data packet, and can fully utilize the rerouting function of the first node, thereby increasing the stability of the data relay and reducing the air interface signaling overhead. For example, there are multiple paths between the first node and the destination node.
- the first node When an RLF occurs on one of the paths, the first node itself can trigger the rerouting function, and use other paths to route data to the destination node. Sending the above-mentioned first indication information to the third node, otherwise, unnecessary rerouting by the third node may result in a waste of resources, and a large amount of the above-mentioned first indication information may also be transmitted over the air interface.
- this embodiment of the present application may further include the following operations:
- S603A The first node sends the second indication information to the third node.
- the second indication information is used to indicate that the path from the first node to the destination node is unavailable.
- the second indication information includes a BAP address (address) of the destination node.
- the BAP address of the destination node may refer to the BAP address of the Donor-DU; for downlink transmission, the BAP address of the destination node may refer to the BAP address of the access IAB node.
- the second indication information indicates that the path from the first node to the destination node is unavailable, which may mean that all paths from the first node to the destination node are unavailable.
- the second indication information includes a path identity (path identity, Path ID) corresponding to the path from the first node to the destination node, or a path from the first node to the destination node.
- Path ID corresponding to the path.
- the second indication information indicates that the path from the first node to the destination node is unavailable, which may refer to all the paths from the first node to the destination node, and the corresponding path ID is equal to the second indication The path for the path ID included in the information is not available.
- the second indication information includes a routing identity (routing identity, routing ID) corresponding to the path from the first node to the destination node, or a route from the first node to the destination node.
- the route ID corresponding to the path.
- the route identifier consists of the BAP address and path ID of the destination node.
- the second indication information may include one or more routing identifiers.
- the second indication information indicates that the path from the first node to the destination node is unavailable, which may refer to all the paths from the first node to the destination node, the corresponding routing ID is equal to the second indication
- the information includes the routing ID of the route is not available.
- the second indication information indicates that the path from the first node to the destination node is unavailable, which may mean that all paths from the first node to the destination node are unavailable.
- the third node receives the second indication information.
- the third node may determine to route data to the destination node through other paths according to the second indication information.
- the other path does not include the first node.
- the third node may determine to route data to the destination node through other paths according to the second indication information.
- the routing ID of the other path is not equal to the routing ID included in the second indication information. Or the other path does not include the first node.
- the third node may determine to perform re-routing (re-routing) only on the data packets to be sent to the destination node. That is, the third node can determine that the data packets to be sent to other destination nodes are not rerouted, and can still be routed through the first node.
- the host node may determine to route data to the destination node through other paths according to the second indication information.
- the path identifier of the other path is not equal to the Path ID included in the second indication information.
- first indication information and second indication information may be carried in the same message and sent to the third node, for example, carried in the same BAP control PDU.
- the first indication information and the second indication information may be the same indication information, that is, the indication information has both the function of the first indication information and the function of the second indication information.
- Operation S603A is an optional operation, that is, the first node may not send the second indication information to the third node. For example, after receiving the first indication information, the third node determines to route data to the destination node through other paths. The other path does not include the first node.
- the third node can obtain more accurate information about the RLF, thereby realizing more efficient and accurate rerouting.
- the third node may route data to the destination node through the first node, and route other data to other destination nodes through the first node. Further, there may be multiple path.
- the first indication information and the second indication information can enable the third node to perform more efficient and accurate rerouting.
- this embodiment of the present application may further include the following operations:
- S604A The first node sends third indication information to the third node.
- the third indication information is used to indicate that the radio link is recovered successfully.
- the first node successfully restores the link with the parent node for example: the first node successfully restores the link with the second node, or the first node is connected through the RRC re-establishment process. Enter the new parent node, and then send the third indication information to the third node.
- the third node receives the third indication information.
- the third node stops the rerouting function, that is, stops routing data to the destination node through other paths (backup paths), and continues to use the source path (that is, the original master path). path) to route the data to the destination node, for example: the third node continues to route the data to the first node, and the first node further routes the data to the destination node.
- the third node after receiving the third indication information, the third node does not stop the rerouting function, and continues to route data to the destination node through other paths (backup paths) until the IAB host configures a new route configuration.
- the third node can be made to stop rerouting (or turn off the rerouting function) in time, which can reduce the processing complexity of the upstream or downstream nodes of the third node.
- the first indication information may only be used to indicate a radio link failure.
- the first indication information may be used to indicate that the wireless link fails, or the first indication information may be used to indicate that the link is being attempted Road recovery.
- the first node, the second node or the third node may be an IAB node
- the host node may be an IAB host
- the access node of the terminal device may be an access IAB node
- FIG. 6B shows a communication method 600B according to an embodiment of the present application.
- the second node is an upstream node of the first node (for example, the second node is a parent node of the first node), and the second node is a parent node of the first node.
- the host node is the host node to which the first node and the second node are connected. At least one relay node may be included between the second node and the host node, or the second node may also be directly connected to the host node (it can be understood that the host node is the parent node of the second node).
- the embodiments of the present application may be applied to a scenario in which the first node sends an uplink data packet to a destination node through the second node, and the destination node may be a host node.
- the communication method 600B includes:
- S601B The second node sends the first information to the host node.
- the first information may include a first threshold value.
- the first information may be used to indicate that when the number of data packet transmission/retransmission times of the first node reaches/exceeds the first threshold value, uplink rerouting is triggered.
- the data packet of the first node may be any data packet of the BAP layer, the RLC layer, the MAC layer or the PHY layer.
- the first information may be used to indicate: when the number of times of transmission/retransmission of the BAP layer data packet (eg, BAP PDU) of the first node is greater than or equal to the first threshold, the uplink rerouting is triggered.
- the first information may be used to indicate that uplink rerouting is triggered when the number of times of transmission/retransmission of the RLC layer data packet (eg, RLC PDU) of the first node is greater than or equal to the first threshold.
- the first threshold value is smaller than the maximum retransmission threshold value of the RLC layer, and the maximum retransmission threshold value of the RLC layer can be used for the first node to judge whether RLF occurs in the link between the first node and the second node.
- the maximum retransmission threshold value of the RLC layer may be sent by the host node to the first node through an RRC message.
- the first information may be used to indicate that the number of times of transmission/retransmission of a MAC layer data packet (such as a MAC PDU, also called a transport block (transport block) TB) at the first node is greater than or equal to the first gate When the limit is reached, uplink rerouting is triggered.
- the first information may be used to indicate: when the number of times of transmission/retransmission of a PHY layer data packet (such as a code block group (code block group, CBG)) of the first node is greater than or equal to the first threshold value, Trigger upstream rerouting.
- a PHY layer data packet such as a code block group (code block group, CBG)
- the first information may include the configuration of the first timer, and the configuration of the first timer may include the duration of the first timer.
- the first information may be used to indicate that when the first timer expires and the data packet of the first node has not been successfully sent, uplink rerouting is triggered.
- the data packet of the first node may be any data packet of the BAP layer, the RLC layer, the MAC layer or the PHY layer.
- the first information may be used to indicate that: when the first timer expires (that is, the timing duration of the first timer reaches/exceeds the configured first timer duration), and the BAP layer of the first node When the data packet has not been successfully sent, upstream rerouting is triggered.
- the first information may be used to indicate that when the first timer expires and the RLC layer data packet of the first node has not been successfully sent, uplink rerouting is triggered.
- the duration of the first timer needs to satisfy: before the first timer expires, the number of times of transmission/retransmission of the RLC layer data packet of the first node is less than the maximum retransmission threshold of the RLC layer.
- the first information may be used to indicate that when the first timer expires and the MAC layer data packet of the first node has not been successfully sent, uplink rerouting is triggered.
- the first information may be used to indicate that when the first timer expires and the PHY layer data packet of the first node has not been successfully sent, uplink rerouting is triggered.
- the first node or the second node in this embodiment of the present application may be an IAB node (for example, the first node may be an access IAB node, and the second node may be an intermediate IAB node), and the host node may be an IAB host.
- the second node may send the first information to the CU hosted by the IAB through an RRC message or an F1AP message.
- S602B The host node sends the first information to the first node.
- the CU of the IAB host may send the first information to the MT of the first node through an RRC message, or the CU of the IAB host may send the first information to the DU of the first node through an F1AP message.
- This S601B is an optional step.
- the first information may be generated by the host node and sent to the first node.
- the second node may be optional, that is, the first node may be directly connected to the host node (that is, the host node is the parent node of the first node), and the host node generates the first node The information can then be sent directly to the first node.
- the first information may not need to be forwarded by the host node.
- the second node may carry the first information in a BAP control PDU or a media access control control element (media access control control element, MAC CE), through the communication between the first node and the second node.
- a wireless backhaul link is sent to the first node.
- the first information may be generated by the first node itself.
- the first node may generate the first information according to a protocol, or the first information may be pre-configured in the first node, or the first node may be based on the channel quality between the first node and the second node and other parameters to generate the first information.
- S603B The first node determines whether to trigger uplink rerouting according to the first information.
- the first information includes the first threshold, when the first node determines that the number of times of transmission/retransmission of the BAP layer/RLC layer/MAC layer/PHY layer data packet is greater than or equal to the first threshold When the value is set, upstream rerouting is triggered.
- the uplink rerouting when the first node detects that the number of times of transmission/retransmission of the BAP layer data packet is greater than or equal to the first threshold value, the uplink rerouting is triggered. Alternatively, when the first node detects that the number of times of transmission/retransmission of the RLC layer data packet is greater than or equal to the first threshold value, the uplink rerouting is triggered. Alternatively, when the first node detects that the number of times of transmission/retransmission of the MAC layer data packet is greater than or equal to the first threshold value, the uplink rerouting is triggered. Alternatively, when the first node detects that the number of times of transmission/retransmission of the uplink PHY layer data packet is greater than or equal to the first threshold value, the uplink rerouting is triggered.
- the first information includes the configuration of the first timer, when the first node determines that the first timer expires, and the BAP layer/RLC layer/MAC layer/PHY layer data of the first node When the packet has not been successfully sent, upstream rerouting is triggered.
- the first node may start the timer when the BAP layer/RLC layer/MAC layer/PHY layer data packet is transmitted for the first time, that is, the first timer starts timing.
- uplink rerouting is triggered.
- uplink rerouting is triggered.
- the first timer expires and the RLC layer data packet of the first node has not been successfully sent uplink rerouting is triggered.
- the first timer expires and the MAC layer data packet of the first node has not been successfully sent uplink rerouting is triggered.
- uplink rerouting is triggered.
- the number of times of transmission/retransmission of data packets at the BAP layer/RLC layer/MAC layer/PHY layer can be counted according to the granularity of the next-hop node or the next-hop link. That is, the number of times of transmission/retransmission of the BAP layer/RLC layer/MAC layer/PHY layer data packet may refer to the total transmission or total retransmission of the BAP layer/ The number of RLC layer/MAC layer/PHY layer data packets, or, the first node transmits or retransmits the BAP layer/RLC layer/ number of MAC layer/PHY layer packets).
- triggering uplink rerouting can be understood as: the first node routes to the host node through another path (that is, a backup path, and the backup path may not include the second node) or other nodes (that is, not the second node) data pack.
- the parent node of the first node is the second node, data packets are no longer routed to the host node through the second node; when the parent node of the first node is the host node, data packets are no longer routed directly to the host node. Bag.
- S604B The first node stops uplink rerouting.
- the first node Node stops upstream rerouting.
- the first node after the first node triggers uplink rerouting, and before the first node determines that an RLF occurs between the first node and the second node/host node, if the first node passes the measurement, it is determined that the first node is connected to the host node. If the link quality between the second node/host node is greater than the preset value, the first node can stop uplink rerouting.
- the first node After triggering the uplink rerouting, the first node starts a timer. When the timer expires and the first node has not yet determined that RLF occurs with the second node/host node, the first node may stop uplink rerouting.
- stopping the uplink rerouting can be understood as: the first node stops sending the host node to the host node through another path (that is, a backup path, and the backup path may not include the second node) or other nodes (that is, not the second node).
- For routing data continue to use the source path (ie, the original main path, where the main path includes the second node) or the second node to route data to the host node.
- the parent node of the first node is the second node
- the data packet continues to be routed to the host node through the second node; when the parent node of the first node is the host node, the data packet is continued to be routed directly to the host node.
- This S604B is an optional step.
- the first node may not stop uplink rerouting until the host node reconfigures a new uplink routing configuration for the first node.
- the first node can be made to perform more efficient and accurate rerouting.
- the first node can be configured to trigger rerouting flexibly under the configuration of the host node.
- the rerouting of the first node can be triggered in advance, thereby reducing the possible interruption of data transmission, thereby improving the stability of data transmission.
- FIG. 6C shows a communication method 600C according to an embodiment of the present application.
- the first node is the parent node of the second node.
- the first node is directly or indirectly connected to the host node, or the first node is the host node.
- the embodiments of the present application may be applied to a scenario where the first node sends a downlink data packet to the destination node through the second node.
- the destination node may be the access node of the terminal device.
- At least one relay node may be included between the second node and the destination node, or the second node may also be the parent node of the destination node, or the second node may also be the destination node (then the embodiment of the present application It can be applied to the scenario where the first node sends downlink data packets to the second node).
- the communication method 600C includes:
- S601C The host node sends the second information to the first node.
- the second information may include a second threshold value.
- the second information may be used to indicate that the downlink rerouting is triggered when the number of data packet transmission/retransmission times of the first node reaches/exceeds the second threshold value.
- the data packet of the first node may be any data packet of the BAP layer, the RLC layer, the MAC layer or the PHY layer.
- the second information may be used to indicate that the downlink rerouting is triggered when the number of times of transmission/retransmission of the BAP layer data packet of the first node is greater than or equal to the second threshold.
- the second information may be used to indicate that the downlink rerouting is triggered when the number of times of transmission/retransmission of the RLC layer data packet of the first node is greater than or equal to the second threshold value.
- the second threshold value is smaller than the maximum retransmission threshold value of the above-mentioned RLC layer, and the maximum retransmission threshold value of the RLC layer can be used for the first node to judge whether the link between the first node and the second node is wireless Link failed.
- the maximum retransmission threshold value of the RLC layer may be sent by the host node to the first node through an RRC message.
- the second information may be used to indicate that the downlink rerouting is triggered when the number of times of transmission/retransmission of the MAC layer data packet of the first node is greater than or equal to the second threshold value.
- the second information may be used to indicate that the downlink rerouting is triggered when the number of times of transmission/retransmission of the PHY layer data packet of the first node is greater than or equal to the second threshold value.
- the second information may include the configuration of the second timer, and the configuration of the second timer may include the duration of the second timer.
- the second information may be used to indicate that downlink rerouting is triggered when the second timer expires and the data packet of the first node has not been successfully sent.
- the data packet of the first node may be any data packet of the BAP layer, the RLC layer, the MAC layer or the PHY layer.
- the second information may be used to indicate that: when the second timer times out (that is, the timing duration of the second timer reaches/exceeds the configured second timer duration), and the BAP layer of the first node Downlink rerouting is triggered when the data packet has not been successfully sent.
- the second information may be used to indicate that when the second timer expires and the RLC layer data packet of the first node has not been successfully sent, downlink rerouting is triggered.
- the duration of the second timer needs to satisfy: before the second timer expires, the number of times of transmission/retransmission of the RLC layer data packet of the first node is less than the maximum retransmission threshold value of the RLC layer.
- the second information may be used to indicate that the downlink rerouting is triggered when the second timer expires and the MAC layer data packet of the first node has not been successfully sent.
- the second information may be used to indicate that the downlink rerouting is triggered when the second timer expires and the PHY layer data packet of the first node has not been successfully sent.
- the first node or the second node may be an IAB node (for example, the first node may be an intermediate IAB node, and the second node may be an access IAB node), and the host node is an IAB host.
- S601C may be that the CU hosted by the IAB sends the second information to the MT of the first node through an RRC message.
- the CU of the IAB host may send the second information to the DU of the first node through an F1AP message.
- the S601C is an optional step.
- the second information may be generated by the first node itself.
- the first node may generate the second information according to a protocol, or the second information may be pre-configured in the first node, or the first node may be based on the channel quality between the first node and the second node
- the second information is generated.
- the first node itself is the host node
- the first node includes the DU of the host node and the CU of the host node
- the second information may be sent by the CU of the host node to the DU of the host node, or by the host node.
- the DU of the node is generated by itself.
- S602C The first node determines whether to trigger downlink rerouting according to the second information.
- the second information includes the second threshold
- the first node determines that the number of times of transmission/retransmission of the BAP layer/RLC layer/MAC layer/PHY layer data packet is greater than or equal to the second threshold value, trigger downlink rerouting.
- the downlink rerouting is triggered.
- the downlink rerouting is triggered.
- the downlink rerouting is triggered.
- the downlink rerouting is triggered.
- the downlink rerouting is triggered.
- the downlink rerouting is triggered.
- the second information includes the configuration of the second timer, when the first node determines that the second timer expires, the BAP layer/RLC layer/MAC layer/PHY layer data packet has not been successfully sent , trigger downlink rerouting.
- the first node may start the timer when the BAP layer/RLC layer/MAC layer/PHY layer data packet is transmitted for the first time, that is, the second timer starts timing.
- downlink rerouting is triggered.
- the second timer expires and the RLC layer data packet of the first node has not been successfully sent.
- downlink rerouting is triggered.
- the second timer expires and the MAC layer data packet of the first node has not been successfully sent.
- downlink rerouting is triggered.
- the second timer expires and the PHY layer data packet of the first node has not been successfully sent.
- the number of times of transmission/retransmission of data packets at the BAP layer/RLC layer/MAC layer/PHY layer can be counted according to the granularity of the next-hop node or the next-hop link. That is, the number of times of transmission/retransmission of the BAP layer/RLC layer/MAC layer/PHY layer data packet may refer to the total transmission or total retransmission of the BAP layer/RLC layer/MAC layer/PHY from the first node to the second node layer data packets, or the total number of times the first node transmits or retransmits the BAP layer/RLC layer/MAC layer/PHY layer data packet in total on the link between the first node and the second node).
- triggering downlink rerouting can be understood as: the first node routes to the destination node through another path (that is, a backup path, and the backup path may not include the second node) or other nodes (that is, not the second node) data pack.
- S603C The first node stops downlink rerouting.
- the first node stops the downlink. Reroute.
- the first node after the first node triggers downlink rerouting and before the first node determines that an RLF occurs between the first node and the second node, if the first node passes the measurement or feedback from the second node (for example: PHY Layer channel quality information (channel quality information, CQI) feedback), determine that the link quality between the first node and the second node is greater than the preset value, then the first node can stop downlink rerouting.
- PHY Layer channel quality information channel quality information, CQI
- the first node After triggering downlink rerouting, the first node starts a timer. When the timer expires and the first node has not yet determined that RLF occurs between the first node and the second node, the first node may stop downlink rerouting.
- stopping downlink rerouting can be understood as: the first node stops sending the destination node through another path (that is, a backup path, and the backup path may not include the second node) or other nodes (that is, not the second node).
- the first node stops sending the destination node through another path (that is, a backup path, and the backup path may not include the second node) or other nodes (that is, not the second node).
- the source path ie, the original main path, where the main path includes the second node
- the second node to route data to the destination node.
- the S603C is an optional step.
- the first node may not stop downlink rerouting until the host node reconfigures a new downlink routing configuration for the first node.
- the first node may stop routing the data packet to the host node through the source path.
- the first node may stop routing the data packet to the destination node through the source path.
- the first node stopping routing the data packet to the destination node through the source path may specifically include at least one of the following: the BAP layer of the first node sends indication information to the RLC layer, where the indication information is used to instruct the RLC layer to perform re-establishment; or, The BAP layer of the first node sends indication information to the MAC layer, where the indication information is used to instruct the MAC layer to perform a reset (reset).
- the first node may not stop routing the data packet to the destination node through the source path.
- the first node may not stop routing the data packet to the destination node through the source path.
- the first node supports DC, MC or NSA functionality. After the first node triggers uplink/downlink rerouting, and before the first node determines that an RLF occurs between the first node and the second node, the first node routes data through both the backup path and the source path (for example, RLC layer or MAC layer retransmission data).
- the first information in the method 600B and the second information in the method 600C may be the same third information.
- the first threshold value and the second threshold value may be the same third threshold value, and the third information may be used to indicate that the number of data packet transmission/retransmission times at the first node reaches/exceeds the third threshold value.
- the threshold is three, rerouting is triggered.
- the configuration of the first timer and the configuration of the second timer may be the configuration of the same third timer.
- the third information may be used to indicate that the third timer expires and the first node's Rerouting is triggered when the packet has not been successfully sent. That is, the first node may determine whether to trigger uplink rerouting according to the third information, or determine whether to trigger downlink rerouting according to the third information. In this way, air interface signaling overhead can be saved.
- FIG. 6D shows a communication method 600D according to an embodiment of the present application.
- the first node may be a child node of the second node, and the first node may be a parent node of the third node, and the destination node may be a host node.
- the first node may be the parent node of the second node, and the first node may be the child node of the third node, and the destination node may be the access node of the terminal device (also referred to as the terminal the node to which the device is connected).
- At least one relay node may be included between the second node and the destination node, or the second node may also be directly connected to the destination node.
- the communication method 600D includes:
- S601D The first node sends the first indication information to the third node.
- the first indication information may be used to indicate that the wireless link is abnormal, for example, the first indication information may be used to indicate that the wireless link fails, or the first indication information may be used to indicate that link recovery is being attempted.
- the first node may determine that the wireless link between the first node and all the second nodes is unavailable (for example, RLF occurs on the wireless link, or the wireless link is congested, or the wireless link is due to traffic). control is unavailable, or the backhaul RLC channel between the first node and all second nodes is unavailable) (it can also be understood that the first node may be determining the first node and all child nodes or When the wireless links between all parent nodes are unavailable), the first indication information is sent to the third node.
- the wireless link between the first node and all the second nodes is unavailable (for example, RLF occurs on the wireless link, or the wireless link is congested, or the wireless link is due to traffic). control is unavailable, or the backhaul RLC channel between the first node and all second nodes is unavailable) (it can also be understood that the first node may be determining the first node and all child nodes or When the wireless links between all parent nodes are unavailable), the first indication information is sent to the third node.
- the DU part of the first node may send indication information to the MT of the first node when determining that the wireless links between the first node and all the second nodes are unavailable, the indication information indicating The MT of the first node sends the first indication information to the third node.
- the first node may be determining that the radio link between the first node and all second nodes is unavailable, and attempting radio link recovery (eg, when the second node is located at the first node). Between the main base station/main host node of the first node, or the second node is the main base station/main host node of the first node, it may be trying to recover the main cell group (master cell group, MCG).
- MCG master cell group
- the second node when the second node is located between the first node and the secondary host node of the first node or the second node is the secondary host node of the first node, it may be trying to secondary cell group ( In the case of secondary cell group, SCG) recovery (recovery process), the first indication information is sent to the third node. At this time, the first indication information may be used to indicate that link recovery is being attempted.
- SCG secondary cell group
- the DU part of the first node determines that the radio link between the first node and all the second nodes is unavailable, and in the case of trying to recover the radio link, to the MT of the first node Sending indication information, the indication information instructing the MT of the first node to send the first indication information to the third node.
- the first indication information may be carried in a backhaul adaptation protocol (BAP) control protocol data unit (control PDU) or a media access control control element (MAC CE) ) is sent.
- BAP backhaul adaptation protocol
- control PDU control protocol data unit
- MAC CE media access control control element
- the third node after receiving the first indication information, performs re-routing (re-routing) on the data packet to be sent to the destination node.
- Rerouting the data packets to be sent to the destination node refers to routing data to the destination node through other paths.
- the other path can also be called a backup path, that is, different from the situation where the wireless link between the first node and all the second nodes is unavailable, the third node routes to the destination node through the first node The original path of the data.
- the third node can trigger the rerouting function of the data packet after receiving the first indication information, to reroute the data packet to be sent to the destination node, and route the data packet to the destination through other available paths
- the node ensures the stability and timely reliability of data transmission.
- this embodiment of the present application may further include the following operations:
- S603D The first node sends the second indication information to the third node.
- the second indication information is used to indicate that the first node is unavailable.
- the second indication information includes an identifier of the first node, such as a BAP address (address) of the first node.
- the second indication information may be used to indicate that the channels between the first node and all the second nodes are unavailable.
- the second indication information includes an identifier of the second backhaul RLC channel, and the second backhaul RLC channel has a corresponding relationship with the first backhaul RLC channel.
- the first backhaul RLC channel is all backhaul RLC channels between the first node and the second node
- the second backhaul RLC channel is all backhaul RLC channels between the first node and the third node channel.
- the second backhaul RLC channel and the first backhaul RLC channel may be many possibilities for the correspondence between the second backhaul RLC channel and the first backhaul RLC channel, which is not limited in this application.
- a certain backhaul RLC channel among the second backhaul RLC channels may correspond to a certain one or more backhaul RLC channels among the first backhaul RLC channels, and a certain one of the first backhaul RLC channels
- the backhaul RLC channel may also correspond to one or more backhaul RLC channels in the second backhaul RLC channel.
- the first node maps data from the first backhaul RLC channel to the second backhaul RLC channel according to the correspondence between the second backhaul RLC channel and the first backhaul RLC channel, or the The first node may map the data from the second backhaul RLC channel to the first backhaul RLC channel according to the corresponding relationship.
- the correspondence between the wireless link and the backhaul RLC channel may be one-to-one, many-to-one, or one-to-many, which is not limited in this application.
- the third node receives the second indication information.
- the third node may determine to route data to the destination node through other paths (it may be understood as data that originally needs to be routed through the first node). The other path does not include the first node.
- the above-mentioned first indication information and second indication information may be carried in the same message and sent to the third node, for example, carried in the same BAP control PDU or MAC CE.
- the first indication information and the second indication information may be the same indication information, that is, the indication information has both the function of the first indication information and the function of the second indication information.
- Operation S603D is an optional operation, that is, the first node may not send the second indication information to the third node. For example, after receiving the first indication information, the third node determines to route data to the destination node through other paths. The other path does not include the first node.
- the third node can obtain more accurate information about the RLF, thereby realizing more efficient and accurate rerouting.
- the third node may route data to the destination node through the first node, and route other data to other destination nodes through the first node. Further, there may be multiple path.
- the first indication information and the second indication information can enable the third node to perform more efficient and accurate rerouting.
- this embodiment of the present application may further include the following operations:
- S604D The first node sends third indication information to the third node.
- the third indication information is used to indicate that the radio link is recovered successfully.
- the first node successfully restores the link with the second node for example, the first node successfully restores the link with a certain second node, or the first node successfully restores the link with a certain second node.
- the third node receives the third indication information.
- the third node stops the rerouting function, that is, stops routing data to the destination node through other paths (backup paths), and continues to use the source path (that is, the original master path). path) to route the data to the destination node, for example: the third node continues to route the data to the first node, and the first node further routes the data to the destination node.
- the third node after receiving the third indication information, the third node does not stop the rerouting function, and continues to route data to the destination node through other paths (backup paths) until the host node configures a new route configuration.
- the third node can stop rerouting (or turn off the rerouting function) in time, which can reduce the processing complexity of the upstream or downstream nodes of the third node.
- the first indication information may only be used to indicate a radio link failure.
- the first indication information may be used to indicate that the wireless link fails, or the first indication information may be used to indicate that the link is being attempted Road recovery.
- the first node, the second node or the third node may be an IAB node
- the host node may be an IAB host
- the access node of the terminal device may be an access IAB node
- FIG. 6E shows a communication method 600E according to an embodiment of the present application.
- the first node may be a child node of the second node, and the first node is a parent node of the third node, and the destination node may be a host node.
- the first node may be the parent node of the second node, and the first node may be the child node of the third node, and the destination node may be the access node of the terminal device (also referred to as node to which the terminal device is connected).
- the terminal device also referred to as node to which the terminal device is connected.
- the second node may be located between the first node and the primary base station/host node of the first node, or between the first node and the secondary host node of the first node, or the The second node is the primary base station/primary host node of the first node, or the second node is the secondary host node of the first node.
- the primary base station/primary host node or the secondary host node can be understood with reference to the embodiment corresponding to FIG. 5 .
- At least one relay node may be included between the second node and the destination node, or the second node may also be directly connected to the destination node.
- the communication method 600E includes:
- S601E The first node sends the first indication information to the third node.
- the first indication information may be used to indicate that the radio link is abnormal, for example, it may be used to indicate that the radio link fails, or it may be used to indicate that the backhaul RLC channel is unavailable (for example, RLF occurs on the backhaul RLC channel, or congestion occurs on the backhaul RLC channel). , or the backhaul RLC channel is unavailable due to flow control), or the backhaul RLC channel recovery is being attempted, or the path identified by the first routing ID is unavailable, or the path recovery is being attempted.
- the first node may be in a situation where it is determined that the first backhaul RLC channel with the second node is unavailable (for example, RLF occurs on the first backhaul RLC channel, or the first backhaul RLC channel is congested, Or, when the first backhaul RLC channel is unavailable due to flow control), the first indication information is sent to the third node.
- the DU part of the first node may send indication information to the MT of the first node when it is determined that the first backhaul RLC channel is unavailable, where the indication information instructs the MT of the first node to send the MT to the first node.
- the third node sends the first indication information.
- the first node may be determining that the first backhaul RLC channel is unavailable with the second node, and attempting to restore the backhaul RLC channel (eg, when the second node is located at the first node and Between the main base station/main host node of the first node, or the second node is the main base station/main host node of the first node, it may be trying to recover a master cell group (MCG).
- MCG master cell group
- the second node is located between the first node and the secondary host node of the first node or the second node is the secondary host node of the first node, it may be trying a secondary cell group (secondary cell group).
- the first indication information is sent to the third node.
- the DU part of the first node may send indication information to the MT of the first node when it determines that the first backhaul RLC channel is unavailable and attempts to recover the backhaul RLC channel, the indication information Instructing the MT of the first node to send the first indication information to the third node.
- the first indication information may include the identifier of the second backhaul RLC channel.
- the second backhaul RLC channel is a backhaul RLC channel between the first node and the third node. There is a corresponding relationship between the second backhaul RLC channel and the unavailable first backhaul RLC channel.
- the first backhaul RLC channel is a backhaul RLC channel that is unavailable between the first node and the second node. The correspondence between the second backhaul RLC channel and the unavailable first backhaul RLC channel may have many possibilities, which is not limited in this application.
- the second backhaul RLC channel may correspond to one or more of the unavailable first backhaul RLC channels, and the unavailable first backhaul RLC channel may also correspond to one or more of the second backhaul RLC channels correspond.
- the first node maps data from the first backhaul RLC channel to the second backhaul RLC channel according to the correspondence between the second backhaul RLC channel and the first backhaul RLC channel, or the The first node may map the data from the second backhaul RLC channel to the first backhaul RLC channel according to the corresponding relationship.
- the first node may send the first indication information to the third node when it is determined that the path identified by the first routing ID between the first node and the second node is unavailable.
- the DU part of the first node may send indication information to the MT of the first node when determining that the path identified by the first routing ID is unavailable, where the indication information instructs the MT of the first node to send a message to the MT of the first node.
- the third node sends the first indication information.
- the first node may be in determining that the path identified by the first routing ID between the second node is unavailable, and is attempting path recovery (eg, when the second node is located between the first node and the second node). Between the master base station/master host node of a node, or the second node is the master base station/master host node of the first node, it may be in the process of trying to recover the master cell group (MCG).
- MCG master cell group
- the second node when it is located between the first node and the secondary host node of the first node or the second node is the secondary host node of the first node, it can be a secondary cell group in an attempt to , SCG) in the case of recovery (recovery process), send the first indication information to the third node.
- the DU part of the first node may send indication information to the MT of the first node when determining that the path identified by the first routing ID is unavailable, and in the case of attempting to restore the path, the indication information indicates the The MT of the first node sends the first indication information to the third node.
- the first indication information may include a first routing ID.
- the first indication information may be carried in a BAP control PDU or a MAC CE and sent.
- the third node after receiving the first indication information, performs re-routing (re-routing) on the data packet to be sent to the destination node.
- Rerouting the data packets to be sent to the destination node refers to routing data to the destination node through other paths.
- the other path can also be called a backup path, that is, different from the situation before the first backhaul RLC channel is unavailable or the path identified by the first routing ID is unavailable, the third node sends the The original path of the destination node routing data.
- the first indication information is sent to the third node, then through the above operations S601E to S602E, the third node can trigger the rerouting function of the data packet after receiving the first indication information, The data packets that are about to be sent to the destination node are rerouted, and the data packets are routed to the destination node through other available paths.
- the third node can trigger the rerouting function of the data packet after receiving the first indication information, and is about to send it to the destination node.
- the data packets are rerouted, and the data packets are routed to the destination node through other available paths.
- the third node may determine, according to the second indication information, that routing to the destination node through other paths originally needs to be mapped to the second backhaul. Data of the transmitted RLC channel (that is, before the first backhaul RLC channel becomes unavailable, the third node will map the data to the second backhaul RLC channel for transmission). The other path does not include the first node or does not pass the second backhaul RLC channel.
- the third node may determine, according to the second indication information, to route the data to the destination node through other paths (exemplarily, the routing ID carried by the data). is equal to the first routing ID included in the second indication information).
- the routing ID of the other route is not equal to the first routing ID included in the second indication information.
- the third node can obtain more accurate information about the link abnormality, thereby realizing more efficient and accurate rerouting.
- this embodiment of the present application may further include the following operations:
- S603E The first node sends third indication information to the third node.
- the third indication information is used to indicate that the backhaul RLC channel or path is successfully recovered.
- the first node may send the third indication information to the third node in the case of successfully recovering the first backhaul RLC channel or the path identified by the first routing ID with the second node.
- the third node receives the third indication information.
- the third node stops the rerouting function, that is, stops routing data to the destination node through other paths (backup paths), and continues to use the second backhaul
- the RLC channel or the path identified by the first routing ID routes data to the destination node, for example, the third node continues to route the data to the first node, and the first node further routes the data to the destination node.
- the third node after receiving the third indication information, the third node does not stop the rerouting function, and continues to route to the destination node through other paths (backup paths) that originally need to be mapped to the second backhaul
- the data of the RLC channel or the carried routing ID is equal to the data of the first routing ID, until the IAB host configures a new routing configuration.
- the third node can stop rerouting (or close the rerouting function) in time, which can reduce the processing complexity of the upstream or downstream nodes of the third node.
- the first node, the second node or the third node may be an IAB node
- the host node may be an IAB host
- the access node of the terminal device may be an access IAB node
- FIG. 6F shows a communication method 600F according to an embodiment of the present application.
- the first node may be a child node of the second node, or the first node may be a parent node of the second node, or the first node may be a host node of the second node, the The first node may be located between the second node and the primary base station/host node of the second node, or between the second node and the secondary host node of the second node, or the first node is the first node.
- the primary base station/primary host node of the two nodes, or the first node is the secondary host node of the second node.
- the primary base station/primary host node or the secondary host node can be understood with reference to the embodiment corresponding to FIG. 5 .
- S601F The second node sends the first indication information to the first node.
- the first indication information may be used to indicate that the wireless link is abnormal, for example, the first indication information may be used to indicate that the wireless link fails, or the first indication information may be used to indicate that link recovery is being attempted, or the BAP PDU cannot be route.
- the two nodes determine that the first BAP PDU cannot be routed (for example, the first BAP PDU is congested in the first node, or the first BAP PDU has not been sent out in the first node for a preset period of time)
- the first indication information is sent to the first node.
- the DU part of the second node may send indication information to the MT of the second node when it is determined that the first BAP PDU cannot be routed, and the indication information instructs the MT of the second node to send the MT of the second node to the first BAP PDU.
- a node sends the first indication information.
- the first indication information may include a routing ID (routing ID) or a BAP address corresponding to the first BAP PDU.
- the routing ID or BAP address corresponding to the first BAP PDU may refer to the routing ID or BAP address carried in the BAP header of the first BAP PDU.
- the first node after receiving the first indication information, performs re-routing (re-routing) on the data packet to be sent to the destination node.
- Rerouting the data packets to be sent to the destination node refers to routing data to the destination node through other paths.
- the other path may also be referred to as a backup path, which is different from the original path through which the first node routed data to the destination node through the second node before receiving the first indication information.
- the first node may determine, according to the first indication information, to route the first BAP PDU to the destination node through other paths, and the BAP of the first BAP PDU is The routing ID or BAP address carried in the header.
- the second node is not included on the other path.
- the first node may determine, according to the first indication information, to route the first BAP PDU to the destination node through other paths, and the BAP header of the first BAP PDU is The routing ID or BAP address carried in .
- the routing ID of the other path is not equal to the routing ID included in the first indication information. Or the second node is not included on the other path.
- FIG. 7 shows a communication method 700 according to an embodiment of the present application.
- the first node is the parent node of the second node
- the host node is the host node connected to the first node.
- a node may be an access node for a terminal device.
- the communication method 700 includes:
- S701 The first node sends first indication information to the host node.
- the first indication information may be used to indicate a radio link failure.
- the first node may send the first indication information to the host node when it is determined that RLF occurs in the wireless link with the second node.
- the first indication information may be used to indicate that the radio link fails.
- the first node may send the first indication information to the host node when it is determined that RLF occurs on the wireless link with the second node and there is no other available path with the destination node. .
- the first indication information may be used to indicate that the radio link fails.
- the first indication information can be carried in the F1AP message, for example, in the user equipment context release request (UE Context Release Request) message.
- UE Context Release Request user equipment context release request
- the reason ( cause) field is set to radio link failure indication (RLF indication).
- the first indication information can also be carried in the BAP control PDU and sent to the host node in a hop-by-hop manner.
- S702 The host node receives the first indication information.
- the host node after receiving the first indication information, reroutes the data packet to be sent to the destination node.
- Rerouting the data packets to be sent to the destination node refers to routing data to the destination node through other paths. This other path may also be referred to as a backup path.
- the above operations S701 to S702 can cause the host node to receive the first indication information.
- the first indication information can then trigger the rerouting function of the data packet, that is, the data packet sent to the destination node is to be rerouted, and the data packet is routed to the destination node through other available paths.
- the first node sends the first indication information to the host node when RLF occurs on the wireless link with the second node and there is no other available path with the destination node, then pass The above operations S701 to S702 can enable the host node to trigger the rerouting operation of the data packet after receiving the first indication information, and can make full use of the rerouting function of the first node, thereby increasing the stability of the data relay and reducing the amount of time lost.
- Air interface signaling overhead For example, there are multiple paths between the first node and the destination node. When an RLF occurs on one of the paths, the first node can perform rerouting by itself, and use other paths to route data to the destination node.
- the host node sends the above-mentioned first indication information, otherwise, resources may be wasted due to unnecessary rerouting performed by the host node, and a large amount of the above-mentioned first indication information is transmitted over the air interface.
- this embodiment of the present application may further include the following operations:
- S703 The first node sends second indication information to the host node.
- the second indication information is used to indicate that the path from the first node to the destination node is unavailable.
- the second indication information includes a BAP address (address) of the destination node.
- the BAP address of the destination node may refer to the BAP address of the access IAB node.
- the second indication information indicates that the path from the first node to the destination node is unavailable, which may mean that all paths from the first node to the destination node are unavailable.
- the second indication information includes a path identifier (Path ID) corresponding to the path from the first node to the destination node, or the path from the first node to the destination node. Path ID.
- the second indication information indicates that the path from the first node to the destination node is unavailable, which may refer to all the paths from the first node to the destination node, and the corresponding path ID is equal to the second indication The path for the path ID included in the information is not available.
- the second indication information includes a routing ID corresponding to the path from the first node to the destination node, or a routing ID corresponding to the path from the first node to the destination node.
- the route identifier consists of the BAP address and path ID of the destination node.
- the second indication information may include one or more routing IDs.
- the second indication information indicates that the path from the first node to the destination node is unavailable, which may refer to all the paths from the first node to the destination node, the corresponding routing ID is equal to the second indication
- the information includes the routing ID of the route is not available. Or at this time, the second indication information indicates that the path from the first node to the destination node is unavailable, which may mean that all paths from the first node to the destination node are unavailable.
- the second indication information includes an identifier of the second node.
- the identifier of the second node may be the BAP address of the second node.
- the identifier of the second node may also be the identifier of the second node on the F1 interface between the second node and the host node, such as the F1 interface application layer protocol identity (F1 application protocol identity, F1AP ID).
- F1 interface application layer protocol identity F1 application protocol identity, F1AP ID
- the second indication information indicates that the path from the first node to the destination node is unavailable, which may refer to all the paths from the first node to the destination node, including the first node and the second node. The path between the direct wireless links is not available.
- the second indication information indicates that the path from the first node to the destination node is unavailable, which may mean that all paths from the first node to the destination node are unavailable.
- S704 The host node receives the second indication information.
- the host node may determine to route data to the destination node through other paths according to the second indication information.
- the other path does not include the first node.
- the host node may determine to route data to the destination node through other paths according to the second indication information.
- the routing ID of the other path is not equal to the routing ID included in the second indication information.
- the host node may determine that only the data packets to be sent to the destination node are to be rerouted. That is, the host node can determine that the data packets to be sent to other destination nodes are not rerouted, and can still be routed through the first node.
- the host node may determine to route data to the destination node through other paths according to the second indication information.
- the path identifier of the other path is not equal to the Path ID included in the second indication information.
- the host node may determine, according to the second indication information, to route data to the destination node through another path.
- the routing ID of other paths is not equal to the routing ID corresponding to the path from the first node to the destination node including the direct wireless link between the first node and the second node. Or the other path does not include the first node.
- the above-mentioned first indication information and second indication information may be carried in the same message and sent to the host node, for example, carried in the same F1AP message, for example, in the UE Context Release Request message. Alternatively, it is carried in the same BAP control PDU and sent to the host node in a hop-by-hop manner.
- Operations S703 and S704 are optional operations, that is, the first node may not send the second indication information to the host node. For example, after receiving the first indication information, the host node determines to route data to the destination node through other paths. The other path does not include the first node.
- the host node can obtain more accurate information about the RLF, thereby realizing more efficient and accurate rerouting.
- the host node may not only route data to the destination node through the first node, but also route other data to other destination nodes through the first node. Further, there may be multiple paths between the first node and the destination node. , in these cases, the first indication information and the second indication information can enable the host node to perform more efficient and accurate rerouting.
- the first node, the second node or the third node may be an IAB node
- the host node may be an IAB host
- the access node of the terminal device may be an access IAB node
- FIG. 8 shows a communication method 800 according to an embodiment of the present application.
- the first node is the parent node of the second node
- the host node is the host node connected to the first node.
- a node may be an access node for a terminal device.
- the communication method 800 includes:
- S801 The primary base station sends a first message to the first node.
- the first message is used to request to add the first node as the secondary base station of the second node.
- the first message is used to request to add the first node as the secondary base station of the fourth node.
- the master base station may send the first message to the first node after receiving the sixth message from the third node.
- the third node is the source secondary base station of the second node or the fourth node.
- the sixth message is used to request the first node to be the target secondary base station of the second node or the fourth node.
- the sixth message may include the identifier of the first node.
- the identity of the first node may be a base station identity (gNB ID) of the first node.
- the master base station may be an LTE master base station (master eNodeB, MeNB).
- the secondary base station may be an NR secondary base station (secondary gNodeB, SgNB).
- the primary base station may also be an NR primary base station, and the secondary base station may be an NR secondary base station.
- the first message when the first message is used to request to add a secondary base station in which the first node is a second node, the first message includes a physical cell identifier (physical cell) of a cell of a third node accessed by the second node. identity, PCI) and the cell radio network temporary identifier (cell radio network temporary identifier, C-RNTI) of the second node in the cell of the third node.
- the second node is the third node and is the downstream node.
- the second node may be a child node of the third node, or may be a child node of the child node of the third node.
- the second node may be a wireless backhaul device or a terminal.
- the cell of the third node accessed by the second node may refer to a cell provided by the third node and used to serve the fourth node.
- the first message when the first message is used to request to add a secondary base station in which the first node is the second node, the first message includes the identifier of the third node and the location of the second node in the third node and the second node.
- the identity of the third node may be a base station identity (eg, gNB ID) of the third node.
- the interface between the third node and the first node may be an X2 interface, and the identifier of the second node on the interface between the third node and the first node may be that the third node is the second node
- the user application protocol identity (UE X2 Application Protocol identity, UE X2AP ID) allocated on the X2 interface may also be the UE X2AP ID allocated by the first node to the second node on the X2 interface, or the UE X2AP ID.
- the third node is the UE X2AP ID allocated by the second node on the X2 interface and the first node is the UE X2AP ID allocated by the second node on the X2 interface.
- the interface between the third node and the first node may be an Xn interface
- the identifier of the second node on the interface between the third node and the first node may be that the third node is the first node
- the user application protocol identifier (UE Xn Application Protocol identity, UE XnAP ID) allocated by the second node on the Xn interface can also be the UE X2AP ID allocated by the first node to the second node on the Xn interface, or it can be It is the UE X2AP ID allocated by the third node on the Xn interface for the second node and the UE X2AP ID allocated by the first node on the Xn interface for the second node.
- the first message when the first message is used to request to add a secondary base station in which the first node is a fourth node, the first message includes a physical cell identifier (physical cell) of the cell of the second node accessed by the fourth node. identity, PCI) and the cell radio network temporary identifier (cell radio network temporary identifier, C-RNTI) of the fourth node in the cell of the second node.
- the fourth node is that the second node is a downstream node.
- the fourth node may be a child node of the second node, or may be a child node of a child node of the second node.
- the fourth node may be a wireless backhaul device or a terminal.
- the cell of the second node accessed by the fourth node may refer to a cell provided by the second node and used to serve the fourth node.
- the first message when the first message is used to request to add a secondary base station in which the first node is the fourth node, the first message includes the identifier of the third node and the location of the fourth node in the third node and the fourth node. An identifier on an interface between nodes.
- the identity of the third node may be a base station identity (eg, gNB ID) of the third node.
- the interface between the third node and the first node may be an X2 interface, and the identification of the fourth node on the interface between the third node and the first node may be that the third node is the fourth node
- the user application protocol identifier (UE X2 Application Protocol identity, UE X2AP ID) allocated on the X2 interface may also be the UE X2AP ID allocated by the first node to the fourth node on the X2 interface, or the UE X2AP ID.
- the third node is the UE X2AP ID allocated by the fourth node on the X2 interface and the first node is the UE X2AP ID allocated by the fourth node on the X2 interface.
- the interface between the third node and the first node may be an Xn interface
- the identification of the fourth node on the interface between the third node and the first node may be that the third node is the first node
- the user application protocol identity (UE Xn Application Protocol identity, UE XnAP ID) allocated by the four nodes on the Xn interface can also be the UE X2AP ID allocated by the first node to the fourth node on the Xn interface, or it can be It is the UE X2AP ID allocated by the third node for the fourth node on the Xn interface and the UE X2AP ID allocated by the first node for the fourth node on the Xn interface.
- the first message may be a secondary base station addition request (such as SgNB addition request) message, or a secondary base station modification request (such as SgNB modification request) message.
- the second message may be a secondary base station change request (eg SgNB change required)
- the first node after receiving the first information, obtains the context information of the second node.
- the first node may extract the context information of the second node from the internal cache according to the identifier of the second node in the first message.
- the first node after receiving the first information, obtains the context information of the fourth node.
- the first node may extract the context information of the fourth node from the internal cache according to the identifier of the fourth node in the first message.
- the context information of the second node or the fourth node cached on the first node may be obtained in advance from the third node and cached on the first node through the following operations:
- S803 The first node receives the second message from the second node.
- the second message is used to request to establish or re-establish a radio resource control (radio resource control, RRC) connection with the second node.
- RRC radio resource control
- the second message may be an RRC reestablishment request message (eg, RRC reestablishment request).
- the second node may send the second message to the first node when RLF occurs on the radio link between it and the third node.
- a scenario in which the second node is directly connected to the first node is used as an example for description.
- This embodiment is also applicable to a scenario in which the second node is connected to the first node through at least one other wireless backhaul device, that is, the second node sends the second message to the first node through at least one other wireless backhaul device.
- S804 The first node sends a third message to the third node.
- the third message is used to request to obtain context information related to the second node.
- the third message may be a request message for obtaining user equipment context (eg retrieve UE context request).
- S805 The first node receives the fourth message from the third node.
- the fourth message includes contextual information related to the second node.
- the fourth message may be a retrieve UE context response message (retrieve UE context response).
- the context information related to the second node includes at least one of the following: context information of the second node, topology information between the second node and its downstream nodes, context information of the downstream nodes of the second node, indicating the first node. Indication information indicating whether the second node is a wireless backhaul device, or indication information indicating whether the downstream node of the second node is a wireless backhaul device.
- the downstream node of the second node includes a child node of the second node, a child node of the child node, etc., and may be a wireless backhaul device or a terminal.
- the downstream node of the second node may refer to the fourth node.
- the context information of the downstream node of the second node includes the PCI and the C-RNTI, or the context information of the downstream node of the second node includes the identifier of the third node and the relationship between the third node and the third node of the downstream node. An identifier on an interface between nodes.
- the context information of the second node may include the context of the MT part of the IAB node, and/or the context of the DU part of the IAB node.
- the context of the MT part of the IAB node includes configuration information of a backhaul radio link control channel (backhaul RLC channel, BH RLC CH).
- backhaul RLC channel backhaul RLC channel, BH RLC CH.
- the context of the DU part of the IAB node includes the identity of the IAB-DU, the configuration of the IAB-DU cell, and the like.
- the topology information between the second node and the downstream node of the second node may include indicating that the downstream node of the second node is a terminal device, and/or indicating that the downstream node of the second node is a terminal device.
- Wireless backhaul device may include indicating that the downstream node of the second node is a terminal device, and/or indicating that the downstream node of the second node is a terminal device.
- the first node may acquire the context information of the fourth node, and the first node may cache the context information of the fourth node locally, so that the primary base station that receives the fourth node sends the information After the first message of the first message, according to the identifier of the fourth node carried in the first message, the context information of the fourth node is extracted from the cache.
- this embodiment of the present application may further include the following operations:
- S806 The first node sends a fifth message to the second node.
- the fifth message is used to establish or re-establish an RRC connection with the second node.
- the fifth message may be an RRC reestablishment message (eg, RRC reestablishment).
- the fifth message may include information for updating the cell served by the second node.
- the information for updating the cell served by the second node may include a cell global identifier (CGI) and/or a cell identity of the cell when the second node is connected to the first node.
- the cellidentity may be composed of a base station identifier (such as a gNB Id) and a cell local identifier (cell local identifier, cellLocalId).
- the CGI consists of a cell global identifier, which consists of a public land mobile network identifier (PLMNId), a base station identifier (such as a gNB Id), and a cellLocalId.
- the first node allocates a new CGI and/or cellidentity to the cell served by the second node, and sends the new CGI and/or cellidentity to the second node through a fifth message.
- the base station identity eg gNB ID
- the base station identity contained in the new CGI and/or cellidentity of the cell served by the second node is the same as the base station identity to which the first node belongs.
- the fifth message may not only be used to establish or re-establish an RRC connection with the second node, but also include the information used to update the cell served by the second node.
- S806 can be before S801 and S802, or before S801 and after S802, or after S801 and S802.
- a scenario in which the second node is directly connected to the first node is used as an example for description.
- This embodiment is also applicable to a scenario in which the second node is connected to the first node through at least one other wireless backhaul device, that is, the second node sends the second message to the first node through at least one other wireless backhaul device.
- the second node in the scenario where RLF occurs on the second node, the second node can be re-established from the source secondary base station to the new secondary base station, thereby reducing the impact on the downstream nodes of the second node and ensuring the second node's The normal operation of downstream nodes.
- FIG. 9 is a schematic block diagram of a communication apparatus 900 provided by an embodiment of the present application. The structure and functions of the communication apparatus 900 will be described in detail below with reference to FIG. 9 .
- the communication apparatus 900 may include a processing module 901 and a sending module 902 .
- a processing module 901 configured to determine that a radio link failure RLF occurs in the radio link with the second node, and there is no other available path with the destination node;
- a sending module 902 configured to send first indication information to a third node, where the first indication information is used to indicate RLF or is trying to link recovery;
- the second node is a parent node of the first node, and the third node is a child node of the first node; or, the second node is a child node of the first node, and the third node is a child node of the first node.
- the three nodes are the parent node of the first node or the host node to which the first node is connected.
- the sending module 902 is specifically configured to: attempt radio link recovery At the time, first indication information is sent to the third node, where the first indication information is used to indicate that link recovery is being attempted.
- the sending module 902 is further configured to send second indication information to the third node, where the second indication information is used to indicate that the path from the first node to the destination node is unavailable.
- the second indication information includes a backhaul adaptation layer BAP address of the destination node, or a routing ID corresponding to the path from the first node to the destination node, or, through all The path identifier path ID corresponding to the path from the first node to the destination node.
- the second indication information is used to indicate that the path from the first node to the destination node is unavailable, including: the second indication information is used to indicate that the path from the first node to the destination node is unavailable. All paths are unavailable; or, the second indication information is used to indicate that among all the paths passing through the first node to the destination node, the path whose corresponding path ID is equal to the path ID included in the second indication information is unavailable Or, the second indication information is used to indicate that in all the paths that pass through the first node to the destination node, the path whose corresponding routing ID is equal to the routing ID included in the second indication information is unavailable.
- the second indication information includes the information of the second node. logo.
- the second indication information is used to indicate that the path from the first node to the destination node is unavailable, including: the second indication information is used to indicate that all the paths from the first node to the destination node are not available. Among the paths, the path including the direct wireless link between the first node and the second node is unavailable.
- FIG. 10 is a schematic block diagram of a communication apparatus 1000 provided by an embodiment of the present application. The structure and functions of the communication apparatus 1000 will be described in detail below with reference to FIG. 10 .
- the communication apparatus 1000 may include a processing module 1001 and an acquisition module 1002 .
- an obtaining module 1002 configured to receive second indication information from the first node, where the second indication information is used to indicate that the path from the first node to the destination node is unavailable;
- the processing module 1001 is configured to determine to route data to the destination node through other paths.
- the obtaining module 1002 is further configured to receive first indication information from the first node, where the first indication information is used to indicate RLF or link recovery is being attempted.
- the second indication information includes a backhaul adaptation layer BAP address of the destination node, or a routing ID corresponding to the path from the first node to the destination node, or, through all The path identifier path ID corresponding to the path from the first node to the destination node.
- the other path does not include the first node, or the routing ID of the other path is not equal to the routing ID included in the second indication information, or the Path ID of the other path is not equal to the The Path ID included in the second indication information.
- the second indication information includes an identifier of a second node, where the second node is a child node of the first node, and the wireless link between the first node and the second node occurs. RLF.
- the routing ID of the other path is not equal to that including the direct wireless link between the first node and the second node, and the path corresponding to the path from the first node to the destination node. routing ID.
- the obtaining module 1002 is further configured to receive third indication information from the first node, where the third indication information is used to indicate that the wireless link is successfully restored;
- the processing module 1001 is further configured to stop routing data to the destination node through the other paths.
- FIG. 11 is a schematic block diagram of a communication apparatus 1100 provided by an embodiment of the present application. The structure and functions of the communication apparatus 1100 will be described in detail below with reference to FIG. 11 .
- the communication apparatus 1100 may include an obtaining module 1101 and a processing module 1102, and optionally, may further include a sending module 1103.
- an obtaining module 1101 configured to receive a first message from the primary base station of the fourth node, where the first message is used to request to add the first node as the secondary base station of the fourth node;
- the first message includes: the physical cell identifier PCI of the cell of the second node accessed by the fourth node and the temporary wireless network identifier C- of the cell of the fourth node in the cell of the second node RNTI; or, the identity of the third node and the identity of the fourth node on the interface between the third node and the first node; wherein the third node is the source of the fourth node a secondary base station, where the fourth node is a downstream node of the second node;
- the processing module 1102 is configured to acquire the context information of the fourth node.
- the obtaining module 1101 is further configured to receive a second message from the second node, where the second message is used to request to establish or re-establish a relationship with the second node.
- the fifth message includes information for updating the cell served by the second node.
- the information for updating the cell served by the second node includes: when the second node is connected to the first node, the global cell identifier CGI of the cell of the second node and/or Cell identity cell identity.
- the context information related to the second node includes at least one of the following: context information of the second node, topology information between the second node and the fourth node, the fourth node The context information of the node, the indication information indicating whether the second node is a wireless backhaul device, or the indication information indicating whether the fourth node is a wireless backhaul device.
- the context information of the fourth node includes: the PCI and the C-RNTI; or, the identifier of the third node and the information of the fourth node between the third node and the first node An identifier on an interface between nodes.
- FIG. 12 is a schematic block diagram of a communication apparatus 1200 provided by an embodiment of the present application. The structure and functions of the communication apparatus 1200 will be described in detail below with reference to FIG. 12 .
- the communication apparatus 1200 may include an obtaining module 1201 and a sending module 1202.
- the obtaining module 1201 is configured to receive a sixth message from a third node, where the sixth message is used to request that the first node be used as a target secondary base station of the fourth node, wherein the third node is the third node Four-node source and secondary base station;
- a sending module 1202 configured to send a first message to the first node, where the first message is used to request to add a secondary base station whose first node is the fourth node, wherein the first message includes: the physical cell identifier PCI of the cell of the second node accessed by the fourth node and the temporary radio network identifier C-RNTI of the cell of the fourth node in the cell of the second node; or, the third node and the identity of the fourth node on the interface between the third node and the first node.
- an embodiment of the present application further provides an apparatus 1300 , and the structure and function of the apparatus 1300 will be described in detail below with reference to FIG. 13 , a schematic block diagram of the apparatus 1300 .
- the apparatus may include at least one processor 1301.
- an interface circuit 1302 is also included.
- the apparatus 1300 can be made to implement the communication method provided in any of the foregoing embodiments and any of the possible designs.
- the processor 1301 is used to implement the communication method and any possible design provided by any of the foregoing embodiments through logic circuits or executing code instructions.
- the interface circuit 1302 can be used to receive program instructions and transmit them to the processor, or the interface circuit 1302 can be used for the apparatus 1300 to communicate and interact with other communication devices, such as interactive control signaling and/or service data.
- the interface circuit 1302 can be used to receive signals from other devices other than the device 1300 and transmit to the processor 1301 or send signals from the processor 1301 to other communication devices other than the device 1300 .
- the interface circuit 1302 may be a code and/or data read/write interface circuit, or the interface circuit 1302 may be a signal transmission interface circuit between the communication processor and the transceiver.
- the communication apparatus 1300 may further include at least one memory 1303, and the memory 1303 may be used to store required program instructions and/or data.
- the apparatus 1300 may further include a power supply circuit 1304, and the power supply circuit 1304 may be used to supply power to the processor 1301.
- the power supply circuit 1304 may be located in the same chip as the processor 1301, or may be located where the processor 1301 is located. outside the chip inside another chip.
- the apparatus 1300 may further include a bus 1305 , and various parts of the apparatus 1300 may be interconnected through the bus 1305 .
- the processor in the embodiment of the present application may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), application-specific integrated circuits (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, etc.
- a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
- the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
- the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
- Volatile memory may be random access memory (RAM), which acts as an external cache.
- RAM random access memory
- SRAM static random access memory
- DRAM dynamic random access memory
- DRAM synchronous dynamic random access memory
- SDRAM double data rate synchronous dynamic random access memory
- double data rate SDRAM double data rate SDRAM
- DDR SDRAM enhanced synchronous dynamic random access memory
- ESDRAM Synchronous link dynamic random access memory
- direct rambus RAM direct rambus RAM, DR RAM
- the power supply circuit described in the embodiments of the present application includes, but is not limited to, at least one of the following: a power supply line, a power supply subsystem, a power management chip, a power consumption management processor, or a power consumption management control circuit.
- the transceiver device, the interface circuit, or the transceiver described in the embodiments of the present application may include a separate transmitter and/or a separate receiver, or the transmitter and the receiver may be integrated.
- Transceiver devices, interface circuits, or transceivers may operate under the direction of a corresponding processor.
- the transmitter may correspond to the transmitter in the physical device
- the receiver may correspond to the receiver in the physical device.
- the disclosed system, apparatus and method may be implemented in other manners.
- the device embodiments described above are only illustrative.
- the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods.
- multiple units or components may be combined. Either it can be integrated into another system, or some features can be omitted, or not implemented.
- the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
- “implemented by software” may mean that the processor reads and executes the program instructions stored in the memory to realize the functions corresponding to the above modules or units, wherein the processor refers to a processing circuit with the function of executing program instructions, Including but not limited to at least one of the following: central processing unit (CPU), microprocessor, digital signal processing (DSP), microcontroller (MCU), or artificial intelligence processing Various types of processing circuits that can run program instructions, such as a processor. In other embodiments, the processor may also include circuits for other processing functions (eg, hardware circuits for hardware acceleration, bus and interface circuits, etc.).
- the processor may be presented in the form of an integrated chip, for example, in the form of an integrated chip whose processing function only includes the function of executing software instructions, or in the form of a system on a chip (SoC), that is, on a chip , in addition to including a processing circuit (usually called a "core") capable of running program instructions, it also includes other hardware circuits for implementing specific functions (of course, these hardware circuits can also be implemented independently based on ASIC and FPGA), correspondingly Yes, in addition to the function of executing software instructions, the processing function may also include various hardware acceleration functions (such as AI calculation, encoding and decoding, compression and decompression, etc.).
- SoC system on a chip
- the hardware processing circuit can be composed of discrete hardware components or an integrated circuit. In order to reduce power consumption and reduce size, it is usually implemented in the form of integrated circuits.
- the hardware processing circuit may include an ASIC, or a programmable logic device (programmable logic device, PLD); wherein, the PLD may in turn include an FPGA, a complex programmable logic device (complex programmable logic device, CPLD), and the like.
- These hardware processing circuits can be a single semiconductor chip packaged separately (such as packaged into an ASIC); they can also be integrated with other circuits (such as CPU, DSP) and packaged into a semiconductor chip, for example, can be formed on a silicon substrate
- a variety of hardware circuits and CPUs are individually packaged into a chip, which is also called SoC, or circuits and CPUs for implementing FPGA functions can also be formed on a silicon substrate and individually enclosed into a single chip. Also known as a programmable system on a chip (system on a programmable chip, SoPC).
- the unit described as a separate component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or may be distributed to multiple on the network unit. Some or all of the units may be selected according to actual needs to achieve the purpose of the solutions of the embodiments of the present application.
- each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
- the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
- the integrated unit if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium.
- the medium may include several instructions to cause a computer device, such as a personal computer, a server, or a network device, or a processor to perform all or part of the operations of the methods described in the various embodiments of the present application.
- the aforementioned storage medium may include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, etc. that can store program codes medium or computer-readable storage medium.
- transmission may include the following three situations: data transmission, data reception, or data transmission and data reception.
- data may include service data, and/or signaling data.
- At least one means one or more. “Includes at least one of the following: A, B, C.” means that it may include A, or B, or C, or A and B, or A and C, or B and C, or A, B and C.
- GSM global system of mobile communication
- CDMA code division multiple access
- WCDMA wideband code division multiple access
- general packet radio service general packet radio service
- GPRS general packet radio service
- long term evolution long term evolution
- LTE long term evolution
- LTE frequency division duplex frequency division duplex
- TDD LTE Time division duplex
- WiMAX worldwide interoperability for microwave access
- 5G 5th generation
- NR new radio
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (46)
- 一种通信方法,其特征在于,应用于第一节点,包括:确定与第二节点之间的无线链路发生无线链路失败RLF,且与目的节点之间不存在其他可用路径;向第三节点发送第一指示信息,所述第一指示信息用于指示RLF或者正在尝试链路恢复;所述第二节点为所述第一节点的父节点,所述第三节点为所述第一节点的子节点;或者,所述第二节点为所述第一节点的子节点,所述第三节点为所述第一节点的父节点或者所述第一节点连接的宿主节点。
- 根据权利要求1所述的方法,其特征在于,当所述第二节点为所述第一节点的父节点,所述第三节点为所述第一节点的子节点时,所述方法还包括:尝试无线链路恢复时,向所述第三节点发送第一指示信息,所述第一指示信息用于指示正在尝试链路恢复。
- 根据权利要求1或2所述的方法,其特征在于,还包括:向所述第三节点发送第二指示信息,所述第二指示信息用于指示经过所述第一节点到所述目的节点的路径不可用。
- 根据权利要求3所述的方法,其特征在于,所述第二指示信息包括所述目的节点的回传适配层BAP地址,或者,经过所述第一节点到所述目的节点的路径对应的路由标识routing ID,或者,经过所述第一节点到所述目的节点的路径对应的路径标识path ID。
- 根据权利要求4所述的方法,其特征在于,所述第二指示信息用于指示经过所述第一节点到所述目的节点的路径不可用,包括:所述第二指示信息用于指示经过所述第一节点到目的节点的所有路径均不可用;或者,所述第二指示信息用于指示所有经过所述第一节点到目的节点的路径中,对应的path ID等于所述第二指示信息包括的path ID的路径不可用;或者,所述第二指示信息用于指示所有经过所述第一节点到目的节点的路径中,对应的routing ID等于所述第二指示信息包括的routing ID的路径不可用。
- 根据权利要求3所述的方法,其特征在于,当所述第二节点为所述第一节点的子节点,所述第三节点为所述第一节点连接的宿主节点时,所述第二指示信息包括所述第二节点的标识。
- 根据权利要求6所述的方法,其特征在于,所述第二指示信息用于指示经过所述第一节点到所述目的节点的路径不可用,包括:所述第二指示信息用于指示所有经过所述第一节点到目的节点的路径中,包括所述第一节点和所述第二节点之间的直连无线链路的路径不可用。
- 一种通信方法,其特征在于,应用于第三节点,包括:接收来自第一节点的第二指示信息,所述第二指示信息用于指示经过所述第一节点到目的节点的路径不可用;确定通过其他路径向所述目的节点路由数据。
- 根据权利要求8所述的方法,其特征在于,所述方法还包括:接收来自第一节点的第一指示信息,第一指示信息用于指示RLF或者正在尝试链路恢复。
- 根据权利要求8或9所述的方法,其特征在于,所述第二指示信息包括所述目的节点的回传适配层BAP地址,或者,经过所述第一节点到所述目的节点的路径对应的路由标识routing ID,或者,经过所述第一节点到所述目的节点的路径对应的路径标识path ID。
- 根据权利要求10所述的方法,其特征在于,所述其他路径不包括所述第一节点,或者,所述其他路径的routing ID不等于所述第二指示信息包括的routing ID,或者,所述其他路径的Path ID不等于所述第二指示信息中包括的Path ID。
- 根据权利要求8或9所述的方法,其特征在于,所述第二指示信息包括第二节点的标识,其中,所述第二节点为所述第一节点的子节点,所述第一节点和第二节点之间的无线链路发生RLF。
- 根据权利要求12所述的方法,其特征在于,所述其他路径的routing ID不等于包括所述第一节点和所述第二节点之间的直连无线链路的,经过所述第一节点到所述目的节点的路径对应的routing ID。
- 根据权利要求8-13中任一所述的方法,其特征在于,还包括:接收来自所述第一节点的第三指示信息,所述第三指示信息用于指示无线链路恢复成功;停止通过所述其他路径向所述目的节点路由数据。
- 一种通信方法,其特征在于,应用于第一节点,包括:接收来自第四节点的主基站的第一消息,所述第一消息用于请求添加所述第一节点为第四节点的辅基站;其中,所述第一消息包括:所述第四节点接入的第二节点的小区的物理小区标识PCI和所述第四节点在所述第二节点的小区中的小区临时无线网络标识C-RNTI;或者,第三节点的标识和所述第四节点在所述第三节点和所述第一节点之间的接口上的标识;其中,所述第三节点为所述第四节点的源辅基站,所述第四节点为第二节点的下游节点;获取所述第四节点的上下文信息。
- 根据权利要求15所述的方法,其特征在于,在接收第一消息之前,所述方法还包括:接收来自所述第二节点的第二消息,所述第二消息用于请求建立或者重建立与所述第二节点之间的无线资源控制RRC连接;向所述第三节点发送第三消息,所述第三消息用于请求获取与所述第二节点相关的上下文信息;接收来自所述第三节点的第四消息,所述第四消息包括所述与所述第二节点相关的上下文信息;向所述第二节点发送第五消息,所述第五消息用于建立或者重建立与所述第二节点之间的RRC连接。
- 根据权利要求16所述的方法,其特征在于,所述第五消息中包括用于更新所述第二节点服务的小区的信息。
- 根据权利要求17所述的方法,其特征在于,所述用于更新所述第二节点服务的小区的信息包括:所述第二节点连接到所述第一节点时,所述第二节点的小区的全球小区标识CGI和/或小区标识cell identity。
- 根据权利要求15-18中任一所述的方法,其特征在于,与所述第二节点相关的上下文信息包括以下至少一种:所述第二节点的上下文信息,所述第二节点与所述第四节点之间的拓扑信息,所述第四节点的上下文信息,指示所述第二节点是否为无线回传设备的指示信息,或者指示所述第四节点是否为无线回传设备的指示信息。
- 根据权利要求19所述的方法,其特征在于,所述第四节点的上下文信息包括:所述PCI和所述C-RNTI;或者,所述第三节点的标识和所述第四节点在所述第三节点和所述第一节点之间的接口上的标识。
- 一种通信方法,其特征在于,应用于第四节点的主基站,包括:接收来自第三节点的第六消息,所述第六消息用于请求将第一节点作为所述第四节点的目标辅基站,其中,所述第三节点为所述第四节点的源辅基站;向所述第一节点发送第一消息,所述第一消息用于请求添加所述第一节点为所述第四节点的辅基站,其中,所述第一消息包括:所述第四节点接入的第二节点的小区的物理小区标识PCI和所述第四节点在所述第二节点的小区中的小区临时无线网络标识C-RNTI;或者,所述第三节点的标识和所述第四节点在所述第三节点和所述第一节点之间的接口上的标识。
- 一种通信装置,其特征在于,包括:处理模块,用于确定与第二节点之间的无线链路发生无线链路失败RLF,且与目的节点之间不存在其他可用路径;发送模块,用于向第三节点发送第一指示信息,所述第一指示信息用于指示RLF或者正在尝试链路恢复;所述第二节点为所述第一节点的父节点,所述第三节点为所述第一节点的子节点;或者,所述第二节点为所述第一节点的子节点,所述第三节点为所述第一节点的父节点或者所述第一节点连接的宿主节点。
- 根据权利要求22所述的装置,其特征在于,当所述第二节点为所述第一节点的父节点,所述第三节点为所述第一节点的子节点时,所述发送模块具体用于:尝试无线链路恢复时,向所述第三节点发送第一指示信息,所述第一指示信息用于指示正在尝试链路恢复。
- 根据权利要求22或23所述的装置,其特征在于,所述发送模块还用于:向所述第三节点发送第二指示信息,所述第二指示信息用于指示经过所述第一节点到所述目的节点的路径不可用。
- 根据权利要求24所述的装置,其特征在于,所述第二指示信息包括所述目的节点的回传适配层BAP地址,或者,经过所述第一节点到所述目的节点的路径对应的路由标识routing ID,或者,经过所述第一节点到所述目的节点的路径对应的路径标识path ID。
- 根据权利要求25所述的装置,其特征在于,所述第二指示信息用于指示经过所述第一节点到所述目的节点的路径不可用,包括:所述第二指示信息用于指示经过所述第一节点到目的节点的所有路径均不可用;或者,所述第二指示信息用于指示所有经过所述第一节点到目的节点的路径中,对应的path ID等于所述第二指示信息包括的path ID的路径不可用;或者,所述第二指示信息用于指示所有经过所述第一节点到目的节点的路径中,对应的routing ID等于所述第二指示信息包括的routing ID的路径不可用。
- 根据权利要求24所述的装置,其特征在于,当所述第二节点为所述第一节点的子节点,所述第三节点为所述第一节点连接的宿主节点时,所述第二指示信息包括所述第二节点的标识。
- 根据权利要求27所述的装置,其特征在于,所述第二指示信息用于指示经过所述第 一节点到所述目的节点的路径不可用,包括:所述第二指示信息用于指示所有经过所述第一节点到目的节点的路径中,包括所述第一节点和所述第二节点之间的直连无线链路的路径不可用。
- 一种通信装置,其特征在于,包括:获取模块,用于接收来自第一节点的第二指示信息,所述第二指示信息用于指示经过所述第一节点到目的节点的路径不可用;处理模块,用于确定通过其他路径向所述目的节点路由数据。
- 根据权利要求29所述的装置,其特征在于,所述获取模块还用于:接收来自第一节点的第一指示信息,第一指示信息用于指示RLF或者正在尝试链路恢复。
- 根据权利要求29或30所述的装置,其特征在于,所述第二指示信息包括所述目的节点的回传适配层BAP地址,或者,经过所述第一节点到所述目的节点的路径对应的路由标识routing ID,或者,经过所述第一节点到所述目的节点的路径对应的路径标识path ID。
- 根据权利要求31所述的装置,其特征在于,所述其他路径不包括所述第一节点,或者,所述其他路径的routing ID不等于所述第二指示信息包括的routing ID,或者,所述其他路径的Path ID不等于所述第二指示信息中包括的Path ID。
- 根据权利要求29或30所述的装置,其特征在于,所述第二指示信息包括第二节点的标识,其中,所述第二节点为所述第一节点的子节点,所述第一节点和第二节点之间的无线链路发生RLF。
- 根据权利要求33所述的装置,其特征在于,所述其他路径的routing ID不等于包括所述第一节点和所述第二节点之间的直连无线链路的,经过所述第一节点到所述目的节点的路径对应的routing ID。
- 根据权利要求29-34中任一所述的装置,其特征在于,所述获取模块还用于接收来自所述第一节点的第三指示信息,所述第三指示信息用于指示无线链路恢复成功;所述处理模块还用于停止通过所述其他路径向所述目的节点路由数据。
- 一种通信装置,其特征在于,包括:获取模块,用于接收来自第四节点的主基站的第一消息,所述第一消息用于请求添加所述第一节点为第四节点的辅基站;其中,所述第一消息包括:所述第四节点接入的第二节点的小区的物理小区标识PCI和所述第四节点在所述第二节点的小区中的小区临时无线网络标识C-RNTI;或者,第三节点的标识和所述第四节点在所述第三节点和所述第一节点之间的接口上的标识;其中,所述第三节点为所述第四节点的源辅基站,所述第四节点为第二节点的下游节点;处理模块,用于获取所述第四节点的上下文信息。
- 根据权利要求36所述的装置,其特征在于,在接收第一消息之前,所述获取模块还用于接收来自所述第二节点的第二消息,所述第二消息用于请求建立或者重建立与所述第二节点之间的无线资源控制RRC连接;发送模块,用于向所述第三节点发送第三消息,所述第三消息用于请求获取与所述第二节点相关的上下文信息;所述获取模块还用于接收来自所述第三节点的第四消息,所述第四消息包括所述与所述 第二节点相关的上下文信息;所述发送模块还用于向所述第二节点发送第五消息,所述第五消息用于建立或者重建立与所述第二节点之间的RRC连接。
- 根据权利要求37所述的装置,其特征在于,所述第五消息中包括用于更新所述第二节点服务的小区的信息。
- 根据权利要求38所述的装置,其特征在于,所述用于更新所述第二节点服务的小区的信息包括:所述第二节点连接到所述第一节点时,所述第二节点的小区的全球小区标识CGI和/或小区标识cell identity。
- 根据权利要求36-39中任一所述的装置,其特征在于,与所述第二节点相关的上下文信息包括以下至少一种:所述第二节点的上下文信息,所述第二节点与所述第四节点之间的拓扑信息,所述第四节点的上下文信息,指示所述第二节点是否为无线回传设备的指示信息,或者指示所述第四节点是否为无线回传设备的指示信息。
- 根据权利要求40所述的装置,其特征在于,所述第四节点的上下文信息包括:所述PCI和所述C-RNTI;或者,所述第三节点的标识和所述第四节点在所述第三节点和所述第一节点之间的接口上的标识。
- 一种通信装置,其特征在于,应用于第四节点的主基站,包括:获取模块,用于接收来自第三节点的第六消息,所述第六消息用于请求将第一节点作为所述第四节点的目标辅基站,其中,所述第三节点为所述第四节点的源辅基站;发送模块,用于向所述第一节点发送第一消息,所述第一消息用于请求添加所述第一节点为所述第四节点的辅基站,其中,所述第一消息包括:所述第四节点接入的第二节点的小区的物理小区标识PCI和所述第四节点在所述第二节点的小区中的小区临时无线网络标识C-RNTI;或者,所述第三节点的标识和所述第四节点在所述第三节点和所述第一节点之间的接口上的标识。
- 一种通信装置,其特征在于,包括:至少一个处理器和接口电路,所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置,所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至21中任一项所述的方法。
- 一种通信***,其特征在于,包括如权利要求22至28中任一项所述的通信装置和如权利要求29至35中任一项所述的通信装置,或者,包括如权利要求36至41中任一项所述的通信装置和如权利要求42中任一项所述的通信装置。
- 一种计算机可读存储介质,所述计算机可读存储介质中存储有计算机程序或指令,其特征在于,当所述计算机程序或指令被通信装置执行时,使得通信装置执行如权利要求1至21中任一项所述的方法。
- 一种计算机程序产品,包含计算机程序指令,其特征在于,所述计算机程序指令被通信装置执行时,使得通信装置执行实现如权利要求1至21中任一项所述的方法。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2023519813A JP2023543492A (ja) | 2020-09-30 | 2021-04-01 | 通信方法及び関連デバイス |
EP21873831.8A EP4213536A4 (en) | 2020-09-30 | 2021-04-01 | COMMUNICATION METHOD AND ASSOCIATED DEVICE |
CN202180065838.7A CN116325911A (zh) | 2020-09-30 | 2021-04-01 | 一种通信方法及相关设备 |
KR1020237014550A KR20230074583A (ko) | 2020-09-30 | 2021-04-01 | 통신 방법 및 관련 디바이스 |
US18/192,141 US20230239954A1 (en) | 2020-09-30 | 2023-03-29 | Communication method and related device |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNPCT/CN2020/119697 | 2020-09-30 | ||
PCT/CN2020/119697 WO2022067781A1 (zh) | 2020-09-30 | 2020-09-30 | 一种通信方法及相关设备 |
PCT/CN2020/137817 WO2022068094A1 (zh) | 2020-09-30 | 2020-12-19 | 一种通信方法及相关设备 |
CNPCT/CN2020/137817 | 2020-12-19 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/192,141 Continuation US20230239954A1 (en) | 2020-09-30 | 2023-03-29 | Communication method and related device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022068164A1 true WO2022068164A1 (zh) | 2022-04-07 |
Family
ID=80949230
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2021/085137 WO2022068164A1 (zh) | 2020-09-30 | 2021-04-01 | 一种通信方法及相关设备 |
Country Status (6)
Country | Link |
---|---|
US (1) | US20230239954A1 (zh) |
EP (1) | EP4213536A4 (zh) |
JP (1) | JP2023543492A (zh) |
KR (1) | KR20230074583A (zh) |
CN (1) | CN116325911A (zh) |
WO (1) | WO2022068164A1 (zh) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107666727A (zh) * | 2016-07-25 | 2018-02-06 | 中兴通讯股份有限公司 | 能力协商的方法及装置、*** |
EP3589069A1 (en) * | 2017-03-25 | 2020-01-01 | LG Electronics Inc. -1- | Method and apparatus for improving procedure for lte/nr interworking in wireless communication system |
CN110831095A (zh) * | 2018-08-11 | 2020-02-21 | 华为技术有限公司 | 通信方法和通信装置 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11700565B2 (en) * | 2018-09-18 | 2023-07-11 | Qualcomm Incorporated | Management of radio link failure in wireless backhaul |
WO2020165278A1 (en) * | 2019-02-13 | 2020-08-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Using alternative paths of descendant nodes for backhaul-link failure reporting in integrated access |
KR20230069987A (ko) * | 2020-10-21 | 2023-05-19 | 후지쯔 가부시끼가이샤 | 라우팅 방법, 장치 및 시스템 |
-
2021
- 2021-04-01 JP JP2023519813A patent/JP2023543492A/ja active Pending
- 2021-04-01 WO PCT/CN2021/085137 patent/WO2022068164A1/zh unknown
- 2021-04-01 CN CN202180065838.7A patent/CN116325911A/zh active Pending
- 2021-04-01 KR KR1020237014550A patent/KR20230074583A/ko active Search and Examination
- 2021-04-01 EP EP21873831.8A patent/EP4213536A4/en active Pending
-
2023
- 2023-03-29 US US18/192,141 patent/US20230239954A1/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107666727A (zh) * | 2016-07-25 | 2018-02-06 | 中兴通讯股份有限公司 | 能力协商的方法及装置、*** |
EP3589069A1 (en) * | 2017-03-25 | 2020-01-01 | LG Electronics Inc. -1- | Method and apparatus for improving procedure for lte/nr interworking in wireless communication system |
CN110831095A (zh) * | 2018-08-11 | 2020-02-21 | 华为技术有限公司 | 通信方法和通信装置 |
Non-Patent Citations (3)
Title |
---|
HUAWEI: "(TP for NR_IAB BL CR for TS 38.401): Backhaul RLF recovery", 3GPP DRAFT; R3-195467 BACKHAUL RLF RECOVERY, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Chongqing, China; 20191014 - 20191018, 5 October 2019 (2019-10-05), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051792502 * |
HUAWEI: "(TP for NR_IAB BL CR for TS 38.401): Backhaul RLF recovery", 3GPP TSG-RAN WG3 MEETING #106 R3-196993, 22 November 2019 (2019-11-22), XP051820652 * |
See also references of EP4213536A4 |
Also Published As
Publication number | Publication date |
---|---|
KR20230074583A (ko) | 2023-05-30 |
CN116325911A (zh) | 2023-06-23 |
EP4213536A4 (en) | 2024-03-13 |
US20230239954A1 (en) | 2023-07-27 |
EP4213536A1 (en) | 2023-07-19 |
JP2023543492A (ja) | 2023-10-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11510131B2 (en) | Configuration method, data transmission method, and apparatus | |
US11425600B2 (en) | Wireless backhaul data transmission method and apparatus | |
WO2022082679A1 (zh) | 一种通信方法及相关设备 | |
WO2022001503A1 (zh) | 一种用于iab网络通信的方法及相关设备 | |
WO2022011496A1 (zh) | 一种通信方法和通信装置 | |
US20230247521A1 (en) | Lossless data transmission communication method, apparatus, and system | |
CN114026929B (zh) | 一种f1接口管理方法及装置 | |
US20230328607A1 (en) | Communication control method | |
WO2022068164A1 (zh) | 一种通信方法及相关设备 | |
WO2022068094A1 (zh) | 一种通信方法及相关设备 | |
WO2022082543A1 (zh) | Iab节点的移植方法及装置 | |
WO2021026936A1 (zh) | 一种处理回传链路发生链路失败的方法及装置 | |
WO2023131091A1 (zh) | 通信方法和装置 | |
WO2020029080A1 (zh) | 切换网络的方法、网络节点、芯片和通信*** | |
WO2023011111A1 (zh) | 路由方法和通信装置 | |
WO2022237357A1 (zh) | 通信方法和装置 | |
WO2023131094A1 (zh) | 通信方法及通信装置 | |
WO2023010298A1 (zh) | 信息发送方法,信息处理方法以及装置 | |
US20240179543A1 (en) | Communication control method | |
WO2023150968A1 (zh) | 收发信号的方法、装置和通信*** | |
WO2023273926A1 (zh) | 一种多连接下的通信方法及装置 | |
WO2023060401A1 (zh) | 无线路由方法及装置 | |
WO2020029074A1 (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: 21873831 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2023519813 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2021873831 Country of ref document: EP Effective date: 20230411 |
|
ENP | Entry into the national phase |
Ref document number: 20237014550 Country of ref document: KR Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |