WO2021027817A1

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

Info

Publication number: WO2021027817A1
Application number: PCT/CN2020/108483
Authority: WO
Inventors: 刁雪莹
Original assignee: 中兴通讯股份有限公司
Priority date: 2019-08-15
Filing date: 2020-08-11
Publication date: 2021-02-18
Also published as: CN110536377A

Abstract

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

Description

Parent node selection method, device, equipment and medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office with application number 201910755605.4 on August 15, 2019. The entire content of this application is incorporated into this application by reference.

Technical field

This application relates to the field of wireless communication, and in particular to a method, device, equipment and medium for selecting a parent node.

Background technique

The high transmission speed of 5G networks is mainly due to the use of millimeter waves. However, millimeter waves have large attenuation in the air and weak diffraction capabilities. For this reason, the integrated access and backhaul links (IAB) technology Been proposed. The self-access backhaul link includes the wireless access link and the wireless backhaul link. The wireless access link is the communication link between the UE (User Equipment) and the IAB node, and the wireless backhaul link is the IAB The communication link between nodes is used for data return, so the IAB node does not need a wired transmission network for data return. When an IAB node accesses the network, the IAB node may be connected to a DU (Distributed Unit, distributed unit entity) or base station that does not support the IAB function. At this time, the IAB node cannot implement its IAB function.

Summary of the invention

This application provides a method, device, equipment, and medium for selecting a parent node to ensure that an IAB node can realize its IAB function.

In the first aspect, an embodiment of the present application provides a method for selecting a parent node, which is applied to an IAB node, including:

Determine the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.

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

After the IAB node determines the target parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node’s access to the network, the IAB authorization indication information of the IAB node or the IAB node’s The IAB node instruction is sent to the donor centralized unit entity or base station corresponding to the target parent node.

In a third aspect, an embodiment of the present application provides a parent node selection device, which is applied to an IAB node, and is characterized in that it includes:

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

In a fourth aspect, an embodiment of the present application provides a parent node selection device, which is applied to an access management function entity, and includes:

The second parent node selection module is configured to determine the target parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node’s access to the network, and then send the IAB authorization indication information of the IAB node or The IAB node indication of the IAB node is sent to the donor centralized unit entity or the base station corresponding to the target parent node.

In a fifth aspect, an embodiment of the present application provides an IAB node, including: one or more processors; a storage device, configured to store one or more programs; when the one or more programs are used by the one or more The processor executes, so that the one or more processors implement the parent node selection method applied to the IAB node as described in any embodiment of the present application.

In a sixth aspect, an embodiment of the present application provides a storage medium, the storage medium stores a computer program, and when the computer program is executed by a processor, it is applied to the parent of the IAB node as described in any embodiment of the present application. Node selection method.

In a seventh aspect, an embodiment of the present application provides an access management function entity, including: one or more processors; a storage device, configured to store one or more programs; when the one or more programs are used by the one Or multiple processors execute, so that the one or more processors implement the parent node selection method applied to the access management functional entity as described in any embodiment of the present application.

In an eighth aspect, an embodiment of the present application provides a storage medium that stores a computer program that, when executed by a processor, implements the application to an access management function entity as described in any embodiment of the present application The parent node selection method in.

Regarding the above embodiments and other aspects of the present application and their implementation manners, more descriptions are provided in the description of the drawings, specific implementation manners, and claims.

Description of the drawings

Figure 1 is a schematic diagram of network IAB deployment;

Figure 2 is a schematic diagram of network IAB deployment with separated CU and DU;

FIG. 3 is a schematic flowchart of a method for selecting a parent node provided by this application;

Figure 4 is a schematic diagram of the first IAB node deployment scenario provided by this application;

Figure 5 is a schematic diagram of the second IAB node deployment scenario provided by this application;

Figure 6 is a schematic diagram of the third deployment scenario of IAB nodes provided by this application;

Figure 7 is a schematic diagram of the fourth IAB node deployment scenario provided by this application;

Figure 8 is a schematic diagram of a fifth IAB node deployment scenario provided by this application;

FIG. 9 is a schematic diagram of the sixth IAB node deployment scenario provided by this application;

FIG. 10 is a schematic flowchart of a method for selecting a parent node provided by this application;

FIG. 11 is a schematic structural diagram of a parent node selection device provided by this application;

FIG. 12 is a schematic structural diagram of a parent node selection device provided by this application;

FIG. 13 is a schematic structural diagram of an IAB node provided by this application;

FIG. 14 is a schematic structural diagram of an access management function entity provided by this application.

detailed description

In order to make the purpose, technical solutions, and advantages of the present application clearer, the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings. It should be noted that the embodiments in this application and the features in the embodiments can be combined arbitrarily with each other if there is no conflict.

Before describing the implementation manners provided by the present application, IAB is first exemplarily explained.

An example of a network deployed with IAB is shown in Figure 1. The figure includes node 10, node 20, and node 30. Node 10 is connected to the core network through a wired connection, for example, node 10 is connected to the core network through optical fiber 11. , The node 20 and the node 30 send and receive data to the core network through the node 10. User Equipment (UE) can access node 10, node 20, and node 30 through an access link, and data can be transmitted between nodes through a wireless backhaul link (BH link). In an IAB network, an access node that supports wireless access and wireless backhaul of data is called an IAB node (IAB node), such as the node 20 and the node 30 in FIG. 1. In the IAB network, the wireless backhaul function is provided for the IAB node, so that the access node that connects the UE to the core network is called an IAB donor (IAB donor), such as the node 10 in FIG. 1. Taking data uplink transmission as an example, the node 20 may send data received from the UE to the node 10 through a wireless backhaul link, and the access node 10 then sends the UE data to the core network element. Taking data downlink transmission as an example, the core network element sends the UE data packet to the node 10, the access node 10 then sends the UE data to the node 20 through the wireless backhaul link, and then the access node 20 sends the UE data through the access link To the UE.

In addition, supporting the separate deployment of CU (Centralized Unit) and DU (Distributed Unit) is an important technical feature in NR (New Radio). Therefore, in the separate deployment scenario of CU and DU Also need to support IAB function. Figure 2 is a schematic diagram of the network IAB deployment in which CU and DU are separated. As shown in Figure 2, IAB nodes can have DU-like functions and MT (Mobile Terminal, mobile terminal)-like functions. MT-like functions are also UE-like functions. IAB nodes access two parent IAB nodes through dual connections, that is, IAB The nodes connect to the parent IAB node 1 and the parent IAB node 2 respectively through dual connections.

When the IAB node accesses the network, there may be DUs or base stations that do not support the IAB function near the IAB node. If the IAB node is connected to a DU or base station that does not support the IAB function, it will not be able to serve other child IAB nodes or UEs.

In an exemplary embodiment, FIG. 3 is a schematic flowchart of a method for selecting a parent node provided by this application. This method can be applied to the situation where the IAB selects a parent node that supports the IAB function when accessing the network. This method can be executed by the parent node selection device applied to the IAB node provided by the present application, and the parent node selection device can be implemented by software and/or hardware and integrated in the IAB node.

As shown in Fig. 3, a parent node selection method applied to IAB nodes provided by this application includes:

S120: Determine the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.

The IAB node of an IAB node is called the child IAB node of the IAB node, and the DU or base station supporting the IAB function accessed by an IAB node as a connection is called the parent IAB node of the IAB node.

The network access of IAB nodes can be divided into initial access and non-initial access. The deployment scenarios of IAB node access to the network can be divided into multiple types. Specifically, the DU entity and base station in the area can be set according to the deployment location. The IAB function can be divided according to whether the AMF (Access and Mobility Management Function) entity connected to the base station that does not support the IAB function supports the IAB function, and it can also be divided according to the DU entity that does not support the IAB function. Whether the CU entity supports the IAB function, and whether the further connected AMF entity supports the IAB function.

Therefore, when the IAB node selects the parent node that supports the IAB function, it can be determined by combining the access situation of the IAB node and the deployment scenario of the access network. In different access situations and different deployment scenarios, the way the IAB node selects the parent node may be the same or different.

Wherein, the IAB node may be a DU entity or an MT.

This application provides a method for selecting a parent node. When an IAB node accesses the network, the parent node of the IAB node is determined according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network, which effectively solves how the IAB node The problem of selecting the parent node ensures that the parent node selected by the IAB node supports the IAB function, thereby ensuring the IAB function of the IAB node, and achieving the effect of serving other child IAB nodes and UEs.

On the basis of the above-mentioned embodiment, a modified embodiment of the above-mentioned embodiment is proposed. It should be noted that, in order to make the description concise, only the differences from the above-mentioned embodiment are described in the modified embodiment.

In an example, the deployment scenarios for the IAB node to access the network may include the following six deployment scenarios.

The first scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station supporting the IAB function.

As shown in Figure 4, the donor central unit entity (donor CU) 101 is connected to the donor DU102 through the F1 interface, and the donor DU 102 is connected to the IAB node 103 through the backhaul link (BH link). Among them, the donor CU 101, the donor DU102 and IAB nodes 103 all support IAB functions. The IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the first scenario, such as an IAB mobile terminal (IAB-MT) that is undergoing initial access, and all DUs and base stations near the deployed location support IAB function.

The second scenario is: the IAB node deployment location setting area includes the IAB donor DU and the distributed unit entity that does not support the IAB function, and the distributed unit entity that does not support the IAB function is connected to the donor centralized unit entity donor CU.

As shown in Figure 5, the donor CU 101 is connected to the donor DU 102 through the F1 interface, and is connected to the normal distribution unit entity (normal DU) 105, and the donor DU 102 is connected to the IAB node 103 through the BH link. Among them, the donor CU 101, Both the donor DU 102 and the IAB node 103 support the IAB function, and the conventional distributed unit entity 105 does not support the IAB function. The IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the second scenario, for example, an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support IAB functions Donor DU 102, and normal DU 105 that does not support IAB.

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

As shown in Figure 6, AMF 107 is connected to donor CU 101 through the NG interface and connected to base station (gNB) 106. The AMF 107 connected to donor CU 101 and the AMF 107 connected to gNB 106 can be the same AMF or They are different AMFs, shown in Figure 6 as an example. The donor CU 101 is connected to the donor DU 102 through the F1 interface, and the donor DU 102 is connected to the IAB node 103 through the BH link. Among them, AMF 107, donor CU 101, donor DU 102 and IAB node 103 all support the IAB function, but gNB 106 does not. IAB function. The IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the third scenario, such as an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support the IAB function Donor DU 102, and gNB 106 that does not support the IAB function, but the AMF 107 connected to the gNB 106 supports the IAB function, and other core network network elements connected to the AMF 107 have network elements that support the IAB function.

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

As shown in Figure 7, AMF 107 is connected to donor CU 101 through the NG interface, and AMF 108 is connected to gNB 106 through the NG interface. The donor CU 101 is connected to the donor DU 102 through the F1 interface, and the donor DU 102 is connected to the IAB node 103 through the BH link. Among them, AMF 107, donor CU 101, donor DU 102 and IAB node 103 all support the IAB function, while AMF 108 and gNB 106 does not support the IAB function. The IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the fourth scenario, for example, an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support IAB functions The donor DU 102 and the gNB 106 that does not support the IAB function, and the AMF 108 connected to the gNB 106 that does not support the IAB function also does not support the IAB function.

The fifth scenario is: the IAB node deployment location setting area includes IAB donor DU, the IAB node and the distributed unit entity that does not support the IAB function, and the centralized unit entity connected to the distributed unit entity that does not support the IAB function does not support IAB function, the access management function entity connected with the centralized unit entity supports the IAB function.

As shown in Figure 8, AMF 107 is connected to donor CU 101 through the NG interface and connected to normal CU109. AMF 107 connected to donor CU 101 and AMF 107 connected to normal CU 109 can be the same AMF or different The AMF is shown in Figure 8 with different examples. The donor CU101 is connected to the donor DU 102 through the F1 interface, the donor DU 102 is connected to the IAB node 103 through the BH link, and the normal CU 109 is connected to the normal DU105 through the F1 interface. Among them, AMF 107, donor CU 101, donor DU 102 and IAB node 103 Both support IAB function, but normal CU109 and normal DU105 do not support IAB function. The IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the fifth scenario, for example, an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support IAB functions Donor DU 102, and normal DU105 that does not support IAB function, and normal CU 109 connected to normal DU105 does not support IAB function, but AMF 107 connected to normal CU 109 supports IAB function, and other core networks connected to AMF 107 Among the network elements, there are network elements that support the IAB function.

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

As shown in Figure 9, AMF 107 is connected to donor CU 101 through an NG interface, and AMF 108 is connected to normal CU 109 through an NG interface. Donor CU 101 is connected to donor DU 102 through F1 interface, donor DU 102 is connected to IAB node 103 through BH link, and normal CU 109 is connected to normal DU 105 through F1 interface. Among them, AMF 107, donor CU 101, donor DU 102 and IAB node 103 all support IAB function, while AMF 108, normal CU 109 and normal DU105 do not support IAB function. The IAB node 104 refers to a node that will be deployed in the IAB network corresponding to the sixth scenario, for example, an IAB-MT that is undergoing initial access, and there are other IAB nodes 103 near the deployed location that support IAB functions The donor DU 102 and the normal DU105 that does not support the IAB function, and the normal CU 109 connected to the normal DU105 that does not support the IAB function, do not support the IAB function, and at the same time, the AMF 108 connected to the normal CU 109 does not support the IAB function.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first to sixth scenarios, and the determining the parent node of the IAB node includes :

The parent node of the IAB node is selected from the parent node list pre-configured by the IAB node.

When the IAB node is initially accessed, when the deployment scenario is any of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node may have a pre-configuration A list of parent nodes, and then you can select one of its pre-configured parent node lists as its parent node.

When the IAB node is non-initial access, when the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node may also have A pre-configured parent node list, and in turn, you can select one of the pre-configured parent node lists as its parent node.

Among them, the pre-configured parent node list is configured by an Operation Administration and Maintenance (OAM) entity, and is added to the configuration information of the IAB node before the IAB node is established. The nodes included in the pre-configured parent node list all support the IAB function.

In an example, the pre-configured parent node list of the IAB node includes at least one of the following:

Currently registered public land mobile network (Public Land Mobile Network, PLMN) cell identity supporting IAB function;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the above method further includes: when the IAB node accesses the cell, judging the IAB according to whether the radio resource control (Radio Resource Control, RRC) reconfiguration message includes a backhaul adaptive protocol layer configuration message Whether the distributed unit entity or base station accessed by the node supports IAB function.

Regardless of whether the IAB node is initially accessed or non-initially accessed, after the IAB node accesses any suitable cell, it can determine whether it is accessed according to whether the RRC reconfiguration message includes a backhaul adaptive protocol layer configuration message. Whether the distributed unit entity or the base station supports the IAB function. When the RRC reconfiguration message includes the backhaul adaptive protocol layer configuration message, the distributed unit entity or base station accessed by the IAB node supports the IAB function; when the RRC reconfiguration message does not include the backhaul adaptive protocol layer configuration message, The distributed unit entity or base station accessed by the IAB node does not support the IAB function.

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

When the IAB node is initially accessed, when the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, when the IAB node accesses the network A node can be selected as its parent node based on the received system information broadcast by the cell.

When the IAB node is non-initial access, and the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node accesses the network It is also possible to select a node as its parent node according to the received system information broadcast by the cell.

In an example, selecting the parent node of the IAB node based on the system information broadcast by the cell includes:

According to whether the system information broadcast by the cell includes the IAB dedicated physical random access channel (Physical Random Access Channel, PRACH) configuration, it is determined whether the cell accessed by the IAB node supports the IAB function.

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

Determine whether the cell accessed by the IAB node supports the IAB function according to whether the system information broadcast by the cell includes IAB dedicated system information, where the IAB dedicated system information includes cell access barring information, admission control parameters, and cell selection parameters , At least one of the cell reselection parameters.

When the system information broadcast by the cell received by the IAB node includes the IAB dedicated system information, it can be determined that the cell accessed by the IAB node supports the IAB function; when the system information broadcast by the IAB node does not include the IAB dedicated system information At this time, it can be determined that the cell accessed by the IAB node does not support the IAB function. Therefore, according to this embodiment, it can also be ensured that the selected parent node supports the IAB function.

The parent node of the IAB node is selected based on the system information used for cell reselection broadcast by the IAB node or the IAB host distribution unit entity.

The IAB node may receive the system information used for cell reselection broadcast by other IAB nodes or IAB donor CU, where the system information used for cell reselection broadcast by the IAB node or IAB donor CU includes at least one of the following:

Frequency information supporting IAB function;

The identity of the cell supporting the IAB function under the currently registered PLMN;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the access situation of the IAB node is initial access, and the deployment scenario is one of the first to sixth scenarios, and the determining the parent node of the IAB node includes:

When the IAB node accesses the cell, obtain a parent node list in the configuration information of the operation management and maintenance entity; select the parent node of the IAB node from the parent node list.

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

Among them, the parent nodes in the parent node list acquired in the OAM configuration information all support the IAB function.

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

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the access situation of the IAB node is non-initial access, the deployment scenario is one of the first to sixth scenarios, and the determining the parent node of the IAB node includes:

The IAB node selects the parent node of the IAB node from the parent node list obtained from the configuration information of the operation management and maintenance entity.

When the IAB node is a non-initial access, and the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node has already switched from OAM The parent node list obtained in the OAM is stored locally in the IAB node, and then a node can be selected as its parent node from the parent node list obtained from the OAM.

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

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

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

The IAB node selects the parent node of the IAB node from a list of parent nodes that the IAB node has obtained from the host centralized unit entity.

When the IAB node is non-initial access, when the deployment scenario is any one of the first, second, third, fourth, fifth, and sixth scenarios, the IAB node has been transferred from the donor The parent node list obtained in the CU is stored locally on the IAB node, and then a node can be selected as its parent node from the parent node list obtained from the donor CU.

Among them, all the nodes in the parent node list obtained from donor CU support the IAB function. The parent node list stored by the donor CU may specifically include at least one of IAB donor DU, IAB node, and gNB supporting the IAB function.

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

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, obtaining the parent node list from the unit entity of the host centralization includes:

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

If the IAB node wants to obtain the parent node list in the donor CU, it can send a request message to the donor CU, for example, a radio resource control layer request message, to request the donor CU to send the parent node list to the IAB node. After the donor CU receives the RRC request message, it sends the parent node list to the IAB node.

In an example, requesting the host central unit entity to send a list of parent nodes through a message includes:

Through the radio resource control layer establishment request message or the radio resource control layer establishment completion message or the radio resource control layer reconfiguration completion message, the donor centralization unit entity is requested to send the parent node list.

When the IAB node requests the donor CU to send the parent node list through the RRC message, it can specifically request the donor CU to send the parent node list through the radio resource control layer setup request (RRC Setup Request) message, or it can be completed through the radio resource control layer (RRC Setup Complete) ) The message requests the donor CU to send the parent node list, and the radio resource control layer reconfiguration complete (RRC Reconfiguration Complete) message can also request the donor CU to send the parent node list.

Through an F1 establishment request message, a gNB-DU configuration update message, or a new F1 Application Protocol (F1 Application Protocol, F1AP) message, the host central unit entity is requested to send a list of parent nodes.

When the IAB node requests the donor CU to send the parent node list through a message, it can specifically request the donor CU to send the parent node list through the F1 establishment request message, or through the gNB-DU configuration update message to request the donor CU to send the parent node list, or through the new The F1AP message requests the donor CU to send the list of parent nodes.

Receive the parent node list actively sent by the donor centralization unit entity through a radio resource control layer message.

The parent node list sent by the donor CU received by the IAB may also be sent by the donor CU actively through the RRC message.

In an example, receiving the parent node list actively sent by the host central unit entity through a radio resource control layer message includes:

Receive the parent node list from which the donor centralization unit entity actively sends a radio resource control layer reconfiguration message or a radio resource control layer release message or a radio resource control layer reject message.

When the donor CU actively sends the parent node list to the IAB node through the RRC message, it can send the parent node list to the IAB node through the radio resource control layer reconfiguration (RRC Reconfiguration) message, or through the radio resource control layer release (RRC Release) message. The IAB node sends the parent node list, and can also send the parent node list to the IAB node through a radio resource control layer reject (RRC Reject) message.

Among them, in the foregoing embodiment, the nodes in the parent node list sent by the donor CU to the IAB node all support the IAB function.

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

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

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:

When the IAB node accesses a cell, when the donor centralization unit entity determines that the DU accessed by the IAB node does not support the IAB function, it re-determines the IAB node's status according to the auxiliary operation of the donor centralization unit entity Parent node.

When the IAB node is initially accessed, and the deployment scenario is the second scenario, after the IAB section is connected to any suitable cell, the donor CU determines whether the DU accessed by the IAB node supports the IAB function. The DU accessed by the IAB node does not support the IAB function, and the donor CU assists the IAB node to reselect a node as its parent node.

When the IAB node is non-initial access, and the deployment scenario is the second scenario, after the IAB section is connected to any suitable cell, the donor CU determines whether the DU accessed by the IAB node supports the IAB function. The DU accessed by the IAB node does not support the IAB function, and the donor CU assists the IAB node to reselect a node as its parent node.

In an example, re-determining the parent node of the IAB node according to the auxiliary operation of the unit entity in the host set includes:

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

When the donor CU judges that the DU accessed by the IAB node does not support the IAB function, it may send a switching instruction to the IAB node to switch the parent node of the IAB node to a node that supports the IAB function.

Receive the radio resource control layer release message sent by the donor centralization unit entity, disconnect the original DU, and obtain the parent node list sent by the donor centralization unit entity through the radio resource control layer message, according to the parent node The list re-determines the parent node of the IAB node.

When the donor CU judges that the DU accessed by the IAB node does not support the IAB function, if the IAB node has completed the connection with the DU that does not support the IAB function, it can send an RRC release message to the IAB node to enable the After the IAB node receives the RRC release message sent by the donor CU, it disconnects the DU that does not support the IAB function.

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.

Receive the radio resource control layer rejection message sent by the donor centralization unit entity, disconnect the original DU, and obtain the parent node list sent by the donor centralization unit entity through the radio resource control layer message, according to the parent node The list re-determines the parent node of the IAB node.

When the donor CU judges that the DU accessed by the IAB node does not support the IAB function, if the IAB node is already establishing a connection with the DU that does not support the IAB function, it can send an RRC rejection message to the IAB node so that all After the IAB node receives the RRC rejection message sent by the donor CU, it abandons the continued connection operation with this DU that does not support the IAB function, and after receiving the parent node list sent by the donor CU, re-starts based on the parent node list. Select a node as its parent node.

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

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:

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the list of parent nodes obtained from the unit entity in the host set includes:

The donor DU and IAB nodes connected to the donor centralization unit entity, and the donor DU and IAB nodes connected to the neighboring base stations of the donor centralization unit entity.

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

In an example, the method for the host central unit entity to learn whether the DU supports the IAB function includes:

According to the DU, it is indicated in the F1 establishment request message or the gNB-DU configuration update message or the new F1AP message that the DU supports the IAB function.

The DU can indicate to the donor CU that it supports the IAB function through an F1 establishment request message or a gNB-DU configuration update message or a new F1AP message.

In an example, the method of generating or updating the parent node list by the host central unit entity includes:

The donor centralized unit entity obtains a list of base stations supporting the IAB function from the configuration information of the operation, management and maintenance entity, where the list of base stations supporting the IAB function includes information of base stations supporting the IAB function and information of serving cells supporting the IAB function.

Donor CU can obtain a list of base stations that support the IAB function from OAM, where the base station list obtained from OAM can include information about base stations that support the IAB function, and can also include information about serving cells that support the IAB function.

The donor centralization unit entity exchanges the information of the serving cell supporting the IAB function with the neighboring base station through the Xn establishment request message or the Next Generation Radio Access Network (NG-RAN) node configuration update information.

The donor CU can use the Xn establishment request to interact with neighboring base stations to support the serving cell information of the IAB function, or through the NG-RAN node configuration update information to interact with the neighboring base station to support the IAB function of the serving cell information, so as to obtain the neighboring base station Serving cell information that supports the IAB function.

In an example, when the host central unit entity determines that the DU accessed by the IAB node does not support the IAB function, re-determining the parent node of the IAB node according to the auxiliary operation of the host central unit entity includes:

Instruct the IAB node to support the IAB function in the radio resource control layer establishment request message;

When the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, the parent node of the IAB node is re-determined according to the auxiliary operation of the donor centralized unit entity.

Instruct the IAB node to support the IAB function in the radio resource control layer establishment complete message;

When the donor centralized unit entity learns that the IAB node supports the IAB function through the IAB authorization indication carried in the initial context establishment request message, and determines that the DU accessed by the IAB node does not support the IAB function, the donor centralized unit The auxiliary operation of the entity redefines the parent node of the IAB node.

That is, the IAB node may indicate its IAB node identity to the donor CU in the RRC establishment request message, and may also indicate its IAB node identity to the donor CU in the RRC establishment complete message.

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

When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, in an example, re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:

Receive the radio resource control layer rejection message sent by the donor centralization unit entity, disconnect the original DU, and re-determine the parent node of the IAB node.

When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can send an RRC rejection message to the IAB node (this When the RRC establishment complete message sent by the IAB node is not received), the IAB node re-selects the cell after receiving the RRC reject message.

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

Support IAB frequency information;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, in an example, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can receive the IAB After the RRC establishment complete message sent by the node, the RRC release message is sent to the IAB node, and the IAB node performs cell selection again after receiving the RRC release message.

In an example, the RRC release message includes at least one of the following:

Support IAB frequency information;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

After receiving the donor centralization unit entity, after determining that the initial access process of the IAB node ends, send a radio resource control layer release message, disconnect the original DU, and re-determine the parent node of the IAB node.

When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the initial access of the IAB node After the process ends, an RRC release message is sent to the IAB node, and after receiving the RRC release message, the IAB node performs cell selection again.

In an example, the RRC release message includes at least one of the following:

Support IAB frequency information;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

According to the handover instruction sent by the donor centralization unit entity after determining that the initial access process of the IAB node ends, the parent node supporting the IAB function corresponding to the handover instruction is re-determined as the parent node of the IAB node.

When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment request message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the initial access of the IAB node After the process is over, a switch instruction is sent to the IAB node to switch the parent node of the IAB node to a node that supports the IAB function.

When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment complete message, in an example, re-determining the parent node of the IAB node according to the auxiliary operation of the donor centralization unit entity includes:

Receive the radio resource control layer release message sent by the donor centralization unit entity, disconnect the original DU, and re-determine the parent node of the IAB node.

When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment complete message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can send an RRC release message to the IAB node After receiving the RRC release message, the IAB node performs cell selection again.

In an example, the RRC release message includes at least one of the following:

Support IAB frequency information;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment complete message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the initial access of the IAB node After the process ends, it sends an RRC release message to the IAB node, and after receiving the RRC release message, the IAB node performs cell selection again.

In an example, the RRC release message includes at least one of the following:

Support IAB frequency information;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

When the IAB node indicates its IAB node identity to the donor CU in the RRC establishment complete message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the initial access of the IAB node After the process is over, a switch instruction is sent to the IAB node to switch the parent node of the IAB node to a node that supports the IAB function.

When the donor CU learns the IAB node identity of the IAB node in the IAB authorization indication carried in the initial context establishment request message, in an example, the parent node of the IAB node is re-determined according to the auxiliary operation of the host centralized unit entity, include:

When the donor CU learns the IAB node identity of the IAB node in the IAB authorization indication carried in the initial context establishment request message, if the donor CU recognizes that the DU accessed by the IAB node does not support the IAB function, the donor CU can wait for the IAB node After the initial access procedure ends, an RRC release message is sent to the IAB node, and the IAB node performs cell selection again after receiving the RRC release message.

In an example, the RRC release message includes at least one of the following:

Support IAB frequency information;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

When the donor CU learns the IAB node identity of the IAB node in the IAB authorization indication carried in the initial context establishment request message, the donor CU can send a handover instruction to the IAB node after waiting for the end of the initial access process of the IAB node to transfer the IAB node The parent node of the node switches to a node that supports the IAB function.

In an example, the above method further includes: updating the locally stored parent node list according to the configuration update information sent by the operation management and maintenance entity.

In the case that the IAB node has stored the parent node list locally, if the OAM configures the parent node list for the IAB node, the IAB node can update the locally stored parent node list according to the configuration information of the OAM.

In an example, when the parent node list stored by the OAM changes, the OAM may send the parent node information whose IAB function has changed to the IAB node, so that the IAB node can pair the parent node information according to the received IAB function change. The locally stored parent node list is updated.

In an example, when the parent node list stored by the OAM changes, the OAM may send the updated parent node list to the IAB node, so that the IAB node can update the locally stored parent node list according to the received parent node list.

In an example, the parent node list stored by OAM includes at least one of the following:

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the above method further includes: updating the locally stored parent node list according to the parent node update information sent by the host central unit entity.

The donor CU stores a list of IAB donor DU and/or IAB nodes and/or gNB that support the IAB function. If the list stored in the donor CU changes, the parent node update information is sent to the IAB node to make the IAB node Update the locally stored parent node list.

In an example, updating the locally stored parent node list according to the parent node update information sent by the host central unit entity includes:

The locally stored parent node list is updated according to the parent node information of the IAB function change sent by the donor centralized unit entity through the radio resource control layer message or the F1 establishment response message or the gNB-CU configuration update message or the new F1AP message.

If there is an IAB donor DU or IAB node or gNB in the list stored in the donor CU that changes the function that supports IAB, the donor CU can send the IAB donor DU, IAB node, and gNB whose IAB function has changed to the IAB node, which can be The RRC reconfiguration message or the F1 establishment response message or the gNB-CU configuration update message or the new F1AP message is sent to the IAB node, so that the IAB node updates the local parent node list.

The locally stored parent node list is updated according to the updated parent node list sent by the donor centralization unit entity through a radio resource control layer message or an F1 establishment response message or a gNB-CU configuration update message or a new F1AP message.

If there is an IAB donor DU or IAB node or gNB in the list stored in the donor CU that supports IAB function changes, the donor CU can send the locally updated parent node list to the IAB node, which can be established through the RRC reconfiguration message or F1 A response message or a gNB-CU configuration update message or a new F1AP message is sent to the IAB node, so that the IAB node updates the local parent node list.

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.

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

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

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an exemplary embodiment, FIG. 10 is a schematic flowchart of a method for selecting a parent node provided by this application. This method can be applied to the situation where the IAB selects a parent node that supports the IAB function when accessing the network. The method can be executed by the parent node selection device applied to the AMF entity provided in this application, and the parent node selection device can be implemented by software and/or hardware and integrated in the AMF entity.

As shown in Figure 10, a parent node selection method applied to an AMF entity provided by this application includes:

S220: Based on the handover of the NG interface, send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralization unit entity or the base station corresponding to the target parent node.

Among them, the handover based on the NG interface mainly includes the case where the donor CU or the base station connected to the IAB node is connected to the same AMF entity, the case of connecting different AMF entities, and the case of connecting to different RATs (Radio Access Technology, radio Access technology).

In the method for selecting a parent node provided by this application, after the IAB node determines the target parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node’s access to the network, the IAB node The IAB authorization indication information or the IAB node indication of the IAB node is sent to the donor central unit entity or base station corresponding to the target parent node, which realizes the connection between the IAB node and the parent node that supports the IAB function selected by the IAB node. The IAB function is guaranteed, and the effect of serving other sub-IAB nodes and UEs is achieved.

In an example, sending the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralization unit entity or base station corresponding to the target parent node includes:

Send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralized unit entity or base station corresponding to the target parent node through an NGAP (Next Generation Application Protocol) handover request message .

Send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the host centralized unit entity or base station corresponding to the target parent node through a path switch request confirmation message.

This embodiment also provides a parent node selection device. FIG. 11 is a schematic structural diagram of a parent node selection device provided by this application. As shown in FIG. 11, an embodiment of this application provides a parent node applied to an IAB node. The selection device can be integrated in the IAB node. The device includes:

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

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

Among them, the IAB node of an IAB node is called the child IAB node of the IAB node, and the DU or base station supporting the IAB function accessed by an IAB node as a connection identity is called the parent IAB node of the IAB node.

The IAB node may be a DU entity or an MT.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is set to: The parent node of the IAB node is selected from the parent node list preconfigured by the IAB node.

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the above-mentioned apparatus further includes a parent node IAB function judgment module, which is set to judge whether the radio resource control layer reconfiguration message includes a backhaul adaptive protocol layer configuration message when the IAB node accesses the cell. Whether the distributed unit entity or base station accessed by the IAB node supports the IAB function.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is set to: The broadcasted system information selects the parent node of the IAB node.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is set to: Whether the broadcast system information includes the IAB-specific PRACH configuration, it is determined whether the cell accessed by the IAB node supports the IAB function.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is set to: Whether the broadcasted system information includes IAB dedicated system information, determine whether the cell accessed by the IAB node supports the IAB function, where the IAB dedicated system information includes cell access barring information, admission control parameters, cell selection parameters, cell Reselect at least one of the parameters.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is set to: The system information used for cell reselection broadcast by the node or the IAB host distribution unit entity selects the parent node of the IAB node.

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

Frequency information supporting IAB function;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the access condition of the IAB node is initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is set to: the IAB node accesses the cell In the case of obtaining the parent node list in the configuration information of the operation management and maintenance entity; selecting the parent node of the IAB node from the parent node list.

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the access condition of the IAB node is non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is configured to: The parent node of the IAB node is selected from the parent node list obtained in the OAM configuration information.

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the access condition of the IAB node is non-initial access, the deployment scenario is one of the first to sixth scenarios, and the first parent node selection module 320 is configured to: The parent node of the IAB node is selected from the acquired parent node list in the unit entity of the host centralization.

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the first parent node selection module 320 is configured to request the host central unit entity to send a parent node list through a message, so that the host central unit entity sends the parent node list to the IAB node after receiving the request , And select the parent node of the IAB node from the list of parent nodes that the IAB node has obtained from the host centralized unit entity.

In an example, the first parent node selection module 320 is configured to request the donor central unit entity to send the parent node through a radio resource control layer establishment request message or a radio resource control layer establishment completion message or a radio resource control layer reconfiguration completion message. Node list, and select the parent node of the IAB node from the parent node list that the IAB node has obtained from the host centralized unit entity.

In an example, the first parent node selection module 320 is configured to request the host central unit entity to send a list of parent nodes through an F1 establishment request message or a gNB-DU configuration update message or a new F1AP message, and send the parent node list to the IAB The node selects the parent node of the IAB node from the parent node list that has been obtained in the unit entity of the host centralization.

In an example, the first parent node selection module 320 is configured to: receive the parent node list actively sent by the host centralized unit entity via a radio resource control layer message, and obtain the parent node list from the host centralized unit entity by the IAB node. Select the parent node of the IAB node in the parent node list.

In an example, the first parent node selection module 320 is configured to receive a list of parent nodes sent by the donor centralized unit entity actively through a radio resource control layer reconfiguration message or a radio resource control layer release message or a radio resource control layer rejection message , And select the parent node of the IAB node from the list of parent nodes that the IAB node has obtained from the host centralized unit entity.

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: In this case, when the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, the parent node of the IAB node is re-determined according to the auxiliary operation of the donor centralized unit entity.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: In this case, when the host central unit entity determines that the DU accessed by the IAB node does not support the IAB function, according to the switching instruction sent by the host central unit entity, the parent node supporting the IAB function corresponding to the switching instruction Re-determined as the parent node of the IAB node.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: In this case, when the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, it receives the radio resource control layer release message sent by the donor centralized unit entity, disconnects the original DU, and Obtain the parent node list sent by the donor centralization unit entity through a radio resource control layer message, and re-determine the parent node of the IAB node according to the parent node list.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: In this case, when the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, it receives the radio resource control layer rejection message sent by the donor centralized unit entity, disconnects the original DU, and Obtain the parent node list sent by the donor centralization unit entity through a radio resource control layer message, and re-determine the parent node of the IAB node according to the parent node list.

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the parent node list obtained from the unit entity in the host set includes:

The donor centralization unit entity interacts with the neighboring base station through the Xn establishment request message or the NG-RAN node configuration update information, and exchanges the information of the serving cell supporting the IAB function.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is configured to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; when the donor centralization unit entity determines that the DU accessed by the IAB node does not support the IAB function, it re-determines the parent of the IAB node according to the auxiliary operation of the donor centralization unit entity node.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is configured to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; receives the radio resource control layer rejection message sent by the donor centralization unit entity, disconnects the original DU, and re-determines the parent node of the IAB node.

Support IAB frequency information;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is configured to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; receives the radio resource control layer release message sent by the donor centralization unit entity after receiving the RRC establishment complete message, disconnects the original DU, and re-determines the IAB node The parent node.

In an example, the RRC release message includes at least one of the following:

Support IAB frequency information;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; receiving the donor centralization unit entity, after determining the end of the initial access process of the IAB node, sends a radio resource control layer release message, disconnects the original DU, and Re-determine the parent node of the IAB node.

In an example, the RRC release message includes at least one of the following:

Support IAB frequency information;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: establish a request message in the radio resource control layer Indicates that the IAB node supports the IAB function; according to the handover instruction sent by the host central unit entity after determining that the initial access process of the IAB node ends, the parent node supporting the IAB function corresponding to the handover instruction is determined again Is the parent node of the IAB node.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: establish a complete message in the radio resource control layer Indicates that the IAB node supports the IAB function; when the donor centralization unit entity determines that the DU accessed by the IAB node does not support the IAB function, it re-determines the parent of the IAB node according to the auxiliary operation of the donor centralization unit entity node.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: establish a complete message in the radio resource control layer Indicates that the IAB node supports the IAB function; receives the radio resource control layer release message sent by the donor centralization unit entity, disconnects the original DU, and re-determines the parent node of the IAB node.

In an example, the RRC release message includes at least one of the following:

Support IAB frequency information;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: establish a complete message in the radio resource control layer Indicates that the IAB node supports the IAB function; receiving the donor centralization unit entity, after determining the end of the initial access process of the IAB node, sends a radio resource control layer release message, disconnects the original DU, and Re-determine the parent node of the IAB node.

In an example, the RRC release message includes at least one of the following:

Support IAB frequency information;

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is set to: establish a complete message in the radio resource control layer Indicates that the IAB node supports the IAB function; according to the handover instruction sent by the host central unit entity after determining that the initial access process of the IAB node ends, the parent node supporting the IAB function corresponding to the handover instruction is determined again Is the parent node of the IAB node.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is configured to: pass through the host central unit entity When the IAB authorization indication carried in the initial context establishment request message learns that the IAB node supports the IAB function, and determines that the DU accessed by the IAB node does not support the IAB function, re-determine all the units according to the auxiliary operation of the donor central unit entity The parent node of the IAB node.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is configured to: pass through the host central unit entity When the IAB authorization indication carried in the initial context establishment request message learns that the IAB node supports the IAB function, and determines that the DU accessed by the IAB node does not support the IAB function, the host central unit entity is received, and the IAB node is determined After the initial access process ends, the sent radio resource control layer release message disconnects the original DU, and re-determines the parent node of the IAB node.

In an example, the RRC release message includes at least one of the following:

Support IAB frequency information;

The identity of the cell supporting the IAB function currently registered;

All the cell identities that support the IAB function;

Global cell identification code;

Physical cell identity.

In an example, the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the first parent node selection module 320 is configured to: pass through the host central unit entity When the IAB authorization indication carried in the initial context establishment request message learns that the IAB node supports the IAB function, and determines that the DU accessed by the IAB node does not support the IAB function, it is determined according to the donor central unit entity that the IAB node is initially The switching instruction sent after the end of the access process re-determines the parent node supporting the IAB function corresponding to the switching instruction as the parent node of the IAB node.

In an example, the above-mentioned apparatus further includes a first parent node list update module, which is configured to update the locally stored parent node list according to configuration update information sent by the operation management and maintenance entity.

In an example, the first parent node list update module is configured to update the locally saved parent node list according to the parent node information sent by the operation management and maintenance entity whose IAB function has changed.

In an example, the first parent node list update module is configured to update the locally stored parent node list according to the updated parent node list sent by the operation management and maintenance entity.

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

In an example, the above-mentioned apparatus further includes a second parent node list update module, configured to update the locally stored parent node list according to the parent node update information sent by the unit entity in the host centralization.

In an example, the second parent node list update module is configured to: according to the IAB function sent by the host central unit entity through a radio resource control layer message or an F1 establishment response message or a gNB-CU configuration update message or a new F1AP message The changed parent node information updates the locally stored parent node list.

In an example, the second parent node list update module is configured to: according to the updated information sent by the host central unit entity through a radio resource control layer message or an F1 establishment response message or a gNB-CU configuration update message or a new F1AP message Parent node list, update the locally stored parent node list.

In an example, the second parent node list update module is configured to update the local parent node list according to the parent node list carried in the RRC release message.

In an example, the second parent node list update module is configured to update the local parent node list according to the parent node list carried in the RRC rejection message.

All PLMN cell identities that support IAB function;

Global cell identification code;

Physical cell identity.

This embodiment also provides a parent node selection device. FIG. 12 is a schematic structural diagram of a parent node selection device provided by this application. As shown in FIG. 12, an embodiment of the application provides a parent node applied to an AMF entity. The selection device can be integrated in the AMF entity. The device includes:

The second parent node selection module 420 is configured to switch based on the NG interface and send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralized unit entity or base station corresponding to the target parent node.

The device for selecting a parent node in an AMF entity provided in this embodiment is used to implement the method for selecting a parent node in an AMF entity as described in the embodiment of this application, and the parent node in an AMF entity provided in this embodiment The implementation principle and technical effect of the selection device are similar to the parent node selection method applied to the AMF entity described in the embodiment of the present application, and will not be repeated here.

In an example, the second parent node selection module 420 is configured to: send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the home set corresponding to the target parent node through an NGAP switching request message Unit entity or base station.

In an example, the second parent node selection module 420 is configured to: send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the corresponding parent node via a path switch request confirmation message Donor central unit entity or base station.

The embodiment of this application provides an IAB node. FIG. 13 is a schematic structural diagram of an IAB node provided by this application. As shown in FIG. 13, the IAB node provided by this application includes: one or more processors 510 and storage The processor 510 of the IAB node may be one or more. One processor 510 is taken as an example in FIG. 13; the storage device 520 is used to store one or more programs; the one or more programs are One or more processors 510 execute, so that the one or more processors 510 implement the parent node selection method applied to the IAB node as described in the embodiment of the present invention.

The processor 510 and the storage device 520 in the IAB node may be connected through a bus or in other ways. In FIG. 13, the connection through a bus is taken as an example.

The storage device 520, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as the program instructions/modules (for example, , Applied to the first parent node selection module 320 in the parent node selection device of the IAB node). The storage device 520 may include a storage program area and a storage data area. The storage program area may store an operating system and an application program required by at least one function; the storage data area may store data created according to the use of the device, and the like. In addition, the storage device 520 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some examples, the storage device 520 may further include a memory remotely provided with respect to the processor 510, and these remote memories may be connected to the first node through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

The embodiments of this application provide an access management function entity. FIG. 14 is a schematic structural diagram of an access management function entity provided by this application. As shown in FIG. 14, the access management function entity provided by this application includes: One or more processors 610 and storage devices 620; the processor 610 of the access management function entity may be one or more, and one processor 610 is taken as an example in FIG. 14; the storage device 620 is used to store one or more Program; The one or more programs are executed by the one or more processors 610, so that the one or more processors 610 implement the parent of the access management functional entity as described in the embodiment of the present invention Node selection method.

The processor 610 and the storage device 620 in the access management function entity may be connected through a bus or other methods. In FIG. 14, the connection through a bus is taken as an example.

The storage device 620, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as the program instructions corresponding to the parent node selection method applied to the access management functional entity as described in the embodiments of this application. Module (for example, the first parent node selection module 420 applied to the parent node selection device of the access management functional entity). The storage device 620 may include a storage program area and a storage data area. The storage program area may store an operating system and an application program required by at least one function; the storage data area may store data created according to the use of the device, and the like. In addition, the storage device 620 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some examples, the storage device 620 may further include memories remotely provided with respect to the processor 610, and these remote memories may be connected to the first node through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

The embodiment of the present application also provides a storage medium, the storage medium stores a computer program, and when the computer program is executed by a processor, it implements the parent node selection method or the parent node selection method applied to the IAB node in any of the embodiments of the present application. Any method for selecting a parent node applied to an access management functional entity described in the embodiments of the present application.

Wherein, the parent node selection method applied to the IAB node includes: determining the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.

The parent node selection method applied to the access management functional entity includes: based on the handover of the NG interface, sending the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the host centralized unit entity corresponding to the target parent node Or base station.

The above are only exemplary embodiments of the present application, and are not used to limit the protection scope of the present application.

Those skilled in the art should understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

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

The embodiments of the present application may be implemented by executing computer program instructions by a data processor of a physical device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. Computer program instructions can be assembly instructions, instruction set architecture (Instruction Set Architecture, ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages Source code or object code.

The block diagram of any logical flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program can be stored on the memory. The memory can be of any type suitable for the local technical environment and can be implemented by any suitable data storage technology, such as but not limited to read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (ASICs) ), programmable logic devices (Field-Programmable Gate Array, FGPA), and processors based on multi-core processor architecture.

By way of exemplary and non-limiting examples, a detailed description of the exemplary embodiments of the present application has been provided above. However, considering the accompanying drawings and claims, various modifications and adjustments to the above embodiments are obvious to those skilled in the art, but they do not deviate from the scope of the present invention. Therefore, the proper scope of the present invention will be determined according to the claims.

Claims

A method for selecting a parent node, which is applied to IAB nodes in the self-access backhaul link, includes:

Determine the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.
The method according to claim 1, wherein the IAB node includes at least one of a distributed network element DU and a mobile terminal MT.
The method according to claim 1, wherein the deployment scenario is one of the first scenario to the sixth scenario;

The first scenario is: the IAB node deployment location setting area includes the IAB host distribution unit entity donor DU, the IAB node and the base station supporting the IAB function;

The second scenario is: the IAB node deployment location setting area includes an IAB donor DU and a distributed unit entity that does not support the IAB function, and the distributed unit entity that does not support the IAB function is connected to the donor centralized unit entity donor CU;

The third scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station that does not support the IAB function, and the access management function entity connected to the base station that does not support the IAB function Support IAB function;

The fourth scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the base station that does not support the IAB function, and the access management function entity connected to the base station that does not support the IAB function Does not support IAB function;

The fifth scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the distributed unit entity that does not support the IAB function are connected to the distributed unit entity that does not support the IAB function. The unit entity does not support the IAB function, and the access management function entity connected to the centralized unit entity supports the IAB function;

The sixth scenario is: the IAB node deployment location setting area includes the IAB donor DU, the IAB node and the distributed unit entity that does not support the IAB function, and the centralized connection to the distributed unit entity that does not support the IAB function The unit entity does not support the IAB function, and the access management function entity connected to the centralized unit entity does not support the IAB function.
The method according to claim 3, wherein the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first scenario to the sixth scenario, and the Determining the parent node of the IAB node includes:

The parent node of the IAB node is selected from the parent node list pre-configured by the IAB node.
The method according to claim 3, wherein the access status of the IAB node is initial access or non-initial access, the deployment scenario is one of the first scenario to the sixth scenario, and the Determining the parent node of the IAB node includes:

The parent node of the IAB node is selected based on the system information broadcast by the cell.
The method according to claim 5, wherein the selecting the parent node of the IAB node based on the system information broadcast by the cell comprises:

According to whether the system information broadcast by the cell includes the IAB dedicated physical random access channel configuration, determine whether the cell accessed by the IAB node supports the IAB function; or,

Determine whether the cell accessed by the IAB node supports the IAB function according to whether the system information broadcast by the cell includes IAB dedicated system information, where the IAB dedicated system information includes cell access barring information, admission control parameters, and cell selection parameters , At least one of the cell reselection parameters; or select the parent node of the IAB node based on the system information for cell reselection broadcast by the IAB node or the IAB host distribution unit entity, wherein the parent node for the cell reselection The selected system information includes at least one of the following:

Frequency information supporting IAB function;

The identity of the cell supporting the IAB function under the current registered public land mobile network;

All public land mobile networks supporting IAB function cell identity;

Global cell identification code;

Physical cell identity.
The method according to claim 3, wherein the access condition of the IAB node is initial access, the deployment scenario is one of the first scenario to the sixth scenario, and the determining the IAB node The parent node includes:

In the case that the IAB node accesses the cell, acquiring the parent node list in the configuration information of the operation management and maintenance entity;

Select the parent node of the IAB node from the parent node list.
The method according to claim 3, wherein the access condition of the IAB node is non-initial access, the deployment scenario is one of the first scenario to the sixth scenario, and the determining the IAB The parent node of the node, including:

Select the parent node of the IAB node from the list of parent nodes that the IAB node has obtained from the configuration information of the operation management and maintenance entity.
The method according to claim 3, wherein the access condition of the IAB node is non-initial access, the deployment scenario is one of the first scenario to the sixth scenario, and the determining the IAB The parent node of the node, including:

Select the parent node of the IAB node from the list of parent nodes that the IAB node has obtained from the host centralized unit entity.
The method according to claim 9, wherein obtaining the list of parent nodes from the host centralized unit entity comprises:

Request the host central unit entity to send the list of parent nodes through a message, so that the host central unit entity sends the list of parent nodes to the IAB node after receiving the request; or,

Receiving the parent node list actively sent by the donor centralization unit entity through a radio resource control layer message.
The method according to claim 10, wherein requesting the host central unit entity to send the list of parent nodes through a message comprises:

Request the donor central unit entity to send the parent node list through a radio resource control layer establishment request message or through the radio resource control layer establishment complete message or through the radio resource control layer reconfiguration complete message; or,

Request the host central unit entity to send the parent node list through an F1 interface establishment request message or a gNB-DU configuration update message or a new F1 application protocol F1AP message;

Receiving the parent node list actively sent by the donor centralization unit entity through a radio resource control layer message includes:

Receiving the parent node list sent by the donor centralization unit entity actively through a radio resource control layer reconfiguration message or a radio resource control layer release message or a radio resource control layer rejection message.
The method according to claim 3, wherein the access status of the IAB node is initial access or non-initial access, the deployment scenario is the second scenario, and the determining the parent node of the IAB node ,include:

In the case that the IAB node accesses a cell, when the donor centralization unit entity determines that the DU accessed by the IAB node does not support the IAB function, the IAB node is re-determined according to the auxiliary operation of the donor centralization unit entity The parent node.
The method according to claim 12, wherein the re-determining the parent node of the IAB node according to the auxiliary operation of the host central unit entity comprises:

According to the switching instruction sent by the host central unit entity, the parent node supporting the IAB function corresponding to the switching instruction is re-determined as the parent node of the IAB node; or,

Receive the radio resource control layer release message or radio resource control layer rejection message sent by the donor centralized unit entity, disconnect the original DU, and obtain the parent node sent by the donor centralized unit entity through the radio resource control layer message List, and re-determine the parent node of the IAB node according to the parent node list.
The method according to any one of claims 4, 7, 8, 9 and 13, wherein the parent node list includes at least one of the following:

The identity of the cell supporting the IAB function under the current registered public land mobile network;

All public land mobile networks supporting IAB function cell identity;

Global cell identification code;

Physical cell identity.
The method according to claim 9 or 13, wherein the parent node list obtained from the host central unit entity comprises:

The donor DU and IAB nodes connected to the donor centralization unit entity, and the donor DU and IAB nodes connected to the neighboring base stations of the donor centralization unit entity.
The method according to claim 15, wherein the manner in which the donor centralization unit entity determines whether the DU accessed by the IAB node supports IAB function comprises:

According to the DU accessed by the IAB node, it is indicated in the F1 interface establishment request message or the gNB-DU configuration update message or the new F1AP message that the DU accessed by the IAB node supports the IAB function.
The method according to claim 15, wherein the method of generating or updating the parent node list by the host central unit entity comprises:

The donor centralized unit entity obtains a list of base stations supporting IAB function from the configuration information of the operation, management and maintenance entity, wherein the list of base stations supporting IAB function includes information of base stations supporting IAB function and information of serving cells supporting IAB function; or ,

The donor centralized unit entity interacts with neighboring base stations through the Xn interface establishment request message or the next-generation radio access network NG-RAN node configuration update information, and interacts with neighboring base stations to support the serving cell information of the IAB function.
The method according to claim 12, wherein when the donor concentration unit entity determines that the DU accessed by the IAB node does not support the IAB function, the IAB is re-determined according to the auxiliary operation of the donor concentration unit entity The parent node of the node, including:

Instruct the IAB node to support the IAB function in the radio resource control layer establishment request message;

When the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, the parent node of the IAB node is re-determined according to the auxiliary operation of the donor centralized unit entity.
The method according to claim 18, wherein the re-determining the parent node of the IAB node according to the auxiliary operation of the host central unit entity comprises:

Receiving a radio resource control layer rejection message sent by the donor centralization unit entity, disconnecting the original DU, and re-determining the parent node of the IAB node;

Wherein, the radio resource control layer rejection message includes at least one of the following:

Support IAB frequency information;

The identity of the cell supporting the IAB function under the current registered public land mobile network;

All public land mobile networks supporting IAB function cell identity;

Global cell identification code;

Physical cell identity.
The method according to claim 12, wherein when the donor concentration unit entity determines that the DU accessed by the IAB node does not support the IAB function, the IAB is re-determined according to the auxiliary operation of the donor concentration unit entity The parent node of the node, including:

Instruct the IAB node to support the IAB function in the radio resource control layer establishment complete message;

When the donor centralized unit entity determines that the DU accessed by the IAB node does not support the IAB function, the parent node of the IAB node is re-determined according to the auxiliary operation of the donor centralized unit entity.
The method according to claim 20, wherein the re-determining the parent node of the IAB node according to the auxiliary operation of the host central unit entity comprises:

Receiving the radio resource control layer release message sent by the donor centralization unit entity, disconnecting the original DU, and re-determining the parent node of the IAB node;

The radio resource control layer release message includes at least one of the following:

Support IAB frequency information;

The identity of the cell supporting the IAB function under the current registered public land mobile network;

All public land mobile networks supporting IAB function cell identity;

Global cell identification code;

Physical cell identity.
The method according to claim 12, wherein when the donor concentration unit entity determines that the DU accessed by the IAB node does not support the IAB function, the IAB is re-determined according to the auxiliary operation of the donor concentration unit entity The parent node of the node, including:

When the donor centralization unit entity learns that the IAB node supports the IAB function through the IAB authorization indication carried in the initial context establishment request message, and determines that the DU accessed by the IAB node does not support the IAB function, according to the donor concentration The auxiliary operation of the unit entity redefines the parent node of the IAB node.
The method according to any one of claims 18, 20 and 22, wherein the re-determining the parent node of the IAB node according to the auxiliary operation of the entity of the host centralization unit comprises:

Receiving the radio resource control layer release message sent by the donor centralized unit entity after determining that the initial access process of the IAB node is completed, disconnecting the original DU, and re-determining the parent node of the IAB node; or ,

Re-determining the parent node supporting the IAB function corresponding to the switching instruction as the parent node of the IAB node according to the handover instruction sent by the host central unit entity after determining that the initial access process of the IAB node is completed;

Wherein, the radio resource control layer release message includes at least one of the following:

Support IAB frequency information;

The identity of the cell supporting the IAB function under the current registered public land mobile network;

All public land mobile networks supporting IAB function cell identity;

Global cell identification code;

Physical cell identity.
The method according to claim 1, further comprising:

According to the parent node update information sent by the host central unit entity, the locally saved parent node list is updated.
The method according to claim 24, wherein the updating the locally stored parent node list according to the parent node update information sent by the host centralized unit entity comprises:

According to the parent node information of the IAB function change sent by the host central unit entity through the radio resource control layer message or the response message established by the F1 interface or the gNB-CU configuration update message or the new F1AP message, perform the locally stored parent node list Update; or,

The locally saved parent node list is updated according to the updated parent node list sent by the host central unit entity through the radio resource control layer message or the response message established by the F1 interface or the gNB-CU configuration update message or the new F1AP message.
A method for selecting a parent node, applied to an access management function entity, includes:

Based on the handover of the NG interface, the IAB authorization indication information of the self-access backhaul link IAB node or the IAB node indication of the IAB node is sent to the donor central unit entity or base station corresponding to the target parent node.
The method according to claim 26, wherein the sending the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralization unit entity or the base station corresponding to the target parent node comprises:

Send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the host centralization unit corresponding to the target parent node through a next generation application protocol NGAP switching request message or a path switching request confirmation message Entity or base station.
A device for selecting a parent node, which is applied to a self-access backhaul link IAB node, includes:

The first parent node selection module is configured to determine the parent node of the IAB node according to the access situation of the IAB node and the deployment scenario of the IAB node accessing the network.
A parent node selection device, applied to an access management functional entity, includes:

The second parent node selection module is configured to switch based on the NG interface and send the IAB authorization indication information of the IAB node or the IAB node indication of the IAB node to the donor centralized unit entity or base station corresponding to the target parent node.
An IAB node, including:

At least one processor;

The storage device is set to store at least one program;

When the at least one program is executed by the at least one processor, the at least one processor realizes the method for selecting a parent node according to any one of claims 1-25.
An access management functional entity, including:

At least one processor;

The storage device is set to store at least one program;

When the at least one program is executed by the at least one processor, the at least one processor implements the method for selecting a parent node according to claim 26 or 27.
A storage medium storing a computer program, and when the computer program is executed by a processor, the method for selecting a parent node according to any one of claims 1-25 is realized, or the method for selecting a parent node according to any one of claims 1-25, or the method for selecting a parent node as described in claim 26 or 27 is realized. The parent node selection method.