Parent node selection method, device, equipment and medium

Abstract

The present application proposes a parent node selection method, device, equipment and medium. The parent node selection method is applied to an IAB node in an access backhaul link, and includes: determining the parent node of the IAB node according to the access status of the IAB node and the deployment scenario of the IAB node access network.

Description

Technical Field

[0001] The present application relates to the field of wireless communications, and in particular to a parent node selection method, device, equipment and medium. Background Art

[0002] The high transmission speed of 5G network mainly lies in the use of millimeter waves. However, millimeter waves have large attenuation in the air and weak diffraction ability. For this reason, the Integrated Access and Backhaul links (IAB) technology is proposed. The integrated access backhaul link includes a wireless access link and a wireless backhaul link. The wireless access link is a communication link between the UE (User Equipment) and the IAB node. The wireless backhaul link is a communication link between IAB nodes and is used for data backhaul. Therefore, the IAB node does not need a wired transmission network for data backhaul. When the IAB node accesses the network, the IAB node may be connected to a DU (Distributed Unit) or base station that does not support the IAB function. At this time, the IAB node cannot realize its IAB function. Summary of the invention

[0003] The present application provides a parent node selection method, apparatus, device and medium to ensure that an IAB node can implement its IAB function.

[0004] In a first aspect, an embodiment of the present application provides a parent node selection method, which is applied to an IAB node, including:

[0005] According to the access status of the IAB node and the deployment scenario of the IAB node accessing the network, the parent node of the IAB node is determined.

[0006] In a second aspect, an embodiment of the present application provides a parent node selection method, which is applied to an access management function entity, including:

[0007] After the IAB node determines the target parent node of the IAB node according to the access status of the IAB node and the deployment scenario of the IAB node access network, the IAB node sends 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.

[0008] 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 by comprising:

[0009] The first parent node selection module is used to determine the parent node of the IAB node according to the access status of the IAB node and the deployment scenario of the IAB node accessing the network.

[0010] 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, including:

[0011] The second parent node selection module is used to 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 after determining the target parent node of the IAB node according to the access status of the IAB node and the deployment scenario of the IAB node access network.

[0012] In a fifth aspect, an embodiment of the present application provides an IAB node, comprising: one or more processors; a storage device for storing one or more programs; when the one or more programs are executed by the one or more processors, 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.

[0013] In a sixth aspect, an embodiment of the present application provides a storage medium storing a computer program, which, when executed by a processor, implements a parent node selection method applied to an IAB node as described in any embodiment of the present application.

[0014] In the seventh aspect, an embodiment of the present application provides an access management functional entity, including: one or more processors; a storage device for storing one or more programs; when the one or more programs are executed by the one or more processors, 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.

[0015] In an eighth aspect, an embodiment of the present application provides a storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the parent node selection method applied to the access management function entity as described in any embodiment of the present application.

[0016] With regard to the above embodiments and other aspects of the present application and their implementation, further description is provided in the accompanying drawings, detailed description and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 This is a diagram of network IAB deployment;

[0018] Figure 2 Schematic diagram of IAB deployment for a network with CU and DU separated;

[0019] Figure 3 A schematic diagram of a parent node selection method provided in this application;

[0020] Figure 4 A schematic diagram of the first IAB node deployment scenario provided for this application;

[0021] Figure 5 A schematic diagram of the second IAB node deployment scenario provided for this application;

[0022] Figure 6 A schematic diagram of the third IAB node deployment scenario provided for this application;

[0023] Figure 7 A schematic diagram of the fourth IAB node deployment scenario provided for this application;

[0024] Figure 8 A schematic diagram of the fifth IAB node deployment scenario provided for this application;

[0025] Fig. 9 A schematic diagram of the sixth IAB node deployment scenario provided for this application;

[0026] Fig.10 A schematic diagram of a parent node selection method provided in this application;

[0027] Fig.11 A schematic diagram of the structure of a parent node selection device provided by the present application;

[0028] Fig.12 A schematic diagram of the structure of a parent node selection device provided by the present application;

[0029] Fig.13 A schematic diagram of the structure of an IAB node provided in this application;

[0030] Fig.14 A schematic diagram of the structure of an access management functional entity provided for this application. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solution and advantages of the present application more clear, the embodiments of the present application will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily without conflict.

[0032] Before describing the embodiments provided in the present application, IAB is firstly explained exemplarily.

[0033] An example of a network with IAB deployed is Figure 1As shown, the figure includes node 10, node 20 and node 30, wherein node 10 is connected to the core network by wire, for example, node 10 is connected to the core network by optical fiber 11, and node 20 and node 30 send and receive data to the core network through 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. In an IAB network, an access node that supports wireless access and wirelessly backhauls data is called an IAB node, for example Figure 1 Node 20 and node 30 in the IAB network. In the IAB network, the access node that provides wireless backhaul function for the IAB node so that the UE can connect to the core network is called the IAB donor. Figure 1 Node 10 in the network. Taking data uplink transmission as an example, node 20 can send data received from UE to node 10 via a wireless backhaul link, and access node 10 then sends UE data to the core network element. Taking data downlink transmission as an example, the core network element sends the UE data packet to node 10, and access node 10 then sends UE data to node 20 via a wireless backhaul link, and then access node 20 sends UE data to UE via an access link.

[0034] In addition, supporting the separate deployment of CU (Centralized Unit) and DU (Distributed Unit) is an important technical feature of NR (New Radio). Therefore, the IAB function also needs to be supported in the scenario where CU and DU are separately deployed. Figure 2 This is a diagram of IAB deployment in a network with separate CU and DU. Figure 2 As shown, the IAB node can have DU similar functions and MT (Mobile Terminal) similar functions, MT similar functions are also UE similar functions, and the IAB node accesses two parent IAB nodes through dual connections, that is, the IAB node accesses parent IAB node 1 and parent IAB node 2 through dual connections respectively.

[0035] When an IAB node accesses the network, there may be a DU or base station near the IAB node that does not support the IAB function. 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.

[0036] In an exemplary embodiment, Figure 3A flow chart of a parent node selection method provided by the present application. The method can be applied to the case where an IAB selects a parent node supporting the IAB function when accessing a network. The method can be performed by a parent node selection device applied to an 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.

[0037] like Figure 3 As shown, the present application provides a parent node selection method applied to an IAB node, comprising:

[0038] S120: Determine a parent node of the IAB node according to the access status of the IAB node and the deployment scenario of the IAB node accessing the network.

[0039] An IAB node of an IAB node is called a child IAB node of the IAB node, and a DU or base station supporting the IAB function to which an IAB node is connected as a connection identity is called a parent IAB node of the IAB node.

[0040] The network access status of IAB nodes can be divided into initial access and non-initial access. There are many deployment scenarios for IAB node access to the network. Specifically, it can be divided according to whether the DU entity and base station in the deployment location setting area support the IAB function, and 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. It can also be divided according to whether the CU entity connected to the DU entity that does not support the IAB function supports the IAB function, and whether the further connected AMF entity supports the IAB function.

[0041] Therefore, when the IAB node selects a parent node that supports the IAB function, it can be determined in combination with 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 a parent node may be the same or different.

[0042] The IAB node may be a DU entity or a MT.

[0043] The present application provides a parent node selection method, which determines the parent node of the IAB node according to the access status of the IAB node and the deployment scenario of the IAB node accessing the network when the IAB node accesses the network, effectively solves the problem of how the IAB node selects the parent node, ensures that the parent node selected by the IAB node supports the IAB function, and further ensures the IAB function of the IAB node, thereby achieving the effect of serving other child IAB nodes and UEs.

[0044] Based on the above embodiment, a variant embodiment of the above embodiment is proposed. It should be noted that in order to make the description concise, only the differences from the above embodiment are described in the variant embodiment.

[0045] In an example, deployment scenarios of IAB nodes accessing a network may include the following six deployment scenarios.

[0046] The first scenario is that the IAB node deployment location setting area includes an IAB donor DU, an IAB node and a base station supporting the IAB function.

[0047] like Figure 4 As shown, the host centralized unit entity (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 backhaul link (BH link), wherein the donor CU 101, the donor DU 102 and the IAB node 103 all support the IAB function. The IAB node 104 refers to a node to 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 deployment location support the IAB function.

[0048] 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 a host centralized unit entity donor CU.

[0049] like Figure 5 As shown, donor CU 101 is connected to donor DU 102 through F1 interface, and is connected to normal distribution unit entity (normal DU) 105, and donor DU 102 is connected to IAB node 103 through BH link, wherein the host donorCU 101, donor DU 102 and IAB node 103 all support IAB function, and normal distribution unit entity 105 does not support IAB function. IAB node 104 refers to a node to be deployed in the IAB network corresponding to the second scenario, such as an IAB-MT that is undergoing initial access, and there are other IAB nodes 103, donor DU 102 that supports IAB function, and normal DU 105 that does not support IAB function near its deployment location.

[0050] The third scenario is that the IAB node deployment location setting area includes an IAB donor DU, an IAB node and a base station that does not support the IAB function, and an access management function entity connected to the base station supports the IAB function.

[0051] like Figure 6 As shown, AMF 107 is connected to donor CU 101 and base station (gNB) 106 through an NG interface. The AMF 107 connected to donor CU 101 and the AMF 107 connected to gNB 106 can be the same AMF or different AMFs. Figure 6 Different examples are used in the figure. Donor CU 101 is connected to donor DU 102 through F1 interface, and donor DU 102 is connected to IAB node 103 through BH link, wherein AMF 107, donor CU 101, donor DU 102 and IAB node 103 all support IAB function, while gNB 106 does not support IAB function. IAB node 104 refers to a node to 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, donor DU 102 that supports IAB function, and gNB 106 that does not support IAB function near its deployment location, but AMF 107 connected to gNB 106 supports IAB function, and there are network elements supporting IAB function in other core network elements connected to AMF 107.

[0052] The fourth scenario is that the IAB node deployment location setting area includes an IAB donor DU, an IAB node and a base station that does not support the IAB function, and an access management function entity connected to the base station does not support the IAB function.

[0053] like Figure 7As shown, AMF 107 is connected to donor CU 101 via NG interface, and AMF 108 is connected to gNB 106 via NG interface. Donor CU 101 is connected to donor DU 102 via F1 interface, and donor DU 102 is connected to IAB node 103 via BH link, wherein AMF 107, donor CU 101, donor DU 102 and IAB node 103 all support IAB function, while AMF 108 and gNB 106 do not support IAB function. IAB node 104 refers to a node to be deployed in the IAB network corresponding to the fourth scenario, such as an IAB-MT that is undergoing initial access, and there are other IAB nodes 103, donor DU 102 that supports IAB function, and gNB 106 that does not support IAB function near its deployment location, and AMF 108 connected to gNB 106 that does not support IAB function also does not support IAB function.

[0054] The fifth scenario is: the IAB node deployment location setting area includes an IAB donor DU, an IAB node and a distribution unit entity that does not support the IAB function, a centralized unit entity connected to the distribution unit entity that does not support the IAB function does not support the IAB function, and an access management function entity connected to the centralized unit entity supports the IAB function.

[0055] like Figure 8 As shown, AMF 107 is connected to donor CU 101 and normal CU 109 through an NG interface. The AMF 107 connected to donor CU 101 and the AMF 107 connected to normal CU 109 may be the same AMF or different AMFs. Figure 8The difference is shown as an example. The donor CU 101 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 normalDU 105 through the F1 interface, wherein the AMF 107, the donor CU 101, the donor DU 102 and the IAB node 103 all support the IAB function, while the normal CU 109 and the normal DU 105 do not support the IAB function. The IAB node 104 refers to a node to be deployed in the IAB network corresponding to the fifth scenario, for example, an IAB-MT that is undergoing initial access. There are other IAB nodes 103, donor DU 102 that supports the IAB function, and normal DU 105 that does not support the IAB function near its deployment location. The normal CU 109 connected to the normal DU 105 does not support the IAB function either, but the AMF 107 connected to the normal CU 109 supports the IAB function, and other core network elements connected to the AMF 107 include network elements that support the IAB function.

[0056] The sixth scenario is: the IAB node deployment location setting area includes an IAB donor DU, an IAB node and a distribution unit entity that does not support the IAB function, a centralized unit entity connected to the distribution unit entity that does not support the IAB function does not support the IAB function, and an access management function entity connected to the centralized unit entity does not support the IAB function.

[0057] like Fig. 9As shown, AMF 107 is connected to donor CU 101 through the NG interface, and AMF 108 is connected to normal CU 109 through the NG interface. Donor CU 101 is connected to donor DU 102 through the F1 interface, donor DU 102 is connected to IAB node 103 through BHlink, and normal CU 109 is connected to normal DU 105 through the F1 interface, wherein AMF 107, donor CU 101, donor DU 102 and IAB node 103 all support the IAB function, while AMF 108, normal CU 109 and normal DU 105 do not support the IAB function. The IAB node 104 refers to a node to be deployed in the IAB network corresponding to the sixth scenario, for example, an IAB-MT that is undergoing initial access. There are other IAB nodes 103, donor DU 102 that supports the IAB function, and normal DU 105 that does not support the IAB function near its deployment location. Moreover, the normal CU 109 connected to the normal DU 105 that does not support the IAB function does not support the IAB function either. At the same time, the AMF 108 connected to the normal CU 109 does not support the IAB function either.

[0058] 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 scenario to the sixth scenario, and the determining the parent node of the IAB node includes:

[0059] A parent node of the IAB node is selected from a parent node list preconfigured for the IAB node.

[0060] When the IAB node is initially accessed, in the case where the deployment scenario is any one of the first scenario, the second scenario, the third scenario, the fourth scenario, the fifth scenario and the sixth scenario, the IAB node may have a preconfigured parent node list, and may then select one from its preconfigured parent node list as its parent node.

[0061] When the IAB node is not initially accessed, when the deployment scenario is any one of the first scenario, the second scenario, the third scenario, the fourth scenario, the fifth scenario and the sixth scenario, the IAB node may also have a preconfigured parent node list, and then may also select one from its preconfigured parent node list as its parent node.

[0062] 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.

[0063] In one example, the parent node list preconfigured by the IAB node includes at least one of the following:

[0064] The cell ID of the currently registered public land mobile network (PLMN) that supports the IAB function;

[0065] Identifiers of cells supporting IAB function in all PLMNs;

[0066] Global Cell Identifier;

[0067] Physical cell identifier.

[0068] In one example, the method further includes: when the IAB node accesses a cell, judging whether the distributed unit entity or base station to which the IAB node accesses supports the IAB function according to whether the radio resource control layer (Radio Resource Control, RRC) reconfiguration message contains a backhaul adaptation protocol layer configuration message.

[0069] Regardless of whether the IAB node is in initial access or non-initial access, after the IAB node accesses any appropriate cell, it can be determined whether the distributed unit entity or base station it accesses supports the IAB function according to whether the backhaul adaptation protocol layer configuration message is included in the RRC reconfiguration message. When the RRC reconfiguration message includes the backhaul adaptation 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 adaptation protocol layer configuration message, the distributed unit entity or base station accessed by the IAB node does not support the IAB function.

[0070] 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 scenario to the sixth scenario, and the determining the parent node of the IAB node includes:

[0071] The parent node of the IAB node is selected based on the system information broadcast by the cell.

[0072] When the IAB node is initially accessed, when the deployment scenario is any one of the first scenario, the second scenario, the third scenario, the fourth scenario, the fifth scenario and the sixth scenario, the IAB node can select a node as its parent node based on the system information broadcast by the received cell when accessing the network.

[0073] When the IAB node is not in the initial access, when the deployment scenario is any of the first scenario, the second scenario, the third scenario, the fourth scenario, the fifth scenario and the sixth scenario, the IAB node can also select a node as its parent node according to the system information broadcast by the received cell when accessing the network.

[0074] In one example, selecting the parent node of the IAB node based on the system information broadcast by the cell includes:

[0075] According to whether the system information broadcast by the cell includes the IAB-specific physical random access channel (PRACH) configuration, it is determined whether the cell accessed by the IAB node supports the IAB function.

[0076] When the system information broadcast by the cell received by the IAB node includes the IAB-specific PRACH configuration, it can be determined that the cell accessed by the IAB node supports the IAB function; when the system information broadcast by the cell received by the IAB node does not include the IAB-specific PRACH configuration, it can be determined that the cell accessed by the IAB node does not support the IAB function. Therefore, according to this implementation, it can also be ensured that the selected parent node supports the IAB function.

[0077] In one example, selecting the parent node of the IAB node based on the system information broadcast by the cell includes:

[0078] Whether the cell accessed by the IAB node supports the IAB function is determined according to whether the system information broadcast by the cell includes IAB dedicated system information, wherein the IAB dedicated system information includes at least one of cell access prohibition information, admission control parameters, cell selection parameters, and cell reselection parameters.

[0079] 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 cell received by the IAB node does not include the IAB dedicated system information, it can be determined that the cell accessed by the IAB node does not support the IAB function. Therefore, according to this implementation, it can also be ensured that the selected parent node supports the IAB function.

[0080] In one example, selecting the parent node of the IAB node based on the system information broadcast by the cell includes:

[0081] The parent node of the IAB node is selected based on the system information for cell reselection broadcasted by the IAB node or the IAB host distribution unit entity.

[0082] The IAB node may receive system information for cell reselection broadcasted by other IAB nodes or IAB donor CUs, wherein the system information for cell reselection broadcasted by the IAB nodes or IAB donor CUs includes at least one of the following:

[0083] Frequency information supporting IAB function;

[0084] The cell ID supporting the IAB function under the currently registered PLMN;

[0085] Identifiers of cells supporting IAB function in all PLMNs;

[0086] Global Cell Identifier;

[0087] Physical cell identifier.

[0088] In an example, 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 parent node of the IAB node includes:

[0089] When the IAB node accesses a cell, a parent node list in the operation management and maintenance entity configuration information is obtained; and a parent node of the IAB node is selected from the parent node list.

[0090] When the IAB node is initially accessed, when the deployment scenario is any of the first scenario, the second scenario, the third scenario, the fourth scenario, the fifth scenario and the sixth scenario, after the IAB node accesses any suitable cell, it establishes a connection with the OAM and obtains the OAM configuration information. The OAM configuration information includes a parent node list. The IAB node can select a node in the parent node list as its parent node.

[0091] The parent nodes in the parent node list obtained in the OAM configuration information all support the IAB function.

[0092] In one example, the parent node list obtained in the OAM configuration information includes at least one of the following:

[0093] The cell ID supporting the IAB function under the currently registered PLMN;

[0094] Identifiers of cells supporting IAB function in all PLMNs;

[0095] Global Cell Identifier;

[0096] Physical cell identifier.

[0097] In an example, 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 parent node of the IAB node includes:

[0098] The parent node of the IAB node is selected from the parent node list obtained from the operation management and maintenance entity configuration information at the IAB node.

[0099] When the IAB node is not initially accessed, in the case where the deployment scenario is any one of the first scenario, the second scenario, the third scenario, the fourth scenario, the fifth scenario and the sixth scenario, the IAB node has obtained the parent node list from OAM and stored it locally in the IAB node, and then a node can be selected from the parent node list obtained from OAM as its parent node.

[0100] Among them, all nodes in the parent node list obtained from OAM support the IAB function.

[0101] In one example, the parent node list obtained from the OAM includes at least one of the following:

[0102] The cell ID supporting the IAB function under the currently registered PLMN;

[0103] Identifiers of cells supporting IAB function in all PLMNs;

[0104] Global Cell Identifier;

[0105] Physical cell identifier.

[0106] In an example, 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 parent node of the IAB node includes:

[0107] The IAB node selects a parent node of the IAB node from a parent node list obtained from a host centralized unit entity.

[0108] When the IAB node is not initially accessed, in the case where the deployment scenario is any one of the first scenario, the second scenario, the third scenario, the fourth scenario, the fifth scenario and the sixth scenario, the IAB node has obtained the parent node list from the donor CU and stored it locally in the IAB node, and then can select a node from the parent node list obtained from the donor CU as its parent node.

[0109] The nodes in the parent node list obtained from the donor CU all support the IAB function. The parent node list stored in the donor CU may specifically include at least one of an IAB donor DU, an IAB node, and a gNB that supports the IAB function.

[0110] In one example, the parent node list obtained from the donor CU includes at least one of the following:

[0111] The cell ID supporting the IAB function under the currently registered PLMN;

[0112] Identifiers of cells supporting IAB function in all PLMNs;

[0113] Global Cell Identifier;

[0114] Physical cell identifier.

[0115] In one example, obtaining a parent node list from the host centralized unit entity includes:

[0116] The host centralized unit entity is requested to send a parent node list through a message, so that the host centralized unit entity sends the parent node list to the IAB node after receiving the request.

[0117] 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, such as a radio resource control layer request message, to request the donor CU to send the parent node list to the IAB node. After receiving the RRC request message, the donor CU sends the parent node list to the IAB node.

[0118] In one example, requesting the host centralized unit entity to send a parent node list through a message includes:

[0119] The host centralized unit entity is requested to send a parent node list through a radio resource control layer establishment request message, a radio resource control layer establishment completion message, or a radio resource control layer reconfiguration completion message.

[0120] 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 wireless resource control layer establishment request (RRCSetupRequest) message, or request the donor CU to send the parent node list through the wireless resource control layer establishment completion (RRCSetupComplete) message, or request the donor CU to send the parent node list through the wireless resource control layer reconfiguration completion (RRCReconfigurationComplete) message.

[0121] In one example, requesting the host centralized unit entity to send a parent node list through a message includes:

[0122] The host centralized unit entity is requested to send a parent node list through an F1 establishment request message or a GNB-DU configuration update message or a new F1AP message.

[0123] 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 an F1 establishment request message, or request the donor CU to send the parent node list through a GNB-DU configuration update message, or request the donor CU to send the parent node list through a new F1AP message.

[0124] In one example, obtaining a parent node list from the host centralized unit entity includes:

[0125] Receive a parent node list actively sent by the host centralized unit entity through a radio resource control layer message.

[0126] The parent node list sent by the donor CU and received by the IAB may also be actively sent by the donor CU through an RRC message.

[0127] In one example, receiving a parent node list actively sent by the host centralized unit entity through a radio resource control layer message includes:

[0128] Receive the parent node list actively sent by the host centralized unit entity through a radio resource control layer reconfiguration message, a radio resource control layer release message, or a radio resource control layer rejection message.

[0129] When the donor CU actively sends the parent node list to the IAB node through the RRC message, the parent node list can be sent to the IAB node through the radio resource control layer reconfiguration (RRCReconfiguration) message, the parent node list can be sent to the IAB node through the radio resource control layer release (RRCRelease) message, and the parent node list can be sent to the IAB node through the radio resource control layer rejection (RRCReject) message.

[0130] In the above embodiment, all nodes in the parent node list sent by the donor CU to the IAB node support the IAB function.

[0131] In an example, the parent node list sent by the donor CU to the IAB node includes at least one of the following:

[0132] The cell ID supporting the IAB function under the currently registered PLMN;

[0133] Identifiers of cells supporting IAB function in all PLMNs;

[0134] Global Cell Identifier;

[0135] Physical cell identifier.

[0136] 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:

[0137] When the IAB node accesses a cell, when the host 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 host centralized unit entity.

[0138] When the IAB node is initially accessed, in the case where the deployment scenario is the second scenario, after the IAB node accesses any suitable cell, the donor CU determines whether the DU accessed by the IAB node supports the IAB function. If the DU accessed by the IAB node does not support the IAB function, the donor CU assists the IAB node to reselect a node as its parent node.

[0139] When the IAB node is not initially accessed, in the case where the deployment scenario is the second scenario, after the IAB node accesses any suitable cell, the donor CU determines whether the DU accessed by the IAB node supports the IAB function. If the DU accessed by the IAB node does not support the IAB function, the donor CU assists the IAB node to reselect a node as its parent node.

[0140] In one example, re-determining the parent node of the IAB node according to the auxiliary operation of the host concentration unit entity includes:

[0141] According to the switching instruction sent by the host concentration unit entity, a parent node supporting the IAB function corresponding to the switching instruction is re-determined as the parent node of the IAB node.

[0142] When the donor CU determines that the DU connected to the IAB node does not support the IAB function, it can send a switching instruction to the IAB node to switch the parent node of the IAB node back to a node that supports the IAB function.

[0143] In one example, re-determining the parent node of the IAB node according to the auxiliary operation of the host concentration unit entity includes:

[0144] Receive a radio resource control layer release message sent by the host centralized unit entity, disconnect the connection with the original DU, obtain a parent node list sent by the host centralized unit entity through a radio resource control layer message, and redetermine the parent node of the IAB node according to the parent node list.

[0145] When the donor CU determines 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, an RRC release message can be sent to the IAB node so that the IAB node disconnects the connection with the DU that does not support the IAB function after receiving the RRC release message sent by the donor CU.

[0146] 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.

[0147] In one example, re-determining the parent node of the IAB node according to the auxiliary operation of the host concentration unit entity includes:

[0148] Receive a wireless resource control layer rejection message sent by the host centralized unit entity, disconnect the connection with the original DU, obtain a parent node list sent by the host centralized unit entity through a wireless resource control layer message, and redetermine the parent node of the IAB node according to the parent node list.

[0149] When the donor CU determines that the DU connected to 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 may send an RRC reject message to the IAB node so that the IAB node will give up the continued connection operation with the DU that does not support the IAB function after receiving the RRC reject message sent by the donor CU, and reselect a node as its parent node based on the parent node list after receiving the parent node list sent by the donor CU.

[0150] Among them, all nodes in the parent node list sent by the donor CU through the RRC message support the IAB function.

[0151] 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:

[0152] The cell ID supporting the IAB function under the currently registered PLMN;

[0153] Identifiers of cells supporting IAB function in all PLMNs;

[0154] Global Cell Identifier;

[0155] Physical cell identifier.

[0156] In one example, the parent node list obtained from the host centralized unit entity includes:

[0157] The donor DU and IAB node of the host centralized unit entity are connected, and the donor DU and IAB node of the adjacent base station of the host centralized unit entity are connected.

[0158] The parent node list sent by the donor CU may include the donor DU and IAB nodes connected to the donor CU, and may also include the donor DU and IAB nodes connected to the base station adjacent to the donor CU.

[0159] In one example, the host centralized unit entity obtains information about whether the DU supports the IAB function in the following manner:

[0160] According to the DU, in the F1 setup request message or the GNB-DU configuration update message or the new F1AP message, it is indicated that the DU supports the IAB function.

[0161] The DU can indicate to the donorCU that it supports the IAB function through an F1 setup request message, a GNB-DU configuration update message, or a new F1AP message.

[0162] In one example, the host centralized unit entity generates or updates the parent node list in the following manner:

[0163] The host centralized unit entity obtains a list of base stations supporting the IAB function from the operation management and maintenance entity configuration information, wherein the list of base stations supporting the IAB function includes information of base stations supporting the IAB function and information of service cells supporting the IAB function.

[0164] The Donor CU may obtain a base station list supporting the IAB function from the OAM, wherein the base station list obtained from the OAM may include base station information supporting the IAB function and may also include service cell information supporting the IAB function.

[0165] In one example, the host centralized unit entity generates or updates the parent node list in the following manner:

[0166] The host centralized unit entity exchanges service cell information supporting the IAB function with the neighboring base station through an Xn establishment request message or NG-RAN node configuration update information.

[0167] The donor CU can exchange service cell information supporting the IAB function with the neighboring base station through Xn establishment request, or exchange service cell information supporting the IAB function with the neighboring base station through NG-RAN node configuration update information, so as to obtain service cell information belonging to the neighboring base station and supporting the IAB function.

[0168] In one example, when the host centralized unit entity determines that the DU connected to 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 centralized unit entity includes:

[0169] Indicating in a radio resource control layer establishment request message that the IAB node supports the IAB function;

[0170] When the host centralized unit entity determines that the DU connected to 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 host centralized unit entity.

[0171] In one example, when the host centralized unit entity determines that the DU connected to 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 centralized unit entity includes:

[0172] Indicating in a radio resource control layer establishment complete message that the IAB node supports the IAB function;

[0173] When the host centralized unit entity determines that the DU connected to 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 host centralized unit entity.

[0174] In one example, when the host centralized unit entity determines that the DU connected to 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 centralized unit entity includes:

[0175] When the host 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 parent node of the IAB node is re-determined according to the auxiliary operation of the host centralized unit entity.

[0176] That is, the IAB node may indicate its own IAB node identity to the donor CU in the RRC setup request message, and may also indicate its own IAB node identity to the donor CU in the RRC setup complete message.

[0177] The donor CU can also obtain the IAB node identity of a node from the IAB authorization indication carried in the initial context establishment request message, that is, learn that the node supports the IAB function.

[0178] When the IAB node indicates its own IAB node identity to the donor CU in the RRC setup request message, in one example, re-determining the parent node of the IAB node according to the auxiliary operation of the host centralized unit entity includes:

[0179] A radio resource control layer rejection message sent by the host centralized unit entity is received, the connection with the original DU is disconnected, and the parent node of the IAB node is re-determined.

[0180] When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, if the donorCU identifies 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 (at this time, the RRC establishment completion message sent by the IAB node is not received). After receiving the RRC rejection message, the IAB node re-selects the cell.

[0181] In an example, the radio resource control layer rejection message includes at least one of the following:

[0182] Supports IAB frequency information;

[0183] The cell ID supporting the IAB function under the currently registered PLMN;

[0184] Identifiers of cells supporting IAB function in all PLMNs;

[0185] Global Cell Identifier;

[0186] Physical cell identifier.

[0187] When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, in one example, if the donor CU identifies that the DU accessed by the IAB node does not support the IAB function, the donor CU may send an RRC release message to the IAB node after receiving the RRC establishment completion message sent by the IAB node. After receiving the RRC release message, the IAB node re-selects a cell.

[0188] In one example, the RRC release message includes at least one of the following:

[0189] Supports IAB frequency information;

[0190] The cell ID supporting the IAB function under the currently registered PLMN;

[0191] Identifiers of cells supporting IAB function in all PLMNs;

[0192] Global Cell Identifier;

[0193] Physical cell identifier.

[0194] When the IAB node indicates its own IAB node identity to the donor CU in the RRC setup request message, in one example, re-determining the parent node of the IAB node according to the auxiliary operation of the host centralized unit entity includes:

[0195] The host centralized unit entity receives the radio resource control layer release message sent after determining that the initial access process of the IAB node is completed, disconnects the connection with the original DU, and re-determines the parent node of the IAB node.

[0196] When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, if the donorCU identifies that the DU accessed by the IAB node does not support the IAB function, the donor CU may send an RRC release message to the IAB node after waiting for the initial access process of the IAB node to end. After receiving the RRC release message, the IAB node re-selects a cell.

[0197] In one example, the RRC release message includes at least one of the following:

[0198] Supports IAB frequency information;

[0199] The cell ID supporting the IAB function under the currently registered PLMN;

[0200] Identifiers of cells supporting IAB function in all PLMNs;

[0201] Global Cell Identifier;

[0202] Physical cell identifier.

[0203] When the IAB node indicates its own IAB node identity to the donor CU in the RRC setup request message, in one example, re-determining the parent node of the IAB node according to the auxiliary operation of the host centralized unit entity includes:

[0204] According to the switching instruction sent by the host centralized unit entity after determining that the initial access process of the IAB node is completed, a parent node supporting the IAB function corresponding to the switching instruction is re-determined as the parent node of the IAB node.

[0205] When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, if the donorCU identifies that the DU accessed by the IAB node does not support the IAB function, the donor CU can send a switching instruction to the IAB node after waiting for the initial access process of the IAB node to end, and switch the parent node of the IAB node back to a node that supports the IAB function.

[0206] When the IAB node indicates its own IAB node identity to the donor CU in the RRC setup complete message, in one example, re-determining the parent node of the IAB node according to the auxiliary operation of the host centralized unit entity includes:

[0207] A radio resource control layer release message sent by the host centralized unit entity is received, the connection with the original DU is disconnected, and the parent node of the IAB node is re-determined.

[0208] When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment completion message, if the donorCU identifies that the DU accessed by the IAB node does not support the IAB function, the donor CU may send an RRC release message to the IAB node. After receiving the RRC release message, the IAB node reselects a cell.

[0209] In one example, the RRC release message includes at least one of the following:

[0210] Supports IAB frequency information;

[0211] The cell ID supporting the IAB function under the currently registered PLMN;

[0212] Identifiers of cells supporting IAB function in all PLMNs;

[0213] Global Cell Identifier;

[0214] Physical cell identifier.

[0215] When the IAB node indicates its own IAB node identity to the donor CU in the RRC setup complete message, in one example, re-determining the parent node of the IAB node according to the auxiliary operation of the host centralized unit entity includes:

[0216] The host centralized unit entity receives the radio resource control layer release message sent after determining that the initial access process of the IAB node is completed, disconnects the connection with the original DU, and re-determines the parent node of the IAB node.

[0217] When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment completion message, if the donorCU identifies that the DU accessed by the IAB node does not support the IAB function, the donor CU may send an RRC release message to the IAB node after waiting for the initial access process of the IAB node to end. After receiving the RRC release message, the IAB node re-selects a cell.

[0218] In one example, the RRC release message includes at least one of the following:

[0219] Supports IAB frequency information;

[0220] The cell ID supporting the IAB function under the currently registered PLMN;

[0221] Identifiers of cells supporting IAB function in all PLMNs;

[0222] Global Cell Identifier;

[0223] Physical cell identifier.

[0224] When the IAB node indicates its own IAB node identity to the donor CU in the RRC setup complete message, in one example, re-determining the parent node of the IAB node according to the auxiliary operation of the host centralized unit entity includes:

[0225] According to the switching instruction sent by the host centralized unit entity after determining that the initial access process of the IAB node is completed, a parent node supporting the IAB function corresponding to the switching instruction is re-determined as the parent node of the IAB node.

[0226] When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment completion message, if the donorCU identifies that the DU accessed by the IAB node does not support the IAB function, the donor CU can send a switching instruction to the IAB node after waiting for the initial access process of the IAB node to end, and switch the parent node of the IAB node back to a node that supports the IAB function.

[0227] 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 one example, re-determining the parent node of the IAB node according to the auxiliary operation of the host centralized unit entity includes:

[0228] The host centralized unit entity receives the radio resource control layer release message sent after determining that the initial access process of the IAB node is completed, disconnects the connection with the original DU, and re-determines the parent node of the IAB node.

[0229] 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 identifies 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 waiting for the initial access process of the IAB node to end. After receiving the RRC release message, the IAB node re-selects a cell.

[0230] In one example, the RRC release message includes at least one of the following:

[0231] Supports IAB frequency information;

[0232] The cell ID supporting the IAB function under the currently registered PLMN;

[0233] Identifiers of cells supporting IAB function in all PLMNs;

[0234] Global Cell Identifier;

[0235] Physical cell identifier.

[0236] 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 one example, re-determining the parent node of the IAB node according to the auxiliary operation of the host centralized unit entity includes:

[0237] According to the switching instruction sent by the host centralized unit entity after determining that the initial access process of the IAB node is completed, a parent node supporting the IAB function corresponding to the switching instruction is re-determined as the parent node of the IAB node.

[0238] 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 switching instruction to the IAB node after waiting for the initial access process of the IAB node to end, and switch the parent node of the IAB node back to a node supporting the IAB function.

[0239] 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.

[0240] 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 may update the locally stored parent node list according to the configuration information of the OAM.

[0241] In one example, when the parent node list stored in the OAM changes, the OAM may send parent node information with changed IAB functions to the IAB node, so that the IAB node updates the parent node list stored locally according to the received parent node information with changed IAB functions.

[0242] In one example, when the parent node list stored in the OAM changes, the OAM may send the updated parent node list to the IAB node, so that the IAB node updates the parent node list stored locally according to the received parent node list.

[0243] In one example, the parent node list stored in the OAM includes at least one of the following:

[0244] The cell ID supporting the IAB function under the currently registered PLMN;

[0245] Identifiers of cells supporting IAB function in all PLMNs;

[0246] Global Cell Identifier;

[0247] Physical cell identifier.

[0248] In one example, the method further includes: updating the locally stored parent node list according to the parent node update information sent by the host centralized unit entity.

[0249] The donor CU stores a list of IAB donor DUs and / or IAB nodes and / or gNBs 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 so that the IAB node updates the parent node list stored locally.

[0250] In one example, updating the locally stored parent node list according to the parent node update information sent by the host centralized unit entity includes:

[0251] The locally stored parent node list is updated according to the parent node information of the IAB function change sent by the host centralized 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.

[0252] If the functions of the IAB donor DU, IAB node or gNB supporting IAB in the list stored in the donor CU are changed, the donor CU may send information of the IAB donor DU, IAB node and gNB whose IAB functions have been changed to the IAB node, which may be sent to the IAB node via an RRC reconfiguration message or an F1 setup response message or a GNB-CU configuration update message or a new F1AP message, so that the IAB node updates the local parent node list.

[0253] In one example, updating the locally stored parent node list according to the parent node update information sent by the host centralized unit entity includes:

[0254] The locally stored parent node list is updated according to the updated parent node list sent by the host centralized 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.

[0255] If there is an IAB donor DU or IAB node or gNB supporting IAB functions in the list stored in the donor CU, the donor CU may send the locally updated parent node list to the IAB node, which may be sent to the IAB node via an RRC reconfiguration message or an F1 setup response message or a GNB-CU configuration update message or a new F1AP message, so that the IAB node updates the local parent node list.

[0256] 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.

[0257] In an example, the IAB node may also update the local parent node list according to the parent node list carried in the RRC reject message.

[0258] In an example, the parent node list stored in the donor CU includes at least one of the following:

[0259] The cell ID supporting the IAB function under the currently registered PLMN;

[0260] Identifiers of cells supporting IAB function in all PLMNs;

[0261] Global Cell Identifier;

[0262] Physical cell identifier.

[0263] In an exemplary embodiment, Fig.10A flow chart of a parent node selection method provided by the present application. The method can be applied to the case where the IAB selects a parent node that supports the IAB function when accessing the network. The method can be performed by a parent node selection device applied to an AMF entity provided by the present application, and the parent node selection device can be implemented by software and / or hardware and integrated in the AMF entity.

[0264] like Fig.10 As shown, the present application provides a parent node selection method applied to an AMF entity, including:

[0265] S220: Based on the switching of the NG interface, the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node is sent to the host centralized unit entity or the base station corresponding to the target parent node.

[0266] Among them, the switching based on the NG interface mainly includes the situation before and after the parent node of the IAB node is switched, the situation where the donor CU or base station connected to the IAB node is connected to the same AMF entity, the situation where different AMF entities are connected, and the situation where different RATs (Radio Access Technology) are connected.

[0267] The present application provides a parent node selection method. After the IAB node determines the target parent node of the IAB node according to the access status of the IAB node and the deployment scenario of the IAB node accessing the network, the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node is sent to the host centralized unit entity or base station corresponding to the target parent node, thereby realizing the connection between the IAB node and the parent node supporting the IAB function selected by the IAB node, thereby ensuring the IAB function of the IAB node and achieving the effect of serving other child IAB nodes and UEs.

[0268] In one example, sending the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to a host centralized unit entity or a base station corresponding to a target parent node includes:

[0269] The IAB authorization indication information of the IAB node or the IAB node indication of the IAB node is sent to a host centralized unit entity or a base station corresponding to the target parent node through an NGAP (Next Generation Application Protocol) handover request message.

[0270] In one example, sending the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to a host centralized unit entity or a base station corresponding to a target parent node includes:

[0271] The IAB authorization indication information of the IAB node or the IAB node indication of the IAB node is sent to the host centralized unit entity or the base station corresponding to the target parent node through a path switching request confirmation message.

[0272] This embodiment also provides a parent node selection device, Fig.11 A schematic diagram of the structure of a parent node selection device provided in this application, such as Fig.11 As shown, an embodiment of the present application provides a parent node selection device applied to an IAB node, which can be integrated in the IAB node. The device includes:

[0273] The first parent node selection module 320 is configured to determine the parent node of the IAB node according to the access status of the IAB node and the deployment scenario of the IAB node accessing the network.

[0274] The parent node selection device applied to the IAB node provided in this embodiment is used to implement the parent node selection method applied to the IAB node as described in the embodiment of the present application. The implementation principle and technical effect of the parent node selection device applied to the IAB node provided in this embodiment are similar to the parent node selection method applied to the IAB node as described in the embodiment of the present application, and will not be repeated here.

[0275] Among them, an IAB node of an IAB node is called a child IAB node of the IAB node, and a DU or base station supporting the IAB function to which an IAB node is connected as a connection identity is called a parent IAB node of the IAB node.

[0276] The IAB node may be a DU entity or a MT.

[0277] In an example, deployment scenarios of IAB nodes accessing a network may include the following six deployment scenarios.

[0278] The first scenario is that the IAB node deployment location setting area includes an IAB donor DU, an IAB node and a base station supporting the IAB function.

[0279] 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 a host centralized unit entity donor CU.

[0280] The third scenario is that the IAB node deployment location setting area includes an IAB donor DU, an IAB node and a base station that does not support the IAB function, and an access management function entity connected to the base station supports the IAB function.

[0281] The fourth scenario is that the IAB node deployment location setting area includes an IAB donor DU, an IAB node and a base station that does not support the IAB function, and an access management function entity connected to the base station does not support the IAB function.

[0282] The fifth scenario is: the IAB node deployment location setting area includes an IAB donor DU, an IAB node and a distribution unit entity that does not support the IAB function, a centralized unit entity connected to the distribution unit entity that does not support the IAB function does not support the IAB function, and an access management function entity connected to the centralized unit entity supports the IAB function.

[0283] The sixth scenario is: the IAB node deployment location setting area includes an IAB donor DU, an IAB node and a distribution unit entity that does not support the IAB function, a centralized unit entity connected to the distribution unit entity that does not support the IAB function does not support the IAB function, and an access management function entity connected to the centralized unit entity does not support the IAB function.

[0284] In one example, 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 first parent node selection module 320 is configured to: select the parent node of the IAB node from the parent node list preconfigured by the IAB node.

[0285] In one example, the parent node list preconfigured by the IAB node includes at least one of the following:

[0286] The cell ID supporting the IAB function under the currently registered PLMN;

[0287] Identifiers of cells supporting IAB function in all PLMNs;

[0288] Global Cell Identifier;

[0289] Physical cell identifier.

[0290] In one example, the above-mentioned device also includes a parent node IAB function judgment module, which is configured to: when the IAB node accesses a cell, determine whether the distributed unit entity or base station accessed by the IAB node supports the IAB function based on whether the wireless resource control layer reconfiguration message contains a return adaptation protocol layer configuration message.

[0291] In one example, 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 first parent node selection module 320 is configured to select the parent node of the IAB node based on the system information broadcast by the cell.

[0292] In one 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: determine whether the cell to which the IAB node accesses supports the IAB function based on whether the system information broadcast by the cell includes an IAB-specific PRACH configuration.

[0293] In one 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 configured to: determine whether the cell accessed by the IAB node supports the IAB function based on whether the system information broadcast by the cell includes IAB dedicated system information, wherein the IAB dedicated system information includes at least one of cell access prohibition information, admission control parameters, cell selection parameters, and cell reselection parameters.

[0294] In one 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 configured to: 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.

[0295] The system information for cell reselection broadcast by the IAB node or the IAB donor CU includes at least one of the following:

[0296] Frequency information supporting IAB function;

[0297] The cell ID supporting the IAB function under the currently registered PLMN;

[0298] Identifiers of cells supporting IAB function in all PLMNs;

[0299] Global Cell Identifier;

[0300] Physical cell identifier.

[0301] In one example, the access status 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: when the IAB node accesses a cell, obtain a parent node list in the operation management and maintenance entity configuration information; and select the parent node of the IAB node from the parent node list.

[0302] In one example, the parent node list obtained in the OAM configuration information includes at least one of the following:

[0303] The cell ID supporting the IAB function under the currently registered PLMN;

[0304] Identifiers of cells supporting IAB function in all PLMNs;

[0305] Global Cell Identifier;

[0306] Physical cell identifier.

[0307] In one example, the access status 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: select the parent node of the IAB node from the parent node list obtained in the OAM configuration information at the IAB node.

[0308] In one example, the parent node list obtained from the OAM includes at least one of the following:

[0309] The cell ID supporting the IAB function under the currently registered PLMN;

[0310] Identifiers of cells supporting IAB function in all PLMNs;

[0311] Global Cell Identifier;

[0312] Physical cell identifier.

[0313] In one example, the access status 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: select the parent node of the IAB node from the parent node list obtained by the IAB node from the host centralized unit entity.

[0314] In one example, the parent node list obtained from the donor CU includes at least one of the following:

[0315] The cell ID supporting the IAB function under the currently registered PLMN;

[0316] Identifiers of cells supporting IAB function in all PLMNs;

[0317] Global Cell Identifier;

[0318] Physical cell identifier.

[0319] In one example, the first parent node selection module 320 is configured to: request the host centralized unit entity to send a parent node list through a message, so that the host centralized unit entity sends the parent node list to the IAB node after receiving the request, and the IAB node selects the parent node of the IAB node from the parent node list obtained in the host centralized unit entity.

[0320] In one example, the first parent node selection module 320 is configured to: request the host centralized unit entity to send a parent node list through a wireless resource control layer establishment request message or a wireless resource control layer establishment completion message or a wireless resource control layer reconfiguration completion message, and select the parent node of the IAB node from the parent node list obtained in the host centralized unit entity at the IAB node.

[0321] In one example, the first parent node selection module 320 is configured to: request the host centralized unit entity to send a parent node list through an F1 establishment request message or a GNB-DU configuration update message or a new F1AP message, and select the parent node of the IAB node from the parent node list obtained in the host centralized unit entity at the IAB node.

[0322] In one example, the first parent node selection module 320 is configured to: receive a parent node list actively sent by the host centralized unit entity through a radio resource control layer message, and select the parent node of the IAB node from the parent node list obtained from the host centralized unit entity at the IAB node.

[0323] In one example, the first parent node selection module 320 is configured to: receive a parent node list actively sent by the host centralized unit entity through a wireless resource control layer reconfiguration message, a wireless resource control layer release message, or a wireless resource control layer rejection message, and select the parent node of the IAB node from the parent node list obtained in the host centralized unit entity at the IAB node.

[0324] In an example, the parent node list sent by the donor CU to the IAB node includes at least one of the following:

[0325] The cell ID supporting the IAB function under the currently registered PLMN;

[0326] Identifiers of cells supporting IAB function in all PLMNs;

[0327] Global Cell Identifier;

[0328] Physical cell identifier.

[0329] In one 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: when the IAB node accesses the cell, when the host 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 host centralized unit entity.

[0330] In one 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: when the IAB node accesses the cell, when the host concentration 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 concentration 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.

[0331] In one 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: when the IAB node accesses a cell, when the host centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, receive the wireless resource control layer release message sent by the host centralized unit entity, disconnect the connection with the original DU, and obtain the parent node list sent by the host centralized unit entity through the wireless resource control layer message, and redetermine the parent node of the IAB node according to the parent node list.

[0332] In one 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: when the IAB node accesses a cell, when the host centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, it receives a wireless resource control layer rejection message sent by the host centralized unit entity, disconnects from the original DU, and obtains a parent node list sent by the host centralized unit entity through a wireless resource control layer message, and redetermines the parent node of the IAB node according to the parent node list.

[0333] 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:

[0334] The cell ID supporting the IAB function under the currently registered PLMN;

[0335] Identifiers of cells supporting IAB function in all PLMNs;

[0336] Global Cell Identifier;

[0337] Physical cell identifier.

[0338] In one example, the parent node list obtained from the host centralized unit entity includes:

[0339] The donor DU and IAB node of the host centralized unit entity are connected, and the donor DU and IAB node of the adjacent base station of the host centralized unit entity are connected.

[0340] In one example, the host centralized unit entity obtains information about whether the DU supports the IAB function in the following manner:

[0341] According to the DU, in the F1 setup request message or the GNB-DU configuration update message or the new F1AP message, it is indicated that the DU supports the IAB function.

[0342] In one example, the host centralized unit entity generates or updates the parent node list in the following manner:

[0343] The host centralized unit entity obtains a list of base stations supporting the IAB function from the operation management and maintenance entity configuration information, wherein the list of base stations supporting the IAB function includes information of base stations supporting the IAB function and information of service cells supporting the IAB function.

[0344] In one example, the host centralized unit entity generates or updates the parent node list in the following manner:

[0345] The host centralized unit entity exchanges service cell information supporting the IAB function with the neighboring base station through an Xn establishment request message or NG-RAN node configuration update information.

[0346] In one 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: indicate in a wireless resource control layer establishment request message that the IAB node supports the IAB function; when the host centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, redetermine the parent node of the IAB node based on the auxiliary operation of the host centralized unit entity.

[0347] In one 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: indicate that the IAB node supports the IAB function in the wireless resource control layer establishment request message; receive the wireless resource control layer rejection message sent by the host centralized unit entity, disconnect the connection with the original DU, and re-determine the parent node of the IAB node.

[0348] In an example, the radio resource control layer rejection message includes at least one of the following:

[0349] Supports IAB frequency information;

[0350] The cell ID supporting the IAB function under the currently registered PLMN;

[0351] Identifiers of cells supporting IAB function in all PLMNs;

[0352] Global Cell Identifier;

[0353] Physical cell identifier.

[0354] In one 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: indicate that the IAB node supports the IAB function in the wireless resource control layer establishment request message; receive the wireless resource control layer release message sent by the host centralized unit entity after receiving the RRC establishment completion message, disconnect the connection with the original DU, and re-determine the parent node of the IAB node.

[0355] In one example, the RRC release message includes at least one of the following:

[0356] Supports IAB frequency information;

[0357] The cell ID supporting the IAB function under the currently registered PLMN;

[0358] Identifiers of cells supporting IAB function in all PLMNs;

[0359] Global Cell Identifier;

[0360] Physical cell identifier.

[0361] In one 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: indicate in the wireless resource control layer establishment request message that the IAB node supports the IAB function; receive the wireless resource control layer release message sent by the host centralized unit entity after determining that the initial access process of the IAB node is completed, disconnect the connection with the original DU, and re-determine the parent node of the IAB node.

[0362] In one example, the RRC release message includes at least one of the following:

[0363] Supports IAB frequency information;

[0364] The cell ID supporting the IAB function under the currently registered PLMN;

[0365] Identifiers of cells supporting IAB function in all PLMNs;

[0366] Global Cell Identifier;

[0367] Physical cell identifier.

[0368] In one 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: indicate in a wireless resource control layer establishment request message that the IAB node supports the IAB function; according to a switching instruction sent by the host centralized unit entity after determining that the initial access process of the IAB node is completed, redetermine the parent node supporting the IAB function corresponding to the switching instruction as the parent node of the IAB node.

[0369] In one 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: indicate in the wireless resource control layer establishment completion message that the IAB node supports the IAB function; when the host centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, redetermine the parent node of the IAB node according to the auxiliary operation of the host centralized unit entity.

[0370] In one 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: indicate that the IAB node supports the IAB function in the wireless resource control layer establishment completion message; receive the wireless resource control layer release message sent by the host centralized unit entity, disconnect the connection with the original DU, and re-determine the parent node of the IAB node.

[0371] In one example, the RRC release message includes at least one of the following:

[0372] Supports IAB frequency information;

[0373] The cell ID supporting the IAB function under the currently registered PLMN;

[0374] Identifiers of cells supporting IAB function in all PLMNs;

[0375] Global Cell Identifier;

[0376] Physical cell identifier.

[0377] In one 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: indicate that the IAB node supports the IAB function in the wireless resource control layer establishment completion message; receive the wireless resource control layer release message sent by the host centralized unit entity after determining that the initial access process of the IAB node is completed, disconnect the connection with the original DU, and re-determine the parent node of the IAB node.

[0378] In one example, the RRC release message includes at least one of the following:

[0379] Supports IAB frequency information;

[0380] The cell ID supporting the IAB function under the currently registered PLMN;

[0381] Identifiers of cells supporting IAB function in all PLMNs;

[0382] Global Cell Identifier;

[0383] Physical cell identifier.

[0384] In one 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: indicate that the IAB node supports the IAB function in the wireless resource control layer establishment completion message; according to the switching instruction sent by the host centralized unit entity after determining that the initial access process of the IAB node is over, the parent node supporting the IAB function corresponding to the switching instruction is re-determined as the parent node of the IAB node.

[0385] In one 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: when the host centralized unit entity learns through the IAB authorization indication carried in the initial context establishment request message 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 parent node of the IAB node is re-determined according to the auxiliary operation of the host centralized unit entity.

[0386] In one 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: when the host 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 host centralized unit entity receives the wireless resource control layer release message sent after determining that the initial access process of the IAB node is completed, disconnects the connection with the original DU, and re-determines the parent node of the IAB node.

[0387] In one example, the RRC release message includes at least one of the following:

[0388] Supports IAB frequency information;

[0389] The ID of the cell that supports the IAB function under current registration;

[0390] All cell identifiers that support the IAB function;

[0391] Global Cell Identifier;

[0392] Physical cell identifier.

[0393] In one 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: when the host 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, according to the switching instruction sent by the host centralized unit entity after determining that the initial access process of the IAB node is completed, the parent node supporting the IAB function corresponding to the switching instruction is re-determined as the parent node of the IAB node.

[0394] In one example, the apparatus further includes a first parent node list updating module configured to update the locally stored parent node list according to configuration update information sent by the operation management and maintenance entity.

[0395] In one example, the first parent node list updating module is configured to update the locally stored parent node list according to the parent node information of the IAB function change sent by the operation management and maintenance entity.

[0396] In one example, the first parent node list updating 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.

[0397] In one example, the parent node list stored in the OAM includes at least one of the following:

[0398] The cell ID supporting the IAB function under the currently registered PLMN;

[0399] Identifiers of cells supporting IAB function in all PLMNs;

[0400] Global Cell Identifier;

[0401] Physical cell identifier.

[0402] In one example, the apparatus further includes a second parent node list updating module configured to update the locally stored parent node list according to the parent node update information sent by the host centralized unit entity.

[0403] In one example, the second parent node list update module is configured to update the locally stored parent node list according to the parent node information of the IAB function change sent by the host centralized unit entity through a wireless resource control layer message or an F1 establishment response message or a GNB-CU configuration update message or a new F1AP message.

[0404] In one example, the second 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 host centralized unit entity through a wireless resource control layer message or an F1 establishment response message or a GNB-CU configuration update message or a new F1AP message.

[0405] In one example, the second parent node list updating module is configured to update the local parent node list according to the parent node list carried in the RRC release message.

[0406] In one example, the second parent node list updating module is configured to: update the local parent node list according to the parent node list carried in the RRC reject message.

[0407] In an example, the parent node list stored in the donor CU includes at least one of the following:

[0408] The cell ID supporting the IAB function under the currently registered PLMN;

[0409] Identifiers of cells supporting IAB function in all PLMNs;

[0410] Global Cell Identifier;

[0411] Physical cell identifier.

[0412] This embodiment also provides a parent node selection device, Fig.12A schematic diagram of the structure of a parent node selection device provided in this application, such as Fig.12 As shown, a parent node selection device applied to an AMF entity provided in an embodiment of the present application can be integrated in the AMF entity, and the device includes:

[0413] 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 host centralized unit entity or the base station corresponding to the target parent node.

[0414] The parent node selection device applied to the AMF entity provided in this embodiment is used to implement the parent node selection method applied to the AMF entity as described in the embodiment of the present application. The implementation principle and technical effect of the parent node selection device applied to the AMF entity provided in this embodiment 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.

[0415] In one 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 host centralized unit entity or base station corresponding to the target parent node via an NGAP handover request message.

[0416] In one 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 host centralized unit entity or base station corresponding to the target parent node via a path switching request confirmation message.

[0417] This embodiment of the application provides an IAB node, Fig.13 A schematic diagram of the structure of an IAB node provided in this application, such as Fig.13 As shown, the IAB node provided by the present application includes: one or more processors 510 and a storage device 520; the processor 510 of the IAB node may be one or more, Fig.13 A processor 510 is taken as an example; the storage device 520 is used to store one or more programs; the one or more programs are executed by the one or more processors 510, 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.

[0418] The processor 510 and the storage device 520 in the IAB node may be connected via a bus or other means. Fig.13 The example of connecting through bus is taken in the following.

[0419] The storage device 520, as a computer-readable storage medium, may be configured to store software programs, computer executable programs, and modules, such as the program instructions / modules corresponding to the parent node selection method applied to the IAB node described in the embodiment of the present application (for example, the first parent node selection module 320 in the parent node selection device applied to the IAB node). The storage device 520 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to the use of the device, etc. 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 disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the storage device 520 may further include a memory remotely arranged relative to the processor 510, and these remote memories may be connected to the first node via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0420] The embodiment of the present application provides an access management function entity, Fig.14 A schematic diagram of the structure of an access management function entity provided in this application, such as Fig.14 As shown, the access management function entity provided by the present application includes: one or more processors 610 and a storage device 620; the processor 610 of the access management function entity may be one or more, Fig.14 A processor 610 is taken as an example; the storage device 620 is used to store one or more programs; 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 node selection method applied to the access management function entity as described in the embodiment of the present invention.

[0421] The processor 610 and the storage device 620 in the access management function entity may be connected via a bus or other means. Fig.14 The example of connecting through bus is taken in the following.

[0422] 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 / modules corresponding to the parent node selection method applied to the access management function entity described in the embodiment of the present application (for example, the first parent node selection module 420 in the parent node selection device applied to the access management function entity). The storage device 620 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to the use of the device, etc. 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 disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the storage device 620 may further include a memory remotely arranged relative to the processor 610, and these remote memories may be connected to the first node via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0423] An embodiment of the present application also provides a storage medium, which stores a computer program. When the computer program is executed by a processor, it implements any of the parent node selection methods applied to the IAB node described in the embodiments of the present application or any of the parent node selection methods applied to the access management function entity described in the embodiments of the present application.

[0424] The parent node selection method applied to the IAB node includes: determining the parent node of the IAB node according to the access status of the IAB node and the deployment scenario of the IAB node accessing the network.

[0425] The parent node selection method applied to the access management function entity includes: based on the switching 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 or base station corresponding to the target parent node.

[0426] The above description is merely an exemplary embodiment of the present application and is not intended to limit the protection scope of the present application.

[0427] It will be appreciated by those skilled in the art that the term user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a vehicle-mounted mobile station.

[0428] In general, various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software that can be executed by a controller, microprocessor or other computing device, although the present application is not limited thereto.

[0429] Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a physical device, such as in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

[0430] The block diagram of any logic 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. A computer program may be stored on a memory. The memory may have any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as but not limited to read-only memory (ROM), random access memory (RAM), optical memory devices and systems (digital versatile discs (DVD) or compact disks (CD)), etc. Computer-readable media may include non-transient storage media. A data processor may be any type suitable for the local technical environment, such as but not limited to a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FGPAs) and a processor based on a multi-core processor architecture.

[0431] By way of exemplary and non-limiting examples, a detailed description of exemplary embodiments of the present application has been provided above. However, various modifications and adjustments to the above embodiments will be apparent to those skilled in the art when considered in conjunction with the accompanying drawings and claims, but will not depart from the scope of the present invention. Therefore, the proper scope of the present invention will be determined according to the claims.

Claims

1. A parent node selection method, applied to an IAB node of an access backhaul link, characterized in that: include: Determine a parent node of the IAB node according to an access status of the IAB node and a deployment scenario of the IAB node accessing a network; The determining the parent node of the IAB node comprises: selecting the parent node of the IAB node based on system information broadcast by a cell; The selecting the parent node of the IAB node based on the system information broadcast by the cell includes: selecting 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 system information for cell reselection includes at least one of the following: frequency information supporting the IAB function; a cell identifier supporting the IAB function under the currently registered public land mobile network; and a cell identifier supporting the IAB function under all public land mobile networks.

2. The method according to claim 1, characterized in that The IAB node includes at least one of a distributed network element DU and a mobile terminal MT.

3. The method according to claim 1, characterized in that The access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first scenario, the second scenario, the third scenario, the fourth scenario, the fifth scenario, and the sixth scenario, and determining the parent node of the IAB node includes: Selecting a parent node of the IAB node from a parent node list preconfigured for the IAB node; The first scenario is that the IAB node deployment location setting area includes an IAB donor distribution unit entity donor DU, an IAB node and a base station supporting the IAB function; The second scenario is: the IAB node deployment location setting area includes an IAB donor DU and a distribution unit entity that does not support the IAB function, and the distribution unit entity that does not support the IAB function is connected to a host centralized unit entity donor CU; The third scenario is: the IAB node deployment location setting area includes an IAB donor DU, an IAB node and a 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 that the IAB node deployment location setting area includes an IAB donor DU, an IAB node and a 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 an IAB donor DU, an IAB node and a distributed unit entity that does not support the IAB function, a centralized unit entity connected to the distributed unit entity that does not support the IAB function does not support the IAB function, and an access management function entity connected to the centralized unit entity supports the IAB function; The sixth scenario is: the IAB node deployment location setting area includes an IAB donor DU, an IAB node and a distributed unit entity that does not support the IAB function, a centralized unit entity connected to the distributed unit entity that does not support the IAB function does not support the IAB function, and an access management function entity connected to the centralized unit entity does not support the IAB function.

4. The method according to claim 1, characterized in that Selecting a parent node of the IAB node based on system information broadcast by a cell includes: Determining whether the cell accessed by the IAB node supports the IAB function according to whether the system information broadcast by the cell includes the IAB dedicated physical random access channel configuration; or, Whether the cell accessed by the IAB node supports the IAB function is determined according to whether the system information broadcast by the cell includes IAB dedicated system information, wherein the IAB dedicated system information includes at least one of cell access prohibition information, admission control parameters, cell selection parameters, and cell reselection parameters.

5. The method according to claim 3, characterized in that: The access condition of the IAB node is initial access, the deployment scenario is one of the first scenario, the second scenario, the third scenario, the fourth scenario, the fifth scenario, and the sixth scenario, and determining the parent node of the IAB node includes: When the IAB node accesses a cell, obtaining a parent node list in the operation management and maintenance entity configuration information; A parent node of the IAB node is selected from the parent node list.

6. The method according to claim 3, characterized in that The access condition of the IAB node is non-initial access, the deployment scenario is one of the first scenario, the second scenario, the third scenario, the fourth scenario, the fifth scenario, and the sixth scenario, and determining the parent node of the IAB node includes: The parent node of the IAB node is selected from the parent node list obtained from the operation management and maintenance entity configuration information at the IAB node.

7. The method according to claim 3, characterized in that The access condition of the IAB node is non-initial access, the deployment scenario is one of the first scenario, the second scenario, the third scenario, the fourth scenario, the fifth scenario, and the sixth scenario, and determining the parent node of the IAB node includes: The IAB node selects a parent node of the IAB node from a parent node list obtained from a host centralized unit entity.

8. The method according to claim 7, characterized in that Obtaining a parent node list from the host centralized unit entity includes: Requesting the host centralized unit entity to send a parent node list through a message, so that the host centralized unit entity sends the parent node list to the IAB node after receiving the request; or Receive a parent node list actively sent by the host centralized unit entity through a radio resource control layer message.

9. The method according to claim 8, characterized in that Requesting the host centralized unit entity to send a parent node list through a message includes: Requesting the host centralized unit entity to send a parent node list through a radio resource control layer establishment request message, a radio resource control layer establishment completion message, or a radio resource control layer reconfiguration completion message; or, Requesting the host centralized unit entity to send a parent node list through an F1 establishment request message or a GNB-DU configuration update message or a new F1AP message; Receiving a parent node list actively sent by the host centralized unit entity through a radio resource control layer message, including: Receive the parent node list actively sent by the host centralized unit entity through a radio resource control layer reconfiguration message, a radio resource control layer release message, or a radio resource control layer rejection message.

10. The method according to claim 3, characterized in that: 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: When the IAB node accesses a cell, when the host 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 host centralized unit entity.

11. The method according to claim 10, characterized in that Re-determining the parent node of the IAB node according to the auxiliary operation of the host centralized unit entity includes: According to the switching instruction sent by the host centralized unit entity, a parent node supporting the IAB function corresponding to the switching instruction is re-determined as the parent node of the IAB node; or, Receive a wireless resource control layer release message or a wireless resource control layer rejection message sent by the host centralized unit entity, disconnect the connection with the original DU, and obtain a parent node list sent by the host centralized unit entity through a wireless resource control layer message, and redetermine the parent node of the IAB node according to the parent node list.

12. The method according to any one of claims 3, 5, 6, 7 and 11, characterized in that The parent node list includes at least one of the following: The cell identity supporting the IAB function under the currently registered public land mobile network; Identifiers of cells supporting IAB function in all public land mobile networks; Global Cell Identifier; Physical cell identifier.

13. The method according to claim 11, characterized in that The parent node list obtained from the host centralized unit entity includes: The donor DU and IAB node of the host centralized unit entity are connected, and the donor DU and IAB node of the adjacent base station of the host centralized unit entity are connected.

14. The method according to claim 13, characterized in that The host centralized unit entity obtains information about whether the DU supports the IAB function by: According to the DU, in the F1 setup request message or the GNB-DU configuration update message or the new F1AP message, it is indicated that the DU supports the IAB function.

15. The method according to claim 13, characterized in that The manner in which the host centralized unit entity generates or updates the parent node list includes: The host centralized unit entity obtains a list of base stations supporting the IAB function from the operation management and maintenance entity configuration information, wherein the list of base stations supporting the IAB function includes information of base stations supporting the IAB function and information of service cells supporting the IAB function; or, The host centralized unit entity exchanges service cell information supporting the IAB function with the neighboring base station through an Xn establishment request message or NG-RAN node configuration update information.

16. The method according to claim 10, characterized in that When the host centralized unit entity determines that the DU connected to 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 centralized unit entity includes: Indicating in a radio resource control layer establishment request message that the IAB node supports the IAB function; When the host centralized unit entity determines that the DU connected to 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 host centralized unit entity.

17. The method according to claim 16, characterized in that Re-determining the parent node of the IAB node according to the auxiliary operation of the host centralized unit entity includes: receiving a radio resource control layer rejection message sent by the host centralized unit entity, disconnecting from the original DU, and re-determining the parent node of the IAB node; The radio resource control layer rejection message includes at least one of the following: Supports IAB frequency information; The cell identity supporting the IAB function under the currently registered public land mobile network; Identifiers of cells supporting IAB function in all public land mobile networks; Global Cell Identifier; Physical cell identifier.

18. The method according to claim 10, characterized in that When the host centralized unit entity determines that the DU connected to 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 centralized unit entity includes: Indicating in a radio resource control layer establishment complete message that the IAB node supports the IAB function; When the host centralized unit entity determines that the DU connected to 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 host centralized unit entity.

19. The method according to claim 18, characterized in that Re-determining the parent node of the IAB node according to the auxiliary operation of the host centralized unit entity includes: receiving a radio resource control layer release message sent by the host centralized unit entity, disconnecting from 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: Supports IAB frequency information; The cell identity supporting the IAB function under the currently registered public land mobile network; Identifiers of cells supporting IAB function in all public land mobile networks; Global Cell Identifier; Physical cell identifier.

20. The method according to claim 10, characterized in that When the host centralized unit entity determines that the DU connected to 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 centralized unit entity includes: When the host 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 parent node of the IAB node is re-determined according to the auxiliary operation of the host centralized unit entity.

21. The method according to any one of claims 16, 18 and 20, characterized in that Re-determining the parent node of the IAB node according to the auxiliary operation of the host centralized unit entity includes: receiving a radio resource control layer release message sent by the host centralized unit entity after determining that the initial access process of the IAB node is completed, disconnecting from the original DU, and re-determining the parent node of the IAB node; or, According to the switching instruction sent by the host centralized unit entity after determining that the initial access process of the IAB node is completed, re-determining the parent node supporting the IAB function corresponding to the switching instruction as the parent node of the IAB node; The radio resource control layer release message includes at least one of the following: Supports IAB frequency information; The cell identity supporting the IAB function under the currently registered public land mobile network; Identifiers of cells supporting IAB function in all public land mobile networks; Global Cell Identifier; Physical cell identifier.

22. The method according to claim 1, characterized in that Also includes: According to the parent node update information sent by the host centralized unit entity, the locally stored parent node list is updated.

23. The method according to claim 22, characterized in that According to the parent node update information sent by the host centralized unit entity, the locally stored parent node list is updated, including: Update the locally stored parent node list according to the parent node information of the IAB function change sent by the host centralized 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; or, The locally stored parent node list is updated according to the updated parent node list sent by the host centralized 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.

24. A parent node selection device, applied to an IAB node of an access backhaul link, characterized in that: include: A first parent node selection module is configured to determine a parent node of the IAB node according to an access status of the IAB node and a deployment scenario of the IAB node accessing a network; The determining the parent node of the IAB node comprises: selecting the parent node of the IAB node based on system information broadcast by a cell; The selecting the parent node of the IAB node based on the system information broadcast by the cell includes: selecting 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 system information for cell reselection includes at least one of the following: frequency information supporting the IAB function; a cell identifier supporting the IAB function under the currently registered public land mobile network; and a cell identifier supporting the IAB function under all public land mobile networks.

25. An IAB node, characterized in that: include: one or more processors; A storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the parent node selection method as described in any one of claims 1-23.

26. A storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the parent node selection method described in any one of claims 1 to 23 is implemented.

Images