WO2021027817A1 - Parent node selection method and apparatus, device and medium - Google Patents

Parent node selection method and apparatus, device and medium Download PDF

Info

Publication number
WO2021027817A1
WO2021027817A1 PCT/CN2020/108483 CN2020108483W WO2021027817A1 WO 2021027817 A1 WO2021027817 A1 WO 2021027817A1 CN 2020108483 W CN2020108483 W CN 2020108483W WO 2021027817 A1 WO2021027817 A1 WO 2021027817A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab
node
parent node
function
donor
Prior art date
Application number
PCT/CN2020/108483
Other languages
French (fr)
Chinese (zh)
Inventor
刁雪莹
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2021027817A1 publication Critical patent/WO2021027817A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point

Definitions

  • This application relates to the field of wireless communication, and in particular to a method, device, equipment and medium for selecting a parent node.
  • the high transmission speed of 5G networks is mainly due to the use of millimeter waves.
  • millimeter waves have large attenuation in the air and weak diffraction capabilities.
  • the integrated access and backhaul links (IAB) technology Been proposed.
  • the self-access backhaul link includes the wireless access link and the wireless backhaul link.
  • the wireless access link is the communication link between the UE (User Equipment) and the IAB node, and the wireless backhaul link is the IAB
  • the communication link between nodes is used for data return, so the IAB node does not need a wired transmission network for data return.
  • the IAB node When an IAB node accesses the network, the IAB node may be connected to a DU (Distributed Unit, distributed unit entity) or base station that does not support the IAB function. At this time, the IAB node cannot implement its IAB function.
  • DU Distributed Unit, distributed unit entity
  • This application provides a method, device, equipment, and medium for selecting a parent node to ensure that an IAB node can realize its IAB function.
  • an embodiment of the present application provides a method for selecting a parent node, which is applied to an IAB node, including:
  • an embodiment of the present application provides a method for selecting a parent node, which is applied to an access management function entity, including:
  • the IAB authorization indication information of the IAB node or the IAB node After the IAB node determines the target parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node’s access to the network, the IAB authorization indication information of the IAB node or the IAB node’s
  • the IAB node instruction is sent to the donor centralized unit entity or base station corresponding to the target parent node.
  • an embodiment of the present application provides a parent node selection device, which is applied to an IAB node, and is characterized in that it includes:
  • the first parent node selection module is used to determine the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.
  • an embodiment of the present application provides a parent node selection device, which is applied to an access management function entity, and includes:
  • the second parent node selection module is configured to determine the target parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node’s access to the network, and then send the IAB authorization indication information of the IAB node or The IAB node indication of the IAB node is sent to the donor centralized unit entity or the base station corresponding to the target parent node.
  • an embodiment of the present application provides an IAB node, including: one or more processors; a storage device, configured to store one or more programs; when the one or more programs are used by the one or more The processor executes, so that the one or more processors implement the parent node selection method applied to the IAB node as described in any embodiment of the present application.
  • an embodiment of the present application provides a storage medium, the storage medium stores a computer program, and when the computer program is executed by a processor, it is applied to the parent of the IAB node as described in any embodiment of the present application. Node selection method.
  • an embodiment of the present application provides an access management function entity, including: one or more processors; a storage device, configured to store one or more programs; when the one or more programs are used by the one Or multiple processors execute, so that the one or more processors implement the parent node selection method applied to the access management functional entity as described in any embodiment of the present application.
  • an embodiment of the present application provides a storage medium that stores a computer program that, when executed by a processor, implements the application to an access management function entity as described in any embodiment of the present application The parent node selection method in.
  • Figure 1 is a schematic diagram of network IAB deployment
  • Figure 2 is a schematic diagram of network IAB deployment with separated CU and DU;
  • FIG. 3 is a schematic flowchart of a method for selecting a parent node provided by this application.
  • Figure 4 is a schematic diagram of the first IAB node deployment scenario provided by this application.
  • FIG. 5 is a schematic diagram of the second IAB node deployment scenario provided by this application.
  • FIG. 6 is a schematic diagram of the third deployment scenario of IAB nodes provided by this application.
  • FIG. 7 is a schematic diagram of the fourth IAB node deployment scenario provided by this application.
  • Figure 8 is a schematic diagram of a fifth IAB node deployment scenario provided by this application.
  • FIG. 9 is a schematic diagram of the sixth IAB node deployment scenario provided by this application.
  • FIG. 10 is a schematic flowchart of a method for selecting a parent node provided by this application.
  • FIG. 11 is a schematic structural diagram of a parent node selection device provided by this application.
  • FIG. 12 is a schematic structural diagram of a parent node selection device provided by this application.
  • FIG. 13 is a schematic structural diagram of an IAB node provided by this application.
  • FIG. 14 is a schematic structural diagram of an access management function entity provided by this application.
  • FIG. 1 An example of a network deployed with IAB is shown in Figure 1.
  • the figure includes node 10, node 20, and node 30.
  • Node 10 is connected to the core network through a wired connection, for example, node 10 is connected to the core network through optical fiber 11.
  • the node 20 and the node 30 send and receive data to the core network through the node 10.
  • User Equipment (UE) can access node 10, node 20, and node 30 through an access link, and data can be transmitted between nodes through a wireless backhaul link (BH link).
  • IAB node an access node that supports wireless access and wireless backhaul of data
  • IAB node an IAB node
  • IAB node an access node that supports wireless access and wireless backhaul of data
  • the wireless backhaul function is provided for the IAB node, so that the access node that connects the UE to the core network is called an IAB donor (IAB donor), such as the node 10 in FIG. 1.
  • IAB donor IAB donor
  • the node 20 may send data received from the UE to the node 10 through a wireless backhaul link, and the access node 10 then sends the UE data to the core network element.
  • the core network element sends the UE data packet to the node 10
  • the access node 10 then sends the UE data to the node 20 through the wireless backhaul link, and then the access node 20 sends the UE data through the access link To the UE.
  • FIG. 2 is a schematic diagram of the network IAB deployment in which CU and DU are separated.
  • IAB nodes can have DU-like functions and MT (Mobile Terminal, mobile terminal)-like functions.
  • MT-like functions are also UE-like functions.
  • IAB nodes access two parent IAB nodes through dual connections, that is, IAB The nodes connect to the parent IAB node 1 and the parent IAB node 2 respectively through dual connections.
  • the IAB node When the IAB node accesses the network, there may be DUs or base stations that do not support the IAB function near the IAB node. If the IAB node is connected to a DU or base station that does not support the IAB function, it will not be able to serve other child IAB nodes or UEs.
  • FIG. 3 is a schematic flowchart of a method for selecting a parent node provided by this application. This method can be applied to the situation where the IAB selects a parent node that supports the IAB function when accessing the network. This method can be executed by the parent node selection device applied to the IAB node provided by the present application, and the parent node selection device can be implemented by software and/or hardware and integrated in the IAB node.
  • a parent node selection method applied to IAB nodes includes:
  • S120 Determine the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.
  • the IAB node of an IAB node is called the child IAB node of the IAB node, and the DU or base station supporting the IAB function accessed by an IAB node as a connection is called the parent IAB node of the IAB node.
  • the network access of IAB nodes can be divided into initial access and non-initial access.
  • the deployment scenarios of IAB node access to the network can be divided into multiple types. Specifically, the DU entity and base station in the area can be set according to the deployment location.
  • the IAB function can be divided according to whether the AMF (Access and Mobility Management Function) entity connected to the base station that does not support the IAB function supports the IAB function, and it can also be divided according to the DU entity that does not support the IAB function. Whether the CU entity supports the IAB function, and whether the further connected AMF entity supports the IAB function.
  • AMF Access and Mobility Management Function
  • the IAB node selects the parent node that supports the IAB function, it can be determined by combining the access situation of the IAB node and the deployment scenario of the access network. In different access situations and different deployment scenarios, the way the IAB node selects the parent node may be the same or different.
  • the IAB node may be a DU entity or an MT.
  • This application provides a method for selecting a parent node.
  • the parent node of the IAB node is determined according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network, which effectively solves how the IAB node
  • the problem of selecting the parent node ensures that the parent node selected by the IAB node supports the IAB function, thereby ensuring the IAB function of the IAB node, and achieving the effect of serving other child IAB nodes and UEs.
  • the deployment scenarios for the IAB node to access the network may include the following six deployment scenarios.
  • the first scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station supporting the IAB function.
  • the donor central unit entity (donor CU) 101 is connected to the donor DU102 through the F1 interface, and the donor DU 102 is connected to the IAB node 103 through the backhaul link (BH link).
  • the donor CU 101, the donor DU102 and IAB nodes 103 all support IAB functions.
  • the IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the first scenario, such as an IAB mobile terminal (IAB-MT) that is undergoing initial access, and all DUs and base stations near the deployed location support IAB function.
  • IAB-MT IAB mobile terminal
  • the second scenario is: the IAB node deployment location setting area includes the IAB donor DU and the distributed unit entity that does not support the IAB function, and the distributed unit entity that does not support the IAB function is connected to the donor centralized unit entity donor CU.
  • the donor CU 101 is connected to the donor DU 102 through the F1 interface, and is connected to the normal distribution unit entity (normal DU) 105, and the donor DU 102 is connected to the IAB node 103 through the BH link.
  • the donor CU 101, Both the donor DU 102 and the IAB node 103 support the IAB function, and the conventional distributed unit entity 105 does not support the IAB function.
  • the IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the second scenario, for example, an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support IAB functions Donor DU 102, and normal DU 105 that does not support IAB.
  • the third scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station that does not support the IAB function, and the access management function entity connected to the base station supports the IAB function.
  • AMF 107 is connected to donor CU 101 through the NG interface and connected to base station (gNB) 106.
  • the AMF 107 connected to donor CU 101 and the AMF 107 connected to gNB 106 can be the same AMF or They are different AMFs, shown in Figure 6 as an example.
  • the donor CU 101 is connected to the donor DU 102 through the F1 interface, and the donor DU 102 is connected to the IAB node 103 through the BH link.
  • AMF 107, donor CU 101, donor DU 102 and IAB node 103 all support the IAB function, but gNB 106 does not. IAB function.
  • the IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the third scenario, such as an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support the IAB function Donor DU 102, and gNB 106 that does not support the IAB function, but the AMF 107 connected to the gNB 106 supports the IAB function, and other core network network elements connected to the AMF 107 have network elements that support the IAB function.
  • the fourth scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station that does not support the IAB function, and the access management function entity connected to the base station does not support the IAB function.
  • AMF 107 is connected to donor CU 101 through the NG interface, and AMF 108 is connected to gNB 106 through the NG interface.
  • the donor CU 101 is connected to the donor DU 102 through the F1 interface, and the donor DU 102 is connected to the IAB node 103 through the BH link.
  • AMF 107, donor CU 101, donor DU 102 and IAB node 103 all support the IAB function, while AMF 108 and gNB 106 does not support the IAB function.
  • the IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the fourth scenario, for example, an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support IAB functions.
  • the donor DU 102 and the gNB 106 that does not support the IAB function, and the AMF 108 connected to the gNB 106 that does not support the IAB function also does not support the IAB function.
  • the fifth scenario is: the IAB node deployment location setting area includes IAB donor DU, the IAB node and the distributed unit entity that does not support the IAB function, and the centralized unit entity connected to the distributed unit entity that does not support the IAB function does not support IAB function, the access management function entity connected with the centralized unit entity supports the IAB function.
  • AMF 107 is connected to donor CU 101 through the NG interface and connected to normal CU109.
  • AMF 107 connected to donor CU 101 and AMF 107 connected to normal CU 109 can be the same AMF or different
  • the AMF is shown in Figure 8 with different examples.
  • the donor CU101 is connected to the donor DU 102 through the F1 interface
  • the donor DU 102 is connected to the IAB node 103 through the BH link
  • the normal CU 109 is connected to the normal DU105 through the F1 interface.
  • AMF 107, donor CU 101, donor DU 102 and IAB node 103 Both support IAB function, but normal CU109 and normal DU105 do not support IAB function.
  • the IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the fifth scenario, for example, an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support IAB functions Donor DU 102, and normal DU105 that does not support IAB function, and normal CU 109 connected to normal DU105 does not support IAB function, but AMF 107 connected to normal CU 109 supports IAB function, and other core networks connected to AMF 107 Among the network elements, there are network elements that support the IAB function.
  • the sixth scenario is: the IAB node deployment location setting area includes IAB donor DU, the IAB node and the distributed unit entity that does not support the IAB function, and the centralized unit entity connected to the distributed unit entity that does not support the IAB function does not support IAB function, the access management function entity connected to the centralized unit entity does not support the IAB function.
  • AMF 107 is connected to donor CU 101 through an NG interface
  • AMF 108 is connected to normal CU 109 through an NG interface
  • Donor CU 101 is connected to donor DU 102 through F1 interface
  • donor DU 102 is connected to IAB node 103 through BH link
  • normal CU 109 is connected to normal DU 105 through F1 interface.
  • AMF 107, donor CU 101, donor DU 102 and IAB node 103 all support IAB function
  • AMF 108, normal CU 109 and normal DU105 do not support IAB function.
  • the IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the sixth scenario, for example, an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support IAB functions.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is one of the first to sixth scenarios
  • the determining the parent node of the IAB node includes :
  • the parent node of the IAB node is selected from the parent node list pre-configured by the IAB node.
  • the IAB node When the IAB node is initially accessed, when the deployment scenario is any of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node may have a pre-configuration A list of parent nodes, and then you can select one of its pre-configured parent node lists as its parent node.
  • the IAB node When the IAB node is non-initial access, when the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node may also have A pre-configured parent node list, and in turn, you can select one of the pre-configured parent node lists as its parent node.
  • the pre-configured parent node list is configured by an Operation Administration and Maintenance (OAM) entity, and is added to the configuration information of the IAB node before the IAB node is established.
  • OAM Operation Administration and Maintenance
  • the nodes included in the pre-configured parent node list all support the IAB function.
  • the pre-configured parent node list of the IAB node includes at least one of the following:
  • PLMN Public Land Mobile Network
  • the above method further includes: when the IAB node accesses the cell, judging the IAB according to whether the radio resource control (Radio Resource Control, RRC) reconfiguration message includes a backhaul adaptive protocol layer configuration message Whether the distributed unit entity or base station accessed by the node supports IAB function.
  • RRC Radio Resource Control
  • the IAB node Regardless of whether the IAB node is initially accessed or non-initially accessed, after the IAB node accesses any suitable cell, it can determine whether it is accessed according to whether the RRC reconfiguration message includes a backhaul adaptive protocol layer configuration message. Whether the distributed unit entity or the base station supports the IAB function. When the RRC reconfiguration message includes the backhaul adaptive protocol layer configuration message, the distributed unit entity or base station accessed by the IAB node supports the IAB function; when the RRC reconfiguration message does not include the backhaul adaptive protocol layer configuration message, The distributed unit entity or base station accessed by the IAB node does not support the IAB function.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is one of the first to sixth scenarios
  • the determining the parent node of the IAB node includes :
  • the parent node of the IAB node is selected based on the system information broadcast by the cell.
  • the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios
  • the IAB node accesses the network A node can be selected as its parent node based on the received system information broadcast by the cell.
  • the IAB node accesses the network It is also possible to select a node as its parent node according to the received system information broadcast by the cell.
  • selecting the parent node of the IAB node based on the system information broadcast by the cell includes:
  • the system information broadcast by the cell includes the IAB dedicated physical random access channel (Physical Random Access Channel, PRACH) configuration, it is determined whether the cell accessed by the IAB node supports the IAB function.
  • PRACH Physical Random Access Channel
  • the system information broadcast by the IAB node includes the IAB-specific PRACH configuration
  • the system information broadcast by the IAB node does not include the IAB-specific During PRACH configuration
  • selecting the parent node of the IAB node based on the system information broadcast by the cell includes:
  • the IAB node Determine whether the cell accessed by the IAB node supports the IAB function according to whether the system information broadcast by the cell includes IAB dedicated system information, where the IAB dedicated system information includes cell access barring information, admission control parameters, and cell selection parameters , At least one of the cell reselection parameters.
  • the system information broadcast by the cell received by the IAB node includes the IAB dedicated system information
  • the system information broadcast by the IAB node does not include the IAB dedicated system information
  • selecting the parent node of the IAB node based on the system information broadcast by the cell includes:
  • the parent node of the IAB node is selected based on the system information used for cell reselection broadcast by the IAB node or the IAB host distribution unit entity.
  • the IAB node may receive the system information used for cell reselection broadcast by other IAB nodes or IAB donor CU, where the system information used for cell reselection broadcast by the IAB node or IAB donor CU includes at least one of the following:
  • the access situation of the IAB node is initial access
  • the deployment scenario is one of the first to sixth scenarios
  • the determining the parent node of the IAB node includes:
  • the IAB node accesses the cell, obtain a parent node list in the configuration information of the operation management and maintenance entity; select the parent node of the IAB node from the parent node list.
  • the IAB node When the IAB node is initially accessed, when the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node accesses any one After a suitable cell, it establishes a connection with OAM and obtains OAM configuration information.
  • the OAM configuration information includes a parent node list, and the IAB node can select a node from the parent node list as its parent node.
  • the parent nodes in the parent node list acquired in the OAM configuration information all support the IAB function.
  • the parent node list obtained in the OAM configuration information includes at least one of the following:
  • the access situation of the IAB node is non-initial access
  • the deployment scenario is one of the first to sixth scenarios
  • the determining the parent node of the IAB node includes:
  • the IAB node selects the parent node of the IAB node from the parent node list obtained from the configuration information of the operation management and maintenance entity.
  • the IAB node When the IAB node is a non-initial access, and the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node has already switched from OAM
  • the parent node list obtained in the OAM is stored locally in the IAB node, and then a node can be selected as its parent node from the parent node list obtained from the OAM.
  • the nodes in the parent node list obtained from OAM all support the IAB function.
  • the parent node list obtained from OAM includes at least one of the following:
  • the access situation of the IAB node is non-initial access
  • the deployment scenario is one of the first to sixth scenarios
  • the determining the parent node of the IAB node includes:
  • the IAB node selects the parent node of the IAB node from a list of parent nodes that the IAB node has obtained from the host centralized unit entity.
  • the IAB node When the IAB node is non-initial access, when the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node has been transferred from the donor
  • the parent node list obtained in the CU is stored locally on the IAB node, and then a node can be selected as its parent node from the parent node list obtained from the donor CU.
  • the parent node list stored by the donor CU may specifically include at least one of IAB donor DU, IAB node, and gNB supporting the IAB function.
  • the parent node list obtained from donor CU includes at least one of the following:
  • obtaining the parent node list from the unit entity of the host centralization includes:
  • the host central unit entity is requested to send the parent node list through a message, so that the host central unit entity sends the parent node list to the IAB node after receiving the request.
  • the IAB node wants to obtain the parent node list in the donor CU, it can send a request message to the donor CU, for example, a radio resource control layer request message, to request the donor CU to send the parent node list to the IAB node. After the donor CU receives the RRC request message, it sends the parent node list to the IAB node.
  • a request message for example, a radio resource control layer request message
  • the donor CU After the donor CU receives the RRC request message, it sends the parent node list to the IAB node.
  • requesting the host central unit entity to send a list of parent nodes through a message includes:
  • the donor centralization unit entity is requested to send the parent node list.
  • the IAB node When the IAB node requests the donor CU to send the parent node list through the RRC message, it can specifically request the donor CU to send the parent node list through the radio resource control layer setup request (RRC Setup Request) message, or it can be completed through the radio resource control layer (RRC Setup Complete) )
  • RRC Setup Request radio resource control layer setup request
  • RRC Setup Complete radio resource control layer
  • the message requests the donor CU to send the parent node list, and the radio resource control layer reconfiguration complete (RRC Reconfiguration Complete) message can also request the donor CU to send the parent node list.
  • requesting the host central unit entity to send a list of parent nodes through a message includes:
  • the host central unit entity Through an F1 establishment request message, a gNB-DU configuration update message, or a new F1 Application Protocol (F1 Application Protocol, F1AP) message, the host central unit entity is requested to send a list of parent nodes.
  • F1 Application Protocol F1AP
  • the IAB node When the IAB node requests the donor CU to send the parent node list through a message, it can specifically request the donor CU to send the parent node list through the F1 establishment request message, or through the gNB-DU configuration update message to request the donor CU to send the parent node list, or through the new The F1AP message requests the donor CU to send the list of parent nodes.
  • obtaining the parent node list from the unit entity of the host centralization includes:
  • the parent node list sent by the donor CU received by the IAB may also be sent by the donor CU actively through the RRC message.
  • receiving the parent node list actively sent by the host central unit entity through a radio resource control layer message includes:
  • the donor CU When the donor CU actively sends the parent node list to the IAB node through the RRC message, it can send the parent node list to the IAB node through the radio resource control layer reconfiguration (RRC Reconfiguration) message, or through the radio resource control layer release (RRC Release) message.
  • RRC Reconfiguration radio resource control layer reconfiguration
  • RRC Release radio resource control layer release
  • the IAB node sends the parent node list, and can also send the parent node list to the IAB node through a radio resource control layer reject (RRC Reject) message.
  • RRC Reject radio resource control layer reject
  • the nodes in the parent node list sent by the donor CU to the IAB node all support the IAB function.
  • the parent node list sent by the donor CU to the IAB node includes at least one of the following:
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the determining the parent node of the IAB node includes:
  • the donor centralization unit entity determines that the DU accessed by the IAB node does not support the IAB function, it re-determines the IAB node's status according to the auxiliary operation of the donor centralization unit entity Parent node.
  • the donor CU determines whether the DU accessed by the IAB node supports the IAB function.
  • the DU accessed by the IAB node does not support the IAB function, and the donor CU assists the IAB node to reselect a node as its parent node.
  • the donor CU determines whether the DU accessed by the IAB node supports the IAB function.
  • the DU accessed by the IAB node does not support the IAB function, and the donor CU assists the IAB node to reselect a node as its parent node.
  • re-determining the parent node of the IAB node according to the auxiliary operation of the unit entity in the host set includes:
  • the parent node supporting the IAB function corresponding to the switching instruction is re-determined as the parent node of the IAB node.
  • the donor CU When the donor CU judges that the DU accessed by the IAB node does not support the IAB function, it may send a switching instruction to the IAB node to switch the parent node of the IAB node to a node that supports the IAB function.
  • re-determining the parent node of the IAB node according to the auxiliary operation of the unit entity in the host set includes:
  • the donor CU judges that the DU accessed by the IAB node does not support the IAB function, if the IAB node has completed the connection with the DU that does not support the IAB function, it can send an RRC release message to the IAB node to enable the After the IAB node receives the RRC release message sent by the donor CU, it disconnects the DU that does not support the IAB function.
  • the donor CU sends a parent node list to the IAB node through an RRC message. After receiving the parent node list sent by the donor CU, the IAB node reselects a node as its parent node based on the parent node list.
  • re-determining the parent node of the IAB node according to the auxiliary operation of the unit entity in the host set includes:
  • the donor CU judges that the DU accessed by the IAB node does not support the IAB function, if the IAB node is already establishing a connection with the DU that does not support the IAB function, it can send an RRC rejection message to the IAB node so that all After the IAB node receives the RRC rejection message sent by the donor CU, it abandons the continued connection operation with this DU that does not support the IAB function, and after receiving the parent node list sent by the donor CU, re-starts based on the parent node list. Select a node as its parent node.
  • the nodes in the parent node list sent by the donor CU through the RRC message all support the IAB function.
  • the parent node list sent by the donor CU to the IAB node through the RRC message includes at least one of the following:
  • the list of parent nodes obtained from the unit entity in the host set includes:
  • the parent node list sent by the donor CU may include donor DU and IAB nodes connected to the donor CU, and may also include donor DU and IAB nodes connected to base stations adjacent to the donor CU.
  • the method for the host central unit entity to learn whether the DU supports the IAB function includes:
  • the DU it is indicated in the F1 establishment request message or the gNB-DU configuration update message or the new F1AP message that the DU supports the IAB function.
  • the DU can indicate to the donor CU that it supports the IAB function through an F1 establishment request message or a gNB-DU configuration update message or a new F1AP message.
  • the method of generating or updating the parent node list by the host central unit entity includes:
  • the donor centralized unit entity obtains a list of base stations supporting the IAB function from the configuration information of the operation, management and maintenance entity, where the list of base stations supporting the IAB function includes information of base stations supporting the IAB function and information of serving cells supporting the IAB function.
  • Donor CU can obtain a list of base stations that support the IAB function from OAM, where the base station list obtained from OAM can include information about base stations that support the IAB function, and can also include information about serving cells that support the IAB function.
  • the method of generating or updating the parent node list by the host central unit entity includes:
  • the donor centralization unit entity exchanges the information of the serving cell supporting the IAB function with the neighboring base station through the Xn establishment request message or the Next Generation Radio Access Network (NG-RAN) node configuration update information.
  • NG-RAN Next Generation Radio Access Network
  • the donor CU can use the Xn establishment request to interact with neighboring base stations to support the serving cell information of the IAB function, or through the NG-RAN node configuration update information to interact with the neighboring base station to support the IAB function of the serving cell information, so as to obtain the neighboring base station Serving cell information that supports the IAB function.
  • re-determining the parent node of the IAB node according to the auxiliary operation of the host central unit entity includes:
  • the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, the parent node of the IAB node is re-determined according to the auxiliary operation of the donor centralized unit entity.
  • re-determining the parent node of the IAB node according to the auxiliary operation of the host central unit entity includes:
  • the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, the parent node of the IAB node is re-determined according to the auxiliary operation of the donor centralized unit entity.
  • re-determining the parent node of the IAB node according to the auxiliary operation of the host central unit entity includes:
  • the donor centralized unit entity learns that the IAB node supports the IAB function through the IAB authorization indication carried in the initial context establishment request message, and determines that the DU accessed by the IAB node does not support the IAB function, the donor centralized unit The auxiliary operation of the entity redefines the parent node of the IAB node.
  • the IAB node may indicate its IAB node identity to the donor CU in the RRC establishment request message, and may also indicate its IAB node identity to the donor CU in the RRC establishment complete message.
  • the donor CU can also learn the IAB node identity of a node in the IAB authorization indication carried in the initial context establishment request message, that is, learn that it supports the IAB function.
  • re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:
  • the IAB node When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can send an RRC rejection message to the IAB node (this When the RRC establishment complete message sent by the IAB node is not received), the IAB node re-selects the cell after receiving the RRC reject message.
  • the radio resource control layer rejection message includes at least one of the following:
  • the donor CU When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, in an example, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can receive the IAB After the RRC establishment complete message sent by the node, the RRC release message is sent to the IAB node, and the IAB node performs cell selection again after receiving the RRC release message.
  • the RRC release message includes at least one of the following:
  • re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:
  • the donor CU When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the initial access of the IAB node After the process ends, an RRC release message is sent to the IAB node, and after receiving the RRC release message, the IAB node performs cell selection again.
  • the RRC release message includes at least one of the following:
  • re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:
  • the parent node supporting the IAB function corresponding to the handover instruction is re-determined as the parent node of the IAB node.
  • the donor CU When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the initial access of the IAB node After the process is over, a switch instruction is sent to the IAB node to switch the parent node of the IAB node to a node that supports the IAB function.
  • re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:
  • the donor CU When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment complete message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can send an RRC release message to the IAB node After receiving the RRC release message, the IAB node performs cell selection again.
  • the RRC release message includes at least one of the following:
  • re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:
  • the donor CU When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment complete message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the initial access of the IAB node After the process ends, it sends an RRC release message to the IAB node, and after receiving the RRC release message, the IAB node performs cell selection again.
  • the RRC release message includes at least one of the following:
  • re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:
  • the parent node supporting the IAB function corresponding to the handover instruction is re-determined as the parent node of the IAB node.
  • the donor CU When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment complete message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the initial access of the IAB node After the process is over, a switch instruction is sent to the IAB node to switch the parent node of the IAB node to a node that supports the IAB function.
  • the parent node of the IAB node is re-determined according to the auxiliary operation of the host centralized unit entity, include:
  • the donor CU When the donor CU learns the IAB node identity of the IAB node in the IAB authorization indication carried in the initial context establishment request message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the IAB node After the initial access procedure ends, an RRC release message is sent to the IAB node, and the IAB node performs cell selection again after receiving the RRC release message.
  • the RRC release message includes at least one of the following:
  • the parent node of the IAB node is re-determined according to the auxiliary operation of the host centralized unit entity, include:
  • the parent node supporting the IAB function corresponding to the handover instruction is re-determined as the parent node of the IAB node.
  • the donor CU When the donor CU learns the IAB node identity of the IAB node in the IAB authorization indication carried in the initial context establishment request message, the donor CU can send a handover instruction to the IAB node after waiting for the end of the initial access process of the IAB node to transfer the IAB node The parent node of the node switches to a node that supports the IAB function.
  • the above method further includes: updating the locally stored parent node list according to the configuration update information sent by the operation management and maintenance entity.
  • the IAB node In the case that the IAB node has stored the parent node list locally, if the OAM configures the parent node list for the IAB node, the IAB node can update the locally stored parent node list according to the configuration information of the OAM.
  • the OAM may send the parent node information whose IAB function has changed to the IAB node, so that the IAB node can pair the parent node information according to the received IAB function change.
  • the locally stored parent node list is updated.
  • the OAM may send the updated parent node list to the IAB node, so that the IAB node can update the locally stored parent node list according to the received parent node list.
  • the parent node list stored by OAM includes at least one of the following:
  • the above method further includes: updating the locally stored parent node list according to the parent node update information sent by the host central unit entity.
  • the donor CU stores a list of IAB donor DU and/or IAB nodes and/or gNB that support the IAB function. If the list stored in the donor CU changes, the parent node update information is sent to the IAB node to make the IAB node Update the locally stored parent node list.
  • updating the locally stored parent node list according to the parent node update information sent by the host central unit entity includes:
  • the locally stored parent node list is updated according to the parent node information of the IAB function change sent by the donor centralized unit entity through the radio resource control layer message or the F1 establishment response message or the gNB-CU configuration update message or the new F1AP message.
  • the donor CU can send the IAB donor DU, IAB node, and gNB whose IAB function has changed to the IAB node, which can be The RRC reconfiguration message or the F1 establishment response message or the gNB-CU configuration update message or the new F1AP message is sent to the IAB node, so that the IAB node updates the local parent node list.
  • updating the locally stored parent node list according to the parent node update information sent by the host central unit entity includes:
  • the locally stored parent node list is updated according to the updated parent node list sent by the donor centralization unit entity through a radio resource control layer message or an F1 establishment response message or a gNB-CU configuration update message or a new F1AP message.
  • the donor CU can send the locally updated parent node list to the IAB node, which can be established through the RRC reconfiguration message or F1 A response message or a gNB-CU configuration update message or a new F1AP message is sent to the IAB node, so that the IAB node updates the local parent node list.
  • the IAB node may also update the local parent node list according to the parent node list carried in the RRC release message.
  • the IAB node may also update the local parent node list according to the parent node list carried in the RRC rejection message.
  • the parent node list stored in the donor CU includes at least one of the following:
  • FIG. 10 is a schematic flowchart of a method for selecting a parent node provided by this application. This method can be applied to the situation where the IAB selects a parent node that supports the IAB function when accessing the network. The method can be executed by the parent node selection device applied to the AMF entity provided in this application, and the parent node selection device can be implemented by software and/or hardware and integrated in the AMF entity.
  • a parent node selection method applied to an AMF entity provided by this application includes:
  • S220 Based on the handover of the NG interface, send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralization unit entity or the base station corresponding to the target parent node.
  • the handover based on the NG interface mainly includes the case where the donor CU or the base station connected to the IAB node is connected to the same AMF entity, the case of connecting different AMF entities, and the case of connecting to different RATs (Radio Access Technology, radio Access technology).
  • the donor CU or the base station connected to the IAB node is connected to the same AMF entity, the case of connecting different AMF entities, and the case of connecting to different RATs (Radio Access Technology, radio Access technology).
  • RATs Radio Access Technology, radio Access technology
  • the IAB node determines the target parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node’s access to the network
  • the IAB node The IAB authorization indication information or the IAB node indication of the IAB node is sent to the donor central unit entity or base station corresponding to the target parent node, which realizes the connection between the IAB node and the parent node that supports the IAB function selected by the IAB node.
  • the IAB function is guaranteed, and the effect of serving other sub-IAB nodes and UEs is achieved.
  • sending the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralization unit entity or base station corresponding to the target parent node includes:
  • sending the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralization unit entity or base station corresponding to the target parent node includes:
  • FIG. 11 is a schematic structural diagram of a parent node selection device provided by this application. As shown in FIG. 11, an embodiment of this application provides a parent node applied to an IAB node. The selection device can be integrated in the IAB node. The device includes:
  • the first parent node selection module 320 is configured to determine the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.
  • the device for selecting a parent node applied to an IAB node provided in this embodiment is used to implement the method for selecting a parent node applied to an IAB node as described in the embodiment of this application.
  • the parent node selection method provided in this embodiment is applied to an IAB node.
  • the implementation principle and technical effect of the selection device are similar to the parent node selection method applied to the IAB node described in the embodiment of the present application, and will not be repeated here.
  • the IAB node of an IAB node is called the child IAB node of the IAB node, and the DU or base station supporting the IAB function accessed by an IAB node as a connection identity is called the parent IAB node of the IAB node.
  • the IAB node may be a DU entity or an MT.
  • the deployment scenarios for the IAB node to access the network may include the following six deployment scenarios.
  • the first scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station supporting the IAB function.
  • the second scenario is: the IAB node deployment location setting area includes the IAB donor DU and the distributed unit entity that does not support the IAB function, and the distributed unit entity that does not support the IAB function is connected to the donor centralized unit entity donor CU.
  • the third scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station that does not support the IAB function, and the access management function entity connected to the base station supports the IAB function.
  • the fourth scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station that does not support the IAB function, and the access management function entity connected to the base station does not support the IAB function.
  • the fifth scenario is: the IAB node deployment location setting area includes IAB donor DU, the IAB node and the distributed unit entity that does not support the IAB function, and the centralized unit entity connected to the distributed unit entity that does not support the IAB function does not support IAB function, the access management function entity connected with the centralized unit entity supports the IAB function.
  • the sixth scenario is: the IAB node deployment location setting area includes IAB donor DU, the IAB node and the distributed unit entity that does not support the IAB function, and the centralized unit entity connected to the distributed unit entity that does not support the IAB function does not support IAB function, the access management function entity connected to the centralized unit entity does not support the IAB function.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is one of the first to sixth scenarios
  • the first parent node selection module 320 is set to: The parent node of the IAB node is selected from the parent node list preconfigured by the IAB node.
  • the pre-configured parent node list of the IAB node includes at least one of the following:
  • the above-mentioned apparatus further includes a parent node IAB function judgment module, which is set to judge whether the radio resource control layer reconfiguration message includes a backhaul adaptive protocol layer configuration message when the IAB node accesses the cell. Whether the distributed unit entity or base station accessed by the IAB node supports the IAB function.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is one of the first to sixth scenarios
  • the first parent node selection module 320 is set to:
  • the broadcasted system information selects the parent node of the IAB node.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is one of the first to sixth scenarios
  • the first parent node selection module 320 is set to: Whether the broadcast system information includes the IAB-specific PRACH configuration, it is determined whether the cell accessed by the IAB node supports the IAB function.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is one of the first to sixth scenarios
  • the first parent node selection module 320 is set to: Whether the broadcasted system information includes IAB dedicated system information, determine whether the cell accessed by the IAB node supports the IAB function, where the IAB dedicated system information includes cell access barring information, admission control parameters, cell selection parameters, cell Reselect at least one of the parameters.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is one of the first to sixth scenarios
  • the first parent node selection module 320 is set to: The system information used for cell reselection broadcast by the node or the IAB host distribution unit entity selects the parent node of the IAB node.
  • the system information used for cell reselection broadcast by the IAB node or IAB donor CU includes at least one of the following:
  • the access condition of the IAB node is initial access
  • the deployment scenario is one of the first to sixth scenarios
  • the first parent node selection module 320 is set to: the IAB node accesses the cell In the case of obtaining the parent node list in the configuration information of the operation management and maintenance entity; selecting the parent node of the IAB node from the parent node list.
  • the parent node list obtained in the OAM configuration information includes at least one of the following:
  • the access condition of the IAB node is non-initial access
  • the deployment scenario is one of the first to sixth scenarios
  • the first parent node selection module 320 is configured to: The parent node of the IAB node is selected from the parent node list obtained in the OAM configuration information.
  • the parent node list obtained from OAM includes at least one of the following:
  • the access condition of the IAB node is non-initial access
  • the deployment scenario is one of the first to sixth scenarios
  • the first parent node selection module 320 is configured to: The parent node of the IAB node is selected from the acquired parent node list in the unit entity of the host centralization.
  • the parent node list obtained from donor CU includes at least one of the following:
  • the first parent node selection module 320 is configured to request the host central unit entity to send a parent node list through a message, so that the host central unit entity sends the parent node list to the IAB node after receiving the request , And select the parent node of the IAB node from the list of parent nodes that the IAB node has obtained from the host centralized unit entity.
  • the first parent node selection module 320 is configured to request the donor central unit entity to send the parent node through a radio resource control layer establishment request message or a radio resource control layer establishment completion message or a radio resource control layer reconfiguration completion message. Node list, and select the parent node of the IAB node from the parent node list that the IAB node has obtained from the host centralized unit entity.
  • the first parent node selection module 320 is configured to request the host central unit entity to send a list of parent nodes through an F1 establishment request message or a gNB-DU configuration update message or a new F1AP message, and send the parent node list to the IAB
  • the node selects the parent node of the IAB node from the parent node list that has been obtained in the unit entity of the host centralization.
  • the first parent node selection module 320 is configured to: receive the parent node list actively sent by the host centralized unit entity via a radio resource control layer message, and obtain the parent node list from the host centralized unit entity by the IAB node. Select the parent node of the IAB node in the parent node list.
  • the first parent node selection module 320 is configured to receive a list of parent nodes sent by the donor centralized unit entity actively through a radio resource control layer reconfiguration message or a radio resource control layer release message or a radio resource control layer rejection message , And select the parent node of the IAB node from the list of parent nodes that the IAB node has obtained from the host centralized unit entity.
  • the parent node list sent by the donor CU to the IAB node includes at least one of the following:
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is set to:
  • the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function
  • the parent node of the IAB node is re-determined according to the auxiliary operation of the donor centralized unit entity.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is set to: In this case, when the host central unit entity determines that the DU accessed by the IAB node does not support the IAB function, according to the switching instruction sent by the host central unit entity, the parent node supporting the IAB function corresponding to the switching instruction Re-determined as the parent node of the IAB node.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is set to:
  • the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function
  • it receives the radio resource control layer release message sent by the donor centralized unit entity, disconnects the original DU, and Obtain the parent node list sent by the donor centralization unit entity through a radio resource control layer message, and re-determine the parent node of the IAB node according to the parent node list.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is set to:
  • the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, it receives the radio resource control layer rejection message sent by the donor centralized unit entity, disconnects the original DU, and Obtain the parent node list sent by the donor centralization unit entity through a radio resource control layer message, and re-determine the parent node of the IAB node according to the parent node list.
  • the parent node list sent by the donor CU to the IAB node through the RRC message includes at least one of the following:
  • the parent node list obtained from the unit entity in the host set includes:
  • the method for the host central unit entity to learn whether the DU supports the IAB function includes:
  • the DU it is indicated in the F1 establishment request message or the gNB-DU configuration update message or the new F1AP message that the DU supports the IAB function.
  • the method of generating or updating the parent node list by the host central unit entity includes:
  • the donor centralized unit entity obtains a list of base stations supporting the IAB function from the configuration information of the operation, management and maintenance entity, where the list of base stations supporting the IAB function includes information of base stations supporting the IAB function and information of serving cells supporting the IAB function.
  • the method of generating or updating the parent node list by the host central unit entity includes:
  • the donor centralization unit entity interacts with the neighboring base station through the Xn establishment request message or the NG-RAN node configuration update information, and exchanges the information of the serving cell supporting the IAB function.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is configured to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; when the donor centralization unit entity determines that the DU accessed by the IAB node does not support the IAB function, it re-determines the parent of the IAB node according to the auxiliary operation of the donor centralization unit entity node.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is configured to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; receives the radio resource control layer rejection message sent by the donor centralization unit entity, disconnects the original DU, and re-determines the parent node of the IAB node.
  • the radio resource control layer rejection message includes at least one of the following:
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is configured to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; receives the radio resource control layer release message sent by the donor centralization unit entity after receiving the RRC establishment complete message, disconnects the original DU, and re-determines the IAB node The parent node.
  • the RRC release message includes at least one of the following:
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is set to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; receiving the donor centralization unit entity, after determining the end of the initial access process of the IAB node, sends a radio resource control layer release message, disconnects the original DU, and Re-determine the parent node of the IAB node.
  • the RRC release message includes at least one of the following:
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is set to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; according to the handover instruction sent by the host central unit entity after determining that the initial access process of the IAB node ends, the parent node supporting the IAB function corresponding to the handover instruction is determined again Is the parent node of the IAB node.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is set to: establish a complete message in the radio resource control layer Indicates that the IAB node supports the IAB function; when the donor centralization unit entity determines that the DU accessed by the IAB node does not support the IAB function, it re-determines the parent of the IAB node according to the auxiliary operation of the donor centralization unit entity node.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is set to: establish a complete message in the radio resource control layer Indicates that the IAB node supports the IAB function; receives the radio resource control layer release message sent by the donor centralization unit entity, disconnects the original DU, and re-determines the parent node of the IAB node.
  • the RRC release message includes at least one of the following:
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is set to: establish a complete message in the radio resource control layer Indicates that the IAB node supports the IAB function; receiving the donor centralization unit entity, after determining the end of the initial access process of the IAB node, sends a radio resource control layer release message, disconnects the original DU, and Re-determine the parent node of the IAB node.
  • the RRC release message includes at least one of the following:
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is set to: establish a complete message in the radio resource control layer Indicates that the IAB node supports the IAB function; according to the handover instruction sent by the host central unit entity after determining that the initial access process of the IAB node ends, the parent node supporting the IAB function corresponding to the handover instruction is determined again Is the parent node of the IAB node.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is configured to: pass through the host central unit entity
  • the IAB authorization indication carried in the initial context establishment request message learns that the IAB node supports the IAB function, and determines that the DU accessed by the IAB node does not support the IAB function, re-determine all the units according to the auxiliary operation of the donor central unit entity The parent node of the IAB node.
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is configured to: pass through the host central unit entity
  • the IAB authorization indication carried in the initial context establishment request message learns that the IAB node supports the IAB function, and determines that the DU accessed by the IAB node does not support the IAB function
  • the host central unit entity is received, and the IAB node is determined
  • the sent radio resource control layer release message disconnects the original DU, and re-determines the parent node of the IAB node.
  • the RRC release message includes at least one of the following:
  • the access status of the IAB node is initial access or non-initial access
  • the deployment scenario is the second scenario
  • the first parent node selection module 320 is configured to: pass through the host central unit entity
  • the IAB authorization indication carried in the initial context establishment request message learns that the IAB node supports the IAB function, and determines that the DU accessed by the IAB node does not support the IAB function, it is determined according to the donor central unit entity that the IAB node is initially
  • the switching instruction sent after the end of the access process re-determines the parent node supporting the IAB function corresponding to the switching instruction as the parent node of the IAB node.
  • the above-mentioned apparatus further includes a first parent node list update module, which is configured to update the locally stored parent node list according to configuration update information sent by the operation management and maintenance entity.
  • the first parent node list update module is configured to update the locally saved parent node list according to the parent node information sent by the operation management and maintenance entity whose IAB function has changed.
  • the first parent node list update module is configured to update the locally stored parent node list according to the updated parent node list sent by the operation management and maintenance entity.
  • the parent node list stored by OAM includes at least one of the following:
  • the above-mentioned apparatus further includes a second parent node list update module, configured to update the locally stored parent node list according to the parent node update information sent by the unit entity in the host centralization.
  • the second parent node list update module is configured to: according to the IAB function sent by the host central unit entity through a radio resource control layer message or an F1 establishment response message or a gNB-CU configuration update message or a new F1AP message
  • the changed parent node information updates the locally stored parent node list.
  • the second parent node list update module is configured to: according to the updated information sent by the host central unit entity through a radio resource control layer message or an F1 establishment response message or a gNB-CU configuration update message or a new F1AP message Parent node list, update the locally stored parent node list.
  • the second parent node list update module is configured to update the local parent node list according to the parent node list carried in the RRC release message.
  • the second parent node list update module is configured to update the local parent node list according to the parent node list carried in the RRC rejection message.
  • the parent node list stored in the donor CU includes at least one of the following:
  • FIG. 12 is a schematic structural diagram of a parent node selection device provided by this application. As shown in FIG. 12, an embodiment of the application provides a parent node applied to an AMF entity. The selection device can be integrated in the AMF entity. The device includes:
  • the second parent node selection module 420 is configured to switch based on the NG interface and send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralized unit entity or base station corresponding to the target parent node.
  • the device for selecting a parent node in an AMF entity provided in this embodiment is used to implement the method for selecting a parent node in an AMF entity as described in the embodiment of this application, and the parent node in an AMF entity provided in this embodiment
  • the implementation principle and technical effect of the selection device are similar to the parent node selection method applied to the AMF entity described in the embodiment of the present application, and will not be repeated here.
  • the second parent node selection module 420 is configured to: send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the home set corresponding to the target parent node through an NGAP switching request message Unit entity or base station.
  • the second parent node selection module 420 is configured to: send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the corresponding parent node via a path switch request confirmation message Donor central unit entity or base station.
  • FIG. 13 is a schematic structural diagram of an IAB node provided by this application.
  • the IAB node provided by this application includes: one or more processors 510 and storage
  • the processor 510 of the IAB node may be one or more.
  • One processor 510 is taken as an example in FIG. 13; the storage device 520 is used to store one or more programs; the one or more programs are One or more processors 510 execute, so that the one or more processors 510 implement the parent node selection method applied to the IAB node as described in the embodiment of the present invention.
  • the processor 510 and the storage device 520 in the IAB node may be connected through a bus or in other ways.
  • the connection through a bus is taken as an example.
  • the storage device 520 can be configured to store software programs, computer-executable programs, and modules, such as the program instructions/modules (for example, , Applied to the first parent node selection module 320 in the parent node selection device of the IAB node).
  • the storage device 520 may include a storage program area and a storage data area.
  • the storage program area may store an operating system and an application program required by at least one function; the storage data area may store data created according to the use of the device, and the like.
  • the storage device 520 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the storage device 520 may further include a memory remotely provided with respect to the processor 510, and these remote memories may be connected to the first node through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • FIG. 14 is a schematic structural diagram of an access management function entity provided by this application.
  • the access management function entity provided by this application includes: One or more processors 610 and storage devices 620; the processor 610 of the access management function entity may be one or more, and one processor 610 is taken as an example in FIG. 14; the storage device 620 is used to store one or more Program; The one or more programs are executed by the one or more processors 610, so that the one or more processors 610 implement the parent of the access management functional entity as described in the embodiment of the present invention Node selection method.
  • the processor 610 and the storage device 620 in the access management function entity may be connected through a bus or other methods.
  • the connection through a bus is taken as an example.
  • the storage device 620 can be configured to store software programs, computer-executable programs, and modules, such as the program instructions corresponding to the parent node selection method applied to the access management functional entity as described in the embodiments of this application.
  • Module for example, the first parent node selection module 420 applied to the parent node selection device of the access management functional entity.
  • the storage device 620 may include a storage program area and a storage data area.
  • the storage program area may store an operating system and an application program required by at least one function; the storage data area may store data created according to the use of the device, and the like.
  • the storage device 620 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the storage device 620 may further include memories remotely provided with respect to the processor 610, and these remote memories may be connected to the first node through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • the embodiment of the present application also provides a storage medium, the storage medium stores a computer program, and when the computer program is executed by a processor, it implements the parent node selection method or the parent node selection method applied to the IAB node in any of the embodiments of the present application. Any method for selecting a parent node applied to an access management functional entity described in the embodiments of the present application.
  • the parent node selection method applied to the IAB node includes: determining the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.
  • the parent node selection method applied to the access management functional entity includes: based on the handover of the NG interface, sending the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the host centralized unit entity corresponding to the target parent node Or base station.
  • user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.
  • the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
  • Computer program instructions may be implemented by executing computer program instructions by a data processor of a physical device, for example, in a processor entity, or by hardware, or by a combination of software and hardware.
  • Computer program instructions can be assembly instructions, instruction set architecture (Instruction Set Architecture, ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages Source code or object code.
  • instruction set architecture Instruction Set Architecture, ISA
  • machine instructions machine-related instructions
  • microcode firmware instructions
  • state setting data or written in any combination of one or more programming languages Source code or object code.
  • the block diagram of any logical flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
  • the computer program can be stored on the memory.
  • the memory can be of any type suitable for the local technical environment and can be implemented by any suitable data storage technology, such as but not limited to read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (ASICs) ), programmable logic devices (Field-Programmable Gate Array, FGPA), and processors based on multi-core processor architecture.
  • DSP Digital Signal Processing
  • ASICs application specific integrated circuits
  • FGPA programmable logic devices

Landscapes

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

Abstract

The present application proposes a parent node selection method and apparatus, a device and a medium. The parent node selection method is applied to integrated access and backhaul link (IAB) nodes, and comprises: determining the parent node of an IAB node according to the access situation of the IAB node and the deployment scenario of a network to which the IAB node accesses.

Description

父节点选择方法、装置、设备及介质Parent node selection method, device, equipment and medium
本申请要求在2019年8月15日提交中国专利局、申请号为201910755605.4的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。This application claims the priority of a Chinese patent application filed with the Chinese Patent Office with application number 201910755605.4 on August 15, 2019. The entire content of this application is incorporated into this application by reference.
技术领域Technical field
本申请涉及无线通讯领域，具体涉及一种父节点选择方法、装置、设备及介质。This application relates to the field of wireless communication, and in particular to a method, device, equipment and medium for selecting a parent node.
背景技术Background technique
5G网络的高传输速度主要在于毫米波的使用，但是，毫米波在空气中衰减较大且绕射能力较弱，为此，自接入回传链路(Integrated Access and Backhaul links，IAB)技术被提出。自接入回传链路包括无线接入链路和无线回传链路，无线接入链路为UE(User Equipment，用户设备)与IAB节点之间通信链路，无线回传链路为IAB节点之间的通信链路，用于进行数据回传，故IAB节点无需有线传输网络进行数据回传。当IAB节点接入网络时，IAB节点有可能连接到不支持IAB功能的DU(Distributed Unit，分布单元实体)或者基站，此时IAB节点无法实现其IAB功能。The high transmission speed of 5G networks is mainly due to the use of millimeter waves. However, millimeter waves have large attenuation in the air and weak diffraction capabilities. For this reason, the integrated access and backhaul links (IAB) technology Been proposed. The self-access backhaul link includes the wireless access link and the wireless backhaul link. The wireless access link is the communication link between the UE (User Equipment) and the IAB node, and the wireless backhaul link is the IAB The communication link between nodes is used for data return, so the IAB node does not need a wired transmission network for data return. When an IAB node accesses the network, the IAB node may be connected to a DU (Distributed Unit, distributed unit entity) or base station that does not support the IAB function. At this time, the IAB node cannot implement its IAB function.
发明内容Summary of the invention
本申请提供一种父节点选择方法、装置、设备及介质，以保证IAB节点能够实现其IAB功能。This application provides a method, device, equipment, and medium for selecting a parent node to ensure that an IAB node can realize its IAB function.
第一方面，本申请实施例提供一种父节点选择方法，应用于IAB节点中，包括：In the first aspect, an embodiment of the present application provides a method for selecting a parent node, which is applied to an IAB node, including:
根据IAB节点的接入情况以及IAB节点接入网络的部署场景，确定所述IAB节点的父节点。Determine the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.
第二方面，本申请实施例提供一种父节点选择方法，应用于接入管理功能实体中，包括：In the second aspect, an embodiment of the present application provides a method for selecting a parent node, which is applied to an access management function entity, including:
在IAB节点根据所述IAB节点的接入情况以及IAB节点接入网络的部署场景，确定出所述IAB节点的目标父节点之后，将所述IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示发送给与目标父节点对应的宿主集中单元实体或基站。After the IAB node determines the target parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node’s access to the network, the IAB authorization indication information of the IAB node or the IAB node’s The IAB node instruction is sent to the donor centralized unit entity or base station corresponding to the target parent node.
第三方面，本申请实施例提供一种父节点选择装置，应用于IAB节点中，其特征在于，包括：In a third aspect, an embodiment of the present application provides a parent node selection device, which is applied to an IAB node, and is characterized in that it includes:
第一父节点选择模块，用于根据IAB节点的接入情况以及IAB节点接入网络的部署场景，确定所述IAB节点的父节点。The first parent node selection module is used to determine the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.
第四方面，本申请实施例提供一种父节点选择装置，应用于接入管理功能实体中，包括：In a fourth aspect, an embodiment of the present application provides a parent node selection device, which is applied to an access management function entity, and includes:
第二父节点选择模块，用于在根据IAB节点的接入情况以及IAB节点接入网络的部署场景，确定出所述IAB节点的目标父节点之后，将所述IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示发送给与目标父节点对应的宿主集中单元实体或基站。The second parent node selection module is configured to determine the target parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node’s access to the network, and then send the IAB authorization indication information of the IAB node or The IAB node indication of the IAB node is sent to the donor centralized unit entity or the base station corresponding to the target parent node.
第五方面，本申请实施例提供一种IAB节点，包括：一个或多个处理器；存储装置，用于存储一个或多个程序；当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如本申请任意实施例所述的应用于IAB节点中的父节点选择方法。In a fifth aspect, an embodiment of the present application provides an IAB node, including: one or more processors; a storage device, configured to store one or more programs; when the one or more programs are used by the one or more The processor executes, so that the one or more processors implement the parent node selection method applied to the IAB node as described in any embodiment of the present application.
第六方面，本申请实施例提供了一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现如本申请任意实施例所述的应用于IAB节点中的父节点选择方法。In a sixth aspect, an embodiment of the present application provides a storage medium, the storage medium stores a computer program, and when the computer program is executed by a processor, it is applied to the parent of the IAB node as described in any embodiment of the present application. Node selection method.
第七方面，本申请实施例提供一种接入管理功能实体，包括：一个或多个处理器；存储装置，用于存储一个或多个程序；当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如本申请任意实施例 所述的应用于接入管理功能实体中的父节点选择方法。In a seventh aspect, an embodiment of the present application provides an access management function entity, including: one or more processors; a storage device, configured to store one or more programs; when the one or more programs are used by the one Or multiple processors execute, so that the one or more processors implement the parent node selection method applied to the access management functional entity as described in any embodiment of the present application.
第八方面，本申请实施例提供了一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现如本申请任意实施例所述的应用于接入管理功能实体中的父节点选择方法。In an eighth aspect, an embodiment of the present application provides a storage medium that stores a computer program that, when executed by a processor, implements the application to an access management function entity as described in any embodiment of the present application The parent node selection method in.
关于本申请的以上实施例和其他方面以及其实现方式，在附图说明、具体实施方式和权利要求中提供更多说明。Regarding the above embodiments and other aspects of the present application and their implementation manners, more descriptions are provided in the description of the drawings, specific implementation manners, and claims.
附图说明Description of the drawings
图1为网络IAB部署示意图；Figure 1 is a schematic diagram of network IAB deployment;
图2为CU和DU分离的网络IAB部署示意图；Figure 2 is a schematic diagram of network IAB deployment with separated CU and DU;
图3为本申请提供的一种父节点选择方法的流程示意图；FIG. 3 is a schematic flowchart of a method for selecting a parent node provided by this application;
图4为本申请提供的第一种IAB节点部署场景示意图；Figure 4 is a schematic diagram of the first IAB node deployment scenario provided by this application;
图5为本申请提供的第二种IAB节点部署场景示意图；Figure 5 is a schematic diagram of the second IAB node deployment scenario provided by this application;
图6为本申请提供的第三种IAB节点部署场景示意图；Figure 6 is a schematic diagram of the third deployment scenario of IAB nodes provided by this application;
图7为本申请提供的第四种IAB节点部署场景示意图；Figure 7 is a schematic diagram of the fourth IAB node deployment scenario provided by this application;
图8为本申请提供的第五种IAB节点部署场景示意图；Figure 8 is a schematic diagram of a fifth IAB node deployment scenario provided by this application;
图9为本申请提供的第六种IAB节点部署场景示意图；FIG. 9 is a schematic diagram of the sixth IAB node deployment scenario provided by this application;
图10为本申请提供的一种父节点选择方法的流程示意图；FIG. 10 is a schematic flowchart of a method for selecting a parent node provided by this application;
图11为本申请提供的一种父节点选择装置的结构示意图；FIG. 11 is a schematic structural diagram of a parent node selection device provided by this application;
图12为本申请提供的一种父节点选择装置的结构示意图；FIG. 12 is a schematic structural diagram of a parent node selection device provided by this application;
图13为本申请提供的一种IAB节点的结构示意图；FIG. 13 is a schematic structural diagram of an IAB node provided by this application;
图14为本申请提供的一种接入管理功能实体的结构示意图。FIG. 14 is a schematic structural diagram of an access management function entity provided by this application.
具体实施方式detailed description
为使本申请的目的、技术方案和优点更加清楚明白，下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中 的实施例及实施例中的特征可以相互任意组合。In order to make the purpose, technical solutions, and advantages of the present application clearer, the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings. It should be noted that the embodiments in this application and the features in the embodiments can be combined arbitrarily with each other if there is no conflict.
在描述本申请提供的实施方式之前，首先对IAB进行示例性地解释说明。Before describing the implementation manners provided by the present application, IAB is first exemplarily explained.
部署了IAB的网络的一个示例如图1所示，图中包括节点10、节点20和节点30，其中，节点10与核心网之间进行有线连接，例如是节点10与核心网通过光纤11连接，节点20和节点30通过节点10向核心网收发数据。用户设备(User Equipment，UE)可通过接入链路(access link)接入节点10、节点20和节点30，节点之间可通过无线的回传链路(backhaul link，BH link)传输数据。在IAB网络中，支持无线接入并且将数据进行无线回传的接入节点称为IAB节点(IAB node)，例如图1中的节点20和节点30。在IAB网络中，为IAB node提供无线回传功能，以使UE连接于核心网的接入节点称为IAB宿主(IAB donor)，例如图1中的节点10。以数据上行传输为例，节点20可通过无线的backhaul link将从UE接收的数据发送给节点10，接入节点10再将UE数据发送给核心网网元。以数据下行传输为例，核心网网元将UE数据包发送给节点10，接入节点10再通过无线的backhaul link将UE数据发送给节点20，然后接入节点20通过access link将UE数据发送给UE。An example of a network deployed with IAB is shown in Figure 1. The figure includes node 10, node 20, and node 30. Node 10 is connected to the core network through a wired connection, for example, node 10 is connected to the core network through optical fiber 11. , The node 20 and the node 30 send and receive data to the core network through the node 10. User Equipment (UE) can access node 10, node 20, and node 30 through an access link, and data can be transmitted between nodes through a wireless backhaul link (BH link). In an IAB network, an access node that supports wireless access and wireless backhaul of data is called an IAB node (IAB node), such as the node 20 and the node 30 in FIG. 1. In the IAB network, the wireless backhaul function is provided for the IAB node, so that the access node that connects the UE to the core network is called an IAB donor (IAB donor), such as the node 10 in FIG. 1. Taking data uplink transmission as an example, the node 20 may send data received from the UE to the node 10 through a wireless backhaul link, and the access node 10 then sends the UE data to the core network element. Taking data downlink transmission as an example, the core network element sends the UE data packet to the node 10, the access node 10 then sends the UE data to the node 20 through the wireless backhaul link, and then the access node 20 sends the UE data through the access link To the UE.
另外，支持CU(Centralized Unit，集中网元)和DU(Distributed Unit，分布网元)分离部署是NR(New Radio，新空口)中一个重要的技术特征，因此，在CU和DU分离部署场景中也需要支持IAB功能。图2是CU和DU分离的网络IAB部署示意图。如图2所示，其中IAB节点可以具有DU类似功能和MT(Mobile Terminal，移动终端)类似功能，MT类似功能也即UE类似功能，IAB节点通过双连接接入两个父IAB节点，即IAB节点通过双连接分别接入父IAB节点1和父IAB节点2。In addition, supporting the separate deployment of CU (Centralized Unit) and DU (Distributed Unit) is an important technical feature in NR (New Radio). Therefore, in the separate deployment scenario of CU and DU Also need to support IAB function. Figure 2 is a schematic diagram of the network IAB deployment in which CU and DU are separated. As shown in Figure 2, IAB nodes can have DU-like functions and MT (Mobile Terminal, mobile terminal)-like functions. MT-like functions are also UE-like functions. IAB nodes access two parent IAB nodes through dual connections, that is, IAB The nodes connect to the parent IAB node 1 and the parent IAB node 2 respectively through dual connections.
当IAB节点接入网络时，IAB节点附近可能存在不支持IAB功能的DU或者基站。如果IAB节点连接到不支持IAB功能的DU或者基站，它将无法服务其他的子IAB节点或者UE。When the IAB node accesses the network, there may be DUs or base stations that do not support the IAB function near the IAB node. If the IAB node is connected to a DU or base station that does not support the IAB function, it will not be able to serve other child IAB nodes or UEs.
在一个示例性实施方式中，图3为本申请提供的一种父节点选择方法的流程示意图。该方法可以适用于IAB在接入网络时选择一个支持IAB功能的父节点的情况。该方法可以由本申请提供的应用于IAB节点的父节点选择装置执行，该父节点选择装置可以由软件和/或硬件实现，并集成在IAB节点。In an exemplary embodiment, FIG. 3 is a schematic flowchart of a method for selecting a parent node provided by this application. This method can be applied to the situation where the IAB selects a parent node that supports the IAB function when accessing the network. This method can be executed by the parent node selection device applied to the IAB node provided by the present application, and the parent node selection device can be implemented by software and/or hardware and integrated in the IAB node.
如图3所示，本申请提供的应用于IAB节点的一种父节点选择方法，包括：As shown in Fig. 3, a parent node selection method applied to IAB nodes provided by this application includes:
S120、根据IAB节点的接入情况以及IAB节点接入网络的部署场景，确定所述IAB节点的父节点。S120: Determine the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.
一个IAB节点的IAB节点称为这个IAB节点的子IAB节点，一个IAB节点以连接身份所接入的支持IAB功能的DU或基站称为这个IAB节点的父IAB节点。The IAB node of an IAB node is called the child IAB node of the IAB node, and the DU or base station supporting the IAB function accessed by an IAB node as a connection is called the parent IAB node of the IAB node.
IAB节点的网络接入情况可以分为初始接入和非初始接入，IAB节点接入网络的部署场景有可以划分为多种，具体可以根据部署位置设定区域内的DU实体和基站是否支持IAB功能来划分，还可以根据不支持IAB功能的基站所连接的AMF(Access and Mobility Management Function，接入管理功能)实体是否支持IAB功能来划分，还可以根据不支持IAB功能的DU实体所连接的CU实体是否支持IAB功能，以及进一步连接的AMF实体是否支持IAB功能来划分。The network access of IAB nodes can be divided into initial access and non-initial access. The deployment scenarios of IAB node access to the network can be divided into multiple types. Specifically, the DU entity and base station in the area can be set according to the deployment location. The IAB function can be divided according to whether the AMF (Access and Mobility Management Function) entity connected to the base station that does not support the IAB function supports the IAB function, and it can also be divided according to the DU entity that does not support the IAB function. Whether the CU entity supports the IAB function, and whether the further connected AMF entity supports the IAB function.
因此，在IAB节点选择支持IAB功能的父节点时可以结合IAB节点的接入情况以及接入网络的部署场景来确定。不同接入情况下，不同部署场景下，IAB节点选择父节点的方式可能有相同的，也可能有不同的。Therefore, when the IAB node selects the parent node that supports the IAB function, it can be determined by combining the access situation of the IAB node and the deployment scenario of the access network. In different access situations and different deployment scenarios, the way the IAB node selects the parent node may be the same or different.
其中，所述IAB节点可以是DU实体，也可以是MT。Wherein, the IAB node may be a DU entity or an MT.
本申请提供的一种父节点选择方法，在IAB节点接入网络时，根据IAB节点的接入情况以及IAB节点接入网络的部署场景，来确定IAB节点父节点，有效地解决了IAB节点如何选择父节点的问题，确保了IAB节点选择的父节点支 持IAB功能，进而使IAB节点的IAB功能得以保证，达到了为其他的子IAB节点以及UE服务的效果。This application provides a method for selecting a parent node. When an IAB node accesses the network, the parent node of the IAB node is determined according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network, which effectively solves how the IAB node The problem of selecting the parent node ensures that the parent node selected by the IAB node supports the IAB function, thereby ensuring the IAB function of the IAB node, and achieving the effect of serving other child IAB nodes and UEs.
在上述实施例的基础上，提出了上述实施例的变型实施例，在此需要说明的是，为了使描述简要，在变型实施例中仅描述与上述实施例的不同之处。On the basis of the above-mentioned embodiment, a modified embodiment of the above-mentioned embodiment is proposed. It should be noted that, in order to make the description concise, only the differences from the above-mentioned embodiment are described in the modified embodiment.
在一示例中，IAB节点接入网络的部署场景可以包括如下六种部署场景。In an example, the deployment scenarios for the IAB node to access the network may include the following six deployment scenarios.
第一场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，IAB节点和支持IAB功能的基站。The first scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station supporting the IAB function.
如图4所示，宿主集中单元实体(donor CU)101通过F1接口与donor DU102连接，donor DU 102通过回传链路(BH link)与IAB节点103连接，其中，donor CU 101、donor DU102和IAB节点103均支持IAB功能。IAB节点104，指的是即将部署于与第一场景对应的IAB网络中的节点，例如是正在进行初始接入的IAB移动终端(IAB-MT)，其部署的位置附近所有DU和基站都支持IAB功能。As shown in Figure 4, the donor central unit entity (donor CU) 101 is connected to the donor DU102 through the F1 interface, and the donor DU 102 is connected to the IAB node 103 through the backhaul link (BH link). Among them, the donor CU 101, the donor DU102 and IAB nodes 103 all support IAB functions. The IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the first scenario, such as an IAB mobile terminal (IAB-MT) that is undergoing initial access, and all DUs and base stations near the deployed location support IAB function.
第二场景为：所述IAB节点部署位置设定区域内包括IAB donor DU和不支持IAB功能的分布单元实体，所述不支持IAB功能的分布单元实体连接宿主集中单元实体donor CU。The second scenario is: the IAB node deployment location setting area includes the IAB donor DU and the distributed unit entity that does not support the IAB function, and the distributed unit entity that does not support the IAB function is connected to the donor centralized unit entity donor CU.
如图5所示，donor CU 101通过F1接口与donor DU 102连接，以及与常规分布单元实体(normal DU)105连接，donor DU 102通过BH link与IAB节点103连接，其中，宿donor CU 101、donor DU 102和IAB节点103均支持IAB功能，常规分布单元实体105不支持IAB功能。IAB节点104，指的是即将部署于与第二场景对应的IAB网络中的节点，例如是正在进行初始接入的IAB-MT，其部署的位置附近有其他的IAB节点103，支持IAB功能的donor DU 102，以及不支持IAB功能的normal DU 105。As shown in Figure 5, the donor CU 101 is connected to the donor DU 102 through the F1 interface, and is connected to the normal distribution unit entity (normal DU) 105, and the donor DU 102 is connected to the IAB node 103 through the BH link. Among them, the donor CU 101, Both the donor DU 102 and the IAB node 103 support the IAB function, and the conventional distributed unit entity 105 does not support the IAB function. The IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the second scenario, for example, an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support IAB functions Donor DU 102, and normal DU 105 that does not support IAB.
第三场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，IAB节点和不支持IAB功能的基站，与所述基站连接的接入管理功能实体支持IAB 功能。The third scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station that does not support the IAB function, and the access management function entity connected to the base station supports the IAB function.
如图6所示，AMF 107通过NG接口与donor CU 101连接，以及与基站(gNB)106连接，与donor CU 101连接的AMF 107和与gNB 106连接的AMF 107可以是同一个AMF，也可以是不同的AMF，图6中以不同为例示出。donor CU 101通过F1接口与donor DU 102连接，donor DU 102通过BH link与IAB节点103连接，其中，AMF 107、donor CU 101、donor DU 102和IAB节点103均支持IAB功能，而gNB 106不支持IAB功能。IAB节点104，指的是即将部署于与第三场景对应的IAB网络中的节点，例如是正在进行初始接入的IAB-MT，其部署的位置附近有其他的IAB节点103，支持IAB功能的donor DU 102，以及不支持IAB功能的gNB 106，但是gNB 106连接的AMF 107是支持IAB功能的，AMF 107所连接的其他核心网网元中有支持IAB功能的网元。As shown in Figure 6, AMF 107 is connected to donor CU 101 through the NG interface and connected to base station (gNB) 106. The AMF 107 connected to donor CU 101 and the AMF 107 connected to gNB 106 can be the same AMF or They are different AMFs, shown in Figure 6 as an example. The donor CU 101 is connected to the donor DU 102 through the F1 interface, and the donor DU 102 is connected to the IAB node 103 through the BH link. Among them, AMF 107, donor CU 101, donor DU 102 and IAB node 103 all support the IAB function, but gNB 106 does not. IAB function. The IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the third scenario, such as an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support the IAB function Donor DU 102, and gNB 106 that does not support the IAB function, but the AMF 107 connected to the gNB 106 supports the IAB function, and other core network network elements connected to the AMF 107 have network elements that support the IAB function.
第四场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，IAB节点和不支持IAB功能的基站，与所述基站连接的接入管理功能实体不支持IAB功能。The fourth scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station that does not support the IAB function, and the access management function entity connected to the base station does not support the IAB function.
如图7所示，AMF 107通过NG接口与donor CU 101连接，AMF 108通过NG接口与gNB 106连接。donor CU 101通过F1接口与donor DU 102连接，donor DU 102通过BH link与IAB节点103连接，其中，AMF 107、donor CU 101、donor DU 102和IAB节点103均支持IAB功能，而AMF 108和gNB 106均不支持IAB功能。IAB节点104，指的是即将部署于与第四场景对应的IAB网络中的节点，例如是正在进行初始接入的IAB-MT，其部署的位置附近有其他的IAB节点103，支持IAB功能的donor DU 102，以及不支持IAB功能的gNB 106，而且不支持IAB功能的gNB 106连接的AMF 108也是不支持IAB功能的。As shown in Figure 7, AMF 107 is connected to donor CU 101 through the NG interface, and AMF 108 is connected to gNB 106 through the NG interface. The donor CU 101 is connected to the donor DU 102 through the F1 interface, and the donor DU 102 is connected to the IAB node 103 through the BH link. Among them, AMF 107, donor CU 101, donor DU 102 and IAB node 103 all support the IAB function, while AMF 108 and gNB 106 does not support the IAB function. The IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the fourth scenario, for example, an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support IAB functions The donor DU 102 and the gNB 106 that does not support the IAB function, and the AMF 108 connected to the gNB 106 that does not support the IAB function also does not support the IAB function.
第五场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，IAB节点和不支持IAB功能的分布单元实体，与所述不支持IAB功能的分布单元实体连接的集中单元实体不支持IAB功能，与所述集中单元实体连接的接入管理 功能实体支持IAB功能。The fifth scenario is: the IAB node deployment location setting area includes IAB donor DU, the IAB node and the distributed unit entity that does not support the IAB function, and the centralized unit entity connected to the distributed unit entity that does not support the IAB function does not support IAB function, the access management function entity connected with the centralized unit entity supports the IAB function.
如图8所示，AMF 107通过NG接口与donor CU 101连接，以及与normal CU109连接，与donor CU 101连接的AMF 107和与normal CU 109连接的AMF 107可以是同一个AMF，也可以是不同的AMF，图8中以不同为例示出。donor CU101通过F1接口与donor DU 102连接，donor DU 102通过BH link与IAB节点103连接，normal CU 109通过F1接口与normal DU105连接，其中，AMF 107、donor CU 101、donor DU 102和IAB节点103均支持IAB功能，而normal CU 109和normal DU105不支持IAB功能。IAB节点104，指的是即将部署于与第五场景对应的IAB网络中的节点，例如是正在进行初始接入的IAB-MT，其部署的位置附近有其他的IAB节点103，支持IAB功能的donor DU 102，以及不支持IAB功能的normal DU105，而且normal DU105连接的normal CU 109也不支持IAB功能，但是normal CU 109所连接的AMF 107是支持IAB功能的，AMF 107所连接的其他核心网网元中有支持IAB功能的网元。As shown in Figure 8, AMF 107 is connected to donor CU 101 through the NG interface and connected to normal CU109. AMF 107 connected to donor CU 101 and AMF 107 connected to normal CU 109 can be the same AMF or different The AMF is shown in Figure 8 with different examples. The donor CU101 is connected to the donor DU 102 through the F1 interface, the donor DU 102 is connected to the IAB node 103 through the BH link, and the normal CU 109 is connected to the normal DU105 through the F1 interface. Among them, AMF 107, donor CU 101, donor DU 102 and IAB node 103 Both support IAB function, but normal CU109 and normal DU105 do not support IAB function. The IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the fifth scenario, for example, an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support IAB functions Donor DU 102, and normal DU105 that does not support IAB function, and normal CU 109 connected to normal DU105 does not support IAB function, but AMF 107 connected to normal CU 109 supports IAB function, and other core networks connected to AMF 107 Among the network elements, there are network elements that support the IAB function.
第六场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，IAB节点和不支持IAB功能的分布单元实体，与所述不支持IAB功能的分布单元实体连接的集中单元实体不支持IAB功能，与所述集中单元实体连接的接入管理功能实体不支持IAB功能。The sixth scenario is: the IAB node deployment location setting area includes IAB donor DU, the IAB node and the distributed unit entity that does not support the IAB function, and the centralized unit entity connected to the distributed unit entity that does not support the IAB function does not support IAB function, the access management function entity connected to the centralized unit entity does not support the IAB function.
如图9所示，AMF 107通过NG接口与donor CU 101连接，AMF 108通过NG接口与normal CU 109连接。donor CU 101通过F1接口与donor DU 102连接，donor DU 102通过BH link与IAB节点103连接，normal CU 109通过F1接口与normal DU105连接，其中，AMF 107、donor CU 101、donor DU 102和IAB节点103均支持IAB功能，而AMF 108、normal CU 109和normal DU105均不支持IAB功能。IAB节点104，指的是即将部署于与第六场景对应的IAB网络中的节点，例如是正在进行初始接入的IAB-MT，其部署的位置附近有其他的IAB节点103，支持IAB功能的donor DU 102，以及不支持IAB功能的normal DU105，而且不支持IAB功能的normal DU105连接的normal CU 109也不支持 IAB功能，同时，normal CU 109所连接的AMF 108也不支持IAB功能。As shown in Figure 9, AMF 107 is connected to donor CU 101 through an NG interface, and AMF 108 is connected to normal CU 109 through an NG interface. Donor CU 101 is connected to donor DU 102 through F1 interface, donor DU 102 is connected to IAB node 103 through BH link, and normal CU 109 is connected to normal DU 105 through F1 interface. Among them, AMF 107, donor CU 101, donor DU 102 and IAB node 103 all support IAB function, while AMF 108, normal CU 109 and normal DU105 do not support IAB function. The IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the sixth scenario, for example, an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support IAB functions The donor DU 102 and the normal DU105 that does not support the IAB function, and the normal CU 109 connected to the normal DU105 that does not support the IAB function, do not support the IAB function, and at the same time, the AMF 108 connected to the normal CU 109 does not support the IAB function.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第一场景至第六场景之一，所述确定所述IAB节点的父节点，包括：In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first to sixth scenarios, and the determining the parent node of the IAB node includes :
在所述IAB节点预配置的父节点列表中选择所述IAB节点的父节点。The parent node of the IAB node is selected from the parent node list pre-configured by the IAB node.
当IAB节点为初始接入时，在部署场景为第一场景、第二场景、第三场景、第四场景、第五场景以及第六场景中任一场景的情况下，IAB节点可以具有预配置的父节点列表，进而可以在其预配置的父节点列表中选择一个作为其父节点。When the IAB node is initially accessed, when the deployment scenario is any of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node may have a pre-configuration A list of parent nodes, and then you can select one of its pre-configured parent node lists as its parent node.
当IAB节点为非初始接入时，在部署场景为第一场景、第二场景、第三场景、第四场景、第五场景以及第六场景中任一场景的情况下，IAB节点也可以具有预配置的父节点列表，进而也可以在其预配置的父节点列表中选择一个作为其父节点。When the IAB node is non-initial access, when the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node may also have A pre-configured parent node list, and in turn, you can select one of the pre-configured parent node lists as its parent node.
其中，预配置的父节点列表是操作管理维护(Operation Administration and Maintenance，OAM)实体配置的，在IAB节点建立之前添加至IAB节点的配置信息中。预配置的父节点列表中包括的节点均支持IAB功能。Among them, the pre-configured parent node list is configured by an Operation Administration and Maintenance (OAM) entity, and is added to the configuration information of the IAB node before the IAB node is established. The nodes included in the pre-configured parent node list all support the IAB function.
在一示例中，IAB节点预配置的父节点列表中至少包括下述之一：In an example, the pre-configured parent node list of the IAB node includes at least one of the following:
当前注册公共陆地移动网络(Public Land Mobile Network，PLMN)下的支持IAB功能的小区标识；Currently registered public land mobile network (Public Land Mobile Network, PLMN) cell identity supporting IAB function;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，上述方法还包括：所述IAB节点接入小区的情况下，根据无线资源控制层(Radio Resource Control，RRC)重配消息中是否包含回程自适应协议层配置消息判断所述IAB节点接入的分布单元实体或者基站是否支持IAB 功能。In an example, the above method further includes: when the IAB node accesses the cell, judging the IAB according to whether the radio resource control (Radio Resource Control, RRC) reconfiguration message includes a backhaul adaptive protocol layer configuration message Whether the distributed unit entity or base station accessed by the node supports IAB function.
无论IAB节点为初始接入还是非初始接入，在所述IAB节点接入任意一个合适的小区之后，可以根据RRC重配消息中是否包括回程自适应协议层配置消息，来判断其接入的分布单元实体或者基站是否支持IAB功能。当RRC重配消息中包括回程自适应协议层配置消息时，所述IAB节点接入的分布单元实体或者基站支持IAB功能；当RRC重配消息中不包括回程自适应协议层配置消息时，所述IAB节点接入的分布单元实体或者基站不支持IAB功能。Regardless of whether the IAB node is initially accessed or non-initially accessed, after the IAB node accesses any suitable cell, it can determine whether it is accessed according to whether the RRC reconfiguration message includes a backhaul adaptive protocol layer configuration message. Whether the distributed unit entity or the base station supports the IAB function. When the RRC reconfiguration message includes the backhaul adaptive protocol layer configuration message, the distributed unit entity or base station accessed by the IAB node supports the IAB function; when the RRC reconfiguration message does not include the backhaul adaptive protocol layer configuration message, The distributed unit entity or base station accessed by the IAB node does not support the IAB function.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第一场景至第六场景之一，所述确定所述IAB节点的父节点，包括：In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first to sixth scenarios, and the determining the parent node of the IAB node includes :
基于小区广播的***信息选择所述IAB节点的父节点。The parent node of the IAB node is selected based on the system information broadcast by the cell.
当IAB节点为初始接入时，在部署场景为第一场景、第二场景、第三场景、第四场景、第五场景以及第六场景中任一场景的情况下，IAB节点接入网络时可以根据接收到的小区广播的***信息选择一个节点作为其父节点。When the IAB node is initially accessed, when the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, when the IAB node accesses the network A node can be selected as its parent node based on the received system information broadcast by the cell.
当IAB节点为非初始接入时，在部署场景为第一场景、第二场景、第三场景、第四场景、第五场景以及第六场景中任一场景的情况下，IAB节点接入网络时也可以根据接收到的小区广播的***信息选择一个节点作为其父节点。When the IAB node is non-initial access, and the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node accesses the network It is also possible to select a node as its parent node according to the received system information broadcast by the cell.
在一示例中，基于小区广播的***信息选择所述IAB节点的父节点，包括：In an example, selecting the parent node of the IAB node based on the system information broadcast by the cell includes:
根据小区广播的***信息中是否包括IAB专有物理随机接入信道(Physical Random Access Channel，PRACH)配置，判断所述IAB节点接入的小区是否支持IAB功能。According to whether the system information broadcast by the cell includes the IAB dedicated physical random access channel (Physical Random Access Channel, PRACH) configuration, it is determined whether the cell accessed by the IAB node supports the IAB function.
当IAB节点接收的小区广播的***信息中包括IAB专有PRACH配置时，则可以确定所述IAB节点接入的小区支持IAB功能；当IAB节点接收的小区广播的***信息中不包括IAB专有PRACH配置时，则可以确定所述IAB节点接入的小区不支持IAB功能。由此，根据此种实施方式也可以确保选择的父节点支持IAB功能。When the system information broadcast by the IAB node includes the IAB-specific PRACH configuration, it can be determined that the cell that the IAB node accesses supports the IAB function; when the system information broadcast by the IAB node does not include the IAB-specific During PRACH configuration, it can be determined that the cell accessed by the IAB node does not support the IAB function. Therefore, according to this embodiment, it can also be ensured that the selected parent node supports the IAB function.
在一示例中，基于小区广播的***信息选择所述IAB节点的父节点，包括：In an example, selecting the parent node of the IAB node based on the system information broadcast by the cell includes:
根据小区广播的***信息中是否包括IAB专用***信息，判断所述IAB节点接入的小区是否支持IAB功能，其中，所述IAB专用***信息包括小区接入禁止信息、接纳控制参数、小区选择参数、小区重选参数中的至少一种。Determine whether the cell accessed by the IAB node supports the IAB function according to whether the system information broadcast by the cell includes IAB dedicated system information, where the IAB dedicated system information includes cell access barring information, admission control parameters, and cell selection parameters , At least one of the cell reselection parameters.
当IAB节点接收的小区广播的***信息中包括IAB专用***信息时，则可以确定所述IAB节点接入的小区支持IAB功能；当IAB节点接收的小区广播的***信息中不包括IAB专用***信息时，则可以确定所述IAB节点接入的小区不支持IAB功能。由此，根据此种实施方式也可以确保选择的父节点支持IAB功能。When the system information broadcast by the cell received by the IAB node includes the IAB dedicated system information, it can be determined that the cell accessed by the IAB node supports the IAB function; when the system information broadcast by the IAB node does not include the IAB dedicated system information At this time, it can be determined that the cell accessed by the IAB node does not support the IAB function. Therefore, according to this embodiment, it can also be ensured that the selected parent node supports the IAB function.
在一示例中，基于小区广播的***信息选择所述IAB节点的父节点，包括：In an example, selecting the parent node of the IAB node based on the system information broadcast by the cell includes:
基于IAB节点或者IAB宿主分布单元实体广播的用于小区重选的***信息选择所述IAB节点的父节点。The parent node of the IAB node is selected based on the system information used for cell reselection broadcast by the IAB node or the IAB host distribution unit entity.
IAB节点可以接收其他IAB节点或者IAB donor CU广播的用于小区重选的***信息，其中，所述IAB节点或者IAB donor CU广播的用于小区重选的***信息包括下述至少之一：The IAB node may receive the system information used for cell reselection broadcast by other IAB nodes or IAB donor CU, where the system information used for cell reselection broadcast by the IAB node or IAB donor CU includes at least one of the following:
支持IAB功能的频率信息；Frequency information supporting IAB function;
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为初始接入，所述部署场景为第一场景至第六场景之一，所述确定所述IAB节点的父节点，包括：In an example, the access situation of the IAB node is initial access, and the deployment scenario is one of the first to sixth scenarios, and the determining the parent node of the IAB node includes:
所述IAB节点接入小区的情况下，获取操作管理维护实体配置信息中的父节点列表；从所述父节点列表中选择所述IAB节点的父节点。When the IAB node accesses the cell, obtain a parent node list in the configuration information of the operation management and maintenance entity; select the parent node of the IAB node from the parent node list.
当IAB节点为初始接入时，在部署场景为第一场景、第二场景、第三场景、第四场景、第五场景以及第六场景中任一场景的情况下，IAB节点接入任意一个合适的小区之后，与OAM建立连接，获取OAM配置信息，OAM配置信息中包括父节点列表，IAB节点可以在这个父节点列表中选择一个节点作为其父节点。When the IAB node is initially accessed, when the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node accesses any one After a suitable cell, it establishes a connection with OAM and obtains OAM configuration information. The OAM configuration information includes a parent node list, and the IAB node can select a node from the parent node list as its parent node.
其中，在OAM配置信息中获取的父节点列表中的父节点均支持IAB功能。Among them, the parent nodes in the parent node list acquired in the OAM configuration information all support the IAB function.
在一示例中，在OAM配置信息中获取的父节点列表中至少包括下述之一：In an example, the parent node list obtained in the OAM configuration information includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为非初始接入，所述部署场景为第一场景至第六场景之一，所述确定所述IAB节点的父节点，包括：In an example, the access situation of the IAB node is non-initial access, the deployment scenario is one of the first to sixth scenarios, and the determining the parent node of the IAB node includes:
在所述IAB节点从操作管理维护实体配置信息中已获取的父节点列表中选择所述IAB节点的父节点。The IAB node selects the parent node of the IAB node from the parent node list obtained from the configuration information of the operation management and maintenance entity.
当IAB节点为非初始接入时，在部署场景为第一场景、第二场景、第三场景、第四场景、第五场景以及第六场景中任一场景的情况下，IAB节点已经从OAM中获取过父节点列表，存储于IAB节点本地，进而可以在这个从OAM中已获取的父节点列表中选择一个节点作为其父节点。When the IAB node is a non-initial access, and the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node has already switched from OAM The parent node list obtained in the OAM is stored locally in the IAB node, and then a node can be selected as its parent node from the parent node list obtained from the OAM.
其中，从OAM中已获取的父节点列表中的节点均支持IAB功能。Among them, the nodes in the parent node list obtained from OAM all support the IAB function.
在一示例中，从OAM中已获取的父节点列表中至少包括下述之一：In an example, the parent node list obtained from OAM includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为非初始接入，所述部署场景为第一场景至第六场景之一，所述确定所述IAB节点的父节点，包括：In an example, the access situation of the IAB node is non-initial access, the deployment scenario is one of the first to sixth scenarios, and the determining the parent node of the IAB node includes:
在所述IAB节点从宿主集中单元实体中已获取的父节点列表中选择所述IAB节点的父节点。The IAB node selects the parent node of the IAB node from a list of parent nodes that the IAB node has obtained from the host centralized unit entity.
当IAB节点为非初始接入时，在部署场景为第一场景、第二场景、第三场景、第四场景、第五场景以及第六场景中任一场景的情况下，IAB节点已经从donor CU中获取过父节点列表，存储于IAB节点本地，进而可以在这个从donor CU中已获取的父节点列表中选择一个节点作为其父节点。When the IAB node is non-initial access, when the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node has been transferred from the donor The parent node list obtained in the CU is stored locally on the IAB node, and then a node can be selected as its parent node from the parent node list obtained from the donor CU.
其中，从donor CU中已获取的父节点列表中的节点均支持IAB功能。donor CU存储的父节点列表中具体可以包含支持IAB功能的IAB donor DU、IAB节点、gNB中的至少一种。Among them, all the nodes in the parent node list obtained from donor CU support the IAB function. The parent node list stored by the donor CU may specifically include at least one of IAB donor DU, IAB node, and gNB supporting the IAB function.
在一示例中，从donor CU中已获取的父节点列表中至少包括下述之一：In an example, the parent node list obtained from donor CU includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，从所述宿主集中单元实体中获取父节点列表，包括：In an example, obtaining the parent node list from the unit entity of the host centralization includes:
通过消息请求所述宿主集中单元实体发送父节点列表，以使所述宿主集中单元实体接收到请求之后向所述IAB节点发送父节点列表。The host central unit entity is requested to send the parent node list through a message, so that the host central unit entity sends the parent node list to the IAB node after receiving the request.
IAB节点如果想要在donor CU中获取父节点列表，则可以向donor CU发送请求消息，例如是无线资源控制层请求消息，以请求donor CU向所述IAB节点发送父节点列表。donor CU接收到RRC请求消息后，向所述IAB节点发送父 节点列表。If the IAB node wants to obtain the parent node list in the donor CU, it can send a request message to the donor CU, for example, a radio resource control layer request message, to request the donor CU to send the parent node list to the IAB node. After the donor CU receives the RRC request message, it sends the parent node list to the IAB node.
在一示例中，通过消息请求所述宿主集中单元实体发送父节点列表，包括：In an example, requesting the host central unit entity to send a list of parent nodes through a message includes:
通过无线资源控制层建立请求消息或者无线资源控制层建立完成消息或者无线资源控制层重配完成消息，请求所述宿主集中单元实体发送父节点列表。Through the radio resource control layer establishment request message or the radio resource control layer establishment completion message or the radio resource control layer reconfiguration completion message, the donor centralization unit entity is requested to send the parent node list.
IAB节点通过RRC消息请求donor CU发送父节点列表时，具体可以通过无线资源控制层建立请求(RRC Setup Request)消息请求donor CU发送父节点列表，也可以通过无线资源控制层建立完成(RRC Setup Complete)消息请求donor CU发送父节点列表，还可以通过无线资源控制层重配完成(RRC Reconfiguration Complete)消息请求donor CU发送父节点列表。When the IAB node requests the donor CU to send the parent node list through the RRC message, it can specifically request the donor CU to send the parent node list through the radio resource control layer setup request (RRC Setup Request) message, or it can be completed through the radio resource control layer (RRC Setup Complete) ) The message requests the donor CU to send the parent node list, and the radio resource control layer reconfiguration complete (RRC Reconfiguration Complete) message can also request the donor CU to send the parent node list.
在一示例中，通过消息请求所述宿主集中单元实体发送父节点列表，包括：In an example, requesting the host central unit entity to send a list of parent nodes through a message includes:
通过F1建立请求消息或gNB-DU配置更新消息或新的F1应用协议(F1Application Protocol，F1AP)消息，请求所述宿主集中单元实体发送父节点列表。Through an F1 establishment request message, a gNB-DU configuration update message, or a new F1 Application Protocol (F1 Application Protocol, F1AP) message, the host central unit entity is requested to send a list of parent nodes.
IAB节点通过消息请求donor CU发送父节点列表时，具体可以通过F1建立请求消息请求donor CU发送父节点列表，也可以通过gNB-DU配置更新消息请求donor CU发送父节点列表，还可以通过新的F1AP消息请求donor CU发送父节点列表。When the IAB node requests the donor CU to send the parent node list through a message, it can specifically request the donor CU to send the parent node list through the F1 establishment request message, or through the gNB-DU configuration update message to request the donor CU to send the parent node list, or through the new The F1AP message requests the donor CU to send the list of parent nodes.
在一示例中，从所述宿主集中单元实体中获取父节点列表，包括：In an example, obtaining the parent node list from the unit entity of the host centralization includes:
接收所述宿主集中单元实体主动通过无线资源控制层消息发送的父节点列表。Receive the parent node list actively sent by the donor centralization unit entity through a radio resource control layer message.
IAB接收的donor CU发送的父节点列表，还可以是donor CU主动通过RRC消息发送的。The parent node list sent by the donor CU received by the IAB may also be sent by the donor CU actively through the RRC message.
在一示例中，接收所述宿主集中单元实体主动通过无线资源控制层消息发送的父节点列表，包括：In an example, receiving the parent node list actively sent by the host central unit entity through a radio resource control layer message includes:
接收所述宿主集中单元实体主动通过无线资源控制层重配消息或者无线资 源控制层释放消息或者无线资源控制层拒绝消息发送的父节点列表。Receive the parent node list from which the donor centralization unit entity actively sends a radio resource control layer reconfiguration message or a radio resource control layer release message or a radio resource control layer reject message.
donor CU主动通过RRC消息向IAB节点发送父节点列表时，可以通过无线资源控制层重配(RRC Reconfiguration)消息向IAB节点发送父节点列表，也可以通过无线资源控制层释放(RRC Release)消息向IAB节点发送父节点列表，还可以通过无线资源控制层拒绝(RRC Reject)消息向IAB节点发送父节点列表。When the donor CU actively sends the parent node list to the IAB node through the RRC message, it can send the parent node list to the IAB node through the radio resource control layer reconfiguration (RRC Reconfiguration) message, or through the radio resource control layer release (RRC Release) message. The IAB node sends the parent node list, and can also send the parent node list to the IAB node through a radio resource control layer reject (RRC Reject) message.
其中，在上述实施例中，donor CU向IAB节点发送的父节点列表中的节点均支持IAB功能。Among them, in the foregoing embodiment, the nodes in the parent node list sent by the donor CU to the IAB node all support the IAB function.
在一示例中，donor CU向IAB节点发送的父节点列表中至少包括下述之一：In an example, the parent node list sent by the donor CU to the IAB node includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，所述确定所述IAB节点的父节点，包括：In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the determining the parent node of the IAB node includes:
所述IAB节点接入小区的情况下，在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点。When the IAB node accesses a cell, when the donor centralization unit entity determines that the DU accessed by the IAB node does not support the IAB function, it re-determines the IAB node's status according to the auxiliary operation of the donor centralization unit entity Parent node.
当IAB节点为初始接入时，在部署场景为第二场景的情况下，IAB节接入任意一个合适的小区之后，donor CU判断所述IAB节点接入的DU是否支持IAB功能，如果所述IAB节点接入的DU不支持IAB功能，donor CU则辅助所述IAB节点重新选择一个节点作为其父节点。When the IAB node is initially accessed, and the deployment scenario is the second scenario, after the IAB section is connected to any suitable cell, the donor CU determines whether the DU accessed by the IAB node supports the IAB function. The DU accessed by the IAB node does not support the IAB function, and the donor CU assists the IAB node to reselect a node as its parent node.
当IAB节点为非初始接入时，在部署场景为第二场景的情况下，IAB节接入任意一个合适的小区之后，donor CU判断所述IAB节点接入的DU是否支持 IAB功能，如果所述IAB节点接入的DU不支持IAB功能，donor CU则辅助所述IAB节点重新选择一个节点作为其父节点。When the IAB node is non-initial access, and the deployment scenario is the second scenario, after the IAB section is connected to any suitable cell, the donor CU determines whether the DU accessed by the IAB node supports the IAB function. The DU accessed by the IAB node does not support the IAB function, and the donor CU assists the IAB node to reselect a node as its parent node.
在一示例中，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：In an example, re-determining the parent node of the IAB node according to the auxiliary operation of the unit entity in the host set includes:
根据所述宿主集中单元实体发送的切换指令，将与所述切换指令对应的支持IAB功能的父节点重新确定为所述IAB节点的父节点。According to the switching instruction sent by the host central unit entity, the parent node supporting the IAB function corresponding to the switching instruction is re-determined as the parent node of the IAB node.
donor CU判断所述IAB节点接入的DU不支持IAB功能时，可以向IAB节点发送切换指令，将IAB节点的父节点重新切换至一个支持IAB功能的节点。When the donor CU judges that the DU accessed by the IAB node does not support the IAB function, it may send a switching instruction to the IAB node to switch the parent node of the IAB node to a node that supports the IAB function.
在一示例中，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：In an example, re-determining the parent node of the IAB node according to the auxiliary operation of the unit entity in the host set includes:
接收所述宿主集中单元实体发送的无线资源控制层释放消息，断开与原有DU的连接，并获取所述宿主集中单元实体通过无线资源控制层消息发送的父节点列表，根据所述父节点列表重新确定所述IAB节点的父节点。Receive the radio resource control layer release message sent by the donor centralization unit entity, disconnect the original DU, and obtain the parent node list sent by the donor centralization unit entity through the radio resource control layer message, according to the parent node The list re-determines the parent node of the IAB node.
donor CU判断所述IAB节点接入的DU不支持IAB功能时，如果所述IAB节点已经与不支持IAB功能的DU连接完成，则可以通过向所述IAB节点发送RRC释放消息，以使所述IAB节点接收到donor CU发送的RRC释放消息之后，断开与这个不支持IAB功能的DU之间的连接。When the donor CU judges that the DU accessed by the IAB node does not support the IAB function, if the IAB node has completed the connection with the DU that does not support the IAB function, it can send an RRC release message to the IAB node to enable the After the IAB node receives the RRC release message sent by the donor CU, it disconnects the DU that does not support the IAB function.
donor CU通过RRC消息向所述IAB节点发送父节点列表，所述IAB节点在接收到donor CU发送的父节点列表之后，基于所述父节点列表重新选择一个节点作为其父节点。The donor CU sends a parent node list to the IAB node through an RRC message. After receiving the parent node list sent by the donor CU, the IAB node reselects a node as its parent node based on the parent node list.
在一示例中，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：In an example, re-determining the parent node of the IAB node according to the auxiliary operation of the unit entity in the host set includes:
接收所述宿主集中单元实体发送的无线资源控制层拒绝消息，断开与原有DU的连接，并获取所述宿主集中单元实体通过无线资源控制层消息发送的父节 点列表，根据所述父节点列表重新确定所述IAB节点的父节点。Receive the radio resource control layer rejection message sent by the donor centralization unit entity, disconnect the original DU, and obtain the parent node list sent by the donor centralization unit entity through the radio resource control layer message, according to the parent node The list re-determines the parent node of the IAB node.
donor CU判断所述IAB节点接入的DU不支持IAB功能时，如果所述IAB节点已经与不支持IAB功能的DU正在建立连接，则可以通过向所述IAB节点发送RRC拒绝消息，以使所述IAB节点接收到donor CU发送的RRC拒绝消息之后，放弃与这个不支持IAB功能的DU之间的继续连接操作，并在接收到donor CU发送的父节点列表之后，基于所述父节点列表重新选择一个节点作为其父节点。When the donor CU judges that the DU accessed by the IAB node does not support the IAB function, if the IAB node is already establishing a connection with the DU that does not support the IAB function, it can send an RRC rejection message to the IAB node so that all After the IAB node receives the RRC rejection message sent by the donor CU, it abandons the continued connection operation with this DU that does not support the IAB function, and after receiving the parent node list sent by the donor CU, re-starts based on the parent node list. Select a node as its parent node.
其中，donor CU通过RRC消息发送的父节点列表中的节点均支持IAB功能。Among them, the nodes in the parent node list sent by the donor CU through the RRC message all support the IAB function.
在一示例中，donor CU通过RRC消息向IAB节点发送的父节点列表中至少包括下述之一：In an example, the parent node list sent by the donor CU to the IAB node through the RRC message includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，从所述宿主集中单元实体中获取的父节点列表中，包括：In an example, the list of parent nodes obtained from the unit entity in the host set includes:
连接所述宿主集中单元实体的donor DU和IAB节点，以及连接所述宿主集中单元实体相邻基站的donor DU和IAB节点。The donor DU and IAB nodes connected to the donor centralization unit entity, and the donor DU and IAB nodes connected to the neighboring base stations of the donor centralization unit entity.
donor CU发送的父节点列表中，既可能包含连接所述donor CU的donor DU和IAB节点，也可能包含连接与所述donor CU相邻的基站的donor DU和IAB节点。The parent node list sent by the donor CU may include donor DU and IAB nodes connected to the donor CU, and may also include donor DU and IAB nodes connected to base stations adjacent to the donor CU.
在一示例中，所述宿主集中单元实体获知DU是否支持IAB功能的方式包括：In an example, the method for the host central unit entity to learn whether the DU supports the IAB function includes:
根据DU在F1建立请求消息或者gNB-DU配置更新消息或新的F1AP消息 中指示所述DU支持IAB功能。According to the DU, it is indicated in the F1 establishment request message or the gNB-DU configuration update message or the new F1AP message that the DU supports the IAB function.
DU可以通过F1建立请求消息或者gNB-DU配置更新消息或新的F1AP消息向donor CU指示其支持IAB功能。The DU can indicate to the donor CU that it supports the IAB function through an F1 establishment request message or a gNB-DU configuration update message or a new F1AP message.
在一示例中，所述宿主集中单元实体生成或更新所述父节点列表的方式包括：In an example, the method of generating or updating the parent node list by the host central unit entity includes:
所述宿主集中单元实体从操作管理维护实体配置信息中获取支持IAB功能的基站列表，其中，所述支持IAB功能的基站列表中包括支持IAB功能的基站信息以及支持IAB功能的服务小区信息。The donor centralized unit entity obtains a list of base stations supporting the IAB function from the configuration information of the operation, management and maintenance entity, where the list of base stations supporting the IAB function includes information of base stations supporting the IAB function and information of serving cells supporting the IAB function.
Donor CU可以从OAM获取一个支持IAB功能的基站列表，其中，从OAM获取的基站列表中可以包含支持IAB功能的基站信息，也可以包含支持IAB功能的服务小区信息。Donor CU can obtain a list of base stations that support the IAB function from OAM, where the base station list obtained from OAM can include information about base stations that support the IAB function, and can also include information about serving cells that support the IAB function.
在一示例中，所述宿主集中单元实体生成或更新所述父节点列表的方式包括：In an example, the method of generating or updating the parent node list by the host central unit entity includes:
所述宿主集中单元实体通过Xn建立请求消息或者下一代无线接入网(Next Generation Radio Access Network，NG-RAN)节点配置更新信息，与相邻基站交互支持IAB功能的服务小区信息。The donor centralization unit entity exchanges the information of the serving cell supporting the IAB function with the neighboring base station through the Xn establishment request message or the Next Generation Radio Access Network (NG-RAN) node configuration update information.
donor CU可以通过Xn建立请求与相邻基站交互支持IAB功能的服务小区信息，也可以通过NG-RAN节点配置更新信息与相邻基站交互支持IAB功能的服务小区信息，以达到获取属于相邻基站的且支持IAB功能的服务小区信息。The donor CU can use the Xn establishment request to interact with neighboring base stations to support the serving cell information of the IAB function, or through the NG-RAN node configuration update information to interact with the neighboring base station to support the IAB function of the serving cell information, so as to obtain the neighboring base station Serving cell information that supports the IAB function.
在一示例中，在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：In an example, when the host central unit entity determines that the DU accessed by the IAB node does not support the IAB function, re-determining the parent node of the IAB node according to the auxiliary operation of the host central unit entity includes:
在无线资源控制层建立请求消息中指示所述IAB节点支持IAB功能；Instruct the IAB node to support the IAB function in the radio resource control layer establishment request message;
在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时， 根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点。When the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, the parent node of the IAB node is re-determined according to the auxiliary operation of the donor centralized unit entity.
在一示例中，在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：In an example, when the host central unit entity determines that the DU accessed by the IAB node does not support the IAB function, re-determining the parent node of the IAB node according to the auxiliary operation of the host central unit entity includes:
在无线资源控制层建立完成消息中指示所述IAB节点支持IAB功能；Instruct the IAB node to support the IAB function in the radio resource control layer establishment complete message;
在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点。When the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, the parent node of the IAB node is re-determined according to the auxiliary operation of the donor centralized unit entity.
在一示例中，在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：In an example, when the host central unit entity determines that the DU accessed by the IAB node does not support the IAB function, re-determining the parent node of the IAB node according to the auxiliary operation of the host central unit entity includes:
在所述宿主集中单元实体通过初始上下文建立请求消息携带的IAB授权指示获知所述IAB节点支持IAB功能，并判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点。When the donor centralized unit entity learns that the IAB node supports the IAB function through the IAB authorization indication carried in the initial context establishment request message, and determines that the DU accessed by the IAB node does not support the IAB function, the donor centralized unit The auxiliary operation of the entity redefines the parent node of the IAB node.
也即，IAB节点可以在RRC建立请求消息中向donor CU指示出自己的IAB节点身份，还可以在RRC建立完成消息中向donor CU指示出自己的IAB节点身份。That is, the IAB node may indicate its IAB node identity to the donor CU in the RRC establishment request message, and may also indicate its IAB node identity to the donor CU in the RRC establishment complete message.
donor CU还可以在初始上下文建立请求消息携带的IAB授权指示中获知一个节点的IAB节点身份，也即获知其支持IAB功能。The donor CU can also learn the IAB node identity of a node in the IAB authorization indication carried in the initial context establishment request message, that is, learn that it supports the IAB function.
当IAB节点在RRC建立请求消息中向donor CU指示出自己的IAB节点身份时，在一示例中，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, in an example, re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:
接收所述宿主集中单元实体发送的无线资源控制层拒绝消息，断开与原有DU的连接，并重新确定所述IAB节点的父节点。Receive the radio resource control layer rejection message sent by the donor centralization unit entity, disconnect the original DU, and re-determine the parent node of the IAB node.
当IAB节点在RRC建立请求消息中向donor CU指示出自己的IAB节点身份时，donor CU如果识别出IAB节点接入的DU不支持IAB功能，donor CU则可以向IAB节点发送RRC拒绝消息(此时未收到IAB节点发送的RRC建立完成消息)，所述IAB节点接收到该RRC拒绝消息之后，重新进行小区选择。When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can send an RRC rejection message to the IAB node (this When the RRC establishment complete message sent by the IAB node is not received), the IAB node re-selects the cell after receiving the RRC reject message.
在一示例中，无线资源控制层拒绝消息中至少包括如下之一：In an example, the radio resource control layer rejection message includes at least one of the following:
支持IAB的频率信息；Support IAB frequency information;
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
当IAB节点在RRC建立请求消息中向donor CU指示出自己的IAB节点身份时，在一示例中，donor CU如果识别出IAB节点接入的DU不支持IAB功能，donor CU则可以在接收到IAB节点发送的RRC建立完成消息之后，向所述IAB节点发送RRC释放消息，所述IAB节点接收到该RRC释放消息之后，重新进行小区选择。When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, in an example, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can receive the IAB After the RRC establishment complete message sent by the node, the RRC release message is sent to the IAB node, and the IAB node performs cell selection again after receiving the RRC release message.
在一示例中，RRC释放消息中至少包括如下之一：In an example, the RRC release message includes at least one of the following:
支持IAB的频率信息；Support IAB frequency information;
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
当IAB节点在RRC建立请求消息中向donor CU指示出自己的IAB节点身份时，在一示例中，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB 节点的父节点，包括：When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, in an example, re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:
接收所述宿主集中单元实体，在确定所述IAB节点初始接入过程结束之后，发送的无线资源控制层释放消息，断开与原有DU的连接，并重新确定所述IAB节点的父节点。After receiving the donor centralization unit entity, after determining that the initial access process of the IAB node ends, send a radio resource control layer release message, disconnect the original DU, and re-determine the parent node of the IAB node.
当IAB节点在RRC建立请求消息中向donor CU指示出自己的IAB节点身份时，donor CU如果识别出IAB节点接入的DU不支持IAB功能，donor CU则可以在等待所述IAB节点初始接入过程结束之后，向所述IAB节点发送RRC释放消息，所述IAB节点接收到该RRC释放消息之后，重新进行小区选择。When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the initial access of the IAB node After the process ends, an RRC release message is sent to the IAB node, and after receiving the RRC release message, the IAB node performs cell selection again.
在一示例中，RRC释放消息中至少包括如下之一：In an example, the RRC release message includes at least one of the following:
支持IAB的频率信息；Support IAB frequency information;
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
当IAB节点在RRC建立请求消息中向donor CU指示出自己的IAB节点身份时，在一示例中，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, in an example, re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:
根据所述宿主集中单元实体在确定所述IAB节点初始接入过程结束之后发送的切换指令，将与所述切换指令对应的支持IAB功能的父节点重新确定为所述IAB节点的父节点。According to the handover instruction sent by the donor centralization unit entity after determining that the initial access process of the IAB node ends, the parent node supporting the IAB function corresponding to the handover instruction is re-determined as the parent node of the IAB node.
当IAB节点在RRC建立请求消息中向donor CU指示出自己的IAB节点身份时，donor CU如果识别出IAB节点接入的DU不支持IAB功能，donor CU则可以在等待所述IAB节点初始接入过程结束之后，向IAB节点发送切换指令，将IAB节点的父节点重新切换至一个支持IAB功能的节点。When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the initial access of the IAB node After the process is over, a switch instruction is sent to the IAB node to switch the parent node of the IAB node to a node that supports the IAB function.
当IAB节点在RRC建立完成消息中向donor CU指示出自己的IAB节点身份时，在一示例中，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment complete message, in an example, re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:
接收所述宿主集中单元实体发送的无线资源控制层释放消息，断开与原有DU的连接，并重新确定所述IAB节点的父节点。Receive the radio resource control layer release message sent by the donor centralization unit entity, disconnect the original DU, and re-determine the parent node of the IAB node.
当IAB节点在RRC建立完成消息中向donor CU指示出自己的IAB节点身份时，donor CU如果识别出IAB节点接入的DU不支持IAB功能，donor CU则可以向所述IAB节点发送RRC释放消息，所述IAB节点接收到该RRC释放消息之后，重新进行小区选择。When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment complete message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can send an RRC release message to the IAB node After receiving the RRC release message, the IAB node performs cell selection again.
在一示例中，RRC释放消息中至少包括如下之一：In an example, the RRC release message includes at least one of the following:
支持IAB的频率信息；Support IAB frequency information;
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
当IAB节点在RRC建立完成消息中向donor CU指示出自己的IAB节点身份时，在一示例中，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment complete message, in an example, re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:
接收所述宿主集中单元实体，在确定所述IAB节点初始接入过程结束之后，发送的无线资源控制层释放消息，断开与原有DU的连接，并重新确定所述IAB节点的父节点。After receiving the donor centralization unit entity, after determining that the initial access process of the IAB node ends, send a radio resource control layer release message, disconnect the original DU, and re-determine the parent node of the IAB node.
当IAB节点在RRC建立完成消息中向donor CU指示出自己的IAB节点身份时，donor CU如果识别出IAB节点接入的DU不支持IAB功能，donor CU则可以在等待所述IAB节点初始接入过程结束之后，向所述IAB节点发送RRC 释放消息，所述IAB节点接收到该RRC释放消息之后，重新进行小区选择。When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment complete message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the initial access of the IAB node After the process ends, it sends an RRC release message to the IAB node, and after receiving the RRC release message, the IAB node performs cell selection again.
在一示例中，RRC释放消息中至少包括如下之一：In an example, the RRC release message includes at least one of the following:
支持IAB的频率信息；Support IAB frequency information;
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
当IAB节点在RRC建立完成消息中向donor CU指示出自己的IAB节点身份时，在一示例中，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment complete message, in an example, re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:
根据所述宿主集中单元实体在确定所述IAB节点初始接入过程结束之后发送的切换指令，将与所述切换指令对应的支持IAB功能的父节点重新确定为所述IAB节点的父节点。According to the handover instruction sent by the donor centralization unit entity after determining that the initial access process of the IAB node ends, the parent node supporting the IAB function corresponding to the handover instruction is re-determined as the parent node of the IAB node.
当IAB节点在RRC建立完成消息中向donor CU指示出自己的IAB节点身份时，donor CU如果识别出IAB节点接入的DU不支持IAB功能，donor CU则可以在等待所述IAB节点初始接入过程结束之后，向IAB节点发送切换指令，将IAB节点的父节点重新切换至一个支持IAB功能的节点。When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment complete message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the initial access of the IAB node After the process is over, a switch instruction is sent to the IAB node to switch the parent node of the IAB node to a node that supports the IAB function.
当donor CU在初始上下文建立请求消息携带的IAB授权指示中获知IAB节点的IAB节点身份时，在一示例中，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：When the donor CU learns the IAB node identity of the IAB node in the IAB authorization indication carried in the initial context establishment request message, in an example, the parent node of the IAB node is re-determined according to the auxiliary operation of the host centralized unit entity, include:
接收所述宿主集中单元实体，在确定所述IAB节点初始接入过程结束之后，发送的无线资源控制层释放消息，断开与原有DU的连接，并重新确定所述IAB节点的父节点。After receiving the donor centralization unit entity, after determining that the initial access process of the IAB node ends, send a radio resource control layer release message, disconnect the original DU, and re-determine the parent node of the IAB node.
当donor CU在初始上下文建立请求消息携带的IAB授权指示中获知IAB 节点的IAB节点身份时，donor CU如果识别出IAB节点接入的DU不支持IAB功能，donor CU则可以在等待所述IAB节点初始接入过程结束之后，向所述IAB节点发送RRC释放消息，所述IAB节点接收到该RRC释放消息之后，重新进行小区选择。When the donor CU learns the IAB node identity of the IAB node in the IAB authorization indication carried in the initial context establishment request message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the IAB node After the initial access procedure ends, an RRC release message is sent to the IAB node, and the IAB node performs cell selection again after receiving the RRC release message.
在一示例中，RRC释放消息中至少包括如下之一：In an example, the RRC release message includes at least one of the following:
支持IAB的频率信息；Support IAB frequency information;
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
当donor CU在初始上下文建立请求消息携带的IAB授权指示中获知IAB节点的IAB节点身份时，在一示例中，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：When the donor CU learns the IAB node identity of the IAB node in the IAB authorization indication carried in the initial context establishment request message, in an example, the parent node of the IAB node is re-determined according to the auxiliary operation of the host centralized unit entity, include:
根据所述宿主集中单元实体在确定所述IAB节点初始接入过程结束之后发送的切换指令，将与所述切换指令对应的支持IAB功能的父节点重新确定为所述IAB节点的父节点。According to the handover instruction sent by the donor centralization unit entity after determining that the initial access process of the IAB node ends, the parent node supporting the IAB function corresponding to the handover instruction is re-determined as the parent node of the IAB node.
当donor CU在初始上下文建立请求消息携带的IAB授权指示中获知IAB节点的IAB节点身份时，donor CU则可以在等待所述IAB节点初始接入过程结束之后，向IAB节点发送切换指令，将IAB节点的父节点重新切换至一个支持IAB功能的节点。When the donor CU learns the IAB node identity of the IAB node in the IAB authorization indication carried in the initial context establishment request message, the donor CU can send a handover instruction to the IAB node after waiting for the end of the initial access process of the IAB node to transfer the IAB node The parent node of the node switches to a node that supports the IAB function.
在一示例中，上述方法还包括：根据操作管理维护实体发送的配置更新信息，对本地保存的父节点列表进行更新。In an example, the above method further includes: updating the locally stored parent node list according to the configuration update information sent by the operation management and maintenance entity.
在IAB节点本地已经存储了父节点列表的情况下，如果OAM为所述IAB节点配置了父节点列表，IAB节点可以根据OAM的配置信息，对本地存储的父 节点列表进行更新。In the case that the IAB node has stored the parent node list locally, if the OAM configures the parent node list for the IAB node, the IAB node can update the locally stored parent node list according to the configuration information of the OAM.
在一示例中，当OAM存储的父节点列表发生变化后，OAM可以将IAB功能发生变化的父节点信息发送给所述IAB节点，以使IAB节点根据接收的IAB功能发生变化的父节点信息对本地存储的父节点列表进行更新。In an example, when the parent node list stored by the OAM changes, the OAM may send the parent node information whose IAB function has changed to the IAB node, so that the IAB node can pair the parent node information according to the received IAB function change. The locally stored parent node list is updated.
在一示例中，当OAM存储的父节点列表发生变化后，OAM可以将更新后的父节点列表发送给IAB节点，以使IAB节点根据接收的父节点列表对本地存储的父节点列表进行更新。In an example, when the parent node list stored by the OAM changes, the OAM may send the updated parent node list to the IAB node, so that the IAB node can update the locally stored parent node list according to the received parent node list.
在一示例中，OAM存储的父节点列表中至少包括下述之一：In an example, the parent node list stored by OAM includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，上述方法还包括：根据宿主集中单元实体发送的父节点更新信息，对本地保存的父节点列表进行更新。In an example, the above method further includes: updating the locally stored parent node list according to the parent node update information sent by the host central unit entity.
donor CU中存储一个包含支持IAB功能的IAB donor DU和/或IAB节点和/或gNB的列表，如果donor CU中存储的列表发生变化，则将父节点更新信息发送至IAB节点，以使IAB节点对本地存储的父节点列表进行更新。The donor CU stores a list of IAB donor DU and/or IAB nodes and/or gNB that support the IAB function. If the list stored in the donor CU changes, the parent node update information is sent to the IAB node to make the IAB node Update the locally stored parent node list.
在一示例中，根据所述宿主集中单元实体发送的父节点更新信息，对本地保存的父节点列表进行更新，包括：In an example, updating the locally stored parent node list according to the parent node update information sent by the host central unit entity includes:
根据所述宿主集中单元实体通过无线资源控制层消息或者F1建立响应消息或者gNB-CU配置更新消息或者新的F1AP消息发送的IAB功能变更的父节点信息，对本地存储的父节点列表进行更新。The locally stored parent node list is updated according to the parent node information of the IAB function change sent by the donor centralized unit entity through the radio resource control layer message or the F1 establishment response message or the gNB-CU configuration update message or the new F1AP message.
如果donor CU中存储的列表中有IAB donor DU或IAB节点或gNB支持IAB的功能发生改变，donor CU可以将IAB功能发生改变的IAB donor DU、IAB 节点以及gNB的信息发送给IAB节点，其中可以通过RRC重配消息或者F1建立响应消息或者gNB-CU配置更新消息或者新的F1AP消息向IAB节点发送，以使IAB节点更新本地父节点列表。If there is an IAB donor DU or IAB node or gNB in the list stored in the donor CU that changes the function that supports IAB, the donor CU can send the IAB donor DU, IAB node, and gNB whose IAB function has changed to the IAB node, which can be The RRC reconfiguration message or the F1 establishment response message or the gNB-CU configuration update message or the new F1AP message is sent to the IAB node, so that the IAB node updates the local parent node list.
在一示例中，根据所述宿主集中单元实体发送的父节点更新信息，对本地保存的父节点列表进行更新，包括：In an example, updating the locally stored parent node list according to the parent node update information sent by the host central unit entity includes:
根据所述宿主集中单元实体通过无线资源控制层消息或者F1建立响应消息或者gNB-CU配置更新消息或者新的F1AP消息发送的已更新父节点列表，对本地存储的父节点列表进行更新。The locally stored parent node list is updated according to the updated parent node list sent by the donor centralization unit entity through a radio resource control layer message or an F1 establishment response message or a gNB-CU configuration update message or a new F1AP message.
如果donor CU中存储的列表中有IAB donor DU或IAB节点或gNB支持IAB的功能发生改变，donor CU可以将本地更新后的父节点列表发送给IAB节点，其中可以通过RRC重配消息或者F1建立响应消息或者gNB-CU配置更新消息或者新的F1AP消息向IAB节点发送，以使IAB节点更新本地父节点列表。If there is an IAB donor DU or IAB node or gNB in the list stored in the donor CU that supports IAB function changes, the donor CU can send the locally updated parent node list to the IAB node, which can be established through the RRC reconfiguration message or F1 A response message or a gNB-CU configuration update message or a new F1AP message is sent to the IAB node, so that the IAB node updates the local parent node list.
在一示例中，IAB节点还可以根据RRC释放消息中携带的父节点列表对本地父节点列表进行更新。In an example, the IAB node may also update the local parent node list according to the parent node list carried in the RRC release message.
在一示例中，IAB节点还可以根据RRC拒绝消息中携带的父节点列表更新本地父节点列表。In an example, the IAB node may also update the local parent node list according to the parent node list carried in the RRC rejection message.
在一示例中，donor CU中存储的父节点列表中至少包括下述之一：In an example, the parent node list stored in the donor CU includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一个示例性实施方式中，图10为本申请提供的一种父节点选择方法的流程示意图。该方法可以适用于IAB在接入网络时选择一个支持IAB功能的父节 点的情况。该方法可以由本申请提供的应用于AMF实体的父节点选择装置执行，该父节点选择装置可以由软件和/或硬件实现，并集成在AMF实体中。In an exemplary embodiment, FIG. 10 is a schematic flowchart of a method for selecting a parent node provided by this application. This method can be applied to the situation where the IAB selects a parent node that supports the IAB function when accessing the network. The method can be executed by the parent node selection device applied to the AMF entity provided in this application, and the parent node selection device can be implemented by software and/or hardware and integrated in the AMF entity.
如图10所示，本申请提供的应用于AMF实体的一种父节点选择方法，包括：As shown in Figure 10, a parent node selection method applied to an AMF entity provided by this application includes:
S220、基于NG接口的切换，将IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示发送给与目标父节点对应的宿主集中单元实体或基站。S220: Based on the handover of the NG interface, send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralization unit entity or the base station corresponding to the target parent node.
其中，基于NG接口的切换，主要包括在IAB节点父节点切换前后，IAB节点连接的donor CU或者基站连接相同AMF实体的情况，连接不同AMF实体的情况，以及连接不同RAT(Radio Access Technology，无线电接入技术)的情况。Among them, the handover based on the NG interface mainly includes the case where the donor CU or the base station connected to the IAB node is connected to the same AMF entity, the case of connecting different AMF entities, and the case of connecting to different RATs (Radio Access Technology, radio Access technology).
本申请提供的一种父节点选择方法，在IAB节点根据所述IAB节点的接入情况以及IAB节点接入网络的部署场景，确定出所述IAB节点的目标父节点之后，将所述IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示发送给与目标父节点对应的宿主集中单元实体或基站，实现了IAB节点与其选择的支持IAB功能的父节点的连接，进而使IAB节点的IAB功能得以保证，达到了为其他的子IAB节点以及UE服务的效果。In the method for selecting a parent node provided by this application, after the IAB node determines the target parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node’s access to the network, the IAB node The IAB authorization indication information or the IAB node indication of the IAB node is sent to the donor central unit entity or base station corresponding to the target parent node, which realizes the connection between the IAB node and the parent node that supports the IAB function selected by the IAB node. The IAB function is guaranteed, and the effect of serving other sub-IAB nodes and UEs is achieved.
在一示例中，将所述IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示发送给与目标父节点对应的宿主集中单元实体或基站，包括：In an example, sending the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralization unit entity or base station corresponding to the target parent node includes:
将所述IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示，通过NGAP(Next Generation Application Protocol，下一代应用协议)切换请求消息发送给与目标父节点对应的宿主集中单元实体或基站。Send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralized unit entity or base station corresponding to the target parent node through an NGAP (Next Generation Application Protocol) handover request message .
在一示例中，将所述IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示发送给与目标父节点对应的宿主集中单元实体或基站，包括：In an example, sending the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralization unit entity or base station corresponding to the target parent node includes:
将所述IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示，通过路径切换请求确认消息，发送给与目标父节点对应的宿主集中单元实体或基 站。Send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the host centralized unit entity or base station corresponding to the target parent node through a path switch request confirmation message.
本实施例还提供了父节点选择装置，图11为本申请提供的一种父节点选择装置的结构示意图，如图11所示，本申请实施例提供的一种应用于IAB节点中的父节点选择装置，可以集成在IAB节点中，该装置包括：This embodiment also provides a parent node selection device. FIG. 11 is a schematic structural diagram of a parent node selection device provided by this application. As shown in FIG. 11, an embodiment of this application provides a parent node applied to an IAB node. The selection device can be integrated in the IAB node. The device includes:
第一父节点选择模块320，设置为根据IAB节点的接入情况以及IAB节点接入网络的部署场景，确定所述IAB节点的父节点。The first parent node selection module 320 is configured to determine the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.
本实施例提供的应用于IAB节点中的父节点选择装置用于实现如本申请实施例所述的应用于IAB节点中的父节点选择方法，本实施例提供的应用于IAB节点中的父节点选择装置实现原理和技术效果与本申请实施例所述的应用于IAB节点中的父节点选择方法类似，此处不再赘述。The device for selecting a parent node applied to an IAB node provided in this embodiment is used to implement the method for selecting a parent node applied to an IAB node as described in the embodiment of this application. The parent node selection method provided in this embodiment is applied to an IAB node The implementation principle and technical effect of the selection device are similar to the parent node selection method applied to the IAB node described in the embodiment of the present application, and will not be repeated here.
其中，一个IAB节点的IAB节点称为这个IAB节点的子IAB节点，一个IAB节点以连接身份所接入的支持IAB功能的DU或基站称为这个IAB节点的父IAB节点。Among them, the IAB node of an IAB node is called the child IAB node of the IAB node, and the DU or base station supporting the IAB function accessed by an IAB node as a connection identity is called the parent IAB node of the IAB node.
所述IAB节点可以是DU实体，也可以是MT。The IAB node may be a DU entity or an MT.
在一示例中，IAB节点接入网络的部署场景可以包括如下六种部署场景。In an example, the deployment scenarios for the IAB node to access the network may include the following six deployment scenarios.
第一场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，IAB节点和支持IAB功能的基站。The first scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station supporting the IAB function.
第二场景为：所述IAB节点部署位置设定区域内包括IAB donor DU和不支持IAB功能的分布单元实体，所述不支持IAB功能的分布单元实体连接宿主集中单元实体donor CU。The second scenario is: the IAB node deployment location setting area includes the IAB donor DU and the distributed unit entity that does not support the IAB function, and the distributed unit entity that does not support the IAB function is connected to the donor centralized unit entity donor CU.
第三场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，IAB节点和不支持IAB功能的基站，与所述基站连接的接入管理功能实体支持IAB功能。The third scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station that does not support the IAB function, and the access management function entity connected to the base station supports the IAB function.
第四场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，IAB节点和不支持IAB功能的基站，与所述基站连接的接入管理功能实体不支持IAB功能。The fourth scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station that does not support the IAB function, and the access management function entity connected to the base station does not support the IAB function.
第五场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，IAB节点和不支持IAB功能的分布单元实体，与所述不支持IAB功能的分布单元实体连接的集中单元实体不支持IAB功能，与所述集中单元实体连接的接入管理功能实体支持IAB功能。The fifth scenario is: the IAB node deployment location setting area includes IAB donor DU, the IAB node and the distributed unit entity that does not support the IAB function, and the centralized unit entity connected to the distributed unit entity that does not support the IAB function does not support IAB function, the access management function entity connected with the centralized unit entity supports the IAB function.
第六场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，IAB节点和不支持IAB功能的分布单元实体，与所述不支持IAB功能的分布单元实体连接的集中单元实体不支持IAB功能，与所述集中单元实体连接的接入管理功能实体不支持IAB功能。The sixth scenario is: the IAB node deployment location setting area includes IAB donor DU, the IAB node and the distributed unit entity that does not support the IAB function, and the centralized unit entity connected to the distributed unit entity that does not support the IAB function does not support IAB function, the access management function entity connected to the centralized unit entity does not support the IAB function.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第一场景至第六场景之一，第一父节点选择模块320设置为：在所述IAB节点预配置的父节点列表中选择所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is set to: The parent node of the IAB node is selected from the parent node list preconfigured by the IAB node.
在一示例中，IAB节点预配置的父节点列表中至少包括下述之一：In an example, the pre-configured parent node list of the IAB node includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，上述装置还包括父节点IAB功能判断模块，设置为：所述IAB节点接入小区的情况下，根据无线资源控制层重配消息中是否包含回程自适应协议层配置消息判断所述IAB节点接入的分布单元实体或者基站是否支持IAB功能。In an example, the above-mentioned apparatus further includes a parent node IAB function judgment module, which is set to judge whether the radio resource control layer reconfiguration message includes a backhaul adaptive protocol layer configuration message when the IAB node accesses the cell. Whether the distributed unit entity or base station accessed by the IAB node supports the IAB function.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部 署场景为第一场景至第六场景之一，第一父节点选择模块320设置为：基于小区广播的***信息选择所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is set to: The broadcasted system information selects the parent node of the IAB node.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第一场景至第六场景之一，第一父节点选择模块320设置为：根据小区广播的***信息中是否包括IAB专有PRACH配置，判断所述IAB节点接入的小区是否支持IAB功能。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is set to: Whether the broadcast system information includes the IAB-specific PRACH configuration, it is determined whether the cell accessed by the IAB node supports the IAB function.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第一场景至第六场景之一，第一父节点选择模块320设置为：根据小区广播的***信息中是否包括IAB专用***信息，判断所述IAB节点接入的小区是否支持IAB功能，其中，所述IAB专用***信息包括小区接入禁止信息、接纳控制参数、小区选择参数、小区重选参数中的至少一种。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is set to: Whether the broadcasted system information includes IAB dedicated system information, determine whether the cell accessed by the IAB node supports the IAB function, where the IAB dedicated system information includes cell access barring information, admission control parameters, cell selection parameters, cell Reselect at least one of the parameters.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第一场景至第六场景之一，第一父节点选择模块320设置为：基于IAB节点或者IAB宿主分布单元实体广播的用于小区重选的***信息选择所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is set to: The system information used for cell reselection broadcast by the node or the IAB host distribution unit entity selects the parent node of the IAB node.
其中，所述IAB节点或者IAB donor CU广播的用于小区重选的***信息包括下述至少之一：The system information used for cell reselection broadcast by the IAB node or IAB donor CU includes at least one of the following:
支持IAB功能的频率信息；Frequency information supporting IAB function;
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为初始接入，所述部署场景为第一场景至第六场景之一，第一父节点选择模块320设置为：所述IAB节点接入小 区的情况下，获取操作管理维护实体配置信息中的父节点列表；从所述父节点列表中选择所述IAB节点的父节点。In an example, the access condition of the IAB node is initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is set to: the IAB node accesses the cell In the case of obtaining the parent node list in the configuration information of the operation management and maintenance entity; selecting the parent node of the IAB node from the parent node list.
在一示例中，在OAM配置信息中获取的父节点列表中至少包括下述之一：In an example, the parent node list obtained in the OAM configuration information includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为非初始接入，所述部署场景为第一场景至第六场景之一，第一父节点选择模块320设置为：在所述IAB节点从OAM配置信息中已获取的父节点列表中选择所述IAB节点的父节点。In an example, the access condition of the IAB node is non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is configured to: The parent node of the IAB node is selected from the parent node list obtained in the OAM configuration information.
在一示例中，从OAM中已获取的父节点列表中至少包括下述之一：In an example, the parent node list obtained from OAM includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为非初始接入，所述部署场景为第一场景至第六场景之一，第一父节点选择模块320设置为：在所述IAB节点从宿主集中单元实体中已获取的父节点列表中选择所述IAB节点的父节点。In an example, the access condition of the IAB node is non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is configured to: The parent node of the IAB node is selected from the acquired parent node list in the unit entity of the host centralization.
在一示例中，从donor CU中已获取的父节点列表中至少包括下述之一：In an example, the parent node list obtained from donor CU includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，第一父节点选择模块320设置为：通过消息请求所述宿主集中单元实体发送父节点列表，以使所述宿主集中单元实体接收到请求之后向所述IAB节点发送父节点列表，并在所述IAB节点从宿主集中单元实体中已获取的父节点列表中选择所述IAB节点的父节点。In an example, the first parent node selection module 320 is configured to request the host central unit entity to send a parent node list through a message, so that the host central unit entity sends the parent node list to the IAB node after receiving the request , And select the parent node of the IAB node from the list of parent nodes that the IAB node has obtained from the host centralized unit entity.
在一示例中，第一父节点选择模块320设置为：通过无线资源控制层建立请求消息或者无线资源控制层建立完成消息或者无线资源控制层重配完成消息，请求所述宿主集中单元实体发送父节点列表，并在所述IAB节点从宿主集中单元实体中已获取的父节点列表中选择所述IAB节点的父节点。In an example, the first parent node selection module 320 is configured to request the donor central unit entity to send the parent node through a radio resource control layer establishment request message or a radio resource control layer establishment completion message or a radio resource control layer reconfiguration completion message. Node list, and select the parent node of the IAB node from the parent node list that the IAB node has obtained from the host centralized unit entity.
在一示例中，第一父节点选择模块320设置为：通过F1建立请求消息或gNB-DU配置更新消息或新的F1AP消息，请求所述宿主集中单元实体发送父节点列表，并在所述IAB节点从宿主集中单元实体中已获取的父节点列表中选择所述IAB节点的父节点。In an example, the first parent node selection module 320 is configured to request the host central unit entity to send a list of parent nodes through an F1 establishment request message or a gNB-DU configuration update message or a new F1AP message, and send the parent node list to the IAB The node selects the parent node of the IAB node from the parent node list that has been obtained in the unit entity of the host centralization.
在一示例中，第一父节点选择模块320设置为：接收所述宿主集中单元实体主动通过无线资源控制层消息发送的父节点列表，并在所述IAB节点从宿主集中单元实体中已获取的父节点列表中选择所述IAB节点的父节点。In an example, the first parent node selection module 320 is configured to: receive the parent node list actively sent by the host centralized unit entity via a radio resource control layer message, and obtain the parent node list from the host centralized unit entity by the IAB node. Select the parent node of the IAB node in the parent node list.
在一示例中，第一父节点选择模块320设置为：接收所述宿主集中单元实体主动通过无线资源控制层重配消息或者无线资源控制层释放消息或者无线资源控制层拒绝消息发送的父节点列表，并在所述IAB节点从宿主集中单元实体中已获取的父节点列表中选择所述IAB节点的父节点。In an example, the first parent node selection module 320 is configured to receive a list of parent nodes sent by the donor centralized unit entity actively through a radio resource control layer reconfiguration message or a radio resource control layer release message or a radio resource control layer rejection message , And select the parent node of the IAB node from the list of parent nodes that the IAB node has obtained from the host centralized unit entity.
在一示例中，donor CU向IAB节点发送的父节点列表中至少包括下述之一：In an example, the parent node list sent by the donor CU to the IAB node includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：所述IAB节点接入小区的情况下，在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: In this case, when the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, the parent node of the IAB node is re-determined according to the auxiliary operation of the donor centralized unit entity.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：所述IAB节点接入小区的情况下，在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体发送的切换指令，将与所述切换指令对应的支持IAB功能的父节点重新确定为所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: In this case, when the host central unit entity determines that the DU accessed by the IAB node does not support the IAB function, according to the switching instruction sent by the host central unit entity, the parent node supporting the IAB function corresponding to the switching instruction Re-determined as the parent node of the IAB node.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：所述IAB节点接入小区的情况下，在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，接收所述宿主集中单元实体发送的无线资源控制层释放消息，断开与原有DU的连接，并获取所述宿主集中单元实体通过无线资源控制层消息发送的父节点列表，根据所述父节点列表重新确定所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: In this case, when the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, it receives the radio resource control layer release message sent by the donor centralized unit entity, disconnects the original DU, and Obtain the parent node list sent by the donor centralization unit entity through a radio resource control layer message, and re-determine the parent node of the IAB node according to the parent node list.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：所述IAB节点接入小区的情况下，在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，接收所述宿主集中单元实体发送的无线资源控制层拒绝消息，断开与原有DU的连接，并获取所述宿主集中单元实体通过无线资源控制层消息发送的父节点列表，根据所述父节点列表重新确定所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: In this case, when the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, it receives the radio resource control layer rejection message sent by the donor centralized unit entity, disconnects the original DU, and Obtain the parent node list sent by the donor centralization unit entity through a radio resource control layer message, and re-determine the parent node of the IAB node according to the parent node list.
在一示例中，donor CU通过RRC消息向IAB节点发送的父节点列表中至少包括下述之一：In an example, the parent node list sent by the donor CU to the IAB node through the RRC message includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，从所述宿主集中单元实体中获取的父节点列表，包括：In an example, the parent node list obtained from the unit entity in the host set includes:
连接所述宿主集中单元实体的donor DU和IAB节点，以及连接所述宿主集中单元实体相邻基站的donor DU和IAB节点。The donor DU and IAB nodes connected to the donor centralization unit entity, and the donor DU and IAB nodes connected to the neighboring base stations of the donor centralization unit entity.
在一示例中，所述宿主集中单元实体获知DU是否支持IAB功能的方式包括：In an example, the method for the host central unit entity to learn whether the DU supports the IAB function includes:
根据DU在F1建立请求消息或者gNB-DU配置更新消息或新的F1AP消息中指示所述DU支持IAB功能。According to the DU, it is indicated in the F1 establishment request message or the gNB-DU configuration update message or the new F1AP message that the DU supports the IAB function.
在一示例中，所述宿主集中单元实体生成或更新所述父节点列表的方式包括：In an example, the method of generating or updating the parent node list by the host central unit entity includes:
所述宿主集中单元实体从操作管理维护实体配置信息中获取支持IAB功能的基站列表，其中，所述支持IAB功能的基站列表中包括支持IAB功能的基站信息以及支持IAB功能的服务小区信息。The donor centralized unit entity obtains a list of base stations supporting the IAB function from the configuration information of the operation, management and maintenance entity, where the list of base stations supporting the IAB function includes information of base stations supporting the IAB function and information of serving cells supporting the IAB function.
在一示例中，所述宿主集中单元实体生成或更新所述父节点列表的方式包括：In an example, the method of generating or updating the parent node list by the host central unit entity includes:
所述宿主集中单元实体通过Xn建立请求消息或者NG-RAN节点配置更新信息，与相邻基站交互支持IAB功能的服务小区信息。The donor centralization unit entity interacts with the neighboring base station through the Xn establishment request message or the NG-RAN node configuration update information, and exchanges the information of the serving cell supporting the IAB function.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：在无线资源控制层建立请求消息中指示所述IAB节点支持IAB功能；在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is configured to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; when the donor centralization unit entity determines that the DU accessed by the IAB node does not support the IAB function, it re-determines the parent of the IAB node according to the auxiliary operation of the donor centralization unit entity node.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：在无线资源控制层建立请求消息中指示所述IAB节点支持IAB功能；接收所述宿主集中单元实体发送的无线资源控制层拒绝消息，断开与原有DU的连接，并重新确定所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is configured to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; receives the radio resource control layer rejection message sent by the donor centralization unit entity, disconnects the original DU, and re-determines the parent node of the IAB node.
在一示例中，无线资源控制层拒绝消息中至少包括如下之一：In an example, the radio resource control layer rejection message includes at least one of the following:
支持IAB的频率信息；Support IAB frequency information;
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：在无线资源控制层建立请求消息中指示所述IAB节点支持IAB功能；接收所述宿主集中单元实体在接收到RRC建立完成消息之后发送的无线资源控制层释放消息，断开与原有DU的连接，并重新确定所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is configured to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; receives the radio resource control layer release message sent by the donor centralization unit entity after receiving the RRC establishment complete message, disconnects the original DU, and re-determines the IAB node The parent node.
在一示例中，RRC释放消息中至少包括如下之一：In an example, the RRC release message includes at least one of the following:
支持IAB的频率信息；Support IAB frequency information;
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部 署场景为第二场景，第一父节点选择模块320设置为：在无线资源控制层建立请求消息中指示所述IAB节点支持IAB功能；接收所述宿主集中单元实体，在确定所述IAB节点初始接入过程结束之后，发送的无线资源控制层释放消息，断开与原有DU的连接，并重新确定所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; receiving the donor centralization unit entity, after determining the end of the initial access process of the IAB node, sends a radio resource control layer release message, disconnects the original DU, and Re-determine the parent node of the IAB node.
在一示例中，RRC释放消息中至少包括如下之一：In an example, the RRC release message includes at least one of the following:
支持IAB的频率信息；Support IAB frequency information;
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：在无线资源控制层建立请求消息中指示所述IAB节点支持IAB功能；根据所述宿主集中单元实体在确定所述IAB节点初始接入过程结束之后发送的切换指令，将与所述切换指令对应的支持IAB功能的父节点重新确定为所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; according to the handover instruction sent by the host central unit entity after determining that the initial access process of the IAB node ends, the parent node supporting the IAB function corresponding to the handover instruction is determined again Is the parent node of the IAB node.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：在无线资源控制层建立完成消息中指示所述IAB节点支持IAB功能；在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: establish a complete message in the radio resource control layer Indicates that the IAB node supports the IAB function; when the donor centralization unit entity determines that the DU accessed by the IAB node does not support the IAB function, it re-determines the parent of the IAB node according to the auxiliary operation of the donor centralization unit entity node.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：在无线资源控制层建立完成消息中指示所述IAB节点支持IAB功能；接收所述宿主集中单元实体发送的无线资源控制层释放消息，断开与原有DU的连接，并重新确定所述IAB节 点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: establish a complete message in the radio resource control layer Indicates that the IAB node supports the IAB function; receives the radio resource control layer release message sent by the donor centralization unit entity, disconnects the original DU, and re-determines the parent node of the IAB node.
在一示例中，RRC释放消息中至少包括如下之一：In an example, the RRC release message includes at least one of the following:
支持IAB的频率信息；Support IAB frequency information;
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：在无线资源控制层建立完成消息中指示所述IAB节点支持IAB功能；接收所述宿主集中单元实体，在确定所述IAB节点初始接入过程结束之后，发送的无线资源控制层释放消息，断开与原有DU的连接，并重新确定所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: establish a complete message in the radio resource control layer Indicates that the IAB node supports the IAB function; receiving the donor centralization unit entity, after determining the end of the initial access process of the IAB node, sends a radio resource control layer release message, disconnects the original DU, and Re-determine the parent node of the IAB node.
在一示例中，RRC释放消息中至少包括如下之一：In an example, the RRC release message includes at least one of the following:
支持IAB的频率信息；Support IAB frequency information;
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：在无线资源控制层建立完成消息中指示所述IAB节点支持IAB功能；根据所述宿主集中单元实体在确定所述IAB节点初始接入过程结束之后发送的切换指令，将与所述切换指令对应的支持IAB功能的父节点重新确定为所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: establish a complete message in the radio resource control layer Indicates that the IAB node supports the IAB function; according to the handover instruction sent by the host central unit entity after determining that the initial access process of the IAB node ends, the parent node supporting the IAB function corresponding to the handover instruction is determined again Is the parent node of the IAB node.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：在所述宿主集中单元实体通过初始上下文建立请求消息携带的IAB授权指示获知所述IAB节点支持IAB功能，并判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is configured to: pass through the host central unit entity When the IAB authorization indication carried in the initial context establishment request message learns that the IAB node supports the IAB function, and determines that the DU accessed by the IAB node does not support the IAB function, re-determine all the units according to the auxiliary operation of the donor central unit entity The parent node of the IAB node.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：在所述宿主集中单元实体通过初始上下文建立请求消息携带的IAB授权指示获知所述IAB节点支持IAB功能，并判断出所述IAB节点接入的DU不支持IAB功能时，接收所述宿主集中单元实体，在确定所述IAB节点初始接入过程结束之后，发送的无线资源控制层释放消息，断开与原有DU的连接，并重新确定所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is configured to: pass through the host central unit entity When the IAB authorization indication carried in the initial context establishment request message learns that the IAB node supports the IAB function, and determines that the DU accessed by the IAB node does not support the IAB function, the host central unit entity is received, and the IAB node is determined After the initial access process ends, the sent radio resource control layer release message disconnects the original DU, and re-determines the parent node of the IAB node.
在一示例中，RRC释放消息中至少包括如下之一：In an example, the RRC release message includes at least one of the following:
支持IAB的频率信息；Support IAB frequency information;
当前注册下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function currently registered;
所有下的支持IAB功能的小区标识；All the cell identities that support the IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为第二场景，第一父节点选择模块320设置为：在所述宿主集中单元实体通过初始上下文建立请求消息携带的IAB授权指示获知所述IAB节点支持IAB功能，并判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体在确定所述IAB节点初始接入过程结束之后发送的切换指令，将与所述切换指令对应的支持IAB功能的父节点重新确定为所述IAB节点的父节点。In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is configured to: pass through the host central unit entity When the IAB authorization indication carried in the initial context establishment request message learns that the IAB node supports the IAB function, and determines that the DU accessed by the IAB node does not support the IAB function, it is determined according to the donor central unit entity that the IAB node is initially The switching instruction sent after the end of the access process re-determines the parent node supporting the IAB function corresponding to the switching instruction as the parent node of the IAB node.
在一示例中，上述装置还包括第一父节点列表更新模块，设置为：根据操作管理维护实体发送的配置更新信息，对本地保存的父节点列表进行更新。In an example, the above-mentioned apparatus further includes a first parent node list update module, which is configured to update the locally stored parent node list according to configuration update information sent by the operation management and maintenance entity.
在一示例中，第一父节点列表更新模块，设置为：根据操作管理维护实体发送的IAB功能发生变化的父节点信息，对本地保存的父节点列表进行更新。In an example, the first parent node list update module is configured to update the locally saved parent node list according to the parent node information sent by the operation management and maintenance entity whose IAB function has changed.
在一示例中，第一父节点列表更新模块，设置为：根据操作管理维护实体发送的更新后的父节点列表，对本地保存的父节点列表进行更新。In an example, the first parent node list update module is configured to update the locally stored parent node list according to the updated parent node list sent by the operation management and maintenance entity.
在一示例中，OAM存储的父节点列表中至少包括下述之一：In an example, the parent node list stored by OAM includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
在一示例中，上述装置还包括第二父节点列表更新模块，设置为：根据宿主集中单元实体发送的父节点更新信息，对本地保存的父节点列表进行更新。In an example, the above-mentioned apparatus further includes a second parent node list update module, configured to update the locally stored parent node list according to the parent node update information sent by the unit entity in the host centralization.
在一示例中，第二父节点列表更新模块，设置为：根据所述宿主集中单元实体通过无线资源控制层消息或者F1建立响应消息或者gNB-CU配置更新消息或者新的F1AP消息发送的IAB功能变更的父节点信息，对本地存储的父节点列表进行更新。In an example, the second parent node list update module is configured to: according to the IAB function sent by the host central unit entity through a radio resource control layer message or an F1 establishment response message or a gNB-CU configuration update message or a new F1AP message The changed parent node information updates the locally stored parent node list.
在一示例中，第二父节点列表更新模块，设置为：根据所述宿主集中单元实体通过无线资源控制层消息或者F1建立响应消息或者gNB-CU配置更新消息或者新的F1AP消息发送的已更新父节点列表，对本地存储的父节点列表进行更新。In an example, the second parent node list update module is configured to: according to the updated information sent by the host central unit entity through a radio resource control layer message or an F1 establishment response message or a gNB-CU configuration update message or a new F1AP message Parent node list, update the locally stored parent node list.
在一示例中，第二父节点列表更新模块，设置为：根据RRC释放消息中携带的父节点列表对本地父节点列表进行更新。In an example, the second parent node list update module is configured to update the local parent node list according to the parent node list carried in the RRC release message.
在一示例中，第二父节点列表更新模块，设置为：根据RRC拒绝消息中携 带的父节点列表更新本地父节点列表。In an example, the second parent node list update module is configured to update the local parent node list according to the parent node list carried in the RRC rejection message.
在一示例中，donor CU中存储的父节点列表中至少包括下述之一：In an example, the parent node list stored in the donor CU includes at least one of the following:
当前注册PLMN下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the currently registered PLMN;
所有PLMN下的支持IAB功能的小区标识；All PLMN cell identities that support IAB function;
全球小区识别码；Global cell identification code;
物理小区标识。Physical cell identity.
本实施例还提供了父节点选择装置，图12为本申请提供的一种父节点选择装置的结构示意图，如图12所示，本申请实施例提供的一种应用于AMF实体中的父节点选择装置，可以集成在AMF实体中，该装置包括：This embodiment also provides a parent node selection device. FIG. 12 is a schematic structural diagram of a parent node selection device provided by this application. As shown in FIG. 12, an embodiment of the application provides a parent node applied to an AMF entity. The selection device can be integrated in the AMF entity. The device includes:
第二父节点选择模块420，设置为基于NG接口的切换，将IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示发送给与目标父节点对应的宿主集中单元实体或基站。The second parent node selection module 420 is configured to switch based on the NG interface and send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralized unit entity or base station corresponding to the target parent node.
本实施例提供的应用于AMF实体中的父节点选择装置用于实现如本申请实施例所述的应用于AMF实体中的父节点选择方法，本实施例提供的应用于AMF实体中的父节点选择装置实现原理和技术效果与本申请实施例所述的应用于AMF实体中的父节点选择方法类似，此处不再赘述。The device for selecting a parent node in an AMF entity provided in this embodiment is used to implement the method for selecting a parent node in an AMF entity as described in the embodiment of this application, and the parent node in an AMF entity provided in this embodiment The implementation principle and technical effect of the selection device are similar to the parent node selection method applied to the AMF entity described in the embodiment of the present application, and will not be repeated here.
在一示例中，第二父节点选择模块420设置为：将所述IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示，通过NGAP切换请求消息发送给与目标父节点对应的宿主集中单元实体或基站。In an example, the second parent node selection module 420 is configured to: send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the home set corresponding to the target parent node through an NGAP switching request message Unit entity or base station.
在一示例中，第二父节点选择模块420设置为：将所述IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示，通过路径切换请求确认消息，发送给与目标父节点对应的宿主集中单元实体或基站。In an example, the second parent node selection module 420 is configured to: send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the corresponding parent node via a path switch request confirmation message Donor central unit entity or base station.
本申请实施例提供了一种IAB节点，图13为本申请提供的一种IAB节点的结构示意图，如图13所示，本申请提供的IAB节点，包括：一个或多个处理器510和存储装置520；该IAB节点的处理器510可以是一个或多个，图13中以一个处理器510为例；存储装置520用于存储一个或多个程序；所述一个或多个程序被所述一个或多个处理器510执行，使得所述一个或多个处理器510实现如本发明实施例中所述的应用于IAB节点的父节点选择方法。The embodiment of this application provides an IAB node. FIG. 13 is a schematic structural diagram of an IAB node provided by this application. As shown in FIG. 13, the IAB node provided by this application includes: one or more processors 510 and storage The processor 510 of the IAB node may be one or more. One processor 510 is taken as an example in FIG. 13; the storage device 520 is used to store one or more programs; the one or more programs are One or more processors 510 execute, so that the one or more processors 510 implement the parent node selection method applied to the IAB node as described in the embodiment of the present invention.
IAB节点中的处理器510、存储装置520可以通过总线或其他方式连接，图13中以通过总线连接为例。The processor 510 and the storage device 520 in the IAB node may be connected through a bus or in other ways. In FIG. 13, the connection through a bus is taken as an example.
存储装置520作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例所述应用于IAB节点的父节点选择方法对应的程序指令/模块(例如，应用于IAB节点的父节点选择装置中的第一父节点选择模块320)。存储装置520可包括存储程序区和存储数据区，其中，存储程序区可存储操作***、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储装置520可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储装置520可进一步包括相对于处理器510远程设置的存储器，这些远程存储器可以通过网络连接至第一节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。The storage device 520, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as the program instructions/modules (for example, , Applied to the first parent node selection module 320 in the parent node selection device of the IAB node). The storage device 520 may include a storage program area and a storage data area. The storage program area may store an operating system and an application program required by at least one function; the storage data area may store data created according to the use of the device, and the like. In addition, the storage device 520 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some examples, the storage device 520 may further include a memory remotely provided with respect to the processor 510, and these remote memories may be connected to the first node through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
本申请实施例提供了一种接入管理功能实体，图14为本申请提供的一种接入管理功能实体的结构示意图，如图14所示，本申请提供的接入管理功能实体，包括：一个或多个处理器610和存储装置620；该接入管理功能实体的处理器610可以是一个或多个，图14中以一个处理器610为例；存储装置620用于存储一个或多个程序；所述一个或多个程序被所述一个或多个处理器610执行，使得所述一个或多个处理器610实现如本发明实施例中所述的应用于接入管理 功能实体的父节点选择方法。The embodiments of this application provide an access management function entity. FIG. 14 is a schematic structural diagram of an access management function entity provided by this application. As shown in FIG. 14, the access management function entity provided by this application includes: One or more processors 610 and storage devices 620; the processor 610 of the access management function entity may be one or more, and one processor 610 is taken as an example in FIG. 14; the storage device 620 is used to store one or more Program; The one or more programs are executed by the one or more processors 610, so that the one or more processors 610 implement the parent of the access management functional entity as described in the embodiment of the present invention Node selection method.
接入管理功能实体中的处理器610、存储装置620可以通过总线或其他方式连接，图14中以通过总线连接为例。The processor 610 and the storage device 620 in the access management function entity may be connected through a bus or other methods. In FIG. 14, the connection through a bus is taken as an example.
存储装置620作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例所述应用于接入管理功能实体的父节点选择方法对应的程序指令/模块(例如，应用于接入管理功能实体的父节点选择装置中的第一父节点选择模块420)。存储装置620可包括存储程序区和存储数据区，其中，存储程序区可存储操作***、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储装置620可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储装置620可进一步包括相对于处理器610远程设置的存储器，这些远程存储器可以通过网络连接至第一节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。The storage device 620, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as the program instructions corresponding to the parent node selection method applied to the access management functional entity as described in the embodiments of this application. Module (for example, the first parent node selection module 420 applied to the parent node selection device of the access management functional entity). The storage device 620 may include a storage program area and a storage data area. The storage program area may store an operating system and an application program required by at least one function; the storage data area may store data created according to the use of the device, and the like. In addition, the storage device 620 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some examples, the storage device 620 may further include memories remotely provided with respect to the processor 610, and these remote memories may be connected to the first node through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
本申请实施例还提供一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中任一所述的应用于IAB节点的父节点选择方法或本申请实施例中任一所述的应用于接入管理功能实体的父节点选择方法。The embodiment of the present application also provides a storage medium, the storage medium stores a computer program, and when the computer program is executed by a processor, it implements the parent node selection method or the parent node selection method applied to the IAB node in any of the embodiments of the present application. Any method for selecting a parent node applied to an access management functional entity described in the embodiments of the present application.
其中，应用于IAB节点的父节点选择方法包括：根据IAB节点的接入情况以及IAB节点接入网络的部署场景，确定所述IAB节点的父节点。Wherein, the parent node selection method applied to the IAB node includes: determining the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.
应用于接入管理功能实体的父节点选择方法包括：基于NG接口的切换，，将IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示发送给与目标父节点对应的宿主集中单元实体或基站。The parent node selection method applied to the access management functional entity includes: based on the handover of the NG interface, sending the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the host centralized unit entity corresponding to the target parent node Or base station.
以上所述，仅为本申请的示例性实施例而已，并非用于限定本申请的保护范围。The above are only exemplary embodiments of the present application, and are not used to limit the protection scope of the present application.
本领域内的技术人员应明白，术语用户终端涵盖任何适合类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。Those skilled in the art should understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。In general, the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
本申请的实施例可以通过实体装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。The embodiments of the present application may be implemented by executing computer program instructions by a data processor of a physical device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. Computer program instructions can be assembly instructions, instruction set architecture (Instruction Set Architecture, ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages Source code or object code.
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和***(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disk，CD))等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FGPA)以及基于多核处理器架构的处理器。The block diagram of any logical flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program can be stored on the memory. The memory can be of any type suitable for the local technical environment and can be implemented by any suitable data storage technology, such as but not limited to read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (ASICs) ), programmable logic devices (Field-Programmable Gate Array, FGPA), and processors based on multi-core processor architecture.
通过示范性和非限制性的示例，上文已提供了对本申请的示范实施例的详细描述。但结合附图和权利要求来考虑，对以上实施例的多种修改和调整对本领域技术人员来说是显而易见的，但不偏离本发明的范围。因此，本发明的恰当范围将根据权利要求确定。By way of exemplary and non-limiting examples, a detailed description of the exemplary embodiments of the present application has been provided above. However, considering the accompanying drawings and claims, various modifications and adjustments to the above embodiments are obvious to those skilled in the art, but they do not deviate from the scope of the present invention. Therefore, the proper scope of the present invention will be determined according to the claims.

Claims (32)

  1. 一种父节点选择方法，应用于自接入回传链路IAB节点中，包括：A method for selecting a parent node, which is applied to IAB nodes in the self-access backhaul link, includes:
    根据所述IAB节点的接入情况以及所述IAB节点接入网络的部署场景，确定所述IAB节点的父节点。Determine the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.
  2. 根据权利要求1所述的方法，其中，所述IAB节点包括分布网元DU和移动终端MT中的至少一种。The method according to claim 1, wherein the IAB node includes at least one of a distributed network element DU and a mobile terminal MT.
  3. 根据权利要求1所述的方法，其中，所述部署场景为第一场景至第六场景之一；The method according to claim 1, wherein the deployment scenario is one of the first scenario to the sixth scenario;
    所述第一场景为：所述IAB节点部署位置设定区域内包括IAB宿主分布单元实体donor DU，所述IAB节点和支持IAB功能的基站；The first scenario is: the IAB node deployment location setting area includes the IAB host distribution unit entity donor DU, the IAB node and the base station supporting the IAB function;
    所述第二场景为：所述IAB节点部署位置设定区域内包括IAB donor DU和不支持IAB功能的分布单元实体，所述不支持IAB功能的分布单元实体连接宿主集中单元实体donor CU；The second scenario is: the IAB node deployment location setting area includes an IAB donor DU and a distributed unit entity that does not support the IAB function, and the distributed unit entity that does not support the IAB function is connected to the donor centralized unit entity donor CU;
    所述第三场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，所述IAB节点和不支持IAB功能的基站，与所述不支持IAB功能的基站连接的接入管理功能实体支持IAB功能；The third scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station that does not support the IAB function, and the access management function entity connected to the base station that does not support the IAB function Support IAB function;
    所述第四场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，所述IAB节点和不支持IAB功能的基站，与所述不支持IAB功能的基站连接的接入管理功能实体不支持IAB功能；The fourth scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station that does not support the IAB function, and the access management function entity connected to the base station that does not support the IAB function Does not support IAB function;
    所述第五场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，所述IAB节点和不支持IAB功能的分布单元实体，与所述不支持IAB功能的分布单元实体连接的集中单元实体不支持IAB功能，与所述集中单元实体连接的接入管理功能实体支持IAB功能；The fifth scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the distributed unit entity that does not support the IAB function are connected to the distributed unit entity that does not support the IAB function. The unit entity does not support the IAB function, and the access management function entity connected to the centralized unit entity supports the IAB function;
    所述第六场景为：所述IAB节点部署位置设定区域内包括IAB donor DU，所述IAB节点和不支持IAB功能的分布单元实体，与所述不支持IAB功能的分布单元实体连接的集中单元实体不支持IAB功能，与所述集中单元实体连接的接入管理功能实体不支持IAB功能。The sixth scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the distributed unit entity that does not support the IAB function, and the centralized connection to the distributed unit entity that does not support the IAB function The unit entity does not support the IAB function, and the access management function entity connected to the centralized unit entity does not support the IAB function.
  4. 根据权利要求3所述的方法，其中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为所述第一场景至所述第六场景之一，所述确定所述IAB节点的父节点，包括：The method according to claim 3, wherein the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first scenario to the sixth scenario, and the Determining the parent node of the IAB node includes:
    在所述IAB节点预配置的父节点列表中选择所述IAB节点的父节点。The parent node of the IAB node is selected from the parent node list pre-configured by the IAB node.
  5. 根据权利要求3所述的方法，其中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为所述第一场景至所述第六场景之一，所述确定所述IAB节点的父节点，包括：The method according to claim 3, wherein the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first scenario to the sixth scenario, and the Determining the parent node of the IAB node includes:
    基于小区广播的***信息选择所述IAB节点的父节点。The parent node of the IAB node is selected based on the system information broadcast by the cell.
  6. 根据权利要求5所述的方法，其中，基于小区广播的***信息选择所述IAB节点的父节点，包括：The method according to claim 5, wherein the selecting the parent node of the IAB node based on the system information broadcast by the cell comprises:
    根据小区广播的***信息中是否包括IAB专有物理随机接入信道配置，判断所述IAB节点接入的小区是否支持IAB功能；或者，According to whether the system information broadcast by the cell includes the IAB dedicated physical random access channel configuration, determine whether the cell accessed by the IAB node supports the IAB function; or,
    根据小区广播的***信息中是否包括IAB专用***信息，判断所述IAB节点接入的小区是否支持IAB功能，其中，所述IAB专用***信息包括小区接入禁止信息、接纳控制参数、小区选择参数、小区重选参数中的至少一种；或者基于所述IAB节点或者IAB宿主分布单元实体广播的用于小区重选的***信息选择所述IAB节点的父节点，其中，所述用于小区重选的***信息包括下述至少之一：Determine whether the cell accessed by the IAB node supports the IAB function according to whether the system information broadcast by the cell includes IAB dedicated system information, where the IAB dedicated system information includes cell access barring information, admission control parameters, and cell selection parameters , At least one of the cell reselection parameters; or select the parent node of the IAB node based on the system information for cell reselection broadcast by the IAB node or the IAB host distribution unit entity, wherein the parent node for the cell reselection The selected system information includes at least one of the following:
    支持IAB功能的频率信息；Frequency information supporting IAB function;
    当前注册公共陆地移动网络下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the current registered public land mobile network;
    所有公共陆地移动网络下的支持IAB功能的小区标识；All public land mobile networks supporting IAB function cell identity;
    全球小区识别码；Global cell identification code;
    物理小区标识。Physical cell identity.
  7. 根据权利要求3所述的方法，其中，所述IAB节点的接入情况为初始接入，所述部署场景为所述第一场景至所述第六场景之一，所述确定所述IAB节点的父节点，包括：The method according to claim 3, wherein the access condition of the IAB node is initial access, the deployment scenario is one of the first scenario to the sixth scenario, and the determining the IAB node The parent node includes:
    在所述IAB节点接入小区的情况下，获取操作管理维护实体配置信息中的父节点列表；In the case that the IAB node accesses the cell, acquiring the parent node list in the configuration information of the operation management and maintenance entity;
    从所述父节点列表中选择所述IAB节点的父节点。Select the parent node of the IAB node from the parent node list.
  8. 根据权利要求3所述的方法，其中，所述IAB节点的接入情况为非初始接入，所述部署场景为所述第一场景至所述第六场景之一，所述确定所述IAB节点的父节点，包括：The method according to claim 3, wherein the access condition of the IAB node is non-initial access, the deployment scenario is one of the first scenario to the sixth scenario, and the determining the IAB The parent node of the node, including:
    在所述IAB节点从操作管理维护实体配置信息中已获取的父节点列表中，选择所述IAB节点的父节点。Select the parent node of the IAB node from the list of parent nodes that the IAB node has obtained from the configuration information of the operation management and maintenance entity.
  9. 根据权利要求3所述的方法，其中，所述IAB节点的接入情况为非初始接入，所述部署场景为所述第一场景至所述第六场景之一，所述确定所述IAB节点的父节点，包括：The method according to claim 3, wherein the access condition of the IAB node is non-initial access, the deployment scenario is one of the first scenario to the sixth scenario, and the determining the IAB The parent node of the node, including:
    在所述IAB节点从宿主集中单元实体中已获取的父节点列表中，选择所述IAB节点的父节点。Select the parent node of the IAB node from the list of parent nodes that the IAB node has obtained from the host centralized unit entity.
  10. 根据权利要求9所述的方法，其中，从所述宿主集中单元实体中获取所述父节点列表，包括：The method according to claim 9, wherein obtaining the list of parent nodes from the host centralized unit entity comprises:
    通过消息请求所述宿主集中单元实体发送所述父节点列表，以使所述宿主集中单元实体接收到请求之后向所述IAB节点发送所述父节点列表；或者，Request the host central unit entity to send the list of parent nodes through a message, so that the host central unit entity sends the list of parent nodes to the IAB node after receiving the request; or,
    接收所述宿主集中单元实体主动通过无线资源控制层消息发送的所述父节点列表。Receiving the parent node list actively sent by the donor centralization unit entity through a radio resource control layer message.
  11. 根据权利要求10所述的方法，其中，通过消息请求所述宿主集中单元实体发送所述父节点列表，包括：The method according to claim 10, wherein requesting the host central unit entity to send the list of parent nodes through a message comprises:
    通过无线资源控制层建立请求消息或者通过所述无线资源控制层建立完成消息或者通过无线资源控制层重配完成消息，请求所述宿主集中单元实体发送所述父节点列表；或者，Request the donor central unit entity to send the parent node list through a radio resource control layer establishment request message or through the radio resource control layer establishment complete message or through the radio resource control layer reconfiguration complete message; or,
    通过F1接口建立请求消息或gNB-DU配置更新消息或新的F1应用协议F1AP消息，请求所述宿主集中单元实体发送所述父节点列表；Request the host central unit entity to send the parent node list through an F1 interface establishment request message or a gNB-DU configuration update message or a new F1 application protocol F1AP message;
    接收所述宿主集中单元实体主动通过无线资源控制层消息发送的所述父节点列表，包括：Receiving the parent node list actively sent by the donor centralization unit entity through a radio resource control layer message includes:
    接收所述宿主集中单元实体主动通过无线资源控制层重配消息或者无线资源控制层释放消息或者无线资源控制层拒绝消息发送的所述父节点列表。Receiving the parent node list sent by the donor centralization unit entity actively through a radio resource control layer reconfiguration message or a radio resource control layer release message or a radio resource control layer rejection message.
  12. 根据权利要求3所述的方法，其中，所述IAB节点的接入情况为初始接入或非初始接入，所述部署场景为所述第二场景，所述确定所述IAB节点的父节点，包括：The method according to claim 3, wherein the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the determining the parent node of the IAB node ,include:
    在所述IAB节点接入小区的情况下，在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点。In the case that the IAB node accesses a cell, when the donor centralization unit entity determines that the DU accessed by the IAB node does not support the IAB function, the IAB node is re-determined according to the auxiliary operation of the donor centralization unit entity The parent node.
  13. 根据权利要求12所述的方法，其中，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：The method according to claim 12, wherein the re-determining the parent node of the IAB node according to the auxiliary operation of the host central unit entity comprises:
    根据所述宿主集中单元实体发送的切换指令，将与所述切换指令对应的支持IAB功能的父节点重新确定为所述IAB节点的父节点；或者，According to the switching instruction sent by the host central unit entity, the parent node supporting the IAB function corresponding to the switching instruction is re-determined as the parent node of the IAB node; or,
    接收所述宿主集中单元实体发送的无线资源控制层释放消息或者无线资源控制层拒绝消息，断开与原有DU的连接，并获取所述宿主集中单元实体通过无线资源控制层消息发送的父节点列表，根据所述父节点列表重新确定所述IAB节点的父节点。Receive the radio resource control layer release message or radio resource control layer rejection message sent by the donor centralized unit entity, disconnect the original DU, and obtain the parent node sent by the donor centralized unit entity through the radio resource control layer message List, and re-determine the parent node of the IAB node according to the parent node list.
  14. 根据权利要求4、7、8、9和13中任一项所述的方法，其中，所述父节点列表至少包括下述之一：The method according to any one of claims 4, 7, 8, 9 and 13, wherein the parent node list includes at least one of the following:
    当前注册公共陆地移动网络下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the current registered public land mobile network;
    所有公共陆地移动网络下的支持IAB功能的小区标识；All public land mobile networks supporting IAB function cell identity;
    全球小区识别码；Global cell identification code;
    物理小区标识。Physical cell identity.
  15. 根据权利要求9或13所述的方法，其中，从所述宿主集中单元实体中获取的父节点列表，包括：The method according to claim 9 or 13, wherein the parent node list obtained from the host central unit entity comprises:
    连接所述宿主集中单元实体的donor DU和IAB节点，以及连接所述宿主集中单元实体相邻基站的donor DU和IAB节点。The donor DU and IAB nodes connected to the donor centralization unit entity, and the donor DU and IAB nodes connected to the neighboring base stations of the donor centralization unit entity.
  16. 根据权利要求15所述的方法，其中，所述宿主集中单元实体判断所述IAB节点接入的DU是否支持IAB功能的方式包括：The method according to claim 15, wherein the manner in which the donor centralization unit entity determines whether the DU accessed by the IAB node supports IAB function comprises:
    根据所述IAB节点接入的DU在F1接口建立请求消息或者在gNB-DU配置更新消息或者新的F1AP消息中指示所述IAB节点接入的DU支持IAB功能。According to the DU accessed by the IAB node, it is indicated in the F1 interface establishment request message or the gNB-DU configuration update message or the new F1AP message that the DU accessed by the IAB node supports the IAB function.
  17. 根据权利要求15所述的方法，其中，所述宿主集中单元实体生成或更新所述父节点列表的方式包括：The method according to claim 15, wherein the method of generating or updating the parent node list by the host central unit entity comprises:
    所述宿主集中单元实体从操作管理维护实体配置信息中获取支持IAB功能的基站列表，其中，所述支持IAB功能的基站列表中包括支持IAB功能的基站信息以及支持IAB功能的服务小区信息；或者，The donor centralized unit entity obtains a list of base stations supporting IAB function from the configuration information of the operation, management and maintenance entity, wherein the list of base stations supporting IAB function includes information of base stations supporting IAB function and information of serving cells supporting IAB function; or ,
    所述宿主集中单元实体通过Xn接口建立请求消息或者下一代无线接入网NG-RAN节点配置更新信息，与相邻基站交互支持IAB功能的服务小区信息。The donor centralized unit entity interacts with neighboring base stations through the Xn interface establishment request message or the next-generation radio access network NG-RAN node configuration update information, and interacts with neighboring base stations to support the serving cell information of the IAB function.
  18. 根据权利要求12所述的方法，其中，所述在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：The method according to claim 12, wherein when the donor concentration unit entity determines that the DU accessed by the IAB node does not support the IAB function, the IAB is re-determined according to the auxiliary operation of the donor concentration unit entity The parent node of the node, including:
    在无线资源控制层建立请求消息中指示所述IAB节点支持IAB功能；Instruct the IAB node to support the IAB function in the radio resource control layer establishment request message;
    在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点。When the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, the parent node of the IAB node is re-determined according to the auxiliary operation of the donor centralized unit entity.
  19. 根据权利要求18所述的方法，其中，所述根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：The method according to claim 18, wherein the re-determining the parent node of the IAB node according to the auxiliary operation of the host central unit entity comprises:
    接收所述宿主集中单元实体发送的无线资源控制层拒绝消息，断开与原有DU的连接，并重新确定所述IAB节点的父节点；Receiving a radio resource control layer rejection message sent by the donor centralization unit entity, disconnecting the original DU, and re-determining the parent node of the IAB node;
    其中，无线资源控制层拒绝消息中至少包括如下之一：Wherein, the radio resource control layer rejection message includes at least one of the following:
    支持IAB的频率信息；Support IAB frequency information;
    当前注册公共陆地移动网络下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the current registered public land mobile network;
    所有公共陆地移动网络下的支持IAB功能的小区标识；All public land mobile networks supporting IAB function cell identity;
    全球小区识别码；Global cell identification code;
    物理小区标识。Physical cell identity.
  20. 根据权利要求12所述的方法，其中，所述在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：The method according to claim 12, wherein when the donor concentration unit entity determines that the DU accessed by the IAB node does not support the IAB function, the IAB is re-determined according to the auxiliary operation of the donor concentration unit entity The parent node of the node, including:
    在无线资源控制层建立完成消息中指示所述IAB节点支持IAB功能；Instruct the IAB node to support the IAB function in the radio resource control layer establishment complete message;
    在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点。When the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, the parent node of the IAB node is re-determined according to the auxiliary operation of the donor centralized unit entity.
  21. 根据权利要求20所述的方法，其中，所述根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：The method according to claim 20, wherein the re-determining the parent node of the IAB node according to the auxiliary operation of the host central unit entity comprises:
    接收所述宿主集中单元实体发送的无线资源控制层释放消息，断开与原有DU的连接，并重新确定所述IAB节点的父节点；Receiving the radio resource control layer release message sent by the donor centralization unit entity, disconnecting the original DU, and re-determining the parent node of the IAB node;
    无线资源控制层释放消息中至少包括下述之一：The radio resource control layer release message includes at least one of the following:
    支持IAB的频率信息；Support IAB frequency information;
    当前注册公共陆地移动网络下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the current registered public land mobile network;
    所有公共陆地移动网络下的支持IAB功能的小区标识；All public land mobile networks supporting IAB function cell identity;
    全球小区识别码；Global cell identification code;
    物理小区标识。Physical cell identity.
  22. 根据权利要求12所述的方法，其中，所述在宿主集中单元实体判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：The method according to claim 12, wherein when the donor concentration unit entity determines that the DU accessed by the IAB node does not support the IAB function, the IAB is re-determined according to the auxiliary operation of the donor concentration unit entity The parent node of the node, including:
    在所述宿主集中单元实体通过初始上下文建立请求消息携带的IAB授权指示，获知所述IAB节点支持IAB功能，并判断出所述IAB节点接入的DU不支持IAB功能时，根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点。When the donor centralization unit entity learns that the IAB node supports the IAB function through the IAB authorization indication carried in the initial context establishment request message, and determines that the DU accessed by the IAB node does not support the IAB function, according to the donor concentration The auxiliary operation of the unit entity redefines the parent node of the IAB node.
  23. 根据权利要求18、20和22任一项所述的方法，其中，所述根据所述宿主集中单元实体的辅助操作，重新确定所述IAB节点的父节点，包括：The method according to any one of claims 18, 20 and 22, wherein the re-determining the parent node of the IAB node according to the auxiliary operation of the entity of the host centralization unit comprises:
    接收所述宿主集中单元实体在确定所述IAB节点初始接入过程结束之后，发送的无线资源控制层释放消息，断开与原有DU的连接，并重新确定所述IAB节点的父节点；或者，Receiving the radio resource control layer release message sent by the donor centralized unit entity after determining that the initial access process of the IAB node is completed, disconnecting the original DU, and re-determining the parent node of the IAB node; or ,
    根据所述宿主集中单元实体在确定所述IAB节点初始接入过程结束之后，发送的切换指令，将与所述切换指令对应的支持IAB功能的父节点重新确定为所述IAB节点的父节点；Re-determining the parent node supporting the IAB function corresponding to the switching instruction as the parent node of the IAB node according to the handover instruction sent by the host central unit entity after determining that the initial access process of the IAB node is completed;
    其中，无线资源控制层释放消息中至少包括下述之一：Wherein, the radio resource control layer release message includes at least one of the following:
    支持IAB的频率信息；Support IAB frequency information;
    当前注册公共陆地移动网络下的支持IAB功能的小区标识；The identity of the cell supporting the IAB function under the current registered public land mobile network;
    所有公共陆地移动网络下的支持IAB功能的小区标识；All public land mobile networks supporting IAB function cell identity;
    全球小区识别码；Global cell identification code;
    物理小区标识。Physical cell identity.
  24. 根据权利要求1所述的方法，还包括：The method according to claim 1, further comprising:
    根据宿主集中单元实体发送的父节点更新信息，对本地保存的父节点列表进行更新。According to the parent node update information sent by the host central unit entity, the locally saved parent node list is updated.
  25. 根据权利要求24所述的方法，其中，所述根据所述宿主集中单元实体发送的父节点更新信息，对本地保存的父节点列表进行更新，包括：The method according to claim 24, wherein the updating the locally stored parent node list according to the parent node update information sent by the host centralized unit entity comprises:
    根据所述宿主集中单元实体通过无线资源控制层消息或者F1接口建立的响应消息或者gNB-CU配置更新消息或者新的F1AP消息发送的IAB功能变更的父节点信息，对本地保存的父节点列表进行更新；或者，According to the parent node information of the IAB function change sent by the host central unit entity through the radio resource control layer message or the response message established by the F1 interface or the gNB-CU configuration update message or the new F1AP message, perform the locally stored parent node list Update; or,
    根据所述宿主集中单元实体通过无线资源控制层消息或者F1接口建立的响应消息或者gNB-CU配置更新消息或者新的F1AP消息发送的已更新父节点列表，对本地保存的父节点列表进行更新。The locally saved parent node list is updated according to the updated parent node list sent by the host central unit entity through the radio resource control layer message or the response message established by the F1 interface or the gNB-CU configuration update message or the new F1AP message.
  26. 一种父节点选择方法，应用于接入管理功能实体中，包括：A method for selecting a parent node, applied to an access management function entity, includes:
    基于NG接口的切换，将自接入回传链路IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示发送给与目标父节点对应的宿主集中单元实体或基站。Based on the handover of the NG interface, the IAB authorization indication information of the self-access backhaul link IAB node or the IAB node indication of the IAB node is sent to the donor central unit entity or base station corresponding to the target parent node.
  27. 根据权利要求26所述的方法，其中，所述将所述IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示发送给与目标父节点对应的宿主集中单元实体或基站，包括：The method according to claim 26, wherein the sending the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralization unit entity or the base station corresponding to the target parent node comprises:
    将所述IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示，通过下一代应用协议NGAP切换请求消息或者通过路径切换请求确认消息，发送给与所述目标父节点对应的宿主集中单元实体或基站。Send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the host centralization unit corresponding to the target parent node through a next generation application protocol NGAP switching request message or a path switching request confirmation message Entity or base station.
  28. 一种父节点选择装置，应用于自接入回传链路IAB节点中，包括：A device for selecting a parent node, which is applied to a self-access backhaul link IAB node, includes:
    第一父节点选择模块，设置为根据所述IAB节点的接入情况以及所述IAB节点接入网络的部署场景，确定所述IAB节点的父节点。The first parent node selection module is configured to determine the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.
  29. 一种父节点选择装置，应用于接入管理功能实体中，包括：A parent node selection device, applied to an access management functional entity, includes:
    第二父节点选择模块，设置为基于NG接口的切换，将IAB节点的IAB授权指示信息或所述IAB节点的IAB节点指示发送给与目标父节点对应的宿主集中单元实体或基站。The second parent node selection module is configured to switch based on the NG interface and send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralized unit entity or base station corresponding to the target parent node.
  30. 一种IAB节点，包括：An IAB node, including:
    至少一个处理器；At least one processor;
    存储装置，设置为存储至少一个程序；The storage device is set to store at least one program;
    所述至少一个程序被所述至少一个处理器执行时，使得所述至少一个处理器实现如权利要求1-25中任一所述的父节点选择方法。When the at least one program is executed by the at least one processor, the at least one processor realizes the method for selecting a parent node according to any one of claims 1-25.
  31. 一种接入管理功能实体，包括：An access management functional entity, including:
    至少一个处理器；At least one processor;
    存储装置，设置为存储至少一个程序；The storage device is set to store at least one program;
    所述至少一个程序被所述至少一个处理器执行时，使得所述至少一个处理器实现如权利要求26或27所述的父节点选择方法。When the at least one program is executed by the at least one processor, the at least one processor implements the method for selecting a parent node according to claim 26 or 27.
  32. 一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时，实现权利要求1-25中任一所述的父节点选择方法，或者，实现如权利要求26或27所述的父节点选择方法。A storage medium storing a computer program, and when the computer program is executed by a processor, the method for selecting a parent node according to any one of claims 1-25 is realized, or the method for selecting a parent node according to any one of claims 1-25, or the method for selecting a parent node as described in claim 26 or 27 is realized. The parent node selection method.
PCT/CN2020/108483 2019-08-15 2020-08-11 Parent node selection method and apparatus, device and medium WO2021027817A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910755605.4A CN110536377A (en) 2019-08-15 2019-08-15 Father node selection method, device, equipment and medium
CN201910755605.4 2019-08-15

Publications (1)

Publication Number Publication Date
WO2021027817A1 true WO2021027817A1 (en) 2021-02-18

Family

ID=68663540

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/108483 WO2021027817A1 (en) 2019-08-15 2020-08-11 Parent node selection method and apparatus, device and medium

Country Status (2)

Country Link
CN (1) CN110536377A (en)
WO (1) WO2021027817A1 (en)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536377A (en) * 2019-08-15 2019-12-03 中兴通讯股份有限公司 Father node selection method, device, equipment and medium
WO2021118253A1 (en) * 2019-12-10 2021-06-17 엘지전자 주식회사 Method for iab multiplexing and timing relationship, and node using method
CN112996061B (en) * 2019-12-12 2022-07-01 维沃移动通信有限公司 Cell reconfiguration method, network control node and mobile IAB node
US11889540B2 (en) 2020-03-19 2024-01-30 Qualcomm Incorporated Interference-aware scheduling during transition instances in an integrated access and backhaul network
US20220312311A1 (en) * 2020-04-08 2022-09-29 Apple Inc. Cell selection for iab nodes
WO2021249153A1 (en) * 2020-06-12 2021-12-16 华为技术有限公司 Relay communication method and related device
CN113810215A (en) * 2020-06-12 2021-12-17 华为技术有限公司 Relay communication method and related equipment
CN113905421B (en) * 2020-06-22 2023-05-26 大唐移动通信设备有限公司 Cell selection method and device
WO2022027389A1 (en) * 2020-08-05 2022-02-10 Nokia Shanghai Bell Co., Ltd. Mechanism for cell identity management
CN114079871B (en) * 2020-08-13 2023-02-03 维沃移动通信有限公司 Information control method, device and base station
CN116508356A (en) * 2020-11-06 2023-07-28 华为技术有限公司 Key generation method and device
WO2023010367A1 (en) * 2021-08-04 2023-02-09 富士通株式会社 Terminal device transfer method, apparatus, and system
CN115604778B (en) * 2022-11-28 2023-03-10 广州世炬网络科技有限公司 Node access method, device, equipment and storage medium

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536377A (en) * 2019-08-15 2019-12-03 中兴通讯股份有限公司 Father node selection method, device, equipment and medium

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10206232B2 (en) * 2016-09-29 2019-02-12 At&T Intellectual Property I, L.P. Initial access and radio resource management for integrated access and backhaul (IAB) wireless networks
CN109257212B (en) * 2018-09-10 2021-09-03 中信科移动通信技术股份有限公司 IAB base station access method

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536377A (en) * 2019-08-15 2019-12-03 中兴通讯股份有限公司 Father node selection method, device, equipment and medium

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CATT: "Parent node selection", 3GPP DRAFT; R3-192061 PARENT NODE SELECTION_V3, vol. RAN WG3, 15 April 2019 (2019-04-15), Xian, China, pages 1 - 2, XP051712340 *
HUAWEI; HISILICON: "R2-1906071 Cell Selection and Reselection of IAB Node", 3GPP DRAFT; R2-1906071 CELL SELECTION AND RESELECTION OF IAB NODE, vol. RAN WG2, 3 May 2019 (2019-05-03), Reno, USA, pages 1 - 3, XP051710398 *
QUALCOMM INCORPORATED: "Support for NR IAB", 3GPP DRAFT; S2-1907203-SUPPORT FOR NR_IAB V6, vol. SA WG2, 18 June 2019 (2019-06-18), Sapparo, Japan, pages 1 - 8, XP051752172 *
SAMSUNG: "Overview on IAB node setup (SA)", 3GPP DRAFT; R3-190434_IABSTARTUP(SA)_V1.0, vol. RAN WG3, 15 February 2019 (2019-02-15), Athens, Greece, pages 1 - 4, XP051604375 *

Also Published As

Publication number Publication date
CN110536377A (en) 2019-12-03

Similar Documents

Publication Publication Date Title
WO2021027817A1 (en) Parent node selection method and apparatus, device and medium
WO2021196799A1 (en) Cell management method and apparatus, device and storage medium
KR102495714B1 (en) Method and device for accessing target cell
WO2020030146A1 (en) Network access method and apparatus, network device, and computer readable storage medium
EP4090078A2 (en) Session management method and related devices
WO2018028342A1 (en) Service processing method, apparatus, system, base station, terminal and core network element
US11622398B2 (en) Methods and devices for connecting a wireless communication device to a user plane in a wireless communication network
WO2019001204A1 (en) Slice selection method and apparatus
US20190159024A1 (en) Implementing Radio Access Network Slicing in a Mobile Network
US9544840B2 (en) Distributed method for client optimization
US20190200266A1 (en) Access network switching method in heterogeneous radio access network and user equipment performing the same
KR102469973B1 (en) Communication method and device
US11330489B2 (en) Apparatus, method and computer program
US11140592B2 (en) Method and apparatus for selecting radio access network device
WO2017012299A1 (en) Selection method and device for cell reestablishment in network sharing
KR102327021B1 (en) Method and apparatus for providing service through network slice
CN111770475A (en) Time delay obtaining method and device and optimization method and device
JP2022531189A (en) Communication methods, communication equipment, and communication systems
JP2023524903A (en) Communication method and device
US9549423B2 (en) Method and device for increasing gateway capacity in LTE mode Femto cell system
WO2021142804A1 (en) Communication method and related device
WO2021168647A1 (en) Method for providing network slice, and communication apparatus
WO2010105410A1 (en) Method, device and system for setting up radio bearer
US11076321B2 (en) Selecting 5G non-standalone architecture capable MME during registration and handover
KR20210078549A (en) Data forwarding method, apparatus, master base station and secondary base station

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20851803

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 20851803

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 28/09/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20851803

Country of ref document: EP

Kind code of ref document: A1