WO2022041249A1 - 一种节点的切换方法以及相关设备 - Google Patents
一种节点的切换方法以及相关设备 Download PDFInfo
- Publication number
- WO2022041249A1 WO2022041249A1 PCT/CN2020/112681 CN2020112681W WO2022041249A1 WO 2022041249 A1 WO2022041249 A1 WO 2022041249A1 CN 2020112681 W CN2020112681 W CN 2020112681W WO 2022041249 A1 WO2022041249 A1 WO 2022041249A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- node
- iab
- iab node
- terminal device
- nodes
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/08—Reselecting an access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/13—Cell handover without a predetermined boundary, e.g. virtual cells
Definitions
- the present application relates to the field of communications, and in particular, to a node switching method and related equipment.
- the protocol standard of the fifth generation cellular mobile communication system formulated by the third generation partnership project (3GPP) standard organization, compared with the long term evolution (LTE) system, the new radio (New Radio, NR) ) system supports larger transmission bandwidth, more transceiver antenna arrays, higher transmission rate and more flexible scheduling mechanism with smaller granularity.
- 3GPP third generation partnership project
- NR new Radio
- IAB Integrated Access and Backhaul
- the existing switching technology can realize that the IAB-MT in the IAB node is switched from the source host node to the target host node without involving the IAB-DU in the IAB node and the children of the IAB node.
- the processing of a node for example, a terminal device or other IAB nodes, so that the child nodes of the IAB node cannot work normally after the IAB node is switched.
- the present application provides a node switching method and related equipment.
- the source host node triggers the IAB node and its child nodes (for example, other IAB nodes or terminals) to switch to the target host node together, thereby ensuring the data of the terminal device after the IAB node is switched. normal transmission.
- a first aspect of the present application provides a node handover method, in which: a source host node sends a handover request message to a target host node, where the handover request message includes context information of the integrated IAB node for access and return and at least one terminal Context information of the device, the handover request message is used to request to handover the IAB node and at least one terminal device to the target host node, wherein the terminal device is directly connected to the IAB node, or the terminal The device is connected to the IAB node through at least one other IAB node; the source host node receives a handover response message sent by the target host node, and the handover response message includes the accepted terminal device in the at least one terminal device , and/or the identifier of the rejected terminal device among the at least one terminal device.
- the terminal device accepted by the target host node is switched to the target host node, so that the IAB node and the accepted terminal device are switched to the target host node together, ensuring that the accepted terminal device normal transmission of data.
- the method further includes: the source host node receives a measurement result sent by the IAB node, and the measurement The result includes the result of measuring the signal quality of the serving cell by the IAB node and the result of measuring the signal quality of the neighboring cell by the IAB node; the source host node determines according to the measurement result that the IAB node and at least A terminal device switches to the target host node.
- the source host node determines the IAB node according to the measurement result. And at least one terminal device switches to the target host node. If the IAB node works in the CA mode, the serving cell includes a primary cell and at least one secondary cell.
- CA carrier aggregation
- the source host node determines the IAB node according to the measurement result. And at least one terminal device switches to the target host node. This possible implementation ensures that the IAB node and at least one terminal device perform handover when the signal quality of the neighboring cell is better than that of the current cell, which improves the communication quality of the IAB node and at least one terminal device.
- the handover request message further includes context information of the other IAB node
- the The handover response message also includes the identifiers of the other IAB nodes that are accepted in the at least one other IAB node, and/or the identifiers of the other IAB nodes that are rejected in the at least one other IAB node.
- the handover response message received by the source host node includes the identification of at least one other IAB node that is accepted in the other IAB node, and/or, the other IAB node that is rejected in at least one other IAB node.
- the method further includes:
- the source host node determines to switch the IAB node, at least one other IAB node and at least one terminal device to the target host node according to the measurement result.
- the source host node determines the IAB node, at least one other IAB node according to the measurement result.
- At least one terminal device switches to the target host node; if the IAB node works in the CA mode, the serving cell includes a primary cell and at least one secondary cell, and if the signal quality of a neighbor cell is higher than that of the primary cell, then The source host node may determine to switch the IAB node, at least one other IAB node and at least one terminal device to the target host node according to the measurement result.
- This possible implementation ensures that the IAB node, at least one other IAB node, and at least one terminal device perform handover when the signal quality of the neighboring cell is better than the signal quality of the current cell, which improves the IAB node, at least one other IAB node, and at least one IAB node.
- the communication quality of an end device if the IAB node works in the CA mode, the serving cell includes a primary cell and at least one secondary cell, and if the signal quality of a neighbor cell is higher than that of the primary cell, then The source host node may determine to switch the IAB node
- the IAB node includes an integrated access and backhaul mobile terminal IAB-MT and an integrated access and backhaul distributed unit IAB-DU, and context information of the IAB node Including the context information of the IAB-MT and the context information of the IAB-DU; the context information of the IAB-MT includes the backhaul radio link control between the IAB-MT and the parent node of the IAB node Configuration information of the channel BH RLC CH; the context information of the IAB-DU includes the identifier of the IAB-DU and/or the cell identifier of the IAB-DU.
- the source host node transmits the context information of the IAB node to the target host node, so that the target host node can prepare for switching resources for the IAB node according to the context information.
- This possible implementation improves the IAB node. The success rate of switching to the target host node.
- the context information of the IAB-DU further includes activation indication information of the cell of the IAB-DU, where the activation indication information is used to indicate whether the cell of the IAB-DU has
- the target host node learns which cells of the IAB-DU have been activated by the source host node, and these cells still need to be activated by the target host node after the IAB node switches to the target host node.
- This possible implementation ensures that the activated cell can still maintain normal communication after the IAB node is handed over to the target host node.
- the context information of the IAB node further includes a backhaul adaptation protocol BAP address allocated by the source host node to the IAB node.
- the target host node learns the BAP address allocated by the source host node for the IAB node, so that the BAP address newly allocated by the target host node for the IAB node is different from the BAP address allocated by the source host node for the IAB node.
- the context information of the terminal device includes an identifier of the terminal device, and the identifier of the terminal device includes a physical cell identifier (physical cell) of a cell accessed by the terminal device identifier, PCI) and the cell-radio network temporary identifier (C-RNTI) of the terminal device in the access cell.
- the identifier of the terminal device includes a physical cell identifier (physical cell) of a cell accessed by the terminal device identifier, PCI) and the cell-radio network temporary identifier (C-RNTI) of the terminal device in the access cell.
- PCI physical cell identifier
- C-RNTI cell-radio network temporary identifier
- the target host node identifies the terminal device according to the identification of the terminal device. This possible implementation improves the identification of the terminal by the target host node. accuracy at the time of the device.
- the context information of the IAB node further includes an identifier of a child node of the IAB node, which is used to indicate the relationship between the IAB node and the child nodes of the IAB node. topological relationship.
- the target host node can learn the topology relationship between the nodes to be switched over.
- the context information of the IAB node further includes network topology list information. If the terminal device is directly connected to the IAB node, the network topology list information is used to indicate the topology relationship between the IAB node and the terminal device; if the terminal device is connected to the IAB node through at least one other IAB node For the IAB node, the network topology list information is used to indicate the topology relationship between the IAB node and the other IAB nodes, and between the other IAB nodes and the terminal device.
- the target host node learns the topology relationship between the nodes to be switched over.
- the other IAB nodes include other IAB-MTs and other IAB-DUs
- the context information of the other IAB nodes includes the context information of the other IAB-MTs and the The context information of other IAB-DUs
- the context information of the other IAB-MTs includes the configuration information of the BH RLC CHs between the other IAB-MTs and the parent nodes of the other IAB nodes
- the context information of the other IAB-DUs includes other The identity of the IAB-DU and/or the cell identity of other IAB-DUs.
- the source host node transmits the context information of other IAB nodes to the target host node, so that the target host node can prepare for switching resources for other IAB nodes according to the context information.
- This possible implementation improves the The success rate of other IAB nodes to follow the IAB node to switch to the target host node.
- the context information of the other IAB-DU further includes activation indication information of the cell of the other IAB-DU, and the activation indication information of the cell of the other IAB-DU is used to indicate Whether the cells of the other IAB-DUs have been activated.
- the target host node learns which cells of other IAB-DUs have been activated by the source host node, and these cells still have to be activated by the target host node after other IAB nodes switch to the target host node.
- the implementation ensures that the activated cells can still maintain normal communication after other IAB nodes are handed over to the target host node.
- the context information of the other IAB nodes further includes a BAP address allocated by the source host node to the other IAB nodes.
- the target host node learns the BAP addresses allocated by the source host node to other IAB nodes, so that the BAP addresses newly allocated by the target host node to other IAB nodes are different from the BAP addresses allocated by the source host node to other IAB nodes .
- the context information of the other IAB nodes further includes the identifier of the parent node of the other IAB node, and/or the identifier of the child node of the other IAB node, using Indicates the topological relationship between the other IAB node and the parent node of the other IAB node, and/or between the other IAB node and the child nodes of the other IAB node.
- the target host node can learn the topology relationship between the nodes to be switched over.
- the source host node includes a source Donor-CU
- the target host node includes a target Donor-CU
- the method further includes: the source Donor-CU from the source Donor-CU
- the first radio resource control RRC message generated by the target Donor-CU is obtained from the handover response message, where the first RRC message includes the cell configuration information after the first IAB node is handed over to the target host node, the first IAB
- the node includes the IAB node and other accepted IAB nodes in other IAB nodes; the source Donor-CU sends the first RRC message to the first IAB node.
- the transmission mode of the cell configuration information provided by this possible implementation mode has little impact on the existing standard, which improves the implementability of the solution.
- the source host node includes a source Donor-CU
- the target host node includes a target Donor-CU
- the method further includes: the source Donor-CU from the source Donor-CU Obtain the first F1 application layer protocol (F1 application protocol, F1AP) message generated by the target Donor-CU in the handover response message, where the first F1AP message includes the cell configuration after the first IAB node is switched to the target host node information, the first IAB node includes the IAB node and other accepted IAB nodes in other IAB nodes; the source Donor-CU encapsulates the first F1AP message in a second F1AP message and sends it to the first F1AP message An IAB node.
- F1 application layer protocol F1 application protocol, F1AP
- the transmission mode of the cell configuration information provided by this possible implementation is to transmit the updated cell configuration information through the existing F1AP message between the source Donor-CU and the first IAB node, which makes little changes to the standard protocol process and improves the feasibility of the program.
- the source host node includes a source Donor-CU
- the target host node includes a target Donor-CU
- the method further includes: the source Donor-CU from the source Donor-CU
- the cell configuration information after the first IAB node is handed over to the target host node is obtained from the handover response message, where the first IAB node includes the IAB node and other IAB nodes accepted from other IAB nodes; the source Donor- The CU encapsulates the cell configuration information in an F1AP message and sends it to the first IAB node.
- the transmission mode of the cell configuration information provided by this possible implementation is to transmit the updated cell configuration information through the existing F1AP message between the source Donor-CU and the first IAB node, which makes little changes to the standard protocol process and improves the solution. achievability.
- a second aspect of the present application provides a node handover method, the method includes: a target host node receives a handover request message sent by a source host node, where the handover request message includes context information of the integrated IAB node for access and return and at least one Context information of a terminal device, the handover request message is used to request to switch the IAB node and at least one terminal device to the target host node, wherein the terminal device is directly connected to the IAB node, or the The terminal device is connected to the IAB node through at least one other IAB node; the target host node sends a handover response message to the source host node, and the handover response message includes the accepted terminal device in the at least one terminal device , and/or the identifier of the rejected terminal device among the at least one terminal device.
- the target host node includes a target Donor-CU
- the method further includes: the target Donor-CU sends a context establishment request message to the first IAB node, the context
- the establishment request message carries the identification of the terminal equipment, and the identification of the terminal equipment includes the cell identification of the terminal equipment accessing the first IAB node and the identification C-RNTI of the terminal equipment in the access cell;
- the terminal device is directly connected to the IAB node, and the first IAB node is the IAB node; if the terminal device is connected to the IAB node through at least one other IAB node, the first IAB node is the IAB node At least one other IAB node.
- the IAB host node sends a terminal device context establishment request message to the parent node of the IAB node (the IAB-DU part of the parent node), so that the parent node of the IAB node performs air interface for the IAB node.
- the allocation of resources establishing the BH RLC CH between the IAB node and its parent node, and establishing the corresponding GTP tunnel between the parent node of the IAB node and the IAB host node to transmit the return data of the IAB node.
- the IAB node includes an integrated access and backhaul mobile terminal IAB-MT and an integrated access and backhaul distributed unit IAB-DU, and context information of the IAB node Including the context information of the IAB-MT and the context information of the IAB-DU; the context information of the IAB-MT includes the backhaul radio link control between the IAB-MT and the parent node of the IAB node Configuration information of the channel BH RLC CH; the context information of the IAB-DU includes the identifier of the IAB-DU and/or the cell identifier of the IAB-DU.
- the source host node transmits the context information of other IAB nodes to the target host node, so that the target host node can prepare for switching resources for other IAB nodes according to the context information.
- This possible implementation improves the The success rate of other IAB nodes to follow the IAB node to switch to the target host node.
- the context information of the IAB-DU further includes activation indication information of the cell of the IAB-DU, where the activation indication information is used to indicate whether the cell of the IAB-DU has Activated.
- the target host node learns which cells of the IAB-DU have been activated by the source host node, and these cells still need to be activated by the target host node after the IAB node switches to the target host node.
- This possible implementation ensures that the activated cells can still maintain normal communication after other IAB nodes are handed over to the target host node.
- the context information of the IAB node further includes a backhaul adaptation protocol BAP address allocated by the source host node to the IAB node.
- the target host node learns the BAP addresses allocated by the source host node to the IAB nodes, so that the BAP addresses newly allocated by the target host node to other IAB nodes are different from the BAP addresses allocated by the source host node to other IAB nodes.
- the context information of the terminal device includes an identifier of the terminal device, and the identifier of the terminal device includes a physical cell identifier PCI of a cell accessed by the terminal device and all The identifier C-RNTI of the terminal equipment in the access cell.
- the target host node identifies the terminal device according to the identification of the terminal device. This possible implementation improves the identification of the terminal by the target host node. accuracy at the time of the device.
- the context information of the IAB node further includes an identifier of the child node of the IAB node, which is used to indicate the relationship between the IAB node and the child node of the IAB node. topological relationship.
- the target host node can learn the topology relationship between the nodes to be switched over.
- the context information of the IAB node further includes network topology list information; if the terminal device is directly connected to the IAB node, the network topology list information is used to indicate The topology relationship between the IAB node and the terminal device; if the terminal device is connected to the IAB node through at least one other IAB node, the network topology list information is used to indicate the IAB node and the other IAB node. Topological relationships between IAB nodes, and between the other IAB nodes and the terminal device.
- the target host node learns the topology relationship between the nodes to be switched over.
- the context information of the other IAB nodes includes the context information of the other IAB-MTs and all The context information of the other IAB-DU;
- the context information of the other IAB-MT includes the configuration information of the BH RLC CH between the other IAB-MT and the parent node of the other IAB node;
- the context information of the other IAB-DU includes The identity of other IAB-DUs and/or the cell identity of other IAB-DUs.
- the source host node transmits the context information of other IAB nodes to the target host node, so that the target host node can prepare for switching resources for other IAB nodes according to the context information.
- This possible implementation improves the The success rate of other IAB nodes to follow the IAB node to switch to the target host node.
- the context information of the other IAB-DU further includes activation indication information of the cell of the other IAB-DU, and the activation indication information of the cell of the other IAB-DU is used to indicate Whether the cells of the other IAB-DUs have been activated.
- the target host node learns which cells of other IAB-DUs have been activated by the source host node, and these cells still have to be activated by the target host node after other IAB nodes switch to the target host node.
- the implementation ensures that the activated cells can still maintain normal communication after other IAB nodes are handed over to the target host node.
- the context information of the other IAB nodes further includes a BAP address allocated by the source host node to the other IAB nodes.
- the target host node learns the BAP addresses allocated by the source host node to other IAB nodes, so that the BAP addresses newly allocated by the target host node to other IAB nodes are different from the BAP addresses allocated by the source host node to other IAB nodes .
- the context information of the other IAB nodes further includes the identifier of the parent node of the other IAB node, and/or the identifier of the child node of the other IAB node, using Indicates the topological relationship between the other IAB node and the parent node of the other IAB node, and/or between the other IAB node and the child nodes of the other IAB node.
- the target host node can learn the topology relationship between the IAB node to be handed over and other IAB nodes.
- the target host node includes a target Donor-CU; the target host node sends a handover response message to the source host node, including: the target Donor-CU to the target Donor-CU
- the source home node sends the handover response message, the handover response message includes a first RRC message, the first RRC message includes the cell configuration information after the first IAB node is handed over to the target home node, the first RRC message
- An IAB node includes the IAB node and other IAB nodes accepted among other IAB nodes.
- the transmission mode of the cell configuration information provided by this possible implementation mode has little impact on the existing standards, which improves the practicability of the solution.
- the target host node includes a target Donor-CU; the target host node sends a handover response message to the source host node, including: the target Donor-CU to the target Donor-CU
- the source host node sends the handover response message, the handover response message includes a first F1AP message, and the first F1AP message includes the cell configuration information after the first IAB node is handed over to the target host node, the first F1AP message
- An IAB node includes the IAB node or other IAB nodes accepted among other IAB nodes.
- the transmission mode of the cell configuration information provided by this possible implementation is to transmit the updated cell configuration information through the existing F1AP message between the source Donor-CU and the first IAB node, which makes little changes to the standard protocol process and improves the feasibility of the program.
- the target host node includes a target Donor-CU; the target host node sends a handover response message to the source host node, including: the target Donor-CU to the target Donor-CU The source host node sends the handover response message, where the handover response message includes the cell configuration information after the first IAB node is handed over to the target host node, and the first IAB node includes the IAB node and other IAB nodes Other IAB nodes accepted in .
- the transmission mode of the cell configuration information provided by this possible implementation is to transmit the updated cell configuration information through the existing F1AP message between the source Donor-CU and the first IAB node, which makes little changes to the standard protocol process and improves the feasibility of the program.
- the target host node includes a target Donor-CU
- the method further includes: the target donor-CU sends first indication information to the other IAB nodes, the The first indication information is used to indicate that the handover of the IAB node is completed.
- the target donor-CU sends the first indication information to other IAB nodes, and the other IAB nodes can sense the completion of the IAB node handover through the first indication information, that is, other IAB nodes can sense the difference between the IAB node and the target host node. The link between them is opened, so the IAB-DU of other IAB nodes can decide the time to trigger the processing of the application layer.
- the method before the target donor-CU sends the first indication information to the other IAB nodes, the method further includes: the target donor-CU sends the other IAB nodes to the Send second indication information, where the second indication information is used to indicate that the IAB node is handing over or preparing for handover.
- the target donor-CU sends second indication information to other IAB nodes, and other IAB nodes can perceive that the IAB node is switching or is preparing to switch through the second indication information, that is, other IAB nodes can perceive the IAB node and the target.
- the links between the host nodes are not opened, so the IAB-DUs of other IAB nodes can decide not to trigger the application layer processing through the second indication information.
- a third aspect of the present application provides a node switching method.
- an IAB node switches from a source host node to a target host node; the IAB node sends first indication information to a child node of the IAB node, and the first The indication information is used to indicate that the handover of the IAB node is completed.
- the child nodes of the IAB node are terminal equipment or other IAB nodes.
- the IAB node sends the first indication information to other IAB nodes, and the other IAB nodes can sense the completion of the IAB node handover through the first indication information, that is, the other IAB nodes can sense that the link between the IAB node and the target host node is opened. , so the IAB-DUs of other IAB nodes can decide the time to trigger the processing of the application layer.
- the method before the IAB node sends the first indication information to its child nodes, the method further includes: the IAB node sends second indication information to its child nodes, the The second indication information is used to indicate that the IAB node is switching or preparing to switch.
- the IAB node sends the second indication information to other IAB nodes, and the other IAB nodes can sense that the IAB node is switching or is preparing to switch through the second indication information, that is, other IAB nodes can sense the IAB node and the target host node.
- the links between them are not opened, so the IAB-DUs of other IAB nodes can decide not to trigger the application layer processing through the second indication information.
- a fourth aspect of the present application provides an IAB host node, where the IAB host node at least includes a sending unit, a receiving unit, and a processing unit;
- a sending unit configured to perform the sending action of the source host node in the node switching method provided in the foregoing first aspect or any possible implementation manner of the first aspect
- a receiving unit configured to perform the receiving action of the source host node in the node switching method provided in the foregoing first aspect or any possible implementation manner of the first aspect
- the processing unit is configured to execute the processing action of the source host node in the node switching method provided in the foregoing first aspect or any possible implementation manner of the first aspect.
- a fifth aspect of the present application provides an IAB host node, where the IAB host node at least includes a sending unit, a receiving unit, and a processing unit;
- a sending unit configured to perform the sending action of the target host node in the node switching method provided in the second aspect or any possible implementation manner of the second aspect
- a receiving unit configured to perform the receiving action of the target host node in the node switching method provided in the second aspect or any possible implementation manner of the second aspect
- the processing unit is configured to execute the processing action of the target host node in the node switching method provided in the second aspect or any possible implementation manner of the second aspect.
- a sixth aspect of the present application provides an IAB node, where the IAB node at least includes a sending unit, a receiving unit, and a processing unit;
- a sending unit configured to perform the sending action of the IAB node in the node switching method provided in the third aspect or any possible implementation manner of the third aspect;
- a receiving unit configured to perform the receiving action of the IAB node in the node switching method provided in the foregoing third aspect or any possible implementation manner of the third aspect;
- a processing unit configured to execute the processing action of the IAB node in the node switching method provided in the foregoing third aspect or any possible implementation manner of the third aspect.
- a seventh aspect of the present application provides a communication device, the communication device comprising: a processor, the processor is coupled with a memory, the memory is used for storing computer programs or instructions, and the processor is used for executing the memory in the memory.
- a computer program or instruction if the communication device is a source host node or a chip of a source host node, the communication device executes the method in the first aspect or any possible implementation of the first aspect, if the communication device is A target host node or a chip of a target host node, the communication device executes the method in the second aspect or any possible implementation manner of the second aspect, if the communication device is an IAB node or a chip of an IAB node, the communication device The apparatus performs the above third aspect or the method in any possible implementation manner of the third aspect.
- An eighth aspect of the present application provides a computer-readable storage medium, characterized in that, the computer-readable storage medium is used to store a computer program, and when the computer program runs on a computer, causes the computer to execute the above-mentioned first
- the method in one aspect or any possible implementation of the first aspect, or cause the computer to perform the method in the second aspect or any possible implementation of the second aspect, or cause the computer to perform the third aspect above or the method in any possible implementation manner of the third aspect.
- a ninth aspect of the present application provides a chip, including a processor and a communication interface, where the processor is configured to read instructions to execute the method in the first aspect or any possible implementation manner of the first aspect, or to execute the first aspect The method in the second aspect or any possible implementation manner of the second aspect, or the method in the above-mentioned third aspect or any possible implementation manner of the third aspect.
- a tenth aspect of the present application provides a network device, including a processor, the processor is connected to a memory, the memory is used for storing a computer program, and the processor is used for executing the computer program stored in the memory, so that the The network device executes the first aspect or the method in any possible implementation manner of the first aspect, or executes the second aspect or the method in any possible implementation manner of the second aspect, or executes the third aspect or The method in any possible implementation manner of the third aspect.
- An eleventh aspect of the present application provides a communication system, including the source host node described in the first aspect or any possible implementation manner of the first aspect and the second aspect or any possible implementation of the second aspect.
- FIG. 1 is a schematic diagram of a separation architecture of gNB-CU and gNB-DU in an existing communication system
- FIG. 2 is a schematic diagram of the control plane protocol stack under the CU-DU separation architecture adopted by the gNB in the existing communication system;
- FIG. 3 is a schematic diagram of a user plane protocol stack under the CU-DU separation architecture adopted by the gNB in the existing communication system;
- FIG. 4 is a schematic diagram of a two-hop data backhaul scenario in an existing communication system
- 5 is a schematic diagram of a control plane protocol stack for two-hop data backhaul
- FIG. 6 is a schematic diagram of a user plane protocol stack for two-hop data backhaul
- FIG. 7 is a schematic diagram of an application scenario of a node switching system provided by the present application.
- FIG. 8 is a schematic diagram of an embodiment of a switching system of a node provided by the present application.
- FIG. 9 is a schematic diagram of another embodiment of a node switching system provided by the present application.
- FIG. 10 is a schematic diagram of an embodiment of a node switching method provided by the present application.
- FIG. 11 is a schematic diagram of another embodiment of a node switching method provided by the present application.
- FIG. 12 is a schematic diagram of another embodiment of a node switching method provided by the present application.
- FIG. 13 is a schematic diagram of another embodiment of the node switching method provided by the present application.
- FIG. 14 is a schematic diagram of another embodiment of a node switching method provided by the present application.
- FIG. 15 is a schematic diagram of another embodiment of a node switching method provided by the present application.
- FIG. 16 is a schematic structural diagram of an IAB host node provided by this application.
- FIG. 17 is another schematic structural diagram of the IAB host node provided by the application.
- FIG. 19 is a schematic structural diagram of a communication device provided by the present application.
- words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations. Any embodiments or designs described in the embodiments of the present application as “exemplary” or “such as” should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present the related concepts in a specific manner to facilitate understanding.
- LTE long term evolution
- FDD frequency division duplex
- TDD time division duplex
- 5th generation, 5G fifth generation
- NR new radio
- the gNB A node that provides NR user plane and control plane transmission for terminal equipment, including one or more cells.
- the gNB is connected to the 5G core network (5G Core, 5GC) through the Next Generation (NG) interface, and is connected to other gNBs through the Xn interface.
- the control plane signaling between the two gNBs is transmitted through the Xn control plane (Xn-control, Xn-C) interface, and the user plane data between the two gNBs is transmitted through the Xn user plane (Xn-user, Xn-U) interface transfer.
- the interface between the gNB and the terminal device is called the Uu interface.
- gNB Centralized Unit gNB-Central Unit, gNB-CU: a logical node, including gNB Radio Resource Control (Radio Resource Control, RRC) layer, Service Data Adaptation Protocol (Service Data Adaptation Protocol, SDAP) layer and grouping
- RRC Radio Resource Control
- SDAP Service Data Adaptation Protocol
- PDCP Packet Data Convergence Protocol
- gNB-Distributed Unit gNB-DU
- gNB-DU A logical node, including the radio link control (Radio Link Control, RLC) layer, medium access control (Medium Access Control, MAC) layer and physical (Physical, PHY) layer of the gNB or en-gNB.
- RLC Radio Link Control
- MAC Medium Access Control
- PHY Physical, PHY
- FIG. 1 is a schematic diagram of a separation architecture of a gNB-CU and a gNB-DU in an existing communication system.
- the gNB can adopt a CU-DU separation architecture.
- the gNB consists of one gNB-CU and one or more gNB-DUs.
- the gNB-CU is connected to the gNB-DU through the F1 interface, and the gNB-CU is connected to the 5G core network through the NG interface.
- the terminal device will access the gNB-CU through the gNB-DU, the functions of the PHY layer, MAC layer and RLC layer equivalent to the terminal device are located on the gNB-DU, and the PDCP layer, SDAP layer, RRC layer equivalent to the terminal device The functions of the layers are located on the gNB-CU.
- FIG. 2 is a schematic diagram of a control plane protocol stack under the CU-DU separation architecture adopted by the gNB in the existing communication system.
- the gNB-DU encapsulates the RRC message generated by the terminal device in the F1AP message of the F1 interface and sends it to the gNB-CU.
- the gNB-CU encapsulates the RRC message in the F1AP message and sends it to the gNB-DU.
- the gNB-DU extracts the RRC message from the F1AP message and maps it to the Signalling Radio Bearer (SRB) corresponding to the Uu interface.
- SRB Signalling Radio Bearer
- Sent to the terminal device optionally, the SRB may be SRB0 or SRB1 or SRB2, which is not specifically limited here.
- FIG. 3 is a schematic diagram of a user plane protocol stack under the CU-DU separation architecture adopted by the gNB in the existing communication system.
- the gNB-DU maps the data packets sent by the terminal device received from the Data Radio Bearer (DRB) of the Uu interface to the corresponding GPRS tunnel It is sent to the gNB-CU in the GPRS Tunneling Protocol (GTP) tunnel.
- DRB Data Radio Bearer
- GTP GPRS Tunneling Protocol
- the gNB-CU maps the data packets of the terminal device to the corresponding GTP tunnel and sends them to the gNB-DU.
- the gNB-DU extracts the data packets of the terminal device from the GTP tunnel and maps the data packets of the terminal device to the gNB-DU. It is sent to the terminal device on the DRB corresponding to the Uu interface.
- IAB node IAB node
- IAB host node IAB donor
- the IAB donor can be a gNB, or an upgraded gNB.
- FIG. 4 is a schematic diagram of a two-hop data backhaul scenario in an existing communication system.
- the IAB network adopts the CU-DU separation architecture, that is, the IAB donor is connected to the backhaul integrated host centralized unit (Integrated Access and Backhaul).
- the donor Central Unit, IAB donor-CU) and the integrated access and backhaul host distributed unit (Integrated Access and Backhaul donor Distributed Unit, IAB donor-DU) are composed of two parts, the IAB node is composed of the mobile terminal of the integrated access and backhaul node (Integrated Access and Backhaul node Mobile Terminal, IAB-MT) and access backhaul integrated host distributed unit (Integrated Access and Backhaul node Distributed Unit, IAB-DU) is composed of two parts.
- IAB-MT may also be called IAB-UE.
- donor-DU the function of donor-DU is similar to that of gNB-DU
- donor-CU the function of donor-CU is similar to that of gNB-CU.
- the IAB-DU is similar in function to the gNB-DU, and is used to provide access services for the child nodes of the IAB node, wherein the child nodes of the IAB node can be terminal equipment or other IAB nodes.
- the IAB-MT has the function of a terminal device and is used to provide data backhaul for the child nodes of the IAB node.
- the IAB node can be further divided into an access IAB node and an intermediate IAB node.
- the IAB node accessed by the terminal device is called the access IAB node, and the IAB node on the path between the access IAB node and the IAB donor is called the intermediate IAB node.
- IAB node2 when a terminal device accesses IAB node2, the terminal device is called a child node of IAB node2, and IAB node2 is called the access IAB node or parent node of the terminal device, which is not limited here.
- the link between the terminal equipment and IAB node2 is called the access link.
- IAB node2 is connected to IAB donor through IAB node1, then the previous hop node of IAB node2 is IAB node1, that is, the parent node of IAB node2 is IAB node1, and the child node of IAB node1 is IAB node2.
- IAB node1 is called an intermediate IAB node.
- the last hop node of IAB node1 is IAB donor, that is, the parent node of IAB node1 is IAB donor, and the child node of IAB donor is IAB node1.
- the link between IAB node1 and IAB node2, and the link between IAB node1 and IAB donor are called backhaul links.
- the PHY layer, MAC layer and RLC layer equivalent to the terminal equipment are located on the access IAB node, that is, on the IAB2-DU, and the PDCP layer, SDAP layer and RRC layer equivalent to the terminal equipment are located on the IAB donor-CU.
- the IAB nodes all adopt the architecture of L2 data forwarding, and the specific control plane protocol stack and user plane protocol stack will be described separately below.
- FIG. 5 is a schematic diagram of a control plane protocol stack for two-hop data backhaul.
- the control plane protocol stack an F1 control plane (F1-Control, F1-C) interface is established between the IAB2-DU and the donor-CU-CP.
- F1-Control, F1-C control plane-user plane
- CP-UP control plane-user plane
- an F1-C interface is established between the IAB2-DU and the donor CU-CP.
- the RRC message of the terminal device is encapsulated in the F1AP message and transmitted through the F1-C interface.
- FIG. 6 is a schematic diagram of a user plane protocol stack for two-hop data backhaul.
- F1 user plane (F1-user, F1-U) interface is established between IAB2-DU and donor CU-UP.
- F1-U interface is established between the IAB2-DU and the donor CU-UP, and a GTP tunnel per UE bearer is established on the F1-U interface. That is to say, each UE DRB established on the interface between the UE and the IAB2-DU corresponds to a separate GTP tunnel on the interface between the IAB2-DU and the donor CU-UP.
- the protocol standard of the fifth generation cellular mobile communication system formulated by the third generation partnership project (3GPP) standard organization, compared with the long term evolution (LTE) system, the new radio (New Radio, NR) ) system supports larger transmission bandwidth, more transceiver antenna arrays, higher transmission rate and more flexible scheduling mechanism with smaller granularity.
- 3GPP third generation partnership project
- NR new Radio
- IAB Integrated Access and Backhaul
- the existing switching technology can only realize the switching of the IAB-MT in the IAB node from the source host node to the target host node, but does not involve the IAB-DU in the IAB node and the IAB node.
- the processing of the child node for example: a terminal device or other IAB node, so that the child node of the IAB node will not work normally after the IAB node is switched.
- a source host node sends a switching request message to a target host node.
- the switching request message includes the context information of the IAB node and the context information of at least one terminal device.
- the host node receives the handover response message sent by the target host node, and the handover response message includes the identifier of the accepted terminal device in at least one terminal device, and/or the identifier of the rejected terminal device in at least one terminal device.
- the terminal devices accepted by the target host node are switched to the target host node, while the terminal devices rejected by the target host node will be reselected by the source host node for them to switch target nodes, so that the IAB node Switch to the target host node together with the accepted terminal equipment to ensure the normal transmission of the data of the accepted terminal equipment, and make the rejected terminal equipment switch to the target node that allows it to switch, thereby also ensuring the rejected terminal equipment. normal transmission of data.
- FIG. 7 is a schematic diagram of an application scenario of a node switching system provided by the present application.
- the source host node 101 , the target host node 102 , the IAB node 103 and the terminal device 104 form a node switching system.
- the embodiments of the present application are described by taking a single-hop backhaul link as an example, but the solutions of the application embodiments are also applicable to scenarios of two-hop and multi-hop backhaul links, which are not specifically limited here.
- the terminal device 104 accesses the IAB node 103 and connects to the source host node 101 through the IAB node 103 .
- the IAB node 103 After the IAB node 103 performs node switching, it switches from the source host node 101 to the target host node 102 , and the terminal device 104 is connected to the target host node 102 through the IAB node 103 .
- the source host node is the abbreviation of the source IAB host node
- the target host node is the abbreviation of the target IAB host node
- the source host node and the target host node may be gNBs, and the source host node and the target host node may also be other devices, which are not specifically limited here.
- the terminal device in this embodiment of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing device connected to a wireless modem.
- Terminal devices may be mobile terminals, such as mobile phones (or "cellular" phones) and computers with mobile terminals, for example, may be portable, pocket-sized, hand-held, computer-built, or vehicle-mounted mobile devices, which are connected to a network Devices exchange language and/or data.
- PCS personal communication service
- SIP Session Initiation Protocol
- WLL wireless local loop
- PDAs personal digital assistants
- Terminal equipment may also be referred to as system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, Remote terminal, access terminal, user agent, user device, or user equipment, user station, remote station, terminal equipment (TE) ), terminals, wireless communication devices, and user agents or user equipment.
- the terminal device may also be a chip system for implementing UE functions. There is no specific limitation here.
- the switching system provided by the embodiment of the present application, only the topology relationship of one terminal device and one IAB node is used for illustration, and the switching system may also include more terminal devices and more IAB nodes, specifically here Not limited.
- FIG. 8 is a schematic diagram of an embodiment of a switching system of a node provided by the present application.
- the terminal device can be directly connected to the IAB node.
- the terminal device may also be connected to the IAB node through other IAB nodes such as IAB node A, IAB node B, etc., which is not specifically limited here.
- FIG. 9 is a schematic diagram of an embodiment of a switching system of a node provided by the present application.
- the direct connection between the terminal device and the IAB node is used as an example for description.
- the IAB node can be directly connected to the source host node or the target host node, the IAB node can also be connected to the source host node through at least one IAB node such as IAB node A, or the IAB node can also be connected through at least one IAB node such as IAB node B.
- the node is connected to the target host node, which is not limited here.
- the IAB node described in the following embodiments may be the IAB node that triggers the handover, and the IAB node that triggers the handover may be called the migrating IAB node (migrating IAB node), and the other IAB nodes are The next-hop child node or multi-hop grandchild node or grand-grandchild node of the IAB node (switching IAB node) is not specifically limited here.
- the terminal device can be directly connected to the switching IAB node.
- the terminal device may also be connected to the handover IAB node through other IAB nodes such as IAB node A, IAB node B, and the like.
- the handover IAB node may be directly connected to the source host node, or the handover IAB node may also be connected to the source host node through at least one IAB node such as IAB node C.
- the switching IAB node can be directly connected to the target host node, or, the switching IAB node can also be connected to the target host node through at least one IAB node such as IAB node D, that is, the solutions shown in Figures 8 and 9 can be combined with each other, There is no specific limitation here.
- FIG. 10 is a schematic diagram of an embodiment of a node switching method provided by the present application.
- an embodiment of the node switching method provided in this application includes steps 201 to 202 .
- the source host node sends a handover request message to the target host node, and similarly, the target host node receives the handover request message sent by the source host node.
- the handover request message is used to request that the IAB node and at least one terminal device be handed over to the target host node.
- the handover request message includes the context information of the IAB node and the context information of at least one terminal device.
- the source host node sends a handover request message to the target host node.
- the handover request message includes the context information of the IAB node and the context information of at least one terminal device; if the terminal device is connected to the IAB node through at least one other IAB node, the handover request message contains Also includes contextual information for other IAB nodes.
- the source host node sends multiple handover request messages to the target host node, and each handover request message includes context information of a node. If the terminal device is directly connected to the IAB node, that is, the context information of the IAB node is carried in a separate handover request message, the context information of one terminal device is carried in a separate handover request message, and the context information of different terminal devices is carried in a separate handover request message.
- the target host node After receiving the handover request message, according to its own network load, etc., if the terminal device is directly connected to the IAB node, the target host node decides whether to accept the IAB node and at least one terminal device to switch together; if the terminal device passes at least one If other IAB nodes are connected to the IAB node, the target host node decides whether to accept the IAB node, at least one other IAB node and at least one terminal device to be handed over together.
- the source host node receives the handover response message sent by the target host node, and similarly, the target host node sends the handover response message to the source host node.
- the handover response message includes an identifier of an accepted terminal device in at least one terminal device, and/or an identifier of a rejected terminal device in at least one terminal device.
- the target host node sends a handover response message to the source host node.
- the handover response message includes the identifier of the accepted terminal device in at least one terminal device, and/or the identifier of the rejected terminal device in at least one terminal device; if the terminal device passes through at least one terminal device
- the handover response message also includes the identification of at least one other IAB node that is accepted in the other IAB node, and/or, the identification of the other IAB node that is rejected in at least one other IAB node .
- the target host node sends multiple handover response messages to the source host node, and each handover response message corresponds to a node.
- the terminal device is directly connected to the IAB node, that is, the IAB node corresponds to a separate handover response message, one terminal device corresponds to a separate handover response message, and different terminal devices correspond to different handover response messages.
- the handover response message corresponding to the accepted terminal device includes the identifier of the accepted terminal device, and the handover response message corresponding to the rejected terminal device is a handover rejection message or a handover preparation failure message or a handover failure message, and the message includes The identity of the rejected end device.
- the message also includes the reason for rejection; if the terminal device is connected to the IAB node through at least one other IAB node, that is, except that the IAB node and at least one terminal device respectively correspond to a separate handover response message, one other IAB
- the node also corresponds to a separate handover response message, and different other IAB nodes correspond to different handover response messages.
- the handover response messages corresponding to the other IAB nodes that are accepted include the identifiers of the other IAB nodes that are accepted, and the handover response messages corresponding to the other IAB nodes that are rejected are the handover rejection message or the handover preparation failure message or the handover failure message.
- the message includes the identities of other IAB nodes that were rejected.
- the message also includes the reason for rejection. The reason for rejection may be due to insufficient resources of the target host node, and the network load of the target host node cannot bear all other IAB nodes requesting handover or all terminal devices requesting handover. .
- the reason for rejection may also be that the node identifier (for example: UE XnAP ID) sent by the source host node is unavailable, and the target host cannot recognize the node identifier sent by the source host node.
- the reasons for rejection can also be other reasons, which are not limited here.
- the source host node in addition to the above steps 201 to 202, before the source host node sends the handover request message to the target host node, the source host node also receives the measurement result sent by the IAB node, and this step will be described in the following embodiments. Explain in detail.
- the source host node receives the measurement results sent by the IAB node.
- the measurement result includes the result A of measuring the signal quality of the serving cell managed by the source donor node by the IAB node and the result B of measuring the signal quality of the neighboring cell managed by the target donor node by the IAB node.
- the measurement result includes reference signal receiving power (RSRP), and/or reference signal receiving quality (reference signal receiving quality, RSRQ), which is not specifically limited here.
- RSRP reference signal receiving power
- RSRQ reference signal receiving quality
- the source host node determines to switch the IAB node and at least one terminal device to the target host node according to the measurement result.
- the source host node confirms that result A is better than result B, it can be seen that the signal quality of the serving cell is better than that of the neighboring cell, and the source host node does not need to send a handover request message to the target host node.
- the IAB node does not work in the CA mode, there is a serving cell. If the signal quality B of a neighbor cell is higher than the signal quality A of the serving cell, the source host node determines the IAB node and at least one terminal device according to the measurement result. Switch to the target host node; if the IAB node works in CA mode, the serving cell includes a primary cell and at least one secondary cell. If the signal quality B of a neighbor cell is higher than the signal quality A of the primary cell, the source host node According to the measurement result, it is determined to switch the IAB node and at least one terminal device to the target host node.
- the source host node uses the IAB node and at least one terminal device as a group, and switches all members in the group to the target host node together. If the source host node sends multiple handover request messages to the target host node, the source host node also needs to send an indication message to the target host node, the indication information is used to indicate the number of members in the group, so that the target host node can determine The number of handover request messages to be received, that is, one member corresponds to one handover request message.
- the source host node receives the measurement results sent by the IAB node.
- the measurement result includes the result A of measuring the signal quality of the serving cell managed by the source donor node by the IAB node and the result B of measuring the signal quality of the neighboring cell managed by the target donor node by the IAB node.
- the measurement result includes RSRP and/or RSRQ, which is not specifically limited here.
- the source host node determines to switch the IAB node, at least one other IAB node and at least one terminal device to the target host node according to the measurement result.
- the source host node confirms that result A is better than result B, it can be seen that the signal quality of the serving cell is better than that of the neighboring cell, and the source host node does not need to send a handover request message to the target host node. If the IAB node does not work in CA mode, there is a serving cell.
- the source host node can determine the IAB node, at least one other The IAB node and at least one terminal device switch to the target host node; if the IAB node works in the CA mode, the serving cell includes a primary cell and at least one secondary cell, if the signal quality B of a neighbor cell is higher than that of the primary cell If the quality is A, the source host node can determine to switch the IAB node, at least one other IAB node and at least one terminal device to the target host node according to the measurement result.
- the source host node regards the IAB node, at least one other IAB node and at least one terminal device as a group, and switches all members in the group to the target host node together. If the source host node sends multiple handover request messages to the target host node, the source host node also sends an indication message to the target host node, the indication information is used to indicate the number of members in the group, so that the target host node can determine the The number of received handover request messages, that is, one member corresponds to one handover request message.
- the context information of the IAB node and the context information of other IAB nodes include a variety of different parameters, which will be specifically described in the following embodiments.
- the IAB node includes IAB-MT and IAB-DU
- the context information of the IAB node includes the context information of the IAB-MT and the context information of the IAB-DU
- the context information of the IAB-MT includes the IAB-MT and the IAB
- the configuration information of the backhaul radio link control channel (BH RLC CH) between the parent nodes of the node, the context information of the IAB-DU includes the identifier of the IAB-DU and/or the cell identifier of the IAB-DU .
- the context information of the IAB-DU may also include activation indication information of the cell of the IAB-DU, and the activation indication information is used to indicate whether the cell of the IAB-DU has been activated, wherein each cell of the IAB-DU corresponds to one Separate activation instructions.
- the context information of the IAB node further includes a backhaul adaptation protocol (backhaul adaptation protocol, BAP) address allocated by the source host node to the IAB node.
- BAP backhaul adaptation protocol
- the context information of the terminal device includes the identifier of the terminal device, and the identifier of the terminal device includes the physical cell identifier (PCI) of the cell accessed by the terminal device and the identifier of the terminal device in the access cell ( cell-radio network temporary identifier, C-RNTI).
- PCI physical cell identifier
- C-RNTI cell-radio network temporary identifier
- other IAB nodes include other IAB-MTs and other IAB-DUs
- context information of other IAB nodes includes context information of other IAB-MTs and context information of other IAB-DUs.
- the context information of the other IAB-MT includes the configuration information of the BH RLC CH between the other IAB-MT and the parent node of the other IAB node.
- the context information of other IAB-DUs includes the identities of other IAB-DUs and/or the cell identities of other IAB-DUs.
- the context information of other IAB-DUs also includes activation indication information of cells of other IAB-DUs, and the activation indication information of cells of other IAB-DUs is used to indicate whether cells of other IAB-DUs have been activated, wherein, Each cell of other IAB-DUs corresponds to a separate activation indication message.
- the context information of other IAB nodes further includes BAP addresses allocated by the source host node to other IAB nodes.
- the context information of the IAB node and the context information of other IAB nodes also include the topology relationship between the IAB node and other IAB nodes and terminal devices, and the specific implementation will be described in the following embodiments.
- the context information of the IAB node further includes the identifier of the child node (or next hop node) of the IAB node, which is used to indicate the topology relationship between the IAB node and the child node (or next hop node) of the IAB node.
- the terminal device is directly connected to the IAB node, the child node (or next-hop node) of the IAB node is the terminal device, and the identifier of the child node (or next-hop node) of the IAB node is the identifier of the terminal device.
- the identifier of the terminal device may be the user equipment Xn application layer protocol identifier (user equipment Xn application protocol identity, UE XnAP ID), which is not specifically limited here.
- the context information of the terminal device may also include the identifier of the parent node (or the previous hop node) of the terminal device, which is used to indicate the topology between the terminal device and the parent node (or the previous hop node) of the terminal device.
- the parent node (or previous hop node) of the terminal device is the IAB node
- the identifier of the parent node (or previous hop node) of the terminal device is the identifier of the IAB node.
- the identifier of the IAB node may be the UE XnAP ID, or may be the BAP address of the IAB node, which is not specifically limited here.
- the context information of the IAB node may also include network topology list information. Since the terminal device is directly connected to the IAB node, the network topology list information is used to indicate the topology relationship between the IAB node and the terminal device. For example, if the terminal device is connected to the IAB node, the network topology list information includes the identifier of the IAB node and the identifier of the child node (or next-hop node) of the IAB node (that is, the identifier of the terminal device), or the network topology list information includes the terminal device. The identification of the device, and the identification of the parent node (or the previous hop node) of the terminal device (ie, the identification of the IAB node). Wherein, the identifier of the terminal device may be the UE XnAP ID, and the identifier of the IAB node may also be the UE XnAP ID or the BAP address, which is not specifically limited here.
- the network topology list information may not be carried in the context information of the IAB node, but directly carried in the handover request message sent by the source host node to the target host node, which is not specifically limited here.
- the target host node can acquire the topology relationship between the IAB node and the terminal device.
- the target host node may also obtain the topology relationship between the IAB node and the terminal device in other manners, which are not specifically limited here.
- the context information of the IAB node further includes the identifier of the child node (or next hop node) of the IAB node, which is used to indicate the topology relationship between the IAB node and the child node (or next hop node) of the IAB node. Since the terminal device is connected to the IAB node through at least one other IAB node, the child node (or next-hop node) of the IAB node is the other IAB node, and the identifier of the child node (or next-hop node) of the IAB node is other The ID of the IAB node.
- the identifiers of other IAB nodes may be UE XnAP IDs, or may be BAP addresses of other IAB nodes, which are not specifically limited here.
- the context information of other IAB nodes also includes the identity of the parent node (or previous hop node) of other IAB nodes, and/or the identity of the child nodes (or next hop node) of other IAB nodes, for Indicates the topology relationship between other IAB nodes and parent nodes (or previous-hop nodes) of other IAB nodes, and/or between other IAB nodes and child nodes (or next-hop nodes) of other IAB nodes.
- the terminal device is connected to the IAB node through at least one other IAB node, for example: the terminal device is connected to the IAB node through the IAB node A, at this time the other IAB node is the IAB node A, the parent node (or the previous hop node) of the other IAB nodes. It is the IAB node, and the identifier of the parent node (or the previous hop node) of other IAB nodes is the identifier of the IAB node.
- the child nodes (or next-hop nodes) of other IAB nodes are terminal devices, and the identifiers of the child nodes (or next-hop nodes) of other IAB nodes are identifiers of terminal devices.
- the identifier of the terminal device may be the UE XnAP ID
- the identifier of the IAB node may also be the UE XnAP ID or the BAP address, which is not specifically limited here.
- the context information of the terminal device also includes the identifier of the parent node (or the previous hop node) of the terminal device, which is used to indicate the topology relationship between the terminal device and the parent node (or the previous hop node) of the terminal device. . Since the terminal device is connected to the IAB node through at least one other IAB node, the parent node (or the previous hop node) of the terminal device is the other IAB node, and the identity of the parent node (or the previous hop node) of the terminal device is the other The ID of the IAB node.
- the identifiers of other IAB nodes may be UE XnAP IDs, or may be BAP addresses of other IAB nodes, which are not specifically limited here.
- the context information of the IAB node also includes network topology list information. Since the terminal device is connected to the IAB node through at least one other IAB node, the network topology list information is used to indicate the topology relationship between the IAB node, other IAB nodes and the terminal device .
- the network topology list information includes two sets of lists, and the first set of lists includes the identifier of the IAB node and the identifier of the child node (or the next hop node) of the IAB node, wherein, The child node of the IAB node is the IAB node A, then the identifier of the child node (or the next hop node) of the IAB node is the identifier of the IAB node A; the second group list includes the identifier of the IAB node A and the child node of the IAB node A ( or next-hop node) identifier, wherein, the child node (or next-hop node) of IAB node A is a terminal device, then the identifier of the child node (or next-hop node) of IAB node A is the identifier of the terminal device.
- the network topology list information includes two sets of lists, and the first set of lists includes the identifier of the terminal device and the identifier of the parent node (or the previous hop node) of the terminal device, wherein the parent node of the terminal device is the IAB node A, then the terminal The identifier of the parent node (or the previous hop node) of the device is the identifier of the IAB node A; the second group list includes the identifier of the IAB node A and the identifier of the parent node (or the previous hop node) of the IAB node A, wherein the IAB If the parent node (or the previous hop node) of the node A is the IAB node, the identifier of the parent node (or the previous hop node) of the IAB node A is the identifier of the IAB node.
- the identifier of the terminal device can be the UE XnAP ID
- the identifier of the IAB node can also be the UE XnAP ID or the BAP address
- the identifier of other IAB nodes (for example: IAB node A) can also be the UE XnAP ID or the BAP address.
- the network topology list information may not be carried in the context information of the IAB node, but directly carried in the handover request message sent by the source host node to the target host node, which is not specifically limited here.
- the target host node acquires the topology relationship among the IAB node, other IAB nodes, and the terminal device.
- the target host node can also obtain the topology relationship between the IAB node, other IAB nodes, and terminal devices in other ways, which are not specifically limited here. .
- FIG. 11 is a schematic diagram of an embodiment of a method for switching a node provided by the present application.
- the terminal device is connected to the IAB node through the IAB node B and the IAB node A.
- the context information of the IAB node includes the identifier of the child node of the IAB node (that is, the identifier of the IAB node A), and the context information of the IAB node A includes the identifier of the child node of the IAB node A.
- the context information of the IAB node B includes the child node identifier of the IAB node B (ie: the identifier of the terminal device), in this way, the target host node will send the target host node according to the source host node.
- the context information carried in the handover request message is used to learn the topology relationship among the IAB node, the IAB node A, the IAB node B and the terminal device.
- the context information of the IAB node A includes the parent node identifier of the IAB node A (that is, the identifier of the IAB node), and the context information of the IAB node B includes the parent node of the IAB node B.
- the node identifier ie: the identifier of the IAB node A
- the context information of the terminal device includes the parent node identifier of the terminal device (ie: the identifier of the IAB node B).
- the target host node learns the topology relationship among the IAB node, IAB node A, IAB node B and the terminal device according to the context information carried in the handover request message sent by the source host node to the target host node.
- the context information of the IAB node includes the child node identifier of the IAB node (that is, the identifier of the IAB node A), and the context information of the IAB node A includes the parent node of the IAB node A.
- the identifier (ie: the identifier of the IAB node) and the child node identifier of the IAB node A (ie: the identifier of the IAB node B)
- the context of the IAB node B includes the parent node identifier of the IAB node B (ie: the identifier of the IAB node A) and the identifier of the child node of the IAB node B (that is, the identifier of the terminal device)
- the context information of the terminal device includes the identifier of the parent node of the terminal device (that is, the identifier of the IAB node B).
- the target host node learns the topology relationship among the IAB node, IAB node A, IAB node B and the terminal device according to the context information carried in the handover request message sent by the source host node to the target host node.
- the network topology relationship between the IAB node, other IAB nodes, and terminal devices may be described by node identifiers, and other implementation manners may also be used, which are not specifically limited here.
- the topology information may also be carried in the handover request message sent by the source host node to the target host node, that is, the handover request message sent by the source host node to the target host node may also include the network The topology list information, the network topology list information is used to indicate the topology relationship between the IAB node, the IAB node A, the IAB node B and the terminal device.
- the network topology list information includes three groups of lists, the first group of lists includes the identifier of the IAB node and the identifier of the child nodes of the IAB node (ie: the identifier of the IAB node A), and the second group of lists includes the identifier of the IAB node A and the IAB node.
- the identifier of the child node of A that is, the identifier of the IAB node B
- the third group list includes the identifier of the IAB node B and the identifier of the child node of the IAB node B (that is, the identifier of the terminal device).
- the first set of lists includes the identity of IAB node A and the identity of the parent node of IAB node A (ie: the identity of the IAB node), and the second set of lists includes the identity of IAB node B and the parent node identity of IAB node B (ie: The identifier of the IAB node A), the third group list includes the identifier of the terminal device and the parent node identifier of the terminal device (ie: the identifier of the IAB node B).
- the identifier of the terminal device may be the UE XnAP ID
- the identifier of the IAB node may also be the UE XnAP ID or the BAP address
- the identifier of the IAB node A may be the UE XnAP ID or the BAP address
- the identifier of the IAB node B may be It is the UE XnAP ID or BAP address, which is not limited here.
- the target host node can acquire the topology relationship among the IAB node, other IAB nodes, and the terminal device.
- the target host node may also acquire the topology relationship among the IAB node, other IAB nodes, and terminal devices in other ways, which are not specifically limited here.
- the source host node can carry the context information of the IAB node and the context information of the terminal device in a handover request message and send it to the target host node, or, the IAB node can also be sent to the target host node.
- the context information of the node and the context information of the terminal device are respectively carried in different handover request messages and sent to the target host node, which is not specifically limited here.
- the source host node can carry the context information of the IAB node, the context information of other IAB nodes, and the context information of the terminal device in a handover request message to send.
- the target host node or, the context information of the IAB node, the context information of other IAB nodes, and the context information of the terminal device may be carried in different handover request messages and sent to the target host node, which is not limited here.
- the cell configuration information after the first IAB node is switched to the target host node is changed, and the first IAB node includes the IAB node and other IAB nodes that are accepted by other IAB nodes. node.
- the IAB node receives the updated cell configuration information from the target host node through the source host node in various implementation manners, and the specific implementation manner will be described in detail in the following embodiments.
- FIG. 12 is a schematic diagram of an embodiment of the source host node sending configuration information in the node switching method provided by the present application.
- the source host node includes a source Donor-CU
- the target host node includes a target Donor-CU
- the first IAB node includes a first IAB-MT and a first IAB-DU.
- the target Donor-CU sends a handover response message to the source host node.
- the target Donor-CU updates the cell configuration of the first IAB node.
- the target Donor-CU can update the cell global of the IAB-DU.
- Identity cell group identifier, CGI
- the target Donor-CU can also update the cell identity (Cell Identity) of the IAB-DU, which is not limited here.
- the updated cell configuration is carried in the handover response message, and the handover response message is sent to the source Donor-CU.
- the handover response message includes the first RRC message generated by the target Donor-CU, the first RRC message includes the cell configuration information after the first IAB node is handed over to the target host node, and the first IAB node includes the IAB node and other IAB nodes. Other IAB nodes accepted in .
- the source Donor-CU obtains the first radio resource control RRC message from the handover response message.
- the source Donor-CU sends the first RRC message to the first IAB-MT through the source Donor-DU.
- the target Donor-CU carries the updated cell configuration information of the first IAB-DU in the first RRC message (RRC Reconfiguration) generated by the target Donor-CU, and then encapsulates the first RRC message
- the Handover Request Acknowledge message is sent to the source Donor-CU.
- the source Donor-CU After extracting the first RRC message from the handover response message, the source Donor-CU sends the first RRC message to the first IAB-MT through the source Donor-DU.
- the first IAB-MT extracts the updated cell configuration of the first IAB-DU from the first RRC message, and sends the received updated cell configuration of the first IAB-DU to the first IAB-DU through the internal interface. DU, so that the first IAB-DU updates the cell configuration.
- the cell configuration of the first IAB-DU is updated, for example: the first IAB-DU cell identifier CGI or the base station identifier included in the Cell Identity is the same as the Donor-DU.
- the identity of the base station to which the CU belongs shall be consistent.
- the first IAB-DU acquires new configuration information from the target Donor-CU.
- FIG. 13 is a schematic diagram of an embodiment of the source host node sending configuration information in the node switching method provided by the present application.
- the source host node includes a source Donor-CU
- the target host node includes a target Donor-CU
- the first IAB node includes a first IAB-MT and a first IAB-DU.
- the target Donor-CU sends a handover response message to the source host node.
- the handover response message includes a first F1AP message
- the first F1AP message includes cell configuration information after the first IAB node is handed over to the target host node
- the first IAB node includes the IAB node and other IAB nodes that are accepted other IAB nodes.
- the source Donor-CU obtains the F1AP message of the first application layer protocol from the handover response message.
- the source Donor-CU encapsulates the first F1AP message in the second F1AP message and sends it to the first IAB-DU.
- the source Donor-CU after the source Donor-CU encapsulates the first F1AP message in the second F1AP message, the source Donor-CU sends the second F1AP message to the first IAB-DU, so that the first IAB-DU updates the cell configuration.
- the target Donor-CU carries the updated cell configuration information of the first IAB-DU in the first F1AP message generated by the target Donor-CU.
- the first F1AP message It can be a newly defined F1AP message, or it can also be an existing F1AP message, such as a gNB configuration update message (gNB-CU Configuration Update), which is not specifically limited here.
- the target Donor-CU carries the F1AP message in the Handover Request Acknowledge message and sends it to the source Donor-CU.
- the source Donor-CU extracts the first F1AP message from the Handover Request Acknowledge message, and carries the first F1AP message in the second F1AP message and sends it to the first IAB-DU through the source Donor-DU.
- the first IAB-DU extracts the first F1AP message generated by the target Donor-CU from the second F1AP message, so that the first IAB-DU updates the cell configuration.
- the cell configuration of the first IAB-DU is updated, for example: the cell identity CGI of the first IAB-DU or the base station identity contained in the Cell Identity and the Donor -
- the identity of the base station to which the CU belongs shall be consistent.
- the first IAB-DU acquires new configuration information from the target Donor-CU.
- the embodiment provided in FIG. 13 in this application has an impact on the existing IAB protocol stack.
- the protocol stack architecture corresponding to the embodiment provided in FIG. 13 in this application is shown in FIG. 14 , that is, the F1AP message carries the F1AP message.
- FIG. 14 is a schematic diagram of the protocol stack architecture of the source host node sending configuration information in the node switching method provided by the present application.
- FIG. 15 is a schematic diagram of an embodiment of the source host node sending configuration information in the node switching method provided by the present application.
- the source host node includes a source Donor-CU
- the target host node includes a target Donor-CU
- the first IAB node includes a first IAB-MT and a first IAB-DU.
- the target Donor-CU sends a handover response message to the source host node.
- the handover response message includes the cell configuration information after the first IAB node is handed over to the target host node, and the first IAB node includes the IAB node and other IAB nodes that are accepted in other IAB nodes.
- the source Donor-CU acquires the cell configuration information after the first IAB node is handed over to the target host node from the handover response message.
- the source Donor-CU encapsulates the cell configuration information after the first IAB node is handed over to the target donor node in an F1AP message and sends it to the first IAB-DU.
- the target Donor-CU carries the updated cell configuration information of the first IAB-DU in a Handover Request Acknowledge message and sends it to the source Donor-CU.
- the source Donor-CU extracts the updated cell configuration information of the first IAB-DU from the Handover Request Acknowledge message, and carries the updated cell configuration information of the first IAB-DU in the F1AP message generated by the source Donor-CU Sent to the first IAB-DU so that the first IAB-DU can update the cell configuration.
- the F1AP message generated by the source Donor-CU may be a newly defined message, or may also be an existing F1AP message, such as a gNB-CU Configuration Update message, which is not specifically limited here.
- the cell configuration of the first IAB-DU is updated, for example: the cell identity CGI of the first IAB-DU or the base station identity contained in the Cell Identity and the Donor -
- the identity of the base station to which the CU belongs shall be consistent.
- the first IAB-DU acquires new configuration information from the target Donor-CU.
- FIG. 12 to FIG. 15 illustrate three ways of sending cell configuration information.
- the target Donor-CU can also send the first IAB node to the first IAB node to switch to the target host in other ways.
- the cell configuration information behind the node is not specifically limited here.
- FIGS. 12 to 15 may be implemented based on the embodiments described in steps 201 and 202 , or may not be implemented independently based on the embodiments described in steps 201 and 202 , which are not specifically limited here.
- the target host node in addition to the above steps 201 to 202, the target host node also sends a context establishment request message to the IAB node, and this step will be described in detail in the following embodiments.
- the source host node includes the source Donor-CU
- the target host node includes the target Donor-CU
- the target Donor-CU sends a context establishment request message to the IAB node.
- the context establishment request message carries the identifier of the terminal equipment
- the identifier of the terminal equipment includes the cell identifier of the terminal equipment accessing the IAB node and the identifier C-RNTI of the terminal equipment in the access cell.
- the terminal equipment The cell identifier of the device accessing the IAB node may be PCI, or may also be CGI, or may also be other identifiers, which are not specifically limited here.
- the context of the child node of the IAB node is established between the IAB node and the target Donor-CU.
- the child node of the IAB node is a terminal device, that is, a context of the terminal device is established between the IAB node and the target Donor-CU.
- the cell identifier PCI of the IAB-DU of the IAB node remains unchanged, and the identifier C-RNTI of the terminal device in the IAB-DU cell remains unchanged.
- the target Donor-CU sends a context setup request message (UE Context Setup Request) to the IAB-DU of the IAB node.
- the identifier of the DU cell optionally, the identifier may be a combination of PCI and C-RNTI, or may be a combination of CGI and C-RNTI, which is not specifically limited here.
- the CGI may be the cell identifier of the IAB-DU of the IAB node under the source host node, or may be the cell identifier of the IAB-DU of the IAB node under the target host node. According to the identification of the terminal device under the IAB-DU cell of the IAB node, the IAB-DU of the IAB node can know which terminal device the UE Context Setup Request message is used to request to establish a context for.
- the target Donor-CU sends a context establishment request message to the second IAB node, where the second IAB node is the access node or parent node of the terminal device, that is: one other IAB node in at least one other IAB node accessed by the terminal device, the context
- the establishment request message carries the identity of the terminal equipment, the identity of the terminal equipment is the cell identity of the terminal equipment accessing one other IAB node in at least one other IAB node and the identity C-RNTI of the terminal equipment in the access cell, optional , the cell identifier of the terminal device accessing the second IAB node may be PCI, or may be CGI, or may also be other identifiers, which are not specifically limited here.
- the context of the child node of the second IAB node is established between the second IAB node and the target Donor-CU.
- the child node of the second IAB node is a terminal device, that is, a context of the terminal device is established between the second IAB node and the target Donor-CU.
- the target Donor-CU sends a context setup request message (UE Context Setup Request) to the IAB-DU of the second IAB node.
- UE Context Setup Request UE Context Setup Request
- the identifier under the IAB-DU cell of the second IAB node optionally, the identifier may be PCI and C-RNTI, or may be CGI and C-RNTI, which is not specifically limited here.
- the CGI may be the cell identifier of the IAB-DU of the second IAB node under the source host node, or may be the cell identifier of the IAB-DU of the second IAB node under the target host node. According to the identification of the terminal device under the IAB-DU cell of the second IAB node, the IAB-DU of the second IAB node can know which terminal device the UE Context Setup Request message is used to request to establish a context for.
- the multiple different embodiments contained in the context establishment request message sent by the target host node to the IAB node may be implemented based on the embodiments described in steps 201 and 202, or may not be independent based on the embodiments described in steps 201 and 202. Implementation is not specifically limited here.
- the target host node or the IAB node in addition to the above steps 201 to 202, if the terminal device is connected to the IAB node through at least one other IAB node, the target host node or the IAB node also sends the first indication information and/or the first indication information and/or the first indication information to the other IAB nodes.
- Two indication information the first indication information is used to indicate that the handover of the IAB node is completed.
- the second indication information is used to indicate that the IAB node is switching or preparing to switch.
- the processing of the application layer may be that the IAB-DU of other IAB nodes triggers the establishment of a stream control transmission protocol (SCTP) association with the target host node (for example, the target Donor-CU), or, it can also be It is the IAB-DU of other IAB nodes that triggers a request to the operation administration and maintenance (OAM) server to obtain a new configuration, or it may be other processing methods, which are not limited here.
- SCTP stream control transmission protocol
- OAM operation administration and maintenance
- the link between the IAB node and the target host node is blocked. Since the IAB node has not completed the handover, it means that the IAB node has not successfully switched to the target host node, then the IAB node The air interface link between the node and the target host node has not been established, and the bearer mapping and routing on the link between the IAB node and the target host node are not configured, so data transmission cannot be performed. Therefore, it can be considered that the link is blocked. of.
- the IAB-DUs of other IAB nodes trigger the processing of the application layer at this time and trigger the SCTP association establishment request to the target host node (for example: Donor-CU), the IAB-DUs of other IAB nodes will be unable to receive the target host node.
- the sent response to the SCTP association request leads to the belief that the underlying link is unreachable, so that the SCTP association establishment process fails.
- the target host node or IAB node may send first indication information and/or second indication information to other IAB nodes, where the first indication information is used to instruct the IAB node to complete the handover, that is, to switch to the target host node.
- the second indication information is used to indicate that the IAB node is switching or preparing to switch.
- the other IAB nodes may be child nodes, or grandchildren, or grandchildren nodes of the IAB node.
- Manner 1 The target host node sends the first indication information and/or the second indication information to other IAB nodes.
- the target host node includes the target Donor-CU
- the IAB node includes IAB-MT1 and IAB-DU1
- other IAB nodes include IAB-MT2 and IAB-DU2.
- the target donor-CU sends the second indication information to other IAB nodes.
- the target Donor-CU after the target Donor-CU receives the handover request message sent by the source Donor-CU, and learns that the IAB node and other IAB nodes will be handed over to the target Donor-CU together, the target Donor-CU sends the message sent by the target Donor-CU to the other IAB nodes.
- the RRC reconfiguration message (or the handover command message) carries the second indication information, which is used to indicate that the IAB node is ready for handover or is handing over.
- the target donor-CU sends the first indication information to other IAB nodes.
- the target Donor-CU sends first indication information to the IAB-MT2, where the first indication information is used to indicate The switching of the IAB node is completed, that is, it has been switched to the target host node.
- the target host node after the IAB node is successfully handed over to the target host node, or, after the IAB-MT1 receives the BAP configuration information of the target Donor-CU (for example, routing configuration information and/or bearer mapping configuration information of the BAP layer, etc.), the target The Donor-CU sends the first indication information to the IAB-MT2, where the first indication information is carried in the RRC message and sent.
- the BAP configuration information of the target Donor-CU for example, routing configuration information and/or bearer mapping configuration information of the BAP layer, etc.
- the IAB node sends the first indication information and/or the second indication information to other IAB nodes.
- the target host node includes the target Donor-CU
- the IAB node includes IAB-MT1 and IAB-DU1
- other IAB nodes include IAB-MT2 and IAB-DU2.
- the IAB node sends second indication information to other IAB nodes.
- IAB-DU1 sends second indication information to IAB-MT2, and the indication information is used to indicate that IAB-MT1 is handing over or IAB-MT1 is switching MT1 is ready to switch.
- the IAB-DU1 may carry the second indication information in the MAC CE and send it to the IAB-MT2, or it may also carry it in the BAP control PDU and send it to the IAB-MT2. Do limit.
- the IAB node sends the first indication information to other IAB nodes.
- IAB-MT1 after IAB-MT1 successfully switches to the target Donor-CU, or after IAB-MT1 receives the BAP configuration information of the target host node (for example: target Donor-CU), IAB-DU1 sends the first message to IAB-MT2. Instructions.
- the BAP configuration information may include routing configuration information of the BAP layer, or may include bearer mapping configuration information, and the BAP configuration information may also include other configuration information, which is not specifically limited here.
- the IAB-DU1 may carry the first indication information in the MAC CE and send it to the IAB-MT2, or it may also carry the first indication information in the BAP control PDU and send it to the IAB-MT2, specifically here Not limited.
- the multiple different embodiments contained in the above-mentioned target host node or IAB node sending the first indication information and/or the second indication information to other IAB nodes may be implemented based on the embodiments described in steps 201 and 202, or may not be based on The embodiments described in step 201 and step 202 are independently implemented, and are not specifically limited here.
- the above embodiments provide different implementations of a node switching method.
- the following provides an IAB host node 30, as shown in FIG. 16, the IAB host node 30 is used to perform the steps performed by the source host node in the above embodiment , the execution steps and the corresponding beneficial effects can be understood with reference to the above-mentioned corresponding embodiments, which will not be repeated here.
- the IAB host node 30 includes:
- a sending unit 301 a receiving unit 302 and a processing unit 303;
- a sending unit 301 configured to perform the sending action of the source host node in the node switching method provided in any possible implementation manner in the foregoing embodiment
- a receiving unit 302 configured to perform the receiving action of the source host node in the node switching method provided in any possible implementation manner in the foregoing embodiment
- the processing unit 303 is configured to perform the processing action of the source host node in the node switching method provided in any possible implementation manner of the foregoing embodiment.
- the IAB host node 30 includes a processing unit and a transceiver unit, and the transceiver unit may include a sending unit 301 and a receiving unit 302 .
- the transceiver unit may be a transceiver
- the transceiver may include an antenna, a radio frequency circuit, etc.
- the processing unit 303 may be a processor (or a processing circuit), such as a baseband processor, and the baseband processor may include one or more Central processing unit (central processing unit, CPU).
- the transceiver unit may be a radio frequency unit, and the processing unit may be a processor (or a processing circuit), such as a baseband processor.
- the transceiver unit may be an input/output interface of a chip (eg, a baseband chip), and the processing unit 303 may be a processor (or a processing circuit) of the chip system, which may include one or more central processing units unit.
- processing unit in the embodiments of the present application may be implemented by a processor or a processor-related circuit component (or, a processing circuit), and the transceiver unit may be implemented by a transceiver or a transceiver-related circuit component.
- the transceiver unit may be a functional module, which can perform both sending and receiving operations.
- the transceiver unit may be used to execute any one of the embodiments shown in FIG. 2 to the embodiments shown in FIG. 15 . All sending operations and receiving operations performed by the source host node in the embodiment, for example, when performing a sending operation, the transceiver unit can be considered to be a sending module, and when performing a receiving operation, it can be considered that the transceiver unit is a receiving module; or,
- the transceiver unit can also be two functional modules, and the transceiver unit can be regarded as the general name of the two functional modules.
- the two functional modules are respectively the sending unit 301 and the receiving unit 302.
- the sending unit 301 is used to complete the sending operation, for example, the sending module It can be used to perform all the sending operations performed by the source host node or the target host node in any of the embodiments shown in FIG. 2 to the embodiments shown in FIG. 15 , and the receiving module is used to complete the receiving operation, for example
- the receiving unit may be configured to perform all receiving operations performed by the source host node or the target host node in any one of the embodiments shown in FIG. 2 to the embodiment shown in FIG. 15 .
- the above embodiments provide different implementations of the IAB host node 30.
- the following provides an IAB host node 40.
- the IAB host node 40 is used to execute the execution of the target host node in the above embodiment.
- the steps, the execution steps and the corresponding beneficial effects can be understood with reference to the above-mentioned corresponding embodiments, and details are not repeated here.
- the IAB host node 40 includes:
- a receiving unit 401 configured to perform the receiving action of the target host node in the node switching method provided in any possible implementation manner in the foregoing embodiment
- a sending unit 402 configured to perform the sending action of the target host node in the node switching method provided in any possible implementation manner in the foregoing embodiment
- the processing unit 403 is configured to execute the processing action of the target host node in the node switching method provided in any possible implementation manner of the foregoing embodiments.
- the IAB host node 40 includes a processing unit and a transceiver unit, and the transceiver unit may include a sending unit 402 and a receiving unit 401 .
- the transceiver unit may be a transceiver, the transceiver may include an antenna and a radio frequency circuit, etc.
- the processing unit may be a processor (or a processing circuit), such as a baseband processor, and the baseband processor may include one or more central Processing unit (central processing unit, CPU).
- the transceiver unit may be a radio frequency unit, and the processing unit may be a processor (or a processing circuit), such as a baseband processor.
- the transceiver unit may be an input/output interface of a chip (eg, a baseband chip), and the processing unit may be a processor (or a processing circuit) of the system-on-chip, which may include one or more central processing units .
- processing unit in the embodiments of the present application may be implemented by a processor or a processor-related circuit component (or, a processing circuit), and the transceiver unit may be implemented by a transceiver or a transceiver-related circuit component.
- the transceiver unit may be a functional module, which can perform both sending and receiving operations.
- the transceiver unit may be used to execute any one of the embodiments shown in FIG. 2 to the embodiments shown in FIG. 15 . All sending operations and receiving operations performed by the target host node in the embodiment, for example, when performing a sending operation, the transceiver unit can be considered to be a sending module, and when performing a receiving operation, it can be considered that the transceiver unit is a receiving module; or,
- the transceiver unit can also be two functional modules.
- the transceiver unit can be regarded as a general term for these two functional modules. These two functional modules are respectively the sending unit 402 and the receiving unit 401.
- the sending unit 402 is used to complete the sending operation, for example, the sending module It can be used to perform all sending operations performed by the target host node in any one of the embodiments shown in FIG. 2 to the embodiments shown in FIG. 15 , and the receiving module is used to complete the receiving operation.
- the receiving unit can use All receiving operations performed by the target host node in any one of the embodiments shown in FIG. 2 to the embodiment shown in FIG. 15 are performed.
- the above embodiments provide different implementations of the IAB host node 40.
- the following provides an IAB node 50.
- the IAB node 50 is used to perform the steps performed by the IAB node in the above embodiments.
- the IAB node 50 includes:
- processing unit 501 sending unit 502;
- the processing unit 501 is configured to execute the processing action of the IAB node in the node switching method provided in any possible implementation manner of the foregoing embodiments.
- the sending unit 502 is configured to perform the sending action of the IAB node in the node switching method provided in any possible implementation manner in the foregoing embodiment.
- the IAB node 50 includes a processing unit and a transceiver unit, and the transceiver unit may include a sending unit 502 .
- the transceiver unit may be a transceiver
- the transceiver may include an antenna, a radio frequency circuit, etc.
- the processing unit 501 may be a processor (or a processing circuit), such as a baseband processor, and the baseband processor may include one or more Central processing unit (central processing unit, CPU).
- the transceiver unit may be a radio frequency unit
- the processing unit may be a processor (or, a processing circuit), such as a baseband processor.
- the transceiver unit may be an input/output interface of a chip (eg, a baseband chip), and the processing unit may be a processor (or processing circuit) of the chip system, which may include one or more central processing units.
- the processing unit 501 in this embodiment of the present application may be implemented by a processor or a processor-related circuit component (or a processing circuit), and the transceiver unit may be implemented by a transceiver or a transceiver-related circuit component.
- the transceiver unit may be a functional module, which can perform both sending and receiving operations.
- the transceiver unit may be used to execute any one of the embodiments shown in FIG. 2 to the embodiments shown in FIG. 15 .
- All sending operations and receiving operations performed by the IAB node in the embodiment for example, when performing a sending operation, it can be considered that the transceiver unit is a sending module, and when performing a receiving operation, it can be considered that the transceiver unit is a receiving module;
- the unit can also be two functional modules.
- the transceiver unit can be regarded as the general name of these two functional modules.
- the two functional modules are the sending unit 502 and the receiving unit, respectively.
- the sending unit 502 is used to complete the sending operation.
- the sending module can use All sending operations performed by the IAB node in any one of the embodiments shown in FIG. 2 to the embodiment shown in FIG. 15 are performed.
- FIG. 19 is a schematic diagram of a communication device 60 provided in an embodiment of the present application, which is used to implement the operations of the source host node, the target host node, and the IAB node in the above embodiments.
- the communication apparatus includes: a processor 601 and a communication interface 602 , and optionally, the communication apparatus further includes a memory 603 .
- Communication interface 602 is used to enable communication with other devices.
- the method performed by the network device or the terminal device may be implemented by the processor 601 calling a program stored in a memory (which may be the memory 603 in the network device or the terminal device, or an external memory). That is, the apparatus used in the source host node, the target host node and the IAB node may include a processor 601, and the processor 601 executes the source host node, the target host node and the The method executed by the IAB node.
- the processor here may be an integrated circuit with signal processing capability, such as a CPU.
- the means for the source host node, the target host node, and the IAB node may be implemented by one or more integrated circuits configured to implement the above methods. For example: one or more ASICs, or, one or more microprocessor DSPs, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Alternatively, the above implementations may be combined.
- the functions/implementation processes of the processing modules in FIG. 16 , FIG. 17 and FIG. 18 can be implemented by the processor 601 in the communication device 60 shown in FIG. 19 calling the computer-executable instructions stored in the memory 603 .
- the function/implementation process of the transceiver unit in FIG. 17 and FIG. 18 can be implemented by the communication interface 602 in the communication device 60 shown in FIG. 19 .
- the disclosed system, apparatus and method may be implemented in other manners.
- the apparatus embodiments described above are only illustrative.
- the division of the units is only a logical function division. In actual implementation, there may be other division methods.
- multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, 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.
- the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
- 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 technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
- the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), magnetic disk or optical disk and other media that can store program codes .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请实施例提供了一种节点切换方法以及相关设备,源宿主节点向目标宿主节点发送切换请求消息,切换请求消息中包括IAB节点的上下文信息以及至少一个终端设备的上下文信息,源宿主节点接收目标宿主节点发送的切换响应消息,切换响应消息中包括至少一个终端设备中被接受的终端设备的标识,和/或,至少一个终端设备中被拒绝的终端设备的标识。这样,与IAB节点相连接的终端设备中被目标宿主节点接受的终端设备可以切换至目标宿主节点,从而使得IAB节点和被接受的终端设备一起切换至目标宿主节点,保证被接受的终端设备的数据的正常传输。
Description
本申请涉及通信领域,尤其涉及一种节点的切换方法以及相关设备。
第三代合作伙伴计划(third generation partnership project,3GPP)标准组织制定的第五代蜂窝移动通信***的协议标准,与长期演进(long term evolution,LTE)***相比,新空口(New Radio,NR)***支持更大的传输带宽,更多的收发天线阵列,更高的传输速率以及更灵活、粒度更小的调度机制,NR***的上述特性提供了更多的适用范围。
现有的NR***中,在接入回传一体化(Integrated Access and Backhaul,IAB)场景下,终端设备与IAB宿主节点之间进行数据交互。终端设备和IAB宿主节点之间存在至少1个IAB节点,终端设备通过该至少一个IAB节点实现与IAB宿主节点建立通信连接,其中,IAB节点进一步包括IAB分布式单元(IAB-Disitributed Unit,IAB-DU)和IAB移动终端(IAB-Mobile Teriminal,IAB-MT)两部分。
当IAB节点切换IAB宿主节点时,现有切换技术可以实现该IAB节点中IAB-MT从源宿主节点切换到目标宿主节点,而并不涉及该IAB节点中的IAB-DU以及该IAB节点的子节点(例如:终端设备或者其他IAB节点)的处理,从而导致该IAB节点的子节点在该IAB节点切换后将无法正常工作。
发明内容
本申请提供了一种节点的切换方法以及相关设备,源宿主节点触发IAB节点和其子节点(例如:其他IAB节点或者终端)一起切换至目标宿主节点,从而保证IAB节点切换后终端设备的数据的正常传输。
本申请第一方面提供一种节点切换方法,该方法中:源宿主节点向目标宿主节点发送切换请求消息,所述切换请求消息中包括接入回传一体化IAB节点的上下文信息以及至少一个终端设备的上下文信息,所述切换请求消息用于请求将所述IAB节点以及至少一个终端设备切换至所述目标宿主节点,其中,所述终端设备直接连接到所述IAB节点,或者,所述终端设备通过至少一个其他IAB节点连接到所述IAB节点;所述源宿主节点接收所述目标宿主节点发送的切换响应消息,所述切换响应消息中包括所述至少一个终端设备中被接受的终端设备的标识,和/或,所述至少一个终端设备中被拒绝的终端设备的标识。
本申请中,与IAB节点相连接的终端设备中被目标宿主节点接受的终端设备切换至目标宿主节点,从而使得IAB节点和被接受的终端设备一起切换至目标宿主节点,保证被接受的终端设备的数据的正常传输。
在第一方面的一种可能的实现方式中,若所述终端设备直接连接到所述IAB节点,所述方法还包括:所述源宿主节点接收所述IAB节点发送的测量结果,所述测量结果包括所述IAB节点对服务小区的信号质量进行测量的结果以及所述IAB节点对邻小区的信号质量 进行测量的结果;所述源宿主节点根据所述测量结果确定将所述IAB节点以及至少一个终端设备切换至所述目标宿主节点。
该种可能的实现方式中,若源宿主节点确认服务小区的信号质量优于邻小区,则源宿主节点无需向目标宿主节点发送切换请求消息。若IAB节点没有工作在载波聚合(carrier aggregation,CA)模式,则有一个服务小区,若一个邻居小区的信号质量高于该服务小区的信号质量,则源宿主节点根据该测量结果确定将IAB节点以及至少一个终端设备切换至目标宿主节点。若IAB节点工作在CA模式,则服务小区包括一个主小区和至少一个辅小区,若有一个邻居小区的信号质量高于该主小区的信号质量,则源宿主节点根据该测量结果确定将IAB节点以及至少一个终端设备切换至目标宿主节点。该种可能的实现方式确保IAB节点以及至少一个终端设备在邻小区的信号质量优于本小区的信号质量时在再进行切换,提升了IAB节点以及至少一个终端设备的通信质量。
在第一方面的一种可能的实现方式中,若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述切换请求消息中还包括所述其他IAB节点的上下文信息,所述切换响应消息中还包括至少一个其他IAB节点中被接受的其他IAB节点的标识,和/或,至少一个其他IAB节点中被拒绝的其他IAB节点的标识。
该种可能的实现方式中,源宿主节点接收到的切换响应消息中包括至少一个其他IAB节点中被接受的其他IAB节点的标识,和/或,至少一个其他IAB节点中被拒绝的其他IAB节点的标识,该种实现方式使得目标宿主节点根据自身的网络负载等情况选择接纳的其他IAB节点,有利于充分利用目标宿主节点的资源,避免由于目标宿主节点资源不足而导致的切换失败。
在第一方面的一种可能的实现方式中,所述方法还包括:
所述源宿主节点接收所述IAB节点发送的测量结果,所述测量结果包括所述IAB节点对服务小区的信号质量进行测量的结果以及所述IAB节点对邻小区的信号质量进行测量的结果;所述源宿主节点根据所述测量结果确定将所述IAB节点、至少一个其他IAB节点以及至少一个终端设备切换至所述目标宿主节点。
该种可能的实现方式中,若源宿主节点确认服务小区的信号质量优于邻小区,则源宿主节点无需向目标宿主节点发送切换请求消息。若IAB节点没有工作在CA模式,则有一个服务小区,若一个邻居小区的信号质量高于该服务小区的信号质量,则源宿主节点可以根据该测量结果确定将IAB节点、至少一个其他IAB节点以及至少一个终端设备切换至目标宿主节点;若IAB节点工作在CA模式,则服务小区包括一个主小区和至少一个辅小区,若有一个邻居小区的信号质量高于该主小区的信号质量,则源宿主节点可以根据该测量结果确定将IAB节点、至少一个其他IAB节点以及至少一个终端设备切换至目标宿主节点。该种可能的实现方式确保IAB节点、至少一个其他IAB节点以及至少一个终端设备在邻小区的信号质量优于本小区信号质量时在再进行切换,提升了IAB节点、至少一个其他IAB节点以及至少一个终端设备的通信质量。
在第一方面的一种可能的实现方式中,所述IAB节点包括接入回传一体化移动终端IAB-MT以及接入回传一体化分布式单元IAB-DU,所述IAB节点的上下文信息包括所述 IAB-MT的上下文信息以及所述IAB-DU的上下文信息;所述IAB-MT的上下文信息包括所述IAB-MT和所述IAB节点的父节点之间的回传无线链路控制信道BH RLC CH的配置信息;所述IAB-DU的上下文信息包括IAB-DU的标识和/或IAB-DU的小区标识。
该种可能的实现方式中,源宿主节点将IAB节点的上下文信息传递给目标宿主节点,以便于目标宿主节点根据上下文信息为IAB节点进行切换资源的准备,该种可能的实现方式提升了IAB节点切换至目标宿主节点的成功率。
在第一方面的一种可能的实现方式中,所述IAB-DU的上下文信息还包括IAB-DU的小区的激活指示信息,所述激活指示信息用于指示所述IAB-DU的小区是否已经被激活,该种可能的实现方式确保了在IAB节点切换至目标宿主节点之后已经被激活的小区仍然能够保持正常通信。
该种可能的实现方式中,目标宿主节点获知IAB-DU的哪些小区已经被源宿主节点激活,这些小区在IAB节点切换到目标宿主节点后仍然要被目标宿主节点激活。该种可能的实现方式确保了在IAB节点切换至目标宿主节点之后已经被激活的小区仍然能够保持正常通信。
在第一方面的一种可能的实现方式中,所述IAB节点的上下文信息还包括所述源宿主节点为所述IAB节点分配的回传适配协议BAP地址。
该种可能的实现方式中,目标宿主节点获知源宿主节点为IAB节点分配的BAP地址,以便目标宿主节点为IAB节点新分配的BAP地址不同于源宿主节点为IAB节点分配的BAP地址。
在第一方面的一种可能的实现方式中,所述终端设备的上下文信息包括所述终端设备的标识,所述终端设备的标识包括所述终端设备接入的小区的物理小区标识(physical cell identifier,PCI)和所述终端设备在接入小区内的小区无线网络临时标识(cell-radio network temporary identifier,C-RNTI)。
该种可能的实现方式中,由于IAB节点切换前后,IAB-DU小区的PCI保持不变,目标宿主节点根据终端设备的标识来识别终端设备,该种可能的实现方式提升了目标宿主节点识别终端设备时的准确性。
在第一方面的一种可能的实现方式中,所述IAB节点的上下文信息还包括所述IAB节点的子节点的标识,用于指示所述IAB节点以及所述IAB节点的子节点之间的拓扑关系。
该种可能的实现方式中,目标宿主节点能够获知准备切换过来的节点之间的拓扑关系。
在第一方面的一种可能的实现方式中,所述IAB节点的上下文信息中还包括网络拓扑列表信息。若所述终端设备直接连接到所述IAB节点,所述网络拓扑列表信息用于指示所述IAB节点和所述终端设备之间的拓扑关系;若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述网络拓扑列表信息用于指示所述IAB节点和所述其他IAB节点之间,以及所述其他IAB节点和所述终端设备之间的拓扑关系。
该种可能的实现方式中,目标宿主节点获知准备切换过来的节点之间的拓扑关系。
在第一方面的一种可能的实现方式中,所述其他IAB节点包括其他IAB-MT以及其他IAB-DU,所述其他IAB节点的上下文信息包括所述其他IAB-MT的上下文信息以及所述其他IAB-DU的上下文信息;所述其他IAB-MT的上下文信息包括其他IAB-MT和其他IAB节点的 父节点之间的BH RLC CH的配置信息;所述其他IAB-DU的上下文信息包括其他IAB-DU的标识和/或其他IAB-DU的小区标识。
该种可能的实现方式中,源宿主节点将其他IAB节点的上下文信息传递给目标宿主节点,以便于目标宿主节点根据上下文信息为其他IAB节点进行切换资源的准备,该种可能的实现方式提升了其他IAB节点跟随IAB节点切换至目标宿主节点的成功率。
在第一方面的一种可能的实现方式中,所述其他IAB-DU的上下文信息还包括其他IAB-DU的小区的激活指示信息,所述其他IAB-DU的小区的激活指示信息用于指示所述其他IAB-DU的小区是否已经被激活。
该种可能的实现方式中,目标宿主节点获知其他IAB-DU的哪些小区已经被源宿主节点激活,这些小区在其他IAB节点切换到目标宿主节点后仍然要被目标宿主节点激活,该种可能的实现方式确保了在其他IAB节点切换至目标宿主节点之后已经被激活的小区仍然能够保持正常通信。
在第一方面的一种可能的实现方式中,所述其他IAB节点的上下文信息还包括所述源宿主节点为所述其他IAB节点分配的BAP地址。
该种可能的实现方式中,目标宿主节点获知源宿主节点为其他IAB节点分配的BAP地址,以便目标宿主节点为其他IAB节点新分配的BAP地址不同于源宿主节点为其他IAB节点分配的BAP地址。
在第一方面的一种可能的实现方式中,所述其他IAB节点的上下文信息还包括所述其他IAB节点的父节点的标识,和/或,所述其他IAB节点的子节点的标识,用于指示所述其他IAB节点和所述其他IAB节点的父节点之间,和/或,所述其他IAB节点和所述其他IAB节点的子节点之间的拓扑关系。
该种可能的实现方式中,目标宿主节点能够获知准备切换过来的节点之间的拓扑关系。
在第一方面的一种可能的实现方式中,所述源宿主节点包括源Donor-CU,所述目标宿主节点包括目标Donor-CU,所述方法还包括:所述源Donor-CU从所述切换响应消息中获取所述目标Donor-CU生成的第一无线资源控制RRC消息,所述第一RRC消息包括第一IAB节点切换至所述目标宿主节点后的小区配置信息,所述第一IAB节点包括所述IAB节点以及其他IAB节点中被接受的其他IAB节点;所述源Donor-CU将所述第一RRC消息发送至所述第一IAB节点。
该种可能的实现方式所提供的小区配置信息的传输方式对于现有标准的影响较小,提升了方案的可实现性。
在第一方面的一种可能的实现方式中,所述源宿主节点包括源Donor-CU,所述目标宿主节点包括目标Donor-CU,所述方法还包括:所述源Donor-CU从所述切换响应消息中获取所述目标Donor-CU生成的第一F1应用层协议(F1 application protocol,F1AP)消息,所述第一F1AP消息包括第一IAB节点切换至所述目标宿主节点后的小区配置信息,所述第一IAB节点包括所述IAB节点以及其他IAB节点中被接受的其他IAB节点;所述源Donor-CU将所述第一F1AP消息封装于第二F1AP消息中发送至所述第一IAB节点。
该种可能的实现方式所提供的小区配置信息的传输方式为通过源Donor-CU和第一IAB 节点之间已有的F1AP消息来传输更新小区配置信息,对标准协议流程改动较小,提升了方案的可实现性。
在第一方面的一种可能的实现方式中,所述源宿主节点包括源Donor-CU,所述目标宿主节点包括目标Donor-CU,所述方法还包括:所述源Donor-CU从所述切换响应消息中获取第一IAB节点切换至所述目标宿主节点后的小区配置信息,所述第一IAB节点包括所述IAB节点以及其他IAB节点中被接受的其他IAB节点;所述源Donor-CU将所述小区配置信息封装于F1AP消息中发送至所述第一IAB节点。
该种可能的实现方式所提供的小区配置信息的传输方式为通过源Donor-CU和第一IAB节点之间已有的F1AP消息来传输更新小区配置信息,对标准协议流程改动小,提升了方案的可实现性。
本申请第二方面提供一种节点切换方法,该方法包括:目标宿主节点接收源宿主节发送的切换请求消息,所述切换请求消息中包括接入回传一体化IAB节点的上下文信息以及至少一个终端设备的上下文信息,所述切换请求消息用于请求将所述IAB节点以及至少一个终端设备切换至所述目标宿主节点,其中,所述终端设备直接连接到所述IAB节点,或者,所述终端设备通过至少一个其他IAB节点连接到所述IAB节点;所述目标宿主节点向所述源宿主节点发送切换响应消息,所述切换响应消息中包括所述至少一个终端设备中被接受的终端设备的标识,和/或,所述至少一个终端设备中被拒绝的终端设备的标识。
在第二方面的一种可能的实现方式中,所述目标宿主节点包括目标Donor-CU,所述方法还包括:所述目标Donor-CU向第一IAB节点发送上下文建立请求消息,所述上下文建立请求消息中携带终端设备的标识,所述终端设备的标识包括所述终端设备接入所述第一IAB节点的小区标识和所述终端设备在接入小区内的标识C-RNTI;若所述终端设备直接连接到所述IAB节点,所述第一IAB节点为所述IAB节点;若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述第一IAB节点为所述至少一个其他IAB节点。
该种可能的实现方式中,IAB宿主节点(donor-CU)向IAB节点的父节点(父节点的IAB-DU部分)发送终端设备上下文建立请求消息,以便IAB节点的父节点为IAB节点进行空口资源的分配,建立IAB节点和其父节点之间的BH RLC CH,以及在IAB节点的父节点和IAB宿主节点之间建立对应的GTP隧道传输IAB节点的回传数据。
在第二方面的一种可能的实现方式中,所述IAB节点包括接入回传一体化移动终端IAB-MT以及接入回传一体化分布式单元IAB-DU,所述IAB节点的上下文信息包括所述IAB-MT的上下文信息以及所述IAB-DU的上下文信息;所述IAB-MT的上下文信息包括所述IAB-MT和所述IAB节点的父节点之间的回传无线链路控制信道BH RLC CH的配置信息;所述IAB-DU的上下文信息包括IAB-DU的标识和/或IAB-DU的小区标识。
该种可能的实现方式中,源宿主节点将其他IAB节点的上下文信息传递给目标宿主节点,以便于目标宿主节点根据上下文信息为其他IAB节点进行切换资源的准备,该种可能的实现方式提升了其他IAB节点跟随IAB节点切换至目标宿主节点的成功率。
在第二方面的一种可能的实现方式中,所述IAB-DU的上下文信息还包括IAB-DU的小区的激活指示信息,所述激活指示信息用于指示所述IAB-DU的小区是否已经被激活。
该种可能的实现方式中,目标宿主节点获知IAB-DU的哪些小区已经被源宿主节点激活,这些小区在IAB节点切换到目标宿主节点后仍然要被目标宿主节点激活。该种可能的实现方式确保了在其他IAB节点切换至目标宿主节点之后已经被激活的小区仍然能够保持正常通信。
在第二方面的一种可能的实现方式中,所述IAB节点的上下文信息还包括所述源宿主节点为所述IAB节点分配的回传适配协议BAP地址。
该种可能的实现方式中,目标宿主节点获知源宿主节点为IAB节点分配的BAP地址,以便目标宿主节点为其他IAB节点新分配的BAP地址不同于源宿主节点为其他IAB节点分配的BAP地址。
在第二方面的一种可能的实现方式中,所述终端设备的上下文信息包括所述终端设备的标识,所述终端设备的标识包括所述终端设备接入的小区的物理小区标识PCI和所述终端设备在接入小区内的标识C-RNTI。
该种可能的实现方式中,由于IAB节点切换前后,IAB-DU小区的PCI保持不变,目标宿主节点根据终端设备的标识来识别终端设备,该种可能的实现方式提升了目标宿主节点识别终端设备时的准确性。
在第二方面的一种可能的实现方式中,所述IAB节点的上下文信息还包括所述IAB节点的子节点的标识,用于指示所述IAB节点和所述IAB节点的子节点之间的拓扑关系。
该种可能的实现方式中,目标宿主节点能够获知准备切换过来的节点之间的拓扑关系。在第二方面的一种可能的实现方式中,所述IAB节点的上下文信息中还包括网络拓扑列表信息;若所述终端设备直接连接到所述IAB节点,所述网络拓扑列表信息用于指示所述IAB节点和所述终端设备之间的拓扑关系;若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述网络拓扑列表信息用于指示所述IAB节点和所述其他IAB节点之间,以及所述其他IAB节点和所述终端设备之间的拓扑关系。
该种可能的实现方式中,目标宿主节点获知准备切换过来的节点之间的拓扑关系。
在第二方面的一种可能的实现方式中,若所述其他IAB节点包括其他IAB-MT以及其他IAB-DU,所述其他IAB节点的上下文信息包括所述其他IAB-MT的上下文信息以及所述其他IAB-DU的上下文信息;所述其他IAB-MT的上下文信息包括其他IAB-MT和其他IAB节点的父节点之间的BH RLC CH的配置信息;所述其他IAB-DU的上下文信息包括其他IAB-DU的标识和/或其他IAB-DU的小区标识。
该种可能的实现方式中,源宿主节点将其他IAB节点的上下文信息传递给目标宿主节点,以便于目标宿主节点根据上下文信息为其他IAB节点进行切换资源的准备,该种可能的实现方式提升了其他IAB节点跟随IAB节点切换至目标宿主节点的成功率。
在第二方面的一种可能的实现方式中,所述其他IAB-DU的上下文信息还包括其他IAB-DU的小区的激活指示信息,所述其他IAB-DU的小区的激活指示信息用于指示所述其他IAB-DU的小区是否已经被激活。
该种可能的实现方式中,目标宿主节点获知其他IAB-DU的哪些小区已经被源宿主节点激活,这些小区在其他IAB节点切换到目标宿主节点后仍然要被目标宿主节点激活,该种 可能的实现方式确保了在其他IAB节点切换至目标宿主节点之后已经被激活的小区仍然能够保持正常通信。
在第二方面的一种可能的实现方式中,所述其他IAB节点的上下文信息还包括所述源宿主节点为所述其他IAB节点分配的BAP地址。
该种可能的实现方式中,目标宿主节点获知源宿主节点为其他IAB节点分配的BAP地址,以便目标宿主节点为其他IAB节点新分配的BAP地址不同于源宿主节点为其他IAB节点分配的BAP地址。
在第二方面的一种可能的实现方式中,所述其他IAB节点的上下文信息还包括所述其他IAB节点的父节点的标识,和/或,所述其他IAB节点的子节点的标识,用于指示所述其他IAB节点和所述其他IAB节点的父节点之间,和/或,所述其他IAB节点和所述其他IAB节点的子节点之间的拓扑关系。
该种可能的实现方式中,目标宿主节点能够获知准备切换过来的IAB节点与其他IAB节点之间的拓扑关系。
在第二方面的一种可能的实现方式中,所述目标宿主节点包括目标Donor-CU;所述目标宿主节点向所述源宿主节点发送切换响应消息,包括:所述目标Donor-CU向所述源宿主节点发送所述切换响应消息,所述切换响应消息中包括第一RRC消息,所述第一RRC消息包括第一IAB节点切换至所述目标宿主节点后的小区配置信息,所述第一IAB节点包括所述IAB节点以及其他IAB节点中被接受的其他IAB节点。
该种可能的实现方式所提供的小区配置信息的传输方式对于现有标准的影响小,提升了方案的可实现性。
在第二方面的一种可能的实现方式中,所述目标宿主节点包括目标Donor-CU;所述目标宿主节点向所述源宿主节点发送切换响应消息,包括:所述目标Donor-CU向所述源宿主节点发送所述切换响应消息,所述切换响应消息中包括第一F1AP消息,所述第一F1AP消息包括第一IAB节点切换至所述目标宿主节点后的小区配置信息,所述第一IAB节点包括所述IAB节点或以及他IAB节点中被接受的其他IAB节点。
该种可能的实现方式所提供的小区配置信息的传输方式为通过源Donor-CU和第一IAB节点之间已有的F1AP消息来传输更新小区配置信息,对标准协议流程改动较小,提升了方案的可实现性。
在第二方面的一种可能的实现方式中,所述目标宿主节点包括目标Donor-CU;所述目标宿主节点向所述源宿主节点发送切换响应消息,包括:所述目标Donor-CU向所述源宿主节点发送所述切换响应消息,所述切换响应消息中包括第一IAB节点切换至所述目标宿主节点后的小区配置信息,所述第一IAB节点包括所述IAB节点以及其他IAB节点中被接受的其他IAB节点。
该种可能的实现方式所提供的小区配置信息的传输方式为通过源Donor-CU和第一IAB节点之间已有的F1AP消息来传输更新小区配置信息,对标准协议流程改动较小,提升了方案的可实现性。
在第二方面的一种可能的实现方式中,所述目标宿主节点包括目标Donor-CU,所述方 法还包括:所述目标donor-CU向所述其他IAB节点发送第一指示信息,所述第一指示信息用于指示所述IAB节点切换完成。
该种可能的实现方式中,目标donor-CU向其他IAB节点发送第一指示信息,其他IAB节点能够通过第一指示信息感知IAB节点切换完成,即其他IAB节点能够感知IAB节点和目标宿主节点之间的链路被打通,所以其他IAB节点的IAB-DU可以决定触发应用层的处理的时间。
在第二方面的一种可能的实现方式中,所述目标donor-CU向所述其他IAB节点发送第一指示信息之前,所述方法还包括:所述目标donor-CU向所述其他IAB节点发送第二指示信息,所述第二指示信息用于指示所述IAB节点正在切换或者准备切换。
该种可能的实现方式中,目标donor-CU向其他IAB节点发送第二指示信息,其他IAB节点能够通过第二指示信息感知IAB节点正在切换或准备切换,即其他IAB节点能够感知IAB节点和目标宿主节点之间的链路未被打通,所以其他IAB节点的IAB-DU能够通过第二指示信息决定不触发应用层处理。
本申请第三方面提供一种节点切换方法,该方法中:IAB节点从源宿主节点切换到目标宿主节点;所述IAB节点向所述IAB节点的子节点发送第一指示信息,所述第一指示信息用于指示所述IAB节点切换完成。其中,所述IAB节点的子节点是终端设备或者其他IAB节点。
本申请中,IAB节点向其他IAB节点发送第一指示信息,其他IAB节点能够通过第一指示信息感知IAB节点切换完成,即其他IAB节点能够感知IAB节点和目标宿主节点之间的链路被打通,所以其他IAB节点的IAB-DU可以决定触发应用层的处理的时间。
在第三方面的一种可能的实现方式中,所述IAB节点向其子节点发送第一指示信息之前,所述方法还包括:所述IAB节点向其子节点发送第二指示信息,所述第二指示信息用于指示所述IAB节点正在切换或者准备切换。
该种可能的实现方式中,IAB节点向其他IAB节点发送第二指示信息,其他IAB节点能够通过第二指示信息感知IAB节点正在切换或准备切换,即其他IAB节点能够感知IAB节点和目标宿主节点之间的链路未被打通,所以其他IAB节点的IAB-DU能够通过第二指示信息决定不触发应用层处理。
本申请第四方面提供一种IAB宿主节点,该IAB宿主节点至少包括发送单元、接收单元以及处理单元;
发送单元,用于执行前述第一方面或第一方面的任意可能的实现方式中提供的节点切换方法中源宿主节点的发送动作;
接收单元,用于执行前述第一方面或第一方面的任意可能的实现方式中提供的节点切换方法中源宿主节点的接收动作;
处理单元,用于执行前述第一方面或第一方面的任意可能的实现方式中提供的节点切换方法中源宿主节点的处理动作。
本申请第五方面提供一种IAB宿主节点,该IAB宿主节点至少包括发送单元、接收单元以及处理单元;
发送单元,用于执行前述第二方面或第二方面的任意可能的实现方式中提供的节点切换方法中目标宿主节点的发送动作;
接收单元,用于执行前述第二方面或第二方面的任意可能的实现方式中提供的节点切换方法中目标宿主节点的接收动作;
处理单元,用于执行前述第二方面或第二方面的任意可能的实现方式中提供的节点切换方法中目标宿主节点的处理动作。
本申请第六方面提供一种IAB节点,该IAB节点至少包括发送单元、接收单元以及处理单元;
发送单元,用于执行前述第三方面或第三方面的任意可能的实现方式中提供的节点切换方法中IAB节点的发送动作;
接收单元,用于执行前述第三方面或第三方面的任意可能的实现方式中提供的节点切换方法中IAB节点的接收动作;
处理单元,用于执行前述第三方面或第三方面的任意可能的实现方式中提供的节点切换方法中IAB节点的处理动作。
本申请第七方面提供了一种通信装置,该通信装置包括:处理器,所述处理器与存储器耦合,所述存储器用于存储计算机程序或指令,所述处理器用于执行存储器中的所述计算机程序或指令,若所述通信装置为源宿主节点或源宿主节点的芯片,所述通信装置执行上述第一方面或第一方面的任意可能的实现方式中的方法,若所述通信装置为目标宿主节点或目标宿主节点的芯片,所述通信装置执行上述第二方面或第二方面的任意可能的实现方式中的方法,若所述通信装置为IAB节点或IAB节点的芯片,所述通信装置执行上述第三方面或第三方面的任意可能的实现方式中的方法。
本申请第八方面提供了一种计算机可读存储介质,其特征在于,所述计算机可读存储介质用于存储计算机程序,当所述计算机程序在计算机上运行时,使得所述计算机执行上述第一方面或第一方面的任意可能的实现方式中的方法,或者使得所述计算机执行上述第二方面或第二方面的任意可能的实现方式中的方法,或者使得所述计算机执行上述第三方面或第三方面的任意可能的实现方式中的方法。
本申请第九方面提供了一种芯片,包括处理器和通信接口,所述处理器用于读取指令以执行上述第一方面或第一方面的任意可能的实现方式中的方法,或者执行上述第二方面或第二方面的任意可能的实现方式中的方法,或者执行上述第三方面或第三方面的任意可能的实现方式中的方法。
本申请第十方面提供了一种网络装置,包括处理器,所述处理器与存储器相连,所述存储器用于存储计算机程序,所述处理器用于执行所述存储器中存储的计算机程序,以使得所述网络装置执行上述第一方面或第一方面的任意可能的实现方式中的方法,或者执行上述第二方面或第二方面的任意可能的实现方式中的方法,或者执行上述第三方面或第三方面的任意可能的实现方式中的方法。
本申请第十一方面提供了一种通信***,包括上述第一方面或第一方面的任意可能的实现方式中所述的源宿主节点以及包括上述第二方面或第二方面的任意可能的实现方式中 所述的目标宿主节点以及包括上述第三方面或第三方面的任意可能的实现方式中所述的IAB节点。
图1为现有通信***中gNB-CU以及gNB-DU的分离架构示意图;
图2为现有通信***中gNB采用CU-DU分离架构下的控制面协议栈示意图;
图3为现有通信***中gNB采用CU-DU分离架构下的用户面协议栈示意图;
图4为现有通信***中两跳数据回传场景示意图;
图5为两跳数据回传的控制面协议栈示意图;
图6为两跳数据回传的用户面协议栈示意图;
图7为本申请提供的节点的切换***的应用场景示意图;
图8为本申请提供的节点的切换***的一实施例示意图;
图9为本申请提供的节点的切换***的另一实施例示意图;
图10为本申请提供的节点的切换方法的一实施例示意图;
图11为本申请提供的节点的切换方法的另一实施例示意图;
图12为本申请提供的节点的切换方法的另一实施例示意图;
图13为本申请提供的节点的切换方法的另一实施例示意图;
图14为本申请提供的节点的切换方法的另一实施例示意图;
图15为本申请提供的节点的切换方法的另一实施例示意图;
图16为本申请提供的IAB宿主节点的一结构示意图;
图17为本申请提供的IAB宿主节点的另一结构示意图;
图18为本申请提供的IAB节点的一结构示意图;
图19为本申请提供的通信装置的一结构示意图。
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域技术人员所获得的所有其他实施例,都属于本发明保护的范围。
本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换,以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。
在本申请实施例中,“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言,使用“示例性的”或者“例如” 等词旨在以具体方式呈现相关概念,便于理解。
本申请中的“和/或”仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况,其中A,B可以是单数或者复数。并且,在本申请的描述中,除非另有说明,“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达,是指的这些项中的任意组合,包括单项(个)或复数项(个)的任意组合。例如,a,b,或c中的至少一项(个),可以表示:a,b,c,a-b,a-c,b-c,或a-b-c,其中a,b,c可以是单个,也可以是多个。
本申请实施例的技术方案可以应用于各种通信***,例如:长期演进(long term evolution,LTE)***、LTE频分双工(frequency division duplex,FDD)***、LTE时分双工(time division duplex,TDD)、第五代(5th generation,5G)***即新无线(new radio,NR)以及未来的移动通信***等。
下面将对本申请实施例中的部分用语进行解释说明,以便于本领域技术人员理解。
gNB:为终端设备提供NR用户面和控制面传输的节点,包含一个或者多个小区。gNB通过下一代(Next Generation,NG)接口连接到5G核心网(5G Core,5GC),并通过Xn接口与其他gNB相连。其中,两个gNB之间的控制面信令通过Xn控制面(Xn-control,Xn-C)接口传输,两个gNB之间的用户面数据通过Xn用户面(Xn-user,Xn-U)接口传输。gNB与终端设备之间的接口称为Uu接口。
gNB集中式单元(gNB-Central Unit,gNB-CU):一个逻辑节点,包含gNB的无线资源控制(Radio Resource Control,RRC)层、业务数据适配协议(Service Data Adaptation Protocol,SDAP)层和分组数据汇聚协议(Packet Data Convergence Protocol,PDCP)层,或者包含en-gNB的RRC和/或PDCP层,用于控制1个或者多个gNB分布式单元(gNB-Distributed Unit,gNB-DU)。
gNB-DU:一个逻辑节点,包含gNB或者en-gNB的无线链路控制(Radio Link Control,RLC)层、媒体接入控制(Medium Access Control,MAC)层和物理(Physical,PHY)层。一个gNB-DU支持一个或者多个小区,但一个小区只能属于一个gNB-DU。此外,一个gNB-DU只能连接到一个gNB-CU。
图1为现有通信***中gNB-CU以及gNB-DU的分离架构示意图。
如图1所示,现有的通信场景中,gNB可以采用CU-DU分离架构。gNB由1个gNB-CU以及1个或者多个gNB-DU组成,其中,gNB-CU与gNB-DU之间通过F1接口相连,gNB-CU与5G核心网之间通过NG接口相连。此外,终端设备将通过gNB-DU接入gNB-CU,与终端设备对等的PHY层、MAC层以及RLC层的功能位于gNB-DU上,与终端设备对等的PDCP层、SDAP层、RRC层的功能位于gNB-CU上。
图2为现有通信***中gNB采用CU-DU分离架构下的控制面协议栈示意图。
如图2所示,对控制面而言,UL方向上,gNB-DU将终端设备生成的RRC消息封装在F1接口的F1AP消息中发送到gNB-CU。DL方向上,gNB-CU将RRC消息封装在F1AP消息中发送到gNB-DU,gNB-DU从F1AP消息中提取出RRC消息映射到Uu接口对应的信令无线承载(Signalling Radio Bearer,SRB)上发送给终端设备,可选的,该SRB可以是SRB0或者 SRB1或者SRB2,具体此处不做限定。
图3为现有通信***中gNB采用CU-DU分离架构下的用户面协议栈示意图。
如图3所示,对用户面而言,UL方向上,gNB-DU将从Uu接口的数据无线承载(Data Radio Bearer,DRB)上收到的终端设备发送的数据包映射到对应的GPRS隧道协议(GPRS Tunneling Protocol,GTP)隧道中发送至gNB-CU。DL方向上,gNB-CU将终端设备数据包映射到对应的GTP隧道中发送到gNB-DU,gNB-DU从GTP隧道中提取出终端设备的数据包,并将该终端设备的数据包映射到Uu接口对应的DRB上发送给终端设备。
现有的通信技术中,引入了IAB节点(IAB node)和IAB宿主节点(IAB donor)的概念。其中,IAB donor可以是gNB,或者升级后的gNB。
图4为现有通信***中两跳数据回传场景示意图。
以两跳数据回传(Backhaul,BH)场景为例,如图4所示,IAB网络采用CU-DU分离架构,即:IAB donor由接入回传一体化宿主集中式单元(Integrated Access and Backhaul donor Central Unit,IAB donor-CU)和接入回传一体化宿主分布式单元(Integrated Access and Backhaul donor Distributed Unit,IAB donor-DU)两部分组成,IAB node由接入回传一体化节点移动终端(Integrated Access and Backhaul node Mobile Terminal,IAB-MT)和接入回传一体化宿主分布式单元(Integrated Access and Backhaul node Distributed Unit,IAB-DU)两部分组成。其中,IAB-MT又可以称为IAB-UE。
对IAB donor而言,donor-DU与gNB-DU的功能类似,donor-CU与gNB-CU的功能类似。
对IAB节点而言,IAB-DU与gNB-DU的功能类似,用于为该IAB节点的子节点提供接入服务,其中,该IAB节点的子节点可以是终端设备,也可以是其他IAB节点。IAB-MT具有终端设备的功能,用于为该IAB节点的子节点提供数据回传。
IAB节点进一步又可以分为接入IAB节点和中间IAB节点,终端设备接入的IAB节点称为接入IAB节点,接入IAB节点和IAB donor之间路径上的IAB节点称为中间IAB节点。
如图4所示,终端设备接入IAB node2,则终端设备称为IAB node2的子节点,IAB node2称为终端设备的接入IAB节点或者父节点,具体此处不做限定。终端设备和IAB node2之间的链路称为接入链路。IAB node2通过IAB node1与IAB donor连接,则IAB node2的上一跳节点为IAB node1,即IAB node2的父节点为IAB node1,IAB node1的子节点为IAB node2。IAB node1称为中间IAB节点。IAB node1的上一跳节点为IAB donor,即IAB node1的父节点为IAB donor,IAB donor的子节点为IAB node1。IAB node1和IAB node2之间的链路,以及IAB node1和IAB donor之间的链路均称为回传链路。其中,与终端设备对等的PHY层、MAC层以及RLC层位于接入IAB节点上,即IAB2-DU上,而与终端设备对等的PDCP层、SDAP层和RRC层位于IAB donor-CU上。IAB节点均采用L2数据转发的架构,具体的控制面协议栈和用户面协议栈将在下文分别进行说明。
图5为两跳数据回传的控制面协议栈示意图。
如图5所示,控制面协议栈:IAB2-DU和donor-CU-CP之间建立F1控制面(F1-Control,F1-C)接口。具体的,如果donor CU采用控制面-用户面(control plane-user plane,CP-UP)分离架构,则IAB2-DU和donor CU-CP之间建立F1-C接口。终端设备的RRC消息 封装F1AP消息中通过F1-C接口传输。
图6为两跳数据回传的用户面协议栈示意图。
如图6所示,用户面协议栈:IAB2-DU和donor CU-UP之间建立F1用户面(F1-user,F1-U)接口。具体的,如果donor CU采用CP-UP分离架构,则IAB2-DU和donor CU-UP之间建立F1-U接口,并在该F1-U接口上建立per UE bearer的GTP隧道。也就是说,UE和IAB2-DU之间接口上建立的每一个UE DRB,在IAB2-DU和donor CU-UP之间接口上对应一个单独的GTP隧道。
第三代合作伙伴计划(third generation partnership project,3GPP)标准组织制定的第五代蜂窝移动通信***的协议标准,与长期演进(long term evolution,LTE)***相比,新空口(New Radio,NR)***支持更大的传输带宽,更多的收发天线阵列,更高的传输速率以及更灵活、粒度更小的调度机制,NR***的上述特性提供了更多的适用范围。
现有的NR***中,在接入回传一体化(Integrated Access and Backhaul,IAB)场景下,终端设备与IAB宿主节点之间进行数据交互。终端设备和IAB宿主节点之间存在至少1个IAB节点,终端设备通过该至少一个IAB节点实现与IAB宿主节点建立通信连接。
当IAB节点切换IAB宿主节点时,现有切换技术仅可以实现IAB节点中的IAB-MT从源宿主节点切换到目标宿主节点,而并不涉及该IAB节点中的IAB-DU以及该IAB节点的子节点(例如:终端设备或者其他IAB节点)的处理,从而导致该IAB节点的子节点在该IAB节点切换后将无法正常工作。
针对上述问题,本申请提供了一种节点的切换方法以及相关设备,源宿主节点向目标宿主节点发送切换请求消息,切换请求消息中包括IAB节点的上下文信息以及至少一个终端设备的上下文信息,源宿主节点接收目标宿主节点发送的切换响应消息,切换响应消息中包括至少一个终端设备中被接受的终端设备的标识,和/或,至少一个终端设备中被拒绝的终端设备的标识。这样,与IAB节点相连接的终端设备中被目标宿主节点接受的终端设备切换至目标宿主节点,而被目标宿主节点拒绝的终端设备将由源宿主节点重新为它们选择切换目标节点,从而使得IAB节点和被接受的终端设备一起切换至目标宿主节点,保证被接受的终端设备的数据的正常传输,并使得被拒绝的终端设备切换到允许其切换的目标节点上,从而也保证被拒绝的终端设备的数据的正常传输。
图7为本申请提供的节点的切换***的应用场景示意图。
请参阅图7,本申请实施例中,源宿主节点101、目标宿主节点102、IAB节点103以及终端设备104组成节点切换***。本申请实施例以单跳回传链路为例进行说明,但申请实施例的方案同样适用于两跳和多跳回传链路场景,具体此处不做限定。
其中,IAB节点103在进行节点切换之前,终端设备104接入IAB节点103,并通过IAB节点103连接到源宿主节点101。IAB节点103在进行节点切换之后,从源宿主节点101切换到目标宿主节点102,终端设备104通过IAB节点103连接到目标宿主节点102。
本申请实施例中,源宿主节点是源IAB宿主节点的简称,目标宿主节点是目标IAB宿主节点的简称。可选的,源宿主节点与目标宿主节点可以是gNB,源宿主节点与目标宿主节点还可以是其他设备,具体此处不做限定。
本申请实施例中的终端设备可以是指向用户提供语音和/或数据连通性的设备,具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。终端设备可以是移动终端,如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机,例如,可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置,它们与网络设备交换语言和/或数据。例如,个人通信业务(personal communication service,PCS)电话、无绳电话、会话发起协议(SIP)话机、无线本地环路(wireless local loop,WLL)站、个人数字助理(personal digital assistant,PDA)等设备。终端设备也可以称为***、订户单元(subscriber unit)、订户站(subscriber station),移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点(access point)、远程终端(remote terminal)、接入终端(access terminal)、用户代理(user agent)、用户设备(user device)、或用户装备(user equipment)、用户站、远方站、用户终端(terminal equipment,TE)、终端、无线通信设备以及用户代理或用户装置。另外,终端设备也可以是用于实现UE功能的芯片***。具体此处不做限定。
本申请实施例所提供的切换***中,仅以一个终端设备以及一个IAB节点的拓扑关系为例进行说明,该切换***中还可以包括更多的终端设备以及更多的IAB节点,具体此处不做限定。
图8为本申请提供的节点的切换***的一实施例示意图。
请参阅图8,本申请所提供的切换***中,可选的,终端设备可以直接连接到IAB节点。终端设备还可以通过IAB节点A、IAB节点B等其他IAB节点连接到IAB节点,具体此处不做限定。
图9为本申请提供的节点的切换***的一实施例示意图。
请参阅图9,本申请所提供的切换***中,以终端设备与IAB节点直接连接为例进行说明。可选的,IAB节点可以直接连接到源宿主节点或目标宿主节点,IAB节点还可以通过IAB节点A等至少一个IAB节点连接到源宿主节点,或IAB节点还可以通过IAB节点B等至少一个IAB节点连接到目标宿主节点,具体此处不做限定。
本申请所提供的切换***中,下述各个实施例中所说明的IAB节点可以为触发切换的IAB节点,可以将触发切换的IAB节点称为切换IAB节点(migrating IAB node),其他IAB节点为IAB节点(切换IAB节点)的下一跳子节点或多跳孙节点或孙孙节点,具体此处不做限定。可选的,终端设备可以直接连接到切换IAB节点。或者,终端设备还可以通过IAB节点A、IAB节点B等其他IAB节点连接到切换IAB节点。可选的,切换前,切换IAB节点可以直接连接到源宿主节点,或者,切换IAB节点还可以通过IAB节点C等至少一个IAB节点连接到源宿主节点。切换后,切换IAB节点可以直接连接到目标宿主节点,或者,切换IAB节点还可以通过IAB节点D等至少一个IAB节点连接到目标宿主节点,即将图8图9中所示的方案可以相互结合,具体此处不做限定。
基于图7至图9所描述的节点的切换***,对本申请提供的节点的切换方法进行描述。
图10为本申请提供的节点的切换方法的一实施例示意图。
请参阅图10,本申请中提供的节点的切换方法的一个实施例包括步骤201至步骤202。
201、源宿主节点向目标宿主节点发送切换请求消息,同样的,目标宿主节点接收源宿主节发送的切换请求消息。
本申请实施例中,切换请求消息用于请求将IAB节点以及至少一个终端设备切换至目标宿主节点。切换请求消息中包括IAB节点的上下文信息以及至少一个终端设备的上下文信息。
可选的,作为一种可能的实现方式,源宿主节点向目标宿主节点发送一个切换请求消息。若终端设备直接连接到IAB节点,则该切换请求消中包括IAB节点的上下文信息以及至少一个终端设备的上下文信息;若终端设备通过至少一个其他IAB节点连接到IAB节点,则该切换请求消息中还包括其他IAB节点的上下文信息。
可选的,作为另一种可能的实现方式,源宿主节点向目标宿主节点发送多个切换请求消息,每个切换请求消息中包含一个节点的上下文信息。若终端设备直接连接到IAB节点,即:IAB节点的上下文信息携带在一个单独的切换请求消息中,一个终端设备的上下文信息携带在一个单独的切换请求消息中,不同的终端设备的上下文信息携带在不同的切换请求消息中;若终端设备通过至少一个其他IAB节点连接到IAB节点,则除了IAB节点和至少一个终端设备的上下文信息分别携带在一个单独的切换请求消息中,一个其他IAB节点的上下文也携带在一个单独的切换请求消息中,不同的其他IAB节点的上下文携带在不同的切换请求消息中。
收到切换请求消息后,目标宿主节点根据自己的网络负载情况等,若终端设备直接连接到IAB节点,则目标宿主节点决定是否接受IAB节点和至少一个终端设备一起切换;若终端设备通过至少一个其他IAB节点连接到IAB节点,则目标宿主节点决定是否接受IAB节点、至少一个其他IAB节点以及至少一个终端设备一起切换。
202、源宿主节点接收目标宿主节点发送的切换响应消息,同样的,目标宿主节点向源宿主节点发送切换响应消息。
本申请实施例中,切换响应消息中包括至少一个终端设备中被接受的终端设备的标识,和/或,至少一个终端设备中被拒绝的终端设备的标识。
可选的,作为一种可能的实现方式,若源宿主节点向目标宿主节点发送一个切换请求消息时,则目标宿主节点向源宿主节点发送一个切换响应消息。若终端设备直接连接到IAB节点,该切换响应消息中包括至少一个终端设备中被接受的终端设备的标识,和/或,至少一个终端设备中被拒绝的终端设备的标识;若终端设备通过至少一个其他IAB节点连接到IAB节点,则该切换响应消息中还包括至少一个其他IAB节点中被接受的其他IAB节点的标识,和/或,至少一个其他IAB节点中被拒绝的其他IAB节点的标识。
可选的,作为另一种可能的实现方式,若源宿主节点向目标宿主节点发送多个切换请求消息时,则目标宿主节点向源宿主节点发送多个切换响应消息,每个切换响应消息对应一个节点。若终端设备直接连接到IAB节点,即:IAB节点对应一个单独的切换响应消息,一个终端设备对应一个单独的切换响应消息,不同的终端设备对应不同的切换响应消息。其中,被接受的终端设备对应的切换响应消息中包括被接受的终端设备的标识,被拒绝的终端设备对应的切换响应消息为切换拒绝消息或者切换准备失败消息或者切换失败消息, 该消息中包括被拒绝的终端设备的标识。可选的,该消息中还包括被拒绝的原因;若终端设备通过至少一个其他IAB节点连接到IAB节点,即:除了IAB节点和至少一个终端设备分别对应一个单独的切换响应消息,一个其他IAB节点也对应一个单独的切换响应消息,不同的其他IAB节点对应不同的切换响应消息。其中,被接受的其他IAB节点对应的切换响应消息中包括被接受的其他IAB节点的标识,被拒绝的其他IAB节点对应的切换响应消息为切换拒绝消息或者切换准备失败消息或者切换失败消息,该消息中包括被拒绝的其他IAB节点的标识。可选的,该消息中还包括被拒绝的原因,被拒绝的原因可以是由于目标宿主节点的资源不足,目标宿主节点的网络负载无法承担所有请求切换的其他IAB节点或者所有请求切换的终端设备。被拒绝的原因还可以是由于源宿主节点发送的节点标识(例如:UE XnAP ID)不可用,目标宿主无法识别源宿主节点所发送的节点标识。被拒绝的原因还可以是其他原因,具体此处不做限定。
本申请实施例中,除上述步骤201至步骤202之外,源宿主节点向目标宿主节点发送切换请求消息之前,源宿主节点还接收IAB节点发送的测量结果,该步骤将在下面的实施例中进行详细说明。
场景1、若终端设备直接连接到IAB节点。
源宿主节点接收IAB节点发送的测量结果。
该测量结果包括IAB节点对源宿主节点所管理的服务小区的信号质量进行测量的结果A以及IAB节点对目标宿主节点所管理的邻小区的信号质量进行测量的结果B。可选的,该测量结果包括参考信号接收功率(reference signal receiving power,RSRP),和/或,参考信号接收质量(reference signal receiving quality,RSRQ),具体此处不做限定。
源宿主节点根据测量结果确定将IAB节点以及至少一个终端设备切换至目标宿主节点。
若源宿主节点确认结果A优于结果B,由此可知,服务小区的信号质量优于邻小区,则源宿主节点无需向目标宿主节点发送切换请求消息。若IAB节点没有工作在CA模式,则有一个服务小区,若一个邻居小区的信号质量B高于该服务小区的信号质量A,则源宿主节点根据该测量结果确定将IAB节点以及至少一个终端设备切换至目标宿主节点;若IAB节点工作在CA模式,则服务小区包括一个主小区和至少一个辅小区,若有一个邻居小区的信号质量B高于该主小区的信号质量A,则源宿主节点根据该测量结果确定将IAB节点以及至少一个终端设备切换至目标宿主节点。
可选的,源宿主节点将IAB节点以及至少一个终端设备作为一个群组,并将该群组内的所有成员一起切换至目标宿主节点。若源宿主节点向目标宿主节点发送多个切换请求消息时,源宿主节点还需要向目标宿主节点发送一个指示信息,该指示信息用于指示该群组内的成员个数,以便目标宿主节点确定待接收切换请求消息的个数,即:一个成员对应一个切换请求消息。
场景2、若终端设备通过至少一个其他IAB节点连接到IAB节点。
源宿主节点接收IAB节点发送的测量结果。
该测量结果包括IAB节点对源宿主节点所管理的服务小区的信号质量进行测量的结果A以及IAB节点对目标宿主节点所管理的邻小区的信号质量进行测量的结果B。可选的,该 测量结果包括RSRP,和/或,RSRQ,具体此处不做限定。
源宿主节点根据测量结果确定将IAB节点、至少一个其他IAB节点以及至少一个终端设备切换至目标宿主节点。
若源宿主节点确认结果A优于结果B,由此可知,服务小区的信号质量优于邻小区,则源宿主节点无需向目标宿主节点发送切换请求消息。若IAB节点没有工作在CA模式,则有一个服务小区,若一个邻居小区的信号质量B高于该服务小区的信号质量A,则源宿主节点可以根据该测量结果确定将IAB节点、至少一个其他IAB节点以及至少一个终端设备切换至目标宿主节点;若IAB节点工作在CA模式,则服务小区包括一个主小区和至少一个辅小区,若有一个邻居小区的信号质量B高于该主小区的信号质量A,则源宿主节点可以根据该测量结果确定将IAB节点、至少一个其他IAB节点以及至少一个终端设备切换至目标宿主节点。
可选的,源宿主节点将IAB节点、至少一个其他IAB节点以及至少一个终端设备作为一个群组,并将该群组内的所有成员一起切换至目标宿主节点。若源宿主节点向目标宿主节点发送多个切换请求消息时,源宿主节点还向目标宿主节点发送一个指示信息,该指示信息用于指示该群组内的成员个数,以便目标宿主节点确定待接收切换请求消息的个数,即:一个成员对应一个切换请求消息。
本申请实施例中,IAB节点的上下文信息以及其他IAB节点的上下文信息中包括多种不同的参数,具体将在下面的实施例中进行说明。
本申请实施例中,IAB节点包括IAB-MT以及IAB-DU,IAB节点的上下文信息包括IAB-MT的上下文信息以及IAB-DU的上下文信息,IAB-MT的上下文信息包括IAB-MT和该IAB节点的父节点之间的回传无线链路控制信道(backhaul radio link control channel,BH RLC CH)的配置信息,IAB-DU的上下文信息包括IAB-DU的标识和/或IAB-DU的小区标识。可选的,IAB-DU的上下文信息还可以包括IAB-DU的小区的激活指示信息,激活指示信息用于指示IAB-DU的小区是否已经被激活,其中,IAB-DU的每个小区对应一个单独的激活指示信息。可选的,IAB节点的上下文信息还包括源宿主节点为IAB节点分配的回传适配协议(backhaul adaptation protocol,BAP)地址。
本申请实施例中,终端设备的上下文信息包括终端设备的标识,终端设备的标识包括终端设备接入的小区的物理小区标识(physical cell identifier,PCI)和终端设备在接入小区内的标识(cell-radio network temporary identifier,C-RNTI)。具体的,终端设备接入的小区属于源宿主节点,即:该小区的小区标识中包含的基站标识与源宿主节点的基站标识一致。
本申请实施例中,其他IAB节点包括其他IAB-MT以及其他IAB-DU,其他IAB节点的上下文信息包括其他IAB-MT的上下文信息以及其他IAB-DU的上下文信息。其他IAB-MT的上下文信息包括其他IAB-MT和其他IAB节点的父节点之间的BH RLC CH的配置信息。其他IAB-DU的上下文信息包括其他IAB-DU的标识和/或其他IAB-DU的小区标识。可选的,其他IAB-DU的上下文信息还包括其他IAB-DU的小区的激活指示信息,其他IAB-DU的小区的激活指示信息用于指示其他IAB-DU的小区是否已经被激活,其中,其他IAB-DU的每个小 区对应一个单独的激活指示信息。可选的,其他IAB节点的上下文信息还包括源宿主节点为其他IAB节点分配的BAP地址。
本申请实施例中,IAB节点的上下文信息以及其他IAB节点的上下文信息中还包括IAB节点与其他IAB节点以及终端设备之间的拓扑关系,具体的实现方式将在下面的实施例中说明。
场景1、若终端设备直接连接到IAB节点。
方式1:IAB节点的上下文信息中还包括IAB节点的子节点(或者下一跳节点)的标识,用于指示IAB节点与IAB节点的子节点(或者下一跳节点)之间的拓扑关系。由于终端设备直接连接到IAB节点,此时IAB节点的子节点(或者下一跳节点)便是终端设备,IAB节点的子节点(或者下一跳节点)的标识即终端设备的标识。例如:终端设备的标识可以是用户设备Xn应用层协议标识(user equipment Xn application protocol identity,UE XnAP ID),具体此处不做限定。
可选的,终端设备的上下文信息中还可以包括终端设备的父节点(或者上一跳节点)的标识,用于指示终端设备与终端设备的父节点(或者上一跳节点)之间的拓扑关系。由于终端设备直接连接到IAB节点,此时终端设备的父节点(或者上一跳节点)便是IAB节点,终端设备的父节点(或者上一跳节点)的标识即IAB节点的标识。例如:IAB节点的标识可以是UE XnAP ID,也可以是IAB节点的BAP地址,具体此处不做限定。
方式2:IAB节点的上下文信息中还可以包括网络拓扑列表信息,由于终端设备直接连接到IAB节点,网络拓扑列表信息用于指示IAB节点和终端设备之间的拓扑关系。例如:终端设备连接到IAB节点,则网络拓扑列表信息包含IAB节点的标识以及IAB节点的子节点(或者下一跳节点)的标识(即终端设备的标识),或者,网络拓扑列表信息包括终端设备的标识,以及终端设备的父节点(或者上一跳节点)的标识(即IAB节点的标识)。其中,终端设备的标识可以是UE XnAP ID,IAB节点的标识也可以是UE XnAP ID或者BAP地址,具体此处不做限定。
可选的,该网络拓扑列表信息可以不携带在IAB节点的上下文信息中,而是直接携带在源宿主节点向目标宿主节点发送的切换请求消息中,具体此处不做限定。
本申请实施例中,根据源宿主节点发送的切换请求消息,目标宿主节点可以获取IAB节点以及终端设备之间的拓扑关系。除上述实施例中方式一以及方式二所提及的实现方式之外,目标宿主节点还可以通过其他的方式获取IAB节点以及终端设备之间的拓扑关系,具体此处不做限定。
场景2、若终端设备通过至少一个其他IAB节点接入到IAB节点。
方式1:IAB节点的上下文信息还包括IAB节点的子节点(或者下一跳节点)的标识,用于指示IAB节点与IAB节点的子节点(或者下一跳节点)之间的拓扑关系。由于终端设备通过至少一个其他IAB节点连接到IAB节点,此时IAB节点的子节点(或者下一跳节点)便是其他IAB节点,IAB节点的子节点(或者下一跳节点)的标识即其他IAB节点的标识。例如:其他IAB节点的标识可以是UE XnAP ID,也可以是其他IAB节点的BAP地址,具体此处不做限定。
可选的,其他IAB节点的上下文信息还包括其他IAB节点的父节点(或者上一跳节点)的标识,和/或,其他IAB节点的子节点(或者下一跳节点)的标识,用于指示其他IAB节点以及其他IAB节点的父节点(或者上一跳节点)之间,和/或,其他IAB节点以及其他IAB节点的子节点(或者下一跳节点)之间的拓扑关系。由于终端设备通过至少一个其他IAB节点连接到IAB节点,例如:终端设备通过IAB节点A连接到IAB节点,此时其他IAB节点为IAB节点A,其他IAB节点的父节点(或者上一跳节点)便是IAB节点,其他IAB节点的父节点(或者上一跳节点)的标识即IAB节点的标识。其他IAB节点的子节点(或者下一跳节点)便是终端设备,其他IAB节点的子节点(或者下一跳节点)的标识即终端设备的标识。其中,终端设备的标识可以是UE XnAP ID,IAB节点的标识也可以是UE XnAP ID或者BAP地址,具体此处不做限定。
可选的,终端设备的上下文信息中还包括终端设备的父节点(或者上一跳节点)的标识,用于指示终端设备与终端设备的父节点(或者上一跳节点)之间的拓扑关系。由于终端设备通过至少一个其他IAB节点连接到IAB节点,此时终端设备的父节点(或者上一跳节点)便是其他IAB节点,终端设备的父节点(或者上一跳节点)的标识即其他IAB节点的标识。例如:其他IAB节点的标识可以是UE XnAP ID,也可以是其他IAB节点的BAP地址,具体此处不做限定。
方式2:IAB节点的上下文信息还包括网络拓扑列表信息,由于终端设备通过至少一个其他IAB节点连接到IAB节点,网络拓扑列表信息用于指示IAB节点、其他IAB节点以及终端设备之间的拓扑关系。例如:终端设备通过IAB节点A连接到IAB节点,则网络拓扑列表信息包含两组列表,第一组列表包括IAB节点的标识以及IAB节点的子节点(或者下一跳节点)的标识,其中,IAB节点的子节点为IAB节点A,则IAB节点的子节点(或者下一跳节点)的标识为IAB节点A的标识;第二组列表包括IAB节点A的标识以及IAB节点A的子节点(或者下一跳节点)的标识,其中,IAB节点A的子节点(或者下一跳节点)为终端设备,则IAB节点A的子节点(或者下一跳节点)的标识为终端设备的标识。或者,网络拓扑列表信息包含两组列表,第一组列表包括终端设备的标识以及终端设备的父节点(或者上一跳节点)的标识,其中,终端设备的父节点为IAB节点A,则终端设备的父节点(或者上一跳节点)的标识为IAB节点A的标识;第二组列表包括IAB节点A的标识以及IAB节点A的父节点(或者上一跳节点)的标识,其中,IAB节点A的父节点(或者上一跳节点)为IAB节点,则IAB节点A的父节点(或者上一跳节点)的标识为IAB节点的标识。其中,终端设备的标识可以是UE XnAP ID,IAB节点的标识也可以是UE XnAP ID或者BAP地址,其他IAB节点(例如:IAB节点A)的标识也可以是UE XnAP ID或者BAP地址,具体此处不做限定。
可选的,该网络拓扑列表信息可以不携带在IAB节点的上下文信息中,而是直接携带在源宿主节点向目标宿主节点发送的切换请求消息中,具体此处不做限定。
本申请实施例中,根据源宿主节点发送的切换请求消息,目标宿主节点获取IAB节点、其他IAB节点以及终端设备之间的拓扑关系。除上述实施例中方式一以及方式二所提及的实现方式之外,目标宿主节点还可以通过其他的方式获取IAB节点、其他IAB节点以及终 端设备之间的拓扑关系,具体此处不做限定。
图11为本申请提供的节点的切换方法的一实施例示意图。
请参阅图11,示例性的,终端设备通过IAB节点B以及IAB节点A连接到IAB节点。
可选的,一种可能的实现方式中,IAB节点的上下文信息中包括IAB节点的子节点标识(即:IAB节点A的标识),IAB节点A的上下文信息中包括IAB节点A的子节点标识(即:IAB节点B的标识),IAB节点B的上下文信息中包括IAB节点B的子节点标识(即:终端设备的标识),这样,目标宿主节点便根据源宿主节点向目标宿主节点发送的切换请求消息中携带的上下文信息来获知IAB节点、IAB节点A、IAB节点B以及终端设备之间的拓扑关系。
可选的,另一种可能的实现方式中,IAB节点A的上下文信息中包括IAB节点A的父节点标识(即:IAB节点的标识),IAB节点B的上下文信息中包括IAB节点B的父节点标识(即:IAB节点A的标识),终端设备的上下文信息中包括终端设备的父节点标识(即:IAB节点B的标识)。这样,目标宿主节点便根据源宿主节点向目标宿主节点发送的切换请求消息中携带的上下文信息来获知IAB节点、IAB节点A、IAB节点B以及终端设备之间的拓扑关系。
可选的,另一种可能的实现方式中,IAB节点的上下文信息中包括IAB节点的子节点标识(即:IAB节点A的标识),IAB节点A的上下文信息中包括IAB节点A的父节点标识(即:IAB节点的标识)以及IAB节点A的子节点标识(即:IAB节点B的标识),IAB节点B的上下文中包括IAB节点B的父节点标识(即:IAB节点A的标识)以及IAB节点B的子节点标识(即:终端设备的标识),终端设备的上下文信息中包括终端设备的父节点标识(即:IAB节点B的标识)。这样,目标宿主节点便根据源宿主节点向目标宿主节点发送的切换请求消息中携带的上下文信息来获知IAB节点、IAB节点A、IAB节点B以及终端设备之间的拓扑关系。
可选的,IAB节点以及其他IAB节点的上下文信息中通过节点标识来阐述IAB节点、其他IAB节点以及终端设备之间的网络拓扑关系还可以采用其他的实现方式,具体此处不做限定。
可选的,拓扑信息除了携带在上下文信息之外,还可以携带在源宿主节点向目标宿主节点发送的切换请求消息中,即:源宿主节点向目标宿主节点发送的切换请求消息还可以包括网络拓扑列表信息,网络拓扑列表信息用于指示IAB节点、IAB节点A、IAB节点B以及终端设备之间的拓扑关系。即:网络拓扑列表信息包含三组列表,第一组列表包括IAB节点的标识以及IAB节点的子节点标识(即:IAB节点A的标识),第二组列表包括IAB节点A的标识和IAB节点A的子节点标识(即:IAB节点B的标识),第三组列表包括IAB节点B的标识和IAB节点B的子节点标识(即:终端设备的标识)。或者,第一组列表包括IAB节点A的标识以及IAB节点A的父节点标识(即:IAB节点的标识),第二组列表包括IAB节点B的标识和IAB节点B的父节点标识(即:IAB节点A的标识),第三组列表包括终端设备的标识和终端设备的父节点标识(即:IAB节点B的标识)。
本申请实施例中,终端设备的标识可以是UE XnAP ID,IAB节点的标识也可以是UE XnAP ID或者BAP地址,IAB节点A的标识可以是UE XnAP ID或者BAP地址,IAB节点B的标识可以是UE XnAP ID或者BAP地址,具体此处不做限定。
本申请实施例中,根据源宿主节点发送的切换请求消息,目标宿主节点可以获取IAB节点、其他IAB节点以及终端设备之间的拓扑关系。除上述实施例中所提及的实现方式之外,目标宿主节点还可以通过其他的方式获取IAB节点、其他IAB节点以及终端设备之间的拓扑关系,具体此处不做限定。
本申请实施例中,若终端设备直接连接到IAB节点,源宿主节点可以将IAB节点的上下文信息以及终端设备的上下文信息携带在一个切换请求消息中发送至目标宿主节点,或者,也可将IAB节点的上下文信息以及终端设备的上下文信息分别携带在不同的切换请求消息中发送至目标宿主节点,具体此处不做限定。
同理可知,若终端设备通过至少一个其他IAB节点接入到IAB节点,源宿主节点可以将IAB节点的上下文信息、其他IAB节点的上下文信息以及终端设备的上下文信息携带在一个切换请求消息中发送至目标宿主节点,或者,也可将IAB节点的上下文信息、其他IAB节点的上下文信息以及终端设备的上下文信息分别携带在不同的切换请求消息中发送至目标宿主节点,具体此处不做限定。
本申请实施例中,除上述步骤201至步骤202之外,第一IAB节点切换至目标宿主节点后的小区配置信息发生改变,第一IAB节点包括IAB节点以及其他IAB节点中被接受的其他IAB节点。IAB节点通过源宿主节点从目标宿主节点接收更新后的小区配置信息具有多种实现方式,具体的实现方式将在下面的实施例中进行详细说明。
图12为本申请提供的节点的切换方法中源宿主节点发送配置信息的一实施例示意图。
请参阅图12,一种可能的实现方式中,源宿主节点包括源Donor-CU,目标宿主节点包括目标Donor-CU,第一IAB节点包括第一IAB-MT和第一IAB-DU。
目标Donor-CU向源宿主节点发送切换响应消息。
本申请实施例中,目标Donor-CU在接收到切换请求消息之后,目标Donor-CU会更新第一IAB节点的小区配置,例如:可选的,目标Donor-CU可以更新IAB-DU的小区全球标识(cell group identifier,CGI),可选的,目标Donor-CU也可以更新IAB-DU的小区标识(Cell Identity),具体此处不做限定。更新后的小区配置携带在切换响应消息中,并将切换响应消息发送至源Donor-CU。具体的,切换响应消息中包括目标Donor-CU生成的第一RRC消息,第一RRC消息包括第一IAB节点切换至目标宿主节点后的小区配置信息,第一IAB节点包括IAB节点以及其他IAB节点中被接受的其他IAB节点。
源Donor-CU从切换响应消息中获取第一无线资源控制RRC消息。
源Donor-CU将第一RRC消息通过源Donor-DU发送至第一IAB-MT。
本申请实施例中,目标Donor-CU将更新后的第一IAB-DU的小区配置信息携带在目标Donor-CU生成的第一RRC消息(RRC Reconfiguration)中,然后再将该第一RRC消息封装在切换响应消息(Handover Request Acknowledge)消息发送到源Donor-CU。源Donor-CU从切换响应消息中提取出第一RRC消息后,将该第一RRC消息通过源Donor-DU发送给第一IAB-MT。第一IAB-MT从第一RRC消息中提取出更新后的第一IAB-DU的小区配置,并通过 内部接口将收到的更新后的第一IAB-DU的小区配置发送给第一IAB-DU,以便第一IAB-DU更新小区配置。
本申请实施例中,源宿主节点向目标宿主节点发送切换请求消息之后,第一IAB-DU的小区配置更新,例如:第一IAB-DU小区标识CGI或者Cell Identity中包含的基站标识跟Donor-CU所属基站标识保持一致。切换过程中,第一IAB-DU从目标Donor-CU获取新的配置信息。
图13为本申请提供的节点的切换方法中源宿主节点发送配置信息的一实施例示意图。
请参阅图13,一种可能的实现方式中,源宿主节点包括源Donor-CU,目标宿主节点包括目标Donor-CU,第一IAB节点包括第一IAB-MT和第一IAB-DU。
目标Donor-CU向源宿主节点发送切换响应消息。
本申请实施例中,切换响应消息中包括第一F1AP消息,第一F1AP消息包括第一IAB节点切换至目标宿主节点后的小区配置信息,第一IAB节点包括IAB节点以及其他IAB节点中被接受的其他IAB节点。
源Donor-CU从切换响应消息中获取第一应用层协议F1AP消息。
源Donor-CU将第一F1AP消息封装于第二F1AP消息中发送至第一IAB-DU。
本申请实施例中,源Donor-CU将第一F1AP消息封装于第二F1AP消息后,源Donor-CU将第二F1AP消息发送至第一IAB-DU,以便第一IAB-DU更新小区配置。
本申请实施例中,示例性的,目标Donor-CU将更新后的第一IAB-DU的小区配置信息携带在目标Donor-CU生成的第一F1AP消息中,可选的,该第一F1AP消息可以是新定义的F1AP消息,或者,也可以是现有的F1AP消息,例如:gNB配置更新消息(gNB-CU Configuration Update),具体此处不做限定。然后,目标Donor-CU将该F1AP消息携带在Handover Request Acknowledge消息中发送到源Donor-CU。源Donor-CU从Handover Request Acknowledge消息中提取出第一F1AP消息,并将该第一F1AP消息携带在第二F1AP消息中通过源Donor-DU发送给第一IAB-DU。第一IAB-DU从第二F1AP消息中提取出目标Donor-CU生成的第一F1AP消息,以便第一IAB-DU更新小区配置。
本身请实施例中,源宿主节点向目标宿主节点发送切换请求消息之后,第一IAB-DU的小区配置更新,例如:第一IAB-DU的小区标识CGI或者Cell Identity中包含的基站标识跟Donor-CU所属基站标识保持一致。切换过程中,第一IAB-DU从目标Donor-CU获取新的配置信息。
本申请中图13所提供的实施例对现有的IAB协议栈存在影响,本申请中图13所提供的实施例对应的协议栈架构如图14所示,即:F1AP消息中携带F1AP消息。
图14为本申请提供的节点的切换方法中源宿主节点发送配置信息的协议栈架构示意图。图15为本申请提供的节点的切换方法中源宿主节点发送配置信息的一实施例示意图。
请参阅图15,一种可能的实现方式中,源宿主节点包括源Donor-CU,目标宿主节点包括目标Donor-CU,第一IAB节点包括第一IAB-MT和第一IAB-DU。
目标Donor-CU向源宿主节点发送切换响应消息。
本申请实施例中,切换响应消息中包括第一IAB节点切换至目标宿主节点后的小区配 置信息,第一IAB节点包括IAB节点以及其他IAB节点中被接受的其他IAB节点。
源Donor-CU从切换响应消息中获取第一IAB节点切换至目标宿主节点后的小区配置信息。
源Donor-CU将第一IAB节点切换至目标宿主节点后的小区配置信息封装于F1AP消息中发送至第一IAB-DU。
本申请实施例中,示例性的,目标Donor-CU将更新后的第一IAB-DU的小区配置信息携带在Handover Request Acknowledge消息中发送到源Donor-CU。源Donor-CU从Handover Request Acknowledge消息中提取出更新后的第一IAB-DU的小区配置信息,并将更新后的第一IAB-DU的小区配置信息携带在源Donor-CU生成的F1AP消息中发送给第一IAB-DU,以便第一IAB-DU更新小区配置。可选的,源Donor-CU生成的F1AP消息可以是新定义的消息,或者,也可以是现有的F1AP消息,例如:gNB-CU Configuration Update消息,具体此处不做限定。
本身请实施例中,源宿主节点向目标宿主节点发送切换请求消息之后,第一IAB-DU的小区配置更新,例如:第一IAB-DU的小区标识CGI或者Cell Identity中包含的基站标识跟Donor-CU所属基站标识保持一致。切换过程中,第一IAB-DU从目标Donor-CU获取新的配置信息。
上述图12至图15所示的实施例阐释了三种发送小区配置信息的方式,可选的,目标Donor-CU还可以通过其他的方式向第一IAB节点发送第一IAB节点切换至目标宿主节点后的小区配置信息,具体此处不做限定。
上述图12至图15所阐述的实施例可以基于步骤201、步骤202所阐述的实施例实施,也可以不基于步骤201、步骤202所阐述的实施例独立实施,具体此处不做限定。
本申请实施例中,除上述步骤201至步骤202之外,目标宿主节点还向IAB节点发送上下文建立请求消息,该步骤将在下面的实施例中进行详细说明。
本申请实施例中,源宿主节点包括源Donor-CU,目标宿主节点包括目标Donor-CU。
场景1、若终端设备直接连接到IAB节点。
目标Donor-CU向IAB节点发送上下文建立请求消息。
本申请实施例中,上下文建立请求消息中携带终端设备的标识,终端设备的标识包括终端设备接入IAB节点的小区标识和终端设备在接入小区内的标识C-RNTI,可选的,终端设备接入IAB节点的小区标识可以为PCI,或者,也可以为CGI,或者,还可以是其他标识,具体此处不做限定。
本申请实施例中,IAB节点与目标Donor-CU之间建立IAB节点的子节点的上下文。本实施例中,IAB节点的子节点为终端设备,即IAB节点和目标Donor-CU之间建立终端设备的上下文。
具体的,IAB节点切换前后,IAB节点的IAB-DU的小区标识PCI保持不变,终端设备在IAB-DU小区下的标识C-RNTI保持不变。一旦IAB节点的IAB-MT成功接入目标Donor-CU后,目标Donor-CU向IAB节点的IAB-DU发送上下文建立请求消息(UE Context Setup Request),该消息中携带终端设备在IAB节点的IAB-DU小区下的标识,可选的,该标识可 以是PCI和C-RNTI的组合,或者,可以是CGI和C-RNTI的组合,具体此处不做限定。其中,CGI可以是IAB节点的IAB-DU在源宿主节点下的小区标识,也可以是IAB节点的IAB-DU在目标宿主节点下的小区标识。根据终端设备在IAB节点的IAB-DU小区下的标识,IAB节点的IAB-DU能够获知该UE Context Setup Request消息用于请求为哪个终端设备建立上下文。
场景2、若终端设备通过至少一个其他IAB节点连接到IAB节点。
目标Donor-CU向第二IAB节点发送上下文建立请求消息,第二IAB节点为终端设备的接入节点或者父节点,即:终端设备接入的至少一个其他IAB节点中的一个其他IAB节点,上下文建立请求消息中携带终端设备的标识,终端设备的标识为终端设备接入至少一个其他IAB节点中的一个其他IAB节点的小区标识和终端设备在接入小区内的标识C-RNTI,可选的,终端设备接入第二IAB节点的小区标识可以为PCI,或者,可以为CGI,或者,还可以是其他标识,具体此处不做限定。
本申请实施例中,第二IAB节点与目标Donor-CU之间建立第二IAB节点的子节点的上下文。本实施例中,第二IAB节点的子节点为终端设备,即第二IAB节点和目标Donor-CU之间建立终端设备的上下文。
具体的,第二IAB节点切换前后,第二IAB节点的IAB-DU的小区PCI保持不变,终端设备在第二IAB节点的IAB-DU小区下的标识C-RNTI保持不变。一旦第二IAB节点的IAB-MT成功接入目标Donor-CU后,目标Donor-CU向第二IAB节点的IAB-DU发送上下文建立请求消息(UE Context Setup Request),该消息中携带终端设备在第二IAB节点的IAB-DU小区下的标识,可选的,该标识可以是PCI和C-RNTI,或者,可以是CGI和C-RNTI,具体此处不做限定。其中,CGI可以是第二IAB节点的IAB-DU在源宿主节点下的小区标识,也可以是第二IAB节点的IAB-DU在目标宿主节点下的小区标识。根据终端设备在第二IAB节点的IAB-DU小区下的标识,第二IAB节点的IAB-DU能够获知该UE Context Setup Request消息用于请求为哪个终端设备建立上下文。
上述目标宿主节点向IAB节点发送上下文建立请求消息所包含的多个不同的实施例可以基于步骤201、步骤202所阐述的实施例实施,也可以不基于步骤201、步骤202所阐述的实施例独立实施,具体此处不做限定。
本申请实施例中,除上述步骤201至步骤202之外,若终端设备通过至少一个其他IAB节点连接到IAB节点,目标宿主节点或者IAB节点还向其他IAB节点发送第一指示信息和/或第二指示信息,第一指示信息用于指示所述IAB节点切换完成。第二指示信息用于指示所述IAB节点正在切换或者准备切换。
该步骤将在下面的实施例中进行详细说明。
现有技术中,IAB节点切换至目标宿主节点后,由于其他IAB节点无法感知IAB节点切换完成,即无法感知IAB节点和目标宿主节点之间的链路被打通,所以其他IAB节点的IAB-DU无法决定什么时候触发应用层的处理。可选的,该应用层的处理可以是其他IAB节点的IAB-DU触发与目标宿主节点(例如:目标Donor-CU)建立流控制传输协议(stream control transmission protocol,SCTP)关联,或者,也可以是其他IAB节点的IAB-DU触 发向操作维护管理(operation administration and maintenance,OAM)服务器请求获取新配置,或者,还可以是其他的处理方式,具体此处不做限定。
示例性的,当IAB节点还没有完成切换时,IAB节点和目标宿主节点之间的链路是不通的,由于IAB节点还没有完成切换,说明IAB节点还没有成功切换到目标宿主节点,则IAB节点和目标宿主节点之间的空口链路还没有建立好,而且IAB节点和目标宿主节点链路上的承载映射和路由都没有配置,则无法进行数据的传输,因此,可以认为链路是不通的。其他IAB节点的IAB-DU若在此时触发应用层的处理,向目标宿主节点(例如:Donor-CU)触发SCTP关联建立请求,会导致其他IAB节点的IAB-DU一直无法收到目标宿主节点发送的SCTP关联请求的响应,导致认为底层链路不通,使得SCTP关联建立过程失败。
为了解决上述问题,本实施中目标宿主节点或者IAB节点可以向其他IAB节点发送第一指示信息和/或第二指示信息,第一指示信息用于指示所述IAB节点完成切换,即已经切换至所述目标宿主节点。第二指示信息用于指示所述IAB节点正在切换或者准备切换。其中,其他IAB节点可以是IAB节点的子节点,或者孙节点,或者孙孙节点。
方式1:目标宿主节点向其他IAB节点发送第一指示信息和/或第二指示信息。
本申请实施例中,目标宿主节点包括目标Donor-CU,IAB节点包括IAB-MT1以及IAB-DU1,其他IAB节点包括IAB-MT2以及IAB-DU2。
1、目标donor-CU向其他IAB节点发送第二指示信息。
本申请实施例中,目标Donor-CU收到源Donor-CU发送的切换请求消息后,获知IAB节点与其他IAB节点将一起切换至目标Donor-CU,则目标Donor-CU向其他IAB节点发送的RRC重配置消息(或者切换命令消息)中携带第二指示信息,用于指示IAB节点准备切换或者正在切换。
2、目标donor-CU向其他IAB节点发送第一指示信息。
本申请实施例中,若IAB节点已经切换至目标宿主节点,即IAB-MT1已经切换至目标Donor-CU,目标Donor-CU向IAB-MT2发送第一指示信息,该第一指示信息用于指示IAB节点切换完成,即:已经切换至目标宿主节点。
示例性的,IAB节点成功切换到目标宿主节点后,或者,IAB-MT1收到目标Donor-CU的BAP配置信息(例如:BAP层的路由配置信息和/或承载映射配置信息等)后,目标Donor-CU向IAB-MT2发送第一指示信息,该第一指示信息携带在RRC消息中发送。
方式2:IAB节点向其他IAB节点发送第一指示信息和/或第二指示信息。
本申请实施例中,目标宿主节点包括目标Donor-CU,IAB节点包括IAB-MT1以及IAB-DU1,其他IAB节点包括IAB-MT2以及IAB-DU2。
1、IAB节点向其他IAB节点发送第二指示信息。
本申请实施例中,IAB-MT1在收到目标Donor-CU发送的切换命令消息后,IAB-DU1向IAB-MT2发送第二指示信息,该指示信息用于指示IAB-MT1正在切换或者IAB-MT1准备切换。
本申请实施例中,可选的,IAB-DU1将第二指示信息可以携带在MAC CE中向IAB-MT2发送,或者,也可以携带在BAP control PDU中向IAB-MT2发送,具体此处不做限定。
2、IAB节点向其他IAB节点发送第一指示信息。
示例性的,IAB-MT1成功切换到目标Donor-CU后,或者,IAB-MT1收到目标宿主节点(例如:目标Donor-CU)的BAP配置信息后,IAB-DU1向IAB-MT2发送第一指示信息。
本申请实施例中,可选的,BAP配置信息可以包括BAP层的路由配置信息,或者,包括承载映射配置信息,BAP配置信息还可以包括其他配置信息,具体此处不做限定。
本申请实施例中,可选的,IAB-DU1可以将第一指示信息可以携带在MAC CE中向IAB-MT2发送,或者,也可以携带在BAP control PDU中向IAB-MT2发送,具体此处不做限定。
上述目标宿主节点或者IAB节点向其他IAB节点发送第一指示信息和/或第二指示信息所包含的多个不同的实施例可以基于步骤201、步骤202所阐述的实施例实施,也可以不基于步骤201、步骤202所阐述的实施例独立实施,具体此处不做限定。
上述实施例提供了一种节点切换方法的不同的实施方式,下面提供了一种IAB宿主节点30,如图16所示,该IAB宿主节点30用于执行上述实施例中源宿主节点执行的步骤,该执行步骤以及相应的有益效果具体请参照上述相应的实施例进行理解,此处不再赘述,该IAB宿主节点30包括:
发送单元301、接收单元302以及处理单元303;
发送单元301,用于执行前述实施例中任意可能的实现方式中提供的节点切换方法中源宿主节点的发送动作;
接收单元302,用于执行前述实施例中任意可能的实现方式中提供的节点切换方法中源宿主节点的接收动作;
处理单元303,用于执行前述实施例中任意可能的实现方式中提供的节点切换方法中源宿主节点的处理动作。
如图16所示,IAB宿主节点30包括处理单元和收发单元,收发单元可以包括发送单元301以及接收单元302。示例性地,收发单元可以是收发器,收发器可以包括天线和射频电路等,处理单元303可以是处理器(或者,处理电路),例如基带处理器,基带处理器中可以包括一个或多个中央处理单元(central processing unit,CPU)。当IAB宿主节点30是具有网络设备功能的部件时,收发单元可以是射频单元,处理单元可以是处理器(或者,处理电路),例如基带处理器。当IAB宿主节点30是芯片***时,收发单元可以是芯片(例如基带芯片)的输入输出接口、处理单元303可以是芯片***的处理器(或者,处理电路),可以包括一个或多个中央处理单元。应理解,本申请实施例中的处理单元可以由处理器或处理器相关电路组件(或者,处理电路)实现,收发单元可以由收发器或收发器相关电路组件实现。
另外,收发单元可以是一个功能模块,该功能模块既能完成发送操作也能完成接收操作,例如收发单元可以用于执行图2所示的实施例至图15所示的实施例中的任一个实施例中由源宿主节点所执行的全部发送操作和接收操作,例如,在执行发送操作时,可以认为收发单元是发送模块,而在执行接收操作时,可以认为收发单元是接收模块;或者,收发单元也可以是两个功能模块,收发单元可以视为这两个功能模块的统称,这两个功能模块 分别为发送单元301和接收单元302,发送单元301用于完成发送操作,例如发送模块可以用于执行图2所示的实施例至图15所示的实施例中的任一个实施例中由源宿主节点或目标宿主节点所执行的全部发送操作,接收模块用于完成接收操作,例如接收单元可以用于执行图2所示的实施例至图15所示的实施例中的任一个实施例中由源宿主节点或目标宿主节点所执行的全部接收操作。
需要说明的是,上述IAB宿主节点30的各模块之间的信息交互、执行过程等内容,由于与本申请方法实施例基于同一构思,其带来的技术效果与本发明方法实施例相同,具体内容可参见本申请前述所示的方法实施例中的叙述,此处不再赘述。
上述实施例提供了一种IAB宿主节点30的不同的实施方式,下面提供了一种IAB宿主节点40,如图17所示,该IAB宿主节点40用于执行上述实施例中目标宿主节点执行的步骤,该执行步骤以及相应的有益效果具体请参照上述相应的实施例进行理解,此处不再赘述,该IAB宿主节点40包括:
接收单元401、发送单元402以及处理单元403;
接收单元401,用于执行前述实施例中任意可能的实现方式中提供的节点切换方法中目标宿主节点的接收动作;
发送单元402,用于执行前述实施例中任意可能的实现方式中提供的节点切换方法中目标宿主节点的发送动作;
处理单元403,用于执行前述实施例中任意可能的实现方式中提供的节点切换方法中目标宿主节点的处理动作。
如图17所示,IAB宿主节点40包括处理单元和收发单元,收发单元可以包括发送单元402以及接收单元401。示例性地,收发单元可以是收发器,收发器可以包括天线和射频电路等,处理单元可以是处理器(或者,处理电路),例如基带处理器,基带处理器中可以包括一个或多个中央处理单元(central processing unit,CPU)。当IAB宿主节点40是具有网络设备功能的部件时,收发单元可以是射频单元,处理单元可以是处理器(或者,处理电路),例如基带处理器。当IAB宿主节点40是芯片***时,收发单元可以是芯片(例如基带芯片)的输入输出接口、处理单元可以是芯片***的处理器(或者,处理电路),可以包括一个或多个中央处理单元。应理解,本申请实施例中的处理单元可以由处理器或处理器相关电路组件(或者,处理电路)实现,收发单元可以由收发器或收发器相关电路组件实现。
另外,收发单元可以是一个功能模块,该功能模块既能完成发送操作也能完成接收操作,例如收发单元可以用于执行图2所示的实施例至图15所示的实施例中的任一个实施例中由目标宿主节点所执行的全部发送操作和接收操作,例如,在执行发送操作时,可以认为收发单元是发送模块,而在执行接收操作时,可以认为收发单元是接收模块;或者,收发单元也可以是两个功能模块,收发单元可以视为这两个功能模块的统称,这两个功能模块分别为发送单元402和接收单元401,发送单元402用于完成发送操作,例如发送模块可以用于执行图2所示的实施例至图15所示的实施例中的任一个实施例中由目标宿主节点所执行的全部发送操作,接收模块用于完成接收操作,例如接收单元可以用于执行图2所 示的实施例至图15所示的实施例中的任一个实施例中由目标宿主节点所执行的全部接收操作。
需要说明的是,上述IAB宿主节点40的各模块之间的信息交互、执行过程等内容,由于与本申请方法实施例基于同一构思,其带来的技术效果与本发明方法实施例相同,具体内容可参见本申请前述所示的方法实施例中的叙述,此处不再赘述。
上述实施例提供了一种IAB宿主节点40的不同的实施方式,下面提供了一种IAB节点50,如图18所示,该IAB节点50用于执行上述实施例中IAB节点执行的步骤,该执行步骤以及相应的有益效果具体请参照上述相应的实施例进行理解,此处不再赘述,该IAB节点50包括:
处理单元501、发送单元502;
处理单元501,用于执行前述实施例中任意可能的实现方式中提供的节点切换方法中IAB节点的处理动作。
发送单元502,用于执行前述实施例中任意可能的实现方式中提供的节点切换方法中IAB节点的发送动作。
如图18所示,IAB节点50包括处理单元和收发单元,收发单元可以包括发送单元502。示例性地,收发单元可以是收发器,收发器可以包括天线和射频电路等,处理单元501可以是处理器(或者,处理电路),例如基带处理器,基带处理器中可以包括一个或多个中央处理单元(central processing unit,CPU)。当IAB节点50是具有网络设备功能的部件时,收发单元可以是射频单元,处理单元可以是处理器(或者,处理电路),例如基带处理器。当IAB节点50是芯片***时,收发单元可以是芯片(例如基带芯片)的输入输出接口、处理单元可以是芯片***的处理器(或者,处理电路),可以包括一个或多个中央处理单元。应理解,本申请实施例中的处理单元501可以由处理器或处理器相关电路组件(或者,处理电路)实现,收发单元可以由收发器或收发器相关电路组件实现。
另外,收发单元可以是一个功能模块,该功能模块既能完成发送操作也能完成接收操作,例如收发单元可以用于执行图2所示的实施例至图15所示的实施例中的任一个实施例中由IAB节点所执行的全部发送操作和接收操作,例如,在执行发送操作时,可以认为收发单元是发送模块,而在执行接收操作时,可以认为收发单元是接收模块;或者,收发单元也可以是两个功能模块,收发单元可以视为这两个功能模块的统称,这两个功能模块分别为发送单元502和接收单元,发送单元502用于完成发送操作,例如发送模块可以用于执行图2所示的实施例至图15所示的实施例中的任一个实施例中由IAB节点所执行的全部发送操作。
需要说明的是,上述IAB节点50的各模块之间的信息交互、执行过程等内容,由于与本申请方法实施例基于同一构思,其带来的技术效果与本发明方法实施例相同,具体内容可参见本申请前述所示的方法实施例中的叙述,此处不再赘述。
请参考图19,为本申请实施例提供的一种通信装置60示意图,用于实现以上实施例中源宿主节点、目标宿主节点以及IAB节点的操作。该通信装置包括:处理器601和通信接口602,可选的,该通信装置还包括存储器603。通信接口602用于实现与其他设备进行 通信。
以上实施例中,网络设备或终端设备执行的方法可以通过处理器601调用存储器(可以是网络设备或终端设备中的存储器603,也可以是外部存储器)中存储的程序来实现。即,用于源宿主节点、目标宿主节点以及IAB节点中的装置可以包括处理器601,该处理器601通过调用存储器中的程序,以执行以上方法实施例中的源宿主节点、目标宿主节点以及IAB节点执行的方法。这里的处理器可以是一种具有信号的处理能力的集成电路,例如CPU。用于源宿主节点、目标宿主节点以及IAB节点的装置可以通过配置成实施以上方法的一个或多个集成电路来实现。例如:一个或多个ASIC,或,一个或多个微处理器DSP,或,一个或者多个FPGA等,或这些集成电路形式中至少两种的组合。或者,可以结合以上实现方式。
例如,图16、图17以及图18中的处理模块的功能/实现过程可以通过图19所示的通信装置60中的处理器601调用存储器603中存储的计算机可执行指令来实现,图16、图17以及图18中的收发单元的功能/实现过程可以通过图19中所示的通信装置60中的通信接口602来实现。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的***,装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的***,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个***,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(ROM,read-only memory)、随机存取存储器(RAM,random access memory)、磁碟或者光盘等各种可以存储程序代码的介质。
需要说明的是,本申请中的描述是适用于所有实施例的,为避免重复,没有在每个实 施例中赘述。应理解,说明书通篇中提到的“实施例”意味着与实施例有关的特定特征、结构或特性,这些特定的特征、结构或特性可以以任意适合的方式结合在一个或多个实施例中。应理解,在本发明的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本发明实施例的实施过程构成任何限定。
Claims (30)
- 一种节点切换方法,其特征在于,包括:目标宿主节点接收源宿主节发送的切换请求消息,所述切换请求消息中包括接入回传一体化IAB节点的上下文信息以及至少一个终端设备的上下文信息,所述切换请求消息用于请求将所述IAB节点以及至少一个终端设备切换至所述目标宿主节点,其中,所述终端设备直接连接到所述IAB节点,或者,所述终端设备通过至少一个其他IAB节点连接到所述IAB节点;所述目标宿主节点向所述源宿主节点发送切换响应消息,所述切换响应消息中包括所述至少一个终端设备中被接受的终端设备的标识,和/或,所述至少一个终端设备中被拒绝的终端设备的标识。
- 根据权利要求1所述的节点切换方法,其特征在于,所述目标宿主节点包括目标Donor-CU,所述方法还包括:所述目标Donor-CU向第一IAB节点发送上下文建立请求消息,所述上下文建立请求消息中携带终端设备的标识,所述终端设备的标识包括所述终端设备接入所述第一IAB节点的小区标识和所述终端设备在接入小区内的标识C-RNTI;若所述终端设备直接连接到所述IAB节点,所述第一IAB节点为所述IAB节点;若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述第一IAB节点为所述至少一个其他IAB节点。
- 根据权利要求1或2所述的节点切换方法,其特征在于,所述IAB节点的上下文信息还包括所述源宿主节点为所述IAB节点分配的回传适配协议BAP地址。
- 根据权利要求1至3中任意一项所述的节点切换方法,其特征在于,所述IAB节点的上下文信息还包括所述IAB节点的子节点的标识,用于指示所述IAB节点和所述IAB节点的子节点之间的拓扑关系。
- 根据权利要求1至3中任意一项所述的节点切换方法,其特征在于,所述IAB节点的上下文信息中还包括网络拓扑列表信息;若所述终端设备直接连接到所述IAB节点,所述网络拓扑列表信息用于指示所述IAB节点和所述终端设备之间的拓扑关系;若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述网络拓扑列表信息用于指示所述IAB节点和所述其他IAB节点之间,以及所述其他IAB节点和所述终端设备之间的拓扑关系。
- 根据权利要求1至5所述的节点切换方法,其特征在于,所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述切换请求消息中包括其他IAB节点的上下文信息,所述其他IAB节点的上下文信息包括所述源宿主节点为所述其他IAB节点分配的BAP地址。
- 根据权利要求6所述的节点切换方法,其特征在于,所述其他IAB节点的上下文信息还包括所述其他IAB节点的父节点的标识,和/或,所述其他IAB节点的子节点的标识,用于指示所述其他IAB节点和所述其他IAB节点的父节点之间,和/或,所述其他IAB节点 和所述其他IAB节点的子节点之间的拓扑关系。
- 根据权利要求1至7所述的节点切换方法,其特征在于,所述目标宿主节点包括目标Donor-CU,若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述方法还包括:所述目标donor-CU向所述其他IAB节点发送第一指示信息,所述第一指示信息用于指示所述IAB节点切换完成。
- 根据权利要求1至8所述的节点切换方法,其特征在于,所述目标宿主节点包括目标Donor-CU,若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述方法还包括:所述目标donor-CU向所述其他IAB节点发送第二指示信息,所述第二指示信息用于指示所述IAB节点正在切换或者准备切换。
- 一种节点切换方法,其特征在于,包括:源宿主节点向目标宿主节点发送切换请求消息,所述切换请求消息中包括接入回传一体化IAB节点的上下文信息以及至少一个终端设备的上下文信息,所述切换请求消息用于请求将所述IAB节点以及至少一个终端设备切换至所述目标宿主节点,其中,所述终端设备直接连接到所述IAB节点,或者,所述终端设备通过至少一个其他IAB节点连接到所述IAB节点;所述源宿主节点接收所述目标宿主节点发送的切换响应消息,所述切换响应消息中包括所述至少一个终端设备中被接受的终端设备的标识,和/或,所述至少一个终端设备中被拒绝的终端设备的标识。
- 根据权利要求10所述的节点切换方法,其特征在于,若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述切换请求消息中还包括所述其他IAB节点的上下文信息,所述切换响应消息中还包括至少一个其他IAB节点中被接受的其他IAB节点的标识,和/或,至少一个其他IAB节点中被拒绝的其他IAB节点的标识。
- 根据权利要求10或11所述的节点切换方法,其特征在于,所述IAB节点的上下文信息还包括所述IAB节点的子节点的标识,用于指示所述IAB节点以及所述IAB节点的子节点之间的拓扑关系。
- 根据权利要求10或11所述的节点切换方法,其特征在于,所述IAB节点的上下文信息中还包括网络拓扑列表信息;若所述终端设备直接连接到所述IAB节点,所述网络拓扑列表信息用于指示所述IAB节点和所述终端设备之间的拓扑关系;若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述网络拓扑列表信息用于指示所述IAB节点和所述其他IAB节点之间,以及所述其他IAB节点和所述终端设备之间的拓扑关系。
- 根据权利要求11所述的节点切换方法,其特征在于,所述其他IAB节点的上下文信息还包括所述其他IAB节点的父节点的标识,和/或,所述其他IAB节点的子节点的标识,用于指示所述其他IAB节点和所述其他IAB节点的父节点之间,和/或,所述其他IAB节点 和所述其他IAB节点的子节点之间的拓扑关系。
- 一种IAB宿主节点,其特征在于,包括:接收单元,用于接收源宿主节发送的切换请求消息,所述切换请求消息中包括接入回传一体化IAB节点的上下文信息以及至少一个终端设备的上下文信息,所述切换请求消息用于请求将所述IAB节点以及至少一个终端设备切换至所述目标宿主节点,其中,所述终端设备直接连接到所述IAB节点,或者,所述终端设备通过至少一个其他IAB节点连接到所述IAB节点;发送单元,用于向所述源宿主节点发送切换响应消息,所述切换响应消息中包括所述至少一个终端设备中被接受的终端设备的标识,和/或,所述至少一个终端设备中被拒绝的终端设备的标识。
- 根据权利要求15所述的IAB宿主节点,其特征在于,目标宿主节点包括目标Donor-CU,所述目标Donor-CU向第一IAB节点发送上下文建立请求消息,所述上下文建立请求消息中携带终端设备的标识,所述终端设备的标识包括所述终端设备接入所述第一IAB节点的小区标识和所述终端设备在接入小区内的标识C-RNTI;若所述终端设备直接连接到所述IAB节点,所述第一IAB节点为所述IAB节点;若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述第一IAB节点为所述至少一个其他IAB节点。
- 根据权利要求15或16所述的IAB宿主节点,其特征在于,所述IAB节点的上下文信息还包括所述源宿主节点为所述IAB节点分配的回传适配协议BAP地址。
- 根据权利要求15至17中任意一项所述的IAB宿主节点,其特征在于,所述IAB节点的上下文信息还包括所述IAB节点的子节点的标识,用于指示所述IAB节点和所述IAB节点的子节点之间的拓扑关系。
- 根据权利要求15至17中任意一项所述的IAB宿主节点,其特征在于,所述IAB节点的上下文信息中还包括网络拓扑列表信息;若所述终端设备直接连接到所述IAB节点,所述网络拓扑列表信息用于指示所述IAB节点和所述终端设备之间的拓扑关系;若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述网络拓扑列表信息用于指示所述IAB节点和所述其他IAB节点之间,以及所述其他IAB节点和所述终端设备之间的拓扑关系。
- 根据权利要求15至19中任意一项所述的IAB宿主节点,其特征在于,所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述切换请求消息中包括其他IAB节点的上下文信息,所述其他IAB节点的上下文信息包括所述源宿主节点为所述其他IAB节点分配的BAP地址。
- 根据权利要求20所述的IAB宿主节点,其特征在于,所述其他IAB节点的上下文信息还包括所述其他IAB节点的父节点的标识,和/或,所述其他IAB节点的子节点的标识,用于指示所述其他IAB节点和所述其他IAB节点的父节点之间,和/或,所述其他IAB节点 和所述其他IAB节点的子节点之间的拓扑关系。
- 根据权利要求15至21中任意一项所述的IAB宿主节点,其特征在于,所述目标宿主节点包括目标Donor-CU,若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述目标donor-CU向所述其他IAB节点发送第一指示信息,所述第一指示信息用于指示所述IAB节点切换完成。
- 根据权利要求15至22中任意一项所述的IAB宿主节点,其特征在于,所述目标宿主节点包括目标Donor-CU,若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述目标donor-CU向所述其他IAB节点发送第二指示信息,所述第二指示信息用于指示所述IAB节点正在切换或者准备切换。
- 一种IAB宿主节点,其特征在于,包括:发送单元,用于向目标宿主节点发送切换请求消息,所述切换请求消息中包括接入回传一体化IAB节点的上下文信息以及至少一个终端设备的上下文信息,所述切换请求消息用于请求将所述IAB节点以及至少一个终端设备切换至所述目标宿主节点,其中,所述终端设备直接连接到所述IAB节点,或者,所述终端设备通过至少一个其他IAB节点连接到所述IAB节点;接收单元,用于接收所述目标宿主节点发送的切换响应消息,所述切换响应消息中包括所述至少一个终端设备中被接受的终端设备的标识,和/或,所述至少一个终端设备中被拒绝的终端设备的标识。
- 根据权利要求24所述的IAB宿主节点,其特征在于,若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述切换请求消息中还包括所述其他IAB节点的上下文信息,所述切换响应消息中还包括至少一个其他IAB节点中被接受的其他IAB节点的标识,和/或,至少一个其他IAB节点中被拒绝的其他IAB节点的标识。
- 根据权利要求24或25所述的IAB宿主节点,其特征在于,所述IAB节点的上下文信息还包括所述IAB节点的子节点的标识,用于指示所述IAB节点以及所述IAB节点的子节点之间的拓扑关系。
- 根据权利要求24或25所述的IAB宿主节点,其特征在于,所述IAB节点的上下文信息中还包括网络拓扑列表信息;若所述终端设备直接连接到所述IAB节点,所述网络拓扑列表信息用于指示所述IAB节点和所述终端设备之间的拓扑关系;若所述终端设备通过至少一个其他IAB节点连接到所述IAB节点,所述网络拓扑列表信息用于指示所述IAB节点和所述其他IAB节点之间,以及所述其他IAB节点和所述终端设备之间的拓扑关系。
- 根据权利要求25所述的IAB宿主节点,其特征在于,所述其他IAB节点的上下文信息还包括所述其他IAB节点的父节点的标识,和/或,所述其他IAB节点的子节点的标识,用于指示所述其他IAB节点和所述其他IAB节点的父节点之间,和/或,所述其他IAB节点 和所述其他IAB节点的子节点之间的拓扑关系。
- 一种通信装置,其特征在于,包括:处理器,所述处理器与存储器耦合,所述存储器用于存储计算机程序或指令,所述处理器用于执行存储器中的所述计算机程序或指令,使得所述计算机执行如权利要求1至9中任意一项所述的方法,或者使得所述计算机执行如权利要求10至14中任意一项所述的方法。
- 一种通信***,包括权利要求15至23任意一项所述的IAB宿主节点以及包括权利要求24至28任意一项所述的IAB宿主节点。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2020/112681 WO2022041249A1 (zh) | 2020-08-31 | 2020-08-31 | 一种节点的切换方法以及相关设备 |
EP20950918.1A EP4192101A4 (en) | 2020-08-31 | 2020-08-31 | NODE SWITCHING METHOD AND RELATED DEVICE |
CN202080101339.4A CN115669058A (zh) | 2020-08-31 | 2020-08-31 | 一种节点的切换方法以及相关设备 |
US18/174,020 US20230199575A1 (en) | 2020-08-31 | 2023-02-24 | Node handover method and related device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2020/112681 WO2022041249A1 (zh) | 2020-08-31 | 2020-08-31 | 一种节点的切换方法以及相关设备 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/174,020 Continuation US20230199575A1 (en) | 2020-08-31 | 2023-02-24 | Node handover method and related device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022041249A1 true WO2022041249A1 (zh) | 2022-03-03 |
Family
ID=80354357
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/112681 WO2022041249A1 (zh) | 2020-08-31 | 2020-08-31 | 一种节点的切换方法以及相关设备 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20230199575A1 (zh) |
EP (1) | EP4192101A4 (zh) |
CN (1) | CN115669058A (zh) |
WO (1) | WO2022041249A1 (zh) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115604778A (zh) * | 2022-11-28 | 2023-01-13 | 广州世炬网络科技有限公司(Cn) | 一种节点接入方法、装置、设备以及存储介质 |
CN116033503A (zh) * | 2023-03-27 | 2023-04-28 | 广州世炬网络科技有限公司 | 基于组网性能的网间节点切换方法及装置 |
CN116033512A (zh) * | 2023-03-30 | 2023-04-28 | 广州世炬网络科技有限公司 | 自回传iab网络中iab宿主节点切换方法、装置、设备及介质 |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220225219A1 (en) * | 2021-01-08 | 2022-07-14 | Qualcomm Incorporated | Enhanced admission control in integrated access and backhaul (iab) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012134116A2 (en) * | 2011-03-25 | 2012-10-04 | Lg Electronics Inc. | Method and apparatus for performing handover procedure in wireless communication system including mobile relay node |
CN102752818A (zh) * | 2011-04-18 | 2012-10-24 | 中兴通讯股份有限公司 | 无线中继节点切换的处理方法及*** |
CN111093286A (zh) * | 2019-08-15 | 2020-05-01 | 中兴通讯股份有限公司 | 连接建立方法、装置、集合接入回传节点及存储介质 |
-
2020
- 2020-08-31 CN CN202080101339.4A patent/CN115669058A/zh active Pending
- 2020-08-31 WO PCT/CN2020/112681 patent/WO2022041249A1/zh unknown
- 2020-08-31 EP EP20950918.1A patent/EP4192101A4/en active Pending
-
2023
- 2023-02-24 US US18/174,020 patent/US20230199575A1/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012134116A2 (en) * | 2011-03-25 | 2012-10-04 | Lg Electronics Inc. | Method and apparatus for performing handover procedure in wireless communication system including mobile relay node |
CN102752818A (zh) * | 2011-04-18 | 2012-10-24 | 中兴通讯股份有限公司 | 无线中继节点切换的处理方法及*** |
CN111093286A (zh) * | 2019-08-15 | 2020-05-01 | 中兴通讯股份有限公司 | 连接建立方法、装置、集合接入回传节点及存储介质 |
Non-Patent Citations (1)
Title |
---|
ERICSSON: "Inter-donor Migration in IAB Networks – General Principles", 3GPP DRAFT; R3-205221, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20200817 - 20200827, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051915889 * |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115604778A (zh) * | 2022-11-28 | 2023-01-13 | 广州世炬网络科技有限公司(Cn) | 一种节点接入方法、装置、设备以及存储介质 |
CN116033503A (zh) * | 2023-03-27 | 2023-04-28 | 广州世炬网络科技有限公司 | 基于组网性能的网间节点切换方法及装置 |
CN116033512A (zh) * | 2023-03-30 | 2023-04-28 | 广州世炬网络科技有限公司 | 自回传iab网络中iab宿主节点切换方法、装置、设备及介质 |
Also Published As
Publication number | Publication date |
---|---|
US20230199575A1 (en) | 2023-06-22 |
EP4192101A1 (en) | 2023-06-07 |
EP4192101A4 (en) | 2023-08-30 |
CN115669058A (zh) | 2023-01-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
TWI713341B (zh) | 5g會話管理狀態映射的方法及使用者設備 | |
WO2022041249A1 (zh) | 一种节点的切换方法以及相关设备 | |
KR102357070B1 (ko) | 통신 방법, 디바이스 및 시스템 | |
CN113556794B (zh) | 通信方法、装置及*** | |
WO2019242749A1 (zh) | 一种切换方法及装置 | |
JP2021518079A (ja) | パケット伝送方法、装置、およびシステム | |
JP7516578B2 (ja) | Iabネットワーク通信方法及び関連デバイス | |
WO2022082679A1 (zh) | 一种通信方法及相关设备 | |
WO2017118191A1 (zh) | 一种控制面信息的传输方法及装置 | |
US11503667B2 (en) | Enhancement for multi-access PDU session release | |
EP4185005A1 (en) | Communication method and communication apparatus for integrated access and backhaul (iab) system | |
WO2022151400A1 (zh) | 一种用于接入回传一体化iab***中的通信方法和通信装置 | |
WO2023011245A1 (zh) | 通信方法和通信装置 | |
US20230171651A1 (en) | Logical channel lch configuration method, communication apparatus, and communication system | |
CN111148158B (zh) | 一种通信方法及装置 | |
WO2021238882A1 (zh) | 一种实现业务连续性的方法及装置 | |
CN108781403B (zh) | 终端设备、接入网设备、空口配置方法和无线通信*** | |
US20230262827A1 (en) | Communication method applied to integrated access and backhaul iab system and related device | |
WO2021159238A1 (zh) | 一种数据处理方法、通信装置和通信*** | |
WO2023246746A1 (zh) | 一种通信方法及相关设备 | |
US20230133792A1 (en) | Handling of collision between pdu session establishment and modification procedure | |
WO2023066223A1 (zh) | 通信方法、通信装置、以及机算机存储介质 | |
WO2023273824A1 (zh) | 切换方法、装置、网络设备及中继终端 | |
WO2023024384A1 (zh) | 小区切换、配置方法及装置、计算机可读存储介质、用户设备、网络设备 | |
WO2022027653A1 (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: 20950918 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2020950918 Country of ref document: EP Effective date: 20230301 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |